Re: Multi-arch netinst getting too big
Steve McIntyre st...@einval.com writes: I don't think sym-links are going to work - the filesystem code in isolinux is very simple (e.g. it only supports basic 8.3 filenames!) and I doubt it'll work. Hard links *might*, however. Hi, Largely immaterial, just for the sake of correctness: ISOLINUX does support long (level 2) ISO 9660 plain filenames. Indeed no Rock Ridge or Joliet extensions, though, thus no symlinks, as you stated. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874ogd7x3r@tac.ki.iif.hu
Re: Multi-arch netinst getting too big
Ian Campbell i...@hellion.org.uk writes: On Sat, 2010-06-26 at 21:49 +0200, Ferenc Wagner wrote: Ian Campbell i...@hellion.org.uk writes: On Sat, 2010-06-26 at 21:12 +0200, Ferenc Wagner wrote: Ian Campbell i...@hellion.org.uk writes: Another option might be to combine gtk/initrd.gz and xen/initrd.gz so that the overhead is only the kernel udebs and not duplicating all the other stuff. I probably mentioned this already, but you aren't constrained to a single initrd.gz: you can use several ones separated by commas. Where can I use several? In a Xen domain config file or in some bootloader config or something? Is it actually supported of does it just happen to work by some coincidence? Unfortunately not in a Xen domain config, AFAIK. But isolinux supports it, as per syslinux.txt: It supports multiple filenames separated by commas. This is mostly useful for initramfs, which can be composed of multiple separate cpio or cpio.gz archives. OK, Thanks. It's actually an overlay, so it may be possible to work around the Xen limitation by making the Xen initrd the base one and overwriting its arch dependent parts as needed. Although it probably could be made to work I'm not that keen on making the regular case more complicated/strange (even if supported by the bootloader) in order to support Xen and I suspect nobody else is either. I'd prefer to drop GTK from the Xen images. By all means go ahead. The multi-initrd feature would be most useful for reusing the normal initrds (mostly kernel modules) in the graphical installer I guess. But then again that may not be worth it. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k4pjh8wv@tac.ki.iif.hu
Re: Multi-arch netinst getting too big
Ian Campbell i...@hellion.org.uk writes: Another option might be to combine gtk/initrd.gz and xen/initrd.gz so that the overhead is only the kernel udebs and not duplicating all the other stuff. I probably mentioned this already, but you aren't constrained to a single initrd.gz: you can use several ones separated by commas. On the other hand I've got no idea how much of the initrd contents is arch independent. And I surely wouldn't miss the graphical part of the Xen installer. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vd95d2vi@tac.ki.iif.hu
Re: Multi-arch netinst getting too big
Ian Campbell i...@hellion.org.uk writes: On Sat, 2010-06-26 at 21:12 +0200, Ferenc Wagner wrote: Ian Campbell i...@hellion.org.uk writes: Another option might be to combine gtk/initrd.gz and xen/initrd.gz so that the overhead is only the kernel udebs and not duplicating all the other stuff. I probably mentioned this already, but you aren't constrained to a single initrd.gz: you can use several ones separated by commas. Where can I use several? In a Xen domain config file or in some bootloader config or something? Is it actually supported of does it just happen to work by some coincidence? Unfortunately not in a Xen domain config, AFAIK. But isolinux supports it, as per syslinux.txt: It supports multiple filenames separated by commas. This is mostly useful for initramfs, which can be composed of multiple separate cpio or cpio.gz archives. It's actually an overlay, so it may be possible to work around the Xen limitation by making the Xen initrd the base one and overwriting its arch dependent parts as needed. Hopefully this can be done without wasting much memory, maybe by adding empty files/directories to the overlay initrd. But I don't know a thing about the powerpc bootloader. If that does not support this, the possible gains are somewhat lower. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ocexd15l@tac.ki.iif.hu
