Comments on: Stupid mistake, drastic solution

By: hal’s day of reckoning « Motho ke motho ka botho

hal’s day of reckoning « Motho ke motho ka botho — Tue, 22 Jun 2010 14:08:00 +0000

[...] blame upon hal whenever something went southward in a system I built. Forgetting to start it up has killed more installations and caused more filesystem errors than I can count. Just managing an international keyboard with [...]

By: Tundro Walker

Tundro Walker — Tue, 21 Apr 2009 02:45:20 +0000

Had the same thing happen while jacking around with an old i-opener. Tweaked the xorg.conf, startx … freeze. Hard booting on an ext2 file system sucks, since FSCK starts going bonkers trying to remedy the corruption. Ended up having to reinstall, this time on ext3. Figure I could live with a less snappy system as long as journaling provided a wee bit of protection against data corruption in such cases. Maybe not.

By: K.Mandla

K.Mandla — Tue, 27 Jan 2009 20:54:22 +0000

Nope. I couldn’t touch or read them at all. It was as if they didn’t exist, but they did, but were off limits. Ghosts, maybe. …

By: johnraff

johnraff — Tue, 27 Jan 2009 15:25:44 +0000

fsck no use for those corrupted files?

By: K.Mandla

K.Mandla — Wed, 21 Jan 2009 23:08:32 +0000

Unfortunately, Mike is right. I compile in SysRq support but X completely ignores anything keyboard-based. I’m going to stop short of calling it a bug, but this, to me, is one of those situations where the default behavior of one program is impeding the core system functions, and unless you take one careful step and tell it not to do something, you end up like I did. …

By: Mike

Mike — Wed, 21 Jan 2009 22:21:28 +0000

I’ve found that if X siezes up completely, SysRq is useless. A hard reboot is the only solution.

By: Dieter_be

Dieter_be — Wed, 21 Jan 2009 18:40:45 +0000

A shot in the dark.. does crux have sysrq support in its kernel?
If so, you can do a pretty clean shutdown by passing some commands straight to the kernel. See http://en.wikipedia.org/wiki/Magic_SysRq_key