Re: [BRLTTY] starting brltty
[quoted lines by mattias jonsson on 2016/09/18 at 17:30 +0200] >on some linux you must start brltty like: > >brltty -b baum -d usb: > >or how should it be? -b bm (not -b baum) -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting brltty automatically
Shérab, on Thu 12 Nov 2015 20:51:45 +0100, wrote: > Wouldn't it be more effficient to have udev rules that would detect the > device when it is plugged and then start brltty with the right driver? > > Are there reasons that make this approach not possible in principle > or not suitable, or is it just because nobody took the time to > implement it so far that it didn't happen? The latter. Sorry for not even having taken the time to answer your mail on debian-accessibility (it is still in my inbox). We have talked a bit about it with Mario at debconf. The plan is to have brltty installed by default on Debian systems, with a udev rule to start it automatically. We however have to be careful not to enable rules for generic USB IDs, to avoid disturbing people who want brltty loaded early, handle the case where several displays get connected, etc. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting Brltty Automatically on a custom system
Hi! You have to fiddle with the configure script and re-compile brltty. THen move /sbin/init to /sbin/real_init then copy brltty from the /program folder to /sbin/init. When running the configure script you have to use the —with-init-path=/sbin/ That is what i recall but you can read this info on the brltty page. WHen the page is available again i can check out where and get back. /A ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] starting brltty before login
Raoul MEGELAS wrote: > is it a way to do this? Does the FreeBSD kernel provide a mechanism that would let you access the text written to the console? If so, a driver could be written so you could get rid of the dependency on screen and BRLTTY could read the console early in the boot process. ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] starting brltty before login
[quoted lines by Raoul MEGELAS on 2012/11/23 at 15:50 +0100] > checking for screen driver: sc > initializing screen driver: sc > Shared memory file system object: / > Trying shared memory key: 0X627B0002 > Screen image shared memory key: 0X627B0002 > Screen Driver: sc [Screen] > Screen Screen Driver: The Screen screeen driver is starting just fine. So is the braille driver. Are you seeing the login prompt, or is even that not showing up on the braille display? What about the brltty startup line? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | 2011 May 21 is the End of Salvation. EMail: d...@mielke.cc | Canada K2A 1H7 | http://Mielke.cc/now.html http://FamilyRadio.com/ | http://Mielke.cc/bible/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] starting brltty before login
[quoted lines by Dave Mielke > >On the *bsd family we must run the screen soft > >before brltty. > >after login all work fine. > > > >but we need is to mimic the linux behaviour: > >starting screen and brltty before the login > >and continue to have it running after login. > > > i tried the command: > > > >screen -dmS MyServer. > > > >screen start, and after it brltty.* > >but we get the traditional > > > >no screen (if logged with the user login, > >or screen is initializing if we root login. > > Are you able to get a brltty log so that we can see any error messages? for sure of course, Please see below. this is not informative, except as (verified), screen does not start before login. but i do not know how to start screen and brltty automatically after login. Sorry for my ignorance... ... i run tcsh. i tried many things without result. is it a way to do this? Thanks. > I don't know the specifics of BSD systems, but it could be that you're > starting > screen before the system is up far enough for shared memory keys to work. i think you are quite right! brltty.log=== regions: text=0.0 status=0.0 shifts: full=1 half=0 vertical=5 ... checking for screen driver: sc initializing screen driver: sc Shared memory file system object: / Trying shared memory key: 0X627B0002 Screen image shared memory key: 0X627B0002 Screen Driver: sc [Screen] Screen Screen Driver: BrlAPI Server: release 0.5.7 API Parameter: auth= API Parameter: host= API Parameter: retaindots= API Parameter: stacksize= checking braille device: usb: checking for braille driver: fs socket 1 established (fd 5) initializing braille driver: fs -> usb: USB: testing: vendor=05A4 product=9862 USB: testing: vendor=0529 product=0001 USB: testing: vendor=088E product=5036 USB: testing: vendor=05A4 product=9837 USB: testing: vendor=05AC product=8242 USB: testing: vendor=0F4E product=0114 USB: ept=82 dir=in xfr=blk pkt=64 ivl=0ms USB: ept=01 dir=out xfr=blk pkt=64 ivl=0ms linking local socket lock: File exists USB Language: 409 USB: Manufacturer Name: Freedom Scientific USB: Product Description: Focus 3 socket 0 established (fd 4) Manufacturer: FREEDOM SCIENTIFIC Model: Focus 40 Firmware: 4.57 Detected Focus 40: cells=40, firmware=4.57 Braille Display Dimensions: 1 row, 40 columns regions: text=0.40 status=0.0 shifts: full=40 half=20 vertical=5 Key Bindings: focus_small file opened: /etc/brltty/brl-fs-focus_small.ktb fd=8 including data file: /etc/brltty/brl-fs-focus_small.ktb file opened: /etc/brltty/brl-fs-focus_basic.kti fd=9 including data file: /etc/brltty/brl-fs-focus_basic.kti file opened: /etc/brltty/brl-fs-common.kti fd=10 including data file: /etc/brltty/brl-fs-common.kti file opened: /etc/brltty/brl-fs-rockers.kti fd=9 including data file: /etc/brltty/brl-fs-rockers.kti Key Table: /etc/brltty/brl-fs-focus_small.ktb api link Braille Driver: fs [FreedomScientific] FreedomScientific Braille Driver: Braille Device: usb: Old Preferences File: /etc/brltty-fs.prefs file opened: /etc/brltty-fs.prefs fd=8 regions: text=0.40 status=0.0 shifts: full=40 half=20 vertical=5 setting braille firmness: 2 beeper enabled tone: msec=60 note=64 speaker open error 2: No such file or directory. api unlink api link no autodetectable speech drivers checking for speech driver: no initializing speech driver: no Speech Driver: no [NoSpeech] NoSpeech Speech Driver: Speech Input: none beeper disabled api unlink api link api unlink beeper enabled tone: msec=60 note=64 speaker open error 2: No such file or directory. beeper disabled ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] starting brltty before login
[quoted lines by Raoul MEGELAS on 2012/11/22 at 20:14 +0100] >On the *bsd family we must run the screen soft >before brltty. >after login all work fine. > >but we need is to mimic the linux behaviour: >starting screen and brltty before the login >and continue to have it running after login. > >i tried the command: > >screen -dmS MyServer. > >screen start, and after it brltty.* >but we get the traditional > >no screen (if logged with the user login, >or screen is initializing if we root login. Are you able to get a brltty log so that we can see any error messages? I don't know the specifics of BSD systems, but it could be that you're starting screen before the system is up far enough for shared memory keys to work. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | 2011 May 21 is the End of Salvation. EMail: d...@mielke.cc | Canada K2A 1H7 | http://Mielke.cc/now.html http://FamilyRadio.com/ | http://Mielke.cc/bible/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] starting brltty before login
Raoul MEGELAS, le Thu 22 Nov 2012 20:14:24 +0100, a écrit : > Pretty sure i miss something here. It's actually BSD which is missing something: support for letting brltty peek from the screen content. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting brltty as init
Cheryl Homiak wrote: > I have a question about the possibility of moving the real init, building > brltty so it knows where init is, moving the real init to the location > specified in the brltty configure, and putting Programs/brltty where init > was. I am assuming that this eliminates the need for putting a brltty line > in inittab since brltty will be starting before init but considering the > never-assume-anything adage, I thought I should check this point. Do I have > to modify the real init at all other than moving it? Also, is there any > reason this might not work and would lock me out from booting into my > system; I do have a means of rescue ready at hand. have you considered putting it in the initrd image instead? Under Debian, at least, there's an option in /etc/default/brltty to do this, after which you would have to run update-initramfs. This would run BRLTTY even earlier in the boot process and you wouldn't have to touch init. ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] starting brltty with alva
Kristoffer Gustafsson, le Wed 28 Jul 2010 17:13:46 +0200, a écrit : > what do I type to start it with alva? > I think it is brltty -b al -d ttys0, or something like that. ttyS0 is if you are using brltty shipped by cygwin. If you are using the build we provide on the mielke.cc and thefreecat.org sites, use COM1. Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting BRLTTY at Login
[quoted lines by Samuel Thibault on 2007/09/04 at 10:04 +0200] >> if [ -x /bin/brltty -a -f /etc/brltty.conf ] then /bin/brltty fi > >There are missing ';'s : it should read as > >if [ -x /bin/brltty -a -f /etc/brltty.conf ]; then /bin/brltty ; fi Or an even shorter syntax: [ -x /bin/brltty -a -f /etc/brltty.conf ] && /bin/brltty -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. http://FamilyRadio.com/ | http://Mielke.cc/bible/ ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting BRLTTY at Login
Christopher Gray, le Mon 03 Sep 2007 17:22:11 -0700, a écrit : > if [ -x /bin/brltty -a -f /etc/brltty.conf ] then /bin/brltty fi There are missing ';'s : it should read as if [ -x /bin/brltty -a -f /etc/brltty.conf ]; then /bin/brltty ; fi Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting brltty as early as possible.
Just a quick follow-up question: in most distributions, if you boot into single user mode, are the required device files guaranteed to be created, and the required file systems mounted? I am thinking in particular of a UDEV-based arrangement where most device files are created dynamically I haven't tested this under Debian, but as I remember from years past, single user mode performs basic initialization and then prompts for the root password, at which point a root shell is available. Red Hat used to offer a root shell without any password prompt, with the obvious security implications for anyone with access to the boot loader. ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting brltty as early as possible.
On Mon, Jul 02, 2007 at 08:28:34AM +0200, S?bastien Hinderer wrote: > I would keep the code, with the possibility to activate it through an > option on the cccommand-line or somewhere in brltty's configuration > file. The ability of brltty to set the system up as needed is precious, > I believe, in contexts like distribution installation, creation of boot > CDs, etc. I assume it is also possible to make such a mess of one's system that the startup scripts won't execute properly and may not mount all of the required device file systems or initialize what BRLTTY needs. In that case, it could also be infeasible to reach a shell in any event, so perhaps having BRLTTY active would only be an advantage in allowing any error messages to be read - still of considerable benefit. The resource initialization code is only activated when the required devices aren't present, so there doesn't seem to be any disadvantage in leaving it active by default, as it will usually be skipped anyway. I agree that boot images are the main context in which this code could remain useful, as well as certain system recovery scenarios as mentioned above. ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
Re: [BRLTTY] Starting brltty as early as possible.
Hi, > The latest brltty (in the repository) can run even though the braille, speech, > and/or screen drivers aren't able to start right away. It just becomes more > functional as the various components come online. This should now allow brltty > to be started as early as right after init, with braille becoming active as > soon as all needed system resources (udev, usbfs, etc) become > operational. This is simply great. > Now for my question: For a long time now, in an attempt to deal with the > "start > as early as possible" problem, brltty, on Linux, has created the resources it > needed. If a screen or serial device wasn't there yet then brltty would create > it, if usbfs wasn't mounted yet then brltty mounted it, etc. My question is: > Should brltty keep on doing this as well, or should the resource creation code > be considered a past work-around and removed? I would keep the code, with the possibility to activate it through an option on the cccommand-line or somewhere in brltty's configuration file. The ability of brltty to set the system up as needed is precious, I believe, in contexts like distribution installation, creation of boot CDs, etc. Cheers, Sébastien. ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
