public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard Drive Crash - Please Help
Date: Sat, 27 Jan 2007 12:10:39 -0800	[thread overview]
Message-ID: <49bf44f10701271210u12c1edcbt1d1323f0c96f36a1@mail.gmail.com> (raw)
In-Reply-To: <20070127194353.GA22364@tarantula.kolej.mff.cuni.cz>

> > and the vi command always seg faults.  Does that mean the /dev/hda3
> > image is done-for and I should just start the laptop over from scratch
> > and import my /etc/ and /home/ directories when it's re-installed?
>
> I would try putting it all back and re-emerge everything (emerge -vaD
> --emptytree world). It would fix if anything bad happened to the compiled
> things and you could start using the things which survived sooner.

I tried re-emerging vim from within the chroot and I got:

/usr/portage/eclass/vim.eclass: line 342: make: command not found

What do you think?

- Grant
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-01-27 20:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 16:20 [gentoo-user] Hard Drive Crash - Please Help Grant
2007-01-25 17:22 ` Thomas Lingefelt
2007-01-25 18:20   ` Grant
     [not found]     ` <49bf44f10701251028n5813295cycdd61aea0cc08347@mail.gmail.com>
2007-01-25 19:16       ` Etaoin Shrdlu
2007-01-25 21:19         ` Kent Fredric
2007-01-26 17:47           ` Grant
2007-01-26 18:16             ` Grant
2007-01-26 20:24               ` Randy Barlow
2007-01-26 20:20             ` Neil Bothwick
2007-01-26 22:16               ` kashani
2007-01-26 22:43             ` Matthias Bethke
2007-01-27  1:53               ` Grant
2007-01-27 16:38                 ` Grant
2007-01-27 18:23                   ` Mick
2007-01-27 18:51                     ` Grant
2007-01-27 19:43                       ` Michal 'vorner' Vaner
2007-01-27 20:10                         ` Grant [this message]
2007-01-27 20:33                           ` Mark Kirkwood
2007-01-27 21:01                             ` Grant
2007-01-27 21:19                               ` Mark Kirkwood
2007-01-27 22:39                                 ` Grant
2007-01-27 23:03                                   ` Mark Kirkwood
2007-01-28  0:01                                     ` Grant
2007-01-28  6:54                                       ` Mark Kirkwood
2007-01-28  4:36                                     ` Grant
2007-01-28  6:26                                       ` Kent Fredric
2007-01-28  6:20                               ` Kent Fredric
2007-01-28  6:17                       ` Kent Fredric
2007-01-27 23:09                   ` Neil Bothwick
2007-01-27 23:20                     ` Neil Bothwick
2007-01-28  0:05                     ` Grant
2007-01-28 10:37                       ` Neil Bothwick
     [not found]                 ` <20070127171100.GF11364@huxley>
2007-01-27 17:34                   ` Grant
2007-01-28 15:55                     ` Matthias Bethke
2007-01-28 17:15                       ` Grant
2007-01-28 17:40                         ` Uwe Thiem
2007-01-28 17:58                         ` Mark Knecht
2007-01-29 16:08                           ` Grant
2007-01-25 17:55 ` Matthias Bethke

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=49bf44f10701271210u12c1edcbt1d1323f0c96f36a1@mail.gmail.com \
    --to=emailgrant@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