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 9257B1381F3 for ; Wed, 31 Jul 2013 15:28:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 25323E0ADA; Wed, 31 Jul 2013 15:27:46 +0000 (UTC) Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A51A8E0AD6 for ; Wed, 31 Jul 2013 15:27:39 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id fp13so601247lab.24 for ; Wed, 31 Jul 2013 08:27:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=hbqeursbNT4rzGiCiQGPWbYYYACJRnVR5K8euhiyzpY=; b=uvqfgnALysTlJqQkfYNVb0pnNyb7SusPYm+c6cwaBykzvMC6p53EPiZyQ8Z7F9PamN /4l0jQlO5BtUxomQ9jQ4Y2lGQC6p7Pn1bV3YEmOc1gkKf+TLmWQdVnVGeuriVDKjiQJc RQwa8baVHRXt6PNWPjLdIiZZHZTK4W6VLh+/2EVXPAzhiCPtUUZJ5otaD91tj/XpCgog rbxT1/QwxKPiyUPf231kUHMwfFrZHH7u5fdDviGMT7pztxyDpnqH5P7lqjzZxHaTlKt3 xlc/ViGIjEywySdOaX2aD7lJD53G5zG47S5wpm2qJUl1xJrBn8RNn3lcKTXpJ0h8lPKT HlPw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.130.134 with SMTP id oe6mr1373464lbb.30.1375284452910; Wed, 31 Jul 2013 08:27:32 -0700 (PDT) Received: by 10.114.96.2 with HTTP; Wed, 31 Jul 2013 08:27:32 -0700 (PDT) In-Reply-To: <878v0mu7kk.fsf@nyu.edu> References: <87d2q050ht.fsf@nyu.edu> <87fvuva522.fsf@nyu.edu> <8738qvjb0y.fsf@einstein.gmurray.org.uk> <878v0mu7kk.fsf@nyu.edu> Date: Wed, 31 Jul 2013 10:27:32 -0500 Message-ID: Subject: Re: [gentoo-user] [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 6e69a38b-da5e-4e6a-af13-72309b58a8a0 X-Archives-Hash: 14fafd092baa349ec4c580a67f94ac79 On Wed, Jul 31, 2013 at 9:28 AM, wrote: > On Wed, Jul 31 2013, Graham Murray wrote: > >> Canek Pel=C3=A1ez Vald=C3=A9s writes: >> >>> The wiki is wrong. The script /etc/init.d/udev is part of sys-fs/udev, >>> which you need to uninstall before installing systemd. Perhaps it's >>> CONFIG_PROTECT'd, but anyway sys-fs/udev and sys-apps/systemd install >>> the udev binary in different directories, so the script is basically >>> useless after the switch. >> >> It is pulled in by sys-fs/udev-init-scripts which is a dependency of >> systemd[openrc]. So the Wiki is correct. > > But the wiki doesn't specify emerging system with the openrc flag. > Should I suggest that the wiki be modified. > > To be sure I understand. At this point I would have already > > 1. merged systemd (perhaps with USE=3D"openrc ..." > 2. set USE=3D"systemd ..." > 3. updated with emerge --newuse --deep --verbose--ask @world > * The wiki doesn't say --update; is that correct? > > I would *not* have > 1. added init=3D/usr/lib/systemd/systemd to the kernel line in grub > 2. rebooted. I think (now that Graham correctly pointed that you can preserve /etc/init.d/udev with the openrc USE flag), that then you should restart udev. > A related question. Am I correct in believing that once I do the > emerge ... @world > above I can *not* reboot until I have added the > init=3D... > phrase to the kernel line in grub (and thus committed to systemd not Open= RC) That, I believe, is correct. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Posgrado en Ciencia e Ingenier=C3=ADa de la Computaci=C3=B3n Universidad Nacional Aut=C3=B3noma de M=C3=A9xico