From: igueths@attbi.com
To: speakup@braille.uwo.ca
Subject: Re: announcement: Woody floppies released!
Date: Wed, 13 Nov 2002 16:58:21 +0000 [thread overview]
Message-ID: <20021113165822.MWCO24365.rwcrmhc51.attbi.com@rwcrwbc72> (raw)
Hi all. The first thing I did was to format two floppy disks, and create a
dos_fs on one of the disks. This disk would be the rescue disk. I then compiled
a kernel with Cvs speakup, BLK_DEV_LOOP, BLK_DEV_RAM, and asorted filesystems.
I then coppied the kernel to the dos-formatted floppy, as well as system.map,
and syslinux.cfg. Before copying system.map though, I gzip -c -9 System.map >
sys_map.gz. This was to save space on the disk. After copppying all the files,
I did syslinux /dev/fd0. This created ldlinux.sys. Now to the root floppy. For
that disk, it didn't require any modifications (this may change due to module
problems). I took the bf24.bin from the official Woody distribution,
decompressed it, and re-compressed with gzip -c -9 for maximum compression. I
then dd if=bf24.bin of=/dev/fd0 to a blank floppy. After all this was done, I
tested the setup. Everything seemed to work ok. I went through some of the
installation steps, however the only part I dind't test was module
installation. After all testing was completed, dd if=/dev/fd0 of=root.bin.
> I'd be interested in the process you used to create the debian installers as
> well.
> Last time I checked when trying to get the boot-floppies package I had trouble
> getting the system to send it to me and even tried getting the src package for
> it and building that so it wouldn't work.
> For handling the different kernels though what I did was go get the kernel
> source tree from the debian site, untared the file, patcked it with speakup,
> retared it and when the different images were being built the config files that
> were used didn't have speakup in them so I was able to answer all the speakup
> questions so this is how I came up with the kernel-image packages when I did the
> installers for Potato some time ago.
> Then what I did was copy the generated .deb files in to place so that the
> boot-floppies build process would extract the kernels out of those packages and
> put the in to place in to the different install images.
>
> Tommy
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
igueths [this message]
` Steve Holmes
-- strict thread matches above, loose matches on Subject: below --
igueths
` Steve Holmes
igueths
igueths
Igor Gueths
` Alex Snow
` shaun_oliver
` Tommy Moore
` Steve Holmes
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=20021113165822.MWCO24365.rwcrmhc51.attbi.com@rwcrwbc72 \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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).