From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot requires a password
Date: Sat, 12 Oct 2013 14:50:21 +0200 [thread overview]
Message-ID: <20131012145021.02d468e4@skate> (raw)
In-Reply-To: <0F793FF065914549A7D55A219164CACB@M58p>
Dear Sabri Altunbas,
On Sat, 12 Oct 2013 14:11:10 +0200, Sabri Altunbas wrote:
> I created a initramfs with buildroot.
> I attach my config
>
> It works. But it requires a password which I have not configured and I wanna
> have no password.
>
> I investigate in forums and find out
>
> http://buildroot-busybox.2317881.n4.nabble.com/Console-login-root-needing-a-
> password-td15155.html
>
> http://buildroot-busybox.2317881.n4.nabble.com/Bug-5366-New-can-t-login-root
> -or-default-td30020.html
>
> I followed all recommendations
>
> - taking output/images/rootfs.cpio
> - BR2_PACKAGE_UTIL_LINUX_LOGIN_UTILS not defined
>
> but only the following solution worked
>
> #ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL
> ttyS0::respawn:/bin/sh # GENERIC_SERIAL
>
> overlooked something ?
By default, there is no password. Can you share your Buildroot .config
file so we can see if something might be causing problems?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-12 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 12:11 [Buildroot] buildroot requires a password Sabri Altunbas
2013-10-12 12:50 ` Thomas Petazzoni [this message]
[not found] ` <72BD24884B4745F4BE4A855D78178642@M58p>
2013-10-12 14:56 ` Thomas Petazzoni
[not found] ` <DE9772AAEF4F4E35B1CA8F3B5A7C7865@M58p>
2013-10-12 15:41 ` Thomas Petazzoni
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=20131012145021.02d468e4@skate \
--to=thomas.petazzoni@free-electrons.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 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.