On Mon, Dec 13, 1999 at 12:39:42AM -0800, Mike Smith wrote:
> >
> > The question is very simple. Is it possible to open the same character
> > pseudo device, for example /dev/foo0, simultaneously from other programs, and
> > to work with this instances independently?
>
> Not in the fashion that I believe you're trying to do, no.
>
> > I'm asked as the developer of a driver with such requirements, so please
> > don't complain about such technique.
>
> I think I'm going to complain anyway; this is an _extremely_ lame way to
> do things, and it breaks many assumptions about how files are meant to
> work.
>
> In your case, however, you can probably steal the 'emuldata' field in the
> proc structure to store a pointer to your per-instance data. At some
> stage, the Linux emulator will want to use this as well, and it will need
> to provide an API for multiple emulator plugins to use.
Oh no, I think it's a bad idea to store something in the proc structure,
because program want two different devices with such semantics, and it
some time 'forked'. And in common, it's a very dirty hack, and it's
doesn't remove the 'last close' problem.
Probably I'll be try to do something like 'rotated' symlink, or intercept
linux open syscall and substitute devices like /dev/foo0a, /dev/foo0b,
until don't open one.
>
> By then I hope that we'll have convinced the VMware folks to do things
> properly, or have our own binary version...
Ya-ya, I hope too.
--
Vladimir Silyaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
