linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Iribarne (GMail)" <netstv@gmail.com>
To: "Clint Thomas" <cthomas@soneticom.com>
Cc: Jason Lamb <JLamb@soneticom.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Continuous Login Loop
Date: Wed, 6 Sep 2006 14:20:30 -0700	[thread overview]
Message-ID: <b4b98b690609061420j4a790227jbac4a681136dc52a@mail.gmail.com> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA24095291C3C92@bluefin.Soneticom.local>

On 9/6/06, Clint Thomas <cthomas@soneticom.com> wrote:
>
>
> Hey,
>
> I'm running the latest kernel pull from the mvista powerpc 2.4 dev source. I
> built a root file system using Busybox 1.2.0 and the mkrootfs script by
> Wolfgang Klingauf (removed all DOS carriage returns). When the system boots
> up, i'm getting this output.
>
> Mounted devfs on /dev
> Freeing unused kernel memory: 44k init
> init started:  BusyBox v1.2.0 (2006.09.06-19:44+0000) multi-call binary
> Starting pid 10, console /dev/console: '/etc/init.d/rcS'
> Bummer, could not run '/etc/
> PowerPC Linux 2.4.26
> (none) login: root
> Process '/sbin/getty 38400 tts/0' (pid 11) exited.  Scheduling i
> PowerPC Linux 2.4.26
> (none) login:
>
> it keeps looping through the login every time I try to enter root. I have
> the root user in the passwd file, and I believe I have the RFS setup
> properly. What would cause this kind of an issue? Is this a problem related
> to getty? or just a missing file or device of some kind? Thanks
>

Hi Clint,

You know in the back of my head (very dusty place) I seem to recall
that this is a Busybox issue with getty.  Something about security.
Not sure... but I'd check with their forums.

-stv
>
>
> Clinton Thomas
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>

      reply	other threads:[~2006-09-06 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 21:08 Continuous Login Loop Clint Thomas
2006-09-06 21:20 ` Steve Iribarne (GMail) [this message]

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=b4b98b690609061420j4a790227jbac4a681136dc52a@mail.gmail.com \
    --to=netstv@gmail.com \
    --cc=JLamb@soneticom.com \
    --cc=cthomas@soneticom.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).