From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot RFS Login Question
Date: Wed, 25 Jan 2012 23:19:39 +0100 [thread overview]
Message-ID: <87aa5b4e84.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CB45C55B.2D94%donald.poole@swri.org> (Donald R. Poole's message of "Wed, 25 Jan 2012 20:56:34 +0000")
>>>>> "Donald" == Poole, Donald R <drpoole@swri.org> writes:
>> Ok, good. How do you create the file system on the SD card exactly?
Donald> I create the file system by first creating a single partition
Donald> (sudo fdisk /dev/sdc && sync && sync in my case and selecting
Donald> the appropriate commands). Then, I format the partition (sudo
Donald> mkfs.ext3 /dev/sdc1 && sync && sync). Finally, I mount the
Donald> partition (sudo mount /dev/sdc1 <some_mount_point>) and untar
Donald> the generated root.tar filesystem tarball to the mount point
Donald> (sudo tar -xvf root.tar -C <some_mount_point> && sync && sync).
That all sounds good.
From your earlier mail you mentioned that you got 'Login incorrect'
right after typing root, so we must end up somewhere here
(busybox/loginutils/login.c):
if (pw->pw_passwd[0] == '!' || pw->pw_passwd[0] == '*')
goto auth_failed;
if (opt & LOGIN_OPT_f)
break; /* -f USER: success without asking passwd */
if (pw->pw_uid == 0 && !check_securetty(short_tty))
goto auth_failed;
/* Don't check the password if password entry is empty (!) */
if (!pw->pw_passwd[0])
break;
..
auth_failed:
..
puts("Login incorrect");
As you're using the default fs skeleton, the pw_passwd[0] and
/etc/securetty tests shouldn't fail, but apparently they do. Could you
enable strace and run
strace -f login
And send the output to the list?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-01-25 22:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 15:16 [Buildroot] Buildroot RFS Login Question Poole, Donald R.
2012-01-25 20:34 ` Peter Korsgaard
2012-01-25 20:56 ` Poole, Donald R.
2012-01-25 22:19 ` Peter Korsgaard [this message]
2012-02-07 6:31 ` Poole, Donald R.
2012-02-07 9:01 ` Peter Korsgaard
2012-02-08 15:20 ` Poole, Donald R.
2012-02-08 16:18 ` Peter Korsgaard
2012-02-08 16:25 ` Poole, Donald R.
2012-02-08 16:34 ` Peter Korsgaard
2012-02-08 23:17 ` Poole, Donald R.
2012-02-09 6:29 ` Peter Korsgaard
2012-02-09 6:49 ` Poole, Donald R.
2012-02-09 8:04 ` Peter Korsgaard
2012-02-09 15:16 ` Poole, Donald R.
2012-02-09 15:36 ` Peter Korsgaard
2012-02-09 19:56 ` Poole, Donald R.
2012-02-09 21:22 ` Peter Korsgaard
2012-02-15 15:22 ` Poole, Donald R.
-- strict thread matches above, loose matches on Subject: below --
2012-01-24 19:59 [Buildroot] FW: " Poole, Donald R.
2012-01-26 7:01 ` [Buildroot] " Sinan Akman
2012-01-26 14:59 ` Poole, Donald R.
[not found] <CAMe6wuROmEc_vWn8AqYdiRa9bo0Yc2iA9WAFbiy+kWohq09=Ag@mail.gmail.com>
2012-01-22 21:43 ` Peter Korsgaard
[not found] ` <CAMe6wuTrAtUXsjByY6pBd9-wZKme0gyvSTzsPnEiFGK3X-n=3g@mail.gmail.com>
2012-01-24 20:29 ` Peter Korsgaard
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=87aa5b4e84.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.