Ubuntu Installation for FOG (12.04+)
-
[quote=“rhythmtone, post: 25214, member: 57”]Hello,
Thanks for the guide. I’ve been using FOG for several years now and I’ve stayed on Ubuntu 11.10 with no problems. However, 11.10 is no longer supported and is getting pretty “long in the tooth”, so I’ve decided to attempt a FOG installation on Ubuntu 13.10. Of course, until I have it working, I do not want to take my 11.10 installation offline, so everything is being done in a test environment.But I have run into an issue, with Ubuntu 13.10. When I type this command:
[U]sudo –c ‘echo “greeter-show-manual-login=true” >> /etc/lightdm/lightdm.conf’[/U]
I get a “Permission denied” error…
I thought that it could be a directory permissions problem so I ran:
sudo chmod -R 777 /etc/lightdm
After modifying the permissions and re-running the command from the guide, it simply says:
sudo -c: command not found
I must be missing something obvious, but any help with this would be greatly appreciated as I was hoping to use some kind of guide/instructions to get FOG .32/.33b up and running on a Ubuntu 13.10 system.
Thanks for reading![/quote]
I think the syntax is incorrect.
Shouldn’t it just be:
[code]sudo ‘echo “greeter-show-manual-login=true” >> /etc/lightdm/lightdm.conf’[/code] -
I have the same issue today under 12.04.4 LTS :
[U]sudo –c ‘echo “greeter-show-manual-login=true” >> /etc/lightdm/lightdm.conf’[/U]
I get a “Permission denied” error…
Then I discovered on the internet:
[U]sudo sh –c ‘echo “greeter-show-manual-login=true” >> /etc/lightdm/lightdm.conf’[/U]
This worked. No idea why. How would the sh help?
Now for my real question: Do I HAVE TO install FOG whilst logged in as ROOT??
Can’t I just stay logged in as a normal user and type:
sudo .[COLOR=#141414][FONT=Courier New]/installfog.sh[/FONT][/COLOR]
Grateful for an answer today if someone is on line and can be bothered. I want to go forward with the install.
[COLOR=#141414][FONT=Courier New][/FONT][/COLOR] -
You can install with just sudo ./installfog.sh
The reason, I think, adding the sh -c is because the -c is usually for the su command, I don’t believe the sudo command supports the -c argument.
-
Thanks Tom, but I’ve already started as root.
-
Terribly sorry about that, I have fixed the issue, thanks for reporting it!
-
Thanks for the reply, you guys are the best. As always, your work is very, very appreciated.
I am a little bit pressed for time, but I will certainly get back to this soon, and report on how it goes. I’m still chugging along with 11.10 for now but really want to move to 12.04 as it is LTS.
Regarding updates, is the new 3.14.0 x64 Tom Elliott kernel supported in Fog 0.32 x64? If so, where is the init.gz for that kernel? I’m positive that I cannot load the 3.14.0 x64 kernel because I am using the stock init.gz from a FOG 0.32 x64 installation. Maybe this setup is not supported and I have to use FOG 0.33b to use the x64 kernel?
I’ve have however had good success with the 3.14.0 Tom Elliott x86 kernel using the stock init.gz from a FOG 0.32 x64 installation.
Thank you,
D.L. -
This post is deleted! -
The tom elliott kernel’s are built in both formats. 32bit and 64bit.
The caveat is that you have to rename the bzImage32 file to bzImage for FOG 0.32 to recognize it properly.
Currently my site is down, so use the svn.
I’m at 3.14.1 already:
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage32[/url] (PROBABLY WHAT YOU NEED, JUST RENAME TO bzImage ON THE FOG SERVER)
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage[/url] (64 bit kernel. Not what you need for FOG 0.32.)
There is no 64bit FOG 0.32 init.gz file that I’ve built so if you MUST use 64 bit stuff, you’d have to upgrade to 0.33b, or be patient, and once I get my Storage Server back up, I might try to generate a 64 bit init.gz for FOG 0.32 just for you cause I’m a nice guy!
-
Thanks Tom!
I’m aware of the naming conventions, etc., and I usually manage the kernels manually from the terminal, but thanks for clarifying.Do not worry about an x64 init.gz, unless you have extra time, haha! As you suggest, I don’t really need to use it under FOG 0.32, I just thought that it could be an interesting test. The 3.14.0 x86 Tom Elliott kernel has been great on a stock FOG 0.32 installation, and I will definitely try 3.14.1 today or tomorrow!
Thanks again for your work and dedication to this project!
-
i am having a lot of trouble getting this to work
when i issue the command
sed -i ‘s/udpcastsrc=“…/packages/udpcast-20071228.tar.gz”/udpcastsrc=“…/packages/udpcast-20120424.tar.gz”/’ …/lib/common/config.sh
i get
sed: -e expression #1, char 27: unknown option to `s’
can someone tell me what i am doing wrong
i am using ubuntu 13.10
-
you can sudo gedit the file and change the information if that command doesn’t do the job.
all it is doing is looking in the file and changing the /udpcastsrc=“…/packages/udpcast-20071228.tar.gz” to /udpcastsrc=“…/packages/udpcast-20120424.tar.gz” in the …/lib/common/config.sh
Look in your fog folder for /lib/common/config.sh
use sudo gedit config.sh and change line /udpcastsrc=“…/packages/udpcast-20071228.tar.gz” to /udpcastsrc=“…/packages/udpcast-20120424.tar.gz”
-
So I finally got back to this… I combined the knowledge from this thread with the Wiki post on Ubuntu 14.04 found here:
[url]http://www.fogproject.org/wiki/index.php/Ubuntu_14.04[/url]
I was able to get the udpcastsrc path/config updated. I think that it is best to do it manually using gedit because there are 2 references to the old version inside config.sh:
/udpcastsrc=“…/packages/udpcast-20071228.tar.gz” to /udpcastsrc="…/packages/udpcast-20120424.tar.gz
and there is another entry 2 lines below this that also needs to be changed, I believe. My server is unavailable at the moment, but remember changing it twice (will post path later, if necessary).
The problem is however that under Ubuntu 14.04 I can’t get TFTP to work correctly, so I don’t yet have a working FOG server on this release. Under 11.10, everything works great. I’ve used the exact same network settings, with a different static IP, and everything else is the same (kernel, drivers, etc).
At PXE boot it just says:
TFTP. . .
The progress creeps slowly until a message saying TFTP timeout (or something similar) appears and it never reaches the FOG PXE menu…
Any help would be greatly appreciated! I plan on trying it on 12.04 on Monday…
Thanks again!
-
My guess is the interface is the issue.
What’s the interface elements? Are they eth0,1,2 or are they p5p1,2,3?
-
Thanks for the reply Tom! I will find out…
It did ask if I wanted to change the default interface from eth0 on installation; not sure if that is plain text or a variable called up from the system…
You’re the best!
PS - Happy Friday! Beer’s on me!
-
Hi,
ifconfig lists the network interface it as eth0, is there somewhere else I should be looking?Thanks!
-
All,
Just to help out, hopefully, a little more. Change the sed commands in the tutorial to:
[code]sed -i ‘s:udpcastout=“udpcast-20071228”:udpcastout=“udpcast-20120424”:’ …/lib/common/config.sh
sed -i ‘s:udpcastsrc=“…/packages/udpcast-20071228.tar.gz”:udpcastsrc=“…/packages/udpcast-20120424.tar.gz”:’ …/lib/common/config.sh[/code] -
If anyone wants to do it the manual/gedit/nano way here is what I did:
/fog_0.32/lib/common/
gedit config.shwhere are the udpcast files from the download package?
udpcastsrc=“…/packages/udpcast-20071228.tar.gz”;
udpcasttmp=“/tmp/udpcast.tar.gz”;
udpcastout=“udpcast-20071228”;You just change the date on the 2nd and 4th lines above from 20071228 to 20120424, save, navigate to /fog_0.32/packages/ and download the new UDPcast :
/fog_0.32/packages/
wget [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/udpcast-20120424.tar.gz[/url]With this change, FOG will install/configure correctly on Ubuntu 14.04 with the newer UDPcast.
But even though it does install/configure correctly, I still can’t get it to PXE boot in my environment… it fails to PXE boot with a TFTP timeout error. I’m going to try it on 12.04 today or soon, but it is strange that it won’t PXE boot at all…Thanks,
D.L.PS - In 10.04 and 11.10 everything works great, so I know that it’s not my network setup that is the problem. Somewhere there is a PXE/TFTP/Linux/Ubuntu/FOG compatibility problem in 12.04+
