public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fwd: [gentoo-project] With regard to udev stabilization
Date: Fri, 16 Nov 2012 23:02:58 -0500	[thread overview]
Message-ID: <CA+czFiBCSoDrxp+1NFvUx2MdgNihPJ8UpNdtZ34-iTOy+qSM-g@mail.gmail.com> (raw)
In-Reply-To: <50A70A5B.5030903@gmail.com>

On Fri, Nov 16, 2012 at 10:54 PM, Dale <rdalek1967@gmail.com> wrote:
> Walter Dnes wrote:
>> On Fri, Nov 16, 2012 at 07:24:54PM -0500, Michael Mol wrote
>>> On Fri, Nov 16, 2012 at 5:47 PM, 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.
>>>>   BTW, this has hit Slashdot...
>>>> http://linux.slashdot.org/story/12/11/16/2052203/gentoo-developers-fork-udev
>>> Be sure to read Richard Yao's response:
>>> http://linux.slashdot.org/comments.pl?sid=3256499&cid=42006113
>>   I understand that he's still getting the effort organized.  I am not a
>> C programmer, but if the effort needs any beta testers, I'm willing to
>> volunteer.  BTW, it looks like Lennart Poettering is more unpopular than
>> Steve Ballmer on Slashdot.
>>
>
> Thing I like about the fork, if people get fed up with udev, udev falls
> flat on its face or something else causes udev to fail, we have a udev
> already ready.  That statement may not be true for another couple months
> or so but at least there is a Gentoo plan B.
>
> Also, I can get rid of dracut too.  ;-)
>
> Walter, I wonder how much your work helped this along?  If you had not
> stepped up and did what you have done, then this fork may have never
> happened.  You could have at least let others know there are people
> looking for something else.  If so, thanks for that.  :-D

I think Walter's work (and his dogged perseverance despite the
negative reactions I'd seen) played a pivotal role in having this play
out the way it did.

If he hadn't, I'm sure the systemd+udev thing would have gotten worked
out anyway, I'm not sure the solution would have come from within
Gentoo, and would not have come in the form of a fork, had Walter's
work not been so obvious a focal point.

Thanks, Walter.

*tips hat*

--
:wq


  reply	other threads:[~2012-11-17  4:04 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
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 [this message]
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=CA+czFiBCSoDrxp+1NFvUx2MdgNihPJ8UpNdtZ34-iTOy+qSM-g@mail.gmail.com \
    --to=mikemol@gmail.com \
    --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