From: Graham Newton <gnewton@peavey-eu.com>
To: buildroot@busybox.net
Subject: [Buildroot] Console login root needing a password
Date: Thu, 03 May 2012 13:35:39 +0100 [thread overview]
Message-ID: <4FA27B9B.3080108@peavey-eu.com> (raw)
In-Reply-To: <CAG6aBkWE0X1fm9LatHE9V+c_kvqvpkYkxZzE+xzEiVcgX6LGwA@mail.gmail.com>
On 03/05/12 10:30, Nigel Sollars wrote:
> Hello Yegor,
>
> The only ttyO2 i have is in inittab and it looks like this:
>
> ttyO2::respawn:/sbin/getty -L ttyO2 115200 vt100
>
> This works fine ( I am able to log in ) on a previous build I did
> without a toolchain.
>
> Here is the link that i referred to ( from google )
>
> http://lists.busybox.net/pipermail/buildroot/2010-May/034546.html
>
> Hope this helps
> Nige
>
> On Thu, May 3, 2012 at 2:45 AM, Yegor Yefremov
> <yegor_sub1 at visionsystems.de <mailto:yegor_sub1@visionsystems.de>> wrote:
>
> Am 03.05.2012 01:38, schrieb Nigel Sollars:
> > Hello,
> >
> > Ive built buildroot with a toolchain successfully, however
> trying to login over the console requires a password. The
> passwd/shadow is the default.
> >
> > Looking around google apparently this has to do with wchar is
> this true?, if so is there a fix since this is required for gdb
> on the target.
>
> Have you tried something like this?
>
> ttyS0::respawn:-/bin/sh
>
> Yegor
>
>
>
>
> --
> "Science is a differential equation. Religion is a boundary condition."
>
> Alan Turing
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Hi
I recently had this issue when I directly mounted the buildroot
generated filesystem via NFS. After a frustrating day I discovered that
the suid bit had be set on the busybox executable. So when login was
run busybox ran as an unknown user (not root) and so failed causing the
login to fail. The fix was to run chmod -s busybox on the NFS server.
What was baffeling was that the issue went away if I copied the
filesystem somewhere else.
In the course of my investigations I found I could login if I tried
Yegor's solution but it did not give me root access.
Hope this helps
Graham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120503/fcf3239d/attachment-0001.html>
next prev parent reply other threads:[~2012-05-03 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 23:38 [Buildroot] Console login root needing a password Nigel Sollars
2012-05-03 6:45 ` Yegor Yefremov
2012-05-03 9:30 ` Nigel Sollars
2012-05-03 12:06 ` Yegor Yefremov
2012-05-03 12:35 ` Graham Newton [this message]
2012-05-03 13:42 ` Thomas Petazzoni
2012-05-04 3:04 ` Nigel Sollars
2012-05-04 6:22 ` Thomas Petazzoni
2012-05-04 6:32 ` Yegor Yefremov
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=4FA27B9B.3080108@peavey-eu.com \
--to=gnewton@peavey-eu.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