> > The answer is /proc/sys/kernel/sysrq and it's been given already, but I have
> > a followup question: why? In early 2.2 you could say Y to sysrq in config,
> > and you had sysrq. Then someone added an extra hurdle in /proc. So now we
> > have this mechanism by which you can get the kernel to do a few things even
> > when userspace is hosed, but it's only good if you can
> > echo 1 >/proc/sys/kernel/sysrq first. What good is that?
>
> What good is that? A lot of good - you just make that default! Just edit
> /etc/sysctl.conf and most of the time (except before you execute sysctl
> from /etc/rc.d/rc.sysinit) you will be ok.
And it does absolutely NO good if the machine doesn't even get to userspace.
2.3.99pre kernels have a problem with NFS-root and crashes. Be nice if I
could just use the thing instead of having to go through the source and undo
the change. But what good is it to have it *DISABLED* at boot up? I
believe that's what his question was.
-- Lab tests show that use of micro$oft causes cancer in lab animals- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:17 EST