[opensuse-arm] Overlay images for Raspberry Pi 3
I am considering using the Raspberry Pi 3 in a project. My testing to date has been with Leap 42.2. It has really worked well. I have a couple of questions: 1. I would like to run openSUSE in such a way that the OS image is read-only. All files that change are in RAM. I have built openSUSE images like this (for standard PCs) using KIWI. Live openSUSE images are also built this way. Has anyone done this for the PI 3? I know that the boot starts out a bit different. Could that be a problem here? 2. If there is no technical reason against this (from the Pi 3 POV), I would imagine my next step would be to copy the appropriate items in OBS into my OBS project, and attempt changes there. Or is there a better approach? What would be the projects to copy? I would prefer to copy as little as possible so that I do not branch off somewhere. I still want to run the released versions of things - except for the kiwi change to get the overlay file system stuff set up. 3. Is it possible to boot the PI 3 via PXE? My motivation would be that the OS image need not be on the SD card. I have looked at resources like https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net.... So I would think this should work - if I can make the previous items work. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 06.09.17 09:36, Roger Oberholtzer wrote:
I am considering using the Raspberry Pi 3 in a project. My testing to date has been with Leap 42.2. It has really worked well. I have a couple of questions:
1. I would like to run openSUSE in such a way that the OS image is read-only. All files that change are in RAM. I have built openSUSE images like this (for standard PCs) using KIWI. Live openSUSE images are also built this way. Has anyone done this for the PI 3? I know that the boot starts out a bit different. Could that be a problem here?
I'm not 100% sure if all internal kiwi logic handles things well, but in general booting, architectures and the read-only logic should be quite well separated. I'd say just give it a try ;). A lot probably depends on the mode you're using. IIRC kiwi supported multiple different ways of doing read-only rootfs images.
2. If there is no technical reason against this (from the Pi 3 POV), I would imagine my next step would be to copy the appropriate items in OBS into my OBS project, and attempt changes there. Or is there a better approach? What would be the projects to copy? I would prefer to copy as little as possible so that I do not branch off somewhere. I still want to run the released versions of things - except for the kiwi change to get the overlay file system stuff set up.
You can just link your local JeOS-raspberrypi3.aarch64 against the JeOS package I guess and then modify it locally. Newer versions of the JeOS code use the multibuild feature, so if you link against it make sure to remove the _multibuild file - otherwise you'll end up building all available images in your local tree ;).
3. Is it possible to boot the PI 3 via PXE? My motivation would be that the OS image need not be on the SD card. I have looked at resources like https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net.... So I would think this should work - if I can make the previous items work.
It is, but I haven't used that boot path yet. You'll have to somehow load grub via pxe, then pxe inside grub and do a "normal" uefi like pxe boot from there. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Alexander Graf -
Roger Oberholtzer