One would _hope_ that an update/upgrade would be kind enough
to not mungle with rc.local -- but that turned out not to be
the case, at least with RH versions though 6.0 ...
Those antecedent versions to RH 6.1 recognized that rc.local
was a 'config' file:
$ rpm -V initscripts
S.5....T c /etc/rc.d/rc.local
... notice the "c". But they would save custom configuration,
and displace the changed file with the 'latest.'
With 6.1, and the new '.rpmnew' construct being adopted, RH no
longer displaces changes to _this_ file. This is progress --
but I like the idea of isolating _all_ non-truly local
content, _including_ the generation of the 'issue' file OUT of
rc.local ... perhaps not an infinite improvement, but an
improvement, nonetheless.
-- Russ
On Mon, 1 Nov 1999, Bill Nottingham wrote:
> H. Peter Anvin ([EMAIL PROTECTED]) said:
> > Changes which can't be trivially automated are majorly evil. That's
> > what the /etc/rc.d/init.d stuff is there for; an
> > /etc/rc.d/init.d/makeissue would have been infinitely better.
>
> It shouldn't need to be 'automated' as such; replacing the rc.local
> file once should be enough - it won't get changed on upgrades.
end
==================================
.-- -... ---.. ... -.- -.--
Copyright (C) 1999 R P Herrold
[EMAIL PROTECTED] NIC: RPH5 (US)
My words are not deathless prose,
but they are mine.
Owl River Company 614 - 221 - 0695
"The World is Open to Linux (tm)"
... Open Source LINUX solutions ...
[EMAIL PROTECTED]
Columbus, OH
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
