[jggimi]

1. The error messages you posted here just now indicate a missing or damaged /etc/login.conf.
2. You must learn some new disciplines:

• Disaster recovery:

• Institute a backup schedule -- a cadence of full and incremental or differential backups, to recover from problems caused by hardware failures, software failures, or your own (or your users) errors.
• Develop and practice recovery procedures until you have a clear and repeatable process so that you are able to restore a complete system onto "bare metal" -- starting with a computer that has no software on it at all.

• Problem reporting:
  • Please read the following quote. I've linked you to it once or twice, but you haven't read it, or haven't understood it. Please, try again.

How to create a problem report

Always provide as much information as possible. Try to pin-point the exact problem. Give clear instructions on how to reproduce the problem. Try to describe the problem with as much accuracy and non-confusing terminology as possible, especially if it is not easy to reproduce. Describing problems like "it crashes" or "I get strange interrupt issues on this one box that I built", are of no use. Communicate with others (on the mailing lists, or any other forum where knowledgeable users congregate) to confirm that the problem is new and preferably repeatable. Please try to make sure it is not a local problem created by broken/unsupported hardware, or by using unsupported build options or software. Please don't start fixing problems that require significant work until you are sure you understand them, especially during our release periods when we must not change major sections of code. If you are going to write significant amounts of code, check various forums to make sure that someone else is not working on the problem (saving duplication of effort).
The following items should be contained in every bug report:

1. The exact sequence of steps from startup necessary to reproduce the problem. This should be self-contained; it is not enough to send in a bare command without the arguments and other data you supplied to it. If a bug requires a particular sequence of events, please list those. You are encouraged to minimize the size of your example, but this is not absolutely necessary. If the bug is reproducible, we'll find it either way.
2. The output you got. Please do not say that it "didn't work" or "failed". If there is an error message, show it, even if you don't understand it. If OpenBSD panics with a particular error, say which. If nothing at all happens, say so. Even if the result of your test case is a program crash or otherwise obvious it might not happen in our testing. The easiest thing is to copy the output from the terminal, if possible. Note: In case of fatal errors, the error message provided might not contain all the information available. In that case, also look at the output in the system log files, such as those stored in /var/log. Also, if you are dealing with an application that has its own log files, such as httpd, check for errors where it keeps its logs (in the case of httpd, this is /var/www/logs).
3. The OpenBSD kernel output. You can get this with the dmesg command, but it is possible that your dmesg output does not contain all the information that is captured in /var/run/dmesg.boot. If this is the case, include information from both. Please include this in all bug reports.
4. If you run third-party software which has to do with your bug, say so, including any subversion that software may have. If you are talking about a CVS or FTP snapshot, mention that, including its date and time.
5. A traceback from your kernel panic. If your kernel panic'ed, and you are at a ddb> prompt, then please provide the panic message, as well as the output of the trace and ps commands in your bug report as advised. If the machine hangs, try enabling sysctl ddb.console=1 prior to the hang and getting in DDB via Ctl+Alt+Esc on the keyboard (must be outside of X), or sending BREAK if using a serial console.
   If, for some reason, the panic message is not visible, you can get it again with the show panic command.
   This is essential whenever possible. Panic reports without panic message, traceback and ps output are useless.
   The output of show registers might be of interest as well. You might then want to reboot with boot dump so that a kernel image could be saved by savecore(8) for further post-mortem debugging as described in the crash(8) manpage.
6. If you're reporting a problem with the X Window System on an architecture that uses the X.Org server, please include the full /var/log/Xorg.0.log file in your report in addition to the dmesg.boot information.

Do not be afraid if your bug report becomes rather lengthy. That is a fact of life. It's better to report everything the first time than us having to squeeze the facts out of you. On the other hand, if your input files are huge, it is fair to ask first whether somebody is interested in looking into it.