From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35806@debbugs.gnu.org
Subject: bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems
Date: Mon, 20 May 2019 17:01:40 +0200 [thread overview]
Message-ID: <87o93xrwyz.fsf@gnu.org> (raw)
In-Reply-To: <20190520093855.3ldl2mjhgi3fx6qz@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Mon, 20 May 2019 11:38:55 +0200")
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
Hi!
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> on a system newly installed from the 1.0.1 ISO image — on only some
> reinstalls. Maybe it was my fault, but maybe not, it is kind of
> spooky. Can others reproduce?
No. (I did many installs in VMs before the release… :-))
Note that you can check by doing an install in a VM using the attached
script.
> The content of /etc/shadow was
>
> root:$6$vWBy92HZjt$P.g83qzyyuZ0AebfKjsS/gZV.1SlaMkUqsmsO9cP1yXtpsCIE.9gDNDtMVwZWa..wmvVNqjqgjg7OFhKadshF.:18036::::::
So a password was set, as expected. Maybe you tried the wrong password,
or with the wrong keyboard layout?
Thanks,
Ludo’.
[-- Attachment #2: the script --]
[-- Type: text/plain, Size: 364 bytes --]
#!/bin/sh
set -e
set -x
ISO="$(./pre-inst-env guix system disk-image --file-system-type=iso9660 gnu/system/install.scm)"
qemu-img create -f qcow2 /tmp/t.img 10G
#EFI_OPTS="-bios $(guix build ovmf)/share/firmware/ovmf_x64.bin"
exec qemu-system-x86_64 -enable-kvm -hda /tmp/t.img -cdrom "$ISO" -m 1024 -boot d -net user -net nic,model=virtio -no-reboot $EFI_OPTS
next prev parent reply other threads:[~2019-05-20 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 9:38 bug#35806: Login passwords incorrect on some newly installed 1.0.1 systems pelzflorian (Florian Pelz)
2019-05-20 15:01 ` Ludovic Courtès [this message]
2019-05-20 20:02 ` pelzflorian (Florian Pelz)
2019-05-20 20:36 ` Ludovic Courtès
2019-05-20 20:41 ` pelzflorian (Florian Pelz)
2019-05-27 10:03 ` Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o93xrwyz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35806@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.