On Thu, Oct 29, 2009 at 12:47:11AM -0400, John Mahoney wrote: > On Wed, Oct 28, 2009 at 3:33 PM, Dan Williams <[1][email protected]> wrote: > > On Wed, 2009-10-28 at 20:02 +0100, Witold Sowa wrote: > > Dan Williams pisze: > > > 2) I guess we should leave the config file bits alone and do > > > an /etc/NetworkManager.state file instead? > > > > It's probably quite a distribution specific issue, but shouldn't we > > store the state in /var instead of /etc ? > > Yes, was checking into that. �/var/lib apparently *must* persist across > reboot, so I believe we should do: > > What standard is that based on?� I am not disargeeing it is just that I > have never heard this stated before.� I happen to work in an environment > that tries to minimize writes and we map all of /var to a tmpfs.� I am not > saying this is the norm but was courious what the source was you were > basing this on.
Thats a bogus setup ... /var on tmpfs is wrong ... /var/cache/ and /var/log on tmpfs is ok ... /var/tmp/ i was told is also technically wrong to be a tmpfs, but probably won't break systems. - Alexander _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
