public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How should I clean up my broken system?
Date: Sun, 14 Feb 2010 08:00:34 +0200	[thread overview]
Message-ID: <201002140800.34850.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20100213175105.GB1783@muc.de>

On Saturday 13 February 2010 19:51:05 Alan Mackenzie wrote:
> Thanks!  In the end, I just used the gcc I had on the system anyway; it
> wasn't broken.  I first did 'emerge -e gcc', which took an hour, then did
> 'emerge -e world', which took ~2 hours 30 mins.
> 
> I was being a bit paranoid.  The reason I "gave up" on the installation
> CD was I failed to find out how to start my LVM2 voluble logics, or
> whatever they're called.

Oh yes, I forgot about that. I have old LiveCDs around too that don't support 
LVM. It can get bloody annoying when you forget and use it anyway. These days 
I use RIPLinux on a small spare USB stick as my rescue system


> I'm now back on track, setting up my PC.  Thanks!
> 
> > The paranoid might want to emerge gcc itself on it's own first so that
> > rebuilding world is done with the same gcc version as what it will
> > become (gcc is not built first when you rebuild world, all sort of
> > toolchain tools and parsers are earlier in the list). Personally, I
> > don't do that - there is an actual chance that using an old compiler to
> > build a new compiler may lead to incompatibility issues, but the risk
> > is extremely small and rare, and it's never bitten me.
> 
> There was that apocryphal tale of the origianl Unix hacker who hardwired
> a backdoor login into the system, and hacked cc to keep inserting the
> backdoor each time the system was built, and to keep this hack in cc each
> time cc was compiled.  Whew!

That's not a myth either :-)

There was a story on /. about that very thing just the other day!


-- 
alan dot mckinnon at gmail dot com



      parent reply	other threads:[~2010-02-14  6:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 19:55 [gentoo-user] How should I clean up my broken system? Alan Mackenzie
2010-02-12 19:55 ` Volker Armin Hemmann
2010-02-12 21:21   ` Kyle Bader
2010-02-12 22:52     ` Neil Bothwick
2010-02-13  7:28       ` Alan McKinnon
2010-02-13 20:43         ` Neil Bothwick
2010-02-14  6:01           ` Alan McKinnon
2010-02-14  9:34             ` Neil Bothwick
2010-02-14 11:03               ` Volker Armin Hemmann
2010-02-14 11:32                 ` Neil Bothwick
2010-02-20 12:08                   ` Mick
2010-02-20 12:20                     ` Volker Armin Hemmann
2010-02-21  0:22                     ` Neil Bothwick
2010-02-21  3:12                     ` Iain Buchanan
2010-02-22 11:29                       ` daid kahl
2010-02-22 13:56                         ` Volker Armin Hemmann
2010-02-22 17:06                           ` [gentoo-user] " Harry Putnam
2010-02-26  7:29                             ` daid kahl
2010-02-26 18:20                   ` [gentoo-user] " Peter Humphrey
2010-02-26 18:47                     ` Alex Schuster
2010-02-27  1:02                       ` Peter Humphrey
2010-02-12 23:46 ` William Kenworthy
2010-02-13  7:27 ` Alan McKinnon
2010-02-13 17:51   ` Alan Mackenzie
2010-02-13 18:50     ` Stroller
2010-02-14  6:00     ` Alan McKinnon [this message]

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=201002140800.34850.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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