Investigating bugs without risking damage (Re: [bash] Everything Segfaults After lib6 -7 Upgrade)
- To: debian-user@lists.debian.org
- Subject: Investigating bugs without risking damage (Re: [bash] Everything Segfaults After lib6 -7 Upgrade)
- From: Jonathan Nieder <jrnieder@gmail.com>
- Date: Thu, 16 Jun 2011 19:09:58 -0500
- Message-id: <[🔎] 20110617000958.GA14695@elie>
- In-reply-to: <201106161647.22364.d_baron@012.net.il>
- References: <201106151753.00413.d_baron@012.net.il> <20110615212541.GD27172@elie> <201106161647.22364.d_baron@012.net.il>
Hi David,
David Baron wrote:
> (I do not want to unnecessarily try to boot up the errant Sid /lib because of
> possible file system damage.)
Quite understandable, but it makes life hard to be tracking down a bug
from memory only. I would not personally expect an ld.so problem to
cause corruption, just segfaults, not that I expect that to be any
comfort.
Dear debian-user list: do you have any advice for this case? In
particular, any hints for booting up in such a way as to be certain
the root partition remains read-only (never changing it to read/write
at all)?
Thanks much. Please cc me on replies, since I am not subscribed.
Cheers,
Jonathan
Reply to: