From: theom+news@chiark.greenend.org.uk
The Natural Philosopher wrote:
> On 23/01/2025 22:12, Chris Green wrote:
> > Is it simply a matter of leaving /boot on the SD card and changing /
> > to being a USB drive or does one need to edit something in /boot
> > somewhere?
>
> AFAICR what you do is simply edit a file and tell it that / is not where
> it thinks it is
>
> But it depends on exactly what you want to happen
>
> The boot process is as follows (I think: Others will correct If I've got
> it wrong)
>
> The Pi firmware looks on the SD card for a Vfat partition, and in there
> is a file called cmdline.txt
>
> e.g.
> console=serial0,115200 console=tty1 root=PARTUUID=778a9e44-02
> rootfstype=ext4 fs
> ck.repair=yes rootwait noswap=1
>
> That file tells the boot loader wher the root directory is to be found
> that it is to grab the kernel off
Not quite. If you do it this way, the kernel comes from the SD card and the
cmdline is the *kernel* command line, ie it tells that kernel where to find
its root FS once it has started. That means you need to ensure that the
kernel on the SD card remains updated, because any kernel on USB storage
will be ignored.
If you did that way, you could set it up with just a FAT /boot partition on
the SD and then your ext4 rootfs on USB, and adjust the cmdline and
/etc/fstab to match. That way any updates would deploy the SD card /boot.
However if you ever want to re-image your rootfs you have to remember that
you also need to re-image your SD and set up this arrangement again.
Otherwise you'd be booting old kernels from SD with your new USB rootfs.
By using bootcode.bin only on SD (something I've not tried), you can use
standard OS images on your USB without any changes.
Or you could boot direct from USB on those Pis that support it with no SD.
Theo
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
