And the mount, clear, and cat errors are undoubtedly because we didn't say toybox in front of them, which is why we need a bunch of symbolic links. IIRC, at that point, I typed ls, it didn't recognize it, then typing toybox ls worked...
@SweetAIBelle@landley yeah, it's still somewhat broken but it's at least in a booting state where I could see how much #toybox and #dropbear I can squeeze into the rootfs.cpio.xz given the limitations and the fact that it competes with the Kernel [bzimage] for space...
@SweetAIBelle@landley for example I didn't compile the kernel with much driver support and getting at least #IPv4-based #Ethernet support will eat up about 200kB...
But I'd rather have a system that cat at least pull stuff and/or go from there...
getting #tmpfs work and being able to #wget / #curl stuff is a pivotal step...
My kernels configs are not particularly trimmed down, they're "minimal number of symbols". There's a horrible CONFIG_EXPERT menu that lets you switch extra stuff off...
@landley I've refrained from using #CONFIG_EXPERT because I want to avoid fiddling with stuff I don't know much about and would first resort to maxing out #menuconfig [or rather minifying] before I'd resort to harsher tricks like more aggressive options to optimize size.
@kkarhan You saw how mkroot makes kernel configs, right? It creates a microconfig (in two parts), then expands it to a miniconfig, then to a full config...
Espechally since in terms of Hardware it makes more sense to [me to] optimize per-architecture [I've not seen VIA or AMD NICs on an amd64 or arm5r11 system]...
Granted the #i486 version is my primary target since it's the one most desperately in need of something like OS/1337 and I can't commit the time necessary to support more as I've got € 0 in funding so it's not as if I can quit my dayjob to commit fully to it.
@landley But I'd shure that's a matter of time...
After all, there is a demand for easy-to-license #Linux for use in #embedded systems, as #FreeBSD and other #BSD derivates are quite lacking in terms of #drivers and supported hardware compared to Linux.
And I think that OS/1337 can be a more permissive alternative to #YoctoProject and a useable solution to get started developing portable CLI & TUI tools that just run on everything...
Just as "#kevkasrtbt" rescue system it would still be useful.
@landley And for a lot of my projects, a #KISS approach is the way to go, since putting Raspbian / Raspberry Pi OS on the #PocketCrypto would be as absurd as installing CP/M on my TI-30 XS MultiView calculator.
@landley Also I was tempted at first to go with the oldest still maintained kernel (something in the 4.x line I guess) but I think that'll not be worth the sacrifices for OS/1337 ....
Add comment