All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@dot.at>
To: Matt Taggart <taggart@carmen.fc.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Many experience done on 720, but `init' fails !!
Date: Mon, 09 Apr 2001 23:12:47 +0200	[thread overview]
Message-ID: <3AD225CF.1AF048F1@dot.at> (raw)
In-Reply-To: 20010409205209.2FF0437CDB@carmen.fc.hp.com

Hello !

Matt Taggart wrote:
> 
> Christoph Plattner writes...
> 
> > SO I build sash, a also build a bash (shared and static !), I build
> > fileutils, text-utils, shell-utils, etc, etc.....
> > The system boots with bash and I can mount, run programs, etc....
> 
> Good.
> 
> > The I build "my own" startup stuff. A /sbin/init.d/xxx , etc/rc.d/xxx
> > and so on. I also build a sysvinit-2.78 (and 2.77 before), but the
> > `init' has it's problems. The error message is:
> 
> Make sure you don't have multiple init's. The kernel will look in several
> places and I don't remember what order it looks in. If you only have one then
> that's the only one it can find :)

I have only one init. But this is not a problem haveing more than one.
In the linux kernel it is very simply to have a "source look"
(init/main.c
bottom of the file). The kernel tries to exec /sbin/init. Only if the
exec fails
(cannot open, load, execute) then the next thing is tried. But if the
init has
a problem later on (faults, execptions, etc)the kernel does not try
other entries.

My problem is in another point. The `init' is also responsible to start
kernel
built-in processes (like kernel threads). They are AFAIK compiled in the
kernel,
the init process only starts and supervise (or only starts) them. With
the command
`ps' those processes are named with `[', `]', like the NFS daemon
`[nfsd]'.
Those procresses have very low pids (2,3,....). So I have to analyse the
code,
what pid=9 will become ? The break happens here !

> 
> Are you still having problems with the init in the base tarball? Is it
> important to you to build your own init? If it is reply privately and maybe I
> can help.

I read from this tarball in thr mailing list.
Is this a new root file system ?
How can I use it.
I have no debian experence, up to now I only had Redhat and formerly
Suse.
Do I need special knowledge ?

It is a hobby of mine, to build everything myself. I `dream' from a
source
directory, where I can say `make install' and a whole Linux is the
result,
of course for very small distribution of embeded Linux or firewall
stuff.
In my private sparetime, "small & embedded" Linux is my hobby and the HP
stuff and HP workstation is for me a perfect
cross-build-lerning-equipment.

  reply	other threads:[~2001-04-09 21:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 22:51 [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ? Christoph Plattner
2001-04-02 23:17 ` Richard Hirst
2001-04-02 23:27   ` Matthew Wilcox
2001-04-02 23:41     ` Richard Hirst
2001-04-03  6:55   ` Christoph Plattner
2001-04-03  9:12     ` Richard Hirst
2001-04-03  9:23       ` Christoph Plattner
2001-04-03 13:16         ` Richard Hirst
2001-04-03 21:34     ` Matthew Wilcox
2001-04-04  7:08       ` Christoph Plattner
2001-04-04 17:05         ` Matthew Wilcox
2001-04-04 20:31           ` Christoph Plattner
2001-04-08 17:08           ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
2001-04-08 17:32             ` [parisc-linux] C180 Progress Marc Eisenbarth
2001-04-09 13:36               ` Matt Taggart
2001-04-09 17:05                 ` Marc Eisenbarth
2001-04-08 21:02             ` [parisc-linux] Many experiments on 720, but `init' fails !! Christoph Plattner
2001-04-09 20:52             ` [parisc-linux] Many experience done " Matt Taggart
2001-04-09 21:12               ` Christoph Plattner [this message]
2001-04-10  8:46                 ` Richard Hirst

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=3AD225CF.1AF048F1@dot.at \
    --to=christoph.plattner@dot.at \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=taggart@carmen.fc.hp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.