From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Boycott Systemd
Date: Tue, 23 Sep 2014 10:55:58 -0400 [thread overview]
Message-ID: <20140923105558.eaed8b57d00ddd92818cec55@comcast.net> (raw)
In-Reply-To: <pan$9b5e5$6e4d0502$901f87a4$6a1c3f35@cox.net>
On Mon, 22 Sep 2014 16:14:11 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
>
> Again, bottom line, report kernel breakage of userspace, the same kernel
> cycle that breakage happens if at all possible, which means testing an
> early enough kernel rc (rc3 is good)
>
That certainly is good advice but unfortunately, even if I had the
desire, I do not have the wherewithal to follow kernel development
too closely. But the next time I see breakage with a new kernel
I will fire off a quick message to LKML about it.
Also, my example of the changes in USB device nodes is not the only
recent occurrence of /dev tree modifications. The kernel folks also
removed the static /dev/rtc, or real-time clock device node. In place
there is now /dev/rtc1, /dev/rtc2, etc., and the intention is to
dynamically allocate these nodes with udev. This change broke my
use space but it was easy to fix.
But does this represent a creep toward having the kernel depend on
the user-space udev (or its equivalents)? Because I don't closely
follow kernel development I cannot say for certain, but it sure seems
that way.
Let's face it. The static device tree is "old" Unix and is way
out of the current fashion. The "old" way is to know your hardware
and manually configure accordingly. The "new" way is to have the system
determine your hardware and do the configuration for you (based
on a distributed database of zillions of entries, possibilities,
and permutations).
next prev parent reply other threads:[~2014-09-23 14:56 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 17:25 [gentoo-amd64] Boycott Systemd Frank Peters
2014-09-21 17:37 ` Canek Peláez Valdés
2014-09-21 18:30 ` Frank Peters
2014-09-21 19:15 ` Canek Peláez Valdés
2014-09-21 19:20 ` Barry Schwartz
2014-09-21 19:22 ` Canek Peláez Valdés
2014-09-21 19:33 ` Barry Schwartz
2014-09-21 19:45 ` Canek Peláez Valdés
2014-09-21 19:48 ` Canek Peláez Valdés
2014-09-21 21:13 ` Frank Peters
2014-09-21 22:04 ` Canek Peláez Valdés
2014-09-21 22:15 ` Harry Holt
2014-09-21 22:28 ` Canek Peláez Valdés
2014-09-22 5:27 ` [gentoo-amd64] " Duncan
2014-09-22 0:26 ` [gentoo-amd64] " Frank Peters
2014-09-22 0:45 ` Rich Freeman
2014-09-22 2:02 ` Frank Peters
2014-09-22 2:34 ` Rich Freeman
2014-09-22 6:00 ` [gentoo-amd64] " Duncan
2014-09-22 12:47 ` Harry Holt
2014-09-22 12:53 ` Rich Freeman
2014-09-22 16:14 ` Duncan
2014-09-23 14:55 ` Frank Peters [this message]
2014-09-24 11:25 ` Duncan
2014-09-24 16:58 ` Frank Peters
2014-09-25 4:12 ` Duncan
2014-09-25 11:34 ` Harry Holt
2014-10-07 14:18 ` Harry Holt
2014-10-07 14:55 ` Barry Schwartz
2014-10-07 17:04 ` Rich Freeman
2014-10-07 20:43 ` Barry Schwartz
2014-10-07 20:54 ` Damien Levac
2014-10-07 21:19 ` Barry Schwartz
2014-10-07 21:45 ` Rich Freeman
2014-10-08 1:15 ` Frank Peters
2014-10-08 2:28 ` Rich Freeman
2014-10-08 3:19 ` Harry Holt
2014-10-08 12:34 ` Phil Turmel
2014-10-08 18:02 ` Frank Peters
2014-10-08 21:42 ` Barry Schwartz
2014-10-08 3:23 ` Frank Peters
2014-09-22 13:23 ` Barry Schwartz
2014-09-22 17:00 ` Frank Peters
2014-09-22 16:21 ` Frank Peters
2014-09-22 19:46 ` Duncan
2014-09-22 17:04 ` [gentoo-amd64] " Lie Ryan
2014-09-22 17:58 ` Barry Schwartz
2014-09-22 18:22 ` Canek Peláez Valdés
2014-09-22 19:08 ` Barry Schwartz
2014-09-22 19:18 ` Canek Peláez Valdés
2014-09-22 19:46 ` Barry Schwartz
2014-09-22 19:30 ` Frank Peters
2014-09-22 19:37 ` Rich Freeman
2014-09-22 19:39 ` Canek Peláez Valdés
2014-09-22 19:54 ` Barry Schwartz
2014-09-22 20:08 ` Harry Holt
2014-09-22 20:22 ` Canek Peláez Valdés
2014-09-23 4:00 ` Canek Peláez Valdés
2014-09-23 3:51 ` Antoine Martin
2014-09-23 4:07 ` Barry Schwartz
2014-09-23 5:17 ` [gentoo-amd64] grub2 upgrade fail (was Boycott Systemd) Antoine Martin
2014-09-23 5:42 ` Barry Schwartz
2014-09-23 5:50 ` Barry Schwartz
2014-09-24 12:29 ` [gentoo-amd64] " Duncan
2014-09-23 4:09 ` [gentoo-amd64] Boycott Systemd Canek Peláez Valdés
2014-09-23 4:32 ` Barry Schwartz
2014-09-23 4:48 ` Canek Peláez Valdés
2014-09-23 5:49 ` Frank Peters
2014-09-23 6:05 ` Barry Schwartz
2014-09-23 6:31 ` Canek Peláez Valdés
2014-09-23 5:28 ` Barry Schwartz
2014-09-23 17:11 ` Paul Jewell
2014-09-23 23:31 ` Systemd is really beside the point, anyway (was Re: [gentoo-amd64] Boycott Systemd) Barry Schwartz
2014-09-24 12:45 ` [gentoo-amd64] Re: Boycott Systemd Duncan
2014-09-22 18:41 ` [gentoo-amd64] " Frank Peters
2014-09-22 18:44 ` Canek Peláez Valdés
2014-09-22 19:24 ` Barry Schwartz
2014-09-22 20:07 ` Frank Peters
2014-09-22 20:24 ` Barry Schwartz
2014-09-22 20:24 ` [gentoo-amd64] " Duncan
2014-09-22 18:07 ` [gentoo-amd64] " Frank Peters
2014-09-22 16:11 ` Lie Ryan
2014-09-22 16:35 ` Barry Schwartz
2014-09-22 17:55 ` Frank Peters
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=20140923105558.eaed8b57d00ddd92818cec55@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@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