[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Symlink, chrdev, blkdev translators

From: Marcus Brinkmann
Subject: Re: Symlink, chrdev, blkdev translators
Date: Mon, 19 Aug 2002 23:08:05 +0200
User-agent: Mutt/1.4i

On Mon, Aug 19, 2002 at 10:52:54PM +0200, Marcus Brinkmann wrote:
> > Actually, what makes a file "look like" a symlink or a character/block 
> > device
> > is just its st_mode field in struct stat. So why do we need a special case
> > that will make these kind of files "look like translators" for filesystems
> > that support them natively -- beside the fact that it's conceptually
> > equivalent?
> So you are saying that showtrans should not give us anything on special
> nodes?  What advantage does it give you to be inconsistent on purpose?

Let me answer this another way: You are looking at this from the Unix
perspective, not the Hurd perspective.  In the Hurd, those file nodes are
not special in any way, they are just translators.  That the translators are
not set by allocating a block and writing "/hurd/fifo" into it and setting a
passive translator flag in the inode, but by setting a special flag that
says "unix fifo" in the inode, is of no concern whatsoever to the Hurd.

In fact, once you access that node, you are talking to the fifo translator
which will lie and report the fifo flag in its response to io_stat.  So it
is completely transparent to the user.  Except for symlink, for which you
don't get a process of its own.


`Rhubarb is no Egyptian god.' GNU
Marcus Brinkmann              The Hurd

reply via email to

[Prev in Thread] Current Thread [Next in Thread]