public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: kde4 upgrading
Date: Wed, 28 Oct 2009 13:44:48 +0000	[thread overview]
Message-ID: <ECBAD956-810B-4FB0-85C8-3B9EB2227D3F@stellar.eclipse.co.uk> (raw)
In-Reply-To: <loom.20091028T010741-743@post.gmane.org>

I've edited your message when quoting it in order to meet my agenda.

On 28 Oct 2009, at 00:28, James wrote:
> ....
> PS, if one of you really smart guys figures out mass/parallel
> upgrades, then I'd use that, even set up my own server
> to keep it efficient. I'm not smart enough (not enough time
> at current mental aptitude) to set all of that up, unless
> somebody else does the foundational work.....
>
> But I very much like the concept. Upgrade a master system.
> Test it. Then  push your own binaries/files to the other systems
> you manage.

There are already a number of ways of managing multiple machines. How  
do you think universities, corporations and public bodies with  
hundreds or thousands of desktops manage? I think I would be looking  
at something like having the machines PXE boot a single image or NFS  
mounting various directories, if I were in your situation. I've never  
actually done this, but I'm sure a little research would produce a  
less labour intensive solution.

> ...
> Interesting, but not what I'm looking for. I do not mind
> upgrading the systems one at a time. I just do 1 per day,
> while I do other work. What has me "hacked" is that every time
> I do an upgrade to kde4, it seems to be a different set
> of problems, even though the upgrades are a few days apart.
> Multiply across a dozen workstations, and it's a time sink.

It seems to me, from your description, that your dozen machines are at  
the limit of your ability to maintain this way. No one would ever  
consider upgrading sites with 100 machines one by one each day, and it  
would be crazy to try and run a beefy thin-client server just to serve  
one or two desktops.

So the network has grown from a couple of machines to a dozen, and  
you're still doing things the same way - the question is, will you be  
able to continue doing things the same way if you were to double the  
number of PCs by next year?

I think that alternative methods of approaching system administration  
are sure to bring their own problems and require an investment of time  
to implement, but I don't see how upgrading machines one by one is  
sustainable. Honestly, it would be driving me crazy to be in your  
position, and I think some other alternative might well show time and  
hassle saved once it's up and running.

Stroller.




  parent reply	other threads:[~2009-10-28 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 16:13 [gentoo-user] kde4 upgrading James
2009-10-27 22:24 ` Alan McKinnon
2009-10-27 22:47   ` Frank Steinmetzger
2009-10-28  0:30     ` [gentoo-user] " James
2009-10-27 23:54   ` [gentoo-user] " Neil Bothwick
2009-10-28  0:28   ` [gentoo-user] " James
2009-10-28  4:37     ` Jonathan Callen
2009-10-28  8:58     ` Alan McKinnon
2009-10-28 13:44     ` Stroller [this message]
2009-10-29 14:59       ` [gentoo-user] Re (DONE): " James
2009-10-29 17:53         ` Stroller
2009-10-29 19:17         ` Alan McKinnon

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=ECBAD956-810B-4FB0-85C8-3B9EB2227D3F@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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