* Hubert Mantel [010512 15:07]:

Hi,

...

util-linux (util for 7.0 and older), too, using rpm -Uhv <packname>.

Ok I have downloaded the util for 7.1 in addition to k_deflt-2.2.19 here are the steps I did rpm -e k_deflt rpm -Uhv k_deflt-2.2.19 rpm -Uhv --nodeps --force util-linux (fails due to conflicts with -Uhv) mk_initrd lilo reboot /dev/hdb3 was not cleanly unmounted ( ????? unable to mount /dev/hdb3 manual fsck require e2fsck -y /dev/hdb3 CONTROL D Ok so far everything looks fine so it was not cosmetic to me unless I did it wrong

As said above, this is purely cosmetic; the mount will succeed and everything works ok. We decided to provide the update nevertheless as the kernel warning might scare some people.

-- Togan Muftuoglu

Hi, On Sat, May 12, Richard Ibbotson wrote:

...

rpm -e k_deflt rpm -Uhv k_deflt-2.2.19 rpm -Uhv --nodeps --force util-linux (fails due to conflicts with -Uhv) mk_initrd

Do I need to download all of these for an ordinary Intel based workstation ?

k_deflt-2.2.19-11.i386.rpm k_eide-2.2.19-0.i386.rpm k_i386-2.2.19-12.i386.rpm

No, you only need one of them depending on the kernel you're using. 99% of all people will use k_deflt-2.2.19-11.i386.rpm. k_eide only is needed for some special EIDE controllers k_i386 is only needed for really old machines (I assume you have at least a Pentium class computer, so just use the default kernel).

Richard -o) Hubert Mantel Goodbye, dots... /\\ _\_v

What type of machine is k_pentiu-2.2.19-0.i386.rpm meant for?

(I did not see this in the 6.3 tree before today. rpm -qip gives no clues.)

Pentium-optimized. Does not run on 486.

dproc

Roman.

...

Ok I have downloaded the util for 7.1 in addition to k_deflt-2.2.19

here are the steps I did

rpm -e k_deflt rpm -Uhv k_deflt-2.2.19 rpm -Uhv --nodeps --force util-linux (fails due to conflicts with -Uhv) mk_initrd lilo reboot /dev/hdb3 was not cleanly unmounted ( ????? unable to mount /dev/hdb3 manual fsck require e2fsck -y /dev/hdb3 CONTROL D

Ok so far everything looks fine so it was not cosmetic to me unless I did it wrong

This is something unrelated. You did update the util-package anyway, so you will not see the NFS mount complaints.

The real question is: Why was /dev/hdb3 not cleanly unmounted on shutdown?

Good morning! :-) The thing with the unclean shutdown can happen if init doesn't know the runlevel it is in. This is the case when init crashed (you don't see that), maybe after an upgrade of some library. It should not repeat, though. Roman. -- - - | Roman Drahtmüller "Caution: Cape does not | SuSE GmbH - Security enable user to fly." | Nürnberg, Germany (Batman Costume warning label) | - -

So if I bring the machine to init 1 for example do the upgrading and then issue another init 1 and then reboot will that solve the problem of e2fsck

Runlevel 1 is not necessary for a kernel upgrade, since the kernel files (and modules) are not actively used from the filesystem any more. It's more about the libc upgrade (shlibs package) if you have a 7.0. Two times init 1 in succession will render the second time useless (it's a no-op). Try to reboot your machine with shutdown -r now, or with init 6. If reboot can't determine the runlevel, it will issue the reboot(2) system call, instead of telling init to go to runlevel 6 (at the end of which there will be a reboot again). I experienced this behaviour a long while ago, and I guess this has changed in the meanwhile, but it is a possible explanation for the problem you see. That you had to repair manually indicates another problem. But I can't tell what's wrong with it. Just see if it repeats. Roman. -- - - | Roman Drahtmüller // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -

* Roman Drahtmueller wrote on Sat, May 12, 2001 at 15:37 +0200:

The thing with the unclean shutdown can happen if init doesn't know the runlevel it is in. This is the case when init crashed (you don't see that), maybe after an upgrade of some library. It should not repeat, though.

init is linked statically, isn't it? IIRC init case that init cannot determine the current runlevel, it displays such a message. oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.

...

The real question is: Why was /dev/hdb3 not cleanly unmounted on shutdown?

If I had only known the answer. As I have to upgrade the kernel for my firewall/router PC which is low on space (well actually the whole thing is 180 MB Hard disk ) so I have to initiate rpm -e for both packages before I can do rpm -Uhv for the new ones so I can have space I have to scp these rpms first unless someone can show me a way to install the rpms over ssh without actually copying the rpm to the firewall

Make a ramdisk that is big enough and copy it there. Mount the directory where the rpm is via NFS and install it from there. Convert the rpm to a cpio archive and pipe this archive directly into cpio, maybe using netcat or alike. I shouldn't give you this advice, actually, because a consistent system is worth something the next time. It's just that in this case it doesn't break that many things... Thanks, Roman. -- - - | Roman Drahtmüller // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -