Dear CRUX-arm users, developers,
Over the last couple months, I have been playing around with CRUX-arm. One of
things I noticed is the lack of a handbook or general approach for CRUX-arm.
I'm aware of the difference with x86 and that there is no one size fits all
solution. It could be the lack of documentation, but I think as of now, CRUX-arm
goes against the main CRUX philosophy. The KISS principle, handbook and simple
package management are, I think, the strong points of CRUX.
For most supported boards, however, it seems it is impossible to redo/retrace
the steps, compile a bootloader/kernel and have a basic working system. With
"basic working system" here I mean something that boots and has basic
funtionality (i.e. networking and usb storage). Referring to the x86 handbook
(installation section) it just mentions how to enable some basic
options（CONFIG_SATA_AHCI=y， CONFIG_BLK_DEV_SD=y，CONFIG_EXT4_FS=y）to bring up
your root filesystem. Maybe your graphics cards or webcam doesn't work. Doesn't
matter. CRUX is targeted for the experienced user. They will figure it out.
Comparing this to the ARM branch of CRUX, most supported boards just provide a
bootloader and kernel image. But I have no idea what these kernels are about.
Are these basic configurations? Or are these copies from armbian just to work
out of the box? Again, this could be a lack of documentation and
misunderstanding on my side. But I would like to see a clearer approach. Maybe
some devices on your board don't work, doesn't matter, at least it is more
elegant. Again, I think CRUX is for the experienced user. Users that want a
fullblown and fast working system, will swander off to armbian anyway.
I would like to hear other people's opinions about the above mentioned points.
Besides that, I willing to work on a general handbook for ARM.
Sincerely,
Robin Krens
