On Jan 26, 2008, at 10:24 AM, Fred wrote: > Hello > > I just added asturw=/dev/hda2 to the .run.conf file, and I can > successfully > write to files. > > One thing though: This means that if copy an application that wasn't > massaged at compile-time to either never write or perform unfrequent > writes... this application now has access to the whole CF card, and > can > then trash it with too many write-cycles. > > If I'm correct... is there a way to tell UnionFS to only make some > parts of > the filesystem writable, and leave the rest read-only?
Fred, Well, the unionfs "rw" overlay to the "ro" base mount is CF based, but most any files that are written-to on a constant basis are mounted as "tmpfs" which is a RAM based filesystem. With unionfs, a person *could* write to /etc/foo 100's of times a second, which would have failed without unionfs, but knowing this would not happen on a normal astlinux setup should be comforting. When in doubt, take a look at /oldroot/mnt/asturw/ these are the files that are in the "rw" unionfs overlay... (ignoring the lib/modules directory which gets removed every startup) determine that the files there are either unique additions or files that supersede the read-only base mount as you would expect. Lonnie ------------------------------------------------------------------------- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
