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] Machine completely broken; Ncursed!
Date: Sat, 11 Apr 2015 20:58:09 -0500	[thread overview]
Message-ID: <5529D131.7000405@gmail.com> (raw)
In-Reply-To: <5529BF6C.7090909@verizon.net>

Alan Grimes wrote:
> Andreas K. Huettel wrote:
>
>> If you kept your system updated all the time, you shouldnt have any
>> problems.
> Byte me.
>
> Linux is crap, it takes all the talent I have to keep this piece of junk
> running. =( I'm the user here, I am not going to take any lip from you
> about how I run my system. =|  I put a great deal more work into
> maintaining my system than most of the rest of you.
>
>

Gentoo is not like binary systems.  Most binary systems, you can upgrade
even after years of not doing any upgrading.  Gentoo doesn't like that. 
Officially Gentoo is supposed to have a upgrade max of one year.  Thing
is, that depends on what changes has taken place in that year.  There
are times when some major changes happen and even if it hasn't been 6
months since a upgrade/update, a person is just as well off to reinstall
and keep their sanity.  That could vary depending on how complex some
things may be to set up again. 

So, if you plan to use Gentoo, keeping a system fairly up to date is the
best way to avoid having to deal with some problems that leave you
kicking and screaming for mercy.  I've found that once a week does
fairly well.  Some on this list have posted they go a month. 

Hope that helps.

Dale

:-)  :-) 



  parent reply	other threads:[~2015-04-12  1:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 14:22 [gentoo-user] Machine completely broken; Ncursed! Alan Grimes
2015-04-11 14:34 ` Neil Bothwick
2015-04-11 17:22   ` Mick
2015-04-11 19:41   ` Alan Grimes
2015-04-11 21:27     ` Neil Bothwick
2015-04-11 20:04 ` Andreas K. Huettel
2015-04-12  0:42   ` Alan Grimes
2015-04-12  0:58     ` [gentoo-user] " walt
2015-04-12  1:02     ` [gentoo-user] " Peter Humphrey
2015-04-12  1:58     ` Dale [this message]
2015-04-12  9:12     ` J. Roeleveld
2015-04-12 17:23       ` [gentoo-user] " »Q«
2015-04-12 18:35         ` Matti Nykyri
2015-04-13  1:07           ` »Q«
2015-04-13  5:48             ` Alan McKinnon
2015-04-14  2:08               ` »Q«
2015-04-12 20:07         ` J. Roeleveld
2015-04-13  1:15           ` »Q«
2015-04-13  1:24             ` Alec Ten Harmsel
2015-04-13  1:38               ` »Q«
2015-04-13  1:52                 ` Alec Ten Harmsel
2015-04-14  1:55                   ` »Q«
2015-04-13  5:52                 ` Alan McKinnon
2015-04-14  3:38                   ` »Q«
2015-04-13  7:51                 ` Neil Bothwick
2015-04-14  3:51                   ` »Q«
2015-04-14  7:47                     ` Neil Bothwick
2015-04-15  3:09                       ` »Q«
2015-04-15  8:24                         ` Neil Bothwick
2015-04-12  9:31     ` [gentoo-user] " Neil Bothwick
2015-04-12 14:13     ` Andreas K. Huettel
2015-04-11 23:23 ` Fernando Rodriguez
2015-04-12  1:25   ` Alan Grimes
2015-04-12  0:06 ` Peter Humphrey
2015-04-12  1:27   ` Alan Grimes
2015-04-12 14:52     ` Peter Humphrey
2015-04-16  2:40 ` Fernando Rodriguez

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=5529D131.7000405@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