Actually, that is what I expect to get tomorrow, when I have access to
hardware and can verify it.
> It's not a debug printk. Please leave the messages in, it's really
> helpful to see what failed when mount doesn't succeed.
Yes, I agree. It is any the "Cramfs didn't find it's magic number,
now we'll try another filesystem instead. Usually this should be
harmless and you can safely ignore this message." that bothers me,
because the current wording sounds more like "Something terrible has
happened, go and find someone to bug with this."
What do you propose instead?
Jörn
-- Everything should be made as simple as possible, but not simpler. -- Albert Einstein - 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/