Re: Linux 2.2.18pre1
According to Bill Rugolsky Jr.: > On Fri, Sep 01, 2000 at 12:05:03PM +0100, Alan Cox wrote: > > Right now Im not happy with the nfsv3 stuff I last looked at and > > it seems to still contain things Linus rejected a while back. > > Alan, would you please describe in a few words what items are > problematic? Yes, please ... without specifics we can't improve the situation. -- Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]> "I wanted to play hopscotch with the impenetrable mystery of existence, but he stepped in a wormhole and had to go in early." // MST3K - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Hello Alan (& Others) , How about describing what it breaks ? I know that invoking the God Linus's name can just get people to back down . So I ask for myself as well as others ... what , where , when , why , who .Hth , JimL On Fri, 1 Sep 2000, Alan Cox wrote: > > > Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So > > > you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre > > > patch of choice. > > Well, I'm asking again, as usual, are you planning to integrate > > kernel-space NFSv3? I'd appreciate if you did. > People would appreciate lots of things but stability happens to come first. > Thats why its primarily focussed on driver stuff not on revamping the > internals. Right now Im not happy with the nfsv3 stuff I last looked at and > it seems to still contain things Linus rejected a while back. > I'd love to have raid 0.90, nfsv3 and the new ide stuff in but I cannot see > a path for that without breaking a supposedly stable product for other people > which is simply not acceptable. > Alan ++ | James W. Laferriere | System Techniques | Give me VMS | | NetworkEngineer | 25416 22nd So | Give me Linux | | [EMAIL PROTECTED] | DesMoines WA 98198 | only on AXP | ++ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Fri, Sep 01, 2000 at 12:05:03PM +0100, Alan Cox wrote: > People would appreciate lots of things but stability happens to come first. > Thats why its primarily focussed on driver stuff not on revamping the > internals. Right now Im not happy with the nfsv3 stuff I last looked at and > it seems to still contain things Linus rejected a while back. Alan, would you please describe in a few words what items are problematic? Are the changes simply too extensive for your comfort? Are there still areas of compatibility in userland that you want ironed out? If the problem is more specific than that, is it Trond's client code: SunRPC rewrite? caching? Credentials? This is not a *me too!* request that you put it in; those of us with environments heavily dependent on NFS have been patching for so long, it hardly matters any more, especially now that the patches have been consolidated by Trond and Dave Higgens, and 2.4 is shaping up. I'm just curious as to what the perceived problems are, since you inevitably see lots of reports of breakage that never find their way onto these lists. Lately I just point everybody who asks me about NFS breakage to H.J. Lu's rpms, and they go away happy. Regards, Bill Rugolsky [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
David Lang <[EMAIL PROTECTED]> said: > attention everyone, > > the assumption that people who use raid or nfs always use a patched kernel > is not true. > > in many cases it is not trivial to find the newest patches and tools to go > with them (documentation limitations) and in other cases the stock stuff > seems to work so people don't realize there is a reason to upgrade. What about being spammed with messages about not being able to use NFSv3 (happens here enough to be anoying, mostly Solaris NFS servers + selfcompiled (stock) kernels on RH)? And no clear way to get at said patches sure doesn't help to get them tested, fixed and up to Linus' standards. -- Dr. Horst H. von Brand mailto:[EMAIL PROTECTED] Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, ChileFax: +56 32 797513 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On 1 Sep 2000, Matthias Andree wrote: > Does including knfsd v3 break v2? Is not NFS v3 a compile-time option? I > would not object if it was tagged "EXPERIMENTAL". it is. asui the NFS patches are bugfixes/improvements on the existing stock V2 knfsd, and the feature add v3 is pretty much independent of v2 - and indeed marked experimental. (v3 works fine for me with IRIX 6.2, server/client in both directions). --paulj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Fri, 1 Sep 2000, Alan Cox wrote: > I'd love to have raid 0.90, nfsv3 and the new ide stuff in but I > cannot see a path for that without breaking a supposedly stable > product for other people which is simply not acceptable. > raid i can understand considering it's a 'no way back' thing. the NFS stuff is a definite improvement in reliability though. and the new tools /are/ backwards compatible. i'd like to see it go in > Alan > regards, --paulj [ps: though i join in the nfs moaning every 2.2pre cycle, i'm still glad to see that it's difficult to slip big patches past you.] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
attention everyone, the assumption that people who use raid or nfs always use a patched kernel is not true. in many cases it is not trivial to find the newest patches and tools to go with them (documentation limitations) and in other cases the stock stuff seems to work so people don't realize there is a reason to upgrade. David Lang On 1 Sep 2000 [EMAIL PROTECTED] wrote: > Date: 1 Sep 2000 12:21:58 GMT > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: Linux 2.2.18pre1 > > In article <[EMAIL PROTECTED]>, > Andi Kleen <[EMAIL PROTECTED]> wrote: > >The big problem with the raid patches is that there is no way back for your > >raid array, unless somebody adds a noconv modus to raidutils and support into > >the kernel to keep the old super block version. It also requires tools > >updates. > > Well at least the RAID0 format from 2.2.x is useable with RAID0.90. > I'm not sure about raid1/5, but people using those probably have > migrated to RAID0.90 anyway (?) > > The biggest problem I think is that the new RAID tools don't work with > older kernels. If they did you could keep your 2.2.x RAID0 array and > switch between 2.2.x raid and 0.90 raid without switching around > tools and rewriting /etc/mdtab to /etc/raidtab and back all the time. > > It would be even better if the raid 0.90 code had a compatibility > mode for the older raidtools.. > > Or has that been fixed already ? > > Mike. > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Alan Cox <[EMAIL PROTECTED]> writes: > People would appreciate lots of things but stability happens to come first. > Thats why its primarily focussed on driver stuff not on revamping the > internals. Right now Im not happy with the nfsv3 stuff I last looked at and > it seems to still contain things Linus rejected a while back. Does including knfsd v3 break v2? Is not NFS v3 a compile-time option? I would not object if it was tagged "EXPERIMENTAL". -- Matthias Andree Where do you think you're going today? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
[EMAIL PROTECTED] (Matthias Andree) writes: >Alan Cox <[EMAIL PROTECTED]> writes: >> Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So >> you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre >> patch of choice. >Well, I'm asking again, as usual, are you planning to integrate >kernel-space NFSv3? I'd appreciate if you did. I support this request. It was promised since 2.2.13 to finally get a working NFSv3 in the official kernel tree but it was always pushed back further by "more important things" like driver updates and VM changes... I know that it is futile but getting LFS and RAID 0.90 would be nice, too. Especially as 95+% of all Linux users (which use a distribution kernel) already _have_ 0.90 RAID and the last 5-% are able to patch the old driver theirselves. At least as a config option? CONFIG_NEW_RAID vs. CONFIG_OLD_RAID? Alan, if you accept such a patch, I would generate one vs. 2.2.18pre1 Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED] Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED] D-91054 Buckenhof Fax.: 09131 / 50654-20 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
> One day I hope you'll explain to us why this is not 2.2.17pre21... > Either you are sure pre20 is going to be the official 2.2.17, > or I'm missing something. The 2.2.18pre1 changes are higher risk problems to fix. 2.2.17pre20 is extremely solid. Its probably the most solid 2.2 kernel so far overall (Im sure it will break for someone though). The 2.2.18pre stuff is now starting again making higher risk changes that should be reliable but might produce suprises and need to be fixed/reverted before 2.2.18 final - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Fri, Sep 01, 2000 at 12:05:03PM +0100, Alan Cox wrote: > > > Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So > > > you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre > > > patch of choice. > > > > Well, I'm asking again, as usual, are you planning to integrate > > kernel-space NFSv3? I'd appreciate if you did. > > People would appreciate lots of things but stability happens to come first. > Thats why its primarily focussed on driver stuff not on revamping the > internals. Right now Im not happy with the nfsv3 stuff I last looked at and > it seems to still contain things Linus rejected a while back. > > I'd love to have raid 0.90, nfsv3 and the new ide stuff in but I cannot see > a path for that without breaking a supposedly stable product for other people > which is simply not acceptable. The big problem with the raid patches is that there is no way back for your raid array, unless somebody adds a noconv modus to raidutils and support into the kernel to keep the old super block version. It also requires tools updates. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Thu, 31 Aug 2000, Alan Cox wrote: > > Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So > you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre > patch of choice. One day I hope you'll explain to us why this is not 2.2.17pre21... Either you are sure pre20 is going to be the official 2.2.17, or I'm missing something. And now that I look closer, you used the work 'Fix' a lot in the changelog. It won't be a great idea to release 2.2.17 with many outstanding bugs (however little they are...). > 2.2.18pre1 (versus 2.2.17pre20) fgrep Fix 2.2.18-changes | wc -l 16 B-) .TM. -- / / / / / / Marco Colombo ___/ ___ / / Technical Manager / / / ESI s.r.l. _/ _/ _/ [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
> > Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So > > you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre > > patch of choice. > > Well, I'm asking again, as usual, are you planning to integrate > kernel-space NFSv3? I'd appreciate if you did. People would appreciate lots of things but stability happens to come first. Thats why its primarily focussed on driver stuff not on revamping the internals. Right now Im not happy with the nfsv3 stuff I last looked at and it seems to still contain things Linus rejected a while back. I'd love to have raid 0.90, nfsv3 and the new ide stuff in but I cannot see a path for that without breaking a supposedly stable product for other people which is simply not acceptable. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. Well, I'm asking again, as usual, are you planning to integrate kernel-space NFSv3? I'd appreciate if you did. People would appreciate lots of things but stability happens to come first. Thats why its primarily focussed on driver stuff not on revamping the internals. Right now Im not happy with the nfsv3 stuff I last looked at and it seems to still contain things Linus rejected a while back. I'd love to have raid 0.90, nfsv3 and the new ide stuff in but I cannot see a path for that without breaking a supposedly stable product for other people which is simply not acceptable. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Thu, 31 Aug 2000, Alan Cox wrote: Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. One day I hope you'll explain to us why this is not 2.2.17pre21... Either you are sure pre20 is going to be the official 2.2.17, or I'm missing something. And now that I look closer, you used the work 'Fix' a lot in the changelog. It won't be a great idea to release 2.2.17 with many outstanding bugs (however little they are...). 2.2.18pre1 (versus 2.2.17pre20) fgrep Fix 2.2.18-changes | wc -l 16 B-) .TM. -- / / / / / / Marco Colombo ___/ ___ / / Technical Manager / / / ESI s.r.l. _/ _/ _/ [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
One day I hope you'll explain to us why this is not 2.2.17pre21... Either you are sure pre20 is going to be the official 2.2.17, or I'm missing something. The 2.2.18pre1 changes are higher risk problems to fix. 2.2.17pre20 is extremely solid. Its probably the most solid 2.2 kernel so far overall (Im sure it will break for someone though). The 2.2.18pre stuff is now starting again making higher risk changes that should be reliable but might produce suprises and need to be fixed/reverted before 2.2.18 final - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
[EMAIL PROTECTED] (Matthias Andree) writes: Alan Cox [EMAIL PROTECTED] writes: Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. Well, I'm asking again, as usual, are you planning to integrate kernel-space NFSv3? I'd appreciate if you did. I support this request. It was promised since 2.2.13 to finally get a working NFSv3 in the official kernel tree but it was always pushed back further by "more important things" like driver updates and VM changes... I know that it is futile but getting LFS and RAID 0.90 would be nice, too. Especially as 95+% of all Linux users (which use a distribution kernel) already _have_ 0.90 RAID and the last 5-% are able to patch the old driver theirselves. At least as a config option? CONFIG_NEW_RAID vs. CONFIG_OLD_RAID? Alan, if you accept such a patch, I would generate one vs. 2.2.18pre1 Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED] Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED] D-91054 Buckenhof Fax.: 09131 / 50654-20 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Alan Cox [EMAIL PROTECTED] writes: People would appreciate lots of things but stability happens to come first. Thats why its primarily focussed on driver stuff not on revamping the internals. Right now Im not happy with the nfsv3 stuff I last looked at and it seems to still contain things Linus rejected a while back. Does including knfsd v3 break v2? Is not NFS v3 a compile-time option? I would not object if it was tagged "EXPERIMENTAL". -- Matthias Andree Where do you think you're going today? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Fri, Sep 01, 2000 at 12:05:03PM +0100, Alan Cox wrote: People would appreciate lots of things but stability happens to come first. Thats why its primarily focussed on driver stuff not on revamping the internals. Right now Im not happy with the nfsv3 stuff I last looked at and it seems to still contain things Linus rejected a while back. Alan, would you please describe in a few words what items are problematic? Are the changes simply too extensive for your comfort? Are there still areas of compatibility in userland that you want ironed out? If the problem is more specific than that, is it Trond's client code: SunRPC rewrite? caching? Credentials? This is not a *me too!* request that you put it in; those of us with environments heavily dependent on NFS have been patching for so long, it hardly matters any more, especially now that the patches have been consolidated by Trond and Dave Higgens, and 2.4 is shaping up. I'm just curious as to what the perceived problems are, since you inevitably see lots of reports of breakage that never find their way onto these lists. Lately I just point everybody who asks me about NFS breakage to H.J. Lu's rpms, and they go away happy. Regards, Bill Rugolsky [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Hello Alan ( Others) , How about describing what it breaks ? I know that invoking the God Linus's name can just get people to back down . So I ask for myself as well as others ... what , where , when , why , who .Hth , JimL On Fri, 1 Sep 2000, Alan Cox wrote: Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. Well, I'm asking again, as usual, are you planning to integrate kernel-space NFSv3? I'd appreciate if you did. People would appreciate lots of things but stability happens to come first. Thats why its primarily focussed on driver stuff not on revamping the internals. Right now Im not happy with the nfsv3 stuff I last looked at and it seems to still contain things Linus rejected a while back. I'd love to have raid 0.90, nfsv3 and the new ide stuff in but I cannot see a path for that without breaking a supposedly stable product for other people which is simply not acceptable. Alan ++ | James W. Laferriere | System Techniques | Give me VMS | | NetworkEngineer | 25416 22nd So | Give me Linux | | [EMAIL PROTECTED] | DesMoines WA 98198 | only on AXP | ++ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
According to Bill Rugolsky Jr.: On Fri, Sep 01, 2000 at 12:05:03PM +0100, Alan Cox wrote: Right now Im not happy with the nfsv3 stuff I last looked at and it seems to still contain things Linus rejected a while back. Alan, would you please describe in a few words what items are problematic? Yes, please ... without specifics we can't improve the situation. -- Chip Salzenberg - a.k.a. - [EMAIL PROTECTED] "I wanted to play hopscotch with the impenetrable mystery of existence, but he stepped in a wormhole and had to go in early." // MST3K - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Paul Jakma <[EMAIL PROTECTED]> writes: > will old tools work with kernel+nfs patches? i think the fear and > main argument against updating NFS in linux 2.2 is that people will > be forced to update their tools. You'd need a pretty recent util-linux package (mount in particular) to actually take use of it, an old 2.9f will not suffice. Check http://nfs.sourceforge.net/ -- Matthias Andree Where do you think you're going today? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Fri, 1 Sep 2000, Neil Brown wrote: > What incompatible tools??? > > Any nfs-utils that work with vanilla 2.2.16 will work just fine with > patched 2.2.16. They may not access any new functionality, but there > ARE NO INCOMPATIBILITIES (that I know of, and I am quute close to the > game). > i meant old tools. sorry. will old tools work with kernel+nfs patches? i think the fear and main argument against updating NFS in linux 2.2 is that people will be forced to update their tools. (however to that arg i say: anybody who uses NFS for any half serious purpose will already have patched up, or is using a dist kernel with patches). > Note that this is in contrast to the changes that went into 2.2.14, > which DID break compatability - all of a sudden you needed to run > lockd from user space, where as before you didn't. (with the patches > you don't any more, so they actaully improve compatability). > cool. another reason to include the patches. > NeilBrown > > -- Paul Jakma [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: I try to keep an open mind, but not so open that my brains fall out. -- Judge Harold T. Stone - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Friday September 1, [EMAIL PROTECTED] wrote: > > 2: incompatible tools: those who follow a dist are already using > incompatible tools anyway, and can either stay with their dist or get > the neccessary tools themselves (nfs-utils is available in RPM and > deb anyway!). those who follow the stock kernel can read the changes > file. What incompatible tools??? Any nfs-utils that work with vanilla 2.2.16 will work just fine with patched 2.2.16. They may not access any new functionality, but there ARE NO INCOMPATIBILITIES (that I know of, and I am quute close to the game). Note that this is in contrast to the changes that went into 2.2.14, which DID break compatability - all of a sudden you needed to run lockd from user space, where as before you didn't. (with the patches you don't any more, so they actaully improve compatability). NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On 1 Sep 2000, Matthias Andree wrote: > Alan Cox <[EMAIL PROTECTED]> writes: > Well, I'm asking again, as usual, are you planning to integrate > kernel-space NFSv3? I'd appreciate if you did. yes please. 0: The new NFS patches work so so much better than vanilla linux nfs. 1: due to (0) most dists have actually been distributing the patches and updated userland for a v. long time now! 2: incompatible tools: those who follow a dist are already using incompatible tools anyway, and can either stay with their dist or get the neccessary tools themselves (nfs-utils is available in RPM and deb anyway!). those who follow the stock kernel can read the changes file. please please lets sort out NFS in 2.2! (cause it's going to be around for a good while yet). Any pain it may cause in tool updates is completely mitigated by the stability, performance and interoperability benefits of the the patches. regards, -- Paul Jakma [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: "Are you sure you're not an encyclopedia salesman?" No, Ma'am. Just a burglar, come to ransack the flat." -- Monty Python - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Alan Cox <[EMAIL PROTECTED]> writes: > Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So > you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre > patch of choice. Well, I'm asking again, as usual, are you planning to integrate kernel-space NFSv3? I'd appreciate if you did. -- Matthias Andree Where do you think you're going today? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Thu, Aug 31, 2000 at 11:54:06PM +0100, Alan Cox wrote: > o Merge the microcode driver from 2.4 into 2.2(Tigran Aivazian) Just to let people know: This doesn't compile as it has devfs stuff left in it. Fix is in the works... Best regards, Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Linux 2.2.18pre1
Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. 2.2.18pre1 (versus 2.2.17pre20) o Update symbios/ncr driver to 1.7.0/3.4.0(Gerhard Roudier) o Updated ATP870U driver (ACard) o Avoid running tq_scheduler stuff sometimes with (Andrea Arcangeli) interrupts off o Futher cpu setup updates(me) o IBM MCA scsi driver updates (Michael Lang) o Fix incorrect out of memory handling in bttv(Dawson Engler) o Fix incorrect out of memory handling in buz (Dawson Engler) o Fix incorrect out of memory handling in qpmouse (Dawson Engler) o Fix error handling memory leak in ipddp (Dawson Engler) o Fix error handling memory leak in sdla (Dawson Engler) o Fix error handling memory leak in softoss (Dawson Engler) o Fix error handling memory leak in ixj (Dawson Engler) o Fix error handling memory leak in ax25 (Dawson Engler) o Merge the microcode driver from 2.4 into 2.2(Tigran Aivazian) o Fix skbuff handling bug in the smc9194 driver (Arnaldo Melo) o Fix problems with SIS900 driver on some 630E(Lei-Chun Chang) boards o Make vfat use the same generation rules as (H. Kawaguchi, in windows 9xChip Salzenberg) o Fix oops in the CPQ array driver(Arnaldo Melo) o Fix ac97 codec not setting the id field (Bill Nottingham) o Further work on the cs46xx/CD power bits(me) o Synclink updates(Paul Fulgham) o Synclink init bug fix (Arnaldo Melo) o Handle odd interrupts from toshiba floppies (Alain Knaff) o Fix trident driver build on nautilus Alpha (Peter Petrakis) o Add later sb16 imix support tot he sb driver(Massimo Dal Zotto) o Ignore luns that report can be connected, but (Matt Domsch) not currently o Fix dereference after kfree in uart401.c(Dawson Engler) o Return correct SuS error code for an unknown(Herbert Xu) socket family o Add sub window clipping to the bttv driver (Thomas Jacob) o Fix nfs cache locked messages (Trond Myklebust) o Fix the modutils misdocumentation (Martin Douda) o Remove bogus biosparm code from seagate.c (Andries Brouwer) o Return correct error code on failed fasync set (Chip Salzenberg) o Handle dcc resume with newer irc clients when (Scottie Shore) doing an irq masq - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Linux 2.2.18pre1
Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. 2.2.18pre1 (versus 2.2.17pre20) o Update symbios/ncr driver to 1.7.0/3.4.0(Gerhard Roudier) o Updated ATP870U driver (ACard) o Avoid running tq_scheduler stuff sometimes with (Andrea Arcangeli) interrupts off o Futher cpu setup updates(me) o IBM MCA scsi driver updates (Michael Lang) o Fix incorrect out of memory handling in bttv(Dawson Engler) o Fix incorrect out of memory handling in buz (Dawson Engler) o Fix incorrect out of memory handling in qpmouse (Dawson Engler) o Fix error handling memory leak in ipddp (Dawson Engler) o Fix error handling memory leak in sdla (Dawson Engler) o Fix error handling memory leak in softoss (Dawson Engler) o Fix error handling memory leak in ixj (Dawson Engler) o Fix error handling memory leak in ax25 (Dawson Engler) o Merge the microcode driver from 2.4 into 2.2(Tigran Aivazian) o Fix skbuff handling bug in the smc9194 driver (Arnaldo Melo) o Fix problems with SIS900 driver on some 630E(Lei-Chun Chang) boards o Make vfat use the same generation rules as (H. Kawaguchi, in windows 9xChip Salzenberg) o Fix oops in the CPQ array driver(Arnaldo Melo) o Fix ac97 codec not setting the id field (Bill Nottingham) o Further work on the cs46xx/CD power bits(me) o Synclink updates(Paul Fulgham) o Synclink init bug fix (Arnaldo Melo) o Handle odd interrupts from toshiba floppies (Alain Knaff) o Fix trident driver build on nautilus Alpha (Peter Petrakis) o Add later sb16 imix support tot he sb driver(Massimo Dal Zotto) o Ignore luns that report can be connected, but (Matt Domsch) not currently o Fix dereference after kfree in uart401.c(Dawson Engler) o Return correct SuS error code for an unknown(Herbert Xu) socket family o Add sub window clipping to the bttv driver (Thomas Jacob) o Fix nfs cache locked messages (Trond Myklebust) o Fix the modutils misdocumentation (Martin Douda) o Remove bogus biosparm code from seagate.c (Andries Brouwer) o Return correct error code on failed fasync set (Chip Salzenberg) o Handle dcc resume with newer irc clients when (Scottie Shore) doing an irq masq - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
Alan Cox [EMAIL PROTECTED] writes: Since 2.2.17 isnt out yet I've released 2.2.18pre1 versus 2.2.17pre20. So you need to grab 2.2.16 then apply the 2.2.17pre20 patch then the 2.2.18pre patch of choice. Well, I'm asking again, as usual, are you planning to integrate kernel-space NFSv3? I'd appreciate if you did. -- Matthias Andree Where do you think you're going today? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On 1 Sep 2000, Matthias Andree wrote: Alan Cox [EMAIL PROTECTED] writes: Well, I'm asking again, as usual, are you planning to integrate kernel-space NFSv3? I'd appreciate if you did. yes please. 0: The new NFS patches work so so much better than vanilla linux nfs. 1: due to (0) most dists have actually been distributing the patches and updated userland for a v. long time now! 2: incompatible tools: those who follow a dist are already using incompatible tools anyway, and can either stay with their dist or get the neccessary tools themselves (nfs-utils is available in RPM and deb anyway!). those who follow the stock kernel can read the changes file. please please lets sort out NFS in 2.2! (cause it's going to be around for a good while yet). Any pain it may cause in tool updates is completely mitigated by the stability, performance and interoperability benefits of the the patches. regards, -- Paul Jakma [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: "Are you sure you're not an encyclopedia salesman?" No, Ma'am. Just a burglar, come to ransack the flat." -- Monty Python - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Friday September 1, [EMAIL PROTECTED] wrote: 2: incompatible tools: those who follow a dist are already using incompatible tools anyway, and can either stay with their dist or get the neccessary tools themselves (nfs-utils is available in RPM and deb anyway!). those who follow the stock kernel can read the changes file. What incompatible tools??? Any nfs-utils that work with vanilla 2.2.16 will work just fine with patched 2.2.16. They may not access any new functionality, but there ARE NO INCOMPATIBILITIES (that I know of, and I am quute close to the game). Note that this is in contrast to the changes that went into 2.2.14, which DID break compatability - all of a sudden you needed to run lockd from user space, where as before you didn't. (with the patches you don't any more, so they actaully improve compatability). NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.2.18pre1
On Fri, 1 Sep 2000, Neil Brown wrote: What incompatible tools??? Any nfs-utils that work with vanilla 2.2.16 will work just fine with patched 2.2.16. They may not access any new functionality, but there ARE NO INCOMPATIBILITIES (that I know of, and I am quute close to the game). i meant old tools. sorry. will old tools work with kernel+nfs patches? i think the fear and main argument against updating NFS in linux 2.2 is that people will be forced to update their tools. (however to that arg i say: anybody who uses NFS for any half serious purpose will already have patched up, or is using a dist kernel with patches). Note that this is in contrast to the changes that went into 2.2.14, which DID break compatability - all of a sudden you needed to run lockd from user space, where as before you didn't. (with the patches you don't any more, so they actaully improve compatability). cool. another reason to include the patches. NeilBrown -- Paul Jakma [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: I try to keep an open mind, but not so open that my brains fall out. -- Judge Harold T. Stone - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
