From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F1F101385A3 for ; Sun, 20 Jan 2013 18:26:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7A04221C182; Sun, 20 Jan 2013 18:26:21 +0000 (UTC) Received: from virtual.dyc.edu (mail.virtual.dyc.edu [67.222.116.22]) by pigeon.gentoo.org (Postfix) with ESMTP id BE74121C182 for ; Sun, 20 Jan 2013 18:26:20 +0000 (UTC) Received: from [192.168.3.7] (cpe-67-252-134-33.buffalo.res.rr.com [67.252.134.33]) by virtual.dyc.edu (Postfix) with ESMTPSA id B3AD474C029 for ; Sun, 20 Jan 2013 13:26:17 -0500 (EST) Message-ID: <50FC36C2.5050105@opensource.dyc.edu> Date: Sun, 20 Jan 2013 13:26:10 -0500 From: "Anthony G. Basile" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121231 Thunderbird/10.0.11 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: eudev mailing list X-BeenThere: eudev@gentoo.org X-BeenThere: eudev@lists.gentoo.org MIME-Version: 1.0 To: eudev@lists.gentoo.org Subject: Re: [eudev] Is it ready now? References: <50FB72D0.90006@gmail.com> <50FBCBFD.4000109@gentoo.org> <50FC2F1C.707@gmail.com> In-Reply-To: <50FC2F1C.707@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: e7d0bf99-6777-4ce4-9cfd-53b5bf115252 X-Archives-Hash: 54a0c47cc6018a3f6f74ab8e2060d863 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. -- Anthony G. Basile, Ph. D. Chair of Information Technology D'Youville College Buffalo, NY 14201 (716) 829-8197