Op maandag 12 augustus 2013 00:13:08 schreef Felix Miata:
On 2013-08-10 05:31 (GMT-0400) Felix Miata composed:
Twice in less than two weeks, minimal X, HTTP method, first M3, now M4, installation proceeded uneventfully nearly to end, then aborted, sometime after /boot/grub/menu.lst was written, but before /root/inst-sys/ was created. System booted, but login failed until I replaced passwd and shadow files with those from another installation. Athlon XP 2400+ CPU, 1G RAM.
Normal y2log set of M4 logs: http://fm.no-ip.com/Tmp/SUSE/Factory/y2l-kt880-131M4.tgz
Extended set: http://fm.no-ip.com/Tmp/SUSE/Factory/y2lsubst-kt880-131M4.tgz
Is this only me? Searching Factory installation bug comments for any of [abort,incomplete,fails] turns up no hits resembling this.
I just noticed beggining a 2nd M4 installation that the default passwd encryption type is SHA512. Is this a change in default type from 12.3? Could it be the reason why I've been unable to login following aborted installations, or why they were aborted late?
No it has been SHA512 before. When asked to enter a user name and password in YaST during installation, you can choose to change the encryption, where you can select to copy users from a previous installation. I did not change SHA512 and copied users, which works after completing the installation. Apparently you only copy some of the content of /etc/passwd and /etc/shadow not /etc/group when one of the copied users has its own group id. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org