SqueakNOS was a project to build a complete operating system via Squeak. In this way you can quickly hack it. There is a great page about these initiatives here: http://wiki.squeak.org/squeak/5727
Prior to SqueakNOS we implemented this: http://swain.webframe.org/squeak/floppy/ (using Linux and modifying Squeak to work with SVGALib instead of X) in just 900mb inspired in this QNX Demo Disk.
For one, to put retro systems to great use. For another, to keep as much cruft/unnecessary bells & whistles from being present as possible. Just because the space is there doesn't mean it has to be used.
3COM NETBuilder II routers had 2.88MB floppies. I once spent an entire day tracking down a local supplier with a 2.88MB floppy drive and floppies in stock, so we could upgrade the software on a few routers being affected by a Vines/IP bug.
A "1.44 MB floppy" has that capacity for files when formatted with the FAT file system from MS-DOS. The unformatted capacity is actually closer to 2 MB but a proper file system has disk-space overhead for metadata and check sums.
You could have a file system with much less disk-space overhead than FAT, and there are many out there. A demo disk would typically be read-only, and in particular there are some read-only file-systems that are really space-optimised,
Another option would be to treat the disk sectors as a single compressed file which the bootloader decompresses into a RAM-disk image which the OS then boots from, but that would require a bit more than 2 MB of RAM.
It's not 2 mb in particular; honestly, I'd say 4 mb is the practical starting limit once you're into 16/32 bit CPUs — a Mac Plus / Classic would go to 4, for instance, and every speck of memory free under that made a difference in performance. 2 is a nice limit for total system size, as it allows for (as can be seen in QNX) a very capable, flexible OS, while leaving headroom for programs to run.
It is mainly an embedded OS for routers and engine-control units and traffic lights. For that role, it doesn't need a GUI or a desktop or dev tools or a network stack.
So are they part of the "full OS"?
It depends where you stand, and how you look at it.
The Demo Disk contains a lot more than 1.4MB of code. It's more like 3-4MB of code, but that does not mean it is "the full OS".
Exactly my thought when reading the title. I remember it took a bit of time to boot because my floppy drive was glacially slow at seeking, but once there it was incredibly reactive.
As a wow factor it probably comes a close second place to when I got to experience BeOS hands-on (which was like, how is that even possible)
QNX always sounded interesting, until one saw just how much effort the company was going to to prevent people from actually using it. Vaguely recall a story about someone trying to buy 50 licenses from them for a prototype kiosk thing but they wanted something like 1,000 minimum for a reseller account; and that killed the project.
I did some demo projects with QNX in the 90s and I thought it was the best OS ever. Unfortunately trying to license it for use with our company products was a nightmare and after a while I just said the fuck with it.
This brings back memories. I remember marveling at this with my best friend when it came out. I got into BeOS around the same time.
I used to use those ad-supported dial up ISP’s and found one that worked with a standard PPP dialer so I didn’t need their software. I remember carrying around the QNX disk and login info so I could get online with basically any computer.
I used that back when it was current. It was an impressive bit of kit, but TBH, what QNX did on a single floppy made -- and more than ever still makes -- Linux look very very bloated.
Tom's Root-and-Boot just about got you a working command line on one floppy.
For comparison, using FOSS equivalents, QNX got that, plus all of X.org, plus Firefox, onto one floppy.
And if you used the status bar to find your IP address, and went to another machine and put that in a browser's URL box, you found that as well as all that, it was also a live webserver, serving live performance stats to the Internet.
So, kernel, busybox, X server, desktop, web browser AND WEB SERVER on one (very heavily compressed) floppy.
Sadly, the genius who built it died young. Cancer. Fsck cancer.
QNX was (is?) such a great OS. This was my first encounter with a microkernel based OS that actually worked, and well.
If I remember correctly, they were moving towards OSS at some point (or at least toward opening it to a wider community). I had it installed in a VM, did some packaging of open source stuff to QNX (bash and irssi, I think), was fun.
At some point they focused on industry/enterprise and that was the end of that for me, but led me to discover L4 later on, and I still have a soft spot for microkernels.
Indeed. I submitted this partly because I get so very tired of Linux zealots claiming that the HURD "proves" that microkernels can't work, or that Minix 3 shows that, OK, they can work, but they're crippled.
Around 2003 there was a demo CD. This brings up a nice system with a GUI and browser.[1][2]
QNX started closed source with a free version, went open source, went closed source, went open source after an acquisition, and then went closed source when RIM (Blackberry) acquired them. Then RIM dropped the GUI to focus on whatever it is Blackberry still does.
As I once told one of their sales execs, "quit worrying about people pirating your system and worry about people ignoring it". During the first free version period, people were porting open source software such as GCC, Eclipse, and browsers to QNX. With all the licensing changes, the open source community got fed up with QNX and stopped making versions for it.
We used QNX for our DARPA Grand Challenge vehicle. All our desktop machines ran QNX, and we could run the real-time program on them as well as the vehicle. The real time features were so good that we could have the entire real-time vehicle system running, at hard real time priority, and run a browser or compile without missing a time check.
1. Nothing. Someone was writing a QNX-type kernel in Rust. What happened to that? There's L4, but it's too low-level. It's more of a hypervisor. People usually run another OS, usually a stripped-down Linux, on top of L4. QNX offers a POSIX API, so you can run applications directly.
I just remembered that I've been running my desktop machine with `preempt=full` for a while now. I wonder why it's not the default for consumer distros yet.
QNX was a true microkernel architecture that worked, and worked well. The basic building block was called IIRC Send/Receive/Reply: Every "system" call looked like a regular function call, but would "Send" a message to a different process, and (usually) suspend the caller; The other process would "Receive", do whatever was requested, and "Reply", at which point control went back (with the response) to the calling process. IIRC it was also possibly to do async calls, but in that case the other process would call ("Send") the response back, rather than "Reply". I might be confusing this with another system though.
device drivers weren't privileged - they were just another process you called into, and could be restarted in the case of a fault (rather than kernel panic or blue screen).
A system that doesn't provide this is not an alternative to QNX; It's just another operating system (which are all, in some ways, alternative to each other and thus QNX, but ...)
In automotive infotainment systems, where QNX was used a lot in the past, it mostly had been replaced with combinations of Linux or Android on the non-realtime critical systems, and smaller microcontrollers which run realtime OS (OSEK and autosar derivates). The latter are usually not open source.
"Folks, we're just waiting on word back from the tower while our instrument panel blocks to render a thumbnail of the airport. We should be touching down in 30 to INT_MAX minutes or so. In the meantime if you want to sit back and watch a movie on your entertainment panel we ask that you refrain from apt installing the non-free Nvidia drivers which can sometimes cause our landing gear to stick..."
"Folks, we're going to go ahead and uninstall Gnome and see if we can't get on the ground a little earlier. Should be anywhere from 30 to INT_MAX minutes. In the meantime a flight attendant will be coming around with wired keyboards if you'd like to play a free game of Snake on your Entertainment terminals..."
Plan 9 has deadline scheduling out-of-the-box for real-time. It runs on x86-64, 386, Arm v7 and AArch64 (And more): http://doc.cat-v.org/plan_9/real_time/ (mostly obsolete but describes the motivation and implementation)
See proc(3) man page for deadline scheduling (towards the bottom real-time i described): http://man.9front.org/3/proc (I always recommend the actively maintained 9front fork)
The best part is you don't need special patches or libraries. You simply configure the process/group by writing messages to the procs ctl file using the command line, a script, or from within your program.
Lots of unixes have real time scheduling classes (Linux too), comes with the POSIX RT APIs. Is there information somewhere about the real-timeness performance of Plan 9 that could be compared with current general purpose operating systems?
FWIW, Windows is not a true RTOS, but it does get pretty darn close.
The true hallmarks of an RTOS kernel is hard-realtime scheduling usually with round-robin priorities, and support for priority inversion, which is when a low priority process blocks a high priority one, it inherits the high priority temporarily to meet the deadline.
Windows is threads have a priority, with the highest priority thread occupying the CPU - however there's a series of 'hacks' that allow it to emulate real time behavior.
Threads can get a priority boost in some cases, such as the aforementioned priority inversion case, when the user interacts with the program associated with the thread, when the thread hasn't run for a long time etc.
Additionally there's a set of 'real-time' priorities that can preempt all non-realtime priorities and you need admin or kernel access to set this prio level, as these threads will lock up your system because they can't be preempted.
While I wouldn't trust Windows to control an ICBM, but it's good enough at giving resources to user processes so the your UI feels responsive.
this demo cd is my benchmark of how a computer is supposed to feel like. if UI interactions are in any way slower than what this provides (on, say, 2008-era hardware), it's basically poop
I was using it at that time as my main desktop OS. I ported and wrote several tools of it. The gui itself was simple, nice to use and to program for.
Driver support wasn't extensive, but the available drivers were working fine. With qnxstart.com at the time and all the oss tooling I didn't have anything missing.
I was in love in a way that only beos gave me before.
This was the last commercial/closed-source OS I ever used in no small part due to the license change.
The final fate of self-hosted QNX was super unfortunate, and poor decision making on the part of RIM/Blackberry. QNX completely dropped support for self-hosted QNX Neutrino development after 6.5 [0], and stopped distributing installation media ISOs with 6.6/7.0. Instead you needed to develop everything on macOS/Windows/Linux hosts, make custom specialized images using their published BSPs (Build Support Packages).
So no neutrino hosted compiler toolchain, no desktop. Oh yeah, they also completely killed off their full GUI desktop, the Photon microGUI in QNX 6.6. There was even a working port of Mozilla Firefox to it at some point. You could use all this freely with a hobbyist/non-commercial license in the early 2000s.
As a casual outside observer, it seems to me that dropping self-hosted support was a very sensible move. They probably didn't want to spend resources on PC hardware support, particularly for laptops. And of course, a developer's PC doesn't just run development tools; it also has to handle things like connecting to VPNs and being manageable by company IT departments. Some people need accessibility accommodations (e.g. screen readers, magnifiers, or alternative input methods), and there's no reason to assume that this group doesn't (or couldn't) include some developers of niche embedded systems. The list goes on and on. Even desktop Linux doesn't do a great job on all these things, never mind a niche OS like QNX. So doing cross-development from Windows or macOS makes a lot of sense.
Edit to add: Just had a scary thought. What if Red Hat and whoever else is actually spending money on desktop Linux development applied the same logic to desktop Linux itself that I retroactively applied to self-hosted QNX? After all, non-developers don't use Linux, right? (I'm speculating that they'd make that assumption, not saying it's actually true.) And developers can work with Linux by connecting to a remote machine or running a VM on a "normal" (i.e. Windows or Mac) computer. Is there enough economic incentive to keep maintaining and improving desktop Linux that this won't happen? The death of desktop Linux wouldn't actually hurt me, as I mainly use Windows, but I'd still be sad.
> dropping self-hosted support was a very sensible move. They probably didn't want to spend resources on PC hardware support, particularly for laptops.
Self-hosting support doesn’t require PC hardware support. You totally can run your toolchain in a VM (every developer using WSL on Windows is doing it). In the past, I’ve put development environments in Docker containers - it makes it easier for people to get started, and on Windows or macOS that’s a VM too.
Making a system self-hosting is exposing it to a broader range of use cases which can help shake out bugs, limitations and performance issues which other use cases don’t. Even if you don’t strictly need it, I still think it is a good idea to maintain that support (even use it in your CI) unless doing so becomes unjustifiably expensive.
> As I once told one of their sales execs, "quit worrying about people pirating your system and worry about people ignoring it".
That's a very frequent comment about tech companies with underperforming sales.
This is how ARM leapfrogged MIPS around 2010. Their licensing was basicaly "you are buying a USB stick". MIPS on other hand was "pre-pay us $100k just to have our attorney to take a look on if we can sell to you"
In those "deep" tech companies, it's absolutely not unusual to have sales staffed by people with zero background knowledge, but nevertheless star sales professionals.
I interviewed at Panasonic years ago due to their in car info systems using QNX.
Also, Coca-Cola’s kiosks for drink selection uses QNX.
In both cases, they’re using Qt instead of Photon.
Photon was just about perfect as a GUI architecture IMHO, although I don’t know if it could have handled an alpha compositing as well as it handled blit stuff across a network connection.
I love how this gets rediscovered by people every few years :)
I still have a floppy set somewhere. I loved it. I ran it in a 486 IBM all in one I had with a compatible NIC for a long time as a conversation piece and guest light surfing machine. Amazing how well it ran up till fairly recently when standards outstripped its browser too much
I still have the Pentium box I used to run it on. Was that really 20+ years ago? How did that happen... I should boot it up and see how well frogfind.com works.
I was there at the time. I just amuse myself digging up obscure, mostly-forgotten languages and OSes and posting them on HN to blow the kids' minds. :-D
Hurd is still stuck using Mach, unfortunately. The issues from the Hurd critique paper haven't been addressed either.
Minix, as cool as it is, does not have a maintainer, and hasn't seen activity for years. There's a lot of out-of-tree work that's just sitting there. It is a shame, because it is a really cool system architecture.
Genode is a modern, proper multiserver OS that has a good architecture, frequent releases and quite solid overall direction. And it has POSIX compatibility, so a lot of software runs, including modern web browser engines.
Back when QNX was distributed on floppy, my work locked down their computers so that I couldn't dial out to the internet. So I booted up the QNX off the floppy and was browsing within minutes. My boss walked in on me browsing the internet and I nearly got fired over it. He was worried because he thought he might get in trouble for it. Once I explained how it worked, he was less worried.
It was amazing that they could fit a semi-functional browser on a floppy.
In high school I'd extensively used Windows from 3.1-98se, Linux (Debian, Mandrake), and dabbled a ton with BeOS and QNX (hampered from making either my main OS only by software support).
BeOS and QNX (Photon) were my two favorite desktop experiences of the bunch. They were so much better than the others—yes, very much including Linux. And BeOS was even at least as "friendly" and polished as Windows was at the time.
Here we are and neither's on the desktop and their closest modern equivalent that is prevalent is probably macOS, which is... fine as a consolation prize, I guess, but I still wish I could see a world where either of those made a real splash in the desktop world (I know QNX wasn't really trying to, but man, it performed so much better as a desktop OS than Windows or Linux).
For quite a while, watching 1997 BeOS demo brought tears to my eyes. It was so sweetly designed in every way. Maybe except the regular multithreading issues. Even the source code, at least the small bit I saw [0], was utterly brilliant.
[0] part of the FS query language, so you could select/filter through file metadata for free.
Do you have experience running Haiku and if so what's the current hardware story like? IOW, could a reasonably determined person get it running as a daily driver on a modern laptop?
Well a lot had to be configured especially for non-standard hardware. But generally it was far more stable and snappy than Windows. Also constant reinstalling and rebooting wasn't necessary. The QNX demo was nice but to be fair you couldn't do much with it unless you wrote your own software I guess...
There was a very short window of time around 2000 when BeOS was viable as a main OS, at least for a high school kid like me. I think I even got rid of Windows entirely and just had a single BeOS partition for a while. It was sooo fast on my little eMachines computer, which was such a breath of fresh air after having hand me down 386s and such that struggled to boot Windows. The only real trouble I remember was the network stack was kind of buggy and had to be restarted every now and then and I think printing was pretty non-existant.
Likewise, between 1996 and 1999 I used BeOS as my main driver and I felt like a smug time-traveller from the future walking amongst the rubes. “One Processor Per Person Is Not Enough”: how prescient they were! I knew they were right from the first moment I read their slogan.
I have extremely fond memories of using BeOS as a main driver OS back in the late nineties (‘96-‘98/‘99). First I had a BeBox (dual 603e-133MHz) and later a dual PIII-300MHz. The former was definitely my favourite hardware platform (‘exotic’ RISC architecture combined with das blinkenlights) while the latter far outclassed it once I finally sorted out the video-card driver issues). An absolutely splendid experience. To this day I still adore the chiselled looks of NeXTStep and BeOS GUIs from the period, but the added colourful “Nintendo-esque” elements of BeOS graphic design attracted me. Oh and the movable yellow tabs across the windows! I was also getting into amateur astronomy and there was a 3D starchart application that utterly awed me. I never knew that sitting in my bedroom in mid 1998 with a BeBox planning an astrophotography shot while Enigma’s Return To Innocence blaring in the background would become the high water mark memory of my late adolescence.
Apple macOS, IBM AIX, HP-UX, the 2 old SCO OSes, and -- oddly -- IBM z/OS.
But no, UNIX is very much not generic, and I generally find Linux people get very upset when I call it a UNIX. Which it is, but even 29 years on, people still think that "Unix" means "based on AT&T code".
Band-Aid, Bubble Wrap, Aspirin and many alike aren't generic either, but we use them as generic names. The same applies to Unix. Nobody means "V7 UNIX" or "Only OS implementations that conform to Open Group's standards" when they say "Minix is a Unix". They just mean "conforming to the original Unix design philosophy, as in file system structure, command-line tools, and process management". As I understand, Open Group's approval's just corporate politics to get permission for using the term "Unix" in marketing materials for enterprise customers, nothing else.
You can argue all you want that Minix (the most popular Unix in existence) or Ubuntu (most popular Linux distro in existence) aren't Unix. They're Unix. They're probably more Unix than most Unices on that list. Some company owning the brand and enforcing some arbitrary licensing scheme doesn't change that.
Look, I personally agree with you, and >1 Linux distro has passed the certification, which means that, strictly and precisely, Linux is a UNIX. (However that means that FreeBSD, NetBSD, OpenBSD and DragonflyBSD technically are not UNIX.)
But that is not what the mainstream industry takes it to mean.
Whereas terms like xNix are, I submit, well understood.
162 comments
[ 4.5 ms ] story [ 212 ms ] threadPrior to SqueakNOS we implemented this: http://swain.webframe.org/squeak/floppy/ (using Linux and modifying Squeak to work with SVGALib instead of X) in just 900mb inspired in this QNX Demo Disk.
TBH, even now, 900 meg isn't very impressive. ;-)
http://209.68.14.80/ref/fdd/formatKB2880-c.html
You could have a file system with much less disk-space overhead than FAT, and there are many out there. A demo disk would typically be read-only, and in particular there are some read-only file-systems that are really space-optimised,
Another option would be to treat the disk sectors as a single compressed file which the bootloader decompresses into a RAM-disk image which the OS then boots from, but that would require a bit more than 2 MB of RAM.
I can't help but to find the min-max of everything. Well at least fantasize about what could be.
The full OS was a ~100MB download:
https://archive.org/details/qnx-neutrino-rtos-x86-runtime-ki...
But it depends what you define as "the full OS".
It is mainly an embedded OS for routers and engine-control units and traffic lights. For that role, it doesn't need a GUI or a desktop or dev tools or a network stack.
So are they part of the "full OS"?
It depends where you stand, and how you look at it.
The Demo Disk contains a lot more than 1.4MB of code. It's more like 3-4MB of code, but that does not mean it is "the full OS".
How they did it: http://web.archive.org/web/20011106140711/http://www.qnx.com...
As a wow factor it probably comes a close second place to when I got to experience BeOS hands-on (which was like, how is that even possible)
I used to use those ad-supported dial up ISP’s and found one that worked with a standard PPP dialer so I didn’t need their software. I remember carrying around the QNX disk and login info so I could get online with basically any computer.
I never hear about QNX anymore, so this is def a blast from the past.
Juno? Netzero?
The 4.0 version works perfectly, 2.2.26 kernel though which was released in 1999
Discussed before here https://news.ycombinator.com/item?id=28515025
http://www.toms.net/rb/
Tom's Root-and-Boot just about got you a working command line on one floppy.
For comparison, using FOSS equivalents, QNX got that, plus all of X.org, plus Firefox, onto one floppy.
And if you used the status bar to find your IP address, and went to another machine and put that in a browser's URL box, you found that as well as all that, it was also a live webserver, serving live performance stats to the Internet.
So, kernel, busybox, X server, desktop, web browser AND WEB SERVER on one (very heavily compressed) floppy.
Sadly, the genius who built it died young. Cancer. Fsck cancer.
https://openqnx.com/node/298
Except it’s not really ALL of X, and the browser is more like IE2 in capabilities…
For a more fair comparison, where QNX wins in terms of absolute size, but Linux wins in terms of functionality, there’s muLinux: http://micheleandreoli.org/public/Software/mulinux/
If I remember correctly, they were moving towards OSS at some point (or at least toward opening it to a wider community). I had it installed in a VM, did some packaging of open source stuff to QNX (bash and irssi, I think), was fun.
At some point they focused on industry/enterprise and that was the end of that for me, but led me to discover L4 later on, and I still have a soft spot for microkernels.
QNX started closed source with a free version, went open source, went closed source, went open source after an acquisition, and then went closed source when RIM (Blackberry) acquired them. Then RIM dropped the GUI to focus on whatever it is Blackberry still does.
As I once told one of their sales execs, "quit worrying about people pirating your system and worry about people ignoring it". During the first free version period, people were porting open source software such as GCC, Eclipse, and browsers to QNX. With all the licensing changes, the open source community got fed up with QNX and stopped making versions for it.
We used QNX for our DARPA Grand Challenge vehicle. All our desktop machines ran QNX, and we could run the real-time program on them as well as the vehicle. The real time features were so good that we could have the entire real-time vehicle system running, at hard real time priority, and run a browser or compile without missing a time check.
[1] http://toastytech.com/guis/qnx621.html
[2] https://archive.org/details/qnx_momentics_6.2.1
2- What tech stack (language) you used for those challenges?
3- Your idea on Lisp (for these applications)?
2. C++. Here's the source code. [1]
3. No.
[1] https://github.com/John-Nagle/Overbot/
Look into Genode.
Why? No hope for real RT? (Or otherwise more generally due to the GC?)
SeL4 with CAmkES, or Genode.
Huge TCB being the main one.
i.e. The code that needs to be trusted. For Linux, it includes the whole kernel, and it is huge.
device drivers weren't privileged - they were just another process you called into, and could be restarted in the case of a fault (rather than kernel panic or blue screen).
A system that doesn't provide this is not an alternative to QNX; It's just another operating system (which are all, in some ways, alternative to each other and thus QNX, but ...)
I know an RTOS does not guarantee smooth desktop performance but I just would love to try it out to compare.
"Folks, we're going to go ahead and uninstall Gnome and see if we can't get on the ground a little earlier. Should be anywhere from 30 to INT_MAX minutes. In the meantime a flight attendant will be coming around with wired keyboards if you'd like to play a free game of Snake on your Entertainment terminals..."
Plan 9 has deadline scheduling out-of-the-box for real-time. It runs on x86-64, 386, Arm v7 and AArch64 (And more): http://doc.cat-v.org/plan_9/real_time/ (mostly obsolete but describes the motivation and implementation)
See proc(3) man page for deadline scheduling (towards the bottom real-time i described): http://man.9front.org/3/proc (I always recommend the actively maintained 9front fork)
The best part is you don't need special patches or libraries. You simply configure the process/group by writing messages to the procs ctl file using the command line, a script, or from within your program.
The true hallmarks of an RTOS kernel is hard-realtime scheduling usually with round-robin priorities, and support for priority inversion, which is when a low priority process blocks a high priority one, it inherits the high priority temporarily to meet the deadline.
Windows is threads have a priority, with the highest priority thread occupying the CPU - however there's a series of 'hacks' that allow it to emulate real time behavior.
Threads can get a priority boost in some cases, such as the aforementioned priority inversion case, when the user interacts with the program associated with the thread, when the thread hasn't run for a long time etc.
Additionally there's a set of 'real-time' priorities that can preempt all non-realtime priorities and you need admin or kernel access to set this prio level, as these threads will lock up your system because they can't be preempted.
While I wouldn't trust Windows to control an ICBM, but it's good enough at giving resources to user processes so the your UI feels responsive.
Driver support wasn't extensive, but the available drivers were working fine. With qnxstart.com at the time and all the oss tooling I didn't have anything missing.
I was in love in a way that only beos gave me before.
This was the last commercial/closed-source OS I ever used in no small part due to the license change.
So no neutrino hosted compiler toolchain, no desktop. Oh yeah, they also completely killed off their full GUI desktop, the Photon microGUI in QNX 6.6. There was even a working port of Mozilla Firefox to it at some point. You could use all this freely with a hobbyist/non-commercial license in the early 2000s.
[0] http://www.qnx.com/developers/docs/7.0.0/index.html#com.qnx....
Edit to add: Just had a scary thought. What if Red Hat and whoever else is actually spending money on desktop Linux development applied the same logic to desktop Linux itself that I retroactively applied to self-hosted QNX? After all, non-developers don't use Linux, right? (I'm speculating that they'd make that assumption, not saying it's actually true.) And developers can work with Linux by connecting to a remote machine or running a VM on a "normal" (i.e. Windows or Mac) computer. Is there enough economic incentive to keep maintaining and improving desktop Linux that this won't happen? The death of desktop Linux wouldn't actually hurt me, as I mainly use Windows, but I'd still be sad.
Self-hosting support doesn’t require PC hardware support. You totally can run your toolchain in a VM (every developer using WSL on Windows is doing it). In the past, I’ve put development environments in Docker containers - it makes it easier for people to get started, and on Windows or macOS that’s a VM too.
Making a system self-hosting is exposing it to a broader range of use cases which can help shake out bugs, limitations and performance issues which other use cases don’t. Even if you don’t strictly need it, I still think it is a good idea to maintain that support (even use it in your CI) unless doing so becomes unjustifiably expensive.
That's a very frequent comment about tech companies with underperforming sales.
This is how ARM leapfrogged MIPS around 2010. Their licensing was basicaly "you are buying a USB stick". MIPS on other hand was "pre-pay us $100k just to have our attorney to take a look on if we can sell to you"
In those "deep" tech companies, it's absolutely not unusual to have sales staffed by people with zero background knowledge, but nevertheless star sales professionals.
edit: poking around https://archive.org/details/software?query=qnx
The only issue was the file system and driver support - if it crashed there was not good recovery tools.
Also, Coca-Cola’s kiosks for drink selection uses QNX.
In both cases, they’re using Qt instead of Photon.
Photon was just about perfect as a GUI architecture IMHO, although I don’t know if it could have handled an alpha compositing as well as it handled blit stuff across a network connection.
I still have a floppy set somewhere. I loved it. I ran it in a 486 IBM all in one I had with a compatible NIC for a long time as a conversation piece and guest light surfing machine. Amazing how well it ran up till fairly recently when standards outstripped its browser too much
I need to rebuild my Ccmp collection. I ended up selling or giving it all away due to having to move. sniff
I ran a NeXTstation Turbo Color as my daily driver up till around 2010. Me and some friends ported over newer line and what not for openstep 4.2.
33mhz 040 with 128mb of 60ns EDO RAM, SCSI HDD. Amazing what you could do with adequate performance on that.
Also ran a BeOS r5 system with massive amounts of hacks and updates for way longer than was really reasonable lol
So snappy and smooth compared to Windows 3.11 on the same 2MB 386.
https://github.com/bluewaysw/pcgeos
0. https://www.genode.org
Minix, as cool as it is, does not have a maintainer, and hasn't seen activity for years. There's a lot of out-of-tree work that's just sitting there. It is a shame, because it is a really cool system architecture.
Genode is a modern, proper multiserver OS that has a good architecture, frequent releases and quite solid overall direction. And it has POSIX compatibility, so a lot of software runs, including modern web browser engines.
It was amazing that they could fit a semi-functional browser on a floppy.
BeOS and QNX (Photon) were my two favorite desktop experiences of the bunch. They were so much better than the others—yes, very much including Linux. And BeOS was even at least as "friendly" and polished as Windows was at the time.
Here we are and neither's on the desktop and their closest modern equivalent that is prevalent is probably macOS, which is... fine as a consolation prize, I guess, but I still wish I could see a world where either of those made a real splash in the desktop world (I know QNX wasn't really trying to, but man, it performed so much better as a desktop OS than Windows or Linux).
[0] part of the FS query language, so you could select/filter through file metadata for free.
You know, I think he was right.
The rule of thumb is if FreeBSD supports it then Haiku will, as a number of important drivers were ported from FreeBSD.
That makes perfect sense for that period, the Linux desktop experience was, well, not atrocious, but definitely left things to be desired.
I'm pretty sure it's not much better now but hardware's powerful enough to make that less-painful.
thanks for the reminder!
Novell donated the trademark to them when it bought Bell Labs in 1993.
1 Linux is currently a registered UNIX™: Huawei EulerOS
https://www.opengroup.org/openbrand/register/brand3622.htm
Formerly Inspur K-UX was, too:
https://www.opengroup.org/openbrand/register/brand3617.htm
You can view the list here:
https://www.opengroup.org/openbrand/register/
Apple macOS, IBM AIX, HP-UX, the 2 old SCO OSes, and -- oddly -- IBM z/OS.
But no, UNIX is very much not generic, and I generally find Linux people get very upset when I call it a UNIX. Which it is, but even 29 years on, people still think that "Unix" means "based on AT&T code".
You can argue all you want that Minix (the most popular Unix in existence) or Ubuntu (most popular Linux distro in existence) aren't Unix. They're Unix. They're probably more Unix than most Unices on that list. Some company owning the brand and enforcing some arbitrary licensing scheme doesn't change that.
But that is not what the mainstream industry takes it to mean.
Whereas terms like xNix are, I submit, well understood.
It is certainly one solution.
As I recall, it was quite a long time after Linux was a thing that someone trademarked the name and donated it to the LF.
It always seemed too "big" (too capable, too complex, too pricey) for my projects so I never took it for a spin.