> > 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).
Ah!
> > 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.
Nor would I. In fact I'd call it "done" with respect to Slackware if
we just pass a note to the Sparc kernel folks making the suggestion.
> If anyone's tested siloconfig and found bugs, do tell.
I just did a reformat install with the 2000-12-20 02:04 iso image file
(md5 sum 7df251161af6a00bbb2c3c186e791eff) and setup did the silo config
and I got booted up OK. Of course, the NVRAM settinsg from previous are
probably still there.
-- ----------------------------------------------------------------- | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/ | -----------------------------------------------------------------
This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT