public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Peter Humphrey" <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug
Subject: Re: [gentoo-user] Re: Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug
Date: Sat, 05 Dec 2009 17:26:48 +0100	[thread overview]
Message-ID: <bDtOqPhD.1260030408.5698450.humphrey@ukfsn.org> (raw)
In-Reply-To: <20091205051452.GB4840@ca.inter.net>


On 5/12/2009, "Philip Webb" <purslow@ca.inter.net> wrote:

>Anyway, don't do testing on the machine you use for everyday computing.
>If you want to get into testing, use a dedicated machine for it.

I've been using a separate partition on an existing machine to run a
~amd64 system for evaluation, and yesterday I got my comeuppance. I
wanted to go back to an earlier backup of the test system*, so I took a
backup of my home directory with its e-mail history, wiped the partition
and restored the old backup followed by the home directory. Wrong. I'd
mixed the home directories of the two systems and so I lost the last
five weeks' worth of e-mails.

And no, I hadn't been drinking or getting over-tired. Just goes to show
- you can't be too careful.

* The current test system had a series of KDE-4 problems, which I thought
must have been caused by the patch bug, but simply remerging everything
installed since then hadn't fixed them.



  parent reply	other threads:[~2009-12-05 16:27 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 16:02 [gentoo-user] Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug Nikos Chantziaras
2009-12-02 10:51 ` Alan McKinnon
2009-12-02 13:45   ` [gentoo-user] " Nikos Chantziaras
2009-12-02 14:18     ` Neil Bothwick
2009-12-02 16:11       ` Volker Armin Hemmann
2009-12-02 14:33     ` Kevin O'Gorman
2009-12-02 14:48     ` Philip Webb
2009-12-02 15:30       ` Alan McKinnon
2009-12-02 15:49         ` Jesús Guerrero
2009-12-02 17:59         ` Stefan G. Weichinger
2009-12-02 20:04           ` Alan McKinnon
2009-12-02 20:54           ` Stefan G. Weichinger
2009-12-02 16:12       ` Nikos Chantziaras
2009-12-02 16:21       ` Neil Bothwick
2009-12-02 16:46       ` felix
2009-12-04 23:02       ` daid kahl
2009-12-05  5:14         ` Philip Webb
2009-12-05  6:47           ` Dale
2009-12-05 13:31           ` Volker Armin Hemmann
2009-12-05 14:10             ` Dale
2009-12-05 17:24               ` Neil Bothwick
2009-12-06  1:15                 ` Dale
2009-12-06  2:21                   ` Philip Webb
2009-12-06  2:53                     ` daid kahl
2009-12-06  9:06                       ` Dale
2009-12-07 10:46                       ` Neil Bothwick
2009-12-07 10:48                   ` Neil Bothwick
2009-12-07 11:18                     ` Dale
2009-12-05 15:08             ` Neil Bothwick
2009-12-05 16:10               ` Volker Armin Hemmann
2009-12-05 19:09             ` Philip Webb
2009-12-05 20:14               ` Volker Armin Hemmann
2009-12-06  6:20                 ` Alan McKinnon
2009-12-06  6:19               ` Alan McKinnon
2009-12-06 19:49                 ` Philip Webb
2009-12-07 11:01                   ` Neil Bothwick
2009-12-07 22:46                     ` Philip Webb
2009-12-07 23:04                       ` Alan McKinnon
2009-12-08  0:17                         ` Dale
2009-12-08 11:19                         ` Arttu V.
2009-12-08  1:04                       ` Neil Bothwick
2009-12-05 16:05           ` daid kahl
2009-12-05 16:26           ` Peter Humphrey [this message]
2009-12-06 10:59             ` Peter Humphrey
2009-12-06 14:11             ` Volker Armin Hemmann

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=bDtOqPhD.1260030408.5698450.humphrey@ukfsn.org \
    --to=peter@humphrey.ukfsn.org \
    --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