> There's also a pretty strong argument that our primary target admin is > going to be managing multiple systems and using kickstart, scripts, thin > client, RHN, or other architectures to avoid configuring them > one-by-one. is it? let me give you a few common examples: 1. prof in the dept with a laptop 2. my dad both run linux. I am the 'admin' for both machines. However I do not have immediate access to ssh into the machine. So I have to be able to talk them through things. Have you ever talked someone through vim or emacs for editing a file in /etc? it's a nightmare. So I think there is definitely an argument for the home user to be editing their config files - even if those files are network configuration and adding a user. -sv
