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 C4829138CD3 for ; Thu, 28 May 2015 22:34:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 20EE8E08AF; Thu, 28 May 2015 22:34:24 +0000 (UTC) Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DA17AE089D for ; Thu, 28 May 2015 22:34:22 +0000 (UTC) Received: by pdbqa5 with SMTP id qa5so51484649pdb.0 for ; Thu, 28 May 2015 15:34:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=k8E9ogBqYHNmBwUxu3pLvoZOURhqmwOmemncsVnuSNU=; b=rhkOxKmbslxc2kNVKrxSlnOtXwP93KS5bzCDJm4Q38ygcsXW9HkNP3aDu6RGlVXBrl OHjUzuJ2wmoiUrQuqws2PDLP1BdFWTvQ2gJma5OLYQULlnBOoKJSo49inWyssXmDX90x WN6Y1wduk9fg7kC1bWonBtyvvGzZqzY8DEcopHAlMCvhzgvB7ys6iRBODu2hYSUKsfMI n0HPZDlcjE3wI0LTTfnsQNraNdm4vrxKa6O7DpodseooP6IhZ6feZlfIpbk0W/7rIy46 ePP30CNTkEQOIuqt6rUGL5DtKXS3JRKICotcvMsdatULVglJrXyidhQQBl8a6nrllrrR fnjQ== X-Received: by 10.70.140.108 with SMTP id rf12mr9436926pdb.140.1432852462006; Thu, 28 May 2015 15:34:22 -0700 (PDT) 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 Received: by 10.66.82.195 with HTTP; Thu, 28 May 2015 15:34:01 -0700 (PDT) In-Reply-To: References: <28995.1432789799@ccs.covici.com> <30995.1432793754@ccs.covici.com> <5566BFF9.7040004@xunil.at> <1823.1432798791@ccs.covici.com> <5566CA9F.5040608@xunil.at> <5450.1432801814@ccs.covici.com> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Thu, 28 May 2015 17:34:01 -0500 Message-ID: Subject: Re: [gentoo-user] problems debugging a systemd problem To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a1135f85403793a05172bf6ca X-Archives-Salt: 5a5e2602-a1d5-4834-8b79-04eeb4250a98 X-Archives-Hash: 6cd190851f05b69ac675ac436a52703e --001a1135f85403793a05172bf6ca Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, May 28, 2015 at 5:23 PM, Rich Freeman wrote: > > On Thu, May 28, 2015 at 5:32 PM, Canek Pel=C3=A1ez Vald=C3=A9s wrote: > > > > As I said, I did the following tests: > > > > 1. Adding "emergency" to the kernel command line, with a valid root=3D. > > 2. Adding "rescue" to the kernel command line, with a valid root=3D. > > 2. Leaving root=3D invalid without adding neither "emergency" nor "rescue". > > > > If root=3D is valid, with emergency systemd drops you to a shell with y= our > > root filesystem mounted read-only. With rescue, systemd drops you to a shell > > with all your filesystems mounted read-write. > > > > If root=3D is invalid, it doesn't matter if you use emergency, rescue, = or > > neither, *dracut* drops you to a shell, still inside the initramfs > > obviously. It takes a while; I didn't took the time, but I think it was 3 > > minutes. Inside this shell, you can use systemd normally, and if you manage > > to mount the root filesystem, I'm sure you could continue the normal boot > > process. You'll have to pivot root manually, though. > > That was basically my understanding of how dracut behaved. I think > we're just having a communication gap or something, because you seem > to be disagreeing with me when I'm basically trying to describe the > behavior you just listed above. It's possible; I was wrong about emergency doing anything when root=3D is invalid, but I did not understood the above behavior from your previous mails. Anyway, if dracut cannot mount the root filesystem, it will drop you into a shell with a functional systemd. Eventually. Regards. -- Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico --001a1135f85403793a05172bf6ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, May 28, 2015 at 5:23 PM, Rich Freeman <rich0@gentoo.org> wrote:
>
>= ; On Thu, May 28, 2015 at 5:32 PM, Canek Pel=C3=A1ez Vald=C3=A9s <caneko@gmail.com> wrote:
> ><= br>> > As I said, I did the following tests:
> >
> >= ; 1. Adding "emergency" to the kernel command line, with a valid = root=3D.
> > 2. Adding "rescue" to the kernel command li= ne, with a valid root=3D.
> > 2. Leaving root=3D invalid without a= dding neither "emergency" nor "rescue".
> >> > If root=3D is valid, with emergency systemd drops you to a shell= with your
> > root filesystem mounted read-only. With rescue, sys= temd drops you to a shell
> > with all your filesystems mounted re= ad-write.
> >
> > If root=3D is invalid, it doesn't m= atter if you use emergency, rescue, or
> > neither, *dracut* drops= you to a shell, still inside the initramfs
> > obviously. It take= s a while; I didn't took the time, but I think it was 3
> > mi= nutes. Inside this shell, you can use systemd normally, and if you manage> > to mount the root filesystem, I'm sure you could continue t= he normal boot
> > process. You'll have to pivot root manually= , though.
>
> That was basically my understanding of how dracut= behaved.=C2=A0 I think
> we're just having a communication gap o= r something, because you seem
> to be disagreeing with me when I'= m basically trying to describe the
> behavior you just listed above.<= br>
It's possible; I was wrong about emergency doing anything when r= oot=3D is invalid, but I did not understood the above behavior from your pr= evious mails.

Anyway, if dracut cannot mount the root filesystem, it= will drop you into a shell with a functional systemd. Eventually.

R= egards.
--
Canek Pel=C3=A1ez Vald=C3=A9s
Profesor de asignatura, F= acultad de Ciencias
Universidad Nacional Aut=C3=B3noma de M=C3=A9xico --001a1135f85403793a05172bf6ca--