| Hurricane hierarchically clustered OS implemented on Hector multiprocessor; manages system resources in clusters, using tight coupling within clusters, loose coupling across clusters. Succeeded by Tornado. |
| Institute_for_Distributed_Systems__IVS Researches distributed and realtime operating systems, communication, software engineering. Part of Department of Computer Science at the Otto-von-Guericke-University of Magdeburg. Some information on |
| MIT_LCS_PDOS Parallel and Distributed Operating Systems Group; research focus: extensible and flexible system services: filesystems, networking, languages. Projects: 'C, Chord, Click, Exokernel (Exopc), Grid, Prol |
| MOSIX_Clusters_of_Surplus_Computers_for_Providing_Common_Network_Services_and_Applications Details active project to illustrate use of MOSIX to create clusters of surplus machines that can be used to provide network services, application resources. |
| Plan_B_Operating_System An operating system that lets applications be built simpler. The system selects and combines resources from the network semi-automatically. |
| Quarks Simple, yet efficient distributed shared memory (DSM) system; a user-level library plus header files supports DSM on groups of Unix workstations. Runs on 4.3BSD/M68k, HP-UX/PA-RISC, IRIX 5.2/MIPS, Sun |
| Sprite Distributed OS gives one system image to/over a networked cluster of workstations, research project, Berkeley, John Outerhoust group; high file system performance via client and server caching, proces |
| SUMO Support for Multimedia in Operating systems, Lancaster University: microkernel OS with facilities to support distributed realtime and multimedia applications and ODP-based multimedia distributed appli |
| The_V_Distributed_System Research OS for a cluster of computer workstations connected by fast network; structured as a small distributed kernel, and set of service modules, runtime libraries, and commands. Stanford University |
| V_Operating_System Growing article, with links to many related topics. Wikipedia. |
| WebOS Gives distributed OS services needed to build applications that are wide-area, highly available, incrementally scalable, dynamically reconfiguring, with mechanisms for: resource discovery, global name |
| YouOS Allows running diverse programs in web browser, integrated program development and management, based on HTML and JavaScript. Descriptions, FAQ, weblog, forum, developer support, tutorial, policy, cont |
| The_Brave_New_OS_of_the_Future Brief, simple layman's treatment of Carnegie Mellon University Odyssey project; IBM Research's Autonomic Computing initiative; Microsoft Farsite project. [CNN.com] (February 13, 2002) |
| Ericsson_Erlang/OTP Commercial support for Erlang/OTP (Open Telecom Platform) under Solaris, NT, and VxWorks. |
| Erlang_Forum Erlang Forums used from discussions on Erlang, OTP, and aspects of concurrent functional programming. |
| Erlang_Mailing_List Erlang questions list and archives. |
| Erlang_Programming_Language Growing article, with links to many related topics. [Wikipedia] |
| Erlang_Projects Site allowing members to participate in Erlang related projects, share documents, and add resources of interest to others. |
| Erlang_Service_Architectures A White Paper comparing the architecture of web applications written in Erlang with those using the Open Source LAMP stack (Linux, Apache, MySQL/Postgres, Perl/Python/PHP/Ruby) and an enterprise Java |
| Erlang__The_Movie Erlang, as they tried to market it in an internal video from 1993. |
| Erlang_Training_and_Consulting_Ltd_ Offers Erlang/OTP training courses at all levels, seminars, consulting services and code reviews. Based in London, its consultants and trainers are available for long and short term jobs worldwide. |
| Erlang_Wiki Home of the Erlang Wiki |
| erlang-fr_org English page of French Erlang site, a few interesting articles. |
| The_Great_Computer_Language_Shootout_-_Erlang A benchmark of Erlang test programs vs other languages. |
| Planet_Erlang A site with Erlang related RSS feeds. |
| Trap_Exit A one-stop place where to find Erlang information, including forums, documentation, tutorials and chats. |
| Wiki A Wiki site developed in Erlang with news and discussions about Erlang/OTP. |
| Commands_Reference_with_Versions,_Syntax,_Notes,_and_Examples Index, description, and syntax, of all built-in commands available in all versions of DOS/Windows since v1.00. |
| Doctor_DOS_Betamax;_DOS_Operating_System Commentary, tutorials, references, Power-Users' Corner, for DOS and related utilities. |
| DOS Growing article, with links to many related topics. Wikipedia. |
| Georgos_the_DOS_compatible_operating_system A free DOS-compatible operating system. Site includes sample applications, discussion forum, and development information. |
| IBM_Corp_ Makes PC DOS 2000; was one of the two original DOSes for the IBM PC. Now year 2000 compliant, and updated for a new century. Preserve your investment in DOS applications. |
| PC_DOS_for_Embedded_Devices Retooling of IBM PC DOS for use in embedded systems. |
| PhysTechSoft_Ltd_ Makes PTS-DOS 2000: network support, file manager, archiver, internal boot virus protection, graphical web browser; email, telnet, FTP clients; many utilities, some for embedded system development. |
| RealDOS A barebones DOS alternative. |
| RMF-DOS Reduced Memory Footprint; goals: match functions of MS-DOS 6.22, IBM PC DOS 7.00, DR-DOS 7 subset. Written mainly in 2 free C compilers and assembler, most parts are smaller uncompressed than compress |
| Shell_Tips Blog covering useful tips for a number of command line interfaces including the DOS shell. |
| Turkish_Rational_DOS The core of DOS compatible operating system that is currently under development. |
| Unofficial_PTS-DOS_FAQ In English and German languages; with wiki, downloads, links. |
| ZDOS Realtime, 32-bit replacement for 16-bit DOS, with modern features: multitasking, demand paging, SMP. Coded in pure Assembly language. Zebor Technology. |
Interview with Matthew Dillon of DragonFly BSD posted by Eugenia Loli-Queru on Sat 13th Mar 2004 09:07 UTC 
Today we feature a very interesting interview with well known *BSD hacker Matthew Dillon over his latest project, DragonFly BSD (also known for his Linux kernel contributions, Amiga C compiler hacking back in the day and the Backplane distributed database). Matthew discusses DragonFly's status, goals, the overall BSD platform, innovation, and more. Update: Added one more question at the end of the Q&A.
1. Please tell us about the general status of DragonFly BSD.
Matthew Dillon: The project has been going very well. We've primarily been focused on the 'guts' of the system during this initial period, and you can get a fair idea of the work that has been accomplished so far by looking at the Diary page on our site.
Most of the work so far has been to operating systems internals. The
work has been a combination of new work, like our light weight kernel
threading core, plus selective backports from FreeBSD-5 to keep the
system's device drivers up to date (e.g. such as the USB subsystem).
From a userland perspective we have maintained a FreeBSD style
environment, so DragonFly basically runs everything that FreeBSD-4.x
can run. The packaging system probably won't be done until the second
release so we are at the moment leveraging off of FreeBSD's ports system
for user apps. Everything you'd expect of a BSD system (X, mozilla,
etc) is available to DragonFly users.
The first release is slated for some time in mid-June, hopefully
before the USENIX Technical Conference. That will be the 1.0 release.
We've been fairly careful to maintain as high a level of reliability
as possible during development and I think we've done a pretty good job
meeting that goal. The first release is intended to be more of a
technology showpiece then an integrated end-user platform.
2. Are you using any bits and pieces from FreeBSD-5, or you only strictly importing/exporting to FreeBSD-4 codebase?
Matthew Dillon: DragonFly began as a fork off of FreeBSD-4, because that was the most
reliable starting point and because we wanted to do major core pieces
of the system quite differently from the direction FreeBSD-5 took. For
example, we are focused on more of a compartmentalized threading model
to scale to SMP rather then the mutex model that FreeBSD-5 has chosen
to use. But the FreeBSD-4 codebase is of strictly limited utility as
a source of new code and maintainance updates. FreeBSD developers
are doing nearly all new coding in the FreeBSD-5 branch.
So, basically, we are doing the major core pieces of the OS differently,
such as our significantly evolved threading and messaging subsystems,
but we are also maintaining a FreeBSD-5 compatible (or mostly compatible)
device driver API in order to be able to bring in all the excellent
device driver work that has gone into FreeBSD-5. It's simple logic,
really... we don't have the manpower to be able to accomplish both
our infrastructure goals *AND* be able to maintain pace with new PC
hardware at the same time. This methodology allows us to proceed on
both fronts by focusing our own new work on the infrastructure and
bringing in FreeBSD-5's device driver work. This isn't to say that we
don't do some of our own DD work, but the vast majority of it is
take from FreeBSD-5 by design.
3. What is the primary goal of dragonfly, servers or desktops?
Matthew Dillon: Both. When it comes right down to it the idea of targeting a system
to the 'server' is simply another word for 'reliability and scaleability',
and the idea of targeting a system to the 'desktop' is simply another
word for 'out of the box GUI'. It's not really an either-or deal.
All UNIX systems, including Linux, the BSD's, DragonFly... basically
use the same desktop components so supporting a desktop environment
comes down to being able to provide integrated solutions that work out
of the box.
It is extraordinarily difficult to make GUIs work out of the box on
PCs due to the wide variability in hardware and peripherals, but at the
same time technology has continued to progress over the years towards
standards that actually make this easier to accomplish. At some point
the standards going in one direction will meet the software going in the
other and systems such as Linux and the BSDs (including DragonFly) will
be able to approach the out-of-the-box compatibility that took Microsoft
billions of dollars of development to accomplish. It isn't a matter of
if, it's a matter of when.
4. Do you eye the embedded systems market at all?
Matthew Dillon: It is not a focus. We fully intend to make DragonFly operate in
64 bit environments such as the AMD64 (which is also compatible with
the Intel's latest 64 bit announcements even though Intel doesn't like to
admit it), but embedded systems are already very well served by
Linux and NetBSD and we would prefer to focus on technology rather
then platform ports. FreeBSD-5 has had a difficult time supporting
the half dozen or so platforms they are trying to work with and I doubt
we would fare any better, so I am not even going to try. Eventually, if
DragonFly becomes popular enough, embedded systems ports will probably
happen, but it's probably several years down the line.
5. How big is the DragonFly team currently? Are you happy with the development pace?
Matthew Dillon: Very happy. The main kernel@ mailing list has 241 people subscribed
to it as of now and I have handed out 9 commit bits, with another dozen
or so people submitting patch sets outside of that. We have a good
spread of developers focused on different subsystems. For example,
Jeffrey Hsu is focused on threading the network stack while Joerg
Sonnenberg has been focused on the PCI bus and ATA disk driver subsystems,
which frees me up to be able to focus on technological infrastructure such
as the threading subsystem. It's about at the limit which I can sustain
and still have time to do significant programming myself, in fact!
Table of contents"Interview with M.Dillon, Page 1/2""Interview with M.Dillon, Page 2/2" 
(0) 26 Comment(s) Related Articles 
Unlocked Cell phones Cell Phones in Canada OSNews Privacy Statement | Notice to Bulk Emailers © 1997-2008 OSNews LLC. All Rights Reserved. OSNews and the OSNews logo are trademarks of OSNews. Source Code © 2007-2008, Adam Scheinberg Reader comments are owned by the poster. We are not responsible for them in any way. All trademarks, icons, and logos shown or mentioned in this web site are the property of their respective owners. OSNews.com uses icons from the Tango Project and FamFamFam. Reproduction of OSNews stories is permitted only with explicit authorization from OSNews. Reproductions must be properly credited. var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");document.write(unescape("%3Cscript src="http://www.osnews.com/story.php?news_id=6338/" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); 