![]() | |||||||||||||
Messages in this thread |
On 22/06/07, Chuck Ebbert <cebbert@redhat.com> wrote: [snip] > > Step 1: run fsck on the filesystem. > I agree that running fsck on the filesystem is a good idea, but still, even a corrupt filesystem should never be able to cause an Oops. In fact, nothing done from userspace should be able to cause an Oops. -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-06-24 22:53 [from the cache] ©2003-2008 | |||||||||||||