Am 18.10.2010 00:48, schrieb Gerardo Exequiel Pozzi: >> We can try porting archiso to union-mounts soon and see how that works >> out. > Interesting. I never experimented with this, only read the documentation. > We need a patched util-linux-ng. (I guess the patch for e2fsprogs is not > needed because writable branch will be tmpfs in our case).
One reason not to do it until it is accepted upstream. >>> another workaround can be in Makefile >>> >>> - mkarchiso -p base create $(WORKDIR) >>> + mkarchiso -p $(shell pacman -Sgq base | grep -v ^kernel26$) create >>> $(WORKDIR) >> If we do not insist on using the base group, why not? > Sorry, I did not understand this. Could you put it another way? > > Are you saying that do not "force" in install all the base packages, > only a selection? There shouldn't be a difference, it's just more code to do this instead of installing base. >> Then the easiest thing to do is move all files to archlinux/ (including >> isomounts) and set archisobasedir=archlinux/. >> > So the medium, by default created by archiso will look like: > > / > /boot/ > /archlinux/ isomounts *.sqfs > > and by archiso2dual: > > / > /boot/ > /archlinux/ isomounts* > /archlinux/any/ *.sqfs > /archlinux/i686/ *.sqfs > /archlinux/x86_64/ *.sqfs No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
signature.asc
Description: OpenPGP digital signature
