From: Roberto Spadim <roberto@spadim.com.br>
To: Phil Turmel <philip@turmel.org>
Cc: Paul van der Vlis <paul@vandervlis.nl>, linux-raid@vger.kernel.org
Subject: Re: Software raid, booting and bios
Date: Fri, 20 May 2011 18:27:26 -0300 [thread overview]
Message-ID: <BANLkTik5N-fmUU=KggAT+0-csds_gSMhCQ@mail.gmail.com> (raw)
In-Reply-To: <4DD6C1EB.1030907@turmel.org>
i´m using usb 'pendrives' for 3 years without problems, only damn
small linux, or slitaz running in a desktop machine
2011/5/20 Phil Turmel <philip@turmel.org>:
> {do use reply-to-all on kernel.org lists... not everyone is subscribed}
>
> On 05/20/2011 11:53 AM, Paul van der Vlis wrote:
>> Op 20-05-11 14:11, Phil Turmel schreef:
>>> (Just to show what's out there.) The embedded boards I use
>>> occasionally have the equivalent of this soldered to their
>>> motherboards.
>>>
>>> The best DMA capable CF cards are usually found in markets that cater
>>> to industrial designers or to professional photographers.
>>
>> Do you think the risk of a problem with a CF card (or something like
>> that) is much lower then the risk of a problem with a harddisk?
>
> the big deal is the lack of moving parts: No spindle bearing, no head positioner gear train. On top of that, when set up to support your boot tasks only, there's no write activity to wear it out.
>
>> And what about booting from an USB stick?
>
> Just as good, technically, IMHO. If mounted internally, just as good, period. Plugged into an external port, I'd be wary of some uninformed soul pulling it out. CF cards look like they "belong".
>
> I like Ed W's suggestions, as well, with the caveat that their usefulness would make them more likely to be "borrowed". Even by yourself, in a pinch.
>
> Phil
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-20 21:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 7:19 Software raid, booting and bios Simon Mcnair
2011-05-20 8:33 ` Paul van der Vlis
2011-05-20 8:56 ` Roman Mamedov
2011-05-20 9:33 ` Paul van der Vlis
2011-05-20 10:00 ` Simon McNair
2011-05-21 16:43 ` Paul van der Vlis
2011-05-20 12:11 ` Phil Turmel
2011-05-20 13:22 ` Gordon Henderson
2011-05-20 15:53 ` Paul van der Vlis
2011-05-20 19:32 ` Phil Turmel
2011-05-20 21:27 ` Roberto Spadim [this message]
2011-05-20 21:52 ` Brad Campbell
2011-05-21 8:19 ` Leslie Rhorer
2011-05-22 6:31 ` Simon McNair
2011-05-20 10:04 ` CoolCold
2011-05-20 19:13 ` Ed W
2011-05-21 16:58 ` Paul van der Vlis
2011-05-21 19:57 ` Ed W
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 6:54 Paul van der Vlis
2011-05-20 7:03 ` Simon Mcnair
2011-05-20 7:14 ` Paul van der Vlis
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='BANLkTik5N-fmUU=KggAT+0-csds_gSMhCQ@mail.gmail.com' \
--to=roberto@spadim.com.br \
--cc=linux-raid@vger.kernel.org \
--cc=paul@vandervlis.nl \
--cc=philip@turmel.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 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 NNTP newsgroup(s).