Thanks for the comments. On Tue, Aug 4, 2015 at 5:43 PM, Joel Rees <joel.r...@gmail.com> wrote: > 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.
I tried deleting all the configurations in /usr/src/sys/arch/`machine`/compile and putting the names of the GPT-enabled configurations in .cvsignore in the same directory, but no desired results. Compiling a GENERIC kernel now produces a kernel that just goes into recursive reset within two lines of output after the boot prompt. Compiling a GPT-enabled kernel produces the results I mention above, unprompted shell, etc. I think this is the effect warned about in reference to working with custom kernels, where I get to keep both pieces. (Heh. So much for keeping the box "-stable".) I'm debating whether to go ahead and compile userland with the misbehaving shell, but I would end up with a system I think I would have reason to distrust, even if it appeared stable. So, the lesson is that custom kernels are not something one wants to have to upgrade or update, I guess. Patch carefully instead of cvs up with stable. And rebuild for the next OS version. Get the work done quickly. And I should avoid doing this kind of dev work on a box that I'm trying to use as a (portable) workstation. Sorry for the noise. -- Joel Rees Be careful when you look at conspiracy. Arm yourself with knowledge of yourself, as well: http://reiisi.blogspot.jp/2011/10/conspiracy-theories.html
