This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: How to update initscripts ? ;)
From: Thomas Dodd <ted@cypress.com>
Date: Thu, 27 Jul 2000 09:59:41 -0500
Franz Sirl wrote:
>
> At 13:23 27.07.00, Bernhard Rosenkraenzer wrote:
> >On Thu, 27 Jul 2000, Piotr Majka wrote:
> >
> > > [root@link SPECS]# rpm -Uhv
> > > ../RPMS/i686/{chkconfig-1.2.7-1.i686.rpm,initscripts-5.35-1.i686.rpm}
> > > file /etc/rc.d/init.d conflicts between attemped installs of
> > > initscripts-5.35-1 and chkconfig-1.2.7-1
> > > file /etc/rc0.d conflicts between attemped installs of initscripts-5.35-1
> > > and chkconfig-1.2.7-1
I had no problems installing chkconfig-1.2.1-1 and initscripts-5.27-1
from rawhide using rpm-3.0.5-0.5 to rebuild the srpms.
Bernhard, what's changed to cause this bug?
> But be extremely careful here, VERIFY that you still have a
> /etc/rc.d/init.d/functions after the upgrade before the next reboot. I
> managed to severely shoot myself into the foot on upgrading
> chkconfig/initscripts from the last rawhide to the current one. My system
> was unbootable until I added init=/bin/sh to the kernel command line and
> recreated /etc/rc.d/init.d/functions with rpm2cpio. rpm won't install it if
> it's already in the database, since it's marked as missingok in the
> initscripts spec, which is a questionable decision IMHO.
Just use the --replacepkg option :)
Also the structure of the init dirs has
changed. look at /etc/rc.d/
it's a symlink to /etc/
so you now have /etc/init.d/
/etc/rc3.d/ and the scripts are
/etc/rc, /etc/rc.local, and /etc/rc.sysinit
like Sun does with Solaris.
The /erc/rc.d symlink is just for compatability.
Now if HP will move them from /sbin to /etc
all the system I use will have the init
scripts in the same place :)
===
Subject: Re: How to update initscripts ? ;)
From: Franz Sirl <Franz.Sirl@munich.netsurf.de>
Date: Thu, 27 Jul 2000 17:21:33 +0200
At 16:59 27.07.00, you wrote:
>Franz Sirl wrote:
> >
> > At 13:23 27.07.00, Bernhard Rosenkraenzer wrote:
> > >On Thu, 27 Jul 2000, Piotr Majka wrote:
> > >
> > > > [root@link SPECS]# rpm -Uhv
> > > > ../RPMS/i686/{chkconfig-1.2.7-1.i686.rpm,initscripts-5.35-1.i686.rpm}
> > > > file /etc/rc.d/init.d conflicts between attemped installs of
> > > > initscripts-5.35-1 and chkconfig-1.2.7-1
> > > > file /etc/rc0.d conflicts between attemped installs of
> initscripts-5.35-1
> > > > and chkconfig-1.2.7-1
>
>I had no problems installing chkconfig-1.2.1-1 and initscripts-5.27-1
>from rawhide using rpm-3.0.5-0.5 to rebuild the srpms.
>
>Bernhard, what's changed to cause this bug?
upgrading to 5.27 was easy, going from 5.27 to 5.35 is the difficult one.
> > But be extremely careful here, VERIFY that you still have a
> > /etc/rc.d/init.d/functions after the upgrade before the next reboot. I
> > managed to severely shoot myself into the foot on upgrading
> > chkconfig/initscripts from the last rawhide to the current one. My system
> > was unbootable until I added init=/bin/sh to the kernel command line and
> > recreated /etc/rc.d/init.d/functions with rpm2cpio. rpm won't install it if
> > it's already in the database, since it's marked as missingok in the
> > initscripts spec, which is a questionable decision IMHO.
>
>Just use the --replacepkg option :)
Nope, I used --force, didn't help. Checking the docs again... Argh, there
is a --allfiles option, it seems that's nearly the option I was looking
for, I wonder why I didn't see it last time... I would prefer a slightly
less drastic option doing a "install all missing missingok files"
>Also the structure of the init dirs has
>changed. look at /etc/rc.d/
>it's a symlink to /etc/
>so you now have /etc/init.d/
>/etc/rc3.d/ and the scripts are
>/etc/rc, /etc/rc.local, and /etc/rc.sysinit
>like Sun does with Solaris.
>
>The /erc/rc.d symlink is just for compatability.
The problem with the upgrade is that the symlink setup changed again, and
rpm is not very good in handling that, so a simple -Uvh of
chkconfig/initscripts wiped all files in /etc/rc.d/init.d belonging to
initscripts and not even repeated --force installs would recreate
/etc/rc.d/init.d/functions. Since I overlooked the --allfiles option, I
ended up using rpm2cpio|cpio to get at the files.
Franz.
===
Subject: Re: How to update initscripts ? ;)
From: Bill Nottingham <notting@redhat.com>
Date: Thu, 27 Jul 2000 11:22:27 -0400
Thomas Dodd (ted@cypress.com) said:
> I had no problems installing chkconfig-1.2.1-1 and initscripts-5.27-1
> from rawhide using rpm-3.0.5-0.5 to rebuild the srpms.
>
> Bernhard, what's changed to cause this bug?
It's not a bug. He's trying to install over 1.2.1/5.27, as we've
moved back to the previous directory structure. This can't be
done without manual intervention, for the same reason that
you really can't move to the structure in 1.2.1/5.27 without
manual intervention.
You must do:
cd /etc
rm rc.d
mkdir rc.d
for foo in init.d rc rc.local rc.sysinit ; do
mv $foo rc.d
ln -s rc.d/$foo $foo
done
for foo in 0 1 2 3 4 5 6 ; do
mv rc$foo.d rc.d
ln -s rc.d/rc$foo.d rc$foo.d
done
Bill
Bill
===
Subject: Re: How to update initscripts ? ;)
From: Thomas Dodd <ted@cypress.com>
Date: Thu, 27 Jul 2000 10:32:04 -0500
Bill Nottingham wrote:
>
> Thomas Dodd (ted@cypress.com) said:
> > I had no problems installing chkconfig-1.2.1-1 and initscripts-5.27-1
> > from rawhide using rpm-3.0.5-0.5 to rebuild the srpms.
> >
> > Bernhard, what's changed to cause this bug?
>
> It's not a bug. He's trying to install over 1.2.1/5.27, as we've
> moved back to the previous directory structure. This can't be
> done without manual intervention, for the same reason that
> you really can't move to the structure in 1.2.1/5.27 without
> manual intervention.
Ughhhh!!!!
Why move back. What does it add?
The rc.d symlink give backward compatability
and moving them up a level matches what other Unix
vendors are doing.
When I told my sysadmin about the chang I saw in rawhide
he was elated. Now It's going back the other way.
(He also want's Sun to add restart to their
initscripts)
Please explain.
-Thomas
_______________________________________________
Redhat-devel-list mailing list
Redhat-devel-list@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Subject: Re: How to update initscripts ? ;)
From: Thomas Dodd <ted@cypress.com>
Date: Thu, 27 Jul 2000 10:32:04 -0500
Bill Nottingham wrote:
>
> Thomas Dodd (ted@cypress.com) said:
> > I had no problems installing chkconfig-1.2.1-1 and initscripts-5.27-1
> > from rawhide using rpm-3.0.5-0.5 to rebuild the srpms.
> >
> > Bernhard, what's changed to cause this bug?
>
> It's not a bug. He's trying to install over 1.2.1/5.27, as we've
> moved back to the previous directory structure. This can't be
> done without manual intervention, for the same reason that
> you really can't move to the structure in 1.2.1/5.27 without
> manual intervention.
Ughhhh!!!!
Why move back. What does it add?
The rc.d symlink give backward compatability
and moving them up a level matches what other Unix
vendors are doing.
When I told my sysadmin about the chang I saw in rawhide
he was elated. Now It's going back the other way.
(He also want's Sun to add restart to their
initscripts)
Please explain.
===
Subject: Re: How to update initscripts ? ;)
From: Bill Nottingham <notting@redhat.com>
Date: Thu, 27 Jul 2000 11:44:48 -0400
Thomas Dodd (ted@cypress.com) said:
> Ughhhh!!!!
> Why move back. What does it add?
Because you really can't move forward and have it work in
the current rpm transaction framework. It managed to work
if you only upgraded initscripts out-of-band (i.e., without
installing anything else in the same transaction.)
===
Subject: Re: How to update initscripts ? ;)
From: kmb <kmb@eticomm.net>
Date: Thu, 27 Jul 2000 11:09:34 -0400
Franz Sirl wrote:
>
> At 13:23 27.07.00, Bernhard Rosenkraenzer wrote:
> >On Thu, 27 Jul 2000, Piotr Majka wrote:
> >
> > > [root@link SPECS]# rpm -Uhv
> > > ../RPMS/i686/{chkconfig-1.2.7-1.i686.rpm,initscripts-5.35-1.i686.rpm}
> > > file /etc/rc.d/init.d conflicts between attemped installs of
> > > initscripts-5.35-1 and chkconfig-1.2.7-1
> > > file /etc/rc0.d conflicts between attemped installs of initscripts-5.35-1
> > > and chkconfig-1.2.7-1
> >
> >The error message is a bug in rpm; the actual problem is that directories
> >have to be replaced with symlinks.
> >Do something like this:
> >
> >cd /etc
> >mkdir initstuff
> >mv init.d rc?.d initstuff
> >rpm -Uvh initscripts* chkconfig*
> >rm -rf rc.d/*
> >mv initstuff/* rc.d
>
> But be extremely careful here, VERIFY that you still have a
> /etc/rc.d/init.d/functions after the upgrade before the next reboot. I
> managed to severely shoot myself into the foot on upgrading
> chkconfig/initscripts from the last rawhide to the current one. My system
> was unbootable until I added init=/bin/sh to the kernel command line and
> recreated /etc/rc.d/init.d/functions with rpm2cpio. rpm won't install it if
> it's already in the database, since it's marked as missingok in the
> initscripts spec, which is a questionable decision IMHO.
>
> Franz.
>
> _______________________________________________
> Redhat-devel-list mailing list
> Redhat-devel-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/redhat-devel-list
I had the same problem and my Xserver died after I did rpm -e
initscripts. The way I arrived at this problem is because
rhs-printfilters and printool both needed LPRng which I never needed and
I never figured out how to get working. I lost everything on my
harddrives after that running rh-6.1 installer since I never figured out
how to burn a rawhide installer cd for each build.
===
Subject: Re: How to update initscripts ? ;)
From: Bernhard Rosenkraenzer <bero@redhat.de>
Date: Thu, 27 Jul 2000 17:57:59 +0200 (CEST)
On Thu, 27 Jul 2000, Thomas Dodd wrote:
> Ughhhh!!!!
> Why move back. What does it add?
> The rc.d symlink give backward compatability
> and moving them up a level matches what other Unix
> vendors are doing.
>
> When I told my sysadmin about the chang I saw in rawhide
> he was elated. Now It's going back the other way.
This is not saying it'll stay that way forever. (It WILL stay that way for
7.0.)
There have been a couple of problems with the initial move. Among other
things, rpm needed some really ugly kludges to be able to handle replacing
a directory with a symlink (quite a bad idea in many other
situations) and some people who do not work with other unixes complained
about the "mess" in /etc caused by the move.
We have /etc/init.d symlinks so if you do what you do in other unixes,
it'll work. (We've just reversed the situation).
LLaP
bero
===
Subject: Re: How to update initscripts ? ;)
From: Thomas Dodd <ted@cypress.com>
Date: Thu, 27 Jul 2000 11:27:44 -0500
Bernhard Rosenkraenzer wrote:
>
> On Thu, 27 Jul 2000, Thomas Dodd wrote:
>
> This is not saying it'll stay that way forever. (It WILL stay that way for
> 7.0.)
I've had my own symlinks for a while, it just was nice to
see that moving to the default. Now it's back to the symlinks.
> There have been a couple of problems with the initial move. Among other
> things, rpm needed some really ugly kludges to be able to handle replacing
> a directory with a symlink (quite a bad idea in many other
> situations) and some people who do not work with other unixes complained
> about the "mess" in /etc caused by the move.
I guess they would love HP-UX 9.x
executables like mount ands shutdown hiding in
/etc along with the config files.
> We have /etc/init.d symlinks so if you do what you do in other unixes,
> it'll work. (We've just reversed the situation).
So /etc/init.d is a symlink to /etc/rc.d/init.d
in the new initscripts?
The wonders of Unix. It'd be nice if Sun, HP, SGI, IBM,
and the linux guys could get together and pick a common
way to configure the system. Don't guess it'll happen
any time soon, but it should.
I really don't care whre the stuff is, just put it in the
same place on all the systems. Or make it so I can.
I tried moving the HPUX stuff in /sbin to /etc
like Red Hat and Solaris. Spent 3 days tracking
down problems and had to give up because it still
didn't work right.
===