From: rmann@rmisp.net
To: speakup@braille.uwo.ca
Subject: Re: best way to install rh9?
Date: Thu, 8 May 2003 20:47:53 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0305082045480.6422-100000@rmnet> (raw)
In-Reply-To: <009001c315ae$b9ff1260$e50b9541@tward1978>
Hi. Can you send me a copy of your Kickstart file? I'm thinking about
installing RH9 on my laptop.
On Thu, 8 May 2003, Thomas D. Ward wrote:
> Hi, Jacob. Do you want a kickstart file? I do have one that you can modify
> to fit your needs.
>
> ----- Original Message -----
> From: Jacob Schmude <jacobs@surferie.net>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, May 08, 2003 3:10 PM
> Subject: Re: best way to install rh9?
>
>
> > Hi
> > I'll probably wind up going with a kickstart file--if I get it wrong the
> > first time I'll just have to get it right--grin. Anyhow, what would I have
> > to do to patch keyboard.c? It's gonna take a bit to get the 3 iso images,
> > so it'll be a little while before I install it.
> > just out of curiosity: what has rh done to keyboard.c that requires it to
> > be patched by hand? I was going to suggest making a patch file, but with
> > CVS, that just might not be an option since it changes so rapidly. Maybe
> > there's a way for a rh-specific patch to be put into cvs and the install
> or
> > checkout script could decide which one to apply based on a condition,
> > possibly the condition of a build number after the kernel version (rh and
> > mandrake are the only distros I know of that do this). I mean something
> > such as 2.4.20 and 2.4.20-9. Perhaps if the script could determine the
> > difference, it could know to apply the 2.4.20 redhat patch to 2.4.20-9,
> for
> > example. Would such a thing be possible?
> > For now, though, can you send me some instructions on how to hand-patch
> it,
> > what line numbers, what I need to change, etc?
> > At 22:41 5/7/2003 -0600, you wrote:
> >
> > >Hi,
> > >
> > > I don't know of a program for verifying a kickstart file. If your
> IP
> > >address is routable, I'd be happy to help you with a telnet installation
> > >over the phone. The Speakup keymaps are available in RH9, although there
> > >a little old. They'll be fine for an initial installation. I do
> > >recommend that you upgrade the kbd package along with the kernel. Use
> the
> > >clean kernel-source-2.4.20-9.i386.rpm from RH to add the CVS version of
> > >Speakup to. You'll have to hand patch keyboard.c, Janina or I can help
> > >with that.
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Jacob Schmude
` Lorenzo Prince
` William F. Acker WB2FLW +1-303-722-7209
` Thomas D. Ward
` jude dashiell
` Thomas D. Ward
[not found] ` <Pine.LNX.4.50.0305072235370.7574-100000@wb2flw.octothorp.o rg>
` Jacob Schmude
` Thomas D. Ward
` Jacob Schmude
` rmann [this message]
` Richard Villa
` William F. Acker WB2FLW +1-303-722-7209
[not found] ` <Pine.LNX.4.50.0305122134540.10625-100000@wb2flw.octothorp. org>
` Got it running (was Re: best way to install rh9?) Jacob Schmude
` Lorenzo Prince
` William F. Acker WB2FLW +1-303-722-7209
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=Pine.LNX.4.44.0305082045480.6422-100000@rmnet \
--to=rmann@rmisp.net \
--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).