The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Dow via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Is it time to resurrect the original dsw (delete with switches)?
Date: Mon, 30 Aug 2021 10:14:15 +0100	[thread overview]
Message-ID: <1e976247-3642-8f84-a429-167e8b640877@me.com> (raw)
In-Reply-To: <CAEdTPBeoaxAhnOGj5ywY_Y7nwRavfmn7FMw2JTGMn-t8W3mYaw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

On 30/08/2021 00:09, Henry Bent wrote:

> On Sun, 29 Aug 2021 at 18:13, Jon Steinhart <jon@fourwinds.com 
> <mailto:jon@fourwinds.com>> wrote:
>
>     I recently upgraded my machines to fc34.  I just did a stock
>     uncomplicated installation using the defaults and it failed miserably.
>
>     Fc34 uses btrfs as the default filesystem so I thought that I'd
>     give it
>     a try.
>
>
> ... cut out a lot about how no sane person would want to use btrfs ...
>
>
>     Or, as Saturday Night Live might put it:  And now, linux, starring the
>     not ready for prime time filesystem.  Seems like something that's been
>     under development for around 15 years should be in better shape.
>
>
> To my way of thinking this isn't a Linux problem, or even a btrfs 
> problem, it's a Fedora problem.  They're the ones who decided to 
> switch their default filesystem to something that clearly isn't ready 
> for prime time.

This. Even the Arch wiki makes it clear that btrfs isn't ready for prime 
time. It's still under very heavy development - not really something you 
want for a filesystem, particularly one storing a large amount of 
critical data.


John


[-- Attachment #2: Type: text/html, Size: 2428 bytes --]

  parent reply	other threads:[~2021-08-30  9:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 22:12 Jon Steinhart
2021-08-29 23:09 ` Henry Bent
2021-08-30  3:14   ` Theodore Ts'o
2021-08-30 13:55     ` Steffen Nurpmeso
2021-08-30  9:14   ` John Dow via TUHS [this message]
2021-08-29 23:57 ` Larry McVoy
2021-08-30  1:21   ` Rob Pike
2021-08-30  3:46   ` Theodore Ts'o
2021-08-30 23:04     ` Bakul Shah
2021-09-02 15:52       ` Jon Steinhart
2021-09-02 16:57         ` Theodore Ts'o
2021-08-30  3:36 ` Bakul Shah
2021-08-30 11:56   ` Theodore Ts'o
2021-08-30 22:35     ` Bakul Shah
2021-08-30 15:05 ` Steffen Nurpmeso
2021-08-31 13:18   ` Steffen Nurpmeso
2021-08-30 21:38 ` Larry McVoy
2021-08-30 13:06 Norman Wilson
2021-08-30 14:42 ` Theodore Ts'o
2021-08-30 18:08   ` Adam Thornton
2021-08-30 16:46 ` Arthur Krewat

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=1e976247-3642-8f84-a429-167e8b640877@me.com \
    --to=tuhs@minnie.tuhs.org \
    --cc=johnmdow@me.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).