init.d script removal

[Wuss912]

Well instead or removing everything how about backing up the conf files?


-----Original Message-----
From: lunar-bounces at lunar-linux.org [mailto:lunar-bounces at lunar-linux.org]
On Behalf Of Richard Pyne
Sent: Wednesday, July 30, 2003 4:27 PM
To: lunar at lunar-linux.org
Subject: Re: init.d script removal


For my 2 cents worth, lrm should remove EVERYTHING installed by the 
lin.

Is it not one of the goals of lunar to make a system as clean as 
possible. This goal is not met unless lrm properly cleans up after 
itself.

--Richard

On Wednesday 30 July 2003 05:02 pm, nestu wrote:
> Hello ladies and gentlemen ;)
> I've been asking a question on irc, that I'd like to
> put on the list: why doesn't lrm remove init'd scripts.
> I don't know if to call it a bug or not, but with the
> naming convention of calling the script by it use and
> not by the module's name it all mucks up. For example: I prepare a DNS 
> server module, that has an init.d script called named. Say the user 
> lrm's the module and installs bind. It would b0rk the whole thing up, 
> wouldn't it? So policy could be: remove init.d scripts in POST_REMOVE,
> or just leave it there. What do you think? I've choosed
> the first option for now. Mmmmm, maybe in CONFIGURE a:
>
> if [ -e /etc/init.d/$MySript]; then
> 	query "Do you want to update $MyScript" y
>
> and so on... ????
> Thanks for listening,
> C U,
> nestu ;))))

-- 
Richard B. Pyne
rpyne at kinfolk.org _______________________________________________
Lunar mailing list
Lunar at lunar-linux.org http://lunar-linux.org/mailman/listinfo/lunar