] > Let me rephrase:
] >
] > 1. Terry, is ssh working for you yet?
]
] The /etc/pam.conf additions have fixed some of the systems,
] but not all of them.
]
] The difference between the systems that work with the
] changes, and the onces which do not, is the precise
] upgrade process.
]
] The systems that work were booted from the CDROM, and
] upgraded via the sysinstall upgrade process.
]
] The systems which do not work were booted from the
] hard disk, and upgraded via the sysinstall upgrade
] process, using a copy of the sysinstall from one of
] the successfully upgraded systems (i.e. they were
] _not_ booted from CDROM, since the machines in
] question are rack-mounts without CDROMs in them).
OK, I have a workaround.
The problem is that when you "Upgrade" via sysinstall, if
you did not boot the CDROM to get started, it does not go
ahead and replace /dev/MAKEDEV and /dev/MAKEDEV.local.
So you can remake the random devices until you are blue in
the face, and it still won't work.
So in addition to carrying around a copy of the sysinstall
binary from disc1 (which is only accessible from a booted
CDROM; it should be on the CDROM itself, I believe, as well),
I have to carry around /dev/MAKEDEV and /dev/MAKEDEV.local
(at least it in /dev on disc2, if you have a disc2).
Really, it's pretty broken that it doesn't install these
files from somewhere on the CDROM (it appears to want to copy
them from the booted system, which in my case, is not the
CDROM floppy image with the right files, but the local system,
with the old ones.
With this corrected (and the /etc/pam.conf fix, too), ssh now
works.
These issues should probably be addressed for the next release.
Terry Lambert
[EMAIL PROTECTED]
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
