Re: 2.4.0 umount problem

(no name) ((no email))
Thu, 11 Jan 2001 05:22:10 -0200

Just FYI, when 2.2.0 was released (yes, 2.2), I moved from
2.0.36 to it on a RedHat 5.1 with all the updates and the rest
built from scratch. And shutting down the system gave me the
same results: / -> device or resource busy. No need to say
that fsck was used. The other partitions were cleanly
unmounted.

2.2.1 was released after some days. Rebooting with this Kernel
would do the same. Then (I was too lazy to try fuser or lsof) I
started doing init 1 and umount / for half a year, then it
worked again (I don't know what changed, but I never edited the
RedHat scripts).

BTW, what's the problem with devfs? I plan to use it, but now
am afraid.

-- 
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/