[LEFT]You can restore a single database from a mysqldump of all-databases.[/LEFT]
[LIST]
[*]mysql -u root -p[I]PASSWORD[/I] --one-database [I]DB[/I] < [I]DBfilename[/I].sql
[/LIST]
[INDENT=1][LEFT][url]http://dev.mysql.com/doc/refman/5.1/en/mysql-command-options.html#option_mysql_one-database[/url][/LEFT][/INDENT]

found code online for FOG Service.
[url]http://fossies.org/dox/fog_0.32/MOD__DisplayManager_8cs_source.html[/url]

hey chat-bisd - thanks for the reply.

I have booted the VM into debug mode, I noticed that when I do an ifconfig the eth0 card is not detected - which is strange! I tried updating the kernel to 3.2.4 with the VMware SCSI Driver Support included - however it still does not detect the eth0 card.

When I run the compatibility test with FOG the hard disk passes but network fails…

Any tips??

was this error from the VM you are uploading, or the real machine you are trying to image?

They are telling you to update the TFTP uesrname and password in the fog web UI settings to match

Try reading through this. It sounds long and complicated, but I just put every detail I could into it. You won’t have the same selections, but it will lead you to the right places to make your selections for your hardware.

[url]http://fogproject.org/forum/threads/compiling-a-custom-kernel-for-acer-iconia-tab-copied-from-old-forums.216/[/url]

Ok, I’m an idiot…I was choosing open instead of save file before I downloaded the application. It’s working now…sorry for my stupidity o_O

My conclusion that it works with CentOS 5.8 was a bit too soon. The problem persist when multicasting from a storage node, even though it works from the main server.

[quote=“khowe2000, post: 2826, member: 636”]I had the same issue until I upgrade my kernel to 3.2.4 core. It is most likely a missing driver from the other kernel modules or something. My 6710b work fine now. Fog 0.32 with Kernel 3.2.4 core.[/quote]

This worked. Thanks a lot!

It was basically guesswork as to what would and wouldn’t work so I just sat it aside while I worked on other open projects.

For others with this problem:
The 3.2.4 kernel is not working currently in the update console, if you get the error Download Failed: filesize = 0 follow the instructions in posts 8 & 9 in this thread to manually download and install it: [url]http://fogproject.org/forum/threads/kernel-3-2-4-core.298/[/url]

I just solved a problem like this for myself. It turned out my Ubuntu mysql installation sets mysql to listen to 127.0.0.1 only. When I changed the IP to the actual IP and opened the firewall (main FOG server), it worked as intended.

On Ubuntu, the config file in question is /etc/mysql/my.cnf, the setting is "bind-address = ".

This all makes sense, unfortunately I have already started rebuilding this system. This just gave me a good excuse to do it, but I was already unhappy with the partitioning. Before FOG I was trying MDT and installing onto the third partition of the Dell factory setup, thus the deleting the recovery partition in the middle and the wasted space. I have actually, since the mishap, switched to the latest KitchenSink kernel. So in the end, even if it all works well, there will have been too many variables to say what actually broke last time. Thanks to all for the help.

I chose SLAX just for simplicity and file size. It is just for an personal experiment, but if it works, I intend to deploy all over our lab for different uses in each department. We develop custom apps for internal use in our Photo Lab and if I can deploy a live OS over PXE, then there would be no more need for our Windows XP machines and no Windows will save us money on anti-virus licenses.

I am going to take a guess and say I am missing some sort of required package in CENTOS Minimal. Any idea what that might be? I followed the exact same setup on ubuntu and it worked prefect.

Have a look at my solution to another issue - [url]http://fogproject.org/forum/threads/fog-server-fatal-error-failed-to-mount-nfs-volume.115/#post-3647[/url]

In short, with a share on openfiler the NFS path was mildly different to the path on the FTP share, that meant that although my NFS share was /mnt/raid6/data/FOG the ftp path was published as /raid6/data/FOG. A couple of edits within FOG and all was well again.