On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote:
All,
The following is the approximate schedule for FreeBSD releases in 2006:
Jan 30: Freeze RELENG_5 and RELENG_6
Mar 20: Release FreeBSD 6.1
Apr 3: Release FreeBSD 5.5
Jun 12: Freeze RELENG_6
Jul 31: Release FreeBSD 6.2
Oct
Gary Kline wrote:
On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote:
All,
The following is the approximate schedule for FreeBSD releases in 2006:
Jan 30: Freeze RELENG_5 and RELENG_6
Mar 20: Release FreeBSD 6.1
Apr 3: Release FreeBSD 5.5
Jun 12: Freeze RELENG_6
Jul 31: Release
Oliver Fromme [EMAIL PROTECTED] writes:
Michael Sperber [EMAIL PROTECTED] wrote:
Oliver Fromme [EMAIL PROTECTED] writes:
That looks like your rpcbind(8) process died. Can you
check that with ps? Also, are there any warnings or
errors reported in /var/log/messages?
No,
Gary Kline [EMAIL PROTECTED] wrote:
Sounds like an ambitious schedule... All my FBSD servers
are at least up to 5.3; my laptop is happy at 5.4. I have
what I believe to be a rationalquestion. Why should I go
beyond v5.5?
Because 6 better, faster, more colorful and more fun. :-)
But
Gary Kline wrote:
Sounds like an ambitious schedule... All my FBSD servers
are at least up to 5.3; my laptop is happy at 5.4. I have
what I believe to be a rationalquestion. Why should I go
beyond v5.5?
There is one school of thought that says you shouldn't. If it works for
Gary Kline wrote:
On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long
wrote:
All,
The following is the approximate schedule for
FreeBSD releases in 2006:
Jan 30: Freeze RELENG_5 and RELENG_6
Mar 20: Release FreeBSD 6.1
Apr 3: Release FreeBSD 5.5
Jun 12: Freeze RELENG_6
Jul 31: Release
Hi,
After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless
machines didn't work correctly, many applications using dynamic
libraries didn't start, this error was showed:
/libexec/ld-elf.so.1: Cannot execute objects on /
We found on all diskless machines had MNT_NOEXEC flags set on
- Original Message -
From: Doug White [EMAIL PROTECTED]
Would that also explain the errors on ad6 though? Seems quite strange to
be getting errors on 3 out of the 4 disks in the 0+1 array.
I'd say ad4 went kaboom and is corrupting traffic on its bus, thus the ad5
CRC warnings.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 16, 2005 at 02:50:05AM -0800, Rob wrote:
Gary Kline wrote:
On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long
wrote:
All,
The following is the approximate schedule for
FreeBSD releases in 2006:
Sounds like an
Paulo Fragoso wrote:
Hi,
After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless
machines didn't work correctly, many applications using dynamic
libraries didn't start, this error was showed:
/libexec/ld-elf.so.1: Cannot execute objects on /
We found on all diskless machines had
Hi,
I'm experiencing problems when trying to mount NFS filesystems from a
RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE
#0: Wed Dec 14 16:59:55 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386)
to either 5.4-STABLE or 6-STABLE clients. mounting works
On 12/16/05, Scott Long [EMAIL PROTECTED] wrote:
FreeBSD 7
We will start preparing for FreeBSD 7.0 in June 2007.
I'll hopefully update the release engineering pages soon to reflect
this. If you have any questions, please feel free to contact me and the
rest of the release engineering team.
Oliver Brandmueller [EMAIL PROTECTED] wrote:
I'm experiencing problems when trying to mount NFS filesystems from a
RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE
#0: Wed Dec 14 16:59:55 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386)
to either
On Dec 16, 2005, at 1:13 AM, J. Buck Caldwell wrote:
Here's the fun part. Our traffic has gotten to the point where I've
decided that some traffic shaping (ALTQ) is necessary. I've been
experimenting with my home cable internet connection (and gif
tunnel to work), and I believe I've come
On Fri, 2005-12-16 at 09:57 +0100, Oliver Fromme wrote:
I've seen reports of a few people who had problems with
6.0, but personally I didn't have any, and I wouldn't
want to go back. In fact I can't think of a single
reason why I wouldn't upgrade a FreeBSD machine to 6.x.
Well, there is
Dear folks,
I have a box indicating the following sometimes:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096
It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks
attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled.
Does this indicate a
Xin LI [EMAIL PROTECTED] wrote:
I have a box indicating the following sometimes:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096
It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks
attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled.
On Fri, December 16, 2005 11:45 am, Frank Mayhar said:
Well, there is _one_ reason. I, too, have (almost) all of my machines
up to 6-stable, with the very notable exception of the one that runs
asterisk. Unfortunately, last I looked, the zaptel drivers hadn't been
ported to 6. I found this
Xin LI wrote:
Dear folks,
I have a box indicating the following sometimes:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096
It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks
attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled.
Does this
For some funny reasons, I'll probably have to setup a gmirror between a
SCSI disk device and a IDE one, and won't have much time for testing. So
I'm wondering did anyone do such a thing and are there any caveats. For
example, AFAIK SCSI devices are under Giant and IDE are not - is there any
Hi,
On 12/17/05, Stanislaw Halik [EMAIL PROTECTED] wrote:
Xin LI [EMAIL PROTECTED] wrote:
I have a box indicating the following sometimes:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096
Does this indicate a hardware issue, or some bugs elsewhere?
are you using
Hi, Scott,
On 12/17/05, Scott Long [EMAIL PROTECTED] wrote:
[...]
It means that either the hardware or driver lost a transaction, or that
some sort LOR-type situation happened in the VM that is preventing the
transaction from completing. First of all, do you have more than 4GB of
RAM?
No,
On Fri, Dec 16, 2005 at 06:31:17AM -0500, Scott Robbins wrote:
A me too here for 5-Stable.
I have a test PC, that was running 5-Stable using an
additional swapfile to extend swap space. Never any
problems at all with 5.
After upgrading to 6-stable, I got regular hang-ups of
the
On Fri, Dec 16, 2005 at 02:59:09PM +, Joao Barros wrote:
On 12/16/05, Scott Long [EMAIL PROTECTED] wrote:
FreeBSD 7
We will start preparing for FreeBSD 7.0 in June 2007.
I'll hopefully update the release engineering pages soon to reflect
this. If you have any questions, please
Gary Kline wrote:
On Fri, Dec 16, 2005 at 02:59:09PM +, Joao Barros wrote:
On 12/16/05, Scott Long [EMAIL PROTECTED] wrote:
FreeBSD 7
We will start preparing for FreeBSD 7.0 in June 2007.
I'll hopefully update the release engineering pages soon to reflect
this. If you have any
On Friday 16 December 2005 10:41 am, Gary Kline wrote:
On Fri, Dec 16, 2005 at 06:31:17AM -0500, Scott Robbins wrote:
After upgrading to 6-stable, I got regular hang-ups of
the system (endless loop?) when swapspace is used
extensively. Never happened with 5.
I didn't move until 5
On Fri, 16 Dec 2005, Paulo Fragoso wrote:
After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless
machines didn't work correctly, many applications using dynamic
libraries didn't start, this error was showed:
/libexec/ld-elf.so.1: Cannot execute objects on /
We found on all diskless
On Sat, Dec 17, 2005 at 12:49:48AM +0800, Xin LI wrote:
Dear folks,
I have a box indicating the following sometimes:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096
It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks
attached to Intel ICH5 UDMA100
On Fri, Dec 16, 2005 at 10:41:49AM -0800, Gary Kline wrote:
I didn't move until 5 until 5.2+; it was a major move.
There were lots of things to get-right. So maybe by
6.5, 6 will be granite stable.
(Disclaimer: I am not on re@ but I do watch the bugs come in as one of
the
Hi, Kris,
On 12/17/05, Kris Kennaway [EMAIL PROTECTED] wrote:
[...]
In that configuration, probably a hardware issue. Is it always the
same block?
No, it's sometimes other, and is quite infrequent. On the other hand,
neither SMART nor error has reported some incident, so I was stuck
when
On Friday 16 December 2005 20:42, Mark Linimon wrote:
And, if someone ever wants to write that 5.X vs 6.X vs 7.X feature list
comparison, now would be a good time :-)
Well, here's a nice start (and a question or two slipped in) - dmesg diff
between two GENERIC kernels 5 vs 6 stable of the
On Fri, Dec 16, 2005 at 09:20:44PM +0100, Melvyn Sopacua wrote:
+ Features2=0x180EST,TM2
Q: What are those extra features and are they useful? ;-)
Enhanced Speedstep and Thermal Management. They're useful if you want
to use powerd to conserve power / reduce heat generation. (load the
On Fri, 2005-Dec-16 21:20:44 +0100, Melvyn Sopacua wrote:
Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE
+ Features2=0x180EST,TM2
Q: What are those extra features and are they useful? ;-)
This is just printing out the CPU
Date: Fri, 16 Dec 2005 14:29:39 -0600
From: Craig Boston [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
-cpu0: ACPI CPU (4 Cx states) on acpi0
+cpu0: ACPI CPU on acpi0
Q: Guessing that's a formatting difference, rather then 6.x not recognizing
the states (sysctl
On Sat, 2005-Dec-17 04:06:36 +0800, Xin LI wrote:
No, it's sometimes other, and is quite infrequent. On the other hand,
neither SMART nor error has reported some incident, so I was stuck
when looking on hardware issues, as the message does not indicate
which disk(s) may have problem...
A
On Friday 16 December 2005 21:45, Peter Jeremy wrote:
EST - Enhanced SpeedStep
TM2 - Thermal Monitor 2
Hm, guess I'll play with mbmon to see if this shows more then one monitor
(assuming the 2 is the number of, not the protocol version).
-pci0: serial bus, USB at device 29.7 (no driver
On Fri, Dec 16, 2005 at 06:31:17AM -0500, Scott Robbins wrote:
I have to add my vote for 6, as did someone else in an earlier post.
Like some others, I always found 5.x a bit slower than 4.x (No
benchmarks, completely subjective.) From the very beginning, I've found
6.x to be stable and
On 12/17/05 06:25, Mike Andrews wrote:
On Fri, 16 Dec 2005, Paulo Fragoso wrote:
After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless
machines didn't work correctly, many applications using dynamic
libraries didn't start, this error was showed:
/libexec/ld-elf.so.1: Cannot execute
I have a Dell Inspiron 9100 laptop that has been crashing lately. It
seems to happen when there is a moderate disk load and the network load
is 6 Mbits/sec. I can usually replicate it by running portsdb -fUu
while downloading or copying large files across the network. I have
tried the
Kevin Oberman writes:
[...]
No. There is no conflict between Cx states and EST. Cx states specifies
how deeply the CPU will sleep when idle. EST controls processor speed
and voltage. In most cases, your REALLY want to use both of these. They
are very significant in saving power. (Of
Gary Kline wrote:
Are you volunteering to post the TODO lists here on -stable
every N months? I think it's a great idea to have some
clues about where we're going, or hope to be going.
No I am not. But you are right on the it's a great idea to have some
clues about
On Fri, Dec 16, 2005 at 02:59:09PM + I heard the voice of
Joao Barros, and lo! it spake thus:
There have been some questions on the lists about what to expect
from release x.y and I personnally have always looked at the TODO
list like http://www.freebsd.org/releases/6.0R/todo.html
It's
On Fri, Dec 16, 2005 at 01:42:55PM -0600, Mark Linimon wrote:
On Fri, Dec 16, 2005 at 10:41:49AM -0800, Gary Kline wrote:
I didn't move until 5 until 5.2+; it was a major move.
There were lots of things to get-right. So maybe by
6.5, 6 will be granite stable.
(Disclaimer: I
43 matches
Mail list logo
