public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Boris DAIX <Boris.Daix@insa-lyon.fr>
To: blinux-list@redhat.com
Subject: Re: woody root.bin
Date: Thu, 04 Jul 2002 22:02:21 +0200	[thread overview]
Message-ID: <87hejfgt2q.fsf@Pulsar.resI.insa-lyon.fr> (raw)
In-Reply-To: <87it3v47sx.fsf@lexx.delysid.org> (Mario Lang's message of "Thu, 04 Jul 2002 21:22:38 +0200")

Mario Lang <mlang@teleweb.at> writes:

> Boris DAIX <Boris.Daix@insa-lyon.fr> writes:
>
>> Mario Lang <mlang@teleweb.at> writes:
>>
>>> Check ftp://ftp.tugraz.at/incoming/debian
>>> for the files I just sent over to kajarii for first time
>>> real-world testing.  I tested the procedure in theory
>>> (without having a brailledisplay connect) and it worked.
>>
>> I would try it as soon as possible :-) I have two debian testing dists
>> to install by yesterday... I wait for your erratum on url given.
> OK, first I have to say, the version there (brltty.tar) does not
> work. We forgot that we needed to link brltty statically.

:-)

>>> The whole idea is that we load brltty via tar
>>> from a disk directly.  The only modification
>>> I made to root.bin is essentially editing /etc/init.d/rcS and 
>>> inserting
>>>
>>> echo "Please insert BRLTTY disk and press ENTER"
>>> read ret 1 </dev/console
>>> cd /
>>> tar xf /dev/fd0
>>> /sbin/brltty
>>
>> Very, very interesting !
>>
> OK, here goes the story:
>
> To build such a third brltty disk, simply create a directory
> tree which looks like a root of a filesystem, something like
>
> etc/brltty
> etc
> lib/brltty
> sbin
>
> Now, put all the brltty files you want/need there, there are actually
> some ways to do it.  Either precompile the text.table and device
> name and driver type into one static brltty, then you just need
> sbin/brltty.
>
> If you still want it to dynload different drivers, just do that,
> but dont forget to compile brltty statically, and put a
> etc/brltty.conf
> in your dummy directory.
>
> Now if everything is there, just tar that up:
>
> tar c * >../brlttydisk.tar
>
> You now write this tar directly to a normal floppy disk, either using
> dd or cat, both work:
> dd if=../brlttydisk.tar of=/dev/fd0
> or
> cat ../brlttydisk.tar >/dev/fd0
>
> Now you just need the modified woody-root.bin from ftp://ftp.tugraz.at/incoming/debian.

Ok, I did it :-)

>>> So, read the file INSTALL in the ftp directory,
>>> and try it.  Please tell me if that worked for you, and if
>>> it is a useable solution at all.
>>
>> I'll do report when I'd have tried it. But how do you modify the
>> root.bin ? 'cause I can't take over mounting it, and source package
>> boot-floppies can't compile (libs needed conflict each other...) ?
>
> Here the second story:
>
> To modify root.bin, you need to unzip it:
>
> mv root.bin root.bin.gz
> gunzip root.bin.gz
> mount root.bin /mnt -o loop

Okay... Sorry ;-) But i didn't know this tip :-)) That makes me
laugh... 

>
> Now you are ready, only thing I did was to insert
> the lines I posted into
> etc/init.d/rcS
>
> Just after proc gets mounted should be ok.
>
> now, dont forget to umount and gzip again :)
>
> cd /
> umount /mnt
> gzip root.bin

I think this is a really good method as it is really "standard". But
before congratulating, I will try :-) after my pizza...

> This is only a rough email to get the info across to interested people,
> as soon as I find more time I will put that together in a readme and on
> a web site.  The right time for the (hopefully soon) coming woody
> release :-)

If you need help, ask and I'll probably there.

>> Thank you a lot
>
> -- 
> CYa,
>   Mario

Boris




  reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Boris DAIX
 ` Mario Lang
   ` Boris DAIX
     ` Andor Demarteau
       ` Boris DAIX
       ` Mario Lang
     ` Mario Lang
       ` Boris DAIX [this message]
       ` Cheryl Homiak
         ` Boris DAIX
       ` Cheryl Homiak
         ` woody root.bin: update on installation attempt Cheryl Homiak
         ` woody root.bin Mario Lang
 ` Nath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hejfgt2q.fsf@Pulsar.resI.insa-lyon.fr \
    --to=boris.daix@insa-lyon.fr \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).