From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [EXTERNAL] Re: [gentoo-user] multipath.conf : learning how to use
Date: Mon, 19 Aug 2019 15:29:20 +0200 [thread overview]
Message-ID: <6404d280-26f0-052e-1d43-56c6487ee53c@xunil.at> (raw)
In-Reply-To: <caa830acb3317ade5974cfed930fc51688565a7d.camel@openeye.net>
On 8/16/19 7:42 PM, Laurence Perkins wrote:
> Note that, in my experience at least, binary distros also tend to
> break hard if you leave them without updates for a year or more and
> then try to bring them current. And they're usually harder to fix
> when they do. So make sure that whatever you put in is kept up to
> date.
>
> The stable branch of a good binary distro has a big advantage
> there, especially with a snapshottable filesystem, because the
> updates can be handed off to a trained monkey, leaving the experts
> free for the important stuff. But it's not a magic bullet. If you
> don't write good documentation and keep the system up to date
> you'll end up in the exact same position a few years down the road
> no matter what distro you use.
I agree ... there'll be unattended updates automatically and I am
monitoring and using that server on a regular base anyway.
The goal now is to get a well-known state with less maintenance
complexity.
I am currently booking my tickets there ;-)
prev parent reply other threads:[~2019-08-19 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 19:28 [gentoo-user] multipath.conf : learning how to use Stefan G. Weichinger
2019-07-29 19:37 ` [gentoo-user] fibrechannel (was: multipath.conf ) Stefan G. Weichinger
2019-07-29 20:08 ` Stefan G. Weichinger
2019-08-14 6:36 ` [gentoo-user] multipath.conf : learning how to use J. Roeleveld
2019-08-14 8:14 ` Stefan G. Weichinger
2019-08-14 11:20 ` J. Roeleveld
2019-08-14 12:17 ` Stefan G. Weichinger
2019-08-14 18:20 ` J. Roeleveld
2019-08-16 17:42 ` [EXTERNAL] " Laurence Perkins
2019-08-19 13:29 ` Stefan G. Weichinger [this message]
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=6404d280-26f0-052e-1d43-56c6487ee53c@xunil.at \
--to=lists@xunil.at \
--cc=gentoo-user@lists.gentoo.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