search for: ncfreenet

I've not been happy with the stories about the "stable" 2.4.x kernels. Everywhere I read people saying "not for production use". Would you recommend adding ext3 to 2.2.19 (ext3-0.0.7a) or moving to 2.4.1x and using ext3 there (ext3-0.9.12)? -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen@ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/

I'm trying to pick a kernel for ext3. Looking at the web page (http://www.zip.com.au/~akpm/linux/ext3/), I see little that clues me in to the fact that "most" of ext3 is already in (some|most|all) of the 2.4 series kernels. Am I correct that most of the patches listed on the web page now are actually bug fixes to the existing ext3 code, as opposed to previous patches that actually

rsync-2.4.6-2mdk I ran an rsync into a file system that filled up. I got no error message out of rsync - it just stopped and exited sliently. I stuck an fprintf into the receiving code and verified that the proper error was being generated - it just never gets printed by the rsync sending process. I submitted a bug report about it; but, I can't believe that other people haven't had

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

I'm getting only partial iso8859-1 translation from an smbfs mount from my Win98SE machine. The smbfs mounted file system shows most lower-case accented characters fine; but, it substitutes underscores for most of the upper-case accented characters (and a few lower-case ones too): # uname -a Linux elm 2.4.18-8.1mdkian3 #7 Sat Aug 17 15:19:44 EDT 2002 i686 unknown (Mandrake 8.2 Linux with all