> > [2.] Full description of the problem/report:
> > In an attempt to compile Mozilla, after running ./configure several
> > files were left in a state, where they could not be accessed nor
> > removed.
> I suppose that problematic files were those just created. Am I right?
Yes, I ran ./configure just after untarring mozilla.
Yesterday I tried the same thing on kernel 2.3.36pre5 and that made fsck
much more unhappy. :-/
--
Med venlig hilsen
Christian Laursen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/