From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002534]: Impossible to log
Date: Wed, 12 Mar 2008 07:53:45 -0700 [thread overview]
Message-ID: <1597e22d334bdc04f23c96084bdade77@bugs.uclibc.org> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=2534
======================================================================
Reported By: saga31
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 2534
Category: Architecture Specific
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
======================================================================
Date Submitted: 03-12-2008 04:21 PDT
Last Modified: 03-12-2008 07:53 PDT
======================================================================
Summary: Impossible to log
Description:
Hello,
I have install and setup buildroot, busybox-1.9.1 and linux kenerl
2.6.22.10, but when I want to connect on my board, it's a big problem.
boot:
......
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 80K
Welcome to the Erik's uClibc development environment.
(none) login: root
Jan 1 00:00:05 login[157]: root login on 'console'
Welcome to the Erik's uClibc development environment.
(none) login: default
Welcome to the Erik's uClibc development environment.
(none) login:
I don't know why login fail.
Help me please.
======================================================================
----------------------------------------------------------------------
sjhill - 03-12-08 07:53
----------------------------------------------------------------------
You have not provided enough information. What is your processor
architecture. Which toolchain and versions of all components (binutils,
GCC, uClibc, etc.). Are you using glibc or uClibc? Once you provide the
information, it can be analyzed.
Issue History
Date Modified Username Field Change
======================================================================
03-12-08 04:21 saga31 New Issue
03-12-08 04:21 saga31 Status new => assigned
03-12-08 04:21 saga31 Assigned To => buildroot
03-12-08 07:53 sjhill Note Added: 0005664
======================================================================
next reply other threads:[~2008-03-12 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 14:53 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-12 15:07 [Buildroot] [buildroot 0002534]: Impossible to log bugs at busybox.net
2008-03-12 11:21 bugs at busybox.net
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=1597e22d334bdc04f23c96084bdade77@bugs.uclibc.org \
--to=bugs@busybox.net \
--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