Skip to main content

Modifying IVS Init.gz for testing purposes

What

The Imaging Virtual Server (IVS) provides init.gz as the network boot image for imaging targets. In a controlled troubleshooting session, you may need to test a driver, utility, or boot-script change inside that image.

When/Why

Use only for temporary troubleshooting. Work with FileWave Support, keep a restorable copy of the original image, and test on an isolated imaging target before using the modified image more broadly.

How

  1. SSH into the IVS

  2. Back up the original /imaging/netboot/kernel/init.gz to a separate, clearly named file so you can restore it after testing.

  3. Create an empty temporary working directory, such as /tmp/working, and change into that directory before extracting the image.

  4. Expand the init.gz boot image, as: zcat /imaging/netboot/kernel/init.gz | cpio -i -d

  5. Confirm that the boot image expanded inside the working directory before changing any files.

  6. Make the scoped test change, such as editing filewave/bootup.py, replacing a driver, adding a troubleshooting utility, or testing another partclone build.

  7. Before rebuilding, verify that every extracted file is owned by root. Files copied from another workstation can retain the wrong owner, which can break services such as SSH in the boot environment.

  8. From the working directory, rebuild init.gz with the test changes: find . | cpio -o -H newc | gzip -9 > /imaging/netboot/kernel/init.gz. Keep the original backup until testing and rollback are complete.

  9. Enable an imaging association and PXE boot a system and it will use this updated filesystem when it boots

Related Content

No comments to display

Back to top