From: Stanislav Vlasic <svlasic@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to login as root to new buildroot system
Date: Sat, 25 Jul 2015 03:46:19 +0200 [thread overview]
Message-ID: <mouppb$le6$1@ger.gmane.org> (raw)
In-Reply-To: <CAChFQ9R=5anPgo9mboKxCkppsadQkSzC_WhpevWoarwgKVhLQg@mail.gmail.com>
Hi,
On 07/25/2015 02:25 AM, Adam Baxter wrote:
> I'm using the latest Git version of buildroot and the following config -
> https://github.com/voltagex/serial-vm-buildroot
>
> It builds and boots with qemu just fine, but no matter what combination
> of getty/no getty/shell/root password I use, I can't login. Even with a
> blank root password I'm told that the password is incorrect, and I can't
> work out how to make it boot straight to a root prompt.
>
> Can anyone help? The repo above should be able to be built with make
> serial_defconfig, but if there's still hardcoded paths to a 'voltagex'
> or 'ubuntu' user you'll have to let me know how to remove them.
>
> I've read
> http://lists.busybox.net/pipermail/buildroot/2012-July/056177.html and
> similar threads found by googling "buildroot root login"
>
> Regards,
> Adam Baxter
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
Try edit system/skeleton/etc/passwd file (or overlay one if you're using
overlays) and replace 1st line:
root:x:0:0:root:/root:/bin/sh
with:
root::0:0:root:/root:/bin/sh
Never had that problem on Buildroot, but did on Ubuntu Core rootfs and
this method fixed it.
next prev parent reply other threads:[~2015-07-25 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 0:25 [Buildroot] Unable to login as root to new buildroot system Adam Baxter
2015-07-25 1:46 ` Stanislav Vlasic [this message]
2015-07-25 17:51 ` Adam Baxter
2015-07-26 16:25 ` Thomas Petazzoni
2015-07-26 16:26 ` Adam Baxter
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='mouppb$le6$1@ger.gmane.org' \
--to=svlasic@gmail.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox