Re: userspace breakage

Linus Torvalds wrote:

On Thu, 29 Dec 2005, Jeff V. Merkey wrote:


The breakage issue is ridiculous, assinine, and unnecessary. I have been
porting dsfs to the various releases over the past month, and the
breakage of user space, usb, nfs, memory management, is beyond absurd.



We're not talking about internal kernel stuff. Internal kernel stuff _does_ get changed, and we dont' care about breakage of out-of-kernel stuff. That's fundamental.



Start caring. People spend lots of money supporting you, and what you are doing. How about taking some
responsibility for that so they don't change their minds and move back to windows or pull their support because it's too
costly or too much of a hassle to produce something stable from these releases. If you export functions from the kernel,
don't break them. Don't let these numbnuts keep breaking things that shouldn't be broken, i.e. memory manager (now that's a
big one). If you replace a subsystem with a newer one, keep a mapping layer through at least the next .<even> release
i.e. 2.4 -> 2.6 (this is reasonable and expected -- you can drop things but you should only do it on well understood
boundries). Don't let these people break everything every other incremental release.

I have a family too Linus and I like to spend my evenings with them rather then unwinding Olaf's bugs in NFS (the most
recent one). Think about "free and easy" and about making peoples lives a little easier to support code on your platform
rather then expecting the rest of the planet to clean up everyone's messes and sloppiness.

Jeff





		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Relevant Pages

  • Re: NFS corruption (duplicated data)
    ... would be very helpful Andy. ... this is data corruption not dropped packets so the protocol ... > comparing the file on B with the file on A over NFS, ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • [FYI] "kernel BUG at fs/nfs/inode.c:152!"
    ... used dhclient to update the route. ... thus today i had some NFS problems... ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: XFS over 7.7TB LVM partition through NFS
    ... And, that stack looks awfully long if it's real, turning on the stack ... > over NFS. ... After exporting the filesystem clients start writing files to ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [PATCH] fix remap of shared read only mappings
    ... >> as the hardware just allows. ... NFS doesn't attempt to implement local Posix semantics, ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [PATCH 01/04] Adding cipher mode context information to crypto_tfm
    ... Laziness to do things right at memory ... > management shifts the burden to the users of the interface. ... Doing it "at memory management" is what many other OS's do and ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)