Modifying IVS Init.gz for testing purposes
What
With the IVS, target devices uses init.gz as the boot image over the network. For troubleshooting purposes, you may want/need to make a change to this image (for instance to change a driver file or to make some workaround).
When/Why
This is not an activity most FileWave administrators will do but is being documented for cases where it is needed. Usually you will do this with support to test something.
How
-
SSH into the IVS
-
Backup the original init.gz so you can restore it if need be (original is in /imaging/netboot/kernel/init.gz)
-
Create a temp working directory like /tmp/working, and make sure you cd into that temp directory
-
Expand the init.gz boot image, as:
zcat /imaging/netboot/kernel/init.gz | cpio -i -d -
You should now find that the boot image is expanded in you working directory
-
Make your changes - such as edit filewave/bootup.py for instance, replace a driver file, add another utility, or modify a version of partclone
-
Once changes are made, now we’ll want to rebuild init.gz incorporating our changes (again make sure you are in your working directory):
find . | cpio -o -H newc | gzip -9 > /imaging/netboot/kernel/init.gz -
Enable an imaging association and PXE boot a system and it will use this updated filesystem when it boots
No Comments