From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alberto =?iso-8859-1?Q?Cort=E9s?= To: 9fans@cse.psu.edu Subject: Re: [9fans] boot.c -> bad nvram key Message-ID: <20040307170709.GA634@shire> References: <20040307141250.GC879@shire> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Date: Sun, 7 Mar 2004 18:07:09 +0100 Topicbox-Message-UUID: 1ef9332a-eacd-11e9-9e20-41e7f4b1d025 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Some time ago, David said: > You're booting a cpu kernel that doesn't expect a user to be around > and does expect to find its key (and other stuff) either in nvram > or in a disk paritition called nvram. >=20 > Boot a terminal kernel (like 9pcdisk or 9pcf). term% 9fat: term% cat /n/9/plan9.ini bootfile=3DsdC0!fs!/386/9pcdisk =2E =2E =2E 9load finds this kernel and loads it to memory, or so it seems, something like: Found 9pcdisk... Plan 9 =2E.. from the booting secuence displayed information. Is there any way to know what kernel is loaded (cpu or terminal) from a runing system? maybe my kernels have wrong names. --=20 url: http://163.117.15.158/~acortes/index.html --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFAS1a93sDfaZ63xaURAu+gAKCjm2iJ2Oxzg4OUstPlcpFhSU5d0ACff5te 0Du/BVZCki7PVktO36Zus0U= =/rEs -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--