Hi!
> > I've seen this question several times in this thread. I haven't seen the
> > obvious answer, though.
> >
> > Have a new system call:
> >
> > ctlfd = open_device_control_fd(fd);
> >
> > If fd is something that doesn't have a control interface (say, it already
> > is a control
Hi!
I've seen this question several times in this thread. I haven't seen the
obvious answer, though.
Have a new system call:
ctlfd = open_device_control_fd(fd);
If fd is something that doesn't have a control interface (say, it already
is a control filehandle), this
On Sunday 20 May 2001 15:40, Alexander Viro wrote:
> > ctlfd = open_device_control_fd(fd);
> > If fd is something that doesn't have a control interface (say, it already
> > is a control filehandle), this returns an appropriate error code.
> It may have several. Which one?
That's why I proposed
[EMAIL PROTECTED] (Pavel Machek) wrote on 19.05.01 in
<[EMAIL PROTECTED]>:
> I think that plan9 uses something different -- they have ttyS0 and
> ttyS0ctl. This would leave us with problem "how do I get handle to
> ttyS0ctl when I only have handle to ttyS0"?
I've seen this question several
[EMAIL PROTECTED] (Pavel Machek) wrote on 19.05.01 in
[EMAIL PROTECTED]:
I think that plan9 uses something different -- they have ttyS0 and
ttyS0ctl. This would leave us with problem how do I get handle to
ttyS0ctl when I only have handle to ttyS0?
I've seen this question several times in
On Sunday 20 May 2001 15:40, Alexander Viro wrote:
ctlfd = open_device_control_fd(fd);
If fd is something that doesn't have a control interface (say, it already
is a control filehandle), this returns an appropriate error code.
It may have several. Which one?
That's why I proposed using
6 matches
Mail list logo