Vector Light: Is it really?

April 21, 2008

I decided to see if I could find any third party information or reviews about Vector Light before I commit to installing it. One of the first things I found was this page with screenshots. It’s not very reassuring given what I wrote this morning.

For example, I see things I wouldn’t ever include in a “light” version -

  • bootsplash
  • slim login (I think it’s slim, maybe kdm light just like Vector?)
  • Fox toolkit (?)
  • pcmanfm (?)
  • gslapt shows the version of mplayer, and it’s the same as in standard Vector.

I guess what I meant this morning by separate paradigm is that it wouldn’t have multiple tools for accomplishing similar tasks the way you might expect it to be on a more full-featured distro — that there would be more consideration to streamline things and reduce duplication and maximize utility. For example, including fox toolkit along with other GUI/RAD toolkits. I checked to make sure vasmCC uses gambas (yes, it does). And so on.

I also would use a separate repository for “light’s” applications because the user bases aren’t the same. Why install a “light” version and then end up with an identical system when all is said and done once packages are chosen from the repository? The only thing that’s different is the choice of a window manager or desktop environment, and that’s an option that can be chosen when using the normal version of Vector.

I don’t know, maybe I’ll try it anyway and see. Or else I’ll go with my original plan and recompile stuff without bloated dependencies so that it’s genuinely light — lighter footprint, lighter on system requirements and resources, and more nimble than “pretty.” In the final analysis, I care a lot less about how my computer looks than what I can do with it. And I can’t do as much if I have its RAM crammed with big, bloated icons and high resolution wallpaper.


Problems with DSL Forums

April 21, 2008

This has been occurring with great frequency the past week, and it totally sucks…

If it’s not one thing, it’s another…

Taken within minutes of each other.


Reconsidering Vector

April 21, 2008

I noted in my entry yesterday that I’m thinking of doing a low resource slackbuild. Part of the reason for that is my experience with both Slackware and Vector Linux. Not to mention my experiences with Damn Small Linux in both traditional and frugal installs.

Now that I’ve had a few months to use Vector, I’ve found several things that cause me second thought about recommending it. I’ll check the Vector forums later today to see if these are issues others have dealt with. Last time I went to the Vector site, it had been hacked (search my vectorlinux category for screenshots).

(Edit noon CDT: I’ve been to the Vector forums and I’m awaiting approval to post in their forums.)

First, upgrade options in gslapt have been disabled. This means users are unable to upgrade their systems using the default package management system’s GUI. I haven’t found out yet if it’s still possible via slapt-get or other parts of pkgtools. I can’t blame Vector for conflicts due to using different repositories, but Slackware and slacky.eu repositories are NOT suitable across the board for use in Vector. I found this out when trying to update OpenSSH and getting an error from SSL not matching the version against which SSH was compiled. Easy fix to revert to the older version. I still haven’t found the security update for OpenSSH in Vector’s repositories, though. Which is the underlying issue for me — security and upgrade-ability.

Second, the base packages are very bloated. I appreciate the desire to make the system usable by everyone without having to add font packages, but the tools for using the included Ethiopian fonts aren’t included. If you’re not going to include the tools to use the fonts, don’t bloat up users’ hard drives with 50+ MB of fonts! Geez. Add to that the dependencies which many packages have been compiled — e.g., requiring samba to run mplayer. Little thought given to users who may not install/keep samba. Like the security issue noted above, that means more work compiling myself. And I was trying so hard to not do that on this ancient laptop.

Also, the included wallpapers and icons aren’t what I consider light or fast. They’re pretty heavyweight compared to other options. This is noteworthy when considering the 82 lines in .jwmrc with icons — some of them being scalable, some of them being quite large, and the menu icon itself being over 40kb. All of that crap loads to RAM and causes performance issues as jwm has to scale the various and sundry icons. I realize my own jwm configuration is spartan and probably not to most users’ tastes, but there has to be a reasonable approach to this. And I’m not arguing for removal of all icons from .jwmrc, just use sensibly-sized icons that don’t cause users to use the same amount of RAM to use jwm as they use for Xfce!

Third, there are several bugs to be sorted out. For example, the setconsolefont script is broken (line 41):

/usr/bin/setconsolefont: line 41: $REPLY: ambiguous redirect
putfont: KDFONTOP: Operation not permitted

While that’s not particularly serious (setfont /path/to/consolefont), I’ve had several getty issues on my laptop. Suspend/tuxonice doesn’t work and causes me to lose all video whether in X or console if I go idle. If I kill X, I don’t get any video input — just a blank screen. I can blindly type “startx” to get back to X but can’t view any console output.

Fourth, another sort of minor thing that isn’t very minor: I also noticed that my wireless router light would continue to flash for a few minutes after I shut down. I found that /etc/wireless/interface.conf listed INTERFACE=”wlan0″ instead of eth0, which is where my interface was set up using VASMCC — Vector’s own tool.

There are a few other issues that I’ve wrestled with but these are the ones that come to mind. While I still think Vector is commendable and headed in the right direction, I can’t recommend it to inexperienced users. I also think in some ways experienced users wanting a Slackware-based desktop would be better served using Slackware in the first place. The packages are going to be about the same. I’ve already recompiled more things than I wanted to, and here I am thinking of removing X altogether and rebuilding the system to pare down the bloat. I just think Slackware’s minimal install with a few select packages is a more sensible choice than Vector for someone wanting a low-resource system.

I intend to check out Vector’s lighter project soon. Maybe that will be better, maybe not. I don’t think it’s adequate to offer jwm and/or fluxbox and call it “light.” There’s more of a need for a paradigm shift to it than merely remixing apps and window managers. Anyone can do that and the world doesn’t need more sub-distro remixes masquerading as “new” distros. Will it actually use distinct, separate packaging with minimal associated bloat? Or will someone ostensibly update to full-blown Vector when installing something from the repo because the apps aren’t compiled with forethought to keeping the system as small and unbloated as possible?

If it’s the latter, no deal. If not, there won’t be any need for me to continue with my low resource slackbuild. Or to be a little more cautious about recommending Vector without qualifying it.

EDIT: I resolved the issue with losing ttys after killing X by modprobe vga16fb (I don’t need framebuffer before X but I do after?). I’m still sorting out tuxonice. Or giving up on it. I’m also still waiting for activation for the Vector forums. Registered once, just hit my second ‘resend activation code’ button today.


Updating vim with AAP

April 20, 2008

After having recommended someone try AAP to build vim through its most recent patches for MyDSL, I finally tried it myself to get vim/gvim current on my laptop. I’ve been using the version that came with VectorLinux but kept running into a couple issues that, upon inspection of newer patches, have been resolved. My preference has always been using ports to handle this kind of thing, but I’ve wanted to install compiled binaries as much as possible on this laptop. (Vector does come with a package to use crux ports but I don’t want to install a full ports tree.)

AAP is another project by Bram Moolenaar, developer of vim. AAP is a tool that can be used to acquire sources and patches which it then autobuilds a certain application per a set of recipes. In some ways, it’s similar to a ports system per application — not a full tree — except for the differences (so it’s like ports, but different). Its recipes can do dependency checking but I don’t know if it can do dependency fulfillment in the event certain dependencies’ recipes aren’t also on the system (I skimmed through the documentation but I don’t see how it could know to go to http://foo-site.foo to get the latest source and patches for foo without that all being defined somewhere — it should exit if it can’t find a dependency, right?). It’s based on python. It’s also still a prototype and its lone supported port (application) is vim.

Building vim with aap is very easy. Go to the build directory and enter the appropriate command, e.g., “aap -f URI://path/to/source CVS=[yes,no].” It fetches the sources and patches and then compiles it. When it comes to a halt, the user enters “aap install” and can designate a PREFIX=/path/to/install (as root to install on system with standard /usr/local as default, else install as user in $HOME).

Pretty easy and simpler than wget’ing 293 patches (btw, when is 7.2 coming out?) then applying in a loop. I agree with the download page for vim that aap is by far the easiest way to install vim.

It should also be the easiest path to updating: entering “aap update” in the appropriate directory takes care of rebuilding when new patches are released.

With so many other build systems, CVS/SVN/git, etc., it’s easy to see how aap could get lost in the shuffle or face inertia for adoption. I think it’s promising — keep individual applications updated and current without maintaining full ports trees. It can also be used for other tasks, as Bram wrote in this Linux Journal article a few years ago.

I’m going to try using aap for a couple other things I want to keep updated on my own computers. I may also try to use it on something I’ve been dabbling with the past few weeks: a build based on VectorLinux that’s “lighter” on resources than their developers appear willing to go. I initially thought of doing a low-resource slackbuild that would be on par with what DSL does except only for hard drive installation (no live CD, no frugal, etc.). It would be similar to DeLi except it would offer choice of 2.4 or 2.6 kernel, use standard glibc instead of uclibc, and maybe offer three levels of install (console only, minimal with gtk1, and one with gtk2). I’ll have more to write about it shortly as I sort it out further and weigh making it available.

(Re the last point, I find the prospects of tracking and maintaining and making available widely available sources for FSF’s lawyers objectionable, especially given their recent tendency to sue first and ask questions later. I’d wanted to work on something in parallel to one distro before until I learned of some of the FSF’s tactics on every downstream distributor and the FSF’s penny-ante insistence on being able to recompile every binary included in a sub-distro even if the binaries came from and could be recompiled within the upstream distro. What I want to do would require me to set up separate repositories — because I would be building with fewer options than Vector and Slackware packages use so users of older hardware wouldn’t have to bloat their systems just to use certain applications — and then separately track and maintain sources of contributed packages. Neither is free as in air, and the latter is ridiculous when using vanilla sources directly available from the various projects.)


An OS Comparison Article

April 17, 2008

I hate this kind of article…

OS Smackdown: Linux vs. Mac OS X vs. Windows Vista vs. Windows XP:

Since the dawn of time — or, at least, the dawn of personal computers — the holy wars over desktop operating systems have raged, with each faction proclaiming the unrivaled superiority of its chosen OS and the vile loathsomeness of all others.

Let’s look at some of the un-truths told by the advocates.

First, the Linux fanboi writes:

Unlike Mac OS and Windows, Linux is free as air and open to development by folks who are motivated by the desire to make the technology better, rather than by corporate tech farms whose real interest is the bottom line.

Free as in air isn’t really free as in air. It may not cost you much to install Linux on your home computer, but installing it on 25 desktops in your business wouldn’t be free as in air. You’d have plenty of costs associated with the installation and with re-training users. Depending on the time frame you’d allow for reduced productivity, it could be cheaper to upgrade to Vista licenses and new hardware. I think this is one of the dumbest arguments for Linux because too many advocates don’t understand that learning curves cost companies time and money. And the last time I checked, the costs of hiring someone with a RHCE were comparable to bringing in a MCSE.

Let’s also forget that the chief submitters to the Linux kernel and to many of the libraries, utilities, and appications are employed by IBM, Novell, Red Hat, Sun, and many other companies whose interests are the bottom line. So I beg to differ, too, that profit is a bad thing.

If the world doesn’t want to use Microsoft software, Microsoft won’t stay in business. That makes them accountable to consumers and users, and I don’t think accountability is such a bad thing. If I have a problem with Windows, I go to my vendor and/or Microsoft. If I have a problem with Vector Linux and getting X set up or problems with python, who’s accountable? Linus won’t take my calls, but neither will Bill. Microsoft has websites and toll free help lines (depending on your level of support). Vector has a website and a forum. Maybe someone in an IRC channel can help me sort it out?

He continues,

Which is all very nice, but is it any good as a desktop operating system? You bet.

“Bet” is a gamble; most enterprise users won’t gamble — and neither will casual users who are more interested in doing things as quickly as possible. I’m not a casual user. I use Linux almost exclusively on desktop. Is it as good as Windows for that? No, I don’t think so. I have few problems using Linux/BSD but I can’t recommend it for most users. It’s not on the same level as Windows yet. And that’s not just my take, that includes many in the Linux/BSD/open source communities and companies like Novell and Red Hat (not to mention computer sellers, some of whom have found out firsthand that users won’t rush in to buy machines with Linux even if they save a few bucks from not needing a Windows license — what does that tell you?).

Let’s start with the hardware footprint: With the possible exception of BSD, Linux’s ’sister,’ Linux is the lightest thing you’ll ever install on your computer. While the minimum required hardware for Windows has been bloating, and Macs need more and more horsepower to run OS X, you can still dig out your old 486 and fire up Linux without problems.

That isn’t entirely true. Nor is it entirely desirable since most users expect more than what you can squeeze out of Linux on a 486. Most modern/updated Linux distros will no longer run on 486s. Indeed, the most popular distros targeted at newer users — who are NOT those who will start with Slackware or LFS — have requirements in line with other modern operating systems like Vista and OSX. Linux distros are prone to the same bloat-mentality prevailing anywhere else. That’s because developers and packagers target modern hardware, not the lowest possible denominator. So initial footprint is beside the point except for experienced users.

While there are some exceptions, the rule in the Linux world has matched that of Vista: the goal is to match system requirements to prevailing technology and expect that users will upgrade systems periodically. That’s why Ubuntu, PCLOS, and SuSe will not run on a 486 (not without lots of stripping and recompiling apps with minimal possible libraries for running in leaner systems). DSL with it’s 2.4 kernel and nearly Y2K-level software will run on console on a 486 so long as it has 16 MB of RAM. But so will a nearly Y2K-era version of Windows — same era software, same era hardware (apples to apples). So what’s the point…

Then the fanboi writes:

Linux is not only small, but it’s also stable. I have several Windows boxes at home, and it seems like whenever I blink, something has gotten screwed up in the registry or I have a Dynamic Link Library conflict.

This is ridiculous hyperbole and ironic. I have one hard drive with Windows NT workstation, circa 1996, that has run admirably with no DLL problems or registry conflicts. Then again, I kept it up to date with the service packs and ran it as it was designed to run: separate administrator account, anti-virus software, etc. I was also an early adopter of XP because it was based on the very stable NT. Again, no problems. Ever. The only virus I’ve ever had on any Microsoft computer was ’stoned’ in about 1990. I started using DOS in 1985. I’d used Apples (got my Apple II in 1979), a series of Commodores and Timex-Sinclairs, and one Mac before switching to PCs for the most part (since 1985, I’ve had a few Macs, one BeBox, and a couple SPARCs). I had more trouble with Apples and Macs than real PCs. I have one Mac remaining but I don’t use it; I also have several boxes of Mac parts.

I’ve also encountered plenty of issues with Linux. That includes buggy drivers and poorly coded scripts that have done things like load modules for filesystems I wasn’t using, cause kernel panics, etc. How the hell is a kernel panic any different from BSOD — a Windows fate I never experienced myself because I’ve kept my systems patched? And what about all the dependency hassles experienced even when running one of the more bloated distros like Ubuntu or PCLOS? How is that any different from the complaint about DLL conflicts?

Same answer to all questions: It isn’t any different. Linux users should stop relying on such stupid arguments because those aren’t significant differences. And with all due respect, average users will find tweaking registry entries in friendly GUIs — or restore points in XP — much easier solutions to sorting out Windows issues than going through series of Linux init scripts and various config files even if they are text files. Much less issues with peculiar libraries used by odd applications; at least Windows users have fairly standard DLLs upon which all developers build apps.

Every operating system and distributed computing environment (since Linux itself is merely a kernel — Linux isn’t Ubuntu, but Ubuntu uses the Linux kernel) is prone to some kind of breakage. The more complex something is, the more likely there are going to be some kinds of issues affecting users. Windows is complex. So are Linux distributions, especially ones focusing on desktop use. Linux distros may even be considered more complex from the standpoint that Windows is more standardized as noted above. This is certainly true when looking at how many different libraries binary packagers build their packages against and how many problems that can cause if the end user doesn’t want all kinds of stuff just to use one app from the package management system.

Linux doesn’t get points over Windows for this. They’re evenly matched. Or Windows gets an edge.

Unfortunately, the penguin-loving fanboi continued with something I’ve blogged about:

In the recent “Pwn 2 Own” hacker challenge, computers running Mac OS X and Windows Vista were cracked, but the Linux machine wasn’t. I won’t claim that Linux has no security or virus problems, but they tend to be right out in the open where you can see them if you look. At the moment, there are far fewer Linux viruses out in the wild than Windows viruses, and there are fairly bullet-proof ways to detect viruses under Linux using checksums on files.

Let’s get something straight. The Mac was pwned due to an exploit in Safari, which is Apple’s own code that comes with the computer; in fairness, the Mac was pwned after the rules were relaxed a little. The laptop with Vista wasn’t pwned until the last day when the rules were relaxed even further. The pwner took advantage of a Flash/Java/DEP vulnerability — using third party software — and not something inherently vulnerable due to Windows code. My understanding of that exploit, which has yet to be published, is that it’s cross-platform — and that it could affect a Linux system with Flash and Java. It wasn’t tried on either other platform in pwn2own because of the rules. Whether or not that specific exploit really works on Linux computers running Flash is beside the point anyway: Linux versions of Flash are every bit as dangerous in the wild.

At least Flash works as it’s supposed to in Windows. What was the point again? Oh yeah, Linux is supposedly better than Windows. Not.

One more thing about this as it relates to Vista. Vista’s security is heads and shoulders above XP’s and earlier versions’. Those who insist that Vista is on par with XP and earlier security simply haven’t investigated it for themselves and are engaging in sheer FUD. Among those giving Microsoft props for their commitment to making Vista more secure are those who’ve won pwn2own before. I’ll go even further and say that I think Vista is inherently safer than Linux; anyone running the same kernel version I am — or within several iterations either way — should have updated with a novmsplice patch or upgraded kernel, which is one of the things I would cite in my reasons why I would say Vista is safer. That’s Linux-specific, not related to PHP or samba or some other code thrown into distros. But when you get into all the other stuff thrown into a standard distro mix of utilities and libraries and applications, that’s where Vista shines. Go ahead and run apt-get –dist-upgrade every day and pray your system doesn’t break; I’ll stick with Microsoft’s automatic updates because their turn-around time on patching is faster and because they’re a centralized and accountable source of the updates, not relying on hundreds or thousands of package submitters whose intentions or abilities you may question.

Now let’s look at the Mac Kool-Aid drinker’s take on OSX:

Did I mention that Leopard is a certified Unix product, too? Mac OS X is the only operating systems that can run all mainstream Windows and “*nix”-based operating systems — and host “*nix” software natively — with few of the usual security risks.

Along with its famed user interface, one of the keys to the success of Mac OS X is the lack of malware, spyware and self-propagating viruses. We can debate the reasons — whether it’s the security inherent to the modern BSD underpinnings of Apple’s code or the “security by obscurity” theory — but Macs are not susceptible to the problems that have always plagued Windows PCs.

Security by obscurity isn’t a theory. Nor is it security. It’s obscurity. Mac’s security is third-rate. Not second-rate, third. Its Unix family lineage isn’t why it’s secure — that’s a non sequitur. Many of the most open vulnerabilities have occurred in or were developed for and on Unix-like operating systems. How many people still use telnet?

Many Mac users insist on running in single user mode. That’s no different from Windows 95 and earlier and the lack of permission levels that led to the prevailing attitude that there’s something inherently inferior about Windows. There isn’t. It doesn’t matter whether you run OSX, Linux, or Windows as root/administrator — it’s a bad, unsafe practice that can lead to serious trouble. I don’t even set computers up to use sudo except with password because I don’t care to allow anyone taking over my account to have full system privileges. Yet that’s how many operating systems are designed. Puppy Linux runs as root only. So does Dynebolic. Knoppix and DSL and other live CDs set up users with full system privileges via sudo. For live CDs, that’s fine. For anything else, I don’t care for it.

Apple does nothing to dissuade users from it. Single user with full system privileges. Coffee shop hot spot. Easy target.

OSX had more severe advisories than Vista and XP combined last year. Local and remote. Third party and first party.

Stop drinking the damn Kool-Aid.

Now let’s look at the one almost everyone else loves to hate. I’m skipping the XP guy because I don’t care for the Luddite-like hysteria by those who insist Microsoft extend XP’s life. I wasn’t happy when the NT 4.x support stopped, but that’s the way business and life goes. I’m no happier that Linux 2.4 development is waning because users are expected to migrate to newer hardware. I’m in the same boat that way, but I’m not crying. I’m using Linux 2.6 and reducing its resource demands to fit my hardware. XP users can do the same thing with Vista, which is not a one-size-fits-all OS as some portray it. It’s very scalable, just like other modern operating systems, and can be tweaked to perform well on older computers within reason. You just won’t enjoy all the graphical BS that has greater demands.

The Vista fanboi candidly writes,

Now, it’s true that for the moment, Windows XP is superior to Vista when it comes to software compatibility. But that won’t last long. The best and newest software will be built for Vista, not XP. So if you want to look to the future, not the past, Vista is the way to go.

This is true. Again let me reminisce about my NT days. I was running an OS that couldn’t run a lot of the stuff my friends using 16-bit Windows (3.1, 95/98 ) were running. I didn’t have the same level of plug and play support. Drivers were written for the other versions, not NT. The only USB drivers for NT I’m aware of were from third-party software companies and Dell (which was developed in-house for NT and worked surprisingly well). In short, most consumer software wasn’t being written for NT and most devices weren’t including driver support for NT. Everything was for 95/98. Then came WinME, a half-hearted attempt to move to NT. Then came XP. There was no turning back. Some of my enterprise software would run on XP, but many companies made upgrades available for those migrating to XP — good business decision because the world was going to turn to XP and away from NT and 95/98.

The same thing is going to happen for Vista. No matter how much FUD is spread about it, it’s not the future. It’s the present. The footdraggers aren’t leading the way. They’re fighting a losing battle.

The Vista guy continues,

As for Linux, if you’re a fan, feel free to fly your uber-geek badge every time you boot up — but don’t expect to run your company’s enterprise software, much less mainstream software and games. And do expect to become very familiar with the confusing vagaries of the specific version of Linux you’ve installed.

This is one of the things about Linux I think gets lost among its most ardent advocates. The world isn’t looking for myriad choices, it’s looking to get stuff done. The distros that target enterprise users understand this very well. You can prattle for days about window managers and eye candy, but that doesn’t lead to adoption in the enterprise. Enterprise is won over by commonalities. Enterprise is lost when the applications it needs are either unavailable or — the irony here is overwhelming — has peculiar library demands. Yes, that nasty issue about libraries/DLLs applies to Linux here.

Microsoft is where they are because they played their cards right when it came to matching their software to the most widely available hardware. Apple was too busy playing with goofy interfaces and buses to be a serious player in the enterprise when it mattered most. While Apple was busy creating its own alternate universe, Microsoft was trying to cater to the real, existing one. That’s why Microsoft runs over 90% of the world’s desktops and has serious marketshare in servers as well.

I’m not anti-any of these platforms. Each can do what some users need. None is perfect for every possible task. Each can be as safe as the other if the user is attentive to keeping his system secure. The user, as I’ve written so many times, is the weakest link in security.

The Mac user noted how easy it is for him to make movies. The Windows user noted how everything, especially enterprise-grade software, is written for Windows. The Linux user made some valid points about the cost of his software (though, to be fair, it’s not exactly free to retrain employees to make equivalent use of open source software if they’re already productive on closed source software). All three also engage in some level of blindness about the others, but two of them stand out: the Mac user has a gullible feeling of invincibility and the Linux user’s smugness about, well, everything and ignorance when it comes to comparing and contrasting Windows and Linux.

Maybe the one lesson from this kind of comparison-article is that we don’t need more of them from advocates. Maybe we need more honesty and fair comparisons from people without axes to grind.


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.


Apple Challenged by Clone Maker

April 15, 2008

Mac cultists are pissed that some interlopers dare move into their sphere. Meanwhile, Apple has been strangely silent. This is the same company that reflexively sends cease and desist orders to people who post steps for installing their OS on non-Apple hardware. Or mentioning that it’s even possible.

Mac Clone Maker Psystar Vows To Challenge Apple EULA - Apple Unvarnished - InformationWeek:

Psystar’s OpenMac clone is priced at about $399 — less than one-fifth of what a similar, Apple-branded system sells for. It also represents a direct violation of Apple’s end-user license agreement, which forbids third-party installations of Leopard.

But Psystar said Monday that the company believes Apple’s terms violate U.S. monopoly laws. “What if Microsoft said you could only install Windows on Dell computers?” said a Psystar employee.

The employee, who would only identify himself as Robert, said Apple grossly overcharges for the hardware on which its operating systems, including Leopard, come preinstalled. “They’re charging an 80% markup on hardware,” Robert said in a brief phone interview.

I agree that Apple charges a premium price for mediocre hardware enshrined in aesthetically above-average casing running an operating system long on flash and short on security. If Mac users want to overpay for that, more power to them. As far as the restrictive OSX EULA, who knows. My own preference is to not do business with someone who requires me to purchase their hardware to use their OS.

The Open Computer can be seen here. Available in black or white. Base price includes Core 2 Duo running 2.2 mhz, 2 GB DDR RAM, 250 MB SATA hard drive, no operating system. They’ll preinstall OSX Leopard for $155. Lawyer not included.

Then there are the skeptics. Fair questions. What’s up with Psystar? Has anyone done business with them before?

Back to the markup issue and thinking of the iPhone rebates Apple authorized when they dropped their prices and the early adopters whined. I wonder how many Mac owners would expect a rebate if Apple’s restrictions were lifted and they had to lower their prices to what cloners would offer. I remember what happened during the brief period when Apple licensed their OS: more savvy users embraced clones that beat Apple to the punch with more standard (e.g., IDE and PCI buses, VGA, etc.) interfaces. It would certainly benefit users to let them choose their own hardware (Intel x86 architecture is the same whether it’s running Windows or OSX or anything else, there’s no special magic); it would cripple Apple.


Added dwm to Desktop

April 14, 2008

I’m holding true to my word about giving dwm at least a week. I also installed it on my desktop, but haven’t done any reconfiguration from the defaults save for making the border 0 pixels and adding a couple applications to float.

My initial opinions haven’t changed much and I’m still resisting the automatic splitting when opening things in the same desktop — it’s mildly annoying when opening a second window in an application like Sylpheed to compose an e-mail (not an issue for mutt or other console apps) or when Firefox splits the screen with the download manager (which wouldn’t be an issue if I’d install the download status bar extension). I can live with it.

No other major changes yet — mainly cosmetic and only a couple apps set to float. I installed artwiz fonts on my laptop and changed my config.h to use smoothansi. I also changed the colors around a little. I think I like this better with the black fonts and lighter grey for the background (yellowgreen for active). I’m using smoothansi for conky and also in aterm. These are both laptop shots.

I removed the date-sleep pipe recommended in the README for adding a clock so now I get dwm-4.9 in the corner. Whatever.

Nice Spring-like theme by Beccary and it has a cool name. Even better, its default CSS allows a little more space for text and images than some of the other themes I’ve used.


Using dwm on My Laptop

April 13, 2008

I decided late last night to try dwm (thanks mikshaw). I’m still playing around with it. I compiled it to match the color scheme I’ve been using in jwm. My status bar matches my background color at the moment. Not exactly eye candy. Hey, it works for me and I like it better than the default blue and silver (is someone a Detroit Lions fan?).

My initial impressions: I like it a lot on my laptop. It accomplishes a lot of what I’ve done with my jwm config mods. It opens most apps maximized. I edited its config file with 0-pixel borders. Its binary is about 20% the size of my no-frills (all options disabled except confirm) jwm binary. Nice!

Peeve: It doesn’t use config files, so it has to be recompiled for any adjustments like colors, classes to float instead of tile, etc. Every time. That’s not too much of a hassle because it’s a tiny program.

I haven’t done much else in the way of configuration — just colors and borders so far. Most of its default keybindings are acceptable, but I’ll probably have to change them to some extent. I also have to decide if I care much for the split screens when I open new windows in the same virtual desktop. That’s what drove me from using larswm.

I also installed dmenu. I like it, too, (and have use it before with other window managers including wmii) but I really need to export some directories to PATH for it to be more useful for me.

One of the reasons I think I still prefer jwm is because I can edit everything on the fly, including the menu; alas, it also requires restarting for any changes to be made available. I’m going to stick with dwm for at least a week and see if my opinion changes.

I may also try awesome at some point. It’s a rewrite of dwm with the difference that it uses a config file and doesn’t require recompiling for changes to take effect. Then again, I don’t mind partaking in a little snobbery at such a small price. As its developers point out:

Because dwm is customized through editing its source code, it’s pointless to make binary packages of it. This keeps its userbase small and elitist. No novices asking stupid questions.

I’ve been a fan of other suckless projects like slock — which accomplishes in a very tiny binary what I’d otherwise use xscreensaver or xlockmore to do, which is overkill considering their bloat. The suckless goal of minimal lines of code works very well on my aged hardware.


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.