Messages in this thread | | | Date | Wed, 25 Feb 1998 13:31:53 -0800 (PST) | From | Shane Wegner <> | Subject | upgrading from linux 2.0 to 2.1 |
| |
-----BEGIN PGP SIGNED MESSAGE-----
Hello all,
I imagine you must get this alot so I'll try to be as brief as possible. A few months ago, I tried upgrading my kernel from the 2.0 set to 2.1.66. I did this primarily for the sound drivers and the serial console feature. About a day after upgrading, I encountered e2fs errors and it created files that were marked as block devices. These files could not be removed with rm or with the unlink system call. Rm gave "operation not permitted." I made all the software upgrades suggested at www.linuxhq.com and I thought the offending program might have been ld.so. However, I put the new ld.so with the 2.0 kernel up on an experemental system and it's been running fairly well for about a month now.
Does anyone have any idea as to what might have caused this and since 2.1.66, have there been any such fixes. In otherwords, is it now safe in that respect to go with the latest devel version? Thanks in advance for your assistance and I hope this isn't too offtopic.
Regards, Shane
-----BEGIN PGP SIGNATURE----- Version: 2.6.2
iQCVAwUBNPSNyaeq+0eJMsK9AQHHqgQA2U13wmpZ4jNrNBpSqKVkEy2Kv7M/as3G Nd1XFPDhLNJIeX0fRglosir6MdjACJB7BZ7MLvuE8HbfPJkyLbwnxej8XWM8U6NN QWBg7QLUB4B8ob+vDOpqzPrbbflNsFyQ9fSFfpInbJUUg9J++OhAWCFFGp8rcMVZ 4JB9RzuWM20= =BKus -----END PGP SIGNATURE-----
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |