Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to login to buildroot
Date: Thu, 24 Feb 2011 12:53:14 +0100	[thread overview]
Message-ID: <87pqqhr6mt.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201102241048.48537.dargaud@lpsc.in2p3.fr> (Guillaume Dargaud's message of "Thu, 24 Feb 2011 10:48:48 +0100")

>>>>> "Guillaume" == Guillaume Dargaud <dargaud@lpsc.in2p3.fr> writes:

Hi,

 Guillaume> Welcome to the Gandalf acquisition
 Guillaume> gandalf login: root
 Guillaume> Jan  1 00:00:10 login[254]: root login on 'ttyUL0'

 Guillaume> Welcome to the Gandalf acquisition
 Guillaume> gandalf login:

 Guillaume> And it repeats... I also cannot login via ssh (I configured
 Guillaume> dropbear) and I have a feeling none of the init.d scripts
 Guillaume> got started. I use the default inittab.

The default skeleton doesn't have a password set for root, and dropbear
doesn't allow root login without a password.

 Guillaume> The drive is mounted via nfs, and there are some missing
 Guillaume> stuff (when looking at them from the NFS server side):
 
 Guillaume> $ ll proc tmp
 Guillaume> proc:
 Guillaume> total 8
 Guillaume> drwxr-xr-x  2 root root 4096 Feb 24 08:31 ./
 Guillaume> drwxr-xr-x 16 root root 4096 Feb 24 09:19 ../

 Guillaume> tmp:
 Guillaume> total 12
 Guillaume> drwxrwxrwt  3 root root 4096 Feb 24 09:24 ./
 Guillaume> drwxr-xr-x 16 root root 4096 Feb 24 09:19 ../
 Guillaume> drwxr-xr-x  2 root root 4096 Feb 24 08:54 ldconfig/
 Guillaume> -rw-r--r--  1 root root    0 Feb 24 09:24 utmp

Looks normal. Proc is a virtual filesystem and /tmp/ is normally a
ramdisk.

 Guillaume> Anything I overlooked ?

Not as far as I can see. You are creating your nfsroot from rootfs.tar
and extracting as root, right?

 Guillaume> Bonus question: if you configure buildroot without an FPU,
 Guillaume> then what is the difference between hard floats and soft
 Guillaume> floats ? Why can you have both and what is preferable ?

Hard float means let the compiler insert hardware FPU instructions
in the code stream whenever floating point calculations are done. Soft
float means add calls to software emulation functions instead.

On a system without a hardware FPU you CAN run hard float binaries if
you have configured the kernel to emulate those instructions, but it
will be very slow. Soft float is preferred.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2011-02-24 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24  9:48 [Buildroot] Unable to login to buildroot Guillaume Dargaud
2011-02-24  9:54 ` Baruch Siach
2011-02-24 10:55   ` Guillaume Dargaud
2011-02-24 11:30 ` Daniel Nyström
2011-02-24 12:59   ` Guillaume Dargaud
2011-02-24 13:28     ` Baruch Siach
     [not found]     ` <4D665ADD.10608@daccii.it>
2011-02-24 14:16       ` Guillaume Dargaud
2011-02-24 15:15         ` Williams, Michael
2011-02-24 15:57           ` Guillaume Dargaud
2011-02-25 11:50           ` [Buildroot] Unable to login to buildroot [SOLVED] Guillaume Dargaud
2011-02-24 11:53 ` Peter Korsgaard [this message]
2011-02-24 14:56   ` [Buildroot] Unable to login to buildroot Guillaume Dargaud
  -- strict thread matches above, loose matches on Subject: below --
2010-03-25 18:11 [Buildroot] unable " sunr2007
2010-03-26 11:37 ` Yury Luneff

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=87pqqhr6mt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox