mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hacksaw <hacksaw@hacksaw.org>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev: what's up with old /dev ?
Date: Mon, 11 Oct 2004 16:06:02 -0400	[thread overview]
Message-ID: <200410112006.i9BK62Xn006966@hacksaw.org> (raw)
In-Reply-To: Your message of "Mon, 11 Oct 2004 14:04:19 +0200." <AE30E0FE-1B7D-11D9-96AD-000D9352858E@linuxmail.org>

>> If the initrd gets corrupted, are we just hosed?
>
>In some way, the answer is yes... I think the best is having a real, 
>on-disk, full "/dev" hierarchy in case the INITRD gets lost or 
>corrupted, which will still allow booting. Now, the INITRD can mount 
>tmpfs over "/dev" and use udev to create needed device nodes.

And see, this is where I say, what if /dev is hosed too? If the kernel at this 
point gives up, then the user has to dig up a boot CD or something worse and 
start trying to fix the system.

If, however, the kernel just made /dev/console and maybe /dev/null, it could 
start a shell and say "/dev missing /console device, initrd corrupted. Hit 
enter for a shell or ctrl-alt-del to reboot."

As a sys-admin, I'd like that. Get me into single user mode the best you can. 
If a shell can be found, that's good enough.
-- 
The best is the enemy of the good  -- Voltaire
The Good Enough is the enemy of the Great -- Me
http://www.hacksaw.org -- http://www.privatecircus.com -- KB1FVD



  reply	other threads:[~2004-10-11 20:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 22:08 J.A. Magallon
2004-10-10 22:51 ` Zack Weinberg
2004-10-10 23:15   ` Hacksaw
2004-10-10 23:25     ` J.A. Magallon
2004-10-11  0:06       ` Hacksaw
2004-10-11 19:13       ` Denis Vlasenko
2004-10-11  9:14     ` Felipe Alfaro Solana
2004-10-11 10:29       ` Arkadiusz Miskiewicz
2004-10-11 12:02         ` Felipe Alfaro Solana
2004-10-11 11:11       ` Hacksaw
2004-10-11 12:04         ` Felipe Alfaro Solana
2004-10-11 20:06           ` Hacksaw [this message]
2004-10-11 20:51             ` Bartlomiej Zolnierkiewicz
2004-10-11 21:28               ` Hacksaw
2004-10-12  0:19 ` Greg KH
2004-10-12  8:11   ` Harald Dunkel
2004-10-12 16:58     ` Greg KH
     [not found]       ` <416C26B4.6040408@t-online.de>
     [not found]         ` <20041012185733.GA31222@kroah.com>
     [not found]           ` <416C3BB6.4040200@t-online.de>
     [not found]             ` <20041012203022.GB32139@kroah.com>
2004-10-12 21:35               ` Harald Dunkel
2004-10-13 13:08                 ` Mathieu Segaud
2004-10-13 14:13                   ` Harald Dunkel
2004-10-13 14:33                     ` Mathieu Segaud
2004-10-10 22:41 Michael Thonke
2004-10-11  7:19 Zack Weinberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410112006.i9BK62Xn006966@hacksaw.org \
    --to=hacksaw@hacksaw.org \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®