From gentoo-dev  Sat Aug 09 09:34:29 2014
From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= <phajdan.jr () gentoo ! org>
Date: Sat, 09 Aug 2014 09:34:29 +0000
To: gentoo-dev
Subject: Re: [gentoo-dev] minimalistic emerge
Message-Id: <53E5EB25.5060500 () gentoo ! org>
X-MARC-Message: https://marc.info/?l=gentoo-dev&m=140757689704838
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--qbecFiMguLqGKWatnLqAJ8KFd2MXNMje0"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qbecFiMguLqGKWatnLqAJ8KFd2MXNMje0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 8/8/14, 6:27 PM, Igor wrote:
>> Is there any warranty that updated with -uDN system will remain=20
>> full functional for 1 year? I have 100% warranty that not updated
>> system is going to remain functional for 5 or 6 years. I have some wit=
h=20
>> 7 years uptime.=20

I'd say there is no "warranty". However, a staging environment can help
detecting issues earlier, before deploying them to production and
allowing you to come up with a way to address them.

I certainly wouldn't recommend just running an update on a running
production server without testing it first.

>> I'm in a trap - if I update daily - the systems are offline, I'm not a=
ble=20
>> to maintain systems after updates - requires too much resources. If yo=
u have=20
>> 1 gentoo it might take a few days, imagine you have 100 or 1000 system=
s and=20
>> they do not share the same hardware or the same boot locations,=20
>> they all can be managed by 2 people if not updated and you need about =
100=20
>> people if you update.=20

Consider automating the processes - as you pointed out, the way
described above doesn't scale.

Possibly relevant article would be
<http://www.site-reliability-engineering.info/2014/04/what-is-site-reliab=
ility-engineering.html>

>> The number of bugs is the same. It's more difficult to hack into 1996 =
system=20
>> than in 2012.

Do you have any evidence to back that claim? There are tons of known
vulnerabilities in '96-era software, and automated exploits for them.

By the way, I can see a point in your thread. Our updates and package
manager could be improved. They have improved greatly in the last few
years. I think I can safely say we welcome further contributions of
patches, packaging and testing effort, especially helping automate many
of these tasks.

Pawe=C5=82


--qbecFiMguLqGKWatnLqAJ8KFd2MXNMje0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQIcBAEBCgAGBQJT5espAAoJEE8aJVXqcZkdkzcQAIdqQzzEJRsqB4fpJaGMXgJj
ZACCqDGgnW9667QmMpqu5Pcn2NzX2IJfwqySLhP7JOOFcguNmbmMzG+lI6vFiB+N
pQtn7dvCGQ4sXDkUUvlGmCzrQxXwKc2aTaQGT02IXHJchWkM8H2rryBSrY20G9Pk
b2WHRB5GQmtPjr57vlKSUo7WW7nYcJhtudS8enp028qrKNpULD+gFcrCQb4dgqt8
4s1LDFVG/Pg+pQBgKbOcFLzI27n6UggH1qMBlzlD7VjWLECt62NY0LfVab8kyHXN
4gOO19YeJFUlR9D0AZu+u7JvEPqTdNgDZvoqEBlubcdNpKNayFeQv7ErInAfwZDX
NNnkECDlQrEfbZ7VVa8D4gMKRpcZlfiyAmYWRvhOIG9e11otEq+tk0dRwDV0q6NS
nQJ07dR8mj8tmJozo3gnXkMy/dagvXkGm2GPDJ2cSau5BxcYKiuRmcZZz6aQPEmB
71jrGJpYdXqCDdaP6G3qNIXoRfFEuDSiZe/n5Jj3ruF3nziSYu/mMMLQHoDgp94X
i7Fk2Q7kh5R+gsdP45hL2dNs7TMr/5ibnOjLw6DaBuOo5IhOhpENjd83WfUMrOrr
6mvbTcRYJMlFJZ5nNvtIafJytD9Qg3A0vfm4m5DxOb8te3pmGFLIp1kuRLch30pU
dAqwzvvwCVExR4XUbDR8
=TYCD
-----END PGP SIGNATURE-----

--qbecFiMguLqGKWatnLqAJ8KFd2MXNMje0--