All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Amadeusz Żołnowski" <aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Better error handling
Date: Wed, 06 Oct 2010 15:45:46 +0200	[thread overview]
Message-ID: <1286369299-sup-4583@etiriah> (raw)
In-Reply-To: <4CAC600C.7040309-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Excerpts from Harald Hoyer's message of Wed Oct 06 13:39:56 +0200 2010:
> Presenting the user the message "Boot has failed, sleeping forever." does not 
> really help.
> 
> Instead of displaying the message, we could:
> 
> - turn "rdshell" into "rd.no_shell" and drop to a shell by default.
>    Admins with security concerns will lock grub with a password, and can add
>    the "rd.no_shell" parameter.

Wouldn't it be a problem for "admins with security concerns" anyway?


> - add simple tools to present the user a list of mountable partitions

We already have functions probing devices, so adding this feature would
be quite easy.  It might be useful.  I can handle this if people are
looking forward for that feature.


A few my ideas:

1) Warning message on boot when option in 'rd' namespace isn't used,
e.g. when module using this option isn't included.

2) We have too much and too little info about what's going on - we have
either full debug or none.  I'd suggest having logging levels.

3) Printing, which module is being sourced, by default.


Cheers,
-- 
Amadeusz Żołnowski

PGP key: E1DBFAB5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      parent reply	other threads:[~2010-10-06 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 11:39 Better error handling Harald Hoyer
     [not found] ` <4CAC600C.7040309-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-10-06 13:45   ` Amadeusz Żołnowski [this message]

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=1286369299-sup-4583@etiriah \
    --to=aidecoe-2qtfh70ttyba5ebddlwbiw@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.