From: Michael Evans <mjevans1983@gmail.com>
To: Leslie Rhorer <lrhorer@satx.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 - RAID6
Date: Mon, 8 Mar 2010 01:09:45 -0800 [thread overview]
Message-ID: <4877c76c1003080109mf1d65e7l3fabb6f675215808@mail.gmail.com> (raw)
In-Reply-To: <B8.32.23425.F5CB49B4@cdptpa-omtalb.mail.rr.com>
On Mon, Mar 8, 2010 at 12:59 AM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
>> Yes, it is for Squeeze, if you want the latest bugfixes and security
>> updates you should seriously consider running debian-testing instead
>> of stable.
>
> No, thanks. I loaded "Squeeze" on another non-RAID workstation in
> order to alleviate a kernel bug causing problems with a 3G wireless modem.
> It was quite unstable, and caused a number of issues, most problematically
> with the fact the distro assumes the system is not headless and would lock
> up tight on boot if no monitor is present. All of the RAID systems are
> headless. More importantly, stability is far and away the absolutely most
> important requirement for these servers. New features I can live without.
> Bug fixes I don't need unless they directly affect the functioning of the
> system, which is highly focussed. These systems have a handful of very
> basic, very mature apps. They run NTP, FTP, SSH, rsync, NUT, SMART, SAMBA,
> NFS, and KDE. One of them also runs Galleon, pyTivo, TyTool under wine, and
> openvpn server. That's it.
>
>> Stable is reserved for 'mature' features. Testing, as far
>> as I'm aware, will almost never (and should never if you are paying
>> attention) cause data-loss, but might occasionally get in to a
>> situation where something breaks; mostly just during upgrades (but
>> then that's true of any upgrade).
>
> It's true no data was lost, but then it's a little difficult to lose
> data if the system hangs hard on boot. I had to yank most of the guts out
> of the system to get it stable. That, plus the new version of KDE really
> sucks badly, and I could not get Kpackage to work properly at all. It also
> did something really goofy to pppd, but I was able to work around it by
> re-trying the pppd launch repeatedly on boot until it works.
>
>
Oh, is THAT where Ubuntu got 10.04's silly framebuffer required to
boot issue from...
--
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:[~2010-03-08 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 1:37 (unknown), Leslie Rhorer
2010-03-08 1:53 ` Neil Brown
2010-03-08 2:01 ` Leslie Rhorer
2010-03-08 2:22 ` Michael Evans
2010-03-08 3:20 ` Leslie Rhorer
2010-03-08 3:27 ` RAID5 - RAID6 Leslie Rhorer
2010-03-08 4:19 ` Michael Evans
2010-03-08 3:31 ` Michael Evans
2010-03-08 8:59 ` RAID5 - RAID6 Leslie Rhorer
2010-03-08 9:09 ` Michael Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-28 13:05 RAID5 -> RAID6 Max Waterman
2009-03-28 20:41 ` NeilBrown
2009-03-28 20:54 ` Max Waterman
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=4877c76c1003080109mf1d65e7l3fabb6f675215808@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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).