From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: initrd question
Date: Sat, 7 Jul 2007 02:44:46 -0500 [thread overview]
Message-ID: <005801c7c06a$b1211470$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070707063206.GA31253@localhost.localdomain>
Greg,
Consider this: an embedded linux system loads a ramdisk
image built using buildroot, and its root fs is in ram and
stays there. They have alsa up and running in seconds.
Alsa is easy because it's in the kernel and can even be
statically included in the kernel. The applications are more
difficult, but surely doable unless there is some weird
limit to ramdisk size. Ram is way faster than disk, and
flash on embedded is way slower than disk. Maybe
some day we'll all be running huge ramdisks. If we had
enough memory, why not? It would be fast. As long as
my critical files, not the system but data, are on disk
then who cares if the root fs is corrupted, in fact, to
reboot an embedded linux system you press a button,
and voila, two seconds later you're whole root fs is
brand new, just as it was because the buildroot makes
a nice image that loads into ram on boot. Another
related interesting tool is uboot bootloader, another
embedded tool but may be relevant here. With the
uboot, you can use command line args to load a
ramdisk. Now if only uboot could talk hehe.
-- Doug
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
` Doug Sutherland [this message]
` 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='005801c7c06a$b1211470$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--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).