interim

sp, and some kind of convertor so SBCL can run Interlisp. You now have an x86-64 LispM, with a whole new architectural model: no files, no disks, no filesystem. It's all just RAM. Workspace at the bottom, disposable. OS and apps higher up where it's nonvolatile. I fleshed this out a bit here: https://archive.fosdem.org/2021/schedule/event/new_type_of_c... And here... https://www.theregister.com/2024/02/26/starting_over_rebooti...

gine it encapsulated by some special Smalltalk context object or something. > There's something very appealing about these "turtles-all-the-way-down" environments where all of the objects in the system are live and can be inspected by using a REPL, and how system behavior can be changed on-the-fly. I am of the belief that a whole new personal computing system -- from the hardware on up -- designed around these principles would be of great benefit to all. It would run directly counter to the current culture of computing, which says that there are developers and users (scribes and plebs!) and nothing in between. In fact, the people who had the greatest qualitative input into the development of personal computing specifically thought that users would be programmers, and therefore programming would need to be something a bit different than it had been up until that time, and so would the computing environment and all the rest (some of these people invented Smalltalk). The major impediments to doing such a thing are time, money, and worldview. Most developers today, or "computer people" who should presumably be in the know, likely aren't very familiar with, if at all, these environments. There is a very ingrained idea about "how things should be done" that is mistakenly equivocated with "how things have to be done." There is also limited funding for these endeavors. The business world is not set up to make these kinds of leaps these days (short-termism and shareholder primary have dominated enterprize thinking since the late 70s). I've said before on here that FOSS is also not the solution: you need long periods of time and lots of money to make something like this (as history shows), and people doing things in their free time isn't going to cut it. Case in point: FOSS is for the most part premised on Unix, because that's what was around and available for free when the movement started. All "new OSes" are some form of Unix because it is impossible for people to think outside of that context given the limited resources available to them. I will end this rant (sorry) with a couple of refs. The first is to the CogNOS project, which was at one point an effort to get the OpensmalltalkVM running on bare metal [6]. I do now know the current status. The second is to Lukas Hartmann's Reform laptop project. Notable for being an entirely open hardware and software platform, he began the project because he wanted to build a custom machine for his own Lisp OS called Interim [7]. When I last asked him about it, he said that he still has a goal of getting Interim to run on the machine. But, of course, it's taken him years of work to even get to the point he's at now. [1] http://wiki.squeak.org/squeak/slang [2] https://en.wikipedia.org/wiki/OMeta [3] http://wiki.squeak.org/squeak/4878 [4] http://scg.unibe.ch/research/helvetia/petitparser [5] https://github.com/SmaCCRefactoring/SmaCC [6] https://github.com/nopsys/CogNOS [7] https://github.com/mntmn/interim

orking is more dynamic as provided by rfork[2] where you can give a child a specific subset of your process's namespace. So you could make a child who can only see specific files, executables, or resources and make it so that the child can't mount, unmount, etc. [1] Interim OS: https://github.com/mntmn/interim [2] http://man.cat-v.org/9front/2/fork Some cool manuals: - http://man.cat-v.org/9front/1/bind - http://man.cat-v.org/9front/1/ns - http://man.cat-v.org/9front/3/proc - http://man.cat-v.org/9front/5/intro