From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-60051-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id D0BC71381F3
	for <garchives@archives.gentoo.org>; Thu,  2 May 2013 23:07:50 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id E793DE0A88;
	Thu,  2 May 2013 23:07:47 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	(using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id E9029E0998
	for <gentoo-dev@lists.gentoo.org>; Thu,  2 May 2013 23:07:46 +0000 (UTC)
Received: from [192.168.1.4] (g230104023.adsl.alicedsl.de [92.230.104.23])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: chithanh)
	by smtp.gentoo.org (Postfix) with ESMTPSA id 80A7033DF39
	for <gentoo-dev@lists.gentoo.org>; Thu,  2 May 2013 23:07:45 +0000 (UTC)
Message-ID: <5182F1C3.4000202@gentoo.org>
Date: Fri, 03 May 2013 01:07:47 +0200
From: =?UTF-8?B?Q2jDrS1UaGFuaCBDaHJpc3RvcGhlciBOZ3V54buFbg==?=
 <chithanh@gentoo.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Making systemd more accessible to "normal" users
References: <CAN3Atvo+RgmFgCYMzqjsuL4G89cJv_J7SXg42qfT3r1xQtEuTQ@mail.gmail.com> <51817269.40707@gentoo.org> <CAN3AtvqevTKBUGjVOj3SbkV8Ymf+1f0XhrjWb5Bazj14BiOH_A@mail.gmail.com> <20130502031819.GB20292@linux1> <CAATnKFBzAWf-fyb0u6RFpVCThk61s6K0S7ujMTxExGL6PKJsaw@mail.gmail.com> <20130502180519.GA25143@linux1> <CAJ0EP43CzwgnsS2ciFQ8S26e+cSojsC96BnbZdLookojT5NB6A@mail.gmail.com> <CAN3Atvqb-NyVyH0Jz4mZGqJjDfCA57+9iSV3HJjj7yuYjtmRag@mail.gmail.com> <CAATnKFAmskB3cRMBh54xQmV=BrtSHiorAocUOfNeb=RhD-uKEQ@mail.gmail.com> <20130502225545.GA29141@linux1>
In-Reply-To: <20130502225545.GA29141@linux1>
X-Enigmail-Version: 1.6a1pre
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Archives-Salt: cac69c1b-5310-4413-8945-610cf3cf81b0
X-Archives-Hash: 792861a153ec4d1497004063f49fae97

William Hubbs schrieb:

> If you use this symlink approach to actually switch your init to point 
> to systemd, then you boot and things don't work, you are hosed.

Well, not fully hosed. You could still edit your kernel command line from
the boot loader pointing init=.. to the actual location and not the symlink
(or have a backup entry ready, but then any gains from switching symlinks
are negated).


Best regards,
Chí-Thanh Christopher Nguyễn