From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fwd: [gentoo-project] With regard to udev stabilization
Date: Wed, 14 Nov 2012 10:44:48 +0700 [thread overview]
Message-ID: <CAA2qdGWoEhFka4764O3oPiJZ2vSLcAU5jriY-aS1QhehBps+oA@mail.gmail.com> (raw)
In-Reply-To: <20121114025754.GA7408@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]
On Nov 14, 2012 10:02 AM, "Walter Dnes" <waltdnes@waltdnes.org> wrote:
>
> On Mon, Nov 12, 2012 at 09:20:42PM -0600, Dale wrote
> >
> > Well, it appears we have someone willing to fork udev. Yeppie !! Me,
> > I'm looking forward to seeing how this works and giving it a test run
> > when it gets ready. Since it is a fork, shouldn't be to long, I hope.
>
> Might even get me to come back to udev. I wonder which group will be
> setting the specs as far as "the official udev" is concerned. The
> Gentoo devs should seek support from other distros and Linus himself.
> If we merely make a fork, and the systemd people still have the
> "official version", we'll be doomed to slavishly follow them in "bug
> compatability" mode. What happens if/when Lennart gets his way?
>
http://lists.freedesktop.org/archives/systemd-devel/2012-August/006066.html
>
> > And what we will certainly not do is compromise the uniform integration
> > into systemd for some cosmetic improvements for non-systemd systems.
> >
> > (Yes, udev on non-systemd systems is in our eyes a dead end, in case
> > you haven't noticed it yet. I am looking forward to the day when we
> > can drop that support entirely.)
>
> And that's probably not the only thing that the systemd people could
> do to jerk us around. A successful fork would need to be one that
> hardware companies release drivers for, and that GNOME/KDE will support.
>
> I still think that the fork team should look at where mdev doesn't
> match udev, and write shims to add the missing functionality. The
> busybox people obviously don't want to bloat their minimal version. But
> it already does most of what is needed, so some shims to add missing
> functionality there would be less effort than an entire udev fork.
>
> > I wonder what they will name it tho.
>
> Howsabout calling it "Woodstock"? We could even have our own cheer
>
> Gimmee an EFF
>
> EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>
> Gimmee an OOO
>
> OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
>
> Gimmee an ARR
>
> ARRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
>
> Gimmee a KAY
>
> KAYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
>
> What's that spell?
>
> FORK!
>
> What's that spell?
>
> FORK!
>
> What's that spell?
>
> FORK!
>
> Now all we need is a quarter of a million people screaming in unison.
>
LOL
Now seriously:
You should follow the discussion in -project. Someone (I forgot who
exactly) has made a personal commitment to within a month produce a
serviceable udev fork, at least a Proof of Concept. And IIRC, hwoarang is
going to 'test the waters' with Debian people.
So, this is not a pipe dream. It's happening, code will be produced, ...
and I bet some people will get offended ;-)
Rgds,
--
[-- Attachment #2: Type: text/html, Size: 3568 bytes --]
next prev parent reply other threads:[~2012-11-14 3:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50A1B335.2080907@gentoo.org>
2012-11-13 3:20 ` [gentoo-user] Fwd: [gentoo-project] With regard to udev stabilization Dale
2012-11-13 8:41 ` Michael Hampicke
2012-11-13 9:23 ` Dale
2012-11-13 11:47 ` Pandu Poluan
2012-11-13 14:42 ` Bruce Hill
2012-11-13 21:56 ` pk
2012-11-14 2:57 ` Walter Dnes
2012-11-14 3:44 ` Pandu Poluan [this message]
2012-11-14 4:45 ` Dale
2012-11-16 22:47 ` Walter Dnes
2012-11-17 0:24 ` Michael Mol
2012-11-17 3:36 ` Walter Dnes
2012-11-17 3:54 ` Dale
2012-11-17 4:02 ` Michael Mol
2012-11-17 3:54 ` Michael Mol
2012-11-17 5:12 ` Walter Dnes
2012-11-17 7:29 ` Dale
2012-11-17 9:16 ` Pandu Poluan
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=CAA2qdGWoEhFka4764O3oPiJZ2vSLcAU5jriY-aS1QhehBps+oA@mail.gmail.com \
--to=pandu@poluan.info \
--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