| To: | linux@cthulhu.engr.sgi.com |
|---|---|
| Subject: | Re: Evidence of Drive Activity to Report |
| From: | Michael Hill <mdhill@interlog.com> |
| Date: | Sat, 16 May 1998 15:43:05 -0400 (EDT) |
| In-reply-to: | <19980511093314.12884@uni-koblenz.de> |
| References: | <13652.59663.188834.236218@mdhill.interlog.com> <13653.59491.302730.251578@mdhill.interlog.com> <35566E3B.109CCAA3@detroit.sgi.com> <19980511093314.12884@uni-koblenz.de> |
| Reply-to: | mdhill@interlog.com |
| Sender: | owner-linux@cthulhu.engr.sgi.com |
ralf@uni-koblenz.de writes: > > Both cases sound like a bad /etc/fstab. Try adding init=/bin/sh to your > firmware command like arguments. You'll get a completly uninitialized > system. Run e2fsck, then you should be able to remount / rw and fix > the fstab. > What should fstab look like? Mine has a single entry (with root-be-0.03) for /proc. I get a bash prompt but e2fsck hangs. Mike -- Michael Hill Toronto, Canada mdhill@interlog.com |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Installer changes..., Alex deVries |
|---|---|
| Next by Date: | Initrd stuff..., Alex deVries |
| Previous by Thread: | Re: Evidence of Drive Activity to Report, ralf |
| Next by Thread: | Re: Evidence of Drive Activity to Report, Leon Verrall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |