> On Jan 4, 2019, at 19:00, Yoshihiro Ota wrote:
>
> I've seen such failures with NFS without lockd.
>
> Svn fails as it cannot lock its files, too.
Yeah. lockd must be running in order for this to work. This hasn’t changed
in the last few years.
Cheers,
-Enji
I've seen such failures with NFS without lockd.
Svn fails as it cannot lock its files, too.
Hiro
On Fri, 4 Jan 2019 10:41:56 -0500
Ed Maste wrote:
> On Fri, 4 Jan 2019 at 10:36, Matthias Apitz wrote:
> >
> > To save space on the netbook
> > I excluded /usr/src/.svn which is causing now the ab
On Fri, Jan 04, 2019 at 11:14:55AM -0800, Manfred Antar wrote:
> sbin/savecore broken when WITHOUT_DYNAMICROOT is defined:
Fixed in r342776, thanks.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
T
sbin/savecore broken when WITHOUT_DYNAMICROOT is defined:
/usr/local/bin/ccache cc -O2 -pipe -DWITH_CASPER -MD -MF.depend.savecore.o
-MTsavecore.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Wall
-Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wp
On 1/3/19 10:40 PM, Kevin Oberman wrote:
> On Wed, Jan 2, 2019 at 5:02 PM Robert Huff wrote:
>
>>
>> John Baldwin writes:
>>
>>> -[8] In order to have a kernel that can run the 4.x binaries needed
>> to
>>> -do an installworld, you must include the COMPAT_FREEBSD4 option in
>>> -yo
On Fri, 4 Jan 2019 at 10:36, Matthias Apitz wrote:
>
> To save space on the netbook
> I excluded /usr/src/.svn which is causing now the absence of the
> revision number.
Yes, newvers.sh relies on the metadata in .svn to determine the
revision number so this is as expected.
___
El día viernes, enero 04, 2019 a las 09:30:05a. m. -0500, Ed Maste escribió:
> It looks like some aspects of this have been broken since r308789. Do
> you happen to have a git or hg tree higher up in the directory
> hierarchy? For example, ~/.git, and ~/src/freebsd/...? I'll have a fix
> for that
On Fri, 4 Jan 2019 at 08:42, Julian H. Stacey wrote:
>
> Matthias Apitz wrote:
> > $ sh /usr/src/sys/conf/newvers.sh
>
> Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
Please read the UPDATING entry and the src.conf description for
WITHOUT_REPRODUCIBLE_BUILD. You probably
On Fri, 4 Jan 2019 at 00:53, Matthias Apitz wrote:
>
> Why is this? I've read in UPDATING that:
>
> ...
> 20180913:
> Reproducible build mode is now on by default, in preparation for
> FreeBSD 12.0. This eliminates build metadata such as the user,
> ...
>
> But this does not expla
On Fri, 4 Jan 2019 15:24:42 +0100
Gary Jennejohn wrote:
> On Fri, 04 Jan 2019 14:41:43 +0100
> "Julian H. Stacey" wrote:
>
> > Matthias Apitz wrote:
> > > $ sh /usr/src/sys/conf/newvers.sh
> >
> > Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
> >
> > /usr/src/.
On Fri, 04 Jan 2019 14:41:43 +0100
"Julian H. Stacey" wrote:
> Matthias Apitz wrote:
> > $ sh /usr/src/sys/conf/newvers.sh
>
> Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
>
> /usr/src/.svn_revision 342578 probably what I used to install / from,
> but how to tell no
Matthias Apitz wrote:
> $ sh /usr/src/sys/conf/newvers.sh
Me too. Mine also returns nothing. Ditto uname. Ditto dmesg. Annoying.
/usr/src/.svn_revision 342578 probably what I used to install / from,
but how to tell now its been excised ?
Good you reported it. (I'd assumed it was local breakage
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable12? |mfc-stable12+
Keywords|n
On 2019-Jan-3, at 22:56, Michal Meloun wrote:
> On 29.12.2018 18:47, Dennis Clarke wrote:
>> On 12/28/18 9:56 PM, Mark Millard via freebsd-arm wrote:
>>>
>>> On 2018-Dec-28, at 12:12, Mark Millard wrote:
>>>
On 2018-Dec-28, at 05:13, Michal Meloun
wrote:
> Mark,
> t
14 matches
Mail list logo
