From: Dale <rdalek1967@gmail.com>
To: eudev@lists.gentoo.org
Subject: Re: [eudev] Is it ready now?
Date: Sun, 20 Jan 2013 17:59:43 -0600 [thread overview]
Message-ID: <50FC84EF.1080104@gmail.com> (raw)
In-Reply-To: <50FC36C2.5050105@opensource.dyc.edu>
Anthony G. Basile wrote:
> On 01/20/2013 12:53 PM, Dale wrote:
>> Anthony G. Basile wrote:
>>> On 01/19/2013 11:30 PM, Dale wrote:
>>>> Howdy,
>>>>
>>>> I just synced my tree and it appears udev wants to upgrade. I have a
>>>> separate /usr on lvm and really want to avoid udev that COULD break
>>>> things. I have a init thingy but not sure if it will pass the test or
>>>> not.
>>>>
>>>> Is eudev ready for people to switch to? I use KDE, latest in the
>>>> tree.
>>>> Other than that, nothing special really. I'm amd64.
>>>>
>>>> Thoughts? Things I should look out for?
>>>>
>>>> Thanks.
>>>>
>>>> Dale
>>>>
>>>> :-) :-)
>>>>
>>>
>>> eudev is ready. It has not been tested in every situation so there
>>> are unknown issues but this is true of systemd-udev also. I've been
>>> running eudev-1_beta1-r2 on a gnome desktop for a while with no
>>> issues. I'm running it on a few servers.
>>>
>>
>> So it is as simple as unmerging udev and emerging eudev? Do I need to
>> reboot afterwards or is it sufficient to go to boot runlevel, kill
>> anything udev related and then go back to default runlevel? I have
>> done this in the past with udev so I know udev restarts when it switches
>> to default runlevel from boot runlevel.
>>
>> Thanks much for the reply. Also, thanks for the work on eudev.
>>
>> Dale
>>
>> :-) :-)
>>
>
> I'm not sure right now what the best migration path would be since
> udev is also progressing forward ... I migrated by keywording eudev-0
> and I've been upgrading from there. I also added USE=openrc
> globally. If I recall, I got a blocker with udev, unmerged it and
> then merge eudev. But as of recently you might also get a blocker with
> kmod.
>
> Having said that, the migration was the worst part. After that I was
> fine.
>
>
>
>
I have the udev USE flag set for some reason, I'm sure something needed
it at some point. Should I turn that off or does it matter?
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2013-01-21 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 4:30 [eudev] Is it ready now? Dale
[not found] ` <50FBCBFD.4000109@gentoo.org>
2013-01-20 17:53 ` Dale
2013-01-20 18:26 ` Anthony G. Basile
2013-01-20 23:59 ` Dale [this message]
2013-01-21 8:46 ` Dale
2013-01-21 12:24 ` Anthony G. Basile
2013-01-22 7:18 ` Dale
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=50FC84EF.1080104@gmail.com \
--to=rdalek1967@gmail.com \
--cc=eudev@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