Domain: utah.edu
Stories and comments across the archive that link to utah.edu.
Comments · 688
-
Re:OSkitOops. Although the link I gave you would take you there (google search), I copied and pasted out of the wrong browser window. Stupid me.
Here is the real link just in case....
--
Garett -
Re:You need libc5 (like from RedHat 6.2)
Under Mandrake, I recall a "compat-glibc" or "campat-libc5" package. I don't remember seeing them under Mandrake 8.0, but under 7.x, they were there.
I'd say install the older rpms first, then install the newer ones with 'rpm -ivh' .. shouldn't be any problems after that.
I had some of the same binary incompatibilities when I upgraded this notebook from mandrake 7.2 to 8.0 .. quite a few problems in fact. A few recompiles and some old libraries installed fixed everything. Needless to say, I'm not installing Mandrake 8.0 on a production machine.
BTW- Nice to see someone from the UofU.
-- -
Re:"Mach is a bad microkernel implementation".. HOWill someone please attempt to assert or refute, using some kind of solid logic or numbers or something, the statement that microkernels are a good idea but Mach is a bad implementation of that idea? What is done wrong in Mach, and can it be fixed?
I don't know enough of the Mach internals to know exactly why it's such a poor performer, but I have read alot of theories put forth. The most common(and accepted) reason is that Mach's memory management is too abstract and that because Mach is built on a hardware abstraction layer. Those two reasons are directly interrelated.
The Hardware abstraction layer(HAL) restricts the u-kernel to operation on a "generic machine". Everything is abstracted in the sense that the HAL contains the units which are common to all CPU architectures. This was done to improve portability. However, it sacrifices a great deal of performance because alot of issues are platform dependent. Things such as page size must be dictated by the architecture you are running on. But because Mach uses the HAL to abstract this away, Mach performance suffers a great deal in memory operations. Often, the HAL dictates a page size which is too small/large for the architecture. The hardware can't handle address translation anymore, so the kernel has to do this manually. This is very expensive.
In general, Mach's architecture just seems poorly designed from what I've read. Alot of research has been done on this topic, and they're coming to the realization that u-kernels are inherently non-portable. That's a very important point. This shouldn't be surprising either because the u-kernel is so small that mostly only platform dependent code end up in there. L4 is 12k, Eros is 32k(I think), VSTa is around 50k and QNX is less than 10k!
The good thing about this approach is that most(if not all) of the platform-dependent code is wrapped up in the u-kernel. The rest of the system is completely portable. So all you have to do is re-write about half of a 20k kernel for the new architecture, and you're done! Re-compile and off you go. Theoretically at least. ;-)
If mach is, indeed, a bad implementation of the microkernel, what would be a *good* implementation of the microkernel? Are any well-designed microkernels out there?
Good u-kernels that have implementations with performance comparable to or exceeding Linux:- QNX: Everyone's heard of this one. They have a very good u-kernel.
- Opearting Systems Group at Dresden: They do alot of great work with u-kernels. They have code for L3 and L4, the first very promising, high-performance u-kernels(though they may not have designed them). They even have Linux running as a service on top of L4, so you may be able to run it right now! Also see This University and the L4KA page for other implementations of L4(ie. other architectures).
- Eros: EROS is a new operating system based on the architectures of earlier high-security capability systems(KeyKOS). Very promising and has performance comparable to L4. The measurements are in the papers section(usually towards the end of the paper). System is GPL'd.
- VSTa: a cool GPL'd hobby u-kernel system(in that it has no university or company backing). This one has a somewhat complete system, ie. self-hosted with gcc, vi, emacs, etc. Runs on a windows partition and uses GRUB to boot(all of which you'll need to run it). No performance metrics that I'm aware of.
- Fluke: No working system as far as I know. The kernel is complete and some performance measurements have been made. Looks promising and source is available(GPL I think).
If there are, then what is it that repeatedly leads projects like xMach/HURD/OS X/mkLinux to embrace Mach as opposed to one of the competing microkernels?
I have no idea. Ignorance of their existence probably.
Unless i am quite confused, supposedly, because the interaction between the microkernel and the OS is somewhat abstract, you ought to be able to replace the microkernel with a better one as long as the interface is the same. Is there any reason a better microkernel with the same software-side interface as Mach could not be written, and used to replace mach?
Yes you could. But then you'd just have Mach. :-) You might be able to engineer the Mach implementation a little better, but having the same interface for the most part means making the same tradeoffs, and then all you'll have left is a bastard child of Mach. *shudder* ;-)
someone once told me that Mach has the ability to host multiple kernels on the same machine at the same time. Is this true? How does that work in terms of sharing the hardware? How do you go about doing this?
Yes that's true, but not in the way you're thinking. Both kernels don't run as kernels at the same time. A well-engineered u-kernel is so thin and provides such a minimal interface to the hardware, that by just slightly modifying Linux(or other kernel) you can get it to run on top of the u-kernel like any other application, and it could do everything that Linux does running on the bare hardware. See L4Linux, MkLinux, Darwin/MacOS X and even this xMach project as examples. The key to good performance is to provide as small a u-kernel with as minimal an interface as feasible to avoid performance problems. It will never run as fast as on bare hardware, but you can get pretty damn close.
I am just thinking that at this point, it would be an utterly useless but nifty parlor trick to try to get Mac OS X/Darwin, MkLinux, xMach and HURD running off the same mach microkernel on the same machine at the same time.
Not so useless as you might think. The problem with any new operating system or kernel is software. There's nothing written for it yet. But what if you could run the Linux kernel on top of your new OS? You'd have near instant access to whatever drivers and applications are currently available for Linux without any porting effort! (except for the initial Linux port) Then you can have a complete system and start writing native drivers for what you need.
-----
"Goose... Geese... Moose... MOOSE!?!?!" -
Re:What prior work?The link doesn't seem to be working, but I think this is the right site. FLASK is what started all of the SELinux stuff, and was a joint project between NSA, some private company and a university in Utah. Any general search on FLASK will turn up a bunch of stuff...
For the Goatse overloaded: http://www.cs.utah.edu/flux/fluke/html/flask.html
-
Re:P. J. Plauger
P. J. Plauger [was] using buddy-system programming at Whitesmith's. The original reason was lack of seats, but the surprising result was better productivity than when both bodies had access to keyboards and screens.
This happened back in the 1970s, and was written up in Constantine on Peopleware. (See also "Strengthening the Case for Pair-Programming" (Google text version). -
Re:What's the point?
The biggest point is that this will save enormous amounts of electrical power that can be used elsewhere.
Sutherland's work is nothing new. The Computer Science department at the (a department he founded) has been working on this for years as well. They have made significant progress.
I know, I worked with one of the professors for a while before I went into electrical engineering.
Just 'cuase the British government can't make it work does not mean it is impossible. Many inventions we use every day were considered "impossible".
Remember that since you don't know about the research, perhaps there is something you don't know.
-
The TCL / TK codeThe TK code is quite excellent. It is bare bones vanilla C, but it is written in a clean OO style. Lots of useful comments, very consistent style and usage. Very portable code. Lots of good stuff.
I haven't looked at the code in four years, though. It may have degraded since, I believe, it has a lot more authors now than it did at that time.
Of course, all the code I work on (for example, the Janos Java NodeOS) looks great, too.
-
Whimsical gene names.The gene has been affectionately nicknamed "I'm Not Dead Yet."
Geneticists, especially Drosophila ones, have a long history of giving genes interesting names.
Several years ago, the Annals of Improbable Research had a story writing contest where the objective was to write a short story using only the names of genes, for instance, like the one below:
In the LOT behind CLUB ETHER-A-GOGO, AMY PRUNE's BREATHLESS TORSO was SPLAYED in the GRAVEL. Her CROOKED-NECK was BENT over the STONEWALL in an ABRUPT TWIST. Her REFRINGENT THRONG was DISHEVELED and her WHITE-MOTTLED MINI UPTURNED . But no COPPER would ARREST the DERANGED KILLER-OF-PRUNE. No CELL would HOLD-UP that HEARTLESS SNAKE. For a SHOTGUN had REDUCED OSKAR's BIG-BRAIN into STARDUST and FAINT-LITTLE-BALLS.
Every single one of the capitalized words happens to be a real name of a Drosophila gene. -
Definitive explanation of color vision
A lot of comments here reflect a somewhat, uh, uninformed view of color vision. I was going to write up a little summary, but then decided to try my Google skills out.
I came up with this definitive article on Color Vision by Peter Gouras. It's very deep, with a special focus on the neurology of color vision.
Another potentially interesting link is the Color Vision Q&A from Rochester Institute of Technology.
What's especially fascinating to me about color vision is that it still isn't fully understood. The low level parts, such as rods and cones, and even some of the "early vision" parts of the brain, have been studied for a while now. However, there are lots of higher level brain activities that are still quite mysterious. As such, making color photographs "match" across computer screen, print, video, etc., is still a subjective art, claims of rigor in "color management solutions" notwithstanding. -
Salt Lake City, Utah
There's gotta be someone out there...
Oh yes, and I made a slash site for University of Utah students. (for those interested, find me there.)
-
Locomotion VR DevicesThere are actually several VR devices that permit locomotion in Virtual Environments. The most basic being a treadmill type device. Military researchers have also developed small "two-way" treadmills that permit locomotion in both longitudinal and lateral directions. The University of Utah developed a locomotion interface called the Treadport that provides longitudinal motion, but also provides haptic (force) feedback to the user. The person walking on the treadmill is attached to a translational robot arm that serves the purpose of pushing and pulling to simulate the force of gravity on sloped surfaces. Inertial forces are also simulated with this device.
For more info: The Utah Treadport
-
Nice VAXnote
Nice note. I wanted to make a similar comment but you did a better job than I could.
Todays new grads laugh about VAX/VMS without really knowing what it is. Yes it is CISC, but with the limitations of the day CISC looked like a good idea. As a person who has spent many all-nighters coding away in ASM without a macro-assembler, CISC does not look too bad. I suspect that many (most?) people who laugh at the VAX have never written assembly outside of a homework assignment or two.
It is sad to see the end of the VAX. I use Unix 'cause I can understand it; VMS documentation takes two bookcases. But I have seen VMS wizards (here is one, in the glasses) at work and you have to respect a VAX in the hands of a master.
The loss of the VAX represents a loss of knowledge, and it is sad.
-
Great stuff
Since these "plastic lasers" can be made in the form of a film or "microdiscs" (of which over 6000 can fit in a single inch) the uses for these are amazing - they can be used for display devices such as monitors or even as optical switches and transmitters for computer circuits.
But since it appears likely that the plastic laser will be able to produce light with smallers wavelengths than conventional lasers it also means a jump in the potential for storing data using the same techniques as CDs and DVDs. A smaller wavelength means a greater density is possible, which is always a good thing.
More information can be found here.
-
some slashcode sitesI don't know of any other open-sourced sites (this is the point of your post). I don't think that website code is as likely to be under the GPL because it typically isn't distributed. If someone comes up with good code, the don't distribute it, they use it on their own website.
Anyone with a little perl knowledge can go a long way towards making a slashcode site into a customer support, file download, or of course a news and events website.
Anyways, here's the slashsites in case anyone is interested.
- Media-Mixer
- RadioTiki
- ipv6news.org
- PRIME Wrestling
- Knowledgerush
- High Performance Hunting
- marketseat.com
- ExtraCrispy.Net
- YourOfficeGeek
- ITCouncil
- Morrissey Solo
- The Cedar Valley Linux Users Group
- EastVan
- earthDot
- meepdot
- Love9
- MedMeta
- jazz-flute.com
- jazz-sax.com
- SigKill
- University of Utah College of Engineering Computing Facility
- Mr. Lego
- FuelCellTalk
- Portland Geekly News
- The Golden Horde Network
- use Perl;
- MacSlash
- bottomquark
- We Have No Product
- TQY3
- gildot
- Tar Heel State Online
- SlashHosting (Hosting for Slash sites)
- slashhost (Hosting for Slash sites)
- IDM Newsbase
- gosports.org
- Anime Station
- NetGAMES
- OnTopofIT
- Web Crush
- HairyPALM.com: The PDA InfoQuarters
- Myworkflow.com
- Techdirt.com
- Be Route (French)
- Yourtown CLN
- DNS Policy
- BarraPunto (Spanish)
- isrec.org
- AbsolutChaos
- Extreme XL Linux News
- Spam Roaster's Club
-
Flux OS Kit
You might want to check out. http://www.cs.utah.edu/flux/oskit/
From the home page:-
The OSKit is a framework and a set of 31 component libraries oriented to operating systems, together with extensive documentation. By providing in a modular way not only most of the infrastructure "grunge" needed by an OS, but also many higher-level components, the OSKit's goal is to lower the barrier to entry to OS R&D and to lower its costs. The OSKit makes it vastly easier to create a new OS, port an existing OS to the x86 (or in the future, to other architectures supported by the OSkit), or enhance an OS to support a wider range of devices, file system formats, executable formats, or network services. The OSKit also works well for constructing OS-related programs, such as boot loaders or OS-level servers atop a microkernel.
I haven't used it so I cannot comment personally on its usefulness, but there does seem to be some interesting projects using it.
-
Re:File extensionThe naming sounds like a tribute to Terry Pratchett. Vorbis and Nanny Ogg are characters in his Discworld series.
Actually, if you look at the Xiphophorus names and logos page, you'll see that they explicitly state:
The Ogg project has nothing to do with the common surname 'Ogg'. Nor is it named after 'Nanny Ogg' from the Terry Pratchett book _Wyrd Sisters_.
"Ogg" actually comes from Netrek. I think that's pretty cool, since I used to play Netrek. They've actually got a couple of things with "Ogg" in the name. There's Ogg Vorbis, and Ogg Squish. I think they should make something called "Ogg Base". (okay, lame Netrek joke)
...
Vorbis, on the other hand is named after the Terry Pratchett character from the book _Small Gods_.
Incidently, that page also has an explanation of their logo. That's Thor apparently, not Jesus or a picture of RMS from back when he was Mr. Universe... -
Oops. Appendum needed...Something got mistyped, and so some links got messed up. (So I'll make the list bigger!)
Things people should be trying out include:
Several of these are pretty UNIX-like, albeit taking some extra "twists," while others are distinctly not like UNIX.Even if you look at these, and go back to a UNIX-like system, there is benefit to seeing the extra abstractions they offer.
-
Re:architecture
If it's based on a Mach microkernel, then it ought to run on a variety of platforms, once all the driver support is in place. Since most new Macs are based on PCI and AGP, and thus have a lot of crossover with PCs in the hardware they have in them, it should be a relatively quick port to other platforms... and I'm sure there'll be plenty of interest.
-
Another genetic science resource.This one at Universtiy of Utah.
-
Re:NachOS...
I've taken an OS course using NachOS and then took an Advanced OS course using Linux. I found that a big problem w/ NachOS (being a simulator) is that it was difficult to tell the difference between the hardware and the OS. You could go in there, and mess with the simulator to get around problems that a normal OS would have to deal with. This was a big problem. Also, the scope of NachOS is very limited, so that when you switch to a "real" OS like Linux you have to re-learn everything the right way... not always that much fun. Linux is well enouch documented, and the kernel is small enough (except for device drivers
:)) that's it is a good OS to start with. Another interesting OS for research and education purposes is called FluxOS. It is a completely modular Operating System, which means you can take any component out and substitute one of your own w/ no dependencies (that's definitely not true of Linux). It is also meant as a reserach/education OS so it is very very very well documented. In 5-6 hours you can learn the basics well, and in a week you could be a FluxOS god. FluxOS uses components of other Open Source OSs such as Linux, FreeBSD, NetBSD, but it wraps them with code that makes them modular.
Link to FluxOS project
There's a link. The only big drawback is that you can't really benchmark with it (you can't do that with NachOS either) because it's non-standard. -
Adesso
I started having some minor pain, and got an Adesso <http://www.adessoinc.com/> keyboard (the MCK-208 Tru-Form sans touchpad [picture]). It's great, and I've since gotten one for home as well. It cost me all of $40 US at http://www.warehouse.com/
The great thing is that is has all the keys in the normal places (the 6 is on the left side, BTW), and none of those stupid internet keys like the MS keyboards.
--
Dave <drr@chpc.utah.edu> -
Yet another mole to whack
I know that everybody and his mother has a mirror for DeCSS, but here's mine anyway. http://www.cc.utah.edu/~rdj5
-
Mirror sitesMandrake's site is swamped right now. The official list of mirror sites is here. The ones listed as doing hourly updates are:
- ftp://mandrake.mudspace.com/pub/linu x/mandrake (Michigan, USA) ++
- ftp://ftp.math.utah.edu/pub/linux/Mandra ke (Utah, USA) ++
- http://www.math.utah.edu/pub/linux/Man drake/ (Utah, USA) ++
- ftp://ftp.cee.odu.edu/pub/CEE/linux/ma ndrake (Virginia, USA) ++
- ftp://ftp.tux.org/pub/distributions/m andrake/ (Virginia, USA) ++
- ftp://ftp.wtfo.com/pub/linux/mandrake/ (Washington, USA) ++
- ftp://sunsite.mff.cuni.cz/OS/Linu x/Dist/Mandrake/ (Pragua Czech Repubic) ++
- ftp://sunsite.mff.cuni.cz/OS/Linu x/Dist/Mandrake/ (Pragua Czech Repubic) ++
- ftp.informatik.hu-berl in.de/pub/Linux/distributions/Mandrake (Berlin, Germany) ++
- ftp://msj.u-3mrs.fr/pub/linux/distr ib/mandrake/ (Marseille, France) ++
- ftp://ftp.ciril.fr/pub/linux/mandrake/ (Nancy, France) ++
- ftp://sunsite.uio.no/pub/unix/Linux/Mandrake (Oslo, Norway) ++
- ftp://ftp.sunet.se/pub/Linux/d istributions/mandrake/ (Sweden) ++
- ftp.linux.org.tr/pub/Mandrake (Turkey) ++
I haven't gotten through to any of those servers to find out if they have 7.0 on them yet, but I expect they will soon. -
Mirror sitesMandrake's site is swamped right now. The official list of mirror sites is here. The ones listed as doing hourly updates are:
- ftp://mandrake.mudspace.com/pub/linu x/mandrake (Michigan, USA) ++
- ftp://ftp.math.utah.edu/pub/linux/Mandra ke (Utah, USA) ++
- http://www.math.utah.edu/pub/linux/Man drake/ (Utah, USA) ++
- ftp://ftp.cee.odu.edu/pub/CEE/linux/ma ndrake (Virginia, USA) ++
- ftp://ftp.tux.org/pub/distributions/m andrake/ (Virginia, USA) ++
- ftp://ftp.wtfo.com/pub/linux/mandrake/ (Washington, USA) ++
- ftp://sunsite.mff.cuni.cz/OS/Linu x/Dist/Mandrake/ (Pragua Czech Repubic) ++
- ftp://sunsite.mff.cuni.cz/OS/Linu x/Dist/Mandrake/ (Pragua Czech Repubic) ++
- ftp.informatik.hu-berl in.de/pub/Linux/distributions/Mandrake (Berlin, Germany) ++
- ftp://msj.u-3mrs.fr/pub/linux/distr ib/mandrake/ (Marseille, France) ++
- ftp://ftp.ciril.fr/pub/linux/mandrake/ (Nancy, France) ++
- ftp://sunsite.uio.no/pub/unix/Linux/Mandrake (Oslo, Norway) ++
- ftp://ftp.sunet.se/pub/Linux/d istributions/mandrake/ (Sweden) ++
- ftp.linux.org.tr/pub/Mandrake (Turkey) ++
I haven't gotten through to any of those servers to find out if they have 7.0 on them yet, but I expect they will soon. -
Other NSA Secure Linux work
There is another ongoing NSA Secure Linux project. It is being done by the Computer Security Research Division at NSA. They are attempting to port the Flask Security Architecture to Linux. Flask is a policy-flexible OS security architecture.
Their Secure Linux project page is available. -
Other NSA Secure Linux work
There is another ongoing NSA Secure Linux project. It is being done by the Computer Security Research Division at NSA. They are attempting to port the Flask Security Architecture to Linux. Flask is a policy-flexible OS security architecture.
Their Secure Linux project page is available. -
NSA Secure Linux web page
This press release doesn't seem consistent with the announcement at http://www.cs.utah.edu/flux/fluke
/html/linux.html. That web page indicates that the NSA is developing a secure Linux system with a flexible security architecture for public release. -
Re:Beowulfs?Beowulf was definately not the first clustering project, and also not the first clustering project on Linux. But they are currently the most popular. Some other clustering projects that preceeded Beowulf include:
- TreadMarks
- The Quarks DSM System (ports to other platforms are here and my port to Linux is here.)
- DIPC (or try here)
- SHRIMP, a high performance parallel system for Linux.
- PVM -- a message passing approach to parallel programming.
-
Quotes are Quotes, Whether Claims are True or Not
Those who do not understand Unix are condemned to reinvent it, poorly.
It's what Henry Spencer said.
It's widely known.
There may be merit to your contention that not understanding Lisp results in reinventing it badly; Erik Naggum commonly makes that contention about Scheme, and I have no problem with the assertion that anyone building new systems that ignores the Common Lisp HyperSpec is likely doomed to reinvent parts of it less well than CLTL2.
That may mean that a more valid claim would be more like
Those who do not understand both Lisp and UNIX are doomed to reinvent parts of both, badly.
That still does not deny the historical fact that what is in my
.signature is what Henry Spencer said.I've got a "cookie file" that populates email and news
.signatures with random quotes; not all of them are true, at all. Some represent downright falsehoods; the Spencer quote isn't one of those.If you are feeling so much feeling towards Lisp, then I'm wondering why you're not running Ocelot or SilkOS or NASOS or the rendition of DrScheme atop FluxOS, or, if you're a Common Lisp partisan, perhaps Genera.
-
Quotes are Quotes, Whether Claims are True or Not
Those who do not understand Unix are condemned to reinvent it, poorly.
It's what Henry Spencer said.
It's widely known.
There may be merit to your contention that not understanding Lisp results in reinventing it badly; Erik Naggum commonly makes that contention about Scheme, and I have no problem with the assertion that anyone building new systems that ignores the Common Lisp HyperSpec is likely doomed to reinvent parts of it less well than CLTL2.
That may mean that a more valid claim would be more like
Those who do not understand both Lisp and UNIX are doomed to reinvent parts of both, badly.
That still does not deny that what is in my
.signature is what Henry Spencer said.I've got a "cookie file" that populates email and news
.signatures with random quotes; not all of them are true, at all. Some represent downright falsehoods; the Spencer quote isn't one of those.If you are feeling so much feeling towards Lisp, then I'm wondering why you're not running Ocelot or SilkOS or NASOS or the rendition of DrScheme atop FluxOS, or, if you're a Common Lisp partisan, perhaps Genera.
-
World's Oldest Living Tree Already Felled
That's like finding the oldest living tree, and cutting it down to put in a museum.
That's already happened (sort of).
From Alamut:
Prometheus
In 1964, a graduate student cut down the oldest living tree, a bristlecone pine (Pinus longaeva, Pinus aristata) in order to count its rings:
"Late in the year of 1964 a young geographer, Donald R. Currey, a student at this university, who was working toward his doctorate, was in the Southwest searching for evidence of Ice Age glaciers. The Wheeler Peak glacier and related phenomena attracted him. When this student and his associate came upon the bristlecones at the timberline, they began to take core samples from several trees, discovering one to be over 4,000 years old! Needless to say they were excited, and at some point, their only coring tool broke. The end of the field season was nearing. They asked for (and I still can't believe it!) were granted permission by the U.S. Forest Service to cut the tree down. The tree was 'Prometheus'.
"After cutting the trunk at a convenient level, which happened to be more than eight feet above the original base, 4,844 rings were counted. This student had just killed the oldest living thing on earth! Eventually, dendrochronologists determined the tree to be 4,950 years of age."
For some reason, Prof. Donald R. Currey's home page at the University of Utah doesn't mention the accomplishment
-
Some Documents
From ESR, I would add The Jargon File. The Cathedral And the Bazaar is more about Software than the Internet, but if that's there, than RMS's Why Software Should Be Free should also be there.
Another critically important RMS piece (and one more relevant to the internet) is The Right to Read.
Also there's The Declaration of Independence [of the USA], not as a document in its own right, but as the first entry into Project Gutenberg.
Getting more internetty, you've got RFC Number 1, the description of the tentative IMP protocol to be used between the four systems on the brand spanking new ARPA network.
Going to distant history (in computer terms) there is the 1945 paper by Vandemaar Bush, As We May Think, one of the inspirations for the ARPA project.
There's the 1989 whitepaper from CERN's Tim Berners-Lee, Information Management: A Proposal, the paper that started the WWW. -
Microkernels! Was: Re:Ok, please tell me...
Not sure if Microkernels have been implemented yet?
NeXTSTEP/OPENSTEP and now MacOS X Server are all based on the Mach microkernel, which has been around for quite some time.
Information about new stuff going on with Mach (Mach 4) is here: Mach 4 Project
Microkernels are very interesting.. you may want to give this stuff a look.
ash -
Re:I would much rather call it Linux
Imagine a system where you can choose any kernel you want (BSD,Linux,IRIX,BeOS, or even NT) use any shell you want (bash, commad.com, KDE or what ever) use any networking layer you want (TCP/IP, ATM
Since the shell and networking layers have to communicate with the kernel, and selecting the right kernel API is an important part of OS design, writing such a system is not practical. ...). This is real choice not having to force ppl into a all or nothing situation ...You might be interested in the OSKit, a modular collection of operating-system libraries. The OSKit was developed so that if you want to have an experimental OS with a few novel features, you (or your graduate students) don't have to write a whole OS from the ground up; just download the OSKit, rewrite a single module, compile it, and benchmark away.
-
How about Flux OSKit?
-
How about Flux OSKit?
-
Mirror
Nice!
When I grabbed a copy from your box, my transfer rate never dropped below 250KB/sec. I guess we've found a use for the vBNS!
For anyone who cares, I've mirrored it at http://qonos.chpc.utah.edu/pub /starwars/menace_480.mov. Physically it's at the University of Utah in Salt Lake City, UT, USA, and is connected to the vBNS.
--
Dave
devon.knull@mail.excite.com -
my two cents
Microkernel based operating systems have been around for a while, but they simply don't have the necessary efficiency to be competitive with traditional monolithic designs.
Which might not always be the case; see, e.g., the Flux project.