On 6/02/09 11:25 AM, Erik Nordmark wrote:
..
What *would* be really useful is a way of saying "hey, this is just perfect, now
save the current configuration".
I think that is how routers and switches work (but I could be off on
that one). Basically all the config changes would be made to the running
configuration, and then at some point the admin can decide to update the
persistent configuration to be the same as the running one.
That is intuitive for single-purpose systems with a single admin. But
does it fall apart when there are separate admins for separate
subsystems? For instance one is handling ZFS and another the network
configuration.
Or even multiple administrators working on different problems
in the same "subsystem"... in which case you're transcending
this and really getting into the problem of "how to do system
admin", where solutions can vary... one example being whoever
owns the RCS lock on the work-history file is the one with
the system-admin mutex.
...
The weak model (aka symlinks) might have some warnings when creating
dependencies on an object which does not (yet) exist, and when an object
with depedants are removed, but would otherwise deal with dangling
references to objects.
Sounds like a winner to me.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
