[gentoo-dev] RFC: brltty not starting early enough

[gentoo-dev] RFC: brltty not starting early enough

[William Hubbs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

brltty is one of our accessibility packages.  It is a program that
drives a braille display which is one way a blind person can access the
computer.

The project's guidelines for linux distributions at http://www.mielke.cc/brltty/guidelines.html suggest starting the program very early in the boot sequence.  Ideally, I would like to be able to start brltty as soon as /dev is set up either with udev, devfs, or static.

There is a new version of brltty which hasn't been put into portage yet,
so I thought now would be a good time to ask about it.  How should we
set this up on gentoo?  Any suggestions would be appreciated.

Thanks,

- -- 
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHeVYPblQW9DDEZTgRAqoSAJ9im3bK2aCniGcnyDEH7CKzNPQd9gCdGdaf
j3ldKDZL5jSNy1FBZ7n7mqA=
=In/i
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] RFC: brltty not starting early enough

[Roy Marples]

On Mon, 2007-12-31 at 14:50 -0600, William Hubbs wrote:
> brltty is one of our accessibility packages.  It is a program that
> drives a braille display which is one way a blind person can access the
> computer.
> 
> The project's guidelines for linux distributions at http://www.mielke.cc/brltty/guidelines.html suggest starting the program very early in the boot sequence.  Ideally, I would like to be able to start brltty as soon as /dev is set up either with udev, devfs, or static.
> 
> There is a new version of brltty which hasn't been put into portage yet,
> so I thought now would be a good time to ask about it.  How should we
> set this up on gentoo?  Any suggestions would be appreciated.

Just make a standard init script for it with this dependency block

depend() {
   before checkfs
}

That way it will be run immediately after /dev, /proc and /sys have been
brought up and the root fs checked. After that, brltty should launch.

However, that doesn't work for baselayout-1 as it forces more services
to start before hand, but should work as expected in newer versions.

Thanks

Roy

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] RFC: brltty not starting early enough

[William Hubbs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jan 01, 2008 at 12:27:24PM +0000, Roy Marples wrote:
> Just make a standard init script for it with this dependency block
> 
> depend() {
>    before checkfs
> }

Would it be safe to change this to before checkroot'?

Thanks,

- -- 
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHenQoblQW9DDEZTgRAsJiAJ42V1WHOhNbRyIe4h6BgwH0MgW5nwCfbkVi
DveDXOMM38vMfgn0Qjjnv6g=
=KXau
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] RFC: brltty not starting early enough

[Roy Marples]

On Tue, 2008-01-01 at 11:11 -0600, William Hubbs wrote:
> On Tue, Jan 01, 2008 at 12:27:24PM +0000, Roy Marples wrote:
> > Just make a standard init script for it with this dependency block
> > 
> > depend() {
> >    before checkfs
> > }
> 
> Would it be safe to change this to before checkroot'?

Some scripts do run before checkroot, such as clock. clock should be the
first script started, so if you want it to go really early then

depend() {
   before *
   after clock
}

would also work. Note that you have to put the dependencies in that
order, and it only works with baselayout-2.

If you wanted it to start before clock you'll need to do this

depend() {
   before *
}

AND add this to /etc/conf.d/clock
RC_AFTER=brltty

Again, baselayout-2 only.

Thanks

Roy

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] RFC: brltty not starting early enough

[William Hubbs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jan 01, 2008 at 05:19:39PM +0000, Roy Marples wrote:
> Some scripts do run before checkroot, such as clock. clock should be the
> first script started, so if you want it to go really early then

My goal is to have the braille display active as early is possible so
that if an error occurs during the boot process a blind person would
know about it.  I can't start before /proc, /dev, and /sys are mounted
because brltty uses things in those filesystems.  Can you think of any
possible reason that I would need to start before clock runs?  If not,
I'll just use your first suggestion.

Besides starting later than expected, will anything break if this goes
on a baselayout 1 system?

Thanks much for your help.

William

> depend() {
>    before *
>    after clock
> }
> 
> would also work. Note that you have to put the dependencies in that
> order, and it only works with baselayout-2.
> 
> If you wanted it to start before clock you'll need to do this
> 
> depend() {
>    before *
> }
> 
> AND add this to /etc/conf.d/clock
> RC_AFTER=brltty
> 
> Again, baselayout-2 only.
> 
> Thanks
> 
> Roy
> 
> -- 
> gentoo-dev@gentoo.org mailing list
> 

- -- 
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHeoCtblQW9DDEZTgRAossAKCsZKHsBIf7oOrECy3LHzKu8867awCgjYyp
AEcpVtjsPJxgLcnKma5BQlw=
=OHnU
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] RFC: brltty not starting early enough

[Roy Marples]

On Tue, 2008-01-01 at 12:04 -0600, William Hubbs wrote:
> On Tue, Jan 01, 2008 at 05:19:39PM +0000, Roy Marples wrote:
> > Some scripts do run before checkroot, such as clock. clock should be the
> > first script started, so if you want it to go really early then
> 
> My goal is to have the braille display active as early is possible so
> that if an error occurs during the boot process a blind person would
> know about it.  I can't start before /proc, /dev, and /sys are mounted
> because brltty uses things in those filesystems.  Can you think of any
> possible reason that I would need to start before clock runs?  If not,
> I'll just use your first suggestion.
> 
> Besides starting later than expected, will anything break if this goes
> on a baselayout 1 system?

depscan.sh may constantly complain about it

You could do this

depend() {
   if [ -z "$svcdir" ]; then
       before *
   fi
   after clock
}

But I would test to see what happens on baselayout-1 first.

Thanks

Roy

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] RFC: brltty not starting early enough

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

On Monday 31 December 2007, William Hubbs wrote:
> The project's guidelines for linux distributions at
> http://www.mielke.cc/brltty/guidelines.html suggest starting the program
> very early in the boot sequence.  Ideally, I would like to be able to start
> brltty as soon as /dev is set up either with udev, devfs, or static.

keep in mind this also requires britty to be completely usable in / ... you 
cannot have /usr dependencies that would prevent it from working.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]