NetBSD 3.1 and 3.0.2 Released

hubertf writes, "The NetBSD release engineering team has announced that the NetBSD 3.1 and 3.0.2 releases are now available. NetBSD 3.1 contains many bugfixes, security updates, new drivers, and new features like support for Xen3 DomU. NetBSD 3.0.2 is the second security/critical update of the NetBSD 3.0 release branch which includes a selected subset of fixes deemed critical in nature for stability or security reasons. See the NetBSD 3.1 Release Announcement and the NetBSD 3.0.2 Release Announcement for more information."

Comments

Re:I don't get it

[debilo]

I've read the press release. What do I get by installing this that I can't get in a 2 year-old Gentoo Linux installation? The BSD's have always been a bit of an enigma to me. Could someone enlighten me?

I'm not sure if this is flamebait or if you really want to be enlightened, but if the BSDs "have always been a bit of an enigma" to you, why not install one of them in a spare partition or fire up a VMware session, and play around with them for awhile? You really don't gain much by reading release information only, you know?

The BSDs provide everything you've come to love in Linux: stability, security, and probably a little more consistency especially regarding system administration and configuration. Linux and the BSDs are both fine systems, but maybe you'll prefer how BSD handles things. I honestly find it easier and more comfortable to do system administration via the CLI on BSD than via the various GUI administration tools in Linux, but that's just a matter of taste.

So, don't just dismiss NetBSD just because a release information page doesn't provide a detailed list of reasons why NetBSD is better than a 2 year old Gentoo installation. Try it out. Get your hands dirty and be "enlightened".

Re:I don't get it

[kv9]

What do I get by installing this that I can't get in a 2 year-old Gentoo Linux installation? The BSD's have always been a bit of an enigma to me. Could someone enlighten me?

firs of all, nobody is trying to make you switch. the BSDs aren't out to conquer the world (AFAIK), they just try to make proper operating systems.

second, you get:

• totally sweet firewalling, with ipf and pf
• proper package management with pkgsrc (your beloved portage? that's where it gets its roots)
• the ability to run the same configuration on dozens of different archs (that might not sound like much, if you only run i386, but there's people with lots of different gear out there)
• a clean, small, stable base system which includes everything you need to get your server going in a few minutes (literally, NetBSD installs in 2 minutes, even on old hardware) -- you can build on top of that, with pkgsrc or prebuilt binary packages
• run your favorite proprietary applications through the emulation layer (compat Linux, compat WIN32, etc)

and many more. you can read in detail on the project's feature page. that being said:

10:49:47 (1.15 MB/s) - `i386cd-3.0.2.iso' saved [209747968]

Re:I don't get it

[debilo]

Uhm, you do know that you can do system administration on the command-line in Linux too, right? (And I bet that there are GUI administration tools for the BSD's too, for that matter...

Yes, Mr. Romero, that's quite obvious, and I think you're misunderstanding what I wrote. I wasn't complaining about the lack of a CLI on Linux or the lack of GUI utilities in BSD. Most of the big Linux distributions come with pretty installers and widgets, and they encourage their users to use those instead of the CLI, so naturally most Linux users who try out one of the BSDs for the first time are rather taken aback by the focus on the CLI and are quick to consider the BSDs old-fashioned and not up the par with Linux. Yes, there's PC-BSD and DesktopBSD, both of them provide nice installers and GUIs, and I also know of Webmin; I was merely pointing out that I find working on the CLI in BSD more comfortable than clicking widgets in Linux, probably due to BSD's more central approach regarding the system layout, compare /etc/rc.conf in BSD to all the runlevel config files in Linux. I never got the hang of them, but again, it's a matter of taste. I just don't want new users to be discouraged by the lack of widgets in BSD as opposed to major Linux distros.

Here's a pretty interesting thread by a BSD user who had to learn to use Debian at work and shares his experiences. He sums up the differences between FreeBSD and Debian quite nicely. Makes for an interesting read.

Re:I don't get it

[LizardKing]

I've found doing anything in *BSD is more painful than it should be.

I'm struggling to think of an example. For instance, installing init scripts for third party software is far more painful on Linux:

cp foo.sh /etc/init.d/
ln /etc/init.d/foo.sh /etc/rcS.d/K69foo
ln /etc/init.d/foo.sh /etc/rc0.d/K69foo
ln /etc/init.d/foo.sh /etc/rc1.d/K69foo
ln /etc/init.d/foo.sh /etc/rc2.d/K69foo
ln /etc/init.d/foo.sh /etc/rc3.d/S69foo
/etc/init.d/foo.sh start

Unless your Linux distribution supports one of the other half-baked init schemes of course.

Meanwhile, on NetBSD it's:

cp foo.sh /etc/rc/
vi /etc/rc.conf (add the line foo=YES)
/etc/rc/foo start

Basically, anything administrative I can think of is more tedious or complex on Linux than on NetBSD.

Re:I don't get it

[phoenix_rizzen]

You do need to hunt down repositories for Debian, if you want software that isn't included in the standard repos. For instance, at the time of writing for that thread (July 2005) you could not get Java, Madwifi, or KDE 3.4+ in the standard repos. To get those, I had to search the web for custom repos to use with Sarge. Not a lot of fun for a Debian newbie.

Debian may have the highest number of packages available, but it does not have the highest number of applications. A lot of the packages in the Debian repos are for the libs that come with apps, and for multiple versions of the same app with various features enabled or disabled. If you take out all those duplicates, you end up with a lot fewer apps. A lot, yes, but probably not the most.

At the time that I wrote that piece, Ubuntu was a horrid little thing that was just starting out. Kubuntu didn't exist yet, and being a KDE user, why would I try Ubuntu?

Wireless is the worst grafted-on technology in the Linux world. There are multiple wireless networking stacks, multiple WPA supplicants, multiple commands for working with wired connections, wireless connections, and device-specific options. And Debian was (at the time) one of the worst for wireless support -- there was none officially in Sarge for madwifi or wpa_supplicant. Now, in Etch, things are a bit better, but nowhere near the level in FreeBSD. Why is there an ifconfig, a iwconfig, and driver-specific commands to work with wireless links? In FreeBSD, there's only ifconfig since they are all network interfaces, there's only a single networking stack that all the devices use. There a single config file to manage the wireless side of things.

I've become proficient with Debian in the year and a bit since I posted that, but Debian in particular and Linux in general remains a conglomeration of a bunch of hacked together software projects without an overarching feeling of togetherness or unity to it. There's no cohesiveness to "Linux" even in some of the distros.

Ubuntu is moving along nicely in that area, but that only drives home the notion that there is no Linux OS, just a hodge podge of OSes built around it, each with their own ideosyncracies, and the only way to get anything done is to standardise on a single distro. People need to get out of the "Linux" mindset and into the "Ubuntu" or "Fedora" or "Debian" or "Gentoo" mindset. Once that happens, then things will probably get better ... or else it will cause the splintering of "Linux" like the splintering of Unix back in the day.

And, yes, upgrading a couple apps can result in an upgrade to the entire OS. I've done it a few times. I'll never understand the whole Linux distro concept of "the OS and apps are one". Why do I need to upgrade to Debian Etch in order to run KDE 3.5? I can run KDE 3.5 on FreeBSD 4.11, 5.5, and 6.1, it doesn't require an OS upgrade to run newer apps.