Date: Thu, 11 Apr 2002 17:04:48 -0700 From: Kris Kennaway <kris@obsecurity.org> To: sjh@ucf.ics.uci.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: sh dies w/ sig 12 Message-ID: <20020411170448.A10569@xor.obsecurity.org> In-Reply-To: <200204111836.g3BIan104358@whiskey.ucf.ics.uci.edu>; from sjh@whiskey.ucf.ics.uci.edu on Thu, Apr 11, 2002 at 11:36:49AM -0700 References: <200204111836.g3BIan104358@whiskey.ucf.ics.uci.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 11, 2002 at 11:36:49AM -0700, Seth Hettich wrote: > Trying to update to -current, in SU mode, doing the make installworld: >=20 > [ ! -e /usr/bin/passwd ] || echo foo >=20 > will make sh die >=20 > This is even with the "new" sh from my buildworld (I am running the new > kernel). You're probably trying to cut corners and aren't following the full (documented) upgrade procedure. Signal 12 is SIGSYS (unimplemented sycall), and you're receiving it because 5.0's /bin/sh depends on a syscall which only exists in recent 5.0 kernels. You shouldn't bump into this if you upgrade correctly. Kris --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8tiSgWry0BWjoQKURAqHxAJ9/5N2FWVYXXLxTZBD60NCKwD3oAACbB3gO xjZmO9+OUFwWImrsB2aqTJo= =DFSo -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020411170448.A10569>