public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tim Burgess" <tim.burgess@blazie.co.uk>
To: <speakup@braille.uwo.ca>
Subject: RE: kernel compile gone wrong.
Date: Mon, 24 Sep 2001 17:28:44 +0100	[thread overview]
Message-ID: <000a01c14516$026e1390$f9b4e5d4@tim02> (raw)
In-Reply-To: <Pine.LNX.4.21.0109241043120.331-100000@hudson.mhonline.net>

Hi all,

Sorry to be a quitter, but I'm pushed on available time for this project.
I've bitten the bullet and I'm going for a rebuild from original media then
I'll take it around the loop again.

If I had more time, I'd stick at it till I knew how to fix it (a much more
satisfactory state of affairs), but I've a deadline to meet, blah, blah,
blah...

Cheers.

Tim


-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Charles Hallenbeck
Sent: 24 September 2001 15:44
To: speakup@braille.uwo.ca
Subject: RE: kernel compile gone wrong.



Hi Tim,

Do this:

mount /dev/hda1 /mnt

Then be sure you include the "/mnt" when you access your files. For
instance, your lilo.conf will now be at /mnt/etc/lilo.conf

HTH - Chuck

On Mon, 24 Sep 2001, Tim Burgess wrote:

> Hi,
>
> I've created a boot disk and a root disk and they work with speech, but I
> don't know how to mount my hard drive so I can get access to the files.  I
> though it was:
>
> mount / /dev/hda1
>
> but this doesn't work.  Can anybody point me at what I'm doing wrong?
>
> Cheers.
>
> Tim
>
>
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Shaun Oliver
> Sent: 24 September 2001 14:51
> To: speakup@braille.uwo.ca
> Subject: RE: kernel compile gone wrong.
>
>
> well for starters, if you have a boot disk for your original kernel, I
> suggest you run it and boot your linux that way.
> then carefully look over your /etc/lilo.conf and make the appropriate
> changes.
> then once you're done, type lilo to reread the configuration file and then
> reboot.
> if all goes well, you'll have yourself a nice shiny new linux kernel to
> play with.
>
> Shaun..
>
>
>
> On Mon, 24 Sep 2001, Tim Burgess wrote:
>
> > Hi all,
> >
> > I got a good kernel compile out of 2.4.6 and SpeakUp 0.10a.tar.gz then
> blew
> > it all by getting my lilo.conf entry wrong, I think.  I'm now stuck
until
> I
> > can borrow some eyeballs to see if I can retrieve the situation.
> >
> > In the meantime, thanks to all of you who have gritted your teeth at my
> > incompetence so far.
> >
> > Tim
> >
> >
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of William F. Acker
> > WB2FLW +1-303-777-8123
> > Sent: 23 September 2001 21:18
> > To: speakup@braille.uwo.ca
> > Subject: RE: kernel compile gone wrong.
> >
> >
> > Hi, Tim,
> >
> >      I have a patch for 2.4 kernels made from the 20010917 CVS snapshot
of
> > Speakup.  I can make a 2.2 version if you need it.  Just say the word
and
> > I'll send it off.
> >
> >
> >
> >
> >           HTH.
> >           Bill in Denver
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Visit me at http://www.mhonline.net/~chuckh
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759.


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Shaun Oliver
 ` Frank Carmickle
   ` Shaun Oliver
   ` Tim Burgess
     ` Shaun Oliver
       ` Steve Holmes
         ` Tim Burgess
           ` Janina Sajka
             ` Tim Burgess
               ` Janina Sajka
             ` Gregory Nowak
               ` Gregory Nowak
                 ` Janina Sajka
               ` Janina Sajka
                 ` Tim Burgess
           ` Gregory Nowak
             ` Tim Burgess
           ` William F. Acker WB2FLW +1-303-777-8123
             ` Tim Burgess
               ` Gregory Nowak
             ` Tim Burgess
               ` Shaun Oliver
                 ` Tim Burgess
                 ` Tim Burgess
                   ` Charles Hallenbeck
                     ` Tim Burgess [this message]
                   ` Shaun Oliver
               ` Gregory Nowak
       ` Gregory Nowak
     ` Gregory Nowak
       ` Tim Burgess
 Holmes, Steve

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='000a01c14516$026e1390$f9b4e5d4@tim02' \
    --to=tim.burgess@blazie.co.uk \
    --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).