Date: Tue, 25 Jun 1996 08:20:51 -0500 (CDT) From: john goerzen <jgoerzen@cs.twsu.edu> To: FreeBSD-questions@freebsd.org Cc: FreeBSD-bugs@freebsd.org, FreeBSD-hackers@freebsd.org, jgoerzen@cs.twsu.edu Subject: Plea for help! And panic & bug reports! Message-ID: <Pine.SUN.3.91.960625080946.22401A-100000@mccoy>
next in thread | raw e-mail | index | archive | help
(NOTE...This is not my normal account. As such, it's not subscribed to the list. Please CC your reponse to me here -- jgoerzen@cs.twsu.edu! THANKS!) I am not currently able to access my mail on my normal computer, so please CC your response here. I have recently upgraded from FreeBSD 9605?? to 960612 SNAP. The biggest problem is this: I cannot login! As root, as my normal user account, etc. It just says "Invalid login." After rebooting the first time under the new OS, I did not have to enter a password for root. I did copy passwd and master.passwd from the backup of the etc directory, ran pwd_mkdb or whatever that program is called, etc. No go! I was using DES for passwords, BTW. And yes, I did install the encryption stuff from the sysinstall program. Now then...The reason I upgraded was a kernel panic when I accidentally bumped the eject button on my Sony CDU33A CD-ROM drive. I relized my mistake as soon as I did it, and wanting to prevent and problems, I quickly unmounted it. Then I got a kernel panic. There were no programs attempting to access the CD-ROM at the time. I came across a number of bugs in the installation program. 1) In the upgrade menu, it fails to load the partition program. The label program then gets into a loop of complaining that no partitions were selected. Had to reboot, go to custom, select partitions, then go to upgrade. 2) Selecting COM2 for the PPP caused the PPP to fail on any com port. Had to reboot, delete lock files, select COM1, then in PPP, type "set device /dev/cuaa1" to make it work on COM2. 3) ftp.freebsd.org was busy. Install program complained, retried once, then said the installation failed and forced a reboot. Very annoying! Had to then re-mount drives, select packages, etc. several times. It also failed to delete the lock files before rebooting. 4) Modem dropped connection -- sometimes dirty lines around here. Program should have timed out on the FTP, and asked to re-enable connection. Instead, it locked until a reboot. 5) Prorgam garbled the string holding the location of the custom etc backup directory. I had entered my own value -- after it had backed it up so many times, I didn't want to overwrite anything important. It was garbage on the screen when it reported that it couldn't reconstruct it. I then did a cp -Rp and edited sysconfig and copied ppp.conf back to do basic reconstruction. 6) Failed to put a kernel in / ! I had to boot kernel.GENERIC to make it "work". 7) Failed to preserve password files. Caused lots of problems I have not yet solved! Now I've worked around all the sysinstall problems except the password file problem. I need help on that one desperately! Please, if at all possible, send me an e-mail here -- this account is not subscribed to the list and I can't log in to use my regular one! -- I will be very appreciative! PS...I realize this is prerelease code. I am not complaining about bugs. I am simply reporting them and asking for assistance in working around one of them. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.960625080946.22401A-100000>