On Tue, May 02, 2006 at 10:52:23AM -0300, Renato Botelho wrote:
I've updated my src today using RELENG_6,
when i'm running a buildworld, i got this problem on libnetgraph
=== lib/libnetgraph (depend,all,install)
rm -f .depend
CC='/usr/local/libexec/ccache/cc' mkdep -f .depend -a
chflags -R noschg /var/empty
2006/5/3, Martin Jackson [EMAIL PROTECTED]:
Hello everyone,
When BETA4 was released, I installed it on a very old machine of mine,
and tried doing a binary upgrade from 6.0-RELEASE to 6.1-BETA4. I got
an error almost immediately that it failed to write because it
At Tue, 2 May 2006 21:56:49 -0400,
Kris Kennaway wrote:
On Wed, May 03, 2006 at 10:54:38AM +0900, MANTANI Nobutaka wrote:
Kris, may I commit the patch and close my PR (ports/95238) ?
It has been in the portmgr team's PR queue for a month. :-)
No, it needs to be fully tested first.
On Wed, May 03, 2006 at 10:14:28AM +0400, Alexey Karagodov wrote:
chflags -R noschg /var/empty
You missed the point..the claim is that sysinstall barfs when it
encounters a /var/empty that is legitimately schg.
Kris
P.S. Don't top-post
2006/5/3, Martin Jackson [EMAIL PROTECTED]:
Hello
On 5/3/06, David Nugent [EMAIL PROTECTED] wrote:
Pietro Cerutti wrote:
just updated my RELENG_6 as Tue May 2 08:25:55 CEST 2006
There are some things that are not clear about the version:
- uname says FreeBSD 6.1-RC #0
- on the FreeBSD FTP site the RC directory is now RC2
On Wednesday 03 May 2006 06:46, Nikolas Britton wrote:
On 3/27/06, Alastair G. Hogge [EMAIL PROTECTED] wrote:
G'day
Having some problem with Xorg-6.9.0 and the radeon or ati driver on mad64
system. X seems to look up at a black screen after setting the resolution
and then resets the
On 5/3/06, Ruslan Ermilov [EMAIL PROTECTED] wrote:
On Tue, May 02, 2006 at 10:52:23AM -0300, Renato Botelho wrote:
I've updated my src today using RELENG_6,
when i'm running a buildworld, i got this problem on libnetgraph
=== lib/libnetgraph (depend,all,install)
rm -f .depend
On Tue, 2 May 2006, Kris Kennaway wrote:
Ditto, same thing with the recent nve fixes. Why release known broken
code when there are tested patches available? Whats the worst that will
happen? It wont work? Thats already the case...
...
OK, I can't speak to that issue specifically.
Kris Kennaway wrote:
On Wed, May 03, 2006 at 10:14:28AM +0400, Alexey Karagodov wrote:
chflags -R noschg /var/empty
You missed the point..the claim is that sysinstall barfs when it
encounters a /var/empty that is legitimately schg.
Kris and freebsd-stable,
Your reading of my bug report is
Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad
(running 6.1-RC) doesn't have a standard db-9 port.
Thx.
David Coder
Erstwhile Network Engineer
Washington, DC
___
freebsd-stable@freebsd.org mailing list
On Wed, May 03, 2006 at 08:33:22AM -0400, David Coder wrote:
Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad
(running 6.1-RC) doesn't have a standard db-9 port.
uftdi(4) for some USB/RS232 adapters.
Marc
___
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nikolas Britton
Sent: Tuesday, May 02, 2006 2:46 PM
To: Alastair G. Hogge
Cc: freebsd-stable@freebsd.org
Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64
On 3/27/06, Alastair G. Hogge [EMAIL PROTECTED]
On 5/2/06, Sean Bryant [EMAIL PROTECTED] wrote:
ndisgen is broken on 6.1 RC1 if I remember correctly.
ndisgen wasn't broken, wpa_supplicant was broken as it didn't
recognize the ndis interfaces. The fix has since been applied to
-CURRENT and MFC'd to the RELENG_6 and RELENG_6_1 branches.
On May 3, 2006, at 8:33 AM, David Coder wrote:
Is there a generic freebsd driver for usb-to-rs-232 adapters? My
Thinkpad
(running 6.1-RC) doesn't have a standard db-9 port.
I bought a generic one from BestBuy which works with the uplcom
driver (I just load it from loader.conf). I have
Marc Fonvieille:
On Wed, May 03, 2006 at 08:33:22AM -0400, David Coder wrote:
Is there a generic freebsd driver for usb-to-rs-232 adapters? My Thinkpad
(running 6.1-RC) doesn't have a standard db-9 port.
uftdi(4) for some USB/RS232 adapters.
uplcom(4) as well, for example
ucom0: Prolific
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear
to have it enabled, but my older i386 server that I just upgraded to 6.x
does:
user pid %cpu %mem vsz rss tt state starttime command
root 14 104.0 0.0 0 8 ?? RL11:38AM 0:55.02
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear
to have it enabled, but my older i386 server that I just upgraded to
6.x
does:
Is it still something that I should disable, and, if so, how in 6.x?
Can you disable it in the BIOS or do you dual boot this machine?
ndisgen fails for me on 6.1-RC1 and 6.1-RC2.
Any ideas?
On 5/3/06, Scot Hetzel [EMAIL PROTECTED] wrote:
On 5/2/06, Sean Bryant [EMAIL PROTECTED] wrote:
ndisgen is broken on 6.1 RC1 if I remember correctly.
ndisgen wasn't broken, wpa_supplicant was broken as it didn't
recognize the ndis
Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear to have it enabled, but my older i386 server that I just
upgraded to 6.x does:
user pid %cpu %mem vsz rss tt state starttime command
root 14 104.0 0.0 0 8 ?? RL
On Wed, 3 May 2006, Zimmerman, Eric wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear
to have it enabled, but my older i386 server that I just upgraded to
6.x
does:
Is it still something that I should disable, and, if so, how in 6.x?
Can you disable it in
On Wed, May 03, 2006 at 01:06:24PM -0300, Marc G. Fournier wrote..
On Wed, 3 May 2006, Zimmerman, Eric wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear
to have it enabled, but my older i386 server that I just upgraded to
6.x
does:
Is it still something
Just had the following panic on 6.1-RC from source current as of 24
hours ago:
db ex/s *panicstr
buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037
db tr
Tracing pid 6158 tid 100120 td 0xc64e4180
kdb_enter(c089df29) at kdb_enter+0x2b
panic(c089d3c0,c08b1ac6,c08a7350,7f5,c6f8a550)
On Wed, 3 May 2006, Wilko Bulte wrote:
On Wed, May 03, 2006 at 01:06:24PM -0300, Marc G. Fournier wrote..
On Wed, 3 May 2006, Zimmerman, Eric wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear
to have it enabled, but my older i386 server that I just upgraded
On 5/3/06, Wilde, Donald [EMAIL PROTECTED] wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nikolas Britton
Sent: Tuesday, May 02, 2006 2:46 PM
To: Alastair G. Hogge
Cc: freebsd-stable@freebsd.org
Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64
At 11:36 AM 5/3/2006, Chuck Swiger wrote:
Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear to have it enabled, but my older i386 server that I just
upgraded to 6.x does:
user pid %cpu %mem vsz rss tt state starttime command
This is for the archives: problem was identified as a bad
motherboard/onboard NIC and has been replaced (thanks Silicon
Mechanics!). Everything is going smoothly now!
-- Robert
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-freebsd-
[EMAIL PROTECTED] On Behalf Of Robert
On Wed, May 03, 2006 at 02:12:45PM -0300, Marc G. Fournier wrote..
On Wed, 3 May 2006, Wilko Bulte wrote:
On Wed, May 03, 2006 at 01:06:24PM -0300, Marc G. Fournier wrote..
On Wed, 3 May 2006, Zimmerman, Eric wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote:
Just had the following panic on 6.1-RC from source current as of 24
hours ago:
db ex/s *panicstr
buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037
db tr
Tracing pid 6158 tid 100120 td 0xc64e4180
On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear
to have it enabled, but my older i386 server that I just upgraded to 6.x
does:
I am not sure I understood your problem correctly... Do you want
to
Spartak Radchenko wrote:
On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear to have it enabled, but my older i386 server that I just
upgraded to 6.x does:
I am not sure I understood your problem
Hi Scott.
I am grateful for and honored by your response. I am pretty much stuck
with the asr device for now, but I would love a list of quality hardware
raid devices and related management utilities that can be used with
freebsd/linux.
I can get raidutil (sysutils/asr-utils) to recognize a
On Wed, May 03, 2006 at 01:36:04PM -0400, Vinny Abello wrote:
An Intel technical rep that gave a presentation on upcoming Intel VT
technology in processors (Virtualization Technology) that I attended
indicated that Hyperthreading was really designed to start getting
programmers to program
On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote:
Just had the following panic on 6.1-RC from source current as of 24
hours ago:
db ex/s *panicstr
buf.1: mutex Giant not owned at /usr/src/sys/kern/vfs_subr.c:2037
db tr
Tracing pid 6158 tid 100120 td 0xc64e4180
Adam wrote:
Hi Scott.
I am grateful for and honored by your response. I am pretty much stuck
with the asr device for now, but I would love a list of quality hardware
raid devices and related management utilities that can be used with
freebsd/linux.
Is there any chance that you could just
On Wed, May 03, 2006 at 01:44:02PM -0500, Larry Rosenman wrote:
Spartak Radchenko wrote:
On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear to have it enabled, but my older i386 server that I just
On Wed, 3 May 2006, Spartak Radchenko wrote:
On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear
to have it enabled, but my older i386 server that I just upgraded to 6.x
does:
I am not sure I understood
Scot, Bill,
Scot Hetzel wrote:
You need to use the ndisgen script to create the NDIS kernel module
for your card.
ndisgen /compat/ndis/w70n51.inf /compat/ndis/w70n51.sys
Thanks! Since when is this required? I think I never ran this tool
before. Where is this documented?
Anyway, now ndis0
On Wed, 3 May 2006, Spartak Radchenko wrote:
On Wed, May 03, 2006 at 01:44:02PM -0500, Larry Rosenman wrote:
Spartak Radchenko wrote:
On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't
appear to have it
This is an odd cosmetic bug, this is what i see when the system boots:
atapci1: HighPoint HighPoint HighPoint HighPoint Hi UDMA133 controller
port
0xb800-0xb807,0xbc00-0xbc03,0xc000-0xc007,0xc400-0xc403,0xc800-0xc8ff
irq 10 at device 19.0 on pci0
The system works fine otherwise, I have
Kris Kennaway wrote:
On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote:
I didn't have a serial console attached at the time (hence the need to
print the panicstr separately) and couldn't get a dump, so I hope the
above is enough to go on.
Unfortunately it may not be..but
On Wed, May 03, 2006 at 03:39:41PM -0400, Mike Jakubik wrote:
Kris Kennaway wrote:
On Wed, May 03, 2006 at 06:01:37PM +0100, Gavin Atkinson wrote:
I didn't have a serial console attached at the time (hence the need to
print the panicstr separately) and couldn't get a dump, so I hope the
We have a bunch of SuperMicro 6013P-8+ boxes that had a lot of issues
under 5.x I've been testing the 6.1-RC and am happy to report that
everthing is working fine. Specifically, the scsi controller
resetting issues reported in:
Subject: FreeBSD 5.3p6-5.4RC3, Supermicro X6DHR-8G, Dual 3.6GHz
On Wed, 3 May 2006, Scott Long wrote:
Adam wrote:
I am pretty much stuck with the asr device for now...
Is there any chance that you could just plug a simple Adaptec 2940 or
even a low-end TekRam card into an unused slot on your motherboard?
I am moving from a scsi raid disk spool to a
I just upgraded one of my old 4.x server to 6.x, and the one annoying
problem that I've experienced with 4.x persists in 6.x ...
... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip
stack (I'm guessing) hangs for a period of time, while my 6.x/bge0 servers
don't hang at
Hi
somebody knows about this?
I get constant messages on a releng_6
I get it on all ath interfaces :
May 3 16:30:01 ap1-and kernel: ath2: discard oversize frame (ether type 5e4
flags 3 len 1522 max 1514)
May 3 16:30:26 ap1-and last message repeated 2 times
May 3 16:32:27 ap1-and last
Marc G. Fournier wrote:
I just upgraded one of my old 4.x server to 6.x, and the one annoying
problem that I've experienced with 4.x persists in 6.x ...
... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip
stack (I'm guessing) hangs for a period of time, while my 6.x/bge0
Robert Watson wrote:
On Tue, 2 May 2006, Kris Kennaway wrote:
Ditto, same thing with the recent nve fixes. Why release known broken
code when there are tested patches available? Whats the worst that
will
happen? It wont work? Thats already the case...
...
OK, I can't speak to that
Dear FreeBSD Folks,
Help me...yeah...OK...so here it goes...I am brand new to
FreeBSD...installed OS onto a box from
a set of floppies I got off the net...
Last login: Wed May 3 14:37:21 2006 from 10.10.20.20
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
On 5/3/06, Marc G. Fournier [EMAIL PROTECTED] wrote:
I just upgraded one of my old 4.x server to 6.x, and the one annoying
problem that I've experienced with 4.x persists in 6.x ...
... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip
stack (I'm guessing) hangs for a period of
On Wed, 03 May 2006 22:26:53 +
John Dworske [EMAIL PROTECTED] wrote:
FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003
Wondering what I need to update my system to make sure it has
everything I need to do work...like want to setup a slave DNS
server and apache
not to sound sharp, but what happened with Google for you?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bind9.html
cd /usr/ports/www/apache13 make make install
On 5/3/06, John Dworske [EMAIL PROTECTED] wrote:
Dear FreeBSD Folks,
Help me...yeah...OK...so here
John Dworske [EMAIL PROTECTED] wrote:
Help me...yeah...OK...so here it goes...I am brand new to
FreeBSD...installed OS onto a box from
a set of floppies I got off the net...
Last login: Wed May 3 14:37:21 2006 from 10.10.20.20
Copyright (c) 1980, 1983, 1986, 1988, 1990,
On 5/3/06, Robert Watson [EMAIL PROTECTED] wrote:
This means that
they will take a significant amount of time to fix, and that each fix is high
risk, as it is likely to reveal latent bugs. This means that each fix will
require a lot of testing -- months of testing, in fact. So the choice is
On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote:
On 5/3/06, Robert Watson [EMAIL PROTECTED] wrote:
This means that
they will take a significant amount of time to fix, and that each fix is
high
risk, as it is likely to reveal latent bugs. This means that each fix will
require
On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote:
Would there really be harm in putting off a release until these well-
acknowledged bugs are taken care of?
Yes. We tagged the ports tree on April 14th, and that's the last date
of any changes the CDs will ship with. That's a
On Wed, May 03, 2006 at 10:26:53PM +, John Dworske wrote:
FreeBSD 4.9-RELEASE (GENERIC) #0: Mon Oct 27 17:51:09 GMT 2003
4.9 is no longer supported. You should use 5.4 or 6.0, or, preferably,
wait for about a week and use 5.5 or 6.1. I would recommend 6.X; 5.X is
at this point essentially
On Wed, May 03, 2006 at 05:42:41PM -0700, David Kirchner wrote:
I don't know the protocol for this -- would the old PRs be re-opened,
or should a new PR be filed for 6.x?
I'd recommend filing a new PR but reference the older ones in case it
is indeed the same problem.
mcl
Also, as an aside ... 6.x em(4) still isn't sending up the arp broadcasts,
so IPs moved from one machine to this one aren't having their routes
appropriately updated ... again, please note, that moving an IP from any
machine to a *non* em(4) interface does update the routes properly and
Kris Kennaway wrote:
On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote:
On 5/3/06, Robert Watson [EMAIL PROTECTED] wrote:
This means that
they will take a significant amount of time to fix, and that each fix is
high
risk, as it is likely to reveal latent bugs. This means that
On 5/3/06, Mark Linimon [EMAIL PROTECTED] wrote:
To summarize: at some point you do, indeed, have to ship something. You
have to choose a point where the least number of users will see regressions
vs. the most number of users will see improvements. (Not everyone uses
quotas.)
FWIW, the
On 5/3/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote:
However, one could argue that as quotas worked OK in releases prior to
6.0 (and perhaps earlier), that there is a longer-term regression.
There was a quota regression in 6.0. It
On Wed, May 03, 2006 at 08:05:12PM -0700, David Kirchner wrote:
On 5/3/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Wed, May 03, 2006 at 06:21:39PM -0700, David Kirchner wrote:
However, one could argue that as quotas worked OK in releases prior to
6.0 (and perhaps earlier), that there is a
On Wed, May 03, 2006 at 08:11:32PM -0700, David Kirchner wrote:
On 5/3/06, Mark Linimon [EMAIL PROTECTED] wrote:
To summarize: at some point you do, indeed, have to ship something. You
have to choose a point where the least number of users will see regressions
vs. the most number of users
Kris Kennaway wrote:
On Wed, May 03, 2006 at 08:11:32PM -0700, David Kirchner wrote:
On 5/3/06, Mark Linimon [EMAIL PROTECTED] wrote:
To summarize: at some point you do, indeed, have to ship something. You
have to choose a point where the least number of users will see regressions
vs.
On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote:
Kris Kennaway wrote:
On Wed, May 03, 2006 at 08:11:32PM -0700, David Kirchner wrote:
On 5/3/06, Mark Linimon [EMAIL PROTECTED] wrote:
To summarize: at some point you do, indeed, have to ship something. You
have to choose
Kris Kennaway wrote:
On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote:
Kris Kennaway wrote:
You missed the part where snapshots have caused deadlocks under
varying conditions since day 1. They have never worked 100% reliably,
and despite our best efforts that will remain
66 matches
Mail list logo
