From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH RFT] blspec: support boot /dev/disk0.rootfs to mean boot disk0.rootfs
Date: Mon, 19 Jun 2023 17:14:43 +0200 [thread overview]
Message-ID: <81bc6192-9232-e4ff-e832-1b4348bd65b6@pengutronix.de> (raw)
In-Reply-To: <20230619150859.ltl55zzgcuhjfjt2@pengutronix.de>
On 19.06.23 17:08, Marco Felsch wrote:
> Hi Ahmad,
>
> On 23-06-19, Ahmad Fatoum wrote:
>> boot /dev/disk0.rootfs would always fail:
>>
>> Nothing bootable found on '/dev/disk0.rootfs'
>> Nothing bootable found
>>
>> boot /mnt/disk0.rootfs and boot disk0.rootfs would however work.
>> This can be surprising to users, so just skip over /dev if supplied.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>> I am not sure why this wasn't the case before. Any ambiguity in doing it
>> this way? Change still needs to be tested.
>
> According commands/boot.c help message:
>
> | "BOOTSRC can be:"
> | "- a filename under /env/boot/"
> | "- a full path to a boot script"
> | "- a full path to a bootspec entry"
> | "- a device name"
> | "- a partition name under /dev/"
> | "- a full path to a directory which"
> | " - contains boot scripts, or"
> | " - contains a loader/entries/ directory containing bootspec entries"
>
> the 'full path' to a device is not suported yet. Should that be fixed
> within the boot-cmd?
You can interpret "a partition name under /dev/" as meaning both
partition name without /dev/ or with /dev/ IMO.
>
> Regards,
> Marco
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-06-19 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 14:37 Ahmad Fatoum
2023-06-19 15:08 ` Marco Felsch
2023-06-19 15:14 ` Ahmad Fatoum [this message]
2023-06-26 10:01 ` 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=81bc6192-9232-e4ff-e832-1b4348bd65b6@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
/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