public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "ace" <ace@talkingirc.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: New Kernel
Date: Tue, 26 Oct 2004 15:50:46 -0700	[thread overview]
Message-ID: <002001c4bbae$3c54a3a0$6c6a5acf@grandpa> (raw)
In-Reply-To: <20041026102806.GB7826@lava-net.com>

I did not copy the system.map file.  I was wondering if it could be missing
a kernel parameter.  Since I pretty much took all of the defaults during the
make config script, it could be expecting some parameters.  Shouldn't the
kernel still work though even if I don't specify the Speakup parameters?

----- Original Message -----
From: "Igor Gueths" <igueths@lava-net.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, October 26, 2004 3:28 AM
Subject: Re: New Kernel


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hmm...Remote editing is netorious for you accidentally deleting lines and
not knowing it. Did you make sure you didn't do anything that didn't move
init from its place in /sbin? Also, did you
> copy the new System.map file from /usr/src/linux to /boot?
> On Mon, Oct 25, 2004 at 09:44:38PM -0700, ace wrote:
> > Hello,
> >
> > I am using Fedora Core II.  It was originally compiled without Speakup
> > support.  I logged into the box remotely (it's my friend's box) to
recompile
> > his kernel with the latest Speakup CVS.  I downloaded the checkout
script
> > and created a symlink called linux to point to the
/usr/src/linux-2.6.8....
> > folder.  The make config and the make ran just fine.  I copied the
> > /arch/i386/boot/bzImage file to /boot.  I then went into /etc/grub.conf
and
> > changed the kernel file name in the kernel line to bzImage.  That's all
I
> > did.  I rebooted the box and it says something like:
> > "No init found, try passing init to the kernel", or something like that.
> > What did I do wrong?
> >
> > NOTE -- I didn't understand many of the long and boring questions in the
> > make config script, so I pressed enter and accepted defaults to all of
them.
> > Plus, there was only one question about Speakup, I think, it was about
> > compiling DoubleTalk into the kernel.  It's possible that I skipped more
> > when I got bored and just pressed enter a few times.
> >
> > Thanks
> > Robby
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> - --
> "The answer to life, the universe, and everything is 42." -- Douglas Adams
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFBfia2Nohoaf1zXJMRAvPPAJ4oF6Le2ilDeLfy6E/DrAR7RsYCKwCdF1hM
> SCdN1+89JM2WgmewxU6QVLQ=
> =hnSA
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 ace
 ` Igor Gueths
   ` ace [this message]
     ` Igor Gueths
       ` ace
         ` Steve Holmes
           ` Sean McMahon
             ` Janina Sajka
         ` Janina Sajka
           ` ace
 ` Janina Sajka

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='002001c4bbae$3c54a3a0$6c6a5acf@grandpa' \
    --to=ace@talkingirc.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).