Hi, Ady:> > > I would suggest not using the work "disk".me:> > I am unhappy with "disk" too. > > But that change would have a much wider scope in the text.Ady:> You can still use a different wording in a linked section. If "disk" > is not the best choice for the new section, then choose a better > term.Two problems: There are probably reasons why "disk" was chosen as term for the wiki. I am reluctant to overthrow this choice without backing from SYSLINUX developers. What term to use instead of "disk" ? "Drive" might be more modern, but an USB stick is not actually a drive. "Device" is probably a unixism and also anbigous, because partitions are devices, too. Finding a new term and getting agreement is worth a separate wiki overhaul project.> > > It [SYSLINUX] works on GPT too. > > This is hopefully a feature, not a problem. :o) > Yes, my point is that a casual user might (mis)interpret (from > certain paragraphs) that Syslinux is for MBR only.This is an interesting wiki enhancement project, too. Starting at the statement on the main wiki: "prepare a normal MS-DOS formatted disk". First one would have to collect tangible information. (I know GPT as i know MBR: on byte level only.) Have a nice day :) Thomas
I played with `mkdiskimage' some last night, here is what i came up with:
mkdiskimage -z -F binary.img 1000
i="$(losetup -f --show binary.img)"
j="$(kpartx -savu "${i}" | awk '{print
"/dev/mapper/"$3 }')"
mount "${j}" /mnt
cp /usr/lib/syslinux/vesamenu.c32 /mnt
cat > /mnt/syslinux.cfg <<EOF
UI vesamenu.c32
DEFAULT linux
LABEL linux
EOF
umount /mnt
syslinux "${j}"
kpartx -d "${i}"
losetup -d "${i}"
kvm binary.img
and it is done, and tested.
This makes a binary hard disk image file, which is partitioned, mounted,
and populated.
Thanks syslinux devs. `mkdiskimage' shaves 3 commands off of this everyday
process. Bringing new comers one step closer to understanding how an entire
system works, and is built.
-dean
Hi, Dean Graff wrote:> mkdiskimage -z -F binary.img 1000 > i="$(losetup -f --show binary.img)" > j="$(kpartx -savu "${i}" | awk '{print "/dev/mapper/"$3 }')" > mount "${j}" /mnt > [...] > umount /mnt > syslinux "${j}" > kpartx -d "${i}" > losetup -d "${i}" > kvm binary.imgI am collecting text for "What is a SYSLINUX disk ?" which brought me to the topic of disk image files. http://www.syslinux.org/wiki/index.php/User:Scdbackup#Populating_disk_images_by_program_syslinux Now i wonder why you take the effort with losetup and kpartx. We know that mkdiskimage -z creates the partition at block 32. So can't you just do: mkdiskimage -z -F binary.img 1000 mount -o loop,offset=16384 binary.img /mnt ... umount syslinux --offset 16384 binary.img kvm binary.img Did i miss something essential here ? Would this work for you ? (Older syslinux is said to have used option -o rather than --offset) Have a nice day :) Thomas