3 ms·
So Dragonfly BSD is the WinNT* of UNIX world, interesting! "One big part of the goal set will be the creation of a middle 'emulation' layer which is manag
by frik 13y ago
So Dragonfly BSD is the WinNT* of UNIX world, interesting!
"One big part of the goal set will be the creation of a
middle 'emulation' layer which is managed by the kernel
but runs in userland, which will take over all primary
system call entry points (in userland) and convert them
to syscall messages that the kernel understands. 4.x,
5.x, SysV, Linux, and other compatibility sets will be
moved out of the kernel and into this middle layer."
-- Matthew Dillon (main dev): http://lists.freebsd.org/pipermail/freebsd-current/2003-July/007080.html http://lists.freebsd.org/pipermail/freebsd-current/2003-July...
* think about subsystems like Win32, POSIX, OS/2 of the WinNT series operating system (XP, Vista, 7, 8, Xbox, ReactOS)
- UNIXgod 13y agoNo it's just BSD UNIX proper. quoted from: http://www.dragonflybsd.org/history/ http://www.dragonflybsd.org/history/ "the logical continuation of the FreeBSD 4.x series"
- weland 13y agoNetBSD does that as well.
- 4ad 13y agoAny BSD does that.
- csmuk 13y agoAnd look where it got NT. POSIX gone. OS/2 gone. NTVDM gone (on 64-bit). Ultimately we are left with an abstraction layer which abstracts nothing because Win32 is the base level abstraction for all the other abstractions now. Metro, WP etc run on top of it all like a massive house of cards throwing 0x80004005 around to piss off devs. If you know the difference between Nt and Zw you'll get what I mean :) It's all a big shame because the NT native API[1] and NTFS are absolutely flipping marvelous. Compatibility layers got destroyed by virtualization as well. Whole emulation layer thing was a bad idea for NT and this as well. [1] Totally undocumented other than the leaked Windows NT/2000 source code a few years ago.