Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Chris H
On Fri, 15 Dec 2017 10:12:09 +0100 "Wolfram Schneider" said Hi, I upgraded a machine from 11-stable to 12-current. The /usr/obj tree is now 11GB huge: FreeBSD 12-current $ du -hs /usr/obj 11G /usr/obj on FreeBSD 11-stable it was less the size: $ du -hs /usr/obj 5.6G

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Masachika ISHIZUKA
>> I upgraded a machine from 11-stable to 12-current. The /usr/obj tree >> is now 11GB huge: >> [snip] > > There was a change near the beginning of November; please see UPDATING > entry 20171101 -- you probably have several no-longer-used > subdirectories under /usr/obj/usr/src/. > > Once

Re: GPTZFSBOOT in Current r326622 has problems

2017-12-15 Thread Warner Losh
On Wed, Dec 6, 2017 at 8:54 AM, Warner Losh wrote: > > > On Wed, Dec 6, 2017 at 8:35 AM, Thomas Laus wrote: > >> Group: >> >> I updated my amd64 computer today to r326622 and copied the >> /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The >>

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Larry Rosenman
On 12/15/17, 1:28 PM, "owner-freebsd-curr...@freebsd.org" wrote: Wolfram Schneider writes: > I upgraded a machine from 11-stable to 12-current. The /usr/obj tree > is now 11GB huge: > > FreeBSD 12-current > $ du -hs

/usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread owner-freebsd-current
Wolfram Schneider writes: > I upgraded a machine from 11-stable to 12-current. The /usr/obj tree > is now 11GB huge: > > FreeBSD 12-current > $ du -hs /usr/obj > 11G /usr/obj > > on FreeBSD 11-stable it was less the size: > $ du -hs /usr/obj > 5.6G /usr/obj Mine - also

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Wolfram Schneider
On 15 December 2017 at 19:39, Konstantin Belousov wrote: > On Fri, Dec 15, 2017 at 06:38:48PM +0100, Wolfram Schneider wrote: >> On 15 December 2017 at 17:51, Wolfram Schneider wrote: >> > On 15 December 2017 at 13:02, David Wolfskill

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Konstantin Belousov
On Fri, Dec 15, 2017 at 06:38:48PM +0100, Wolfram Schneider wrote: > On 15 December 2017 at 17:51, Wolfram Schneider wrote: > > On 15 December 2017 at 13:02, David Wolfskill wrote: > >> On Fri, Dec 15, 2017 at 10:12:09AM +0100, Wolfram Schneider wrote: >

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Wolfram Schneider
On 15 December 2017 at 17:51, Wolfram Schneider wrote: > On 15 December 2017 at 13:02, David Wolfskill wrote: >> On Fri, Dec 15, 2017 at 10:12:09AM +0100, Wolfram Schneider wrote: >>> Hi, >>> >>> I upgraded a machine from 11-stable to 12-current. The

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Wolfram Schneider
On 15 December 2017 at 13:02, David Wolfskill wrote: > On Fri, Dec 15, 2017 at 10:12:09AM +0100, Wolfram Schneider wrote: >> Hi, >> >> I upgraded a machine from 11-stable to 12-current. The /usr/obj tree >> is now 11GB huge: >> >> FreeBSD 12-current >> $ du -hs /usr/obj >>

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread David Wolfskill
On Fri, Dec 15, 2017 at 10:12:09AM +0100, Wolfram Schneider wrote: > Hi, > > I upgraded a machine from 11-stable to 12-current. The /usr/obj tree > is now 11GB huge: > > FreeBSD 12-current > $ du -hs /usr/obj > 11G /usr/obj > > on FreeBSD 11-stable it was less the size: > $ du -hs /usr/obj >

Re: kernel names

2017-12-15 Thread Shane Ambler
On 14/12/2017 16:21, Allan Jude wrote: > On 12/14/2017 00:47, blubee blubeeme wrote: >> When you boot into FreeBSD and you can select kernels, there's only 2 >> options: >> default and kernel.old >> >> Is there a way to have better output and support multiple kernels without >> having to login to

/usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Wolfram Schneider
Hi, I upgraded a machine from 11-stable to 12-current. The /usr/obj tree is now 11GB huge: FreeBSD 12-current $ du -hs /usr/obj 11G /usr/obj on FreeBSD 11-stable it was less the size: $ du -hs /usr/obj 5.6G /usr/obj this is a problem when you have a small VM with 20GB disk space or less. Is