Debian NetBSD 346
bXTr writes "Interesting project over at SourceForge. Quoting from the website, 'Debian NetBSD is a port of the Debian Operating System to the NetBSD kernel. It is currently in an early stage of development and cannot currently be installed from scratch. Instead, a tarball of the current envionment is available and can be extracted into a handy directory on a NetBSD system.' Check out the reasons why they're doing it and some interesting commentary at DailyDaemonNews on this."
Re:kaboom (Score:3, Insightful)
Cooperation (Score:3, Insightful)
Re:kaboom (Score:1, Insightful)
Re:I would prefer the other way around (Score:3, Insightful)
FreeBSD doesn't have as many drivers for esoteric hardware. Not a technical advantage for Linux so much as a side effect of the greater market penetration.
But that's the way it is, nevertheless.
Re:the kernel? my god man (Score:3, Insightful)
This is true of the kernel, but the kernel is not the whole deal. One of the major problems with Linux is *that* it's every yahoo for himself -- Cox and Torvalds and a few others do the kernel, the glibc people are a different bunch, the X consortium [x.org], the ISC [isc.org], Apache Foundation [apache.org], plus all those assorted little libraries, you know the type, it's a kinda neat library, but you've only found 1 app that needs it
So, where the BSD team is some 10-20 people who can all get in a room and hash out details and come out with a coherent ports system, or a standard place to put software (apache goes in
This is a weakness in the Linux system of cooperation. It's also a strength. Just as no one can take control of the whole thing and fix it, also nobody can break the whole thing. Even if Linux and Cox between them decided to sabotage Linux, they couldn't, whereas one guy with cvs commit privileges on cvsup.freebsd.org could give himself a root shell on every BSD box on the planet. (Okay I exaggerate -- he'd get caught, probably, but that's only because most of the people working on BSD are good guys.)
Re:They're not cooperating... (Score:4, Insightful)
I don't like it (Score:5, Insightful)
how different (from standard netbsd) is it? (Score:3, Insightful)
If its just a different package system, its pointless. Less work, and more immediately useful results, would be modifying apt to work with the current binary package system (which actually does support dependencies, etc.), and the large number of binaries in this format already available.
If not, its a more questionable proposition. Arguably, its not really BSD anymore...it runs NetBSD binaries and uses that kernel, but the userland is basically Debian, ie, just like any Linux distribution. And most people who want that should just assume use Debian with the Linux kernel, which is a far more mature combination. Yes, for VAXen, toasters, slide rules and other more arcane platforms this won't exactly work, but Debian-NetBSD doesn't seem to have package for these platforms anyway.
Transition (Score:4, Insightful)
Mandrake/RedHat -> Debian/Slackware -> *BSD
It seems that Debian is going to make that last transition a little easier.
ports (Score:5, Insightful)
More like, what are rpm users missing out on? With rpm -i package.rpm the user may or may not be able to install the intended software. There could be real dependency problems, as in kde2 needs qt2. There could also be bogus dependency problems since you may have compiled qt2 from source but rpm wouldn't know about it.
Enter FreeBSD and ports. A typical FreeBSD install creates a directory called
But you don't have to take my word for it. Check this [freebsd.org] out.
My experience is limited to Mandrake, Slackware, FreeBSD and OpenBSD. They each have their strengths and weaknesses, but when I need to get sh*t done, BSD, espescially FreeBSD is my first choice just because the ports tree contains nearly any software I'd want to run, eliminating the bottleneck that software installation sometimes turns into and letting me get to the task at hand.
As an aside, it seems like everything that Mandrake tries to be to "joe sixpack" who is just getting into trying linux on the desktop, BSD is to the sysadmin or programmer who needs to get a *nix platform up and running for a certain task. Compiling a custom kernel, installing software, modifying the init process, etc are at least as easy for the sysadmin on BSD as adjusting the screen fonts and changing the wallpaper are for a newbie in Mandrake.
FreeBSD ports and Sorcerer (Score:2, Insightful)
Re:I would prefer the other way around (Score:1, Insightful)
Re:ports (Score:4, Insightful)
Because ports does not require packages. Example, if I want to install a KDE app, it does not require that I have the qt package installed. It searches for libqt.so. If it's a gtk package, it runs gtk-config, if it's apache, it runs apxs, and so forth. Now debian's a little better than RPM, which ends up making you force-install just about everything (defeating dependency checking) because you installed something from source, but you still have to intervene when a dependent package isn't present. Ports assumes you know what you're doing, and if the lib is there, it's there, it doesn't need a package manifest to tell you. It does check for the package first, and ports does build a package, so you get a package-based system that degrades gracefully when you don't religiously use the package system.
THAT is why I use ports. Because no sysadmin I know of takes the builds out of the box, they keep their source trees around to tweak and recompile as needed. Oh, and ports lets me do that doo, I just "make get" the port, cd work/packagename, and there's the source tree as if I'd untarred it myself. I can configure && make install it from there, or cd
Re:I would prefer the other way around (Score:2, Insightful)
SMPng project is not only about improving SMP performance of FreeBSD. It is also about making kernel fully preemtable, which has its advantages for real-time tasks, responsiveness in desktop and multgimedia environments. Besides, with an upcoming PPC and UltraSPARC ports having better SMP support kinda starts making more sense
Re:Noooooooo! Stay away! (Score:3, Insightful)
How quickly we forget that stability is how many of us have sold Linux and *BSD to our employers, and that sudden rash changes and stability problems can leave those who require stability out in a lurch.
I see Debian's methodical approach to "current" as a good thing. Debian is about choice: if you want to be on the bleeding edge, please run unstable, we need the beta testers. If that's not your game, here's the stable tree. If you're really anal (or demented), here's the last version with security patches.
Sounds like a win for everybody. NetBSD gains more users (those who happen to get off on apt-get), Debian gets to work on porting to other kernels (a major cornerstone of the Debian project's defined goals), and everybody gets more choice.
Stay away from system administrators who think that the "latest" is always the "greatest."
Re:Noooooooo! Stay away! (Score:3, Insightful)