From: Richard Weinberger <richard@sigma-star.at>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] "Couldn't grant pty"
Date: Sat, 12 Jan 2013 15:29:47 +0100 [thread overview]
Message-ID: <20130112152947.0e89203b@spider.haslach.nod.at> (raw)
In-Reply-To: <50F1585A.8050006@nagafix.co.uk>
Am Sat, 12 Jan 2013 19:34:34 +0700
schrieb Antoine Martin <antoine@nagafix.co.uk>:
> > DEB1-32 login: get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > get_pty : Couldn't grant pty - errno = -2
> > open_pts : Failed to open pts
> > INIT: Id "s0" respawning too fast: disabled for 5 minutes
> Since I made this root_fs, I guess I need to update the webpage as the
> this one is supposed to boot ok with UML, without any tty issues.
>
> Note however that I rarely use those filesystems with UML anymore, and
> many distros have repeatedly moved/changed/broken tty initialization
> in so many undocumented ways that I stopped caring a long time ago.
> That said, if someone finds the solution, I'll gladly apply it.
I test most of your filesystems on UML.
Mostly the Debian ones on both x86_64 and x86.
Bob, what exactly are you doing?
I just did:
make defconfig ARCH=um SUBARCH=x86
make linux ARCH=um SUBARCH=x86
# Image from
http://fs.devloop.org.uk/filesystems/Debian-Squeeze/Debian-Squeeze-x86-root_fs.bz2^C ./linux
ubda=Debian-Squeeze-x86-root_fs root=/dev/ubda mem=512M
It boots like charm.
*confused*,
//richard
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2013-01-12 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 9:55 [uml-devel] "Couldn't grant pty" Dave (Bob)
2013-01-12 9:58 ` Richard Weinberger
2013-01-12 12:07 ` Dave Humphreys (Bob)
2013-01-12 12:34 ` Antoine Martin
2013-01-12 14:29 ` Richard Weinberger [this message]
2013-01-12 15:52 ` Dave Humphreys (Bob)
2013-01-12 16:00 ` Richard Weinberger
2013-01-12 17:05 ` Dave Humphreys (Bob)
2013-01-12 22:06 ` Richard Weinberger
2013-01-14 20:42 ` Dave (Bob)
2013-01-12 18:31 ` [uml-devel] Network related UML Crashing Dave Humphreys (Bob)
2013-01-12 22:11 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130112152947.0e89203b@spider.haslach.nod.at \
--to=richard@sigma-star.at \
--cc=antoine@nagafix.co.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox