From owner-freebsd-fs Mon Jun 26 12:17:29 2000 Delivered-To: freebsd-fs@freebsd.org Received: from io.dreamscape.com (io.dreamscape.com [206.64.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 5453E37B51B; Mon, 26 Jun 2000 12:17:20 -0700 (PDT) (envelope-from krentel@dreamscape.com) Received: from dreamscape.com (sA10-p35.dreamscape.com [209.4.252.227]) by io.dreamscape.com (8.9.3/8.8.4) with ESMTP id PAA09229; Mon, 26 Jun 2000 15:16:01 -0400 (EDT) X-Dreamscape-Track-A: sA10-p35.dreamscape.com [209.4.252.227] X-Dreamscape-Track-B: Mon, 26 Jun 2000 15:16:01 -0400 (EDT) Received: (from krentel@localhost) by dreamscape.com (8.9.3/8.9.3) id PAA02609; Mon, 26 Jun 2000 15:16:51 -0400 (EDT) (envelope-from krentel) Date: Mon, 26 Jun 2000 15:16:51 -0400 (EDT) From: "Mark W. Krentel" Message-Id: <200006261916.PAA02609@dreamscape.com> To: freebsd-emulation@FreeBSD.ORG Subject: Re: panic running linux binaries from ext2fs Cc: clefevre@citeweb.net, freebsd-fs@FreeBSD.ORG Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I guess the problem is here. if the Linux binaries aren't branded, > and not run from /compat/linux, FreeBSD run them in the FreeBSD > kernel space, not the Linux kernel space. since the syscalls are > differents... Ok, I've copied the Linux /mnt/bin to /mnt/brand and branded them. And running the branded version (again from ext2fs) produces the same panic. It's not a branding issue. I asked about this on -emulation several months ago. Except for static binaries, branding has not been necessary for quite some time. For dynamically-linked binaries, the Freebsd loader can identify the binary type from how the binary asks to be loaded. You can even mis-brand binaries, and all you'll get is an Abort trap, certainly not a panic. No, I don't think it's a simple misconfiguration problem. I've run the Linux versions of emacs and netscape, and everything runs fine as long as all the files are on UFS. But moving the binaries to ext2fs produces a panic. --Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message