On Sat, Jan 10, 2009 at 04:07:24AM +0100, Barbara wrote:
[...]
Would try the following WIP version?
http://people.
freebsd.org/~yongari/age/if_age.c
http://people.freebsd.
org/~yongari/age/if_agereg.h
I have no longer access to L1 hardware so I don't
know whether it
helps or
On Fri, Jan 09, 2009 at 01:48:24PM +0200, Danny Braniss wrote:
hi, the mb is asus P5K-VM, the onboard nic is, acccording to pciconf:
ms...@pci0:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab
rev=0x12 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo
Hi,
On 2009-01-09, Doug Barton wrote:
Yannick Cadin wrote:
- first in the stat command. Only with the -x option. If you execute
stat -x on /tmp or /usr/bin/passwd parameters for example, the numeric
representation of mode is wrong. The special bits are always 0. No
suid-bit, no sticky
on 21/11/2008 15:14 Andriy Gapon said the following:
I wasn't sure where this belongs, so writing here.
This is stable/7 on Intel DG33TL:
$ pciconf -lv
...
atap...@pci0:3:0:0: class=0x01018f card=0x610111ab chip=0x610111ab
rev=0xb2 hdr=0x00
vendor = 'Marvell Semiconductor
$ /etc/rc.d/mountd onestart
/etc/rc.d/mountd: WARNING: /etc/exports is not readable.
Exit 1
Actually /etc/exports did not exist at all.
And this was not a WARNING, this was a fatal error, mountd did not start.
Alsp, should it actually fail like this? I have ZFS and I plan to do
all NFS exports
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
- Support AMD/ATI IGP based chips (rs690/rs485)
- Lots of code cleanups
- Lots of other fixes and changes since the
On Sat, Jan 10, 2009 at 6:20 AM, Andriy Gapon a...@icyb.net.ua wrote:
$ /etc/rc.d/mountd onestart
/etc/rc.d/mountd: WARNING: /etc/exports is not readable.
Exit 1
Actually /etc/exports did not exist at all.
And this was not a WARNING, this was a fatal error, mountd did not start.
Alsp,
on 10/01/2009 17:11 Garrett Cooper said the following:
On Sat, Jan 10, 2009 at 6:20 AM, Andriy Gapon a...@icyb.net.ua wrote:
$ /etc/rc.d/mountd onestart
/etc/rc.d/mountd: WARNING: /etc/exports is not readable.
Exit 1
Actually /etc/exports did not exist at all.
And this was not a WARNING,
On Sat, Jan 10, 2009 at 7:14 AM, Andriy Gapon a...@icyb.net.ua wrote:
on 10/01/2009 17:11 Garrett Cooper said the following:
On Sat, Jan 10, 2009 at 6:20 AM, Andriy Gapon a...@icyb.net.ua wrote:
$ /etc/rc.d/mountd onestart
/etc/rc.d/mountd: WARNING: /etc/exports is not readable.
Exit 1
Alsp, should it actually fail like this? I have ZFS and I plan to do
all NFS exports from ZFS, so /etc/exports would never be used.
ZFS writes its own exports file to '/etc/zfs/exports' - as far as I can
tell this is pretty much all that happens when you mark a filesystem
as NFS shared under
On Sat, Jan 10, 2009 at 7:24 AM, Garrett Cooper yanef...@gmail.com wrote:
On Sat, Jan 10, 2009 at 7:20 AM, Andriy Gapon a...@icyb.net.ua wrote:
on 10/01/2009 17:18 Garrett Cooper said the following:
s/same functionality/same basic functionality/.
Mind you, NFS is a networking
FWIW, the other guy I know who is having this problem had already
switched to using ULE under 7.0-release, and did not have any
problems with it. So *his* problem was probably not related to
SCHED_ULE, unless something has recently changed there.
Well, one of my machines just locked up
On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
- Support AMD/ATI IGP based chips (rs690/rs485)
- Lots of code
On Sat, Jan 10, 2009 at 11:49:01AM -0500, Robert Noland wrote:
On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
-
On Sat, 2009-01-10 at 18:54 +0100, Roland Smith wrote:
On Sat, Jan 10, 2009 at 11:49:01AM -0500, Robert Noland wrote:
On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support
On Saturday 10 January 2009 08:49:01 am Robert Noland wrote:
On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
-
I found a 7.1-RELEASE manpage stating first appeared in FreeBSD 8.0. A
little bit of grepping revealed a few more:
setfib(1) setfib(2) ffs(3) ffsl(3) ffsll(3) fls(3) flsl(3) flsll(3)
memchr(3) memrchr(3) malo(4) crashinfo(8) savecore(8)
Some others are correctly stating 7.1 for example
I'm using 7.0-RELEASE.
When there's heavy network traffic through the vr0 interface, I see lots
of vr0: rx packet lost messages, and occasional vr0: watchdog
timeout messages. I googled and found some information, but it was on
an earlier version of FreeBSD, and there weren't any solutions.
On Sat, 2009-01-10 at 15:53 -0800, vehemens wrote:
On Saturday 10 January 2009 08:49:01 am Robert Noland wrote:
On Sat, 2009-01-10 at 10:01 -0500, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and
At 07:49 PM 1/10/2009, David Ehrmann wrote:
I'm using 7.0-RELEASE.
Ideas? Is there any additional information I should provide?
7.1R has a *far* better vr driver that has a lot of bug fixes in it.
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/vr/if_vr.c
has details of what was fixed.
I noticed a similar problem testing 7.1-RC1, It seemed to be a deep
deadlock, as it was triggered by lighttpd doing kern_sendfile, and
never returning. The side effects (being unable to create processes,
etc) is similar.
My kernconf is below, try building the kernel, and send an email
containing
On Sat, Jan 10, 2009 at 08:51:06PM -0500, Mike Tancsa wrote:
At 07:49 PM 1/10/2009, David Ehrmann wrote:
I'm using 7.0-RELEASE.
Ideas? Is there any additional information I should provide?
7.1R has a *far* better vr driver that has a lot of bug fixes in it.
Wow. That really is a lot, but I might just wait for the final release,
though with this command, it might not be such a big deal:
freebsd-update upgrade -r 7.1-RC1
Mike Tancsa wrote:
At 07:49 PM 1/10/2009, David Ehrmann wrote:
I'm using 7.0-RELEASE.
Ideas? Is there any additional
On 2009-Jan-10 19:15:22 -0800, David Ehrmann ehrm...@gmail.com wrote:
Wow. That really is a lot, but I might just wait for the final release,
though with this command, it might not be such a big deal:
freebsd-update upgrade -r 7.1-RC1
FreeBSD 7.1-RELEASE has been available for nearly a week.
24 matches
Mail list logo
