public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: help with compilation of kernel?
Date: Sat, 18 Feb 2006 23:43:13 -0700	[thread overview]
Message-ID: <20060219064313.GB30086@localhost.localdomain> (raw)
In-Reply-To: <000e01c63516$3c760d00$6401a8c0@grandmasfury>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Feb 18, 2006 at 10:34:58PM -0700, Tyler Littlefield wrote:
> I am sort of lost, I have read the docs, but I don't really understand how to do this,
> Can someone explain how to compile the kernel?

Since you've already read the docs, then how about telling us which
part or parts of the process you don't understand, so that we can give
you a specific answer, without having to summarize the docs?

> also, is there a way I can change the output dir?

Not that I know of, though I do stand to be corrected.

> last thing, can I make it boot from a floppy or something, so if I scrue this kernel up, I can just take the floppy out, and I have my old kernel back? like, I will have two kernels on the hd, and when the floppy is in, it will boot debian into the other kernel?

You can boot 2 or more kernels off the hd, without needing to use a
floppy to do so. How to do this depends on if you're using lilo or
grub as your boot loader. Since lilo works just fine with all my
drives and bioses, and since I like using it, I haven't bothered with
grub, so if you're using grub as your boot loader, someone else will
have to tell you how to boot multiple kernels.

You can also load an entire kernel off a floppy. To do this you'd use
syslinux, the url for which I don't recall. Google for syslinux, and
you should find it.

Finally, you can also do what you suggested, use a boot loader on a
floppy to load a kernel off the hard drive. Lilo can do this, and grub
probably can too. However, I don't know why you'd want to put just the
boot loader on a floppy, unless you can't fit the kernel on it as
well, in which case you probably have too many things built into the
kernel, and not as modules.

Greg




- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD+BOB7s9z/XlyUyARAsJ8AKDLt6Wh2r4tljT3398F/26PFFVABgCgm2vH
EffePuQj957TntdEbztEUHM=
=l7Ax
-----END PGP SIGNATURE-----


      reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Gregory Nowak [this message]

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=20060219064313.GB30086@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --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).