Date: Fri, 13 Aug 1999 23:41:07 +0100 From: Brian Somers <brian@Awfulhak.org> To: Julian Elischer <julian@whistle.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/miscfs/specfs spec_vnops.c src/sys/sys conf.h Message-ID: <199908132241.XAA02596@keep.lan.Awfulhak.org> In-Reply-To: Your message of "Fri, 13 Aug 1999 12:51:48 PDT." <Pine.BSF.3.95.990813124653.3531H-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>
>
> On Fri, 13 Aug 1999, Poul-Henning Kamp wrote:
>
> >
> > I'm not sure I copy you here, (actually I very sure I don't :-)
> >
> > Could you explain what it is that the driver wants to know here ?
>
> The driver in one system I was playing with, needed to know when the last
> writer releasd the device so that the driver could downgrade the device to
> read-only mode. The reason for this was that when this happenned, the
> device would complete an internal back-up of the data, and label the
> backup as 'stable'.
>
> Unless you keep track of all closes and mode changes, you can't do this.
> Also Justin was saying he wnated to do this for some of his own reasons as
> well.
>
> The simplest way to do it would be to add an advisory entrypoint
> that was called for ALL closes, not just the last one, and also when a
> fork happenned as you now have more users. I wasn't too fussed about that
> one, but Justin had some good reasons at the time...
[.....]
One possibility would be to support generic devices - /dev/tun for
example rather than /dev/tun*. It'd be amazing to have /dev/pty too
:-)
--
Brian <brian@Awfulhak.org> <brian@FreeBSD.org>
<http://www.Awfulhak.org>; <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour ! <brian@FreeBSD.org.uk>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908132241.XAA02596>