I just tried a catalyst build using the current ~ baselayout (1.11.6-r1) and encountered two problems. (1) the new way of handling the passwd/shadow/fstab/group files doesn't play well with how catalyst handles the stage2 -> stage3 transition (i.e. no use build or bootstrap, but still CONFIG_PROTECT=-*). What happens is that when the stage3 upgrades the baselayout, the files are not copied from /usr/share/baselayout to /etc (since they already exist). And then when the old baselayout is unmerged, the files are completely removed. vapier wrote a quick patch that solved the issue, see next message. (2) this is a cosmetic problem : when the catalyst-built livecd boots, you get the following error : Activating (possibly) more swap... swapon: cannot stat /dev/SWAP: No such file or directory [!!] The old baselayout used (in /etc/init.d/localmount): ebegin "Activating (possibly) more swap" /sbin/swapon -a &>/dev/null eend 0 While the new one uses : ebegin "Activating (possibly) more swap" /sbin/swapon -a eend $? Reverting to the old-style is maybe not desirable, but adding the "-e" option to swapon to silently ignore non-existing devices might be a good idea. That line doesn't make the livecd boot look very good :) If you won't fix this, please let me know : it can still be fixed at livecd level by forcing a /etc/fstab with no swap line.
Created attachment 45137 [details, diff] Patch to baselayout ebuild Patch by vapier to correctly support stage2 -> stage3 catalyst
i'd prefer to not add the -e line because it has the potential of being a useful debugging message on actual user installations fixed the fstab/passwd/etc... in cvs
