mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] sandbox: env: set nv.autoboot=abort to drop to shell
Date: Wed, 7 Apr 2021 12:59:29 +0200	[thread overview]
Message-ID: <20210407105929.dzajx2ypo5gyatko@pengutronix.de> (raw)
In-Reply-To: <20210404111831.592821-1-ahmad@a3f.at>


[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]

On Sun, Apr 04, 2021 at 01:18:30PM +0200, Ahmad Fatoum wrote:
> barebox on sandbox defaults to network boot, which fails either due to
> missing TAP support (like not having CAP_NET_ADMIN) or because the files
> couldn't be fetched.
> 
> Arguably, the most user-friendly thing is to drop to shell. Do so.
> Users can still override nv.autoboot if they want to boot differently.
> 
> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>

Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

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

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2021-04-07 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 11:18 Ahmad Fatoum
2021-04-04 11:18 ` [PATCH 2/2] sandbox: state: reword warning about initial state errors Ahmad Fatoum
2021-04-07 10:59 ` Uwe Kleine-König [this message]
2021-04-13  7:43 ` [PATCH 1/2] sandbox: env: set nv.autoboot=abort to drop to shell Sascha Hauer

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=20210407105929.dzajx2ypo5gyatko@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=ahmad@a3f.at \
    --cc=barebox@lists.infradead.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