Lonnie At 08:50 28/01/2008 -0600, Lonnie Abelbeck wrote: >With unionfs there are two methods. >--- >Method 1) The /mnt/kd/ path is a part of the unionfs "rw" overlay to the >base "ro" filesystem. Note: This method requires the "astkd=" NOT be >defined in the KCMD.
This is what I use, so I don't have to use three partitions (one for the RO AstLinux, one for the RW UnionFS, and one for the KD). I just had to create a second partition, reboot, format it as ext2fs, edit the .run.conf, reboot, and voilà! Writable /var/www :-) One thing, though: With UnionFS active, here's what my root filesystem and mount look like: http://pastebin.ca/883719 So I guess that UnionFS overlays the _whole_ filesystem, and the way to keep part of the filesystem in RAM is through /etc/fstab? This is especially important for /tmp since I might install some external apps (ie. not part of the AstLinux distro) which could trash /tmp since they don't know it's really a CF card underneath. Since in practise, I guess we really only need /etc/ and /var/www to be sticky, while keeping /tmp in RAM, and the rest read-only... is there no way to restrict UnionFS to only part of the filesystem? I don't mind editing /etc/fstab, but I wanted to make sure. Thanks. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
