From: Kevin Fry <kevin@carts.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Init acting strange
Date: Tue, 18 Sep 2001 19:10:30 -0700 [thread overview]
Message-ID: <3BA7FE96.CA24D4EE@carts.com> (raw)
In-Reply-To: 001e01c140ac$88e8b830$fb5a01d9@crtc.corp.mot.com
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??
here's what I'm seeing:
INIT: version 2.78 booti
Mounting local filesystems...
not mounted anything
Cleaning: /etc/network/ifstate.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces: done.
Cleaning: /tmp /var/lock /var/run.
INIT: Entering runlevel:
Starting system log daemon: syslogd klogd.
Starting internet superserver: inetd.
MontaVista Software's Hard Hat Linux 2.0
(none) login: root
MontaVista Software's Hard Hat Linux 2.0
(none) login: guest
MontaVista Software's Hard Hat Linux 2.0
(none) login: kevin
MontaVista Software's Hard Hat Linux 2.0
(none) login: nobody
MontaVista Software's Hard Hat Linux 2.0
(none) login:
MontaVista Software's Hard Hat Linux 2.0
(none) login:
Thanks guys!
Kevin Fry
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-19 2:10 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 ` Kevin Fry [this message]
2001-09-19 2:15 ` Init acting strange Mark Hatle
2001-09-21 2:01 ` Kevin Fry
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=3BA7FE96.CA24D4EE@carts.com \
--to=kevin@carts.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).