Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Poole, Donald R. <drpoole@swri.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot RFS Login Question
Date: Thu, 26 Jan 2012 14:59:26 +0000	[thread overview]
Message-ID: <CB46C5B7.2DBB%donald.poole@swri.org> (raw)
In-Reply-To: <4F20FA32.2000000@writeme.com>

On 1/26/12 1:01 AM, "Sinan Akman" <sinan@writeme.com> wrote:


>On 01/24/2012 02:59 PM, Poole, Donald R. wrote:
>
>> Unfortunately, if I use the root user get a "Login Incorrect" message
>>and a new login prompt that looks like this:
>> Starting input-event-daemon: done
>>
>> Welcome to VICTORY Embedded
>> victory-embedded login: root
>> Login incorrect
>
>   Donald, I am not sure if this is what you are asking but if you are
>using imx53Loco board with rootfs that it ships with, you are probably
>aware that you will have to enter user name : lucid  and password : lucid.
>
>   -- sinan

Thanks Sinan for your reply.  I am using the imx53loco board and I am
aware that the user/password is lucid/lucid.  I am developing a custom
rootfs without a desktop environment from scratch using build root and I
am having trouble logging into the system with the appropriate user/pass.

Donald R. Poole, Jr.
Research Engineer
Voice: 210.522.3131 | Fax: 210.522.4931
Tactical Networks & Communications (tacticalnetworks.swri.org)
Southwest Research Institute (SwRI)

  reply	other threads:[~2012-01-26 14:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CB44467D.2D31%donald.poole@swri.org>
2012-01-24 19:59 ` [Buildroot] FW: Buildroot RFS Login Question Poole, Donald R.
2012-01-26  7:01   ` [Buildroot] " Sinan Akman
2012-01-26 14:59     ` Poole, Donald R. [this message]
2012-02-07  8:51   ` [Buildroot] FW: " Samuel Martin
2012-02-08  6:28     ` Poole, Donald R.
2012-02-08  6:57       ` Mark Constable
2012-02-08  7:49         ` Peter Korsgaard
2012-02-08  9:38           ` Samuel Martin
2012-02-08 20:04           ` Mark Constable
2012-02-08 21:18             ` Peter Korsgaard
2012-03-01 15:11               ` Daniel Nyström
2012-01-25 15:16 [Buildroot] " 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
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.
     [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=CB46C5B7.2DBB%donald.poole@swri.org \
    --to=drpoole@swri.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox