On 2/16/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > > The current UnionFS snapshot doesn't allow one to use dynamic branches > > (we were using UnionFS 1.x, which is now freezed; the new development > > is going into 2.x, which doesn't have all features commited yet). So, > > in other words, you'll probably need to compile a new kernel with an > > updated squashfs patch, keeping the old UnionFS patches.. :-( > > So, do I understand it correctly that unionctl --add is the problem? > Then can't I just change the startGoboLinux script to mount all > squashfs's in one go? > mount -t unionfs -o dirs=/Mount/SquashFS/Foo=ro:/Mount/SquashFS/Bar=ro:...
Yes, you can. If it works fine for you it might be interesting to commit that in the cvs also. You can use the loop to create a variable with the dirs= contents, and then outside the loop just call 'mount -t unionfs -o dirs=$dirsarray ...'. There are some lines commented out in startGoboLinux that can be used as reference. IIRC, I commented them out and decided for a unionctl implementation because the former didn't allow gobohide to work fine on the LiveCD. If you don't care about that, just uncomment them (and remove the unionctl lines); I think that should be enough. > If I'm going to recompile the kernel, is the new unionfs patches > included in the recipe so I can revert them and replace them with the > unionfs patches from some old gobokernel tarball? If you skip all unionctl calls, you can probably keep using the same kernel, with Unionfs 2.x. The last release for 1.x (which includes dynamic branches) is for 2.6.18, available here: ftp://ftp.fsl.cs.sunysb.edu/pub/unionfs/unionfs-1.x/unionfs-1.4.tar.gz I hope the minor modifications in startGoboLinux are enough so that you don't need to waste too much time with kernel issues. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
