linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Fry <kevin@carts.com>
To: Mark Hatle <fray@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Init acting strange
Date: Thu, 20 Sep 2001 19:01:03 -0700	[thread overview]
Message-ID: <3BAA9F5F.D216AD44@carts.com> (raw)
In-Reply-To: 3BA7FFAA.11B7B890@mvista.com


Thanks for the help, I was in fact missing /bin/login, and then found I was
missing the libpam libraries in /lib/security after checking the log files.

thanks a lot!

Kevin Fry

Mark Hatle wrote:

> Kevin Fry wrote:
> >
> > I've been trying to get init working for a while now but I can't getting
> > logging in to work correctly, and I'm out of ideas, maybe someone can help
> >
> > I'm using HHL 2.0 and the ramdisk is made from the target app rpms. I'm using
> > the default passwd file. Do shadow passwords or anything like that need to be
> > compiled in the kernel for the hhl2.0 login stuff to work??
>
> Look at your log files, located in /var/log/.  You should see some type
> of an error message.  My guess from your question is that you are
> missing /bin/login, the shadow tools.
>
> --Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-09-21  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19  1:43 How can I tell if an interrupt has occured in MPC860? Choon Hooi Ng
2001-09-19  2:10 ` Init acting strange Kevin Fry
2001-09-19  2:15   ` Mark Hatle
2001-09-21  2:01     ` Kevin Fry [this message]
2001-09-19 16:53   ` Brian Eliot

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=3BAA9F5F.D216AD44@carts.com \
    --to=kevin@carts.com \
    --cc=fray@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).