Re: fs questions
- To: hurd <firstname.lastname@example.org>
- Subject: Re: fs questions
- From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
- Date: Sat, 1 Apr 2000 18:10:17 +0200
- Message-id: <[🔎] 20000401181017.A418@ulysses.dhis.net>
- In-reply-to: <20000401172548.B4696@DeepThought.>; from email@example.com on Sat, Apr 01, 2000 at 05:25:48PM +0200
- References: <20000331150716.A4921@zebra.ie> <20000331105910.A9006@walfield.org> <20000331200856.A5283@zebra.ie> <20000331132803.B9006@walfield.org> <20000401172548.B4696@DeepThought.>
On Sat, Apr 01, 2000 at 05:25:48PM +0200, Norbert Nemec wrote:
> I remember seeing something for Linux on sunsite.unc.edu. It was very old
> 0.1 version, though. Don't think anything came from it. Seemed to me like
> they had to struggle a lot with inodes, where they did not find a clean
> solution. Guess with hurd's translator concept that would not be a problem
> (Do files have to have inodes in hurd? Or is the path enough to identify
> them within a translator?)
Open files are managed by Mach ports, so you can do everything you want.
A file in the POSIXish nature of the Hurd (glibc + standard Hurd server)
is opened using its path name and the access mode, just as the open()
call describes it.
How you handle open ports or pathnames internally is not restrictd by
anything in the Hurd.
`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server
Marcus Brinkmann GNU http://www.gnu.org for public PGP Key
Marcus.Brinkmann@ruhr-uni-bochum.de, firstname.lastname@example.org PGP Key ID 36E7CD09