Installation of Fedora over SuSE

[William Park]

On Mon, Mar 07, 2005 at 01:32:28PM -0500, Lennart Sorensen wrote:
> On Mon, Mar 07, 2005 at 01:17:35PM -0500, William Park wrote:
> > Consider this situation.  Package XXX installs /etc/rc.d/rc.xxx script.
> > You modified it, so that it calls other scripts that you wrote, like
> >     [ -x /etc/rc.d/rc.xxx-1 ] && . /etc/rc.d/rc.xxx-1
> >     [ -x /etc/rc.d/rc.xxx-2 ] && . /etc/rc.d/rc.xxx-2
> >     [ -x /etc/rc.d/rc.xxx-3 ] && . /etc/rc.d/rc.xxx-3
> > 
> > So, with standard "install+restore" method, you need to backup 4 files
> >     /etc/rc.d/rc.xxx	-- original + your editing
> >     /etc/rc.d/rc.xxx-1	-- your script
> >     /etc/rc.d/rc.xxx-2	-- your script
> >     /etc/rc.d/rc.xxx-3	-- your script
> > as part of your normal incremental backup.  Then, after install, just
> > copy them back.
> > 
> > How will .deb/.rpm handle this situation, when upgrading in "in-place"?
> 
> Files in /etc are conf files, and are not overwriten on upgrades.
> Either (it will ask you) it will install the new one and rename the old
> one to .dpkg_old, or it will leave the old one and install the new one
> as .dpkg_new (that is the default).

Slackware does that too.  So, we may be splitting a proverbial hair, here.
But, what I want to stress (now that I've got my helmet on) is that
"install+restore" will work for any distro.

> It even lets you view a diff to decide if the changes make sense or
> not before deciding.  You then go fix it manually if any of the new
> things are things you need, or to add your own changes to the new
> file.
> 
> And of course Debian doesn't have a /etc/rc.d dir either, as that
> isn't part of the FHS standard.

-- 
William Park <opengeometry-FFYn/CNdgSA at public.gmane.org>, Toronto, Canada
Slackware Linux -- because it works.
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml