Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Linux Filesystems Comparison Article
- Date: Sun, 30 Apr 2006 12:03:02 +0900
- From: Edward Middleton <edwardmiddleton@example.com>
- Subject: Re: [tlug] Linux Filesystems Comparison Article
- References: <444F5E39.1000108@example.com> <2d4c9c600604261752s8e3ef5fo701a643acda1113e@example.com> <1146108972.4496.14.camel@example.com> <20060427105939.e37f0136.godwin.stewart@example.com> <445090D0.1060803@example.com> <3535630.1146204807351.JavaMail.hoanga@example.com>
On Thu, 2006-04-27 at 23:13 -0700, Alain Hoang wrote: > I'm currently wondering if there's a way to recover my system without > having to reinstall but considering world is linked against the libc > version that I had, I don't see any easy way to fix this. Any > pointers from more hard-core Linux gurus? (Besides backups). Since > this is my personal desktop machine, I'm not very worried if I have to > redo everything although I'm now curious if there is a way to recover > from such a dilemna. Allways build binary packages. This will allow you to backout of any failed upgrade. You can either emerge the previous binary if it your system is in a workable state or just untar it over the top if emerge is no longer working. You can force the creation of packages on all builds by adding buildpkg to your FEATURES variable in /etc/make.conf > Some options I'm thinking of > 1. Copy all important data I care about, take inventory of installed > pacakges, and reinstall from scratch) Probably your best option, if you have the time. > 2. Untar a stage 3 over the current dead system and try to rebuild > things in place (sounds utterly risky and jumping into an inconsistent > state) I have got the system working doing this but you will probably end up with files that no longer belong to packages. > 3. See if I can rebuild the relevant system libraries somehow and > merge them into the system and see if that gets me limping along just > enough to emerge world If you can do this it would be your best bet. The is basically why you are best to build packages. > 4. Do nothing for awhile and wait for some really bright (or bad) idea > to hit me on how to fix it 5. pull the backup ;) Edward
- Follow-Ups:
- References:
- [tlug] Linux Filesystems Comparison Article
- From: Alain Hoang
- Re: [tlug] Linux Filesystems Comparison Article
- From: Patrick Niessen
- Re: [tlug] Linux Filesystems Comparison Article
- From: Shawn
- Re: [tlug] Linux Filesystems Comparison Article
- From: Godwin Stewart
- Re: [tlug] Linux Filesystems Comparison Article
- From: Edward Middleton
- Re: [tlug] Linux Filesystems Comparison Article
- From: Alain Hoang
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] 2.6 Kernel vs 2.4 Kernel: "internal s/w"
- Next by Date: Re: [tlug] Linux Filesystems Comparison Article
- Previous by thread: Re: [tlug] Linux Filesystems Comparison Article
- Next by thread: [tlug] How to Make Binary Packages from Source (was: Linux Filesystems Comparison Article)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links