Re: unremovable files and possible fs corruption (2.1.123)

david parsons (o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s)
31 Oct 1998 19:43:41 -0800

In article <linux.kernel.199810310122.UAA00331@hilfy.ece.cmu.edu>,
Brandon S. Allbery KF8NH <allbery@kf8nh.apk.net> wrote:
>In message <71dep8$ari@pell.pell.portland.or.us>, david parsons writes:
>+-----
>| david parsons \bi/ Pushing the published kernel interfaces into a shared
>| \/ library is creeping dangerously close to the NT wad-o-
>| dll's approach.
>+--->8
>
>And what else is libc.so (aside from being one humongous DLL instead of a
>bunch of smaller ones)?

But that's not the kernel interface, that's simply a collection of
nice wrappers around the kernel interface.

Today I can write code that avoids libc altogether and continues to
work, but if libc becomes the published interface, that guarantee is
gone.

____
david parsons \bi/ Yes, I do have some code that links with
\/ ld -m i386linux -o $PROG $OBJS

-
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/