Date: Fri, 30 Jan 2015 14:59:11 +0100 From: Andreas Nilsson <andrnils@gmail.com> To: =?UTF-8?B?TWFya28gQ3VwYcSH?= <marko.cupac@mimar.rs> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: freebsd-update and lib32 Message-ID: <CAPS9%2BSvFcfRnqwwWO1xs26baRqimeV%2BS-ZGyVmBtnRpwCO9feA@mail.gmail.com> In-Reply-To: <20150130145033.9c6459154a028e17b2f03f7f@mimar.rs> References: <20150130145033.9c6459154a028e17b2f03f7f@mimar.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 30, 2015 at 2:50 PM, Marko Cupa=C4=87 <marko.cupac@mimar.rs> wr= ote: > Hi, > > for years I've been leaving default 'lib32' option during initial > install of FreeBSD selected, but now I am experimenting with a server > which will be 64-bit only. > > 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. > > freebsd-update lists what it thinks you have installed, so if it lists lib32 it will be populated. The detection of what is installed is sometimes not good enough, so then one has to specify dists in /etc/freebsd-update.conf Are those files really necessary on 64-bit only system? > > Thank you in advance. > -- > Marko Cupa=C4=87 > https://www.mimar.rs Best regards Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSvFcfRnqwwWO1xs26baRqimeV%2BS-ZGyVmBtnRpwCO9feA>