The SVN is bleeding edge, it is not recommended for production environments as we are actively working on bugs and fixes.

It will ALWAYS appear as the “not the current version” in the GUI because you are on a subversion that does not match the current SUPPORTED version. This won’t cause problems and is merely cosmetic, however it is the test bed where we actively work to find solutions to issues user post. It is not WRONG to use the SVN, but if you plan for a production environment, it would probably be better to at least start with the supported version and if you have issues we will tell you to install the latest release in the SVN.

The sourceforge link is the current supported version.

Hi,

no, but that works until you have working nfs and ftp running.
It’s time to cut additional storage nodes out of fog binding.

I think it’s wrong to force people to install fog on each storage node.
The most problem is that people or companys have a big storage system but we cannot install a linux on it to make fog running.

One of the big goal is indipendent storage nodes for fog!

Regards X23

i just added this line to my 000-default.conf

Redirect /index.html [url]http://(fogserver)/fog/management/[/url]

[quote=“Tom Elliott, post: 33056, member: 7271”]Multicast seems to work now. I’m going to go out on a limb and say with 0.32, when you tried installing it failed at UDPCast? This would be the only reason I can imagine why 32bit was needed. This was a common issue.[/quote]

Yes, you are right. It failed with UDPCast. Is there another way of multicast?
For me Multicast (UDPCast) still fails with Fog 1.1.2 and Ubuntu 12.04. (Uploading and Imaging of single clients works)
I also tried with debian 7.6 with the user-change of the images-folder (chown -R fog.root /images)
Storing the password for tftp-user in fog-webmin for debian seems to be not necessary anymore.

among the list of distro’s to install fog on, debian probably receives the most praise, and Ubuntu 14.04 the most scorn.
personally, i run Ubuntu 12.04 LTS server, however.

Have this working with Freenas… Thank you Joshua…

This might help explain the process [url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]

thanks for info and a great project.
i think it has a great potential to grow.
i’ve forgotten the things we have done 5 years ago and looked for the same solution but more managable.
we have used iSCSI and later AOE to boot windows diskless PCs over ethernet.
iSCSI had many issues on booting and work stability: each PC should have its own image and locks it while usage. if some packet loss occures PC hangs because the driver tries to keep connection alive and fails on packet loss (like HDD loss). It had great issue on client count same time booting: if more than 10 - other failed to boot because of timeouts etc…
AoE worked perfectly with one image for all clients and without hangs on packet loss.
Also Windows need one small tool from Windows Embedded called FBWF (File Base Write Filter) to make the bootable disk read only caching file changes on bootable disk to memory untill the next reboot (very great tool to keep system partition virus clean even on local PCs). Page file must be off and RAM should be 2+ Gb to handle RAM bootable partition (500-800Mb) and other running programs.
So the most powerfull profit was to get bootable Windows partition over network with network mounted work read-write partiion.

I hope sometimes you will include this functionality in your project to make it really powerfull solution to do whatever any one needs to create and maintain large amount of client PCs.

[quote=“mark graham, post: 30784, member: 4117”]yeah, i’m pretty familiar with them 🙂

let me whip something up when i can! hopefully within the next week i’ll have something.[/quote]

Thank you SO MUCH!!!

The service is OK but as regards the cron style deploy in the GUI is launched I 3 and I do not see anywhere he yt there log on the server as in Task Management> Scheduled Tasks there a display issue and that is all white …

can they be changed manually in the table of cron?

Le service est OK mais en ce qui concerne le cron style deploy dans l’interface graphique j’en est lancé 3 et je ne les vois nul part, il y t il des log sur le server car dans task management >[URL=‘http://200.133.56.10/fog/management/index.php?node=tasks&sub=sched’]Scheduled Tasks il y a un problème d’affichage et c’est tout blanc…[/URL]

peut on les modifier à la main dans la table de cron ?[URL=‘http://200.133.56.10/fog/management/index.php?node=tasks&sub=sched’][/URL]

If you’re using the RT-N66U Router, I’d highly recommend using dd-wrt firmware on it.

I can ensure that it works.

[quote=“Tom Elliott, post: 29258, member: 7271”]The date.timezone error you’re seeing, is this still an issue?

Edit the php.ini file and place your timezone setting there.[/quote]

Found the file and edited according & no more errors.
File path:
/etc/php.ini

[code]
Date]
; Defines the default timezone used by the date functions
; http://www.php.net/manual/en/datetime.configuration.php#ini.date.timezone
date.timezone = ‘America/Los_Angeles’
[/code]

I´ve used memdisk from /tftpboot and it worked with fog 0.32:)

[quote=“jbsclm, post: 27870, member: 3158”]also see my previous post

[url]http://fogproject.org/forum/threads/chain-booting-0-33-beta-from-0-32.10156/[/url][/quote]

Nice! Did not find it when i was looking for a solution to this. Much cleaner than what i did 😄

[quote=“Tom Elliott, post: 27535, member: 7271”]This thread is fairly old. Almost as old as when I first moved to partclone in the first place. When we released 1.0.0, we defaulted current images as legacy as most people were upgrading from 0.32 to 1.X.X. This means there’s no more need to download, tweak, and reupload. Hope this helps.[/quote]

I only posted this because I just did a fresh install of 1.0.1 last night and I had that problem with old images that I was using. The screen told me my images weren’t partclone images. I wasn’t aware of any legacy option.

BTW, thanks for the hard work. 🙂

no
[url]http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403/#post-26420[/url]

Assuming that the new card is working, ie ifconfig shows eth1 as the network interface, and you can ping successfully from the box, and ping it from others, there is no need to reinstall, from what I remember you need to go into fog settings, and change the instances of eth0 to eth1, and then go into the storage node settings, and again change eth0 to eth1.
Thia worked at 0.32 and I don’t think it will be any different at .33

The best guess that I have is either the mysql information on the node is incorrect and not communicating with the FOG Server. On the Storage Node system, edit the /var/www/{FOGWEBDIR}/commons/config.php and put in the appropriate information for your Main FOG Server’s mysql information. (e.g. Host, Username, Password)

If anyone wants to do it the manual/gedit/nano way here is what I did:

/fog_0.32/lib/common/
gedit config.sh

where 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+

In case anyone was reading this and hoping for an answer to making ubuntu 14.04 (Or any other distro really) Fog 0.33b svn updates easier, smoother, and automated even, I figured out how to do it and put it in a new thread linked below, enjoy 🙂

[url]http://fogproject.org/forum/threads/automating-fog-0-33b-svn-updates-in-ubuntu-14-04-with-cron-easily-adapted-to-other-linux-distros.10409/#post-26438[/url]