Date: Mon, 4 Jan 2016 19:18:02 +0100 From: Markus Edemalm <markus@edemalm.se> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Safe to delete old files in /usr/lib? Message-ID: <BA58A9C5-5BD4-44AD-AFDC-D3BE54036A78@edemalm.se> In-Reply-To: <20160104185245.5ca2e4f1.freebsd@edvax.de> References: <D6FAF4F3-EE48-4411-909D-9D13D8B9B620@edemalm.se> <20160104181211.76907a30.freebsd@edvax.de> <F4E4B196-36B4-40FE-A54B-FEA95DA96772@edemalm.se> <20160104185245.5ca2e4f1.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> 4 jan. 2016 kl. 18:52 skrev Polytropon <freebsd@edvax.de>:
>=20
> On Mon, 4 Jan 2016 18:28:14 +0100, Markus Edemalm wrote:
>>> 4 jan. 2016 kl. 18:12 skrev Polytropon <freebsd@edvax.de>:
>>>=20
>>> On Mon, 4 Jan 2016 18:06:00 +0100, Markus Edemalm wrote:
>>>> Hello,
>>>>=20
>>>> My system was first installed as 10.0-RELEASE. I have since =
upgraded to 10.1, 10.1-STABLE, 10.2-RELEASE and is now at =
10.2-RELEASE-p8.
>>>> I=E2=80=99ve rebuild from source and followed the steps in the =
handbook. Everything is fine=E2=80=A6 but:
>>>>=20
>>>> I see many files in /usr/lib with old dates, apparently they are no =
longer installed during upgrades.
>>>>=20
>>>> My /etc/make.conf looks like this:
>>>>=20
>>>> NO_PROFILE=3Dtrue
>>>> WITHOUT_X11=3Dyes
>>>>=20
>>>> Today, January the 4th, I upgraded to -p8. The newly installed =
files has todays date, i.e =E2=80=9DJan 4=E2=80=9D.
>>>> If I do:
>>>>=20
>>>> ls -lF /usr/lib | grep -v 'Jan 4' | awk {'print $9'}
>>>>=20
>>>> =E2=80=A6I get the following list of (obsolete?) files and folders =
with older dates.
>>>>=20
>>>> aout/
>>>> compat/
>>>> libBlocksRuntime.a
>>>> libalias.a
>>>> libalias_cuseeme.a
>>=20
>> [long list cut]
>>=20
>>>> liby.a
>>>> libypclnt.a
>>>> libz.a
>>>> libzfs.a
>>>> libzfs_core.a
>>>> libzpool.a
>>>>=20
>>>> Would it be safe to delete them?
>>>=20
>>> If you install from source, use the following targets:
>>>=20
>>> # check-old - List obsolete directories/files/libraries.
>>> # check-old-dirs - List obsolete directories.
>>> # check-old-files - List obsolete files.
>>> # check-old-libs - List obsolete libraries.
>>=20
>> Sorry, no files in /usr/lib comes up. Just a few others I know about.
>>=20
>>> And then:
>>>=20
>>> # delete-old - Delete obsolete directories/files/libraries.
>>> # delete-old-dirs - Delete obsolete directories.
>>> # delete-old-files - Delete obsolete files.
>>> # delete-old-libs - Delete obsolete libraries.
>>>=20
>>> See the comment header of /usr/src/Makefile for more information
>>> (and how those targets fit the recommended updating procedure,
>>> listed a few lines later).
>>>=20
>>> Generally speaking: As long as no program is linked against those
>>> files, and no program requires them, they can be deleted. This
>>> statement highly depends on which programs you have installed
>>> and what they are linked against. :-)
>>=20
>> Thank you. Still wonder why they are so many and where the came from =
in the first place.
>=20
> They have been installed by the OS (from the initial installation
> media or subsequent update processes), as the /usr/lib directory
> is reserved for OS files (like /usr/local/lib is for 3rd party
> libraries).
>=20
>=20
>=20
>> And, they are all .a files, except for libc++.so and libc.so.
>>=20
>> I added NO_PROFILE=3Dtrue to /etc/make.conf a while back. Is that =
relevant?
>=20
> Hmmm... I always thought that would be the default (no profiling libs
> being built and installed). But according to "man src.conf", the
> setting's name is WITHOUT_PROFILE, not NO_PROFILE.
Hmm. I forgot about src.conf, I got:
cat /etc/src.conf=20
WITHOUT_BLUETOOTH=3Dyes
WITHOUT_FLOPPY=3Dyes
WITHOUT_IPFW=3Dyes
WITHOUT_IPFILTER=3Dyes
That may explain why _some_ libs are not being built and installed.
But still, more than 100 .a files with old dates. Doesn=E2=80=99t make =
sense to me at all.
/ME
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA58A9C5-5BD4-44AD-AFDC-D3BE54036A78>