I hold a grudge, I admit it. Months ago, when X started acting up on my central machine, I realized the time and effort spent trying to fix it could be alleviated completely by omitting it altogether.
And as I mentioned then, things have only gotten better. Steering clear of X and anything related has slimmed the system down to nothing without losing a sliver of function, made my system far more reliable, and taught me a thing or two about using still older machines.
But thinking back, my grudge goes deeper than just the failure of the siliconmotion driver (something, to my knowledge, that still doesn’t work), and really extends all the way to November, when all of X turned sour for me. When X shifted to a reliance on hal and dbus, and I had to rely on obscure options (that don’t seem to work anymore, I should add) to avoid using them, I realized the relationship had gone south.
Nowadays I’m hard-pressed to come up with a reason to like X as it travels in the direction it has taken. Consider:
- hal and dbus are heavier than I like. I realize that both are a mere speck in the grand scheme of things, but to me, it’s still more processes than used to be required. I am not so much of a code monkey to fully understand all the reasons why they’re necessary, but I know it has made things harder on me.
I’ve scrambled a half-dozen installations simply by forgetting to start both hal and dbus before starting X, and without some sort of fallback or preventative check, the only result is that complete lockup. Power down the hard way, file systems go nutty, and the system needs major surgery to get back on its feet. 😐
- I don’t know what else to call it, so I’ll just say it: I don’t like the dontzap behavior. I got used to having CTRL+ALT+Backspace, and I’m one of those people who thinks there ought to be an escape route by default, not as an add-on.
If X were 100 percent foolproof, if it never made a mistake and configured everything correctly every time, I couldn’t complain.
- But it doesn’t, and correcting it when it goes wrong is just as much work as setting it up the old way. In some cases, it’s actually more. As an example, I exchanged e-mails for a few days last month with a person setting up keyboard-switching in IceWM. To hear it explained, the old system required only a brief edit of xorg.conf, but the new arrangement needs much more attention.
I don’t have the final details so maybe it’s not fair to hold that up to scrutiny, but it’s the way things seem to go for me too. My Inspiron, with an Arch installation in place (and yes, with hal and dbus running 🙄 ) can’t find the touchpad, or any of the four buttons unless there’s a PS2 mouse connected. It can find the pointer stick — which is important — but if there’s no mouse plugged in, it’s buttonless.
Maybe I’m being hypocritical, since I obviouly still use X on the Inspiron. I’m pleased to say that you can still run a hal-less and dbus-less system with Crux, but I get a sinking feeling every time there’s an update within xorg, because I know at some point that’s going to change.
Or maybe I just complain too much, and do too little, and should take some of my own advice. But instead I take the roundabout solution, and like I mentioned, I omit X altogether, for at least two (and sometimes more) machines.
That’s because short of fully preconfigured systems, like Ubuntu, I see now that X is not nearly as useful (or important) as I thought it was. Or maybe I should say, I see now that there is a lot to learn — and a lot to be gained — by leaving it out.
Rumour has it that Google’s “Chrome OS” will do away with X altogether. Considering the base platform for it is Linux, and it’s geared primarily toward netbooks (very similar in capability to older desktops and notebooks), it may be a better balance.
I know you’re no fan of the cloud, but the premise could yield something worthwile.
I’m sure when Google says that Chrome OS is X free, they just mean that they’re going to hack a solution to display their Chrome browser as full-screen and run everything from within that.
You can run X without hal, add this to xorg.conf:
Option “AutoAddDevices” “off”
and configure everything else there.
And of course it is possible to turn off dontzap:
Option “DontZap” “false”
I doubt that’s their approach. It’s really silly to force everything on the net. And even sillier to force a browser to be the desktop. No matter how “stable, fast, secure” blah blah…
There’s just no way a significant portion of the computer literate population is ready to store their lives on the cloud.
Google does have enough cash and manpower to come up with something new. I have a feeling this was in the works for years. Remember when people were getting curious as to why Google suddenly needed OS experts when they checked for available jobs at the company? Even though they were running Linux machines, why experts on operating systems? Why didn’t they just stick to “Linux experts”?
I have a feeling this isn’t a YAD (Yet Another Distro).
You guys are slow! It has been proven decades ago that you can live, eat, work, sleep, read porn, flirt the opposite sex, and get laid within Emacs, and Emacs can run without X! Plus, according to one of the official names of Emacs (Eight Megabytes And Constantly Swapping), we only need 8 MB of RAM and that’s it!
Long live Emacs 😀
— Proud member of Church of Emacs, time to chant the source code.
The innertubes sayz that the dontzap change was required by Emacs users who seem to mix up Ctrl+Alt+Backspace with Ctrl+Alt+Del once or twice a decade. Whatever the real reson for implementing this ‘feature’, it does way more harm than it solves anything.
Yet another thing one can rely on down the drain…
Oh, forgot to comment on HAL and DBus…
Bloatification for the win!
Pingback: A three-year hall of fame « Motho ke motho ka botho
Pingback: Carving out the garbage « Motho ke motho ka botho
Pingback: Unsolved mysteries: X in 1Mb « Motho ke motho ka botho
Pingback: An X for every application « Motho ke motho ka botho
Pingback: A Windows XP-ish Debian at 120Mhz « Motho ke motho ka botho
Pingback: What was I thinking? « Motho ke motho ka botho
Pingback: Your way is the right way « Motho ke motho ka botho
Pingback: Ubuntu Netbook Edition 10.04 Beta 1 « Doesn't Not Compute
Pingback: That split-second realization « Motho ke motho ka botho
Pingback: hal’s day of reckoning « Motho ke motho ka botho
Pingback: Xorg or Wayland: Color me disinterested « Motho ke motho ka botho
Pingback: Still with ConnochaetOS « Motho ke motho ka botho