On Wed, Dec 20, 2000 at 10:01:28PM -0600, Phil Howard wrote:
> > Saw /proc/sys/sysrq and /proc/sys/stop-a. Cat those and they return "1".
> > Anyone know what these two things control? I'm guessing just an on/off
> > toggle.
>
> I know /proc/sys/sysrq makes SysRQ work if 1, not work if 0.
> I suspect /proc/sys/stop-a makes Stop+A work if 1, not work if 0.
OK, can verify this, but that's what I'll assume.
> BTW, I just discovered that BREAK does not drop to PROM in SILO.
> Maybe that should be suggested to the SILO developers. If they
> are doing I/O via PROM code (I suspect likely) I'm surprised it
> isn't automatically there. It should also accept a special boot
> name "prom" to go to PROM as well. Then, maybe this can be
> configured (I haven't looked).
Type "halt" at the SILO prompt (/usr/doc/silo/README).
> I think our discussion regarding serial break is just how it
> should behave. I think the consensus is that there is not
> 100% consensus on what it should do, but rather, it should be
> configurable.
Yeah, seems to be the general consensus. Well, I don't want to start
hacking on kernel source and delay moving the distribution to the FTP
site, so this task is getting low priority now. I wouldn't call the
BREAK functionality over the serial console a show stopper.
If anyone's tested siloconfig and found bugs, do tell.
--
David Cantrell | david@slackware.com *
KG6CII | Slackware Linux Project
This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT