From owner-freebsd-stable@FreeBSD.ORG  Fri Jan 30 14:09:28 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 060205A1
 for <freebsd-stable@freebsd.org>; Fri, 30 Jan 2015 14:09:28 +0000 (UTC)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com
 [IPv6:2a00:1450:400c:c00::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8A69DDDB
 for <freebsd-stable@freebsd.org>; Fri, 30 Jan 2015 14:09:27 +0000 (UTC)
Received: by mail-wg0-f52.google.com with SMTP id y19so27053865wgg.11
 for <freebsd-stable@freebsd.org>; Fri, 30 Jan 2015 06:09:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=048mfW1eRKRzeAnSpvpZ3sX+tg7GqgYNBl9pKr+m3FU=;
 b=RNFccRIJ/PdXMv+GIqRDaKwnv6mzhrGJ4THIkToiWLkqBjh48dBJtcB74Xpr44LO5C
 w05xi3YUZGcPwQcPsvYsFxIwIZq/J1jMv3UpK/Zz3k/1d6R8rthMFjKHB6b7lELl2kfV
 ocs4jn3HFssFQibyXKseRYxg2rqg/QrPqh8XWlTQoQc9POTHBDYI5j+C9hLs36x00gWR
 8jHzLRBsGMrgaRZ7j7pqvyvxslRI//J+qY+zjYibJlB8QRZuTuZNaNXNSiD5CGARIWLZ
 Kl3Fp7znP1gQT3rrorwK6mthIHyxYyie5GARhVfSMhDwtnpxMjGU9fKyRdx+0M3jnmke
 BtPQ==
MIME-Version: 1.0
X-Received: by 10.194.110.233 with SMTP id id9mr12652783wjb.136.1422626965965; 
 Fri, 30 Jan 2015 06:09:25 -0800 (PST)
Received: by 10.217.150.72 with HTTP; Fri, 30 Jan 2015 06:09:25 -0800 (PST)
In-Reply-To: <20150130145033.9c6459154a028e17b2f03f7f@mimar.rs>
References: <20150130145033.9c6459154a028e17b2f03f7f@mimar.rs>
Date: Fri, 30 Jan 2015 09:09:25 -0500
Message-ID: <CAKFCL4XHSyfsUJnKBORSgt+BObENurObsDJ-JCjUodJXjEGzkQ@mail.gmail.com>
Subject: Re: freebsd-update and lib32
From: Brandon Allbery <allbery.b@gmail.com>
To: =?UTF-8?B?TWFya28gQ3VwYcSH?= <marko.cupac@mimar.rs>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd-stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 14:09:28 -0000

On Fri, Jan 30, 2015 at 8:50 AM, Marko Cupa=C4=87 <marko.cupac@mimar.rs> wr=
ote:

> I have noticed that, after initial install of FreeBSD 10.1-RELEASE
> without lib32 selected, /usr/lib32 folder is created nevertheless,
> containing 3 empty dirs: dtrace, i18n and private. However, running
> freebsd-update on such system pulls a bunch of files into /usr/lib32
> and its subdirs while updating to FreeBSD 10.1-RELEASE-p5.
>
> Are those files really necessary on 64-bit only system?
>

There was a glitch in production of 10.1-R that left lib32 mostly empty by
default, and -p1 attempted to fix it. I suspect both the original bug and
the fix ignored the lib32 setting.

--=20
brandon s allbery kf8nh                               sine nomine associate=
s
allbery.b@gmail.com                                  ballbery@sinenomine.ne=
t
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.ne=
t