I would like to propose the following change.
My understanding is that it was never a true intention to post 'mountroot' event
on every set_rootvnode() call, but rather an accident in the original commit.
But I could be wrong here. In either case I think that it is more appropriate
to post the
Due to the security incident, there are still no official FreeBSD
packages.
Do you know what the status is on that issue?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
Yesterday, I built head ran it without incident (as has been the
daily norm for some time now):
FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #843
r248493M/248493: Tue Mar 19 05:57:09 PDT 2013
r...@g1-235.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
Today, after
On 20/03/2013 15:20, Matthias Gamsjager wrote:
Due to the security incident, there are still no official FreeBSD
packages.
Do you know what the status is on that issue?
Unchanged so far. No official pkgng packages yet.
However, an end to the wait is apparently in sight. There has been
I've been having random panics since the VM changes. I'm stuck
running r247527. If I try to install a newer kernel/world, I get random
panics (I really should enable crashdumps). Not a big deal, but I'm mostly
interested in epair fixes and bhyve enhancements.
On Wed, Mar 20, 2013 at 12:00 PM,
On Wed, Mar 20, 2013 at 04:20:02PM +0100, Matthias Gamsjager wrote:
Due to the security incident, there are still no official FreeBSD
packages.
Do you know what the status is on that issue?
I'd also like to find out what the status of this is.
The packages at:
On Wed, Mar 20, 2013 at 09:00:56AM -0700, David Wolfskill wrote:
Yesterday, I built head ran it without incident (as has been the
daily norm for some time now):
FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #843
r248493M/248493: Tue Mar 19 05:57:09 PDT 2013
On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote:
...
I'm open to suggestions, and willing to hack and test (and report,
of course).
Did you rebuild the nvidia driver after the update ?
Yes; src.conf includes the line:
PORTS_MODULES=x11/nvidia-driver
Do you have a
hello,
would anyone object to the following small patch?
==
Index: vm_pageout.c
===
--- vm_pageout.c(revision 248560)
+++ vm_pageout.c(working copy)
@@ -882,14 +882,17 @@
vm_pageout_init_marker(marker,
on 20/03/2013 19:18 David Wolfskill said the following:
Yes; src.conf includes the line:
PORTS_MODULES=x11/nvidia-driver
Have you double-checked that this actually works according to your intention?
--
Andriy Gapon
___
freebsd-current@freebsd.org
On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote:
...
Did you rebuild the nvidia driver after the update ?
Do you have a core dump partition configured ?
(I note that I have, in the past, captured crash dumps from head running
on this machine with this configuration.)
Try
On Wed, Mar 20, 2013 at 10:37:59AM -0700, David Wolfskill wrote:
On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote:
...
Did you rebuild the nvidia driver after the update ?
Do you have a core dump partition configured ?
(I note that I have, in the past, captured crash
On Wed, Mar 20, 2013 at 07:24:30PM +0200, Andriy Gapon wrote:
on 20/03/2013 19:18 David Wolfskill said the following:
Yes; src.conf includes the line:
PORTS_MODULES=x11/nvidia-driver
Have you double-checked that this actually works according to your intention?
...
Until I started
On 03/19/2013 18:26, Marcus Reid wrote:
On Mon, Mar 04, 2013 at 04:53:10AM +0100, deeptech71 wrote:
I use atimes all the time to get to the bottom of lots of common
problems.
Details !
It sounds like in your case, atime is a debugging feature (which are generally
to be turned off on
On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote:
...
I then started xdm, and (as before), got an unclean reboot. (So: no
difference in behavior as far as I can tell.)
Ok. The best idea I have right now is to rebuild the nvidia.ko.
Again? OK
Do you have a
On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote:
...
Ok. The best idea I have right now is to rebuild the nvidia.ko.
OK; I did this: After rebooting (without attempting to either load
nvidia.ko or start X in any way), I issued:
sudo portmaster x11/nvidia-driver
On Wednesday, March 20, 2013 4:30:27 am Andriy Gapon wrote:
I would like to propose the following change.
My understanding is that it was never a true intention to post 'mountroot'
event
on every set_rootvnode() call, but rather an accident in the original commit.
But I could be wrong
/usr/local/bin/g++48 -o test test.o base64.o registry.o server_abyss.o
server_pstream.o tools.o value.o xml.o testclient.o
/usr/ports/net/xmlrpc-c-devel/work/xmlrpc-c-1.32.99/src/cpp/libxmlrpc_server_abyss++.a
On Mar 20, 2013, at 19:54, deeptech71 deeptec...@gmail.com wrote:
/usr/local/lib/gcc48/include/c++/bits/locale_facets.h:869: undefined
reference to `std::ctypechar::_M_widen_init() const'
[...]
/usr/local/lib/gcc48/include/c++/bits/stl_list.h:1550: undefined reference to
On Wed, Mar 20, 2013 at 11:02:39AM -0700, David Wolfskill wrote:
On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote:
...
Ok. The best idea I have right now is to rebuild the nvidia.ko.
OK; I did this: After rebooting (without attempting to either load
nvidia.ko or start X
On Wed, Mar 20, 2013 at 10:08:57PM +0200, Konstantin Belousov wrote:
...
I looked at the nvidia sources to check that the driver does not use
the interfaces which KBI was changed, and this is indeed the case, as
expected.
OK; thank you for checking reporting.
I must admit that I have no
I would advise that you try the following:
(1) On a machine which is not your laptop, build a CURRENT chroot
(2) Follow the instructions at:
http://www.freebsd.org/doc/handbook/network-pxe-nfs.html
to NFS export the chroot and set up a TFTP server.
(3) Set up your laptop to PXE boot
Dear All,
At present I do not have access to a HP box with a SmartArray
but zfsboot works perfectly with FreeBSD 9.1-RELEASE #0 r245668
(including EDD fix) on:
/hpiLO- show system1
[...]
Properties
name=ProLiant DL160 Gen8
[...]
with the following firmware
/hpiLO- show
On Wed, Mar 20, 2013 at 10:08:57PM +0200, Konstantin Belousov wrote:
...
I looked at the nvidia sources to check that the driver does not use
the interfaces which KBI was changed, and this is indeed the case, as
expected.
I must admit that I have no idea why buffer cache changes could
24 matches
Mail list logo
