I did a cvs update yesterday (-rOPENBSD_5_7, previous update toward the end of June) in the middle of network problems.
Updated src and then ports and then xenocara. Took from about eight in the morning to about eleven at night. So, without doing a build, I went back and updated ports and then src again, to get everything in sync as best I could. Built the kernel, checking myself against the FAQ. The previous build was with GPT enabled, but this build was plain GENERIC. Thought login was freezing after the welcome message, beacause there was no prompt. So I hit the power button, watched it stop CUPS and something else and sync, and moved the old kernel back in for a build with GPT enabled, as a first wild guess. Same results, but I tried a few commands instead of just assuming no prompt meant freeze, and the "only" problem seems to be lack of prompt. Sort of. Piping to a pager doesn't page either. "set" does show that the prompt variable and other such things are set like they're supposed to be. The previous kernel behaves itself, as it should. I'm thinking I'm going to go ahead and try building userland, to see if that restores things, but I thought I'd ask how unusual this kind of behavior between building the kernel and the userland is. I'll post the dmesg from the GPT kernel, at least, before I start the build. I erased the non-GPT kernel without getting a dmesg, but I can build it again if someone tells me I should before then. -- Joel Rees Computer memory is just fancy paper, CPUs just fancy pens. All is a stream of text flowing from the past into the future.
