https://bugzilla.novell.com/show_bug.cgi?id=677246
https://bugzilla.novell.com/show_bug.cgi?id=677246#c2
--- Comment #2 from Marcus Schaefer
We have needed a bootable usbstick carrying an installable system. We do it like this:
1. The usb stick has *no* partition and is formatted FAT32, so it can be handled by Windows.
2. The usbstick contains a. a live image, which contains the root file system of the "live" system. It consists of 3 files 1 rootfs.raw 2 vmlinuz 3 initrd b. a target image, maybe specialized to the particular target hardware in question 4 target.raw.gz c. syslinux 5. syslinux.cfg etc. d. install-to-disk script
The usbstick is made bootable, booting from the stick will start syslinux, which in turn will load the kernel (2), the initial ram disk (3) and loop mount the rootfs.raw as READ ONLY. A writeable layer is added using aufs.
The content of the stick itself is made available as /usb/1. The install-to-disk script is called like any application and will install the target.raw.gz image to the disk in the target system. The install-to-disk script will analyze the disk size, calculate sizes of the desired partitions. The image is installed using gzip -cd target.raw.gz | dd of=/dev/sdXXX bs=1M Then the partition table is corrected using fdisk or similar, and after that fsck and resize2fs will expand the root fs to its final size.
The driving reason for doing it this way was, that the boot stick is created on a Windows system, which is not under our control. So using ext2fsd or similar on Windows was no option.
The above mentioned images are all created using kiwi.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.