config file under RCS

[Todd Troxell]

On Tue, Dec 20, 2005 at 12:00:05PM +0100, Sebastien Estienne wrote:
> 2005/12/20, Fabio Massimo Di Nitto <fabbione at ubuntu.com>:
> > Sebastien Estienne wrote:
> > >>>You didn't comment on the "PS1" and "logout" ideas, i think they are
> > >>>still valid with the crontab autocommit, it gives an immediate visual
> > >>>information.
> > >>
> > >>while the idea might be valid, it would require changes to all shells to check
> > >>for that specific plugin and status. it is a fragile point to touch that i am
> > >>not keep to modify.
> > >>
> > >
> > >
> > > I'm willing to implement this, i don't really see the need to
> > > implement it for all shells other than bash/tcsh/zsh.
> > >
> >
> > Nope.. that won't work. You can't assume what shell the admin is going to use.
> > either all or none.
> >
> 
> I just assumed that bash/tcsh/zsh covered 99% of the admins shell on a
> linux system (i even assumed that bash was 90%) and that the reamin
> 1-10% were clever enought to make it work with their shell of choice.
> I may be completely wrong, but i still think it's better to have it
> for bash only than not having it at all. And nothing can stop someone
> using Ash or any other shell to contribute to the project if he feels
> the need...

I agree, I think it's enough to get the effort started, perhaps with a
generic interface so that it would be easy to extend to other shells.  Too
many things _don't_ happen because we try to make them work with everything.

That said, I'm not completely convinced on the idea:
1. The logout message would be very annoying to seasoned admins.
	-If they want it, they could add the command to their logout script
2. Would obviously not affect changes made outside shell, which happen often,
for example, when making a change across many systems.

Cheers,
-- 
Todd Troxell
http://rapidpacket.com/~xtat