On 02/18/2010 08:34 PM, Thomas Bächler wrote:
Am 18.02.2010 21:04, schrieb Dan McGee:
On Thu, Feb 18, 2010 at 1:14 PM, Thomas Bächler<thomas@archlinux.org> wrote:
That would leave us with: - kernel x86_64 - initrd x86_64 - kernel i686 - initrd i686 - packages core-any - packages core-i686 - packages core-x86_64 - squashfs base system i686 - maybe overlay-any
All 3 of the "packages" things can go in one big directory anyway- the filenames are all unique since we put the architecture in the package filenames. That would make the mounting process a lot less complex as nothing would need to change between what kernel, processor, etc. you are booting up on or want to install. Only the installer would care.
I would create all those as squashfs images. After that, we can put them together for different ISOs, like core-i686, core-x86_64, core-any, netinstall-i686, netinstall-x86_64 - all by just modifying the isomounts file and (not) putting the appropriate squashfs images to the disc, no other remastering necessary.
sounds good, but.... booting x86_64 kernel with i686 userspace, kernel modules are invalid, so maybe, should also add squashfs with only kernel modules, /lib/modules, whn booting x86_64 For overlay any, yes, but pacman.conf need to be parsed at startup, (current pacman does not support $arch in .conf). Since overlay is just 8KB, is not a space issue, can have for both archs with each pacman.conf. Another point, maybe can have a script that launch /sbin/init with linux32 wrapper, and using init=/the/script at kernel command line. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D