From: Mark Hatle <fray@mvista.com>
To: James F Dougherty <jfd@GigabitNetworks.COM>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: SysVInit (RC Scripts) on HHL 2.0
Date: Thu, 06 Sep 2001 12:22:01 -0500 [thread overview]
Message-ID: <3B97B0B9.4ADDFF9F@mvista.com> (raw)
In-Reply-To: 200109061710.KAA13165@krakatoa.gigabitnetworks.com
James F Dougherty wrote:
> I am using HHL 2.0 (2.4.2) on MPC8240 and I downloaded
> the root filesystem RPM's from
>
> ftp://ftp.mvista.com/pub/Journeyman/cd2/ppc_82xx/apps/*.rpm
>
> and installed them on my root filesystem.
>
> Question: How come none of the init scripts work?
>
> I have to run:
>
> devfsd /dev
> mount -a
>
> every time I boot. It spawns a getty, but none of the rc
> files get called ...
>
> Is there some bug in HHL 2.0 on ppc_82xx I don't know about?
See the HHL-JE-20.pdf file located in the (doc) documentation
directory. I point you at Chapter 7, Additional Configuration
Information. (Specifically at the initdconfig section.)
Assuming you used the installer, only the init scripts required to boot
a minimal system (and be able to telnet in and use nfs root) are
enabled. Anything beyond that you, the developer/user will need to
enable. If you did not use the installer, you probably got a bunch of
messages during installation such as "Unable to enable initd service:
checkfs.sh". These messages mean that the initdconfig program was not
able to be run for some reason or another, thus you probably don't have
ANY initscripts installed.
The initscripts are further discussed in the "Initscript Overview"
section of Chapter 7.
--Mark
MontaVista Software, Inc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-06 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 17:10 SysVInit (RC Scripts) on HHL 2.0 James F Dougherty
2001-09-06 17:20 ` Matthew Locke
2001-09-06 17:22 ` Mark Hatle [this message]
2001-09-06 17:39 ` SysVInit (RC Scripts) on HHL 2.0 (Add'n info) Mark Hatle
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=3B97B0B9.4ADDFF9F@mvista.com \
--to=fray@mvista.com \
--cc=jfd@GigabitNetworks.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).