On Tue, Jun 05, 2012 at 02:20:38PM +0200, Richard Weinberger wrote:
> Am 05.06.2012 13:15, schrieb Alan Cox:
> > Actually I'd prefer a clever solution which can spot all the fds are the
> > same process so we can keep compatibility but I've not found a sensible
> > way to do that.
>
> Me too.
>
>
On Tue, Jun 05, 2012 at 01:14:41AM +0200, Richard Weinberger wrote:
> Am 04.06.2012 23:17, schrieb Alan Cox:
> >>On all other ttys login works but bash dies because of of -EIO.
> >>After vhangup() the tty returns -EIO upon read()/write().
> >
> > You can't re-open the tty because a process
Hi!
Using gdbserver inside an UML instance displays "Couldn't write
debug
register". I have discovered this patch from Barry Friedman which
works
fine for me:
http://www.mail-archive.com/user-mode-linux-devel@lists.sourceforge.net/msg06753.html
Here is a rebased version of this patch:
Am 05.06.2012 13:15, schrieb Alan Cox:
> Actually I'd prefer a clever solution which can spot all the fds are the
> same process so we can keep compatibility but I've not found a sensible
> way to do that.
Me too.
For UML users the current situation is odd.
They have to select between:
- Having a
> open_tty() closes all the old file descriptors after tty open:
It needs to close them before.
>
> vhangup();
> ...
> fd = open(tty, O_RDWR | O_NONBLOCK);
> ...
>
> flags = fcntl(fd, F_GETFL);
> flags &= ~O_NONBLOCK;
> fcntl(fd, F_SETFL, flags);
>
> f
