From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Upgrading Debian to Testing with speakup
Date: Wed, 6 Jun 2007 12:10:38 -0700 [thread overview]
Message-ID: <20070606191038.GA570@localhost.localdomain> (raw)
In-Reply-To: <BAY141-DAV602C905B6AF9772267E948F270@phx.gbl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
You don't need an initrd if you don't want to use one, I
don't. However, if you go without an initrd, make sure that things
like your ide/sata chipset, and hd support and the root file system
you use are built into the kernel itself, else you won't be able to
boot. Then, install kernel-package, untar the kernel sources, run make
oldconfig/config/menuconfig, and then run
make-kpkg kernel_image.
If you were building in /usr/src/linux for example, then the resulting
deb will be in /usr/src. Then, install it with dpkg -i package.deb,
where package.deb is the file kernel-package created. Then you'll need
to add the new image to your boot loader, this may or may not be done
for you when you install the package. I'd strongly suggest keeping
your current kernel in the boot loader as well, so that you can boot
back with it if your new kernel panics and doesn't boot. Then reboot.
If the new kernel works like you'd expect, then you can remove your
old kernel from your system, and from the boot loader of course as
well.
This is a very brief description, there are howtos and docs on the web
that cover this in much more detail.
Greg
On Wed, Jun 06, 2007 at 11:58:04AM -0700, Zachary Kline wrote:
> Hiya,
> In that case, I can probably roll my own kernel as well. I believe I'd
> need kernel-package to make that a bit easier. Also, I'm a bit unsure about
> things like initial ram disks--I never needed an initrd with Gentoo. Might
> you be able to provide some instructions on what exactly I'd need to do to
> get a kernel that will boot? I've never had to deal with the vagueries of
> kernel-package and all that before.
> Thanks much,
> Zack.
>
- --
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.6 (GNU/Linux)
iD8DBQFGZwau7s9z/XlyUyARAgawAJ4lX7DZh64jkQM0MCzfuEF97QPgngCg2lCH
8AkB4bC/OEWTOPdvcrPSAW4=
=wuuE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Gregory Nowak
` Zachary Kline
` Gregory Nowak [this message]
` Zachary Kline
` Littlefield, Tyler
` Gregory Nowak
` Gregory Nowak
` Littlefield, Tyler
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=20070606191038.GA570@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).