All of lore.kernel.org
 help / color / mirror / Atom feed
From: Poole, Donald R. <drpoole@swri.org>
To: buildroot@busybox.net
Subject: [Buildroot] FW: Buildroot RFS Login Question
Date: Tue, 24 Jan 2012 19:59:50 +0000	[thread overview]
Message-ID: <CB4468D5.2D36%donald.poole@swri.org> (raw)
In-Reply-To: <CB44467D.2D31%donald.poole@swri.org>

On Sun, Jan 22, 2012 at 3:43 PM, Peter Korsgaard <jacmet at sunsite.dk<mailto:jacmet@sunsite.dk>> wrote:
>>>>> "Donald" == Donald Poole <donny3000 at gmail.com<mailto:donny3000@gmail.com>> writes:

Hi,

CC'ed the buildroot list. Please keep replies on the list as well.

 Donald> Hello Peter,

 Donald>     First off, I would like to send my thanks and gratitude to
 Donald>     you and your team for creating/maintaining the buildroot
 Donald>     embedded filesystem generator.   It is a wonderful tool
 Donald>     that has save me (and I'm sure countless others) a lot of
 Donald>     time putting together a robust working filesytem for
 Donald>     embedded systems.

Thanks!

 Donald>     But, I do have a question regarding how
 Donald>     to login into the system once the filesystem is copied over
 Donald>     to the flash medium, nfs, etc.  Is there a particular
 Donald>     username/password to use for logging into the system once
 Donald>     booted?  I've searched the internet and read a lot of
 Donald>     mailing lists and forums with no success.  My only solution
 Donald>     is to edit the /etc/inittab file and add the -n option for
 Donald>     no login prompt.  But I'd like use the login prompt for
 Donald>     security and not having to hack the /etc/inittab file as a
 Donald>     work-around.  I'm sure it's something dirt simple that I'm
 Donald>     missing, but I can't seem to put a finger on it.  Any help
 Donald>     would be greatly appreciated!   Thanks in advance!

Ehh, unless you are using a custom filesystem skeleton, you should have
a root user without any password set. Does that not work for you?

If it doesn't, then please provide some more details about your setup
(buildroot config, how you boot your system, error messages?, ..)

--
Bye, Peter Korsgaard

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

victory-embedded login:

I'm using the default filesystem skeleton.  I'm not sure what buildroot config information would be helpful, so I will need some more direction on what to give you guys for assistance. But i am using udev, my getty port is ttymxc0 at 115200 baudrate and I'm using BusyBox 1.19.x in the "Package Selection for Target" configuration.  I'm also using buildroot version builroot-2011.11.

Thanks,
Donald R. Poole, Jr.
Research Engineer
Voice: 210.522.3131 | Fax: 210.522.4931
Tactical Networks & Communications (tacticalnetworks.swri.org)
Southwest Research Institute (SwRI)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120124/85d121a6/attachment.html>

       reply	other threads:[~2012-01-24 19:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CB44467D.2D31%donald.poole@swri.org>
2012-01-24 19:59 ` Poole, Donald R. [this message]
2012-01-26  7:01   ` [Buildroot] Buildroot RFS Login Question Sinan Akman
2012-01-26 14:59     ` Poole, Donald R.
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

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=CB4468D5.2D36%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 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.