Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!midway!gargoyle!ddsw1!proxima!lucio
From: lucio@proxima.UUCP (Lucio de Re)
Newsgroups: comp.unix.wizards
Subject: Re: Wizard-level questions
Summary: Now, who doesn't think the UNIX kernel is bloated?
Message-ID: <3829@proxima.UUCP>
Date: 29 Jan 91 07:44:50 GMT
References: <16048@sdcc6.ucsd.edu> <1991Jan26.142403.22812@mp.cs.niu.edu>
Followup-To: alt.flame
Organization: FLAGSHIP Wide Area Networks - Cape Town
Lines: 25

[ follow-ups directed to alt.flame ]

In article <1991Jan26.142403.22812@mp.cs.niu.edu> rickert@mp.cs.niu.edu (Neil Rickert) writes:
>In article <16048@sdcc6.ucsd.edu> cs163wcr@sdcc10.ucsd.edu (I support the U.N.) writes:
>>[1] Can you access a file by its i-node number?  Something like
>>	(for C code) FILE *iopen (int inode, char *mode) ?
>
> I hope not.  Otherwise permissions on directories wouldn't do much.  I
>do think the system design would have been cleaner if you only accessed
>by i-node number, and mapping filename to inode was done outside the kernel.
>But I doubt that I have many supporters in this "keep the kernel small" view.

Hmmm, how about 10000 comp.os.minix readers?
>
>-- 
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
>  Northern Illinois Univ.
>  DeKalb, IL 60115                                   +1-815-753-6940

-- 
Lucio de Re.

Internet: lucio%proxima@ddsw1.mcs.com
usenet: ...!uunet!ddsw1!proxima!lucio