David Cantrell wrote:
> I've tried to get up to speed regarding the BREAK discussion yesterday
> (missed all that due to network outage). Still a bit confused on what
> everyone wants regarding that.
I want to have the SysRQ functionality. HOW to get that isn't really much
of an issue for me. I proposed using BREAK to do SysRQ instead of having
it drop directly to PROM, and adding a way to get to PROM via SysRQ so it
is still possible to get there. I don't need it to be THAT solution. I
just want there to be some way to do things like syncing all filesystems
and remounting all filesystems read/only, directly via the kernel as SysRQ
does, when using a serial console. I proposed this approach because the
Intel platform does it this way. I copied the idea NOT to be consistent,
per se, but because it was a way that seemd to work. Consistency is not
nearly as important to me as functionality is. Any other way is fine by
me. Ultimately, it's really a kernel issue.
> Priority: HIGH
>
> - Make sure siloconfig works on as many machines as we can test on.
> Most of us don't care about this, but having the installer set up
> the booter is pretty much expected by the general public.
I look forward to testing it. While I certainly know how to work around it,
it's always convenient to have it do the job for me the first time.
> - Fix the setup program to write out the proper serial port speed if
> the users selects serial console.
If it prompts the user for the speed, 9600 should be the default, of course.
Be sure to design these features in a way that isn't particularly Sparc
dependent so that they might be rolled back into the general Slackware
setup.
> Priority: MEDIUM
>
> - Add the PCMCIA support packages to the distribution. Is this even
> necessary on the SPARC platform? I know that I can have PCMCIA slots
> in the Ultra 5.
If you can have them, someone will find a need to use them.
> - Disable e2fsck progress bar if machine is using a serial console.
Actually it wasn't really as bad as I first thought it was. I think my machine
was just running slow (it is an old 5/85).
> Anyone have any suggestions for stuff that should absolutely be taken care
> of before moving the port into public view? I know Charles was having
> keyboard map problems. I have no idea what's up with that. I plugged in
> a Type5 here and it appears to work fine. I'll see what I can find on the
> web.
He should be at home now and have a chance to look at that further with an
eye to checking on scan codes and dumping the keymap.
> I'm thinking once the HIGH and MEDIUM stuff are taken care of (or at least
> most of the MEDIUM stuff), the port can make it's way over to
> ftp.slackware.com.
The e2fsck progress bar shouldn't be a beta stopper, and I don't think the
PCMCIA stuff would be either.
Be sure slashdot.org is on your announcement list for the beta release.
-- ----------------------------------------------------------------- | 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