Minimal requirements?

[sphaero]

Great project! I've always wondered if it would be possible to run a BeOS userland on top of Linux. I know this is a big effort!

I was wondering what would be the minimal system requirements to running this. Haiku already is very lightweight which makes it very snappy on all systems. I've done projects where we would target the very first RPI as minimal required system. This forced us to keep the code very lean and mean. The idea behind it was also to be able to use older hardware to reduce the e-waste problem.

So long story short. What would the minimal target for VitruvianOS be? Is 32bit even considered?

[ave4]

I'm currently working on armv7 support. I should be finishing up a PR soon. I'm also planning to develop a lightweight, atomic Vitruvian distribution based on Alpine, or even LFS. Support for 32-bit x86 and arm will be a must.

[ave4]

The GUI on my AllWinner A33 with 512 MB of RAM works pretty well, but it needs some performance optimization. Especially the Tracker, but that seems more like a bug.

[sphaero]

Ow man great! You also answered my next question. I would suggest something like buildroot as opposed to LFS but that's nitpicking. I would definitely try Alpine.

I would surely like to help!

[ave4]

It would be nice to do some performance profiling. In my opinion, the GUI in Vitruvian is currently slower than in Haiku.

[Numerio]

I think this is early and useless work right now, some stuff is intentionally limited for now to avoid creating debugging problems (e.g. thread priorities are not set). We need to be patient, I have been working on that for years and when it will be time I will unleash all performances.

[sphaero]

I'm still working my way through the build and the source to see if it appeals. I'm on Void but it doesn't build yet. Here are my steps if anyone is interested:

xi binutils-devel squashfs-tools zlib-ng-devel xorriso ninja mtools linux-headers\
 libwebp-devel eudev-libudev-devel tiff-devel libpng-devel libopenexr-devel\
 ncurses-devel libjpeg-turbo-devel libinput-devel libicu78-devel libicns-devel\
 giflib-devel freetype-devel libfl-devel elfutils-devel libdwarf-devel grub-x86_64-efi\
 git flex ninja elfutils dkms debootstrap cmake base-devel bison automake autoconf \
 libseat-devel libbacktrace libevdev-devel libblkid-devel libgomp-devel

cmake -DBUILDTOOLS_MODE=1 .. -GNinja
cd ../generated.x86/ && ../configure
[1/2030] cd /home/arnaud/src/Vitruvian/generated.x86/src/s...usr/bin/cmake -E echo Nexus\ will\ not\ be\ built\ locally
Nexus will not be built locally
[2/2030] Running utility command for nexus
FAILED: [code=127] src/system/kernel/nexus/nexus/CMakeFiles/nexus.util 
cd /home/arnaud/src/Vitruvian/src/system/kernel/nexus && /usr/bin/cmake -E echo Building\ nexus-dkms\ package... && bash -c dpkg-buildpackage\ -uc\ -us && bash -c mv\ ../nexus-dkms_1*\ /home/arnaud/src/Vitruvian/generated.x86
Building nexus-dkms package...
bash: line 1: dpkg-buildpackage: command not found
[11/2030] Building CXX object src/libs/agg/CMakeFiles/agg.dir/src/agg_vcgen_contour.cpp.o
ninja: build stopped: subcommand failed.

I think I need to move to a debian container.

[ave4]

dpkg-buildpackage: command not found

Comment out these lines https://github.com/Numerio/Nexus/blob/248db2ea0d843ed68461e8069dcb62877a5096b1/nexus/CMakeLists.txt#L40
Build nexus manually using make.

[sphaero]

Yep, it builds and loads:

[349668.184236] nexus: loading out-of-tree module taints kernel.
[349668.184247] nexus: module verification failed: signature and/or required key missing - tainting kernel
[349668.190220] nexus: loaded

thnx

[Numerio]

FYI you can pass the BUILD_LOCAL_NEXUS var to CMake.

[Numerio]

Great project! I've always wondered if it would be possible to run a BeOS userland on top of Linux. I know this is a big effort!

I was wondering what would be the minimal system requirements to running this. Haiku already is very lightweight which makes it very snappy on all systems. I've done projects where we would target the very first RPI as minimal required system. This forced us to keep the code very lean and mean. The idea behind it was also to be able to use older hardware to reduce the e-waste problem.

So long story short. What would the minimal target for VitruvianOS be? Is 32bit even considered?

Base system requires (boot with only DE running) around 500MB. We are thinking of some 32bit support but it's still unclear exactly how.