I'm responsible for a bunch of servers now.

One of them has a uptime of 660 days. Other, 120 or about it. My server with the lower uptime has 35 days - it has 37 days of life, by the way.

I'm not slightly interested on the booting speed of these machines - my main concern is the speed of the diagnostic procedures I need to carry on when something goes wrong.

God saves the runlevel 1.

What's not necessarily a bad thing, as History tells us.

That's the problem: it's too damn flexible, it's too damn practical, it's too damn EASY to maintain. How in hell a big enterprise will be able to profit on such environment?

Corporations need hard to maintain, almost impossible to learn systems deployd on their customer's machines in order to keep them under their grasp.

It's what is happening with systemd? I don't know. But I know the past, and this is the path that Microsoft, Oracle et all choose to follow - and this was not by accident.

The system ends up booting by a series of well placed accidents.

DMS => DMG

(sorry the typo)

So it was you? Bastard! :-)

Jokes aside, we setup our own server - you would have to portscan half the Internet in order to find our server to DDoS us. :-)

Setting your own game server is Quake 1's most missed feature to me, the rocket jump being the second! :-D

I prefer to respect people for their opinions, not their grammar. As you can easily note. ;-)

Well, now they have. Why Lizard Squat took so long? =P

I didn't knew. By the time I wrote that, I hadn't received any report on a MSN Live attack yet. Now I have.

Why do you *NEED*?

Why the statistical spread of man and womans *NEED* to be equal on the various fields of human knowledge and/or work?

EVerybody must, or at least, should, be able to choose whatever he/she wants - if she/he is able to do so. What I don't get is the use of the verb "NEED".

Why wornens *NEED* to work on I.T.?

Well... I was never DDoSed when playing Quake I's Team Fortress with my friends. :-)

If they manage to repeat the deed next week, you can bet you gamepad it will affect Sony.

Mainly because I don't see MSN Live players complaining about loss of service, do you? XBox owners don't have any reason to fear losing next weekend services, while PSN users will live the week worrying about.

I just paid my taxes. Next month, perhaps?

And yet, cars and airplanes and bicycles and a lot of other tools (some more complicated, some less) are still being engineered by engineers.

I don't see a link here, sorry.

Dealing with (some) corporate egg headed's wishes on how people should use a computer is that it's quite different.

Common People are using computers since the 80's. Some metaphors sucked a lot, some others was successful (and some, besides sucking). The break even point was simple: I work/play/whatever better now that did yesterday?

Cars use steering wheels and pedals since Ford's era, besides a lot of research on new ways to drive a car. Did you ever considered why?

That would had helped a lot, indeed.

Successful to whom? You see, people are not all alike.

Now I see.

Perhaps this happens because is considered BAD ENGINEERING creating something out of the blue just for the sake of it.

There's a good reason cars are still using steering wheels and pedals nowadays - people don't have to be trained and reissued a new driver's license when they sold the old model and buy a new one.

Any nowadays stereo are still using the same metaphors from decades ago (Play, Stop, Next, Previous, Volume Up and Down - even the Eject are still used), and the remote control from my new shining OLED TV has the same buttons my old, ultrasonic, mechanical remote control had (but granted, it has that buttons and a lot more).

Of course modern remote control are a lot more sophisticated and useful that hat old craps, but the basic metaphors are still there - the enhancements were introduced rationally, without breaking current usability.

Why? Because this is considered *GOOD ENGINEERING*.

Because it's already proven that he is capable of handling successfully huge and complex open source projects.

Just because he never did it, doesn't mean that he doesn't have the skills neither. However, he's a proven open source leader that delivers solid artifacts, with a nice (but granted, far from perfect) historic of consistency between releases. I prefer to do not make comparisons with some other Open Source projects - there's no need for a jihad here.

I'm not hiring the guy to write code or specify usability requirements. But you can bet your arse I would hire him to lead a critical software project anytime (if I would be on such position, what can be a good idea to state now that I'm not).

I agree 100% with you here. :-)

Weirdly enough, this never crossed my mind. Perhaps linking this conversation to him?

Me too. The guy is a god damned good engineer with a good leadership skills on Open Source projects. I don't see how his geekness can influence on it - but granted, I'm not entitled to say otherwise.

By the way, I'm not saying he's a polite, nice leader - au contraire, the man can be an ass when pissed on. But again, the guy stills delivers solid artifacts - thanks or besides his assness, I can't say.

Being that the(or one of them) reason you stated before that the Kernel is less complicated and easier to keep than a Desktop?

How the KDE folks are dealing with this issues?

From my point of view, they can shove =P the buttons where they want. Just give-me the choice to move them back to where I want, and I'm happy.