Re: unremovable files and possible fs corruption (2.1.123)

Brandon S. Allbery KF8NH (allbery@kf8nh.apk.net)
Sun, 01 Nov 1998 12:31:29 -0500

In message <Pine.LNX.3.93.981101115722.597A-100000@kjahds.kjahds.com>,
Kenneth
Albanowski writes:
+-----
| > Today I can write code that avoids libc altogether and continues to
| > work, but if libc becomes the published interface, that guarantee is
| > gone.
|
| Also, in my interpreter-evangelist hat, I'd like to be able to bind
| anything to anything else, at any level, which at some point means
| teaching an interpreter to talk directly to the kernel, without libc in
| the middle. This ought to be possible.
+--->8

But that makes changes to the kernel interface difficult or impossible. It
requires the kind of ugliness that you find in NetBIOS, or a special syscall
that every program must make to declare which variant of system interface
they want to use, or requires the syscall interface to expand without limit
to accommodate changed syscalls. (And then we get screams from the folks
who bind directly to the kernel because they can't access the new
functionality without rewriting their programs.)

-- 
brandon s. allbery	[os/2][linux][solaris][japh]	 allbery@kf8nh.apk.net
system administrator	     [WAY too many hats]	   allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering			 KF8NH
			  Kiss my bits, Billy-boy.






-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/