From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (qmail 1779 invoked from network); 12 Jun 1998 21:24:00 -0000 Received: from mail.clark.net (HELO loas.clark.net) (168.143.0.10) by mail2.redhat.com with SMTP; 12 Jun 1998 21:24:00 -0000 Received: from ccs.clark.net (ccs.clark.net [168.143.3.15]) by loas.clark.net (8.8.8/8.8.8) with SMTP id RAA25768 for ; Fri, 12 Jun 1998 17:25:17 -0400 (EDT) Received: by ccs.covici.com (UUPC/extended 1.12j); Fri, 12 Jun 1998 16:59:36 -0400 Message-ID: <358196b8.ccs@ccs.covici.com> From: covici@ccs.covici.com (John Covici) Newsgroups: blinux-list To: blinux-list@redhat.com Subject: Re: segmentation fault?? and fsck problems. Date: Fri, 12 Jun 1998 16:44:41 -0400 Organization: Covici Computer systems Reply-To: covici@ccs.covici.com Message-ID: <5MZg10r1JgCU089yn@ccs.covici.com> References: X-Newsreader: Yarn 0.89 with YES 0.22 List-Id: The problem is you can't issue those commands till its too late -- the serial console feature is special code in console.c and there is no place to specify the tty parameters. All you do is at the lilo prompt say console=/dev/tty0 console=/dev/ttyS0 -- you can specify parity, data bits, but not flow control. on Thu, 11 Jun 1998 11:31:40 -0600 (MDT) "L. C. Robinson" in wrote: >I thought you might have problems with this. I wonder if it's >because you might need to set the protocol on the serial port to >match your terminal device setup. The command to do this would >look something like this: >stty speed 19200 cs8 -parenb -cstopb < /dev/ttyS0 >This would need to be adjusted for the protocol you are using, of >course. You can make stty report the existing protocol by >running the stty command with no protocol options (but add '-a' >to force stty to report everything). Note the odd direction of >the redirection operator '<': this is correct. > >I suspect that the reason things work better with screader is >because you are logged in on a fully booted system, and before >you logged in, the getty set the protocols on the serial port >correctly. Of course, gettys are not active till the boot >process is complete. Screader is not responsible for setting the >port up, but it does offer lots of advantages in terms of >controlling the output, of course. Has anyone found a way to >get speech software like screader, working on a system that is not >yet fully operational (during the boot process)? > >This problem with not having access to the speech resources of >the machine before it is fully booted (which I believe is the way >things should be), is the reason why I think that the right way >to handle the boot message problem for blind users, is to log >everything possible, and allow the user to look at the log files >after the boot is complete (this could be automated). Extra help >should be added where possible, in case things go wrong, by >playing wav files, beeping, and the like, to give cues during the >boot. This discussion has helped me to get a better idea where >to add such things to a modified "initscripts" package which I >have been working on. I am, of course, interested in the ideas >of others, especially since I am not blind, and do not have any >speech hardware, and so have difficulty testing many aspects of >the concept. > >On Thu, 11 Jun 1998, John Covici wrote: > >> on Thu, 11 Jun 1998 00:31:26 -0600 (MDT) "L. C. Robinson" in >> wrote: >> >On Wed, 10 Jun 1998, John Covici wrote: >> > >> >> I didn't want to redirect the whole sysinit process because I had >> >> already put in those echo statements and didn't want to confuse things >> >> further. Also, I want the screens to remain the same in case >> >> something else goes wrong where I need sighted assistance. >> > >> >You probably just need to do: >> >fsck [options] > /dev/ttyS0 >> >or something similar. I tried doing: >> >exec > /dev/tty6 2> /dev/tty6 < /dev/tty6 >> >fsck -fV /dev/hdc2 >> >and it worked in interactive mode (hdc2 is a small experimental >> >partition I use). >> >> I wonder if that is because its a tty and not a serial port -- I have >> had some other problems with programs redirecting their output to the >> serial port -- I can't remember which programs they were, but I know I >> had problems with that approach -- that is why I want to run a program >> like screader and use that instead. >> >> >fsck -fV /dev/hdc2 > /dev/tty6 2> /dev/tty6 < /dev/tty6 >> >worked similarly. > > >-- >L. C. Robinson >reply to infynity@cyberhighway.net (a family account) > >People buy MicroShaft for compatibility, but get incompatibility and >instability instead: then they get to buy upgrades to fix it, and get >still more problems. This is award winning "innovation". > > >--- >Send your message for blinux-list to blinux-list@redhat.com >Blinux software archive at ftp://leb.net/pub/blinux >Blinux web page at http://leb.net/blinux >To unsubscribe send mail to blinux-list-request@redhat.com >with subject line: unsubscribe -- John Covici covici@ccs.covici.com