Archive for the ‘bsd’ Category

Examples of “Unsophisticated Users” I Mentioned at DW

February 5, 2010

I was asked to elaborate on what I meant by “unsophisticated user” before I was banned at Distrowatch earlier this week.

Fortunately, my blog is getting plenty hits for searches related to GNOBSD so now I have some examples of what I meant — just from this morning. The “unsophisticated” classification is for those whose preference is to bypass any learning curve and use a Windows-like starting point. That means no console interaction, boot straight into X and a pre-configured desktop. For example, one of the DW reviewers wants things in a NetBSD-based CD to be more like Linux Windows with automounting and tons of services running by default. And then there’s the whole thing Ladislav started by distorting what actually happened in the OpenBSD lists when GNOBSD guy decided to spam it to notify the project of his fork.

At least these people are using search engines to find information. Some unsophisticated users won’t even try looking it up before rushing to the upstream project and badgering them with questions about something they don’t even support. Which brings me to this:

Attention GNOBSD searchers landing on my blog(s) (see my BSD blog listed in the blog roll on the right): I support and recommend OpenBSD, not GNOBSD. What difference does the underlying operating system mean to you if you’re only going to run a graphical desktop environment anyway? Gnome is Gnome whether it’s on Linux or BSD or OpenSolaris or any other operating system.

Adding gnobsd category so I’ll get even more hits. Woot.

Advertisements

Who Are the Bad Guys in This?

February 2, 2010

This is the kind of crap Linux Hater loves because it shows how idiotic the open source community can be.

I want to provide more complete context of the quotes offered by another site’s owner/reviewer [edit due to too many IMs: yes, Distrowatch] as proof that OpenBSD people “attacked” the GNOBSD guy. I couldn’t find any attacks by OpenBSD people. They didn’t care what the guy did with their code, they only didn’t want him to advertise it in their lists — it was just wrong forum for it. But that’s not how the owner/reviewer saw it and he stoked the irrational passions of his most irrational readers.

Let’s be fair and look at the other side of the story.

First, Gilles@ replied with:

omg ... there will be blood ... :-)

Note the smiley.  How is that combative?

Bryan B next replied with legitimate questions:

You can install to a USB stick with the OpenBSD CDs.  What is special
about yours? Why add a bloated Desktop like GNOME?  What's wrong with
fvwm, ormaybe even fluxbox (in a pinch)?

Tomas B kindly replied:

You will misguide users a lot, because I think that most of the users
of OpenBSD don't need GUI installer and users which will try your OS
may think that it's somewhat easy as eg. Ubuntu because - hey, look at
this nice GUI installer and then they expect GUI everywhere.....

Don't do PR of personal projects on mailing lists which are official
for different projects ;-) Of course that you can do your own project
based on OpenBSD, but take care with marketing.

Again, note the emoticon in addition to the approval to do whatever he wants just don’t announce it on the OpenBSD lists. How mean is that?

Steph and Tomas Pf added a similar advisory about the purpose of OpenBSD lists and linked to another thread in which a similar fork was addressed. They didn’t attack GNOBSD guy.

Mehma then asked Stefan (GNOBSD guy) if he’d be interested in working within the OpenBSD project. Was that over the top?

Chris D amused me with the following:

Generally the best day to post these announcements is the first day
of the fourth month of the year.

And if you're into product life cycle management, it's a wonderful day
for a product to be out of service...

To which Bret L replied

But the day these ideas are traditionally developed is on the twentieth
day of the fourth month of the year.

Then someone from the other site, taking the reviewer’s cue to whine about abject mistreatment and abuse, jumped into the thread. Scott offered (ummm…) “sage” advice about everything from how live Linux CDs work to alternative window managers to advising GNOBSD guy to keep at it and named him an OpenBSD developer. This was corrected by Ingo S — GNOBSD is a lone wolf, not operating within OpenBSD development.

Michiel vB responded to Scott’s mistaken notions in greater detail. He pointed out that many Linux live CDs don’t work. He also addressed Scott’s complaint that FVWM is “outdated” and reiterated the bloat factor of Gnome. The most pertinent point he could make, though, was pointing out that PCBSD users don’t support FreeBSD in response to Scott’s deluded point that GNOBSD supports OpenBSD. Michiel also wrote that the OpenBSD people are okay that this project is being done but they’re not okay that their list is spammed with its announcement:

We dont worry about others, except when they start using the OpenBSD
mailinglists as free advertisment channel for their crap.

Jacob M replies to Scott that live CDs are “legacy” now.

Over all, the most inflammatory post in the whole thread is Scott’s — and he was “defending” Stefan/GNOBSD guy. There wasn’t any hostility from the OpenBSD people. They asked that announcements not be made on their list, explained that they wouldn’t use it, that it doesn’t fit in with what OpenBSD is about.

I’ve seen a lot of bullshit in my years using and cooperating with open source projects. I’ve also dealt with enough assholes in the open source community to know how rough things can get. This wasn’t rough. This was pretty gentle, even diplomatic.

Those who think this was abusive must have some pretty thin skin. Then again, I’ve been banned for having the nerve to tell people that “respect is a two way street and you might want to look both ways before crossing it.” Imagine that.

It was disrespectful for GNOBSD guy to plug on an OpenBSD list. It was disrespectful for Ladislav to make a mountain out of a molehill and besmirch the OpenBSD developers when they were very even-handed about things — certainly more even-handed than he was in taking comments out of context and suggesting things were hostile and abusive.

It was also disrespectful that his sycophants think OpenBSD developers have to cater to their whims and demands. OpenBSD is its own project and has its own goals. They don’t have to be just like any Linux distro to “succeed,” particularly since the project hasn’t ever really seen fit to use popular adoption of itself as a measure of success (compared to security, proper coding, etc.). The project shouldn’t cave to petty demands by users who aren’t sophisticated enough to bother with learning how to use it.

{KDE,Gnome,GNOBSD} != OpenBSD

At the end of the day, though, only one person at Distrowatch was respectful (well, kind of… it’s funny how I’m always the fucking asshole in these situations when others first resort to calling me “troll” and then they make additional posts to pedantically explain the obvious) enough to honestly answer my question about how much difference there is between running Gnome atop Linux or OpenBSD. There’s no difference because Gnome isn’t Linux or BSD and using a desktop environment from boot until shutdown pretty much divorces the user from the underlying operating system. Unsophisticated users — like the one who prattled on and on about themes and configuration, as if an operating system is about aesthetics — don’t actually care what’s under the hood, they just want to be able to say they ran something they didn’t really run and that in reality they didn’t even bother or desire to understand.

Since it really makes no difference to them in any meaningful way, it makes this whole thing even more amusing.

Banned at Distrowatch, LOL

February 2, 2010

Haha, I’ve been blocked from commenting at Distrowatch. The funny part is some tard wanted to challenge my virility.

For the record, I don’t have a girlfriend. My better half won’t let me have one. Neither will the kids. (Edit: Out of curiosity, what’s more Darwinian: your “feelings” about how much action I get or that you actually have “feelings” about it? MYOB, putz. Stop thinking — worse, feeling — about my sex life and worry about your own.)

Here’s my last reply, which won’t post and redirects me to the DWW page:

SUBJECT: @unsophisticated users
@103: "Unsophisticated users" = those Windows/Linux users who won't bother
to actually learn OpenBSD but merely want to pad their "tried that"-resumes'
by running something pre-configured and dumbed down. Kind of like a couple
weeks ago with the whole automounting crap and an expectation based on lowest
common denominators that everything should work just like Windows. 

Just install OpenBSD if you want to run OpenBSD. If your goal is a Gnome
desktop, there are already plenty of Linux projects which accomplish that
and it's clear that the OpenBSD project doesn't care to participate in
attracting "market share" from those projects. They have their own
comfortable niche. They don't want to cater to the kinds of users who want
automagic everything.

Again, it's *irrelevant* what OS is running beneath your desktop environment
if you don't want to get your hands dirty with the OS. This whole thing is
amusing from that aspect because you people are acting like someone's depriving
you of something by not catering to the lowest common denominator of
(unsophisticated) computer user. I've installed OpenBSD 4.6 and its installer is
quite easy to use, even easier than earlier versions -- and those were pretty easy
for anyone willing to actually RTFM.

As I wrote on my own blog yesterday, "Dumbing the process down brings in dummies"
and that's not one of the goals of the OpenBSD project. It's not about snobbiness,
it's just about the project's goals -- and it's not that OpenBSD's goals are out of
step with people like you, people like you are out of step with OpenBSD's goals. They
respect your right to use other operating systems that will cater to your sort, so why
can't you respect their right to not appeal to users like you?

If it's out of step with the project's goals, why should they want someone to spam
their list with an announcement about a fork? If you don't respect the project enough
to work within it, don't be surprised if they express some form of rebuke -- in this
instance, I thought it was very mild -- when someone outside their own ecosystem uses
their list to advertise a fork. They don't owe forks or fork-ers anything. If you don't
work with them, why should they work with you? Answer that, please. 

What's up with the personal attack on my virility, lamer? Stop projecting and stick to
the issues. You *really* don't want to go there.

FWIW:



Personal note to Ladislav: I’ve been banned by better people from better sites for a lot worse. If you can’t stand valid criticism and other points of view, maybe you’re in the wrong business.

Oh Boo Fucking Hoo

February 1, 2010

I just read a “review” of GNOBSD over at a certain website. It was less a review than a timeline of the guy creating a live Gnome-based live DVD using OpenBSD 4.6 and how some in the OpenBSD community reacted when he advertised it in their mailing lists. He withdrew his ISO due to server traffic and less than positive feedback from the community.

He’s not the first to fork from or base something on OpenBSD. He won’t be the last. He’s also not the first person to receive a rebuke of some form from those in the OpenBSD development (and user) community.

I looked through the thread. I didn’t think any of the comments in the thread were incendiary. Some had smilies. Some directed the poster to another thread from last year about a similar issue. I’ve seen much harsher treatment where it’s more deserving. This was all fair and even-handed.

I also think the reaction of the OpenBSD development community might have been a bit different if this GNOBSD guy had first become involved within their community rather than working outside their ecosystem and then advertising a derivative out of the blue in their email lists. Dittos for the guy in the other thread for his “remix” last year. For starters, it would’ve given him an understanding of the community his work is potentially disrupting.

Yes, disrupting. I don’t buy the argument that separate, forked projects like this are of benefit to the upstream project. OpenBSD development is funded by sale of their release CD sets. People downloading an ISO are unlikely to go to the upstream project and support it (just like all the software, music, and movie pirates have a disincentive to go buy more software, music, and movies despite all the fucktards who think they’re acting in the interest of artists when they take it upon themselves to violate copyrights); unfortunately, they are likely to go to the upstream project and ask inane rudimentary questions the developer teams have already answered in their documentation — from their own guides to their man pages. Dumbing the process down brings in dummies. That’s not beneficial to their project.

(Yes, dummies. What’s the fucking purpose of installing something like OpenBSD with a graphical desktop preconfigured if you can do that already with Linux or something else? If you’re unwilling to understand what you’re doing and unwilling to configure it to work exactly the way you want, then you’re looking at the wrong operating system. Stick to your Ubuntu, stick to something that you don’t have to or want to comprehend. Gnome and KDE aren’t Linux or BSD, they’re Gnome and KDE. Most apps can be compiled to run in Windows, so your “friends and family” don’t even have to switch operating systems to see, try, or use them.)

So this is a lose-lose proposition for OpenBSD developers. If they wanted to expand their market share, they already know what they could do — and they’re not doing it. OpenBSD developers are talented enough to assemble such a project if they wanted to. The fact that they haven’t should demonstrate that they’re really not interested in a market-share or dick-measuring contest with other BSDs or with Linux. Accept it.

And to the whiners and bitchers (10, 19, 22, etc.) over at Distrowatch who say they’ll either stop using OpenBSD or never try it over this episode, good riddance. You’re probably not the kind of users Theo&Co would want anyway. Grow a pair.

Update 20100130: Musical Hard Drives, NetBSD, Scientific Linux

January 30, 2010

I’d alluded last weekend that I’d installed NetBSD on a spare hard drive in my new workstation. That drive was the last (I think) OpenBSD 4.3 install I had before I had to go care for family in 2008. Hard to remember anymore, I only know that when I ran last it showed my last reboot was a couple days after I returned last year. Anyway, I’d already installed Scientific Linux 5.4 on another spare hard drive I put in the workstation and set up separate partitions on it. My only nitpick about SL’s installer on the live CD version is that it doesn’t allow many options as far as partitioning or filesystems but that’s not a big deal to set up afterward. (Note: the full install/net install CDs use anaconda.)

I switched drives around so my old OpenBSD 4.3 one would be master. Once I logged in (after finally remembering my root password and changing my user password), I looked around and saw a few things I wanted to make sure I backed up before using that drive for something else. I added entries to my fstab for the other drive so I could copy them to my user account on it (that drive is eventually going into another computer; sorry about image quality but I didn’t have the computer networked when I set up).

I recently said some unkind things about the reviewer of a NetBSD-based live CD on a certain website because he complained that it didn’t automatically mount things for him. The BSDs — excluding possibly desktop-oriented projects based on any of the BSDs — don’t enable such things by default. I also recall in a simulated install of KDE packages one time that directions flew up my screen about enabling various daemons to get it all working if so desired. It’s just a different perspective on things. The BSDs are true to their Unix roots, and Linux distros by and large are true to their “GNU’s Not Unix” (heavy emphasis on “not”) roots. Let me be a little more constructive than I was at that website and show how easy this stuff is (especially if you bother to read the documentation).

I installed NetBSD from CD. The installation took a few minutes. Granted, it’s not like installing the average Linux distro — it doesn’t have a graphical installer, it doesn’t have all kinds of apps to install. It’s pretty basic, but you add what you want on top of it instead of whatever some developer decides to include. It’s fast, it’s easy (RTM), painless. It takes a bit of time to configure and set up but it’s a blank slate and you’ll know exactly what’s going on because you’re the one turning all the stuff on that you want to be on.

I wanted to get my files I copied over to the SL54 drive from the OpenBSD install so I decided to set up /etc/fstab to include my SL54 drive. The first command I ran was dmesg | grep wd1 to make sure the drive was detected as wd1 (the next step would tell you the same thing but I usually look at dmesg first). Then I did disklabel wd1 to get information (man disklabel if you want specific options) about the partitions on that drive.

Once I had that, I could edit fstab accordingly and/or mount the partition I need. In this case, the partitions I wanted were g and i and I needed to make directories (mkdir /mnt/wd1{g,i}) for them and then mount them. Then I was able to get my stuff I’d copied from my old OpenBSD install as well as the few things I’ve had time to get on the other SL54 drive. Hardly a hassle.

I haven’t had time to do anything else with that drive (meaning with NetBSD) yet because things are hectic with family and work. Funny how that works out sometimes — get a new computer, fiddle around with a couple of hard drives, and then have to get back to them in a week or two or three (I’ve only been using SL54 on it). For what it’s worth, I’m very pleased with Scientific Linux 5.4, which is compiled from RHEL5 sources. I’ll write a review of it soon — and probably before I get back to setting up NetBSD.

Freedom, Security, and Lacking Credibility

January 22, 2010

This is in response to something on another site.

Just a quick note to the whiny little fucktard who wanted to lecture me on another site about credibility: screw you.

Every time you asked a question or made a point, I gave a rational and coherent explanation. That includes my own example of why someone wouldn’t necessarily want to automatically run a server despite installing such software. That includes the issue of blind trust via social engineering that could lead someone to install something which unknowingly could present an issue with respect to something on a USB stick “automagically” starting without your knowledge or consent or interaction. Etc.

Oh, but it’s Linux! No fucking worries here. Ever!

That site has become something of a joke, especially the distro reviews (where did Caitlyn go?!). I pointed out that BSDs are not Linux only to get a response from the author about “old ways” as if some isolated KDE-oriented sub-project supersedes the one on which it’s based. You know, as if an exception overshadows the norm. Last time I checked, not one of the three major BSDs sets up automounting by default (and why the fuck should they? certainly not to match the Linux world by starting extraneous processes by default). That “last time” was yesterday when I installed NetBSD 5.0.1 on my new workstation. Works the same as it always has: insert USB stick, console messages (haven’t set up X yet) show me it’s there, “disklabel  /dev/point” shows me what partitions are available on it, then it’s straightforward to mount it and/or add entries in /etc/fstab. Duhhh. But probably not so straightforward if you expect it to work like Linux Windows without ever reading any documentation. Just burn the image, boot it, and wonder why you have to set up something because some developer didn’t do it for you.

By the way, the “Linux way” the author prattled about in his review used to be the “BSD way”: users were given control of what gets mounted and when rather than developers taking it upon themselves to dumb everything down so Windows converts would feel more at home. The “Linux way” is an anti-Unix way, it’s really the Windows way. And it’s apparently a flaw if a reviewer has to ever RTFM to learn that he has to manually add extraneous filesystems to his computer. Let alone manually mount something in the first place.

Unix isn’t Windows. I loathe those who demand making Unix more like Windows. It won’t attract more users. It hasn’t thus far. All it does is piss off people who have to go undo things that shouldn’t be done in the first place for a wide variety of reasons (yes, fucktard, including security — no matter how remote the risks might be, as I pointed out at least twice).

Auto-mounting is not a “feature.” I accept many users may indeed want it — we’re talking lowest common denominator and that’s going to be a lot who don’t bother or want to RTFM. That doesn’t mean it should be configured without user interaction of some sort.

If Linux and open source is ultimately about freedom, then stop forcing users to accept myriad running services in the background until they realize they have a lot of bullshit to undo and instead offer them opportunities to start what they want/need at install. Some distros do this, but most don’t. Isn’t it telling that the distros most popular among Windows users and converts give less freedom at install than Windows itself does? And isn’t just as telling that the Linux distros and BSDs that want the end user to have the most freedom and flexibility are the ones that give users a blank slate and tools upon which to build what they want/need and also seem to have an eye on things like stability and security?

But never mind my lone opinion. As the aforementioned fucktard suggested, nobody can take me seriously. I lack credibility because I think users should decide when things start or mount or are added to any system rather than a developer taking such liberties. Go read the lame reviews, pat the author on his buttocks, and wonder why more distros aren’t just like Windows — or wet your pants over the ones that do take all the decisions out of your hands… while you probably write snotty things about Microsoft for doing that very thing. Putz.

Update 20090817

August 17, 2009

I’ve been busier than expected the past few days. Taking a bit of a break this afternoon to clear my head. Here’s a little update of what’s going on with my computers.

My AA1 continues to be my primary computer, for better or worse. I’ve decided I really need a bigger, faster laptop for full time service. I’m looking at a used high-end business model and also at new mid-level business models now. I’ll probably continue using the AA1 quite a bit since it’s by far the easiest to tote around.

I’m really hard pressed to say I’m still running CrunchBang since I’ve removed a lot of its defaults and replaced them with other things. If anything, it’s more like un-buntu. Nothing against CrunchBang but, even though I think it’s certainly a decent implementation for users wanting less point-click bullshit and less overhead, I think it could benefit from changing window managers and some of the default stuff like the tint2 panel and conky.

I’m still using ion3, which I’ve “fixed” so it doesn’t get full primary use of my function keys. I basically run two “desktops” in it. The first is full screen for well-behaved applications; the other is split so about 30% of the screen is used by the smaller windows of multi-windowed applications like GIMP and Skype. Simple and works for my needs.

I’m also using TinyCore and MicroCore more often but I haven’t had time to finish compiling some of the apps I want. Once I do that, I may enlarge my second Windows partition and reduce the Linux partitions, and get rid of CrunchBang or un-buntu or whatever the hell it is now. I hope to have more to add about all this shortly. {Micro,Tiny}Core is really growing on me.

I’m using NetBSD on my last remaining home server, which I was about to set up as my VPN server. Unfortunately, the server is just about FUBAR. I think the mobo is shot. Regardless, I’m going to scrap it if I can’t figure out if it’s just a bad ribbon cable. It was a rescued MMX box so no big loss. I got a little over a year’s service out of it. I’m thinking of using my old ThinkPad as a VPN server. It’s probably a fire hazard so that could be interesting.

How have I tried to clear my head today? By getting some stuff set up (config files and such) so I can transfer it over to MicroCore, writing a script, etc. I’ll do a separate posting on all that this week. Maybe a video, too, to show the speed and efficiency of console applications and how they can be integrated to work together.

Update 20090713 am – Miscellaneous

July 12, 2009

#! JWMRC STILL TO-DO
I didn’t boot back into #! until late last night. I’ll try to edit the jwmrc later. I’ll add screenshots to the previous entry momentarily.

DSL ISN’T DEBIAN-LITE, IT’S NOT A JUMPSTART TO DEBIAN-STABLE!
I still get a ton of hits for DSL-related things. I see in the search engine terms for today that I already have someone looking for how to use DSL to install Debian. Don’t! I can’t believe people still think they can do this but it’s not a jumpstart to a small Debian system. Go read my hard drive install page linked up in the top right-hand corner on my blog (click on the banner to to “home” if you’ve landed here and the links in the right column aren’t visible).

In a nutshell, DSL was based on an old version of Knoppix which was based on a now-deprecated version of Debian. Debian no longer offers any support for that version (which was called Woody). You cannot do a dist-upgrade from DSL to Debian-stable without breaking every freaking thing in the system.

You can still use DSL as it is but it appears development has ended. I haven’t seen if John Andrews has posted a roadmap or even announced what he’s doing development-wise.

If you want a small-ish Debian system, the best idea I’ve seen is Kerry’s which he’s posted in various forums including at DSL, IIRC. I searched and found it at the Ubuntu forums again just now. You can use that with any net-install-able distro like Debian, Ubuntu, Fedora, etc. The BSDs require a bit more work but also can be used to create lighter systems. Etc. If your computer can run Slitaz or a POS distro like Puppy, you can run Tiny Core and build a light system, too.

WIFI BS
I’m still a bit anxious about how this Atheros card is performing under Linux. I’d hoped the more recent kernel in #! would resolve the matter. I’d suspended and resumed a few times to see if it would flake out on me, but what happened yesterday was the longest time it had been suspended while running #!.

I’m also noticing that my transfer rate is swinging wildly from 1 mb/s to 54 mb/s. I’m going to have to delve through more bug reports and see wtf is happening. I knew the other stuff I’d experienced with older (and apparently not patched as much as I thought) kernels was a known issue. I haven’t looked to see if any other reports have been filed since the big re-write. I compared my signal using my old ThinkPad which uses a Broadcom card and the wireless signal strength, transfer rate, etc., seems more stable with it.

I also need to double check my warranty. I know it’s supposed to be one year but I don’t remember the fine print to see how nitpicky it is. If it’s voided, I may bust this thing up and find another card.

(Edit: Signal strength and rate isn’t an issue in Windows, only in Linux. I likely won’t change the card unless I decide against upgrading to Windows 7.)

Update: Fedora 11 Live CD/USB Fail

June 9, 2009

Note, what follows has been updated in this entry.

I was going to applaud the decision of Red Hat and the Fedora developers for delaying the release of Fedora 11 a couple weeks to iron out some wrinkles. And they deserve to be commended for not rushing something out that they knew would have to be fixed very quickly. I don’t think things should be released as slaves to a calendar but should be released when reasonably ready.

Unfortunately, they didn’t fix enough bugs — or, perhaps, they broke some things along the way (after all, I chose the Gnome version of Fedora 10 after being put off by KDE 4.2 in a preview of 11 which actually booted correctly for me). I couldn’t get the bleeping live usb creator to work with the new image.  Actually, I couldn’t boot with either the Gnome version or the KDE version. When I’d boot from USB, I’d get a white-grey gradient GRUB splash looking thing without anything else visible. I finally got a “boot:” prompt by hitting escape, and I knew the kernel was vmlinuz0. Everything looked fine until the kernel panicked. I was able to get the GRUB menu when trying it in qemu but the boot was too slow and I didn’t have enough time to let it boot all the way. I gave up.

Turns out there are some issues beyond what I was able to discover the hard way. Like how those who want to install from the live CD versions need a very particular partitioning scheme with an ext3 /boot and ext4 /. Fuck that. I wasn’t planning to be yet another guinea pig for ext4. The good news is users maintain more freedom along those lines using the standard CDs rather than the live ones.

No idea if I’ll ever do that. I’m still wavering between going with something a bit more conservative like Slackware or Debian or one of the BSDs (NetBSD most likely, which I’m also about to install on another server here). I’d consider RHEL/CentOS if my hardware were adequately supported yet; I don’t need to be on the bleeding edge every six months, I just want shit to work right and to have support long enough that I don’t have to upgrade or install something twice a year (how old is XP again? and how long has MS supported it?). I ran Debian Live (Xfce version) on the AA1 earlier this evening and was impressed how nimble — from USB — it seemed compared to other things I’ve tried.

Tiny Core is kind of off my radar right now, but not because JWM is back as the default window manager. It’s obviously progressing and maturing quickly; I just don’t think it’s ready for production use yet (at least for what I need). I also want full use of commands which are limited in busybox. By the time I add everything I want, I’m getting very close to what I’d install in a “full” distro. I’ve booted the new release (2.0) a few times now. Haven’t set up wireless yet, but played around a while over wired networking. I was unaware of the Micro Core non-X release from Team TinyCore until I read Robert’s release notes. I’ve booted it now, too, on the AA1. Could be kind of cool to run in a non-X environment (which I do mostly when I use PCLOS) and also to run a full X server in lieu of k-drive. I’ll probably leave Micro Core on here regardless so I don’t have to deal with that wobbly wbar piece of shit at the bottom of the Tiny Core default desktop (bugfix: pkill wbar).

I currently have Windows XP, PCLOS, Fedora 10, and Tiny/Micro Core installed on my AA1. I was hoping to post today about the tedium of backing up stuff and repartitioning, along with my impressions of using and installing Fedora 11 so that my hard drive only had XP and Fedora on it. Now I’m pretty close to scratching it off my list. Just like I’d already done with PCLOS.

De-Bloating PCLOS on AA1

March 23, 2009

I’ve been a lot busier today than I was supposed to be so I didn’t have time to make a bigger dent in the overhead that’s part of a PCLOS install. That didn’t deter me, though, from setting up a very nice and light runlevel 3. Still have a lot left to unbloat, but I’m making a little improvement on a daily basis.

The pay off for my efforts? I’m only using about 50MB at boot into console with ksh as my shell. It’s a bit over double that after startx into ratpoison, starting aterm, and executing free. That sets me up using about 10% of my RAM at the start of a session, which is similar to my old DSL setup on my desktop

This is likely all for naught. If I can get more than a few minutes here and there, I’d really like to install something that gives me a clean slate to buld upon rather a bunch of extraneous stuff for me to remove, shut off, or recompile. Can’t wait to see how screwy things get when I start removing KDE stuff. I’m still considering  FreeBSD and NetBSD, but leaning more towards Slackware-current. Wish I had more time now but morning will be here too soon.

Edited 20090324: Boring screenshot.

screenshot-20090324041208