Archive for the 'bsd' Category

OpenBSD Gets WPA/2!

April 16, 2008

I was playing around with conky, setting up some RSS feeds and trying to decide if I wanted that junk forked into my background. Then I saw the news. Excellent!

OpenBSD is getting WPA/WPA2 support. It includes several chipsets including malo, bwi (new Broadcom 43xx support in OpenBSD 4.3 and DragonFlyBSD), ral, zyd, and others. More on the way. I wrote on my BSD blog that I would give the new bwi driver a shot but I haven’t gotten around to it yet. I definitely will now.

BTW, I decided one instance of conky is enough so the RSS one goes.

OpenBSD 4.3 Song Rips RMS

April 10, 2008

This brings a smile to my face. With the imminent (May 1st) release of OpenBSD 4.3 comes the release of the official song for the release. The target for 4.3: Richard Stallman.

OpenBSD release song lyrics:

We are just plain tired of being lectured to by a man who is a lot like Naomi Campbell.

In 1998 when a United Airlines plane was waiting in the queue at Chicago Airport for take-off to New Orleans (where a Usenix conference was taking place), one man stood up from his seat, demanded that they stop waiting in the queue and be permitted to deplane. Even after orders from the crew and a pilot from the cockpit he refused to sit down. The plane exited the queue and returned to the airport gangway. Security personnel ran onto the plane and removed this man, Richard Stallman, from the plane. After Richard was removed from the plane, everyone else stayed onboard and continued their journey to New Orleans. A few OpenBSD developers were on that same plane, seated very closeby, so we have an accurate story of the events.

This is the man who presumes that he should preach to us about morality, freedom, and what is best for us. He believes it is his God-given role to tell us what is best for us, when he has shown that he takes actions which are not best for everyone. He prefers actions which he thinks are best for him — and him alone — and then lies to the public. Richard Stallman is no Spock.

We release our software in ways that are maximally free. We remove all restrictions on use and distribution, but leave a requirement to be known as the authors. We follow a pattern of free source code distribution that started in the mid-1980’s in Berkeley, from before Richard Stallman had any powerful influence which he could use so falsely.

Among the lyrics:
“And rule two dictates
You must give it to me
So I can give it away properly for free”

“The list goes on of course
But for traders this is all you need”

“This is madness!
He has lost his mind!
This defies the first law of free trade
Rule zero came before this rule one
Freedom means you cannot dictate to anyone”

This is payback for Stallman’s decision to flame OpenBSDers in recent months, objecting to things in the ports tree that are either proprietary or under licenses he finds objectionable. He said this makes OpenBSD non-free. Too bad he doesn’t understand OpenBSD is more ‘free’ than any other OS, including Linux — Theo doesn’t include any binary blobs and OpenBSD has reverse-engineered things which would’ve required binary blobs (such as the Malo driver I used before selling my Marvell Libertas card).

The lyrics page concludes by pointing out that Stallman makes sure GNU/FSF software will compile and run on Windows: “That man is a false leader. He is a hypocrite. There may be some people who listen to him. But we don’t listen to people who do not follow their own stupid rules.”

BSD is really about ‘free’ and really about ‘freedom.’ GPL is about neither.

Debian Out, Vector In

March 14, 2008

Ran into some issues with my tiny Debian hybrid install yesterday. One of the things I wrote about preferring Debian’s packaging to Slackware’s has its dark side: just because you can remove smaller parts to fine tune things, sometimes things are packaged together such that it’s not a good idea. Also, many apps are compiled for use on bleeding edge hardware with compile-time options that require downloading dependent libs and packages all users shouldn’t need. An example of that was the xbindkeys thing I wrote about the other day — massive download for a relatively small utility — especially since it can be compiled without guile; if emacs and vim can have no-X versions, other apps can be added to give users more choices suitable for their own hardware.

I was running into various problems when trying to pare the system down. If I want to remove A, then dpkg insists I have to remove B through K — but that I also have to install L through P, which aren’t currently installed, and then upgrade Q through V. In the process of it all, I was getting the messages that I had all these packages that were no longer needed. That’s when the real fun started.

In the process of all this, I decided it would be easier to start from the ground up and compile things as I see fit. That’s why I’ve favored ports over packages anyway, whether BSD or Linux. And why I’ve favored Slackware because it’s not inextricably tied to its binary packaging. You want source and ports, Slackware is good. You want packaging, Slackware is good.

Since I’m already running Vector, a Slackware desktop-oriented derivative, on my laptop and am very happy with it, I decided that would be good on my new hard drive, too. I’m now running Vector 5.9 both on laptop and desktop. I compiled kernel 2.6.24.3 for the desktop last night (2.6.24.3-r0313 #1 SMP PREEMPT Thu Mar 13 17:38:20 CDT 2008 i686 to be exact). I have one hardware problem to sort out, and that’s editing my xorg.config so the scroll on my new mouse works — minor issue, which I would ignore if not for having a new mouse.

Vector has slapt-get and gslapt, the Slackware packaging versions akin to apt-get from Debian. It also comes with cruxports4slack, which I’m not sure I want to mess with. If I do use a ports system, I’ll stick with pkgsrc (which I’ve used with great results in both Linux and BSD). If that’s what I wanted, though, I’d start with a base install of Slack or just use BSD.

I started removing packages last night before I started on the kernel — no need for Abiword, Gnumeric, or Gnome Office, didn’t need any of the wifi stuff on this because I’m wired, etc. Have a bit more to do yet. I won’t hang on to XFce even though it’s nice and my RAM use hasn’t been too bad, and the kdm and qt3 stuff will be gone tonight. I’ll stick with jwm and ratpoison.

My only regret is that I didn’t use the same config so I could use the kernel on the laptop, too. On the other hand, it’s been working so flawlessly that I’m not sure I want to change it except to test OpenBSD 4.3 and DragonFlyBSD for the new bwi (Broadcom 43xx) wrapper/cutter. If I ever get time to mess with either of those.

Various Updates and Thoughts

February 26, 2008

A few quick updates…

BSD
I updated my BSD blog this weekend. I learned DragonFlyBSD has and OpenBSD will have bwi, a BSD-native Broadcom wirecutter-like module. So I’m at least going to test it out on my laptop and see how well it works. I’m most likely transitioning back to FreeBSD or OpenBSD (maybe DragonFlyBSD), but I’ll continue to do a few things with Damn Small Linux so I’ll keep a few partitions available for that.

TRADEMARK INFRINGEMENT
I downloaded Damn Small Solaris, which infringes on at least two trademarks so I’m striking it out. Why can’t people come up with unique names if they’re going to copy everything else another project is doing? Same apps, roughly same size, and then taking their name as well. I guess some people just lack the ideas and originality to innovate or differentiate at all. Damn Small Linux is trademarked. So is Solaris — maybe someone should’ve noticed Sun’s clear notice about use of their trademarks, which has led to OpenSolaris projects with very unique names like Nexenta and Belenix. Sun has a legal team. I hope John of DSL does, too.

LAPTOP - KDE - VECTORLINUX
Back to my laptop. I’ve been running KDE 3.5.8 on it the past week. I need to compare the configuration used by VectorLinux to what I’m using on my desktop because it’s not using as much RAM as I feared it would (an issue with the laptop since it’s “challenged”). I prefer KDE to Xfce. I’m using less RAM when KDE loads than when Xfce loaded. Even with my choice of apps, I’m using less RAM with KDE.

Needless to say, though, RAM use with KDE is about triple after login what JWM requires. I wish there was a way to get KDE’s (start up) RAM use to about 100-120MB. I would use it all the time.

DEBIAN
One thing I like better about Debian compared to Vector/Slackware is the application packaging. Debian’s repositories aren’t just more prolific, Debian allows a bit more flexibility with respect to meta-packaging. For example, I wanted a specific K application. With slapt-get, I had to take it as part of a larger package with stuff I didn’t want; Debian had it by itself.

REMASTERING
I spent some time working on stripping down and updating things in Knoppix to see how small I could make it. I can get it comfortably under 100MB, but I’m leaving in a few things that wouldn’t come with DSL (no, not KDE!). I may get to work on it again later this week. I have the things I want to work working already. The rest is fluff.

BSDs Get Portable C Compiler

September 17, 2007

The BSDs are increasingly turning their eyes away from GPL software. Today’s good news comes by way of undeadly.org in the form of news that the Portable C Compiler (pcc) is imported into OpenBSD’s CVS tree and is now available via pkgsrc in NetBSD (and other BSDs using pkgsrc).

BSD Licensed PCC Compiler Imported:

It is not yet bug-free, but it can compile the i386 userspace. The big benefit of it (apart from that it’s BSD licensed, for license geeks :-) is that it is fast, 5-10 times faster than gcc, while still producing reasonable code.

Otto Moerbeek writes, “But, as an example, complex programs like ksh and ssh run (linked against libs built with gcc)! Of course the road is still long, but things really look promising…”

Bloatware Update

September 13, 2007

Here’s another sign that there’s really no difference between the mindsets of Microsoft and those churning out Linux distros . The latest abortion is Ubuntu’s decision to enable Compiz by default. Why do I have a problem with this? Because it means users will have to weigh their options between OS upgrades and hardware upgrades.

The hypocrites at FSF joined forces with a few leftwing organizations recently to attack Microsoft for doing this very thing. With so many Linux distros now using Beryl and Compiz by default, maybe it’s time they focus their attention to what’s happening under their own noses.

Ubuntu Technical Board votes on Compiz for Ubuntu 7.10:

The Ubuntu Technical Board voted yesterday to ship Ubuntu 7.10 (”Gutsy”) with Compiz enabled by default. Although Compiz has been featured in Ubuntu 7.10 Tribe prerelesases, the board has had difficulty determining whether or not it is reliable and functionally complete enough to warrant inclusion in the final release.

Here are some plugs for users of older hardware who want continual operating system updates without having to accommodate it with new hardware or hardware upgrades:

  • Damn Small Linux is targeted at users of older hardware and minimal systems, as well as users who want a variety of options in how they run their systems. DSL will run on a 486 with 16 MB of RAM. It can also be run from USB, directly from the CD, or installed in a couple different ways on hard drive.
  • Slackware and Debian both allow minimal installs. This remains a good option for users with vintage hardware who want up-to-date options. Note that Slackware has moved to Linux 2.6 by default; this may or may not be in the best interest of those running older, leaner systems (2.6 also deprecated support for certain hardware which is still supported in 2.4). It also requires a bit of knowledge about the kind of system you want to build. One of the problems encountered with such systems (and this also applies to DSL) is when users have unrealistic goals of adding the latest versions of resource-demanding software like Gnome and KDE. Match your apps to your hardware and you’ll do fine.
  • FreeBSD, OpenBSD, and NetBSD all have very low hardware requirements. Each has its own method for installing binaries (packages) or source (ports), but NetBSD’s pkgsrc is portable across all three. I use FreeBSD and can report, anecdotally, that it seems to schedule processes much more effectively than Linux (2.4). Like the two previous suggestions, the idea of using one of this Unix-like operating systems (much more Unix-like than Linux) is to add applications suitable for the hardware you have.

One more note PCBSD: It’s in the same boat as Ubuntu and bloated Linux distros. PCBSD includes Beryl by default. It’s not suitable for older hardware.

One and Done

September 8, 2007

My transition to FreeBSD is now complete. I’ll continue to post to this blog, particularly about open source issues, security, etc.

Transition to BSD: Why It Matters

September 2, 2007

I’ve been using OpenBSD for servers for several years, and I’ve flirted around with it, FreeBSD, and NetBSD on desktops. I settled instead on Linux for desktop use because Linux development was (and still is) much more dynamic. What mattered when I settled on Linux applies less to me now because I’m not living on the bleeding edge and the dynamism of Linux distros and what they include appeals less and less to me.

Most Linux distros compete without regard for hardware requirements: they presume users will treat hardware as disposable commodities (the frequent argument made against tech-dinosaurs at this point is Moore’s Law, which addresses costs as they relate to rates of technological change but not the issue of continued utility of older technologies). Accordingly, they pile on features that are beautiful to the eye but impossible to run without the latest hardware or major upgrades. That’s why I took exception to the FSF’s anti-Vista campaign this past week. They’re sanctimonious hypocrites for not blasting Linux distros like Mepis and Ubuntu for their system requirements right along with Microsoft’s requirements for Vista. The FSF’s silence over distros like Mint and PCLOS that include proprietary code (drivers, Flash, etc.) by default is also pretty suspect. Maybe they should clean their own house first and let the market decide if Vista is acceptable.

The way so many distros required me to upgrade my hardware to upgrade their releases led me to use two Linux distros: Slackware and Damn Small Linux. You don’t need certain video cards or massive amounts of RAM to run DSL: it will run on a 486 with 16 MB RAM. Each new release of DSL hasn’t rendered older hardware obsolete, it’s made it more useful. Slackware’s base install (which probably isn’t what most Linux advocates recommend to Windows converts) is also very lean and doesn’t require system upgrades; it’s the full install or what you add on top of a base install that affects Slackware’s hardware requirements.

Three things caused me to reassess my choice of operating systems. Individually, they weren’t enough to move me to do anything (especially anything that requires me to burn more ISOs, back up all my data, etc.). Taken together, though, I decided it was time to change.

First, I find the BSD-unit concept more appealing than the cowboy bits-and-pieces approach of Linux. In a nutshell, Linux is just a kernel and not an operating system. The distros pile an ad hoc assembly of tools (usually GNU utilities) on top of it to make a useful OS out of it. From there, it’s a battle between the distros with respect to application versions, system configurations, and package management systems.

In fairness, it usually works and works quite well. But there can be serious problems if one piece of the system doesn’t work right with the rest. This has affected me to various degrees with different distros, from living with little quirks to not being able to upgrade things or even to install certain software because it would break a system. Or actually breaking a system and having to reinstall.

In comparison, a BSD is a complete OS: kernel plus utilities. That’s a unit, one thing. It’s not ad hoc, it’s planned so that it’s integrated and (in theory!) less likely to break. It can recompile itself as a unit. Everything on top of the unit is optional and doesn’t affect the unit. This is why some people (I’m one of them) think BSDs are ultimately more stable than Linux-based systems. You can look up the benchmarking studies and accounts of uptime to satisfy whichever side you’re on.

Second, I want continued legacy hardware support. I’m not going to stop using, much less throw out, a working computer. I practice what FSF preaches (see above). I have functional computers over 12 years old, including some old Macs and early Pentiums. My “newest” computer is a 1300mhz Athlon-based XP box I use mostly for work. I found out last night I may have a new computer in my possession shortly, but it’ll be a donation and not something I’d ever rush out to buy (certainly not so I could run Vista or something that uses Beryl).

Naturally, I’ve had some issues getting certain bloated distros to work on my older hardware. Ironically, that includes ones usually lauded for their auto-detection and ease of use. I’ve been content, as noted above, with Slackware and DSL. Both are relatively user-friendly for users who bother to read the documentation.

I think the BSDs are better for older hardware than Linux — and that they will be better going forward. The Linux kernel has gotten bigger while deprecating support for certain older hardware. I’m unaware of any similar compromises in the BSDs to reduce legacy support; BSD shortcomings seem to be related to supporting bleeding edge hardware even though their wireless support is better than that in Linux (see below for Atheros relicensing issue controversy). Moreover, I know there are ports of all three BSDs available for all my hardware.

Third, and the straw that broke the camel’s back, I have very serious concerns about the restrictions imposed in GPLv3. I have major philosophical differences with FSF zealots over the changes — new restrictions — in the GPL. I’ve addressed those elsewhere in this blog (see category FSF Sucks). In a nutshell, GPLv3 moves the FSF’s goalposts from software to hardware (”anti-tivoization”) and data (DRM).

I think the “free as in speech” kind of freedom shouldn’t be restricted; free should mean “free.” Period. FSF disagrees with me and they’ve changed their license so that free means “less and less free.” They haven’t addressed new areas of technology (as they claim), they’ve only moved their goalposts to places Linus Torvalds isn’t prepared to go because he doesn’t share their peculiar ideological extremism.

The GPL activists also appear to think everyone else’s rules don’t apply to them. The debate over the licensing of the Atheros driver has me wondering if the GPL side thinks they’re above the law. It’s not about whether the code is still open, it’s whether it’s still free.

I’m sure Torvalds isn’t likely to change the kernel’s licensing to GPLv3. I also acknowledge much of the software I use, and will continue to use, is licensed under GPL. I use it because it’s good software and suits my needs, but I use it DESPITE its restrictive licensing.

It would be easier to be complacent and not make changes. Then again, it would’ve been even easier to use Windows or get a new Mac. At least I have options and I’m free to choose between them. That’s the best part of any decision.

FreeBSD Foundation Newsletter: Justin Gibbs on GPLv3

September 2, 2007

Justin Gibbs, founder and vice president of the FreeBSD Foundation, writes in the FreeBSD Foundation Newsletter about the GPLv3 issue. He points out that there’s a very unfortunate assumption in the general population (and among authors of some projects) that open source and GPL mean the same thing. He also mentions a chief concern of enterprise users and vendors that the GPL’s restrictions prevent them from using open source software (including Linux).

Gibbs writes that “the members of our community must engage on this issue, understand the importance of our licensing philosophy, and promote that philosophy to others.” That’s especially apropos given the current Atheros driver discussion I mentioned in a previous post.

FreeBSD Foundation Newsletter, August 29, 2007:

On June 29th, the Free Software Foundation unveiled version 3 of the GNU General Public license (GPL). Even though the majority of software included in the FreeBSD distribution is not covered by any version of the GPL, our community cannot ignore this very popular license or its most recent incarnation. Through extremely successful evangelization, and the popularity of Linux, the misconception that OpenSource and the GPL are synonymous has become pervasive.

This misconception isn’t new, so why write about it now? Version 3 has further “refined” the GPL’s concept of “free” software. Some use models that were possible under “loopholes” in GPLv2 are now explicitly forbidden in GPLv3. Appliance vendors in particular have the most to lose if the large body of software currently licensed under GPLv2 today migrates to the new license. They will no longer have the freedom to use GPLv3 software and restrict modification of the software installed on their hardware. High support costs (”I modified the web server on my Widget 2000 and it stopped running…”) and being unable to guarantee adherence to specifications in order to gain licensing (e.g. FCC spectrum use, Cable TV and media DRM requirements) are only two of a growing list of issues for these users. In short, there is a large base of OpenSource consumers that are suddenly very interested in understanding alternatives to GPL licensed software….

A GPL proponent might argue that a license for free software must be upgraded periodically since we cannot anticipate what new use models for free software might be developed that restrict freedom. The BSD license is as permissive as possible exactly because we cannot predict the future or to what beneficial purpose (commercial or otherwise) our software will be used.

As a community, this is the perfect time to clarify these differences. Toward that end, the FreeBSD Foundation has started to engage with large current and potential users of OpenSource software to understand their use models and how the GPLv3 might impact them. What is clear from the early results of this initiative is that the GPLv3 is a critical concern for many current commercial users of OpenSource software. As these companies devise strategies for dealing with GPLv3, so must the FreeBSD community - strategies that capitalize on this opportunity to increase adoption of FreeBSD.

Theo Addresses Appropriation of BSD Atheros Code

September 1, 2007

This kind of situation is becoming too common: guy takes BSD code, makes a few changes, removes BSD license and copyright information, inserts GPL license information. In this case, it’s over a submitted but not yet included slightly modified OpenBSD Atheros driver for the Linux kernel. The problem isn’t the modification but the way the submitter stripped out the BSD license information and inserted GPL.

What’s wrong if both are “free licenses”? That presumes GPL is free. It isn’t. It’s a very restrictive software license.

Theo de Raadt Responds to License Modification:

GPL fans said the great problem we would face is that companies would take our BSD code, modify it, and not give back. Nope — the great problem we face is that people would wrap the GPL around our code, and lock us out in the same way that these supposed companies would lock us out. Just like the Linux community, we have many companies giving us code back, all the time. But once the code is GPL’d, we cannot get it back.

Ironic.

I hope some people in the GPL community will give that some thought. Your license may benefit you, but you could lose friends you need. The GPL users have an opportunity to ‘develop community’, to keep an ethic of sharing alive. If the Linux developers wrap GPL’s around things we worked very hard on, it will definately not be viewed as community development.