I don’t know of a method of confirming the actual svn revision. Maybe somebody else can be of more help in this regard.
Posts made by Tom Elliott
RE: Fog Cleaning Hard Disks
What version of FOG were you using when this happened to you? I haven’t seen any issues with this as we, in 2011, had received systems with Windows 7, but were, at that time, supporting Windows XP. We created the Windows XP image and uploaded to the relevant system and had no issues that I’m aware of. We were using FOG 0.32, and still are.
RE: Kernel: cannot open /proc/partitions
The FOG 0.33 hdparm, not registering issue you’re seeing, I don’t know how to help out with that completely, unless you can let me in remotely to assess the issue, but even if you’re able to get past the hdparm issue, you still won’t be able to register the host. 0.33b has removed the host association of the OS field, and now the OS is assigned to the image file itself. This makes perfect sense, except the auto.register.php file still has references to inputting the hostOS which it fails because that table doesn’t exist. I’m going to upload my auto.register.php script, this file goes in:
Also, if you know how to modify the init.gz system -> follows:
cd /tftpboot/fog/images; mkdir tmp; gunzip init.gz; mount -o loop init tmp; cd tmp/bin
Then you’ll have to modify the fog.man.reg file to remove the hostOS input field. I’ll post a copy of that file as well.
You can remove the file fog.man.reg then do:
Then type the letter i
Then paste the contents fog.man.txt file here into that file. (sorry i can’t just give fog.man.reg, but they don’t allow uploading an extension of .reg)
Once pasted in:
Type the key esc, then type:
chmod +x fog.man.reg
gzip -9 init
Then you should be good to go without inputting host os.
If all of the init.gz editing seems too complicated, at the very least get rid of the auto.register.php file in fog/service/ and insert the one I’ve provided.
When I first started with fog 0.33b I had the same hdparm issue as you are experiencing, but my exact issue, seemingly, was due to the system not reading the right areas because of my pxe default file missing the trailing slashes as needed. Then I ran into the full registration issue with it and found out about the hostOS field missing from the hosts table in the fog database.
Hopefully this helps you out.
RE: Custom init.gz
So I found out, today, why It isn’t creating the sys.img.000 file. It’s because, with my custom init.gz, it doesn’t recognize the /dev/sda2 partition. I don’t know why it doesn’t, but it doesn’t. I think it’s because the device_table.txt file, isn’t actually set in the config to use the static table versus the dynamic one, but for whatever reason, it only cares about it on the single disk, resizable option. I’ll keep testing to try to narrow it down. I’ve removed the references to partclone as it doesn’t build for some reason. It could be I haven’t got a clue (most likely) or because fog actually manually writes it’s partclone files to the system any way. I’m building now with static table reference.
Just for posterity, I think I need to add this here. To add the fog components to the menu system, after you copy customize to package in buildroot, don’t forget to add source “package/customize/Config.in” somewhere in package/Config.in file. I added mine at the top, right above busybox. Don’t place it outside of a menu reference, so my source line is the 2nd line in the file.
RE: PXE Menu update failed.
When editing the default file,
You’ll find the first PASSWD line as:
MENU MASTER PASSWD <YOUR ENCRYPTED PASSWORD> <-This controls when somebody hits the ESC key>
and the menu options (full host reg, quick img, etc…) as:
MENU PASSWD <YOUR ENCRYPTED PASSWORD> <- When trying to enter a menu option.
For your knowledge, you shouldn’t need them to be encrypted, but, if you prefer to have it encrypted fog has a utility to do that for you which is located in:
To run the command type in a terminal:
/opt/fog/utils/md5pass <YOUR [B]UNENCRYPTED [/B]PASSWORD>
Then copy the line printed out which will look something like:
$1$aobkelGl$gX3rr1kioMdm12KvCCW7N0 (this is the md5pass of password)
Copy that line, and paste it in your desired spots.
RE: Kernel: cannot open /proc/partitions
Are you running FOG 0.33? The init.gz has a few changes to it which may be causing the issue. I don’t when I followed the build a custom init information, using a newer version of buildroot, I ran into the same type of issue because it never even copied the right file structure to the host.