From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: alsa in Debian using the stock 2.4.27 kernel wasRe: hello listers
Date: Wed, 13 Apr 2005 06:14:06 -0500 [thread overview]
Message-ID: <20050413111406.GA3938@blackbox> (raw)
In-Reply-To: <ILECLJPFEPACKLIKIOPFIEBBCAAA.ekosten@tampabay.rr.com>
Hi.
On Tue, Apr 12, 2005 at 11:14:26AM -0400, Eric Kosten wrote:
> Kernel-package packages my 2.4.27 kernel?? Does this allow me to then keep
> an immage of the kernel for a "fall-back form"?
Yes.
> kernel immage being the 2.6.11.7 kernel source tree that I just downloaded??
> file name: patch-2.6.11.7.bz2
Did you download linux-2.6.11.7.bz2?
I believe the files from kernel.org that start with patch are used to
update an existing 2.6 kernel source of an earlier version to the new
version. Since you are going from 2.4.27, you should download
linux-2.6.11.7.tar.bz2.
> This is rather confusing since I have built a total of 2 kernels and this
> with the help of a friend.
I'm guessing, but your friend probably built the kernel the way
described in the docs that come in the kernel source tree. This will
work on Debian, but you will have to do some things manually that will
be done for you using the kernel-package program.
One example is if you used grub as your boot loader. the "make install"
command doesn't understand Debian's grub, so you will have to edit
/boot/grub/menu.lst manually after you are done. The kernel-package is
a Debian program, so it knows about Debian's grub.
Hope this helps.
Kenny
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Eric Kosten
` alsa in Debian using the stock 2.4.27 kernel wasRe: " Kenny Hitt
` Eric Kosten
` Kenny Hitt
` Eric Kosten
` Kenny Hitt [this message]
` Eric Kosten
` Kenny Hitt
` Gregory Nowak
` Kenny Hitt
` Steve Holmes
` alsa in Debian using the stock 2.4.27 kernel wasRe:hello listers Sean McMahon
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=20050413111406.GA3938@blackbox \
--to=kenny@hittsjunk.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).