Oasis: a small statically-linked Linux system
1–10 of 169 posts
Re: Oasis: a small statically-linked Linux system
#2Is "velox" (mentioned in the article) a display server or a window manager?
Re: Oasis: a small statically-linked Linux system
#3it's advertised as "small". how small is that? an Alpine minirootfs is ~2.5 MB tar.gz and ~6.0 MB on ext4 (4k overhead).
Re: Oasis: a small statically-linked Linux system
#4Is "velox" (mentioned in the article) a display server or a window manager?
Window manager I think. Is based on https://github.com/michaelforney/swc that is a Wayland compositor
Re: Oasis: a small statically-linked Linux system
#5Is "velox" (mentioned in the article) a display server or a window manager?
A wayland window manager.
Re: Oasis: a small statically-linked Linux system
#6All README's should begin with some sort of mission statement. What is the goal or reason for the existence of this? I can imagine some, but I am not sure where this is heading.
Re: Oasis: a small statically-linked Linux system
#7This seems to "statically link" binaries in the sense that each program it ships with is a standalone binary. Does anyone know whether it's possible to truly statically link an entire Linux install, in the sense that the whole system is a single statically linked file including the kernel, display manager, web browser, etc so that link-time optimization can deduplicate code across the entire system?
Re: Oasis: a small statically-linked Linux system
#8Would be cool to get a bit of a "why this matters" intro on repos like this. I clicked through the details, but left wondering if I have any potential use for this. Can I compile this onto a USB stick and use it as a throw-away boot Linux for maintenance tasks? Can I cross-compile this for embedded devices? What is the statically-linked advantage here? Not trying to minimize the effort, I would actually love to see more such things, but felt a bit left out as I couldn't figure out why exactly it exists.
Re: Oasis: a small statically-linked Linux system
#9All README's should begin with some sort of mission statement. What is the goal or reason for the existence of this? I can imagine some, but I am not sure where this is heading.
Except that the README of this project answers all your questions. A list of distinctive features and a list of project's principles make up half of the README.
Re: Oasis: a small statically-linked Linux system
#10I'll never use this but it's cool that it exists.