NetBSD Adopts NetBSD/xen for Internal Use
agent dero writes "With NetBSD 2.0, the NetBSD Foundation also released support for a new port, NetBSD/xen.
A version of NetBSD meant to run on top of the Xen virtual machine monitor. In this press release the foundation has announced that it is using the port and Xen for much of its internal development, citing security, and ease of use as main reasons for its adoption."
Maybe I'll switch from using Qemu for my kernel sabotage. I would call it kernel hacking but that would indicate some proficiency :-(
Now multiple BSD instances can die on a single machine, securely.
So Xen supplies a NetBSD kernel that runs under Xen 2.0. NetBSD now supports Xen 1.2. How is this a great advance? Why didn't they just pick up the Xen supplied pathces and go with the latest version of Xen?
When I saw it in Linux Journal (or was it Linux Magazine? Not sure...), I tried to get Xen. I went to their website, but couldn't find a download link.
Of course, now that I've seen it on Slashdot, it's a cinch to find. (Go figure...)
tasks(723) drafts(105) languages(484) examples(29106)
... I could switch between a build world of netbsd, and Counter Strike real fast!!!.
That makes me wonder if I can share one nic between the OSes, or put in two NICs, assign one for each OS.
Apart from Zen, would be cool to do a complete replace-boot, as in the OS state is frozen and written to harddisk (some laptop bioses do this), and the state of another OS is read... making switching between OSes, as fast as reading the same amount of data as your used up ram.
Heck I'll just buy another machine and use a KVM switch.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. I
*BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personae?
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead.
As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
... facts are facts. ;)
FreeBSD:
FreeBSD, Stealth-Growth Open Source Project (Jun 2004)
"FreeBSD has dramatically increased its market penetration over the last year."
Nearly 2.5 Million Active Sites running FreeBSD (Jun 2004)
"[FreeBSD] has secured a strong foothold with the hosting community and continues to grow, gaining over a million hostnames and half a million active sites since July 2003."
What's New in the FreeBSD Network Stack (Sep 2004)
"FreeBSD can now route 1Mpps on a 2.8GHz Xeon whilst Linux can't do much more than 100kpps."
NetBSD:
NetBSD, for When Portability and Stability Matter (Oct 2004)
NetBSD sets Internet2 Land Speed World Record (May 2004)
NetBSD again sets Internet2 Land Speed World Record (Sep 2004)
OpenBSD:
OpenBSD Widens Its Scope (Nov 2004)
Review: OpenBSD 3.6 shows steady improvement (Nov 2004)
OpenSSH (OpenBSD subproject) has become a de facto Internet standard.
*BSD in general:
..and last but not least, we have the cutest mascot as well - undisputedly. ;)
Deep study: The world's safest computing environment (Nov 2004)
"The world's safest and most secure 24/7 online computing environment - operating system plus applications - is proving to be the Open Source platform of BSD (Berkeley Software Distribution) and the Mac OS X based on Darwin."
BSD Success Stories (O'Reilly, 2004) (pdf) ~ from Onlamp BSD DevCenter
"The BSDs - FreeBSD, OpenBSD, NetBSD, Darwin, and others - have earned a reputation for stability, security, performance, and ease of administration."
--
Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.
Requiem for the Requiem for the FUD's FUD
Maybe I'm missing something, but how is Xen different from VirtualPC or VMWare?
I'll try to be polite, and I'll assume (not that I really believe it..) that you're not trolling.
The ancestor is pretty much a collection of facts. Where do you see the FUD exactly?
It's true that FreeBSD can route 1Mpps on a 2.8GHz Xeon while Linux, *on the same hardware*, can't do much more than 100kpps (200kpps? 300kpps? Still quite far from 1Mpps).
It's true that, even if Linux is the current record holder, last year NetBSD broke the Internet2 Land Speed World Record twice.
So, where's the "Requiem for the FUD's FUD" again?
Beware the KVM switch my son,
The mouse emulator that bites,
The cords that catch.
Beware the loss of functionality.
And shun buttons 3 4 and 5, natch.
Now that I've set the Reverend Dodgson spinning in his grave, let me translate.
Smarter KVMs have a big problem with fancy pointing devices. Many are designed to emulate a mouse to each attached CPU. For various reasons, they emulate a two button MSFT scroll mouse. So anything fancier is lost functionality.
I did find (just after purchasing a different one, natch) a USB KVM that is more like the old hard switches, and doesn't do emulation, that should avoid this problem. Of course you can no longer switch CPUs from your keyboard, because it doesn't trap the keyboard output.
It's funny how posts that are offtopic but correct get modded down, but posts that are offtopic AND wrong, like parent, don't. So, even if this slashdot moderator won't like to hear it, here's my question again.
---------
I'll try to be polite, and I'll assume (not that I really believe it..) that you're not trolling.
The ancestor is pretty much a collection of facts. Where do you see the FUD exactly?
It's true that FreeBSD can route 1Mpps on a 2.8GHz Xeon while Linux, *on the same hardware*, can't do much more than 100kpps (200kpps? 300kpps? Still quite far from 1Mpps).
It's true that, even if Linux is the current record holder, last year NetBSD broke the Internet2 Land Speed World Record twice.
So, where's the "Requiem for the FUD's FUD" again?
While running it as the client is cool, are there patches to run the BSD's as the server side as well?
Nothign against the use of linux in general, I just prefer FBSD for servers..
---- Booth was a patriot ----
Not to flame you, but that is a pretty big detail to miss.