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 6EDAC1381F3 for ; Tue, 30 Jul 2013 05:14:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B29FAE0AD7; Tue, 30 Jul 2013 05:14:32 +0000 (UTC) Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7F721E09C4 for ; Tue, 30 Jul 2013 05:14:31 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id fq13so3773330lab.25 for ; Mon, 29 Jul 2013 22:14:29 -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=iWfjUL897jMHQyyfgjPTmU+Fb+fHcmyf2kwOEM5bvbQ=; b=MpH+UYw8D6/Wcu8GcmUPvN5utEerXGu3ZlioGApGB7ahpwRtkcJMg8U6ODnAZWlXma TXpAT2TUDNXXLDVMmfnyogNYSqcORwGY8/tFfgDGqswYcES24a1fEAQyFKkEWadpmLQg +5gvD2rl4GVO4p4B6KlhoSeASfazsAWwQspvhGd4YQxcd1wSHO60Uo21dgEE0pGJMqB0 I5JqdXs2DvdK26hCLkEYY/HLXvwp94+6Y1UdbPMXzNwgkMxUJym/gLuwFbaThX9ALPxr /akT3zXJ6T2t8cmFoAuc+iWCQHeBNJEwR8kkoDs78iDtac0MCub5AvVklXuGlkAaCqSU n2ng== 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.152.121.73 with SMTP id li9mr28439193lab.42.1375161269756; Mon, 29 Jul 2013 22:14:29 -0700 (PDT) Received: by 10.114.96.2 with HTTP; Mon, 29 Jul 2013 22:14:29 -0700 (PDT) In-Reply-To: <87d2q050ht.fsf@nyu.edu> References: <87d2q050ht.fsf@nyu.edu> Date: Tue, 30 Jul 2013 00:14:29 -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: 8aad8206-e76b-42a3-a05b-c3ca7bbda7c7 X-Archives-Hash: 1ffb752838748f6d916ae470dd2163ce On Mon, Jul 29, 2013 at 7:56 PM, wrote: > I am a gnome-3 user, who wants to continue with gnome-3. I understand > now that to move to 3.8 requires I move from openRC to systemd and am > trying to accomplish that now. I have so far only done the easy first > steps. > > 0. I always back up my user files and /etc daily > > 1. I confirmed that my system still boots off my installation CD > (just in case). > > 2. I added enough entries to /etc/portage/package.mask to prevent > systemd being required (list at the end if others are interested). > > 3. Performed the kernel prerequisites from the wiki (most of which > were already enabled). > > 4. My /run directory was already present and populated. Sounds reasonable. > Now I hit my first question > > The wiki says that "upstream suggests that the /etc/mtab file should > be a simlink to /proc/self/mounts." It then points out problems with > and without the symlink. > > My current system has both files but with slightly different contents, > specifically the entries for my filesystems, root (includes /usr) and sev= eral > lvm2 lvs, say "commit=3D0 0 2" in /etc/mtab but say "data=3Dordered 0 0" > in /proc/self/mounts > > Do you advising leaving it alone or executing > ln -sf /proc/self/mounts /etc/mtab AFAIU, systemd will print the following warning if /etc/mtab is not a symlink to /proc/self/mounts: "/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a symlink to avoid incorrect or misleading mount(8) output." Also, upstream will reject flatly any support for systems where this happens. Lastly, if I understand correctly, /proc/self/mounts is how the mounts are really mounted, so if they differ, /proc/self/mounts contains the correct information. If you switch to systemd, you will need to make /etc/mtab a symlink to /proc/self/mounts. > After that comes the big one > > emerge systemd > USE=3D"... systemd ..." > emerge --change-use > /etc/init.d/udev restart > > Can the system be rebooted at this point (I realize init will still not > use systemd) or must the entire conversion (including changing init) be > completed before the system is bootable? I am hoping it is the former. If you install systemd, sys-fs/udev will be uninstalled first (they block each other). At this point, /etc/init.d/udev doesn't exists anymore in your system. If you reboot, I don't believe there is any chance your system will boot up correctly. /etc/init.d/udev is installed by sys-fs/udev; sys-apps/systemd doesn't provide anything similar. I recommend installing everything necessary (and uninstalling everything that is not) before trying the reboot. Also, instead of emerge --changed-use (not --change-use, BTW), try: emerge --update --deep --newuse --verbose Or its shorter equivalent, emerge -uDNv world. --deep will force a check on the entire dependency tree, --newuse will trigger reinstallation for flags you didn't set. I think, in this case at least, it's better to cover as many possible packages affected by the switch. Although I update my systems always with --deep and --newuse. Also, I would do the whole shebang in a one step, removing all the masked packages you did. You can try to boot to multi-user.target instead of graphical.target, if you want to test that systemd works correctly independently of GNOME. 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