The first tutorial coming from my custom-distro experiments. Since it's a good idea to start at the beginning, here is... Booting with runit.
Well, I am still experimenting with my concept-distro.
I am now up to a running PyQt using uClibc, which I thought unlikely ;-)
I completely removed all the sysv init stuff, and replaced it with runit, which has an interesting effect:
It boots to a graphical login in about 15 seconds. Inside qemu. In a 900Mhz duron. Including kernel loading.
Of course the trick is that you have the login while stuff is still loading, but I am working on that, too.
Since using runit it's pretty simple to get a overview of where the booting process is (services have dependencies, they simply get started in order, and in parallel), I will hack a system-wide ksplash-like thing on a side of the xdm (probably will end up writing my own whateverdm).
Think of it as Fedora's rhgb, only you can login instead of getting bored.
I also switched to a root-free system Ubuntu style. Not decided yet on it, but it's not hard to do (or use).
Next step: hack Knoppix HW-detection script (or rather rewrite them in a real language).
I understand why there are 743 Linux distros. It's quite a lot of fun to hack one together.
Oh, and it needs a name. It's not going to be useful for anyone, it's just a personal toy, but it needs one.
Come on, Planetkde guys, throw me names for a non-unix like linux, if you dare ;-)
I am no fan of source-based distributions. I think that for most practical purposes, a distribution where installing KDE takes over a day (I own a lowly Duron as my fast computer) is useless.
However, they are good for one particular niche.
Custom distributions. Weird distributions. Personal distributions.
I have several computers. Most of them too slow and small.
As I was considering reinstalling Linux on my Libretto for fun, I looked at what was installed in it, and decided that really, 90% of it was of no use whatsoever.
The problem was, since it had Debian installed, it has a rather wide network of dependencies that simply could not be done without.
On a regular computer, that's not an issue, but in this tiny workhorse, with 16MB of RAM and a 800MB HD, it makes a lot of difference. The smallest I could get Debian to be, and still have network, PCMCIA and X11, was about 250MB.
And the performance was not awesome, either (but not terrible).
So, what would happen if instead of a regular distribution it had something like this:
uClibc instead of glibc
runit instead of SYSVinit
dropbear instead of OpenSSH
X built as kdrive (formerly tinyX)
python/qt (or maybe python/fltk) for basic admin tools
And so on. Basically rejigger the whole software selection slanting it towards the small side, and dropping a bazillion non-fundamental dependencies along the way.
Well, it can be done. It's just that it's a heck of a lot of work. But here, a source-based distribution gives you a headstart.
For example, I decided to start from ucrux, a uClibc-based port of Crux. Since the native toolchain in ucrux is uClibc, I don't have to worry much about a whole class of mess that happens when you build uClibc-based binaries on a glibc-based system (it's practically cross-compiling).
Qemu lets me install ucrux and work on it somewhat faster than on the target P75 (if I could make KQEmu work I'd be happiest).
Since crux's software packaging mechanism is simplicity itself (a shell script that installs to a fake root), although it's severely underpowered (no dependencies), I can start from ucrux, hack the build of one package at a time, then put everything on a CD very quickly.
So, if you want to hack your own distribution, Crux (or some other similar kit) is quite a nice thing.
For general use... well, my requirements start at apt-get or equivalent ;-)
Now, if only TinyCC worked for more programs, that P75 would be a pocket development powerhouse!
Ok, as everyone and its goat in the free software/open source/pet-keeping communities already has read, Eugenia  has been up to her old antics.
The latest shape of her discontent is, developers of GNOME (and lately of KDE, too ) are developer-centric instead of user-centric.
Basically, the gist is that developers have a responsability to keep in mind their users desires, and follow their wishes when deciding what way their projects should go. That these "people" are developing said software in their free time and giving it away is unimportant, she says, the user's voice shall be heard. 
Well, I am not a developer nowadays, at least not of shared software  but I still recall when I was one. And I am cranky. And I have little care about what people think about me. So...
Let me express my feelings when I read her editorial (and another one called the riddle of the sphinx, I think  ).
I have read, in the editorials and (specially) the clueless talkbacks, the following:
If you are going to do a half-assed job, don't put it on the internet
Well, dude, pretend it's not there. That works for me when I consider japanese tentacle porn, it can work for you and a mail client. If you pretend it's not there, it won't bother you. Then those who tolerate half-assed jobs can live a life of jolly fulfillment.
The user has invested effort on learning and using the program, so the developer owes him something.
I suppose the solution for that is not allowing people to use the software unless they accept that it is provided as-is... oh, wait... that's already true. Never mind.
That since GNOME (or KDE) claim to provide useful and user-friendly software, by failing to follow the user's lead we are engaging in some sort of false advertising.
Coca Cola promised me "Everything is better with Coca Cola". Then I tried pouring a can into my computer, hoping it would make it faster, or somehow better in some way. I have to tell you, those bastards won't know what hit'em!
Posting bug descriptions in bugzilla is too much work.
Well, try fixing one someday, missy! That's WAY harder. You are saying that using a little energy is too much work, to people who spend hundred times more as a consequence.
It's like complaining that planting seeds is too much work, when you later get a harvest. Well, if you think, so, drop agriculture.
That the development is somehow skewed towards developers, not users.
Well, to that I have many answers. Let me share a few.
So? You say that as if it's a bad thing.
Well, that's good for the developers.
What magic potion did I have to drink to become a developer? Developers are just users who are way too involved in the project.
As a lawyer once said, since phoenicians invented money, the question "what can I do for you?" has a single answer. Well, think about it.
No, it isn't.
Finally, let me tell you the depressing part. In a comment, Eugenia said she dropped GNOME for WindowMaker. Let me show you what she said:
RE: So Eugenia refuses to use GNOME? By Eugenia (IP: ---.osnews.com) - Posted on 2005-03-10 20:32:31
I moved back to WindowMaker, yes. At least I don't expect anything more from it, because it is not a prominent environment and I know it's a much smaller project with fewer responsibilities.
Talk about throwing the baby away with the bath water. She is simply saying that she choses to use worse software (according to her needs), because... well, I have no idea why.
Because she has low-enough expectations about WindowMaker that she won't be disappointed? That road leads to dating ex-convicts, you know.
In the end, well, I have no idea what people think. I simply don't understand the world. I mean, I intensely dislike GNOME, and even a few people involved in it, but it's just code. And code that is worth millions of dollars. And it's there, dudes! It's like finding a stack of bullion in your doorstep, and not only that, but on every doorstep .
Why don't people simply look up and thank the invisible dwarves who must have toiled in darkness for years in order to rip it off the earth? 
No, what we get instead is a bunch of jewelers asking for finer craftsmanship in the goods, or else they are just gonna buy some bullion from someone else.
You know what? Developer-centric is good. In an absolute, objective, measurable way. Because it's developer-centric you get developers. developers make code. Code brings users.
If all you attract are users because being a developer is a pain the butt, you have no developers, thus no code, thus no users.
What do you think is better for users in the long term?
So, say it loud, I'm developer-centric and I'm proud. At least this old hack is.
 of OSNEWS.COM fame. You decide if that's a good or bad thing.
 A new post in her site. I suppose she has to feed the hit-monster.
 That being published in a big site that lacks threaded replies in 2005, and a woman who, when she gets a complain about it, said she was doing it in her spare time, so stop bothering her. No, I don't get it either.
 Isn't that much nicer-sounding than open source and much less annoying and pompous than free software?
 Which is, I think, #4 in the list of "ten titles you should never use in an opinion piece". #1 is What I did last summer, but I digress...
 And by some economic miracle, it hasn't caused yet a global depression in the value of bullion.
 Well, at least we work in comfortable chairs.
Here's the challenge: a nicer version of Qt's data-aware widgets, using PyQt.
Did I succeed? Probably not, but it was interesting to do. Maybe it will be interesting to read about ;-)