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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110617000958.GA14695@elie">http://lists.debian.org/20110617000958.GA14695@elie