From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eduardo Pereira Habkost <ehabkost@conectiva.com.br>
Subject: Re: Init panics
Date: Wed, 21 Jul 2004 12:28:49 -0300
Sender: linux-8086-owner@vger.kernel.org
Message-ID: <20040721152848.GB12766@duckman.distro.conectiva>
References: <20040720233400.45011.qmail@web51308.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="DBIVS5p969aUjpLe"
Return-path: <linux-8086-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20040720233400.45011.qmail@web51308.mail.yahoo.com>
List-Id: <linux-8086.vger.kernel.org>
To: linux-8086@vger.kernel.org


--DBIVS5p969aUjpLe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 20, 2004 at 04:34:00PM -0700, Tommy McCabe wrote:
> In line 332 of elkscmd/sys_utils/init.c, there is a
> PANIC that shouldn't be there- it's activated
> regardless of the preceding if statement. But when I
> take it out, init doesn't print out anything. I have
> literally filled every other line of main() with fputs
> and PANICS and init doesn't print out anything.

Have you ever used execv() on unix? If you see some examples of use
of execv(), you will see why the panic is there. Simply because init
should really show a error message (I would print a error string, instead
of just calling PANIC0, however), if it can't run getty, if the execv()
call is successful, the PANIC0 line will not be executed, because the
process is replaced by getty. Is getty included on your disk?

--=20
Eduardo

--DBIVS5p969aUjpLe
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA/ouwcaRJ66w1lWgRArgjAJ46DOIt8/TDl66Vpzv/bDOK/ODWOgCfcCVy
SccuSmJ9+thYDNky2f417K4=
=MlvZ
-----END PGP SIGNATURE-----

--DBIVS5p969aUjpLe--