Init for each machine
-
Hello,
I would like to have a field to set an init for a machine as the kernel.
Best regards,
-
Can you elaborate?
-
why would you want that?
-
We are currently exploiting FOG 1.2.0,and we come up with a problem with the .init file for some of our hosts. As a solution, we thought of re-use the previous version (1.1.1) of the .init file for these particular host, in order to go on testing, without the hassle of putting off the rest of the hosts. Also, sometimes we customize the init.
Best regards,
-
what problem with the init file have you had with some hosts?
if there are problems with the init, we want to know about them
also, what do you customize in init that can’t be done with postdownloadscripts and/or you wouldn’t want for all of your hosts?
[SIZE=2](fyi, you could put these [/SIZE]customizations [SIZE=2]in the init, and activate them on specific hosts with kernel arguments)[/SIZE] -
[quote=“Junkhacker, post: 38615, member: 21583”]what problem with the init file have you had with some hosts?
if there are problems with the init, we want to know about them
also, what do you customize in init that can’t be done with postdownloadscripts and/or you wouldn’t want for all of your hosts?
[SIZE=2](fyi, you could put these [/SIZE]customizations [SIZE=2]in the init, and activate them on specific hosts with kernel arguments)[/SIZE][/quote]
We have 3 images:- windows 7 : os=windows 7 (5), image type = single Disk - Resizable (1)
- Windows xp : os=Windows 2000/XP -(1), image type= single Disk - Resizable (1)
- Linux : os=Linux - (50), image type = Multiple Partition Image - single Disk (Not resizable) - (2)
On optiplex 7010, all images works fine.
On optiplex 755, we have a problem with windows xp :
message on partclone:
device (/dev/sda1) is mounted at
Error exit
After in shell, we have the next message :
Error /dev/sda1 : No such file or directory
- Not expanding (/dev/sda1 imager) … done
Then we imaging with init 1.1.0, we don’t have this problem.
For customizing, yes since 1.2.0, we can customize with postdownloadscript, by the way we just switch the scripts. It’s fine.
Best regards,
Thanks for your very good jobs.
-
if the only reason you want to use custom init’s is because of the xp imaging issue, that problem is fixed in the development version of fog. just use the latest dev version and your problem should go away.
