News for hackers. Stuff that matters.
Re:Incompatible Timesharing System by fiddlerwoaroof on Saturday January 23, 2021 @11:44PM (#25889349)
Has anyone attempted to port these pre-Unix oses to modern hardware?
Re:Incompatible Timesharing System by gumby on Sunday January 24, 2021 @03:45AM (#25890429)
Remember ITS was written in assembly language for the PDP-10, a 36-bit machine with an 18-bit address space (yes, it was also intended to run Lisp efficiently). It was a fun machine to program in assembly code, emulatable on a 64-bit machine sure. But not something you would "port" to a different architecture.
Re:Incompatible Timesharing System by musicale on Sunday January 24, 2021 @05:35PM (#25896899)
I bet you could write a translator to convert PDP-10 code to x86 code or something.

You could also probably rewrite it manually.

Re:Incompatible Timesharing System by klyrs on Saturday January 23, 2021 @11:55PM (#25889403)
I found some here https://www.inwap.com/pdp10/emulators/

> This is the 5,376th access to this page.

Hope we don't hug it too hard

Re:Incompatible Timesharing System by fiddlerwoaroof on Saturday January 23, 2021 @11:59PM (#25889430)
I know about emulators, but I’d think someone would have found porting ITS or Multics to x86 or Arm a fun hobby project
Re:Incompatible Timesharing System by unused0 on Sunday January 24, 2021 @01:14AM (#25889787)
Multics was co-developed with the hardware; that hardware contains Multics specific features that are needed to implement Multics. Segment tables, Rings, Gates and more. enable the memory mapping and protection that that is the basis of Multics.

These hardware features are not found in the current gamut of architectures due to the dominance of the marketing value of being the fasted CPU; these features lower the CPU throughput and also cost valuable silicon space, and the economic value of a secure OS is less then the value of being faster or shinier.

Re:Incompatible Timesharing System by gpderetta on Sunday January 24, 2021 @04:26AM (#25890606)
Being fast is hardly a marketing feature. X86 had gates, segment tables and rings (still fully functional in 32 bit mode, so having them is not an hindrance on being fast). They got dropped in 64 bit mode because no software has used them in 25 years.
Re:Incompatible Timesharing System by corty on Sunday January 24, 2021 @06:17AM (#25891123)
Having them wasn't a hindrance, luckily for intel. But using them to the full extent was far slower than not. E.g. call gates as a syscall mechanism have a far higher overhead compared to int80. Segments, when used in the intended finer-than-page granularity are also too slow, because changing a segment register often is very costly in terms of cache and TLB flush. That's why everyone just used a few fixed segments that almost never changed and did the interesting stuff with page-based memory management.
Re:Incompatible Timesharing System by rbanffy on Sunday January 24, 2021 @12:13PM (#25893660)
> They got dropped in 64 bit mode because no software has used them in 25 years.

I think there was one that used them, but i can't remember its name. Maybe someone here can help.

It was obscure enough that Intel didn't think too much about removing them.

Re:Incompatible Timesharing System by gpderetta on Sunday January 24, 2021 @02:03PM (#25894718)
IIRC Segments were used to speed up (para?) virtualization, before built-in support in the ISA.

Segment registers are also used as thread pointer, but that special case is still supported even in 64 bit mode.

Re:Incompatible Timesharing System by rbanffy on Sunday January 24, 2021 @03:49PM (#25895850)
I was talking about the rings. I remember something that used them.
Re:Incompatible Timesharing System by gpderetta on Sunday January 24, 2021 @10:44PM (#25898811)
I think NT at some point run drvers and some other subsystems in lesser privileged rings than ring 0. Not sure if this was dropped in later versions.
Re:Incompatible Timesharing System by rbanffy on Monday January 25, 2021 @06:07AM (#25901890)
IIRC, NT 4 moved drivers into kernel space for performance. The result was that the system crashed much faster :-P.
Re:Incompatible Timesharing System by Jkvngt on Sunday January 24, 2021 @01:30AM (#25889834)
Here's hoping that state level and non state actors make a huge mess of everything we have now so everybody can sit in the corner and have a big think.
Re:Incompatible Timesharing System by sbierwagen on Sunday January 24, 2021 @05:28AM (#25890889)
I'm not sure about that? Chip-level security functions forcing cache flushes seem like they would be ripe for Meltdown/Spectre-style attacks.