News for hackers. Stuff that matters.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by dasil003 on Tuesday August 25, 2015 @12:52AM (#10114670)
The political factors that led to the adoption of Linux as a defacto standard are endlessly interesting to me. As programmers we like to think of ourselves as objective to the hilt, but the reality is that at some point the pragmatic choice is to capitulate to a common standard for the sake of higher-level efforts. In many ways this is purely a political decision because we don't yet see the fallout from the tradeoffs made, and by the time we do it's too late to go back and rebuild the foundations.

We can't go back now and replace UNIX because we've too much invested in it and there's work to be done.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by pjmlp on Tuesday August 25, 2015 @01:39AM (#10114776)
Yet the way I see it there is more OS research going on with unikernels and at Microsoft Research labs than with Linux.

Which appears just to be the same old idea of UNIX and mainframes revamped in new package, stuck in C and in a kernel model that has hardly changed.

EDIT: To clarify.

Many use GNU/Linux in the same way as they would be using UNIX SYSTEM V, there is hardly any change.

Add to it that besides new filesystems, adoption of mainframe virtualization and sandboxes concepts, there is hardly anything new happening in OS research in regards to Linux.

What I currently care about is OS research that tries to mimick the Xerox PARC experiences, use of micro-kernels, use of safe systems programming languages and so forth.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by AnimalMuppet on Tuesday August 25, 2015 @12:33PM (#10117678)
> What I currently care about is OS research that tries to mimick the Xerox PARC experiences, use of micro-kernels, use of safe systems programming languages and so forth.

Why? When was the last time there was a Linux crash due to it not using a "safe" language? How many people did it effect? Is Linux actually measurably any the worse for using an "unsafe" language?

Would Linux be measurably any better for use of a micro-kernel?

Is anybody going to spend the man-decades (or man-centuries) necessary to re-write Linux using micro-kernels or safe languages, just to wind up at the same level of functionality? No. Ain't nobody got time for that.

So unless you can point to concrete, measurable benefits that are going to come from switching to micro-kernels or Rust or whatever, Linux is going to continue on its way. (I agree that the advantages of micro-kernels are a valid research subject. But you need more than Tannenbaum's "that's the right way to do it". You need a compelling reason where it can do something that people care about that Linux can't do, or where it can do it with much fewer resources (either hardware or programmers), or something of that sort. Merely 10% improvement, say, isn't going to cut it, because you'd have to re-write all of Linux to get that improvement, and it's not worth it.)

Re:Why Some Dead OSes Still Matter (2007) [pdf] by pjmlp on Tuesday August 25, 2015 @03:21PM (#10118891)
I will let CVE database speak for me in what concerns security.

Micro-kernels are used in many embedded scenarios nowadays. Even your phone or car infotainment system might be running one, e.g. L4, QNX.

GNU/Linux being a UNIX clone will never change. Using a micro-kernel or any other language instead of C simply doesn't work out in UNIX culture.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by vezzy-fnord on Tuesday August 25, 2015 @05:46PM (#10119669)
MINIX 3, Hurd, DragonFly BSD (hybrid) are existing counterexamples. Amoeba, Sprite and Spring were research Unixes with microkernels.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by pjmlp on Wednesday August 26, 2015 @01:41AM (#10121276)
Actually I see them as examples that failed to change UNIX culture in regards to OS design. Always downplayed by the majority of UNIX users.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by vezzy-fnord on Tuesday August 25, 2015 @01:54PM (#10118334)
Well, you don't need to rewrite all of Linux. What's currently happening is that some subsystems are incrementally being made more accessible from a user context - e.g. a new flag for madvise(2) to make page fault handling in userspace easier, NSUSE to access certain network drivers as userspace libraries, FUSE to cooperate with the in-kernel VFS to get file systems as user processes, virtual consoles outside the kernel and so on.

The demand for microkernel-like features is there, and Linux will progressively be refactored into a hybrid kernel with a standard set of "servers" you plug on top to augment it (systemd appears to be taking the role of the servers in question). Whether this architecture will end up desirable or an awkward worst-of-both-worlds combination remains unclear.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by vezzy-fnord on Tuesday August 25, 2015 @10:13AM (#10116581)
Yet the way I see it there is more OS research going on with unikernels and at Microsoft Research labs than with Linux.

Unikernels are just the logical continuation of exokernels, except designed to run under a bare metal hypervisor. Though still excellent to see libOS taken to its limits, I find the task of actually turning a full workstation operating system into a secure multi-tenant distributed cluster system to be more versatile, as you could then tailor it to both general-purpose and special tasks, libOS being firmly in the latter - deploying applications.

Singularity was great, though it seems to have stagnated.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by pjmlp on Tuesday August 25, 2015 @11:01AM (#10116974)
Singularity evolved into a few other projects, some of them now on .NET.

The compilation of .NET to native code on Windows Phone 8.x with MDIL, and its successor .NET Native, can be traced back to Bartok. The Singularity's AOT compiler toolchain for Sing#.

Microsoft research then went on to Drawbridge, Midori (still classified) and now IronClad.

Then as programming languages that grew out of it there the M# which was mentioned around two years ago and not much more, and Dafny being used by IronClad.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by ben_bai on Tuesday August 25, 2015 @04:05AM (#10115093)
Minix 3 seems interesting. But for the foreseeable future C seems to be the language of choice for OS development.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by silon7 on Tuesday August 25, 2015 @07:05AM (#10115582)
Rust is safe(r) and could be integrate/replace with C incrementally.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by pjmlp on Tuesday August 25, 2015 @07:28AM (#10115693)
In theory yes, but I don't think a UNIX clone will adopt it as such. It is a matter of culture.

Better in other OS that are already researching alternative systems programming languages.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by cmbaus on Tuesday August 25, 2015 @01:37AM (#10114769)
What political factors are you referring to? I think Linux took off because it was easily accessible and widely available, and Linus made a lot of pragmatic choices.

I remember in the 90s how awesome it seemed to get a *nix system for free with a book.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by cturner on Tuesday August 25, 2015 @04:10AM (#10115106)
IBM's investment in Linux was political. For decades, IBM's identity was as a platform company. It was becoming a regular loser outside of its enterprise monopoly. It was late to the party on home computing. It created the PC but still lost control of the platform. It tried to recover with OS/2. It was a pretty good platform but they couldn't get the details right. This was was fizzing as well.

Around 1996 they made a pivot. They invested heavily to recreate themselves as a company who sold services based on Windows NT. This was a desperate move, but it worked - by the late 90s they had reinvented themselves as a services business. One of the stories of the late 90s was the way that IBM had reinvented themselves.

Then, shrewdly, they invested heavily in Linux. At a time, FreeBSD was still a much better platform. But Linux had the GPL behind it. The GPL forces people to release changes. This sabotaged the commercial software market, which IBM had already lost. IBM could continue to charge for services and retain their hardware monopoly. This has hurt competitors who had strong footholds in software but who who were less strong in services (Sun, Oracle).

Re:Why Some Dead OSes Still Matter (2007) [pdf] by AnimalMuppet on Tuesday August 25, 2015 @12:26PM (#10117620)
> It tried to recover with OS/2. It was a pretty good platform but they couldn't get the details right. This was was fizzing as well.

Well, it locked up the PS/2 hardware with patents, so nobody could clone it. So non-PS/2 hardware was a lot cheaper, because there were a hundred companies trying to sell it. But that cheaper hardware didn't run OS/2 (at least initially).

But when Microsoft was able to keep pace (more or less) with Windows, nobody wanted the PS/2, because Windows on commodity hardware was good enough, and less expensive.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by cturner on Wednesday August 26, 2015 @01:12AM (#10121186)

    > Well, it locked up the PS/2 hardware with patents, so nobody could clone it. 
The "IBM Compatible" was already well-established though. PS2 architecture plays were an attempt for them to get relevant again, and it didn't work. The main technology that they had was EISA, and there wasn't much edge from having that.

    > cheaper hardware didn't run OS/2
I don't think that's quite right. A mate had a PS2 that was bundled with OS/2 4 in 1996. We found that the OS/2 install disks that were bundled with his PS2 wouldn't install to other systems. But I never had trouble getting shrinkwrapped os/2 running on commodity ISA or VESA bus hardware - 2.0, 2.1, 3, 4. I ran it as my main desktop for five years. You did have a poor experience if you didn't have a well-supported video card, and almost nothing was well-supported.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by AnimalMuppet on Wednesday August 26, 2015 @04:17PM (#10125727)
I stand corrected.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by cturner on Thursday August 27, 2015 @02:46AM (#10127918)
Had a wake-at-4am. The prop IBM arch wasn't EISA, it was Micro Channel. (thanks)
Re:Why Some Dead OSes Still Matter (2007) [pdf] by mzs on Tuesday August 25, 2015 @03:39AM (#10115035)
I cannot speak for anyone else but personally in college I went linux instead of a BSD on my desk cause the whole AT&T law suit was still pretty murky and frightening to me.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by kragen on Tuesday August 25, 2015 @04:37AM (#10115181)
Yeah, the political factor was that I didn't know anybody who had a copy of Plan 9 to give me, because Bell Labs had a government-granted monopoly on giving people copies of Plan 9. Meanwhile my uncle was sending me SLS disks...
Re:Why Some Dead OSes Still Matter (2007) [pdf] by jimjimjim on Tuesday August 25, 2015 @03:46AM (#10115050)
It was pretty much the focal point and poster child for open source (even before open source was picked up as the phrase to describe the movement). back then it was everybody versus microsoft.
Re:Why Some Dead OSes Still Matter (2007) [pdf] by rbanffy on Tuesday August 25, 2015 @08:03AM (#10115813)
> the pragmatic choice is to capitulate to a common standard for the sake of higher-level efforts.

That's being very objective. Technical merits can only get you so far. One should never be too attached to them.

Re:Why Some Dead OSes Still Matter (2007) [pdf] by dasil003 on Tuesday August 25, 2015 @03:08PM (#10118806)
Sure, but this only gets you to a local maximum because eventually you pass the point where it is objectively worth it to revisit the foundations of computing. This is the downside of human sentience and global communication where we are incapable of exploring different paths in an evolutionary fashion because we know it's not worth it unless a critical mass joins us, and we know a critical mass will never join us on something that is too foundational across existing bodies of work.