I forgot; I knew what caused this, but forgot to say.
It's handled in /etc/init.d/{checkfs,checkroot}.sh. They both have lines that autologin after fsck with errors, for system repairing. If you comment that one line in both of them, your system will ask for login even with fsck errors.
PS: replace nodma with dma, you'll get about 3x speedThanks Curaga, I'm going to try that now.I think the init.d changes did the trick with the login. If the first run is indicative of what will always happens, it's very, very nice.
Changing to DMA... I don't know why, but it caused my wifi card to connect to the neighbor's WAP so I'm going to leave it at nodma for now. Having some small issues with WPA and will try again when I get past that.
Much thanks.Both of those scripts given an option or warning that it is dropping to a shell to allow manually repairing fsck errors, in which the standard fsck options were not able to repair. This is standard operating procedure. This sort of failure should not normally be encountered and is not as you suggested from a recent change.
Quote
My question is: Is this what I should expect from all Linux distributions or is it something that needs attention because of the addition of multi-user support recently in DSL?
Sorry, I wasn't insinuating anything. I just wanted to understand. My apologoes if my wording offended. I'm trying very hard not to hurt anyone's feelings.Next Page...
original here.