Latest FOG 0.33b
-
[quote=“Tom Elliott, post: 24678, member: 7271”]What is the difference between nlist and rawlist?
What would happen if I just did basename to the path being sent? Would this, theoretically, work properly as the basename of /volumes1/images would be images and the basename of /images would also be images?
The only issue I see with using basename is for those file systems where you need the full path for things to work. I believe this is why nlist was used. It allows you to read the contents within a specified directory. I’m still under the impression that the NAS boxes just need to be configured so /volume1 is not where it plops you in for FTP. It should be relatively simple, though I don’t have a NAS to test with.[/quote]
I’m not strong enough in English to translate everything, but hey never mind, I will continue to change myself both programs.Yet these modules certainly pose problems to other people as we speak in “FOGuserGuide-> Separate_NFS_Server” a rewrite these modules …
[url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Separate_NFS_Server[/url] -
Yes it doesn’t actually deploy the image and the task disappears from active task.
my image is Multi Part All Disk (Non-Resizable) and single too (I tried 2),and the os otherI’ll try again
sorry for my bad english :oops:
I’m not a hurry! you are already a lot to us!!
-
Hello .
I am trying to install FOG 0.33 with dnsmasq .
Following this guide :
[QUOTE]Chainloading iPXE using dnsmasq setup
This information pertains to FOG 0.33 and the new iPXE boot method.
In order to continue to use dnsmasq to dole out ip addresses and to help find the boot file, some changes need to be made to force the boot file to load the iPXE boot file.
The old pxelinux.0 file is still included in the fog installation as pxelinux.0.old but this file has been replaced by a new file called [B]undionly.kpxe[/B]. We will use this file, undionly.kpxe, in place of the pxelinux.0 file when setting up the ltsp.conf file.
The reason we are able to do this is because pxe boot looks for files that match a query of names, first starting with the MAC address of the machine and moving down the list until it reaches the default file. We are going to create a file for it to find every time it queries for the default file.
[LIST=1]
[]Create a default file for undionly.kpxe to load (you may substitute gedit for your favorite text editor):
sudo mkdir pxelinux.cfg
cd pxelinux.cfg
sudo gedit default
[]Insert the following lines and edit the server ip address to reflect your own FOG server:
DEFAULT vesamenu.c32
LABEL fog
MENU DEFAULT
kernel ipxe.krn dhcp && chain [url]http://(fog-server-ip-address)/fog/service/ipxe/boot.php?mac=${net0/mac}[/url]
PROMPT 0
TIMEOUT 01
[*]Save your files and restart your dnsmasq service with the following command:
sudo service dnsmasq restart
[/LIST]
[/QUOTE]didn’t have any success in booting at all .Then , I have renamed “pxelinux.0.old” in “pxelinux.0” , and now I can boot from PXE .
Now ,a client computer find “pxelinux.0” , load it, and then loads iPXE file.(i think)
How can I make use of [B]undionly.kpxe file ? [/B]In this workaround , I don’t think i am using it. -
The option 67 where it tells what file to load during boot (your system is probably using pxelinux.0) point it at undionly.kpxe. Thant’s it.
-
[quote=“Vlad.R, post: 24685, member: 23134”]Hello .
I am trying to install FOG 0.33 with dnsmasq .
Following this guide :
didn’t have any success in booting at all .
Then , I have renamed “pxelinux.0.old” in “pxelinux.0” , and now I can boot from PXE .
Now ,a client computer find “pxelinux.0” , load it, and then loads iPXE file.(i think)
How can I make use of [B]undionly.kpxe file ? [/B]In this workaround , I don’t think i am using it.[/quote]In the past, I was not aware that undionly.kpxe is a drop in replacement for pxelinux.0
You do not need to use the pxelinux.0 file. instead replace it with undionly.kpxe
-
For my probleme in debug I make fdisk /dev/sda and type w
and the deploy start -
Does anyone know how to specify an http proxy for undionly.kpxe?
Thanks.
-
r1384 released.
More “default” reports added to the ReportManagementPage. Still not complete, so you should see the originals. Fixes issue in virus history on host displaying improperly. Adds legacy flagging ability so if you are upgrading to newer revisions of 0.33, you can set whether the image is a “partimage” or “partclone” image. Legacy checked for these images means partimage is what the image is set for and will image as. Legacy unchecked the system will use partclone. More documentation added.
-
[quote=“Tom Elliott, post: 23426, member: 7271”]As I don’t have any Mac’s in my possession, it will likely be a little while, unless you can give what the output of the command: [code]blkid -po udev <partitionnumber>[/code] for each of the partitions on the system (especially a freshly installed system) it’ll probably be a little bit.
While I have made sure to have the partclone.hfsp binary available, and also included the hfs file system support in the kernel, I don’t know what to check for to get the MPS/MPA imaging types to use the proper binary.[/quote]
Tom, I’m not sure whether this is exactly what you were looking for or not, but if not, let me know. Apparently Mac OS doesn’t have the blkid command, so I booted from a linux live cd to get the info. The machine was a MacBook 1,1, freshly imaged with 10.6.8 using DeployStudio.
elementary@elementary:~$ sudo blkid -po udev /dev/sda
ID_PART_TABLE_TYPE=gptelementary@elementary:~$ sudo blkid -po udev /dev/sda1
ID_FS_LABEL=EFI
ID_FS_LABEL_ENC=EFI
ID_FS_UUID=70D6-1701
ID_FS_UUID_ENC=70D6-1701
ID_FS_VERSION=FAT32
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_NAME=EFI\x20System\x20Partition
ID_PART_ENTRY_UUID=62f42160-c44f-48e3-94ab-ba3acef0e71f
ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=40
ID_PART_ENTRY_SIZE=409600
ID_PART_ENTRY_DISK=8:0elementary@elementary:~$ sudo blkid -po udev /dev/sda3
ID_FS_UUID=7e9cb753-bf5c-343c-8dad-cd086af5164b
ID_FS_UUID_ENC=7e9cb753-bf5c-343c-8dad-cd086af5164b
ID_FS_LABEL=Macintosh_HD
ID_FS_LABEL_ENC=Macintosh\x20HD
ID_FS_TYPE=hfsplus
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_NAME=DS_DEV_DISK_X
ID_PART_ENTRY_UUID=a954672e-850a-4493-b852-ff139b5e6002
ID_PART_ENTRY_TYPE=48465300-0000-11aa-aa11-00306543ecac
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=409640
ID_PART_ENTRY_SIZE=116538416
ID_PART_ENTRY_DISK=8:0The bigger issue, unless I misunderstand you, is that you’re talking about making the filesystems work so that machines can be imaged using Mac OS and its HFS filesystems. What I intended to post initially was that Macs won’t boot at all from any version of FOG, 0.33b included (at least without doing the steps listed below). I assume it has something to do with EFI and PXE. I’ve found 2 ways to boot from FOG as-is
- get the iPXE image from their site, burn to CD or copy to flash drive, then boot from the newly created iPXE media. Then FOG is found and booted from without further interaction. The con is that to boot from FOG again, you have to use the CD/Flash drive each time.
2)get a Mac install disc compatible with the machine, boot from it, and re-bless the disk using the command “bless --mount /Volumes/Macintosh\ /HD/ --setBoot --legacy --verbose”. The legacy argument seems to force the machine to use some type of legacy BIOS emulation. Reboot, then the machine will boot from FOG as many times as you’d like - I don’t know whether this will persist once the machine is reimaged or not.
- get the iPXE image from their site, burn to CD or copy to flash drive, then boot from the newly created iPXE media. Then FOG is found and booted from without further interaction. The con is that to boot from FOG again, you have to use the CD/Flash drive each time.
-
I updated from revision 1360 to 1384. Did then a few tests and get this error if I try to create a new image definition:
[CODE]FOG DEBUG: Image: Database Load Failed: ID: 0, Error: Operation field not set: ID[/CODE]
I didn’t have done any changes to the web code or the database.
To find the revision where this error appears, I downgraded to older revisions and it looks like that the error comes with revision 1362. -
[quote=“Albatros, post: 24723, member: 16710”]I updated from revision 1360 to 1384. Did then a few tests and get this error if I try to create a new image definition:
[CODE]FOG DEBUG: Image: Database Load Failed: ID: 0, Error: Operation field not set: ID[/CODE]
I didn’t have done any changes to the web code or the database.
To find the revision where this error appears, I downgraded to older revisions and it looks like that the error comes with revision 1362.[/quote]I found out the issue. It’ll be a minute while I have to move the imageLegacy creation as it’s own schema change. I’m going to ask you to, just as a test, check your images table on the FOG database and please see if you have the imageLegacy column. I’m going out on a limb that your table does not have this field. Because it’s missing, it can’t update the new definition properly as it doesn’t know how to set the non-existent field.
-
r1385 released.
Should fix the issue reported by Albatros, and a couple other minor fixes as well.
-
Updated to revision 1385. Opened the webpage that shows me that I need to update the database. Tried then to create a image, still the same problem. I checked the table images no column named imageLegacy present.
Should I create the column by myself? -
Well, change your system.php schema line to 80, then it will ask you to update again, after that it should create image legacy for you.
-
Ty Tom. Column created and problem is fixed.
-
I’ve imaged 20 Windows 8 PC .
I didn’t use sysprep , all computers are the same , didn’t join Active Directory .Hostname Changer only change NetBIOS name , not Computer Name .
-
Did you install the FOG client on this machine?
-
Yes. Fog client is installed, and fog server address is set by ip.
-
Are the host modules enabled to the system?
The hostname changer part, you mean the system rebooted, and this is what happened, or this is what was changed during the “changing hostname” step during the imaging process?
Make sure the host modules are enabled. Make sure the host AD stuff is correct as well.
if you have a 0.32 system you can verify whether this is a problem with Windows 8, or the FOG Client itself. My guess is this is a windows 8 issue, not a client problem as Windows 7 and XP still work right?
-
I am on Fog 0.33
Modules are enabled, the hostname have changed during imaging proces.
New imaged computer didn’t ask for restart at 1’st boot.
On win 7 it works.
