Thanks to Tom and to the Community!

When I do a fresh install under Centos and I update the DB from the browser, I have problems with the SQLs. It’s easy solve it:

[CODE]138c138
< “INSERT INTO " . DATABASE_NAME . ".users VALUES (‘’,‘fog’, MD5(‘password’),‘0000-00-00 00:00:00’,‘’)”,

“INSERT INTO " . DATABASE_NAME . ".users (uName,uPass, uCreateDate, uCreateBy) VALUES (‘fog’, MD5(‘password’),‘0000-00-00 00:00:00’,‘’)”,
140c140
< “INSERT INTO " . DATABASE_NAME . ".supportedOS VALUES (‘’,'”._(“Windows XP”).“', ‘1’)”,

---

“INSERT INTO " . DATABASE_NAME . ".supportedOS (osName,osValue) VALUES ('”._(“Windows XP”).“', ‘1’)”,
142c142
< “INSERT INTO " . DATABASE_NAME . ".schemaVersion VALUES (‘’,‘1’)”

---

“INSERT INTO " . DATABASE_NAME . ".schemaVersion (vValue) VALUES (‘1’)”
147c147
< “INSERT INTO " . DATABASE_NAME . ".supportedOS VALUES (‘’,'”._(“Windows Vista”).“', ‘2’)”,

---

“INSERT INTO " . DATABASE_NAME . ".supportedOS (osName,osValue) VALUES ('”._(“Windows Vista”).“', ‘2’)”,
257c257
< “INSERT INTO " . DATABASE_NAME . ".supportedOS VALUES (‘’,‘Other’, ‘99’)”,

---

“INSERT INTO " . DATABASE_NAME . ".supportedOS (osName,osValue) VALUES (‘Other’, ‘99’)”,
844c844
< (ngmMemberName, ngmMemberDescription, ngmIsMasterNode, ngmGroupID, ngmRootPath, ngmIsEnabled, ngmHostname, ngmMaxClients, ngmUser, ngmPass )

---

           (ngmMemberName, ngmMemberDescription, ngmIsMasterNode, ngmGroupID, ngmRootPath, ngmIsEnabled, ngmHostname, ngmMaxClients, ngmUser, ngmPass, ngmKey )

846c846
< (‘DefaultMember’, ‘“._(“Auto generated fog nfs group member”).”’, ‘1’, ‘1’, ‘/images/’, ‘1’, ‘" . STORAGE_HOST . "’, ‘10’, ‘" . STORAGE_FTP_USERNAME . "’, ‘" . STORAGE_FTP_PASSWORD . "’ )",

           ('DefaultMember', '"._("Auto generated fog nfs group member")."', '1', '1', '/images/', '1', '" . STORAGE_HOST . "', '10', '" . STORAGE_FTP_USERNAME . "', '" . STORAGE_FTP_PASSWORD . "','' )",[/CODE]

In these insert SQLs you must put the column names. In the last one, you must add the ‘ngmKey’ column

This feature is not in the official FOG version, sorry.

[quote=“Tom Elliott, post: 23744, member: 7271”]Just as I stated before.

From menuconfig

Target packages->Debugging, profiling and benchmark, kexec. I also have added the kexec zlib support as well.[/quote]

I will try to built it again. I test your int.xz and the kexec works fine and I boot one linux distro from debug mode when the W7 partition is the default boot. Now, i must to think how to make a “boot task”.

I find it in /usr/sbin, sorry :oops:
You must say me how make you it

This new init.zx don’t have kexec, no?

Thanks for your time.

Which version of buildroot are you using?

Thanks Tom.

I need to boot from different partition, and I would like to develope a new FOG task to do it.

We have some rooms that are used to do scientific computing along the night, therefore, we need to boot at night under linux and under windows during the day. I think to do it using kexec, but I don’t know if is possible.

In my ubuntu kexec tools are installed, but in the init.gz no. I check the option in Debugging, Profiling, and Benchmark->kexec, but later in the init.gz don’t appear kexec command :oops:

Hi,

I need a new init.gz with kexec support, I try with different buidroot versions but can do it. Can anybody help me with this?

[quote=“fabritrento, post: 22341, member: 21607”]
these pc is waked up by wol, but too fast, so some pc start the process other boots from local disk bypassing.
[/quote]

Check the BIOS setup. In HP machines you must setup the WOL boots from Remote Server and not from local machine.

A multicast tasks with 30 clients -> one thread/slot -> one uncompress process
Two diferent multicast tasks, one with 30 clients and other with 15 clients -> two threads/slots -> two uncompress processes
Three diferents multicast tasks, 30, 15, 18 clients -> three threads/slots -> three uncompress processes
…

Each multicast tasks have one uncompress process, no? And the gunzip process is heavier than udp-sender process, and will overload the CPU.

[quote=“Tom Elliott, post: 22156, member: 7271”]Multicast decompression happens on the server, otherwise, the clients, during upload, compress the image.[/quote]

Hi Tom,

And is not better compress and uncompress on the clients? If you have four, five, six or more multicast threads, the server must make four, five, six or more uncompressions, the CPU load increases a lot of, no?

Tom, in the 0.33 version, is the server who makes the compression of the image files, no?

Is not better compress on the client, you can use the client cores, and upload a compressed image ?

FOG uses FTP for different reasons (i think

a) is a PHP script who moves the files from /images/dev/MAC/. to /images/imagename. A PHP script can run shell commands, but is not very safe. FOG uses VSFTP, is more safe.
b) is the FOG master server who runs mv commands, and if you have storage node, you need a FTP command.

We use RHEL 5.9

[quote=“Tom Elliott, post: 19958, member: 7271”]@Fernando, @darkxeno

I’ve been building the svn as a tarball as well.

The link for tarball download will always be:

[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]

Sometimes I don’t update it right away, but as of right now, it’s at r998, the same as svn.[/quote]

I don know it. Thx for your work!!

You must use SVN, for more information: [url]http://www.fogproject.org/wiki/index.php/SVN[/url]

plas plas plas (cheers)

I’m so glad you wrote this post. I think it was necessary that the project developers expose to where you want to go and why they take so long to get a final version and their goals.

I will give my opinion about some points:

[quote=“Chuck Syperski, post: 13088, member: 4”]
[COLOR=#000000][FONT=Arial][SIZE=15px]FOG initially grew quickly in terms of features to it own detriment. I believe we have a number of features that should not be included in the core release of FOG as they are becoming difficult to maintain. A few of these that come to mind include ClamAV and many of the advanced tasks like file recovery, testdisk, and password reset. Many of the features within the Windows service are no longer functional with Windows 7 and up, but I will discuss the Windows service in more detail later. [/SIZE][/FONT][/COLOR]
[/quote]

If some features are obsolete or don’t work under the new OS (like W7 or W8), remove them. If one final user tests FOG and their “tools” [COLOR=#000000][FONT=Arial][SIZE=15px](like file recovery, testdisk, and password reset) and see that they don’t work, then he will say: “The product is not completely good. The product is good, and deploy images well, very well but their “tools” are trash”[/SIZE][/FONT][/COLOR]

[COLOR=#000000][FONT=Arial][SIZE=15px]The EFI/GPT support is really a big problem. And we/you/the commnity must solve it.[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px][/SIZE][/FONT][/COLOR]

You should check the FOGMulticastManager log in /opt/fog/log/multicast.log. The problem is the FOGMulticstManager daemon, this daemon kill your multicast tasks and the tasks of the clients.

[quote=“YuYo, post: 12476, member: 3300”]
I have a couple questions about the process. Let’s say that I want to deploy 19 PCs and set the min-receivers parameter to 15. Supposedly it will start once it reaches 15 PCs, but what about the remaining 4 PCs?

Will they join the same multicast session?
Will the stay out?
Will they wait until the first 15 PCs finish?[/quote]

[B]*Will they join the same multicast session?[/B]
Generally no.
[B]*Will the stay out?[/B]
Probably, they will be stay out of the multicast session.
[B]Will they wait until the first 15 PCs finish?[/B]
No. Generally, they will be stay in the blue screen “Please Wait” and finally, I think, appears a stdio error message.