All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iordan Iordanov <iordan@cdf.toronto.edu>
To: Hank Barta <hbarta@gmail.com>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
	linux-raid@vger.kernel.org
Subject: Re: RAID for USB flash drives
Date: Mon, 17 Jan 2011 10:41:36 -0500	[thread overview]
Message-ID: <4D346330.8080202@cdf.toronto.edu> (raw)
In-Reply-To: <AANLkTi=cOHgdradDDOFTdZ_xOGMXv8qf_n6xxppGA12y@mail.gmail.com>

Hi Hank,

On 01/14/11 18:25, Hank Barta wrote:
> I could also use 'debirf' as suggested by Iordan Iordanov, but I
> prefer to retain the full (disk based) environment with ease of
> installing and updating S/W. I haven't studied debirf but I suspect I
> would have to create and install a new image any time I want to update
> or install new packages.

Just to help clarify the debirf possibility. Debirf is Debian inside 
initrd, so yes, in order to make a change persistent, one would have to 
copy a new initrd over to the USB stick. However, since Debian is fully 
functional, running in a RAM disk, one is also able to install and 
update software on the fly using apt/aptitude. It's just that changes 
made to the ramdisk do not make it automatically into the initrd on the 
USB stick. You have to run one make command and copy the new image to 
the stick yourself. You can easily cron the building of the image, 
mounting of the USB stick, copying over, and unmounting once a day or 
week to keep the image up-to-date.

Also, all of this may be possible with Ubuntu, I just haven't had to do 
the research.

If you don't do debirf, don't forget to NOT put swap on the stick, and I 
would also make a ramdisk for /var/log and copy the logs to the stick 
upon shutdown (to prevent unnecessary flash wear as logs are gradually 
incremented).

Cheers and good luck!
Iordan

  parent reply	other threads:[~2011-01-17 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 19:40 RAID for USB flash drives Hank Barta
2011-01-04 20:09 ` John Robinson
2011-01-04 20:14   ` Steven Haigh
2011-01-14 23:25   ` Hank Barta
2011-01-15 20:54     ` John Robinson
     [not found]       ` <AANLkTinQcu8jwKGiYViBP_CE0Hd4UbaO4spvMgnmRoa8@mail.gmail.com>
     [not found]         ` <4D358490.4020400@anonymous.org.uk>
2011-01-18 13:47           ` Hank Barta
2011-01-17 15:41     ` Iordan Iordanov [this message]
2011-01-04 21:22 ` Iordan Iordanov

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=4D346330.8080202@cdf.toronto.edu \
    --to=iordan@cdf.toronto.edu \
    --cc=hbarta@gmail.com \
    --cc=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.