public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Mothballing a ~arch gentoo system?
Date: Mon, 28 Dec 2009 00:27:30 -0600	[thread overview]
Message-ID: <4B384FD2.50907@gmail.com> (raw)
In-Reply-To: <1261978906.11618.63.camel@rattus>

William Kenworthy wrote:
> On Sun, 2009-12-27 at 20:45 -0600, Dale wrote:
>   
>> Marcus Wanner wrote:
>>     
>>> When an old (circa 2001) desktop came out of retirement a few months 
>>> ago, I shuffled across Linuxes trying to find something that worked 
>>> well, and finally hit on gentoo. I eventually switched to ~x86 because 
>>> I was tired of using versions of apps from 6 months ago... Too make a 
>>> long story short, I have a new computer now and that one is going back 
>>> into retirement. I may want to use it more in future and would like to 
>>> know how I would go about "mothballing" it so that if it ever needs to 
>>> be used again, bringing it up to date will be as smooth and painless 
>>> as possible. If I need to resurrect it, it will probably be at least a 
>>> year from now. What would you recommend?
>>>
>>> Marcus
>>>
>>>
>>>       
>> Portage is better but that is a while to go without a update.  It mostly 
>> depends on what all is updated with some sort of hiccup between the time 
>> you shut it down and the time you try to update it again.  If there is 
>> no major problems then it wouldn't be a issue but of there is multiple 
>> packages with issues, then you have a problem.
>>
>> Me, I would put it in a closet or something with a ethernet cable hooked 
>> up and just update it say once every 6 to 8 weeks.  Just hope for the 
>> best after that.
>>
>> Dale
>>
>> :-)  :-) 
>>     
>
> I have an "emergency desktop" system at work that I recently pulled out
> of storage to use (laptop HD died!).  Once used, I spent quite a while
> updating it and was just going to put it aside using Dales suggestion
> when this thread got me thinking.
>
> I am going to clean out gnome and anything not of immediate use leaving
> just a bare desktop and minimal tools needed for emergency use (OO,
> evolution) - I'll replace gnome with fluxbox first.
>
> Then if it needs to get serious use other packages can be added on the
> fly.  If it looks like longer term use, its easy to add gnome etc back
> overnight, and while continuing to use the fluxbox desktop.
>
> The minimal system should be quicker and simpler to update than a crufty
> system - and if you have to update much of gnome and the like,
> updating/reinstalling might take longer than building from scratch
> anyway (going by my last update to gnome :)
>
> BillK
>
>   

I should also add that I use KDE.  So, updating all that takes time plus 
if there are packages with "issues" then that adds to the grief.  It 
appears that it depends on just what you have installed.  If it is a 
bare system, then it may not be to bad.  If it is a full blown KDE like 
mine, then that could take a really long while.  Of course, portage has 
been a lot better at handling blocks here lately too.  There are 
exceptions and they always confuse the heck out of me but it is a lot 
better.  That should shorten the update time for a lot of packages.

Maybe a 'emerge -ep world | genlop -p' would be in order here. 

Dale

:-)  :-) 



  reply	other threads:[~2009-12-28  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  1:58 [gentoo-user] Mothballing a ~arch gentoo system? Marcus Wanner
2009-12-28  2:45 ` Dale
2009-12-28  5:41   ` William Kenworthy
2009-12-28  6:27     ` Dale [this message]
2009-12-28  8:40       ` William Kenworthy
2009-12-28 15:58         ` Marcus Wanner

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=4B384FD2.50907@gmail.com \
    --to=rdalek1967@gmail.com \
    --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