From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev-191 bit me. Insufficient ptys
Date: Sat, 2 Feb 2013 16:21:10 +0100 [thread overview]
Message-ID: <20130202162110.1623aaa5@weird.wonkology.org> (raw)
In-Reply-To: <CA+czFiD0PYZ7tDr_zbq0gYeLPPp-MrTsjL4ahJL0yCr1h1bYfg@mail.gmail.com>
Michael Mol writes:
> So, I botched the upgrade to udev-191. I thought I'd followed the
> steps, but I apparently only covered them for one machine, not both.
[...]
> Udev also complained about DEVTMPFS not being enabled in the
> kernel.[2] I couldn't get into X, but I could log in via getty and a
> plain old vt, so I enabled it, rebuilt the kernel, installed it and
> rebooted...and now that's presumably covered.
Ran into the same problem, with my sister's PC. Which I had updated from
remote, so I did not see the elogs. I do not think it is correct
behaviour to continue building udev although the system wouldn't boot
with that kernel option missing. I would expect the udev ebuild to check
the running kernel for that option, and refuse to build until it has it
set. Or until building is forced by some USE flag or an environment
variable.
Had these things not been handled better in the past?
Alex
next prev parent reply other threads:[~2013-02-02 15:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 3:35 [gentoo-user] udev-191 bit me. Insufficient ptys Michael Mol
2013-01-31 4:45 ` Canek Peláez Valdés
2013-01-31 4:48 ` Canek Peláez Valdés
2013-01-31 13:26 ` Michael Mol
2013-01-31 13:47 ` Michael Mol
2013-01-31 14:05 ` Michael Mol
2013-01-31 14:30 ` Peter Humphrey
2013-01-31 14:37 ` Michael Mol
2013-01-31 18:24 ` Mick
2013-01-31 18:29 ` Michael Mol
2013-01-31 14:31 ` Michael Mol
2013-01-31 14:45 ` Peter Humphrey
2013-01-31 15:23 ` Alan McKinnon
2013-01-31 15:26 ` Michael Mol
2013-02-02 15:21 ` Alex Schuster [this message]
2013-02-02 19:17 ` Alan McKinnon
2013-02-02 20:31 ` Neil Bothwick
2013-02-02 20:47 ` Alan McKinnon
2013-02-02 20:53 ` Bruce Hill
2013-02-03 11:24 ` Neil Bothwick
2013-02-03 12:02 ` Alan McKinnon
2013-02-03 14:54 ` Neil Bothwick
2013-02-03 17:24 ` Alan McKinnon
2013-02-03 19:08 ` Neil Bothwick
2013-02-03 19:23 ` Michael Orlitzky
2013-02-02 21:06 ` Michael Mol
2013-02-03 17:51 ` Alex Schuster
2013-02-03 19:08 ` [gentoo-user] " »Q«
2013-02-07 17:40 ` [gentoo-user] " Tanstaafl
2013-02-07 17:53 ` Peter Humphrey
2013-02-07 20:53 ` Tanstaafl
2013-02-07 21:25 ` Paul Hartman
2013-02-07 21:37 ` Tanstaafl
2013-02-07 22:00 ` Alecks Gates
2013-02-07 22:12 ` [gentoo-user] " »Q«
2013-02-08 7:29 ` [gentoo-user] " Alan McKinnon
2013-02-08 16:02 ` Paul Hartman
2013-02-08 20:17 ` Peter Humphrey
2013-02-11 1:40 ` Stroller
2013-02-07 21:38 ` Canek Peláez Valdés
2013-02-11 15:38 ` Stefan G. Weichinger
2013-02-11 16:14 ` Mick
2013-02-11 17:36 ` Dale
2013-02-11 19:41 ` Stefan G. Weichinger
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=20130202162110.1623aaa5@weird.wonkology.org \
--to=wonko@wonkology.org \
--cc=gentoo-user@lists.gentoo.org \
/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