Re: filemon: weird full-time build although filemon enabled

Hi, > I build CURRENT on two technically similar systems on a almost daily basis. > Therefore, it > was a great relief having WITH_META_MODE=yes set in /etc/src-env.conf for > incremental > builds. To make my understanding of this clear (just in case I'm wrong): > setting > WITH_META_MODE

more default uid/gid for NFS in mountd

Hi, Five years ago (yea, it slipped through a crack;-), Slawa reported that files created by root would end up owned by uid 2**32-2 (-2 as uint32_t). This happens if there is no "-maproot=" in the /etc/exports line. The cause is obvious. The value is set to -2 by default. The question is...

Re: filemon: weird full-time build although filemon enabled

> On May 6, 2017, at 00:22, O. Hartmann wrote: > > I build CURRENT on two technically similar systems on a almost daily basis. > Therefore, it > was a great relief having WITH_META_MODE=yes set in /etc/src-env.conf for > incremental > builds. To make my understanding

Re: filemon: weird full-time build although filemon enabled

Am Mon, 8 May 2017 11:23:01 -0700 "Ngie Cooper (yaneurabeya)" schrieb: > > On May 6, 2017, at 00:22, O. Hartmann wrote: > > > > I build CURRENT on two technically similar systems on a almost daily basis. > > Therefore, it was a great relief having

Re: ${src}/release/release.sh fails at makefs state

> On May 8, 2017, at 06:07, Alastair Hogge wrote: > > On Fri, 5 May 2017 11:26:44 PM Ngie Cooper wrote: >> (CCing emaste) >> >>> On May 5, 2017, at 21:55, Alastair Hogge wrote: >> … >> >>> Calculated size of `memstick.img.part': 485474304 bytes, 9435

Re: bootcode capable of booting both UFS and ZFS?

On Friday, May 05, 2017 11:01:03 PM Toomas Soome wrote: > > > On 5. mai 2017, at 22:07, Julian Elischer wrote: > > > > Subject says it all really, is this an option at this time? > > > > we'd like to try boot the main zfs root partition and then fall back to a > > small

Re: filemon: weird full-time build although filemon enabled

Am Mon, 8 May 2017 10:17:05 -0700 "Simon J. Gerraty" schrieb: > Konstantin Belousov wrote: > > If I understand the motto of meta-mode, any file change is detected for any > > file accessed during the build. All dynamically-linked binary includes > > the

Re: filemon: weird full-time build although filemon enabled

On Mon, May 08, 2017 at 09:04:08AM -0700, Simon J. Gerraty wrote: > O. Hartmann wrote: > > It is weird! > > > > Today, after yesterday's built, I face the same 90 minutes build horror > > again, this time > > I switched on "-dM" with the make command. > > > > This

Re: filemon: weird full-time build although filemon enabled

Am Mon, 8 May 2017 19:32:58 +0200 "O. Hartmann" schrieb: > Am Mon, 8 May 2017 10:17:05 -0700 > "Simon J. Gerraty" schrieb: > > > Konstantin Belousov wrote: > > > If I understand the motto of meta-mode, any file change is

Re: filemon: weird full-time build although filemon enabled

Am Sun, 7 May 2017 23:24:55 -0700 "Simon J. Gerraty" schrieb: > Hi, > > > I build CURRENT on two technically similar systems on a almost daily basis. > > Therefore, it was a great relief having WITH_META_MODE=yes set in > > /etc/src-env.conf > > for incremental builds. To

Re: filemon: weird full-time build although filemon enabled

O. Hartmann wrote: > It is weird! > > Today, after yesterday's built, I face the same 90 minutes build horror > again, this time > I switched on "-dM" with the make command. > > This happens: > > [...] >

Re: filemon: weird full-time build although filemon enabled

Konstantin Belousov wrote: > If I understand the motto of meta-mode, any file change is detected for any > file accessed during the build. All dynamically-linked binary includes > the rtld into the process image, and rtld reads all config files in the > libmap.d

Re: ${src}/release/release.sh fails at makefs state

On Fri, 5 May 2017 11:26:44 PM Ngie Cooper wrote: > (CCing emaste) > > > On May 5, 2017, at 21:55, Alastair Hogge wrote: > … > > > Calculated size of `memstick.img.part': 485474304 bytes, 9435 inodes > > Extent size set to 8192 > > memstick.img.part: 463.0MB (948192 sectors)

Re: more default uid/gid for NFS in mountd

On Mon, May 08, 2017 at 11:45:46AM +, Rick Macklem wrote: > Hi, > > Five years ago (yea, it slipped through a crack;-), Slawa reported that files > created by root would end up owned by uid 2**32-2 (-2 as uint32_t). > This happens if there is no "-maproot=" in the /etc/exports line. > > The

Re: more default uid/gid for NFS in mountd

On 05/08/2017 06:45, Rick Macklem wrote: > Hi, > > Five years ago (yea, it slipped through a crack;-), Slawa reported that files > created by root would end up owned by uid 2**32-2 (-2 as uint32_t). > This happens if there is no "-maproot=" in the /etc/exports line. > > The cause is obvious. The

Re: bootcode capable of booting both UFS and ZFS?

On Mon, May 8, 2017 at 12:10 PM, John Baldwin wrote: > On Friday, May 05, 2017 11:01:03 PM Toomas Soome wrote: >> >> > On 5. mai 2017, at 22:07, Julian Elischer wrote: >> > >> > Subject says it all really, is this an option at this time? >> > >> > we'd like

Re: filemon: weird full-time build although filemon enabled

O. Hartmann wrote: > > .MAKE.META.IGNORE_PATHS += /usr/local/etc/libmap.d > > > > --sjg > > I suppose I have to set this flag in > > /etc/src-env.conf That should work. Let us know how it goes ___ freebsd-current@freebsd.org

Re: ${src}/release/release.sh fails at makefs state

On Mon, 8 May 2017 11:47:23 AM Ngie Cooper wrote: [...] > Hi Alastair, > r317967 should allow you to build release images again. Thank you very muchly, Alastair ___ freebsd-current@freebsd.org mailing list