From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Please get me straight about sysvinit vs. systemd, udev vs eudev vs mdev, virtuals and other things...
Date: Mon, 3 Mar 2014 14:10:44 -0500 [thread overview]
Message-ID: <20140303141044.a39135a353f02757254832f3@comcast.net> (raw)
In-Reply-To: <CADPrc83+-cyNCq6hTeB9qFC2d+YsyFqmg3rFp96_+ycEjG86=Q@mail.gmail.com>
On Mon, 3 Mar 2014 12:20:29 -0600
Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> > I have never used udev/eudev/mdev or anything similar and, if I am allowed
> > to nave a choice, I never will.
>
> You will always have that choice, since the software is free.
>
That's not true anymore. My USB scanners will not operate unless udev
is able to create an entry within the /dev tree.
Fortunately, I was able to discover a work-around that does not require
udev, but the point is that freedom of choice is starting to disappear.
Udev will eventually be the *only* way to deal with hardware.
>
> If you want to create a /dev tree for a computer that never gets new
> hardware connected via USB, bluetooth, or another bus, yeah, it's
> pretty trivial.
>
> Too bad that kind of computer is going the way of the dodo.
>
Also not true. We are, to be sure, experiencing explosive growth in
mobile computing but there is still a substantial number of traditional
desktop machines in operation for which udev is still quite unnecessary.
But, to continue your point, we can also claim that hardware itself
is going the way of the dodo. The way of the future is to have Linux,
and all other operating systems, existing on top of layers of virtualization
without the need for specific hardware concerns at all.
This possibility for total virtualization would still not be desirable
for all.
>
> The alternatives will be always available, of course.
>
I hope that you are right, but when I see distributions like "Linux
From Scratch," which purport to give the user total understanding
and control of his system, not including alternatives to udev I begin
to have serious doubts.
Frank Peters
next prev parent reply other threads:[~2014-03-03 19:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 16:57 [gentoo-amd64] Please get me straight about sysvinit vs. systemd, udev vs eudev vs mdev, virtuals and other things Mark Knecht
2014-03-02 17:45 ` Canek Peláez Valdés
2014-03-02 18:12 ` Mark Knecht
2014-03-02 18:38 ` Canek Peláez Valdés
2014-03-02 18:10 ` Rich Freeman
2014-03-02 18:32 ` Mark Knecht
2014-03-02 18:42 ` Canek Peláez Valdés
2014-03-02 18:58 ` Mark Knecht
2014-03-02 20:04 ` B Vance
2014-03-03 17:15 ` Tanstaafl
2014-03-03 17:40 ` Rich Freeman
2014-03-03 18:12 ` Frank Peters
2014-03-03 18:20 ` Canek Peláez Valdés
2014-03-03 18:36 ` Barry Schwartz
2014-03-03 18:40 ` Canek Peláez Valdés
2014-03-03 18:57 ` Barry Schwartz
2014-03-03 19:10 ` Canek Peláez Valdés
2014-03-03 19:10 ` Frank Peters [this message]
2014-03-03 19:20 ` Canek Peláez Valdés
2014-03-03 19:20 ` Mark Knecht
2014-03-03 21:51 ` Frank Peters
2014-03-03 22:00 ` Rich Freeman
2014-03-03 22:02 ` Mark Knecht
2014-03-03 19:26 ` Barry Schwartz
2014-03-03 18:32 ` Barry Schwartz
2014-03-03 17:44 ` [gentoo-amd64] " Duncan
2014-03-03 17:58 ` Canek Peláez Valdés
2014-03-03 18:38 ` Mark Knecht
2014-03-03 18:57 ` Rich Freeman
2014-03-03 19:09 ` Mark Knecht
2014-03-03 19:18 ` Drake Donahue
[not found] ` <5314d594.85a12b0a.3030.ffffda67SMTPIN_ADDED_BROKEN@mx.google.com>
2014-03-03 22:50 ` Mark Knecht
2014-03-03 19:43 ` Duncan
2014-03-03 19:56 ` Rich Freeman
2014-03-13 10:10 ` Duncan
2014-03-13 13:45 ` [gentoo-amd64] Systemd Was: Please get me straight about sysvinit vs. systemd [...] Duncan
2014-03-13 17:24 ` Phil Turmel
2014-03-13 17:55 ` Rich Freeman
2014-03-13 19:20 ` [gentoo-amd64] " Duncan
2014-03-15 6:21 ` Jonathan Callen
2014-03-15 10:11 ` [gentoo-amd64] Systemd and journald Was: Systemd Duncan
2014-03-03 17:47 ` [gentoo-amd64] Please get me straight about sysvinit vs. systemd, udev vs eudev vs mdev, virtuals and other things Canek Peláez Valdés
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=20140303141044.a39135a353f02757254832f3@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