Three days and nobody mentioned TempleOS? If attempting to build The Third Temple in the form of an OS isn't niche and exotic, I don't know what is. 🤣
this post was submitted on 20 Jul 2024
107 points (93.5% liked)
Linux
47151 readers
1359 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
For anyone unfamliar:
TempleOS (formerly J Operating System, LoseThos, and SparrowOS) is a biblical-themed lightweight operating system (OS) designed to be the Third Temple prophesied in the Bible. It was created by American programmer Terry A. Davis, who developed it alone over the course of a decade after a series of manic episodes that he later described as a revelation from God.
Davis began developing TempleOS circa 2003. One of its early names was the "J Operating System" before renaming it to "LoseThos", a reference to a scene from the 1986 film Platoon. In 2008, Davis wrote that LoseThos was "primarily for making video games. It has no networking or Internet support. As far as I'm concerned, that would be reinventing the wheel". Another name he used was "SparrowOS" before settling on "TempleOS". In mid-2013, his website announced: "God's temple is finished. Now, God kills CIA until it spreads [sic]."
Davis died after being hit by a train on August 11, 2018.
TempleOS was written in a programming language developed by Davis as a middle ground between C and C++, originally called "C+" (C Plus), later renamed to "Holy C", possibly a reference to the Holy See. It doubles as the shell language, enabling the writing and execution of entire applications from within the shell. The IDE that comes with TempleOS supports several features, such as embedding images in code. It uses a non-standard text format (known as DolDoc) which has support for hypertext links, images, and 3D meshes to be embedded into what are otherwise standard ASCII files; for example, a file can have a spinning 3D model of a tank as a comment in source code. Most code in the OS is JIT-compiled, and it is generally encouraged to use JIT compilation as opposed to creating binaries. Davis ultimately wrote over 100,000 lines of code for the OS.
From Wikipedia
This is at the very least super interesting.
Red Star OS!
Is Alpine Linux obscure? Well, using it as a desktop is obscure, I guess. The decision to use musl libc is the main limiting factor for desktop usage, but thanks to the existence of runtime package managers like flatpak and/or static linking, you can run basically anything that requires glibc on Alpine these days (at the expense of extra disk usage for glibc libs).
If you don't know much about Alpine, it is an extremely lightweight Linux distro designed primarily for containers and virtualization, that ships with busybox and musl libc. It's basically the closest you can get to GNU/Linux without the GNU. The main appeal to me is the simplicity of the tooling and installation, it's the only Linux distribution I've used that gives me a similar vibe to OpenBSD. The defaults are almost perfect, but the first thing I would do when installing it is install the docs metapackage (otherwise you have no manpages), and optionally replace busybox with coreutils and friends (personally can't stand how non-posix compliant busybox is). I'd also replace the default busybox ash shell with a nice kornlike such as oksh, a clone of the OpenBSD shell.
I had PostmarkedOS, which is Alpine with some extra phone stuff
We need more arm packages..
I like TailsOS, which is an amnesiac system that runs entirely in RAM and boots from a USB hard drive. The goal for the operating system is to be a safe operating system for people who are in compromising situations - from international reporters to survivors of domestic abuse, it is a way to highly reduce your ability to be tracked.
The downsides of amnesiac systems are obvious - without enabling the setting for permanent storage, effectively everything you do on the OS is lost every time. And if you do enable persistent memory, well, that's not exactly entirely safe if you are caught out.
What I like the OS for though is as someone who is not compromised or in a situation where I need these privacies (despite appreciating them), my usage of it makes it safer for others who are using it (since internet is through Tor), and I feel more comfortable using computers in the wild when needed, since I'm not logging in on the public operating system that will be used by everybody else.
Many people give these projects flack or diminish their values as a "daily driver", but I think often times forget the important aspects of them. They may not be a daily driver for you or I by nature of our needs, but they are certainly important daily drivers for others. In addition to that, supporting a project that helps people in compromised situations and becoming another node to bounce off of (again, Tor, not inherent to the usage of this OS) is a nice additional benefit.
Tl;DR amnesiac operating systems because they're simple, straightforward, and make you feel more like whitehat hackerman when you've done nothing at all.
hannah montana, nuff said!
RebeccaBlackOS
Not niche, but surely exotic: NixOS, a distribution that is configured via a purely functional language. There is no such thing as installing or uninstalling packages, you add or remove things from your configuration and then simply apply that configuration.
I really wanted to like NixOS (and I do, theoretically), but I couldn't dedicate more than 5 full days over Christmas to learn how to get to a working development system.
May I ask what the issue actually was? Was it about "working system" or about "working development system"?
I don't recall needing more than two days for getting a system up and running for the first time, and in fact it worked so well that I switched all my machines to it by now; granted, I have changed a lot about the configuration ever since and there seem to be a lot of paths to take in the beginning and it's not always clear which one to take. But getting a working system, even one suited for development (personally, I'd recommend a nix development shell for that), shouldn't really take that long.
Working development system. I got quite far, but after so much work, became very frustrated when a VSCode plugin wouldn't work properly because it needed (and assumed) read/write access. I didn't want to have to manage and think about every little plugin I experimented with at the OS level.
For me, the main blocker was just getting my head around the concept of it, as it seems like such a wild idea for a distro. I still don't think I'm 100% there, but I have enough down now to cobble a working system together at least.
It's very good for servers. I wouldn't use it on desktop.
I think it could be good for something like an office, where it might be beneficial to have everyone on an identical setup that's immutable so they can't mess with it, and can (presumably) be duplicated by just copying a config file.
I assume the con would be that if something breaks in an update, it probably breaks for everyone. But by the same token, the solution should fix it for everyone too.
Using it on all my machines (desktop and notebooks), can't really complain – but then again, couldn't really complain about Arch either
I couldn’t even get the installer to work. Tried a couple times but it just wouldn’t install so I gave up on it - still want to try it though
You can manually install it
view more: next ›