Hi list,
/usr/ports/UPDATING reads:
20061009:
AFFECTS: users of any ports using Python
AUTHOR: [EMAIL PROTECTED]
After upgrading of lang/python, you must rebuild all its consumer
ports to make them get ready to Python 2.5.
To do this, you will need to:
pkgdb -uf cd
On Wednesday 11 October 2006 13:15, Sun Zongjun-E5739C wrote:
I run the command on device running FreeBSD 6.1
Test# cu -l /dev/cuad0
Connected
There is no response on the FreeBSD except the Connected string. Such
string can occur even there is no cable available.
What happens to cu
Daniel O'Connor wrote:
On Wednesday 11 October 2006 13:15, Sun Zongjun-E5739C wrote:
I run the command on device running FreeBSD 6.1
Test# cu -l /dev/cuad0
Connected
There is no response on the FreeBSD except the Connected string. Such
string can occur even there is no cable available.
with the latest cvsup'ed, the em is sending packets but not receiving.
the last working version that i have is from 3rd. Oct.
host is S2466 TIGER MPX, but have seen the problem on PIII/STL2.
o- there is no if_em changes that i can see.
o- smp/up has no effect - the kernel is smp, just
Jeremy Chadwick wrote:
On Thu, Oct 05, 2006 at 05:28:03PM +0200, Heinrich Rebehn wrote:
[EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M
count=10
10485760 bytes transferred in 4.967248 secs (2110980 bytes/sec)
[EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero
On Wed, Oct 11, 2006 at 07:54:45AM +0200, Heinrich Rebehn wrote:
Overhead ?? Would this mean that the 64 bit version will run slower?
It will use more memory
___
freebsd-stable@freebsd.org mailing list
Hi,
On Sun, Oct 01, 2006 at 12:30:22AM -0700, FreeBSD Security Officer wrote:
Users of FreeBSD 4.11 systems are also reminded that that FreeBSD 4.11
will reach its End of Life at the end of January 2007 and that they
should be making plans to upgrade or replace such systems.
Though I admit
On Wednesday 11 October 2006 17:20, Oleg Dambaev wrote:
Two questions
1) Is cuad0 the correct port? Have you tried cuad1?
2) What baud rate are you using? (the -s flag)
Good way to try *first*:
0. man stty
1. use tip instead cu
shrugs I prefer cu - you just specify the baud rate and tty
I'm now starting to get worried... last night the box spewed forth
these:
dtfe2 kernel log messages:
+++ /tmp/security.N8067F3a Wed Oct 11 03:03:32 2006
+g_post_event_x(0x80210a70, 0xff0016c551a0, 2, 262144)
+g_post_event_x(0x80210a70, 0xff003c90cc20, 2, 262144)
Hello!
On Wed, 11 Oct 2006, Jeremie Le Hen wrote:
Though I admit RELENG_4 is getting dusty, it is not rusty. I believe it
is still used in many places because of its stability and performance.
For instance, according to Julian Elischer's posts, it seems he is still
working on it.
Is it
On Tue, 2006-10-10 at 22:11 -0700, Doug Ambrisko wrote:
Sven Willenberger writes:
| FreeBSD 6.2-PRERELEASE #3: Tue Oct 10 13:58:29 EDT 2006
| LSi 8480e SAS Raid card
|
| mount:
| linprocfs on /compat/linux/proc (linprocfs, local)
| linsysfs on /compat/linux/sys (linsysfs, local)
|
Sven Willenberger writes:
| On Tue, 2006-10-10 at 22:11 -0700, Doug Ambrisko wrote:
| Sven Willenberger writes:
| | FreeBSD 6.2-PRERELEASE #3: Tue Oct 10 13:58:29 EDT 2006
| | LSi 8480e SAS Raid card
| Adding mfi_linux_enable=YES to /boot/loader.conf did do the trick of
| having the device
Vivek Khera wrote:
I'm now starting to get worried... last night the box spewed forth
these:
dtfe2 kernel log messages:
+++ /tmp/security.N8067F3a Wed Oct 11 03:03:32 2006
+g_post_event_x(0x80210a70, 0xff0016c551a0, 2, 262144)
+g_post_event_x(0x80210a70,
Bill Moran wrote:
I've copied many of the people who I've been working with directly on
this issue.
Can anyone provide a status update on these problems? Discussion seems
to have stopped since Oct 5.
Any new patches to test?
I'm actively working on fixing the driver right now.
Scott
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Though I admit RELENG_4 is getting dusty, it is not rusty. I believe it
is still used in many places because of its stability and performance.
[...]
Is it envisageable to extend the RELENG_4's and RELENG_4_11's EoL once
more ?
Yes, I'm also
On Wed, Oct 11, 2006 at 12:12:06PM -0300, Eduardo Meyer wrote:
ngctl: send msg: No such file or directory
Exit 71
Same problem. With ngctl list the only node I see is:
There are 1 total nodes:
Name: ngctl19792 Type: socket ID: 003f Num hooks: 0
You do not
ngctl msg my_node: setprogram { thisHook=hook1 ifMatch=hook2
ifNotMatch=hook3 bpf_prog_len=16 bpf_prog=[ { code=40 jt=0 jf=0 k=12
} { code=21 jt=0 jf=4 k=34525 } { code=48 jt=0 jf=0 k=20 } { code=21
jt=0 jf=11 k=6 } { code=40 jt=0 jf=0 k=56 } { code=21 jt=8 jf=9 k=80 }
{ code=21 jt=0 jf=8
here is a picture of a panic i get on a Dell Precision 390 booting
6.2-beta2_amd64. hope this helps.
http://users.centtech.com/~kramer/broadcom/bge_prec390.jpg
--
Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.com
Scott
Hi,
I got the following panic on a i386 6.2-PRELEASE system :
panic: bogus refcnt 0
Uptime: 1d14h3m32s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 319
303 287 271 255 239 223 207 191 175 159 143 127 111
is there a need in ng_ether module?
On 10/11/06, Eduardo Meyer [EMAIL PROTECTED] wrote:
ngctl msg my_node: setprogram { thisHook=hook1 ifMatch=hook2
ifNotMatch=hook3 bpf_prog_len=16 bpf_prog=[ { code=40 jt=0 jf=0 k=12
} { code=21 jt=0 jf=4 k=34525 } { code=48 jt=0 jf=0 k=20 } { code=21
I've copied many of the people who I've been working with directly on
this issue.
Can anyone provide a status update on these problems?
Discussion seems
to have stopped since Oct 5.
Any new patches to test?
I'm sorry but I'm absolutely swamped with my day job 6.5 days a week and
Bill Moran wrote:
I've copied many of the people who I've been working with
directly on
this issue.
Can anyone provide a status update on these problems?
Discussion seems
to have stopped since Oct 5.
Any new patches to test?
I'm actively working on fixing the driver
On Oct 11, 2006, at 10:57 AM, Oliver Fromme wrote:
Vivek Khera wrote:
I'm now starting to get worried... last night the box spewed forth
these:
dtfe2 kernel log messages:
+++ /tmp/security.N8067F3a Wed Oct 11 03:03:32 2006
+g_post_event_x(0x80210a70, 0xff0016c551a0, 2,
I realize that resources to keep chasing this stuff are in limited supply,
but if you solicit the opinion of the community, I'd bet that more people
would rather see 4.x support continue than 5.x support.
I know that it would be a violation of the stated policy, but I think that
On 10/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I realize that resources to keep chasing this stuff are in limited
supply,
but if you solicit the opinion of the community, I'd bet that more
people
would rather see 4.x support continue than 5.x support.
I know that it would be a
GCC would not fix the bug described in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29390
because the compiler is of an unsupported version (they only support 4.x now).
Yet, the problem is rather real and hits when the devel/icu port is built with
low optimization (-O1 or -O0).
Any
On Wed, Oct 11, 2006 at 01:02:50PM -0300, Eduardo Meyer wrote:
ngctl msg my_node: setprogram { thisHook=hook1 ifMatch=hook2
ifNotMatch=hook3 bpf_prog_len=16 bpf_prog=[ { code=40 jt=0 jf=0 k=12
} { code=21 jt=0 jf=4 k=34525 } { code=48 jt=0 jf=0 k=20 } { code=21
jt=0 jf=11 k=6 } { code=40
Mmmm, the 5787. Such is the way of ordering high end Dell workstations
tested only with RHEL3 and Windows XP.
~BAS
On Wed, 2006-10-11 at 11:21 -0500, Kevin Kramer wrote:
here is a picture of a panic i get on a Dell Precision 390 booting
6.2-beta2_amd64. hope this helps.
Hello Thomas,
I'm having an issue with atapicam. Loading the kernel module doesn't
create /dev/cd* as expected but seems to have a serious impact on system
performance. Compiling it into the kernel causes the boot to hang after
detecting acd0 and acd1 (although after reading the mailing list,
Jeremie Le Hen wrote:
Hi,
On Sun, Oct 01, 2006 at 12:30:22AM -0700, FreeBSD Security Officer wrote:
Users of FreeBSD 4.11 systems are also reminded that that FreeBSD 4.11
will reach its End of Life at the end of January 2007 and that they
should be making plans to upgrade or replace such
At 8:42 AM -0700 10/11/06, Jason Stone wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Though I admit RELENG_4 is getting dusty, it is not rusty. I believe it
is still used in many places because of its stability and performance.
[...]
Is it envisageable to extend the RELENG_4's and
Hello,
I have 4 HP Proliant DL360's (1u) which panic/reboot often (minimum
1x month), but in a seemingly inconsistent manner. As per other
suggestions, ipf was replaced with pf, an Intel pro 100 was added, the
BGE device was disabled in the BIOS and the BGE driver was removed from
the
On Wed, Oct 11, 2006 at 04:09:57PM -0400, Matt Smith wrote:
Lately, I've been having Unreal and sometimes Apache on my 6.0 box crash
randomly. I'm thinking it might be RAM related
The best way to test for memory troubles is to run a memory testing
program like memtest86
Oliver,
Thanks for the very insightful post on this topic. I have just one
remaining question, does what you said apply to the new Intel Core 2
Duo chips as well?
thanks,
Doug
--
This .signature sanitized for your protection
___
On Wed, 11 Oct 2006, Dmitry Pryanishnikov wrote:
On Wed, 11 Oct 2006, Jeremie Le Hen wrote:
...
Is it envisageable to extend the RELENG_4's and RELENG_4_11's EoL once
more ?
Yes, I'm also voting for it. This support may be limited to
remote-exploitable vulnerabilities only, but I'm sure
Jason Stone wrote:
I realize that resources to keep chasing this stuff are in limited
supply,
You just hit the nail on the head. The vast majority of FreeBSD
developers (including but not limited to the committer community) have
moved on. If you (meaning the people that want continued
Well, I suspect that most people with the resources to do what you ask
have already moved on precisely because the EoL has been published.
i.e., faced with that limited commitment, we had no choice but to
(grudgingly and at the last minute) move on.
I think the most likely path of success is, as
Garance A Drosihn napsal/wrote, On 10/11/06 21:33:
Even if no new ports will be compilable on 4.x, even if the
old ports will not be updated with exception of update caused by
security bug, I vote for delaying EOL of 4.11
That's easy to say.
I understand that it's much more work than
On Wed, Oct 11, 2006 at 03:36:10PM -0700, Paul Allen wrote:
Well, I suspect that most people with the resources to do what you ask
have already moved on precisely because the EoL has been published.
i.e., faced with that limited commitment, we had no choice but to
(grudgingly and at the last
Lots of knashing of the teeth on this one but lets face it, it had to
die sometime. For all the 4.x users still out there (and plenty of
them have deep pockets) no reason you can't just hire third party
support (possibly even a current developer); hell get together and
maybe pool your resources.
Marcus Alves Grando wrote:
Eric Anholt wrote:
On Mon, 2006-10-02 at 13:25 +0800, Ganbold wrote:
Hi,
http://marcus.grupos.com.br:8080/patch/agp_i810.c.patch
Eric, Marcus,
Any update on 945GM support patch?
I tested Marcus's patch but problem still exists. Without loading
acpi_video mouse
At 12:42 AM +0200 10/12/06, Dan Lukes wrote:
As I'm not commiter, I'm allowed to submit PR and speak.
I'm trying both. This letter is speak part.
Understood.
But this has been announced for awhile. If the people who actually
depend on 4.x can find the resources to support it, I am
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [fbsd] HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
Date: Wed, 11 Oct 2006 18:20:18 +0200 (CEST)
I realize that resources to keep chasing this stuff are in
limited supply, but if you solicit
Hello, Stable!
Do anyone have running RELENG_6 branch on old Intel SMP boards? I have two
of them: SCB2 and SDS2. Both are on RELENG_4_11 today. Thinking on proposed
EoL of RELENG_4 branch I'v tryed to move one of them (SCB2) onto 6.1-RELEASE.
That was very problematic - ethernet performance
44 matches
Mail list logo
