public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: RE: Instructions for installing Kernels.
Date: Tue, 6 Feb 2001 11:14:08 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0102061109450.27854-100000@ignatious> (raw)
In-Reply-To: <000a01c0904d$de814830$3b910f8e@dpsd.gov.calgary.ab.ca>

I am confused as to what the problem in expanding the kernal again. Given
that this takes all of 2 or 3 minutes if you have a slow processor. If you
wanted to keep the old source, then just use different names for the
cource trees and change the softlink linux to the correct one.

I suppose someone can come up with a much more convoluted means, but I
figure that it is much easier to just follow the directions given.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.



  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Thomas Ward
 ` Stephen Dawes
   ` Thomas Ward
     ` Stephen Dawes
       ` Kirk Wood [this message]
 ` William F. Acker WB2FLW +1-303-777-8123

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.21.0102061109450.27854-100000@ignatious \
    --to=cpt.kirk@1tree.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).