From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] minimalistic emerge
Date: Sat, 09 Aug 2014 11:34:29 +0200 [thread overview]
Message-ID: <53E5EB25.5060500@gentoo.org> (raw)
In-Reply-To: <53e4fa56.2679980a.47a0.27e3@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]
On 8/8/14, 6:27 PM, Igor wrote:
>> Is there any warranty that updated with -uDN system will remain
>> 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 with
>> 7 years uptime.
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 able
>> to maintain systems after updates - requires too much resources. If you have
>> 1 gentoo it might take a few days, imagine you have 100 or 1000 systems and
>> they do not share the same hardware or the same boot locations,
>> they all can be managed by 2 people if not updated and you need about 100
>> people if you update.
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-reliability-engineering.html>
>> The number of bugs is the same. It's more difficult to hack into 1996 system
>> 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ł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next prev parent reply other threads:[~2014-08-09 9:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:12 [gentoo-dev] minimalistic emerge Igor
2014-08-08 13:22 ` Ciaran McCreesh
2014-08-08 15:23 ` Igor
2014-08-08 15:36 ` hasufell
2014-08-08 15:53 ` Igor
2014-08-08 15:45 ` Ian Stakenvicius
2014-08-08 16:27 ` Igor
2014-08-08 16:40 ` Homer Parker
2014-08-08 17:26 ` Igor
2014-08-08 17:32 ` Homer Parker
2014-08-08 17:30 ` Ian Stakenvicius
2014-08-09 9:34 ` "Paweł Hajdan, Jr." [this message]
2014-08-09 15:25 ` Igor
2014-08-13 7:54 ` [OT] " Tom Wijsman
2014-08-08 16:31 ` Rich Freeman
2014-08-08 13:23 ` hasufell
2014-08-08 13:32 ` Jeroen Roovers
2014-08-08 15:14 ` Alan McKinnon
2014-08-13 8:13 ` Tom Wijsman
2014-08-08 15:51 ` Kent Fredric
2014-08-08 16:58 ` Igor
2014-08-08 17:29 ` Kent Fredric
2014-08-08 20:52 ` Igor
2014-08-08 21:33 ` Kent Fredric
2014-08-08 21:39 ` Ian Stakenvicius
2014-08-08 21:43 ` Kent Fredric
2014-08-09 14:56 ` Igor
2014-08-09 15:12 ` Chris Reffett
2014-08-09 17:10 ` Ciaran McCreesh
2014-08-13 8:20 ` Tom Wijsman
2014-08-13 13:17 ` hasufell
2014-08-09 19:30 ` Jeroen Roovers
2014-08-09 15:44 ` Chris Reffett
2014-08-09 15:46 ` Chris Reffett
2014-08-09 15:58 ` Chris Reffett
2014-08-08 19:34 ` Peter Stuge
2014-08-08 19:47 ` Ian Stakenvicius
2014-08-08 19:56 ` Kent Fredric
2014-08-08 20:16 ` Ian Stakenvicius
2014-08-09 2:14 ` Rich Freeman
2014-08-09 8:30 ` Peter Stuge
2014-08-08 21:04 ` Johannes Huber
2014-08-13 8:25 ` Tom Wijsman
2014-08-09 3:07 ` [gentoo-dev] " Duncan
2014-08-09 8:34 ` Peter Stuge
2014-08-09 11:03 ` Duncan
2014-08-09 11:06 ` hasufell
2014-08-09 12:16 ` Ambroz Bizjak
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=53E5EB25.5060500@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@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