On Sep 23, 2008, at 1:04 PM, David Kerr wrote: > Running with a unionfs setup... is there a way to get rid of the > notion of a key disk... why do I need a /mnt/kd in the first place? > (I understand why it was needed histrorically, but it doesn seems > necessary now on CF/unionfs setups) It just adds confusion > particularly to directory hierarchy. It also unnecessarily holds > configuration files that are unchanged from defaults. > > Thoughts? > David
Personally, I think the keydisk directory ( /mnt/kd/ ) is a great feature of astLinux. It evolved out of necessity in the early-years, but today is offers a single place (well almost) where all the user's configs are located. In addition, I don't use unionfs for my /mnt/kd/ directory, but rather a separate partition. I feel this is the most robust configuration, but maybe that is just me. :-) The keydisk idea clutters the development side a little, but it is there, and it works, and un-cluttering runs a high risk of bugs. Hopefully the user benefits from a single backup/restore directory out- weighs the development issues. Possibly a little more work is required to make sure all the useful files can be saved in the /mnt/ kd/ path. While unionfs has been a huge benefit to astLinux, it can be quite confusing. Knowing whether a non-/mnt/kd/ file will be mapped to flash or memory is not always obvious. Lonnie ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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]
