3 ms·
I have honestly started to look at your comment feed. Seriously, how the hell do you hold this much arcane (but amazing!) knowledge in your head?
by chris_wot 11y ago
I have honestly started to look at your comment feed. Seriously, how the hell do you hold this much arcane (but amazing!) knowledge in your head?
- vezzy-fnord 11y agoHeh, I'm flattered. I recall we left a rather bitter taste in each other regarding the systemd question (speaking of which, you never got back on my paper). It's really nothing special. Copious amounts of time coupled with an interest in system software research that motivates me to read research papers, dive into project wikis and the like. If you'd like to discuss things further, just reply affirmatively and I'll send you an email.
- chris_wot 11y agoI was quite depressed at the time, I can only apologise for my tone. I've started to read your piece, but I've honestly been interrupted constantly so haven't been able to give it my full attention, which I intend to do as soon as I can! My disagreement with you over systemd, incidentally, never had anything to do with my assessment of your abilities. It was pretty obvious we both have technical skills :-)
- nickpsecurity 11y agoBoth he and I realized that there's lots of answers to modern problems in those old papers, as history repeats a lot in IT. The field has a problem of passing wisdom down to next generations or just generalizing solutions. The constraints and OS/hardware competitiveness also made lots of inherently interesting solutions to problems that you're unlikely to see re-appear outside of embedded or special-purpose. Fun stuff to read. If interested, Timeline of Operating Systems is a good start. Just pick summary of anything major (minus DOS's) and dig into references if it interests you. https://en.wikipedia.org/wiki/Timeline_of_operating_systems https://en.wikipedia.org/wiki/Timeline_of_operating_systems The capability systems were also forward-thinking with much modern work on OOP, isolation, etc slowly reinventing its methods. Easy extension plus strong security/reliability were their thing. https://homes.cs.washington.edu/~levy/capabook/index.html https://homes.cs.washington.edu/~levy/capabook/index.html Here's a paper vezzy-fnord shared with a lot of nice examples with features that defined future work and some still ahead of modern systems: http://brinch-hansen.net/papers/2001b.pdf http://brinch-hansen.net/papers/2001b.pdf Lots of old stuff that still beats modern, mainstream stuff on key metrics. Hopefully, you'll dig into some of it and enjoy the "arcane" stuff yourself. It's arcane, but sometimes awesome too. :)
- chris_wot 11y agoOh, when I say "arcane" it's not a criticism :-) and a little tongue in cheek, I Lo e stuff like this. Hell, I'm reviewing x86 segmented real mode at the moment, just because I can. I'm the last one to criticise someone for doing deep dived into technical material!
- nickpsecurity 11y agoOh, I knew you liked the arcane stuff: it's why I replied. :) Real mode I don't have as much on but segments are powerful in right hands. Even on Atom, they do in 2 cycles what paging isolation takes 8 to do. Called "descriptors" in capability book I referenced so definitely check that out or the dedicated chapter on descriptor architectures. The high-assurance GEMSOS kernel used segments when ported to Intel 286: http://aesec.com/eval/NCSC-FER-94-008.pdf http://aesec.com/eval/NCSC-FER-94-008.pdf Note: Mainly see design, layering, and assurance activities. The most modern use of them is CHERI processor and CheriBSD at Cambridge. https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-864.pdf https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-864.pdf Note: Paper references quite a few past uses of them in detail. A great, modern example in software is Code Pointer Integrity (see 2014 paper link): http://dslab.epfl.ch/proj/cpi/ http://dslab.epfl.ch/proj/cpi/ So, there you go for tonight. Have fun. :)