Hello, Edward.
You wrote 4 сентября 2014 г., 16:43:30:
ETN It's a bug. Or rather, a missing feature. The problem here is that
ETN the / export shadows the rest. To handle this correctly, automountd(8)
ETN would need to mount the / share, then mount autofs on /usr etc, and
ETN then call it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07.09.2014 18:56, Xin Li wrote:
On 9/7/14 11:23 PM, Fabian Keil wrote:
Xin Li delp...@delphij.net wrote:
On 9/7/14 9:02 PM, Fabian Keil wrote:
Using a kernel built from FreeBSD 11.0-CURRENT r271182 I got
the following panic yesterday:
Hans Petter Selasky wrote:
On 09/06/14 00:09, Rick Macklem wrote:
Hans Petter Selesky wrote:
On 09/05/14 23:19, Eric Joyner wrote:
There are some concerns if we use this with devices that ixl
supports:
- The maximum fragment size is 16KB-1, which isn't a power of 2.
Hi Eric,
On 05.09.14 19:37, John Nielsen wrote:
On Sep 5, 2014, at 11:30 AM, Glen Barber g...@freebsd.org wrote:
On Fri, Sep 05, 2014 at 11:20:21AM -0600, John Nielsen wrote:
I have a MacBook Pro Retina, Mid 2012 (MacBookPro10,1) on which I'd like to
be able to boot FreeBSD from an external USB
On Sun, Sep 07, 2014 at 04:03:59PM -0700, Craig Rodrigues wrote:
Hi,
I am using pkg 1.3.7.
I did the following as a regular user, not root:
rm -fr /tmp/package
cd /usr/src
make buildworld
make buildkernel
make -DNO_ROOT -DDB_FROM_SRC installworld DESTDIR=/tmp/package
make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2014 12:24, Gleb Smirnoff wrote:
On Fri, Sep 05, 2014 at 08:38:10AM -0700, Mark Atkinson wrote: M
r271093 GENERIC amd64. Received this panic in the tcp reassembly
code: M Unread portion of the kernel message buffer: M panic:
m_demote:
On Mon, Sep 8, 2014 at 11:48 AM, Brooks Davis bro...@freebsd.org wrote:
If you don't mind the ownership being wrong and there being a few extra
+FOO files tar works. It would be great for someone to teach package to
install without root and to update a METALOG file. That's not 100% of
the
Hi,
I've got some new hardware and have been experiencing lockups using the em
driver. They seem to only happen on large downloads, smaller things like ssh
and web browsing work OK. The hardware is:
em0@pci0:0:25:0:class=0x02 card=0x309f17aa chip=0x153a8086 rev=0x04
hdr=0x00
On 2014-09-08 13:14, Steve Wills wrote:
Hi,
I've got some new hardware and have been experiencing lockups using the em
driver. They seem to only happen on large downloads, smaller things like ssh
and web browsing work OK. The hardware is:
em0@pci0:0:25:0:class=0x02
On Mon, Sep 08, 2014 at 01:29:31PM -0400, Allan Jude wrote:
Try periodically setting dev.em.0.debug=1
it will dump a bunch of stats to syslog then set it self back to -1
there are also a bunch of useful stats under:
dev.em.0 including things like:
dev.em.0.mbuf_alloc_fail
On Mon, Sep 08, 2014 at 01:06:38PM -0400, Julio Merino wrote:
On Mon, Sep 8, 2014 at 11:48 AM, Brooks Davis bro...@freebsd.org wrote:
If you don't mind the ownership being wrong and there being a few extra
+FOO files tar works. It would be great for someone to teach package to
install
On Mon, Sep 8, 2014 at 8:48 AM, Brooks Davis bro...@freebsd.org wrote:
If you don't mind the ownership being wrong and there being a few extra
+FOO files tar works. It would be great for someone to teach package to
install without root and to update a METALOG file. That's not 100% of
the
In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
non-append, write-only path. Consequently, programs that use _ftello()
(via ftell, fgetpos, fsetpos, fseek, rewind...) on non-append, write-only
files and that use capsicum to restrict capabilities on the associated fds
to
On 09.09.2014 0:28, Patrick Kelsey wrote:
In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
non-append, write-only path. Consequently, programs that use _ftello()
(via ftell, fgetpos, fsetpos, fseek, rewind...) on non-append,
write-only files and that use capsicum to restrict
On Mon, Sep 8, 2014 at 4:42 PM, Andrey Chernov a...@freebsd.org wrote:
On 09.09.2014 0:28, Patrick Kelsey wrote:
In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
non-append, write-only path. Consequently, programs that use _ftello()
(via ftell, fgetpos, fsetpos, fseek,
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD/1411/
--
Started by an SCM change
Building remotely on jenkins-10.freebsd.org (FreeBSD-10) in workspace
https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD/ws/
Updating
On 09.09.2014 1:13, Patrick Kelsey wrote:
You make a godo point about the wider use of fcntl() in libc - aside
from the rpc code, by my count there are 14 other entry points in libc
that use fcntl in their implementation. To experience breakage,
programs that use those entry points would also
Let me remove my concerns earlier in the thread -- this patch won't
negatively affect any of our drivers; and the problem I mentioned with ixl
would require a change somewhere further up the stack.
---
- Eric Joyner
On Mon, Sep 8, 2014 at 5:05 AM, Rick Macklem rmack...@uoguelph.ca wrote:
Hans
Please check the headers and then ask me. This is for those who may assume
that I do such things.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
See https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD/1412/changes
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
20 matches
Mail list logo
