On Mon, 20 Mar 2017 22:32:53 -0700 (PDT) Don Lewis wrote
> On 20 Mar, Chris H wrote:
> > I'm not sure which of the two lists I'm directing
> > this to is the best/correct one. So I picked both.
> >
> > To the point; I received this message during a big
> > build session. I was only able to catch
On Tue, 21 Mar 2017 06:16:03 +0100 "O. Hartmann"
wrote
> On Mon, 20 Mar 2017 19:08:41 -0700
> "Chris H" wrote:
>
> > I've seen this discussed before, but there were so many
> > "solutions", I was left feeling this *must* be some sort
> > of bug in GEOM/gpart. So. I just blew away the tables on
On 20 Mar, Chris H wrote:
> I'm not sure which of the two lists I'm directing
> this to is the best/correct one. So I picked both.
>
> To the point; I received this message during a big
> build session. I was only able to catch the one from
> x11/nvidia-driver in such a way as to actually get
> th
On 2017. 03. 21. 3:40, Rick Macklem wrote:
Gergely Czuczy wrote:
[stuff snipped]
Actually I want to test it, but you guys are so vehemently discussing
it, I thought it would be better to do so, once you guys settled your
analysis on the code. Also, me not having the problem occurring, I don't
th
On Tue, 21 Mar 2017 13:14:56 +0800 Kevin Lo wrote
> On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote:
> >
> > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote
> >
> > > I'm not sure which of the two lists I'm directing
> > > this to is the best/correct one. So I picked both.
> > >
>
On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote:
>
> On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote
>
> > I'm not sure which of the two lists I'm directing
> > this to is the best/correct one. So I picked both.
> >
> > To the point; I received this message during a big
> > build ses
On Mon, 20 Mar 2017 21:11:44 -0700
"Chris H" wrote:
> On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote
>
> > I'm not sure which of the two lists I'm directing
> > this to is the best/correct one. So I picked both.
> >
> > To the point; I received this message during a big
> > build session.
On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote
> I'm not sure which of the two lists I'm directing
> this to is the best/correct one. So I picked both.
>
> To the point; I received this message during a big
> build session. I was only able to catch the one from
> x11/nvidia-driver in such a
I'm not sure which of the two lists I'm directing
this to is the best/correct one. So I picked both.
To the point; I received this message during a big
build session. I was only able to catch the one from
x11/nvidia-driver in such a way as to actually get
the entire message:
Installing nvidia-dri
WITHOUT_CLANG fixed it for me. Thanks.
-adrian
On 20 March 2017 at 11:23, Ed Maste wrote:
> On 19 March 2017 at 03:00, Adrian Chadd wrote:
>> gcc version 5.3.0 (FreeBSD Ports Collection for mips)
>>
>> ... so uhm, why are we building libllvm?
>
> As of the Clang 4.0.0 import we build Clang
Gergely Czuczy wrote:
[stuff snipped]
> Actually I want to test it, but you guys are so vehemently discussing
> it, I thought it would be better to do so, once you guys settled your
> analysis on the code. Also, me not having the problem occurring, I don't
> think would mean it's solved, since that
Konstantin Belousov wrote:
[stuff snipped]
> Yes, I have to somewhat retract my claims, but then I have another set
> of surprises.
Righto.
> I realized (remembered) that nfs has its own VOP_PUTPAGES() method.
> Implementation seems to directly initiate write RPC request using the
> pages as the s
I've seen this discussed before, but there were so many
"solutions", I was left feeling this *must* be some sort
of bug in GEOM/gpart. So. I just blew away the tables on
a USB3 flash drive:
# gpart destroy -F da0
# gpart create -s gpt da0
# gpart add -t freebsd-ufs -l jails da0
# newfs -U /dev/
On Tue, 21 Mar 2017 00:09:06 +0200 Toomas Soome wrote
> > On 20. märts 2017, at 23:58, Chris H wrote:
> >
> > I'm attempting to get a video card that DTRT on FreeBSD.
> > I started with the graphics provided by an AMD A6-7470K,
> > only to discover it's not yet supported. So I forked out
> > fo
On Mon, 20 Mar 2017 22:02:06 + Steven Hartland
wrote
> Add the following to /boot/loader.conf
>
> Its a tunable but not a sysctl so you can't query it, you just need to
> set it by adding it to /boot/loader.conf:
> hw.vga.textmode="1"
>
WOW. Thanks for the fast reply!
I gave your suggesti
On Sun, Mar 19, 2017 at 08:52:50PM +, Rick Macklem wrote:
> Kostik wrote:
> [stuff snipped]
> >> >> Dirty pages are flushed by writes, so if we have a set of dirty pages
> >> >> and
> >> >> async vm_object_page_clean() is called on the vnode' vm_object, we get
> >> >> a bunch of delayed-write
> On 20. märts 2017, at 23:58, Chris H wrote:
>
> I'm attempting to get a video card that DTRT on FreeBSD.
> I started with the graphics provided by an AMD A6-7470K,
> only to discover it's not yet supported. So I forked out
> for a recent nvidia card, and build/installed a new
> world/kernel.
>
Add the following to /boot/loader.conf
Its a tunable but not a sysctl so you can't query it, you just need to
set it by adding it to /boot/loader.conf:
hw.vga.textmode="1"
On 20/03/2017 21:58, Chris H wrote:
I'm attempting to get a video card that DTRT on FreeBSD.
I started with the graphics
I'm attempting to get a video card that DTRT on FreeBSD.
I started with the graphics provided by an AMD A6-7470K,
only to discover it's not yet supported. So I forked out
for a recent nvidia card, and build/installed a new
world/kernel.
Everything seemed to be as one would expect, except there
was
> On 20. märts 2017, at 23:53, Rick Macklem wrote:
>
> Baptiste Daroussin wrote:
>> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote:
>>> Hi!
>>>
>>> The current boot code is building NFSv3, with preprocessor conditional
>>> OLD_NFSV2. Should NFSv2 code still be kept around or can
Baptiste Daroussin wrote:
> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote:
> > Hi!
> >
> > The current boot code is building NFSv3, with preprocessor conditional
> > OLD_NFSV2. Should NFSv2 code still be kept around or can we burn it?
> >
> > rgds,
> > toomas
>
> I vote burn
>
> Bap
On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote:
> Hi!
>
> The current boot code is building NFSv3, with preprocessor conditional
> OLD_NFSV2. Should NFSv2 code still be kept around or can we burn it?
>
> rgds,
> toomas
I vote burn
Bapt
signature.asc
Description: PGP signature
On 19 March 2017 at 03:00, Adrian Chadd wrote:
> gcc version 5.3.0 (FreeBSD Ports Collection for mips)
>
> ... so uhm, why are we building libllvm?
As of the Clang 4.0.0 import we build Clang by default, on all
architectures other than those unsupported by Clang, if the
cross-compiler supports C+
Hi!
The current boot code is building NFSv3, with preprocessor conditional
OLD_NFSV2. Should NFSv2 code still be kept around or can we burn it?
rgds,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
On 03/20/17 14:14, Matthias Apitz wrote:
Hello,
I have a very recent 12-CURRENT on amd64 (r314251) with all ports from beginning
of March.
While testing multimedia/webcamd in debug mode it says:
# /usr/local/sbin/webcamd -i 0 -d ugen0.2 -U webcamd -G webcamd -H
: USB HID core driver
Linux vid
Hello,
I have a very recent 12-CURRENT on amd64 (r314251) with all ports from beginning
of March.
While testing multimedia/webcamd in debug mode it says:
# /usr/local/sbin/webcamd -i 0 -d ugen0.2 -U webcamd -G webcamd -H
: USB HID core driver
Linux video capture interface: v2.00
IR NEC protocol
26 matches
Mail list logo
