Closed sedlund closed 4 years ago
Apologies for the delay in responding - I'm currently working on getting a pi3/pi4 image together.
Once that's out of the way, I will consider putting a "server" image together, as it is a request I've had a number of times.
In the meantime, there are instructions for stripping down the image yourself on the project's wiki here, which may be of use.
Best, sakaki
OK I'm having a look at a stripped down, CLI-boot version now.
What do people generally think would be useful to have as dev tools on there? Just the baseline @system
stuff, like gcc
? Or the full clang
, icedtea
, rust
etc?
Suggestions by Aug 27th please; I'll aim to lock off on something then.
Best, sakaki
I think as basic as possible.
I think as basic as possible.
@sedlund, so basically something similar to a stage 4 (but with the RPi-specific kernels, boot services etc. present), is that it?
Best, sakaki
Yes. Would be nice to add the raspbian style systemd service units to configure ssh and wifi as well.
Agree with @sedlund. As basic as possible with the RPi kernels and services present.
Yes, as basic as possible, just network, without wifi, config.txt optimised for CLI system with as much memory as possible. Probably the default kernel and not the bis kernel as default. OpenRC instead of systemd would be Ok for me.
And maybe a 32-bit ARM 7l version, too... For my Rpi2 :-)
OK that's all pretty clear, thanks.
So, I've split out a provisional innercore
package set (here) from the old core
; please let me know if there's anything missing / surplus to requirements on there; the minimal image will just have the transitive dependency closure of this plus the @system
set.
Also, you really want the default rather than -bis kernel (actually kernels, since there'll be a kernel8.img
for the RPi3 and kernel8-p4.img
for the RPi4, either way)?
Best, sakaki
I think the innercore
set looks good!
My only question is about systemd. It there a reason beyond preference for it not being used? What I'm getting at is whether trying to convert this rpi4 setup from OpenRC to systemd is something that can be done by following the Gentoo systemd documentation, or whether there are known roadblocks that make it a fools errand.
@sakaki- Don't you think the default kernels would be a good idea for a minimal image?
Do we really want to include the swap stuff in the innercore? For Rpi4 with 4 GB I would rather disable the swap for all images, guess an SD card it is slow and only damages the card with time...
@chrbayer
the reason for the swap services is really to get zswap
(which also needs some kernel config only in the -bis
kernels). On memory constrained machines this can give a significant boost to the usable memory. Not so critical on 2GiB/4GiB Pi4Bs, where all swap may safely be disabled, but I've found it to be very useful - even for headless instances - on the RPi3.
@sakaki- May I ask if the "server" image is available for download? If yes, where is the url?
@hughjfchen
there will be a 'lite' (aka 'server') image available as part of the v1.5.1 release, which is in final test now, and should be out by the end of this weekend.
best, sakaki
@sakaki- Thanks for your update. Looking forward to the 1.5.1 release!
v1.5.1 now released, with first cut at a 'lite'/'server' image available. Feedback welcome!
Hi @sakaki-. Great work!
I have a few questions regarding the packages for innercore.
Why are stuff like alsa-tools required for the innercore USE flag? I also see stuff like xdm and xconsole which seems to be pulled in by rpi3-init-scripts. Are these strictly required?
Probably not strictly required - I'll need to take a look at ensuring all the deps are minimized cross-sectionally for innercore
. My goal here was just to get an initial iteration released so people could start using it (and feed back). I'll come back to this again later, once I have revisited other pending RPi4-related things (such as updating raspbian-nspawn-64 for Buster etc.)
If you experiment, and have any suggestions for further thinning it down in the meantime, feel free to drop me a PR.
Please note that I'm not going to be able to provide variant-USE flag builds for packages though, to minimize the support burden of this. Apologies, sakaki ><
@sakaki- Shall we add docker package into the "server" image package list? After all, that's a "server" image and intended to run some server applications.
@hughjfchen i think everyone has their own concept of a server. i'd rather have a minimal base to start from, you can always install docker from binpkg.
@sakaki- Fair enough. Thanks for your effort on this image. It helps me a lot getting start on my RPI4B.
Closing now.
Random question, which relates to the server/lite image, is sshd enabled by default?
Yes, it is.
Best, sakaki
On December 12, 2019 8:03:45 PM UTC, "Skyler Mäntysaari" notifications@github.com wrote:
Random question, which relates to the server/lite image, is sshd enabled by default?
-- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: https://github.com/sakaki-/gentoo-on-rpi-64bit/issues/93#issuecomment-565163814
-- sakaki@deciban.com
Could you make a stripped down 'server' image?