search

maxnet / berryboot

Berryboot -- Boot menu / OS installer
http://www.berryboot.com/
Other
807 stars 133 forks source link

BerryBoot and PiNet client image incompatibility #465

Open lawrence2-boothby opened 6 years ago

lawrence2-boothby commented 6 years ago

PiNet boot issue under BerryBoot:

The PiNet client has only a small boot file because it wants to PXE load its fat client OS by PXE so that a computer lab only needs to do updates on the server, not on all the MicroSD cards of each student client Raspberry Pi workstation. It would be very nice if BerryBoot had an option to load the Pinet client's tiny boot file so that it could fetch the rest of its OS by PXE from the Pinet server computer. Instead, BerryBoot uses its own boot loader and there are no data files for BerryBoot to load.

BerryTerminal works well with Edubuntu 12.04, so you must know how to make the initial boot stage of this work for PiNet although PiNet no longer uses the LTSP server it started with before writing its own server.

maxnet commented 6 years ago

Don't think it does PXE, but has a NFS/NBD server address hard coded in cmdline.txt That's problematic for us to support. Doesn't provide a way to auto-detect server.

lawrence2-boothby commented 6 years ago

Quoting from pinet.org.uk home page: " Network booting

The Raspberry Pi operating system (Raspbian) is also stored on the central server, meaning each Raspberry Pi boots up off it each time. This allows you to maintain one perfect master operating system."

It would not be necessary or even desirable for BerryBoot to handle NFS/NBD or PXE when booting PiNet client - all that is necessary is to launch the PiNet client boot process in its image and it will act as though it were the only operating system on the MicroSD card and do these things for itself. What I think is happening is that BerryBoot substitutes its boot code for booting each of the OS multi-booting on the MicroSD card with the result that PiNet never uploads its Rasperian OS from the PiNet server. In production, it would be fine to have only PiNet on the the client MicroSD cards, but for evaluation purposes, people would like to be able to multi-boot many of the OS that BerryBoot does support without having to use a separate MicroSD card just for PiNet. In particular it would be nice to compare BerryTerminal with PiNet on the same MicroSD card and using BerryBoot to switch between them.

-Lawrence

On Wed, Jan 24, 2018 at 11:51 AM, maxnet notifications@github.com wrote:

Don't think it does PXE, but has a NFS/NBD server address hard coded in cmdline.txt That's problematic for us to support.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/maxnet/berryboot/issues/465#issuecomment-360253055, or mute the thread https://github.com/notifications/unsubscribe-auth/AiHowiyr1kL4hbZ0UKdhvnu3Hcbkc4MTks5tN4ncgaJpZM4RrqRd .

maxnet commented 6 years ago

all that is necessary is to launch the PiNet client boot process in its image

Aren't those client files located on the NFS/NBD share?