osdev   1436

« earlier    

An illustration of why it's hard to port outside code into the Linux kernel
@mjn: "Besides being large, I think what makes me slightly wary of ZFS is that it also has a large interface with the rest of the system, and was originally developed in tandem with Solaris/Illumos design and data structures. So any OS that diverges from Solaris in big or small ways requires some porting or abstraction layer, which can result in bugs even when the original code was correct. Here’s a good writeup of such an issue from ZFS-On-Linux."
zfs  linux  osdev 
1 hour ago by mechazoidal
Interim OS
With "Interim", I try to describe a computer and operating system that takes advantage of modern-day hardware technology while ideally being fully comprehensible in a couple of days. My strategy is to use minimalism and generic, reusable patterns wherever possible while learning from historical, ultimately unsuccessful but valuable attempts like Lisp machines or the operating system Plan 9 from Bell Labs [Pike]. The Interim system is supposed to be a pointer in the right direction, not a perfect blueprint, and a documentation of my own experimental attempts.
lisp  osdev 
7 days ago by athena
dump.mntmn.com/interim-paper/
"Interim is, as the name implies, an experiment of combining the homoiconicity of Lisp (manipulation of symbols), the genericity of Plan 9 (everything is a file system) with the minimalism and hackability of home computers. New languages like Rust [Rust2015], Unikernel systems like Mirage OS [Mirage2015] and hardware designs like lowRISC or the Novena laptop [Novena2015] show that it is absolutely possible to build simpler, more open and safer systems than we take for granted today."

facme: note the "list of 'buffers'" and "list of rectangular 'views'": "the same buffer can be interpreted in different ways: listen to an image, look at graphic structure of text, paint into an audio sample."
But of course contrast that with his view on emacs: it wouldn't need to exist if the OS provided the building blocks for integration.
"I argue that an operating system can be designed as a database of well-formed functions that each do one thing well. The functions can then be composed to form ad-hoc "applications". A requirement for this is that unlike in proprietary/closed/binary designs, all source code must be open and all functions reusable in new contexts. Interim OS includes functional building blocks for text display and editing, and an example development environment written in the Interim language:"
plan9  lisp  osdev  research  facme  pmz  via:mechazoidal 
8 days ago by force
dump.mntmn.com/interim-paper/
(repo: https://github.com/mntmn/interim )
"Interim is, as the name implies, an experiment of combining the homoiconicity of Lisp (manipulation of symbols), the genericity of Plan 9 (everything is a file system) with the minimalism and hackability of home computers. New languages like Rust [Rust2015], Unikernel systems like Mirage OS [Mirage2015] and hardware designs like lowRISC or the Novena laptop [Novena2015] show that it is absolutely possible to build simpler, more open and safer systems than we take for granted today."

facme: note the "list of 'buffers'" and "list of rectangular 'views'": "the same buffer can be interpreted in different ways: listen to an image, look at graphic structure of text, paint into an audio sample."
But of course contrast that with his view on emacs: it wouldn't need to exist if the OS provided the building blocks for integration.
"I argue that an operating system can be designed as a database of well-formed functions that each do one thing well. The functions can then be composed to form ad-hoc "applications". A requirement for this is that unlike in proprietary/closed/binary designs, all source code must be open and all functions reusable in new contexts. Interim OS includes functional building blocks for text display and editing, and an example development environment written in the Interim language:"
plan9  lisp  osdev  research  facme  pmz  2015 
11 days ago by mechazoidal
The BeOS file system, an OS geek retrospective | Ars Technica
From the archives: In the '90s, OS geeks adored BFS's ahead-of-its-time feature set.
filesystem  beos  osdev 
13 days ago by vipom
hard state soft state confusion
"Hard state is what the hardware sees. Most simply, it’s the contents of hardware registers, CPU and other devices, but also includes memory which those registers may point to. Soft state is what the kernel sees, and uses to program and initialize the hardware. Bad things happen when the hard state and soft state don’t agree."
osdev  openbsd 
15 days ago by mechazoidal

« earlier    

related tags

2006  2015  2018  android  arm  aws  beos  blog  book  bsd  c++  c  cloud  commentary  comparison  compiler  concurrency  cs  d_language  database  datastructures  dev  development  documentation  dos  ebook  editor  emulator  facme  filesystem  firmware  foster  freebsd  fun  git  github  graphics  hardware  history  ibm  jk-training  kernel  kj  learning  libc  links  linux  linux_kernel  lisp  low-level  memory  microkernel  microkernels  microsoft  networking  online  openbsd  opensource  operating-system  operating-systems  operating  operatingsystem  os  paper  parallel  pdf  performance  pi  plan9  pmz  postmortem  programming  raspberry  raspberry_pi  raspberrypi  raspi  react  reference  repo:github  research  rust  security  server  system  threads  trie  tutorial  tutorials  uart  unix  uvm  virtual  virtualization  vmm  webassembly  x86  xanadu  youtube  zfs 

Copy this bookmark:



description:


tags: