public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg won't start
Date: Fri, 10 Jul 2009 08:36:00 -0700	[thread overview]
Message-ID: <9acccfe50907100836n1cc7af89lefff26af1afa2406@mail.gmail.com> (raw)
In-Reply-To: <4A5740FF.4050209@gmail.com>

On Fri, Jul 10, 2009 at 6:24 AM, Dale<rdalek1967@gmail.com> wrote:
> Kevin O'Gorman wrote:
>> On Fri, Jul 10, 2009 at 1:13 AM, Keith Dart<keith@dartworks.biz> wrote:
>>
>>> On Thu, 9 Jul 2009 17:03:20 +0100
>>> Neil Bothwick <neil@digimed.co.uk> wrote:
>>>
>>>
>>>> The elog message from the xorg-server emerge also warns about updating
>>>> drivers.
>>>>
>>> Users should probably make sure there is at least the following
>>> in /etc/make.conf:
>>>
>>> PORTAGE_ELOG_SYSTEM="echo save_summary"
>>>
>>> So you get a permanent record and a change to view them at the end of a
>>> ebuild set.
>>>
>>
>> I've been running with this for years:
>>
>> PORTAGE_ELOG_CLASSES="info, warn, error, log"
>> PORTAGE_ELOG_SYSTEM="save mail"
>> FEATURES="buildpkg parallel-fetch"
>>
>> And I had been thinking that the "buildpkg" was going to make
>> reversion a lot easier, except that I've never actually installed one
>> of these puppies.  Mind, I only tried once.  I've got about 4 GB of
>> packages at the moment.  :o)
>>
>> ++ kevin
>>
>>
>
> You do know about eclean right?  At least that can clean out some old cruft.

I assumed there was some such thing, but I don't want it.  I
miscounted anyway, and included only the partition set aside for old
cruft, where I copy the oldest packages there every year or so -- it
seems I like having them even if I don't know why.  Counting the new
cruft, it's more like 7 GB.  With drive prices being what they are,
it's no big deal.

Since about a year ago, I've been able to afford mirrored 500GB SATA
drives on this machine, with a separage eSATA for backups, and I have
an eSATA at work for offsite backup too.  The external ones fit in my
backpack nicely for the "sneakernet" part of my backup plan.  Having
suffered and paid for hard drive crashes in the past, I really really
love this.

-- 
Kevin O'Gorman, PhD



  reply	other threads:[~2009-07-10 15:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 17:15 [gentoo-user] xorg won't start Kevin O'Gorman
2009-07-08 17:23 ` James Ausmus
2009-07-08 17:28 ` Dirk Heinrichs
2009-07-09 15:05   ` Kevin O'Gorman
2009-07-09 15:36     ` Paul Hartman
2009-07-09 15:58       ` Dale
2009-07-09 16:03       ` Neil Bothwick
2009-07-10  2:26         ` [gentoo-user] " James
2009-07-10  8:13         ` [gentoo-user] " Keith Dart
2009-07-10 10:16           ` Kevin O'Gorman
2009-07-10 13:24             ` Dale
2009-07-10 15:36               ` Kevin O'Gorman [this message]
2009-07-10 13:21           ` Dale
2009-07-10 13:47             ` Neil Bothwick
2009-07-10 13:59               ` Dale
2009-07-10 14:14                 ` Paul Hartman
2009-07-10 15:54                   ` Dale

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=9acccfe50907100836n1cc7af89lefff26af1afa2406@mail.gmail.com \
    --to=kogorman@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