On Wed, 10 Jan 2007, Chuck Robey wrote:
> I have a problem with my Zaurus, let me paint the scenario. I am a rank
> newbie with OpenBSD, so I was trying (as a startup experiment) to build
> all of it. I have my main machine sitting nearby (running FreeBSD
> current, at which I have years of experience), so I NFS mounted the
> little Zaurus's /usr/src and /usr/obj from my FreeBSD host. I used cvsup
> to get the entire OpenBSD archive, then checked out copies of ports and
> and src (forgot to add ports to my list up on top, I had 3 remotely mounted
> filesystems). OK, I went ahead, built a kernel successfully, and did a
> "make build".
>
> I was kinda shocked to find that the install was included in the build
> target, so this shows me to be a little bit stupid, that I didn't read
> it well enough to make sure, but that's not the problem. I had the new
> kernel
> installed, and it seems to boot ok, but for both of my two user's, once
> I enter my password, it immediately cycles back to "login:" again. I tried
> giving it tons of control'c's but that wouldn't catch it, so I cna't get
> logged in.
>
> Look, as far as emergencies go, I have the orignal Linux OS sitting in
> back as a emergency, and it does work, so if there's no better fix,
> I could reinstall everything, or maybe just my /etc/ but could anyone
> give me guesses as to what sort of screwup I perpetrated, so as to
> keep me from getting logged in? Else, I will probably do this again,
> and I really, really like to learn from my mistakes, you know?
>
> Thanks for your guesses, folks...
Something got broken, and I suspect it was in /etc, but I can't picture
a simple make build in /usr/src as the full culprit here. (This shouldn't
mess with /etc/*. As of yesterday, when I did one (4.0 stable) it didn't.)
so first try this:
at the BOOT> prompt, enter -s ; this should give you "single user mode",
i.e. a root shell on the console, with no filesystems save / mounted.
You can at this point inspect /etc/master.passwd and see what is up.
(Are your users there? what's in their password fields?) Are other things
in /etc messed up? Things that you customized, like /etc/myname, /etc/mygate,
probably /etc/rc.conf, others.
If you find something obvious, you can fix it. First remount / for writing
(mount -u -o rw /) Then you can mount /usr to get some tools (mount /usr
should do it).
Do "dmesg | head" and see what the kernel thinks it is, then read on:
(You will need to mount /usr to get /usr/bin/head, or just "dmesg" and
be quick on the ^S or ^C, or pipe the dmesg to /tmp/foo and use "ed"
on it. In ed, try 1,10p to display lines 1 through 10. Use q to quit.
When you get the system working, print out the ed man page and put it
in your desk.)
You should see something like this:
[EMAIL PROTECTED] root]# dmesg | head -2
OpenBSD 4.0-stable (GENERIC.MP) #3: Wed Jan 10 11:55:06 EST 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
(Probably just "GENERIC" not "GENERIC.MP").
A possible source of your problem: when you checked out the sources, what
tag did you specify in the cvs command? It should have been of the form
-r OPENBSD_4_0. If you didn't specify a tag, you did not get "STABLE",
you got "current", the experimental/developmental branch. You did not
want to do that ;-) If you did, then boot the installation CD and do
a reinstallation. On your freebsd box, you can check the tag by
displaying the file {some path known to you}/src/CVS/Tag. If it's
not "TOPENBSD_4_0" wipe out the hierarchy and re-fetch it. this tag
business applies to the X and ports sources, too.
man 8 release (very most excellent reading, refreshing and engaging,
with a plot you just can't put down.)
man 1 cvs (packed full of vital goodness.)
Dave
