Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Aug 1999 19:13:23 -0700
From:      "David Schwartz" <>
To:        "Brian Somers" <>, "Poul-Henning Kamp" <>
Cc:        "Dag-Erling Smorgrav" <>, <>
Subject:   RE: cvs commit: src/sys/miscfs/specfs spec_vnops.c src/sys/sys conf.h 
Message-ID:  <000001bee856$15352af0$>
In-Reply-To: <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

> Thinking about things more.... maybe the driver just has to figure
> out the global descriptor table offset involved and use that to
> figure out what device structure is required.

	I'm sure I'm missing something here, but can't you make things like
/dev/vty a sort of 'magic symlink' that acts as if it were a symlink to the
'next' device? That way, every open would give a new device, and
fork/dup/close would work right automatically.

	This may cut across layers of abstraction currently, but perhaps a new
interface is necessary to allow drivers to hook into the symlink logic.
Doesn't /proc/curproc do the same thing? Of course, it's easy to put a magic
symlink in a magic directory.


To Unsubscribe: send mail to
with "unsubscribe cvs-all" in the body of the message

Want to link to this message? Use this URL: <$15352af0$021d85d1>