From: Juergen Sauer <juergen.sauer@automatix.de>
To: "Johan Kröckel" <johan.kroeckel@gmail.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: RHEL/CentOS or Debian for stable deployment
Date: Sat, 29 Mar 2014 17:20:41 +0100 [thread overview]
Message-ID: <5336F2D9.4090602@automatix.de> (raw)
In-Reply-To: <CABgvyo_b19P2QPzszv6Vxc2iHOceP-ndCp1oUzO6Hc=Z4CiJ=A@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 28.03.2014 13:29, schrieb Johan Kröckel:
> Hello,
> I am not sure whether this is the correct list, but I will try...
> I am on the way to deploy new server and already am using
> btrfs-volumes. At this point not for root, but in case a stable setup
> is possible, this would be cool, too.
>
> I don't want to use vanilla kernel because I like it when someone else
> is watching security issues for me.
> So the question is:
> Which source for the kernel binaries would you use, to get stable
> btrfs support together with mentioned service?
> I am asking, because I don't know how Red Hat and Debian (Backports
> channel) are dealing with backporting new btrfs code to their
> distributed kernels.
None is really usable for development, IMHO.
For Development we prefer "Arch Linux", it somewhat more "Bare Linux",
mostly all packages made from unpatched and unmodified "vanilla" sources.
Debian and CentOS are for Development mucht "to matrue", or harder
spoken, much too old.
If a product is ready for deployment, the other Debian / Ubuntu / SuSE /
Fedora / RedHat / CentOS got the Level of the system, which Arch had on
start time of development.
Then we enter package stage and depoy the product to the "stable"
Distributions.
On stable Setup/Server we prefer Debian or Ubuntu.
The Enterprise Distributions (aka. RHEL, SELS, CentOS) are looking to us
sometimes like "software achrchelogy ...
mit freundlichen Grüßen
Jürgen Sauer
- --
Jürgen Sauer - automatiX GmbH,
+49-4209-4699, juergen.sauer@automatix.de
Geschäftsführer: Jürgen Sauer,
Gerichtstand: Amtsgericht Walsrode • HRB 120986
Ust-Id: DE191468481 • St.Nr.: 36/211/08000
GPG Public Key zur Signaturprüfung:
http://www.automatix.de/juergen_sauer_publickey.gpg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlM28tkACgkQW7UKI9EqarH/UgCeM/rQ2wKUjXC0az3UuCaSCW0O
ceMAoLGBXtYoqN5gi1CWvG7RHQbyF/r0
=4gue
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-03-29 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 12:29 RHEL/CentOS or Debian for stable deployment Johan Kröckel
2014-03-28 21:42 ` Avi Miller
2014-03-28 23:38 ` Lists
2014-03-28 23:45 ` Hugo Mills
2014-03-30 0:18 ` Marc MERLIN
2014-03-30 1:04 ` Hugo Mills
2014-03-28 23:47 ` Avi Miller
2014-03-29 16:20 ` Juergen Sauer [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=5336F2D9.4090602@automatix.de \
--to=juergen.sauer@automatix.de \
--cc=johan.kroeckel@gmail.com \
--cc=linux-btrfs@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.