From owner-freebsd-current Mon Apr 17 22: 3:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E85B237B691 for ; Mon, 17 Apr 2000 22:03:28 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id WAA01879; Mon, 17 Apr 2000 22:03:25 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200004180503.WAA01879@troutmask.apl.washington.edu> Subject: Re: ** HEADS UP ** ELF Branding changes require action on your part. In-Reply-To: <20000417213121.A5099@dragon.nuxi.com> from "David O'Brien" at "Apr 17, 2000 09:31:21 pm" To: obrien@NUXI.ucdavis.edu Date: Mon, 17 Apr 2000 22:03:25 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > ----- Forwarded message from "David E. O'Brien" ----- > Log: > Change our ELF binary branding to something more acceptable to the Binutils > maintainers. > ... > Note that a new kernel can still properly load old binaries except for > Linux static binaries branded in our old method. > ----- End forwarded message ----- > > One statically linked Linux binary that will cause you trouble after you > build world is the Linux ``ldconfig''. After your ``make world'' and > before you reboot that new kernel, issue: > > brandelf -t Linux /compat/linux/sbin/ldconfig > Does this mean that we can re-brand any statically linux binary if it fails? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message