From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: initrd question
Date: Fri, 6 Jul 2007 23:32:06 -0700 [thread overview]
Message-ID: <20070707063206.GA31253@localhost.localdomain> (raw)
In-Reply-To: <003d01c7c065$8bc2ae50$ab00a8c0@tenstac>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Jul 07, 2007 at 02:07:55AM -0500, Doug Sutherland wrote:
> Well that's all kernel stuff, but it would be best to include
> them all. What is a linux install disk? It's a ramdisk with
> generic kernel. That's the kind of kernel you want. It
> makes no sense to make it specific to your machine,
> you want a ramdisk that will boot on anything.
I only meant this for the initial stage to get things working. Once
that is done, it would be best of course to include support for all
sound cards, that would be trivial compared to the rest of the
process. I have played with creating ramdisks before, so I'm familiar
with the basics. I've also built alsa from source, but never looked at
it. If ./configure, make, make install worked, which they always did,
I just moved on, and never bothered looking at the results, because I
didn't need to, and because I wasn't interested.
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.6 (GNU/Linux)
iD8DBQFGjzNm7s9z/XlyUyARAur5AJ4tdkOlyFIEAnKuwJeFkJXdhfI1PACgwpoi
AGWKJMhoFzBGDTAKG9MFyAQ=
=mQ6i
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland
` Gregory Nowak [this message]
` Doug Sutherland
` Doug Sutherland
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=20070707063206.GA31253@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).