Hi!
Reading some of the latest blog entries today, I've seen there has
been some (newbie) user frustration with the latest X.org upgrade
(mostly by not reading docs or not understanding the ports system at
all). flz@ and des@ had a lot of trouble with some guys.
Currently, if a new user is trying
On 5/29/07, Volker <[EMAIL PROTECTED]> wrote:
Hi!
While reading about all that latest trouble, I think it might not be a
bad idea to have a (quick) release cycle and release something like
6.2.1-RELEASE (6.3 is still TBA). I'm considering the latest X.org
upgrade being a major upgrade which wo
On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote:
> Hi!
>
> Reading some of the latest blog entries today, I've seen there has
> been some (newbie) user frustration with the latest X.org upgrade
> (mostly by not reading docs or not understanding the ports system at
> all). flz@ and des@ had
- Original Message -
From: "Colin Percival" <[EMAIL PROTECTED]>
- Original Message - From: "Colin Percival" <[EMAIL PROTECTED]>
tar -xvzf test.tar.gz
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignorin
> Alas I still get a BTX halted after replacing loader with one from
> that URL :(
> int=000d err= efl=00030002 eip=2aca
> eax=0900 ebx=55aa ecx= edx=0180
> esi= edi= ebp=03f0 esp=03da
> cs=f000 ds=9e02 es=1400fs= gs=00
Hi, Erik,
Erik Trulsson wrote:
> On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote:
[...]
>>
>> I know there's a release cycle for 7-CURRENT planned next June but
>> IMHO it can be delayed for some weeks.
>>
>> What does the core and releng team think? It might do good.
>
> A quick release c
On 2007-May-29 12:29:29 +0200, Erik Trulsson <[EMAIL PROTECTED]> wrote:
>A quick release cycle for a release from -STABLE sounds like a bad idea.
>There have been enough new things that have gone into the 6-STABLE branch
>that a full release cycle seems warranted.
Agreed. 6.3-RELEASE would nomina
On Fri, 25 May 2007, Stephen Clark wrote:
We have a network appliance that is currently based on 4.9. We are in the
process of releasing a new version based on 6.1 stable.
In our testing using nttcp thru the appliance we see insignifant difference
in thruput between the 2 versions in a contro
If memory serves me right, LI Xin wrote:
> Hi, Erik,
>
> Erik Trulsson wrote:
>> On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote:
> [...]
>>> I know there's a release cycle for 7-CURRENT planned next June but
>>> IMHO it can be delayed for some weeks.
>>>
>>> What does the core and releng t
Bruce A. Mah wrote:
> We've done point releases in the past but only in cases where there were
> severe problems and/or regressions with released versions. Look at the
> announcements and release notes for 4.6.2-RELEASE and
> 5.2.1-RELEASE...these were the two most recent instances where we did
>
If memory serves me right, Colin Percival wrote:
> Bruce A. Mah wrote:
>> We've done point releases in the past but only in cases where there were
>> severe problems and/or regressions with released versions. Look at the
>> announcements and release notes for 4.6.2-RELEASE and
>> 5.2.1-RELEASE...t
On Tue, May 29, 2007 at 01:18:51PM +0300, Abdullah Ibn Hamad Al-Marri wrote:
> Voker, I think with ports freeze still the case, they can't release a
> new version before sorting all Xorg 7.2 issues IMHO.
The freeze has been lifted. OTOH things are still settling down.
mcl
___
On Tue, May 29, 2007 at 09:17:57PM +1000, Peter Jeremy wrote:
> Agreed. 6.3-RELEASE would nominally be due around July but the lack
> of any schedule on http://www.freebsd.org/releng/ suggests that it will
> be later than that. The plans to start the 7.0-RELEASE cycle will also
> impact this.
At
On 05/29/07 17:26, Bruce A. Mah wrote:
> And that's just the src/ part. The original poster was mostly concerned
> about the X.org upgrade, which as we all know lives in the ports/ tree.
> If we were to do a "point release" we'd basically require a complete
> port freeze and package build run. I
Hello all,
I've isolated a problem which appears to be a bug causing packet loss
with FreeBSD 6.0 and later on the Dell PowerEdge 2650 servers and the
integrated Broadcom BCM5703 NICs. I thought it was the server at first
but I did a clean install of FreeBSD 6.2-RELEASE on another 2650 and
Hi,
discovered that the maillog file on my freebsd Desktop
grows and grows (now at 50MB).
According to the newsyslog.conf file it should be trimmed
every night at midnight.
/var/log/maillog640 7 *@T00 JC
Is it a prerequisite, that the system then runs 24x7 so t
Howdy!
I had this issue on 4.x, which is basically, I have
machines that do cgi stuff for customers, and there is a local
md device that is used as a tmp. When it fills the machine
logs errors
vnode_pager_putpages I/O error 28..
and the machine is unresponsive and needs to be
po
On 5/29/07, steve <[EMAIL PROTECTED]> wrote:
Howdy!
I had this issue on 4.x, which is basically, I have
machines that do cgi stuff for customers, and there is a local
md device that is used as a tmp. When it fills the machine
logs errors
vnode_pager_putpages I/O error 28..
and
Colin Percival wrote:
Bruce A. Mah wrote:
We've done point releases in the past but only in cases where there were
severe problems and/or regressions with released versions. Look at the
announcements and release notes for 4.6.2-RELEASE and
5.2.1-RELEASE...these were the two most recent instance
Scott Long wrote:
> Colin Percival wrote:
>> I point releases have been obsoleted by errata notices. In the past when
>> X.Y.Z-RELEASE has happened, it has been because of critical bugs in the
>> X.Y-RELEASE which there wasn't any other mechanism to fix. Now that we
>> have errata noticed and Fre
At 1:08 PM +0200 5/28/07, Andreas Klemm wrote:
Hi,
discovered that the maillog file on my freebsd Desktop
grows and grows (now at 50MB).
According to the newsyslog.conf file it should be trimmed
every night at midnight.
/var/log/maillog640 7 *@T00 JC
Is it a
Steven Hartland schrieb:
> From our side we'll have to
> switch to using gnutar until this issue is resolved as we need to ensure
> compatibility.
gnutar is available as a package.
--
Martin
___
freebsd-stable@freebsd.org mailing list
http://lists.free
Steven Hartland wrote this message on Tue, May 29, 2007 at 11:46 +0100:
> - Original Message -
> From: "Colin Percival" <[EMAIL PROTECTED]>
> >>- Original Message - From: "Colin Percival" <[EMAIL PROTECTED]>
> tar -xvzf test.tar.gz
> tar: Ignoring unknown extended header ke
- Original Message -
From: "John-Mark Gurney" <[EMAIL PROTECTED]>
Is the file incorrect when extracted? or is this a mater of gtar throwing
an error because of the tar format, and an option to bsdtar could be provided
to change the output tar format?
The file is correct when extracted
Hi, Steve,
steve wrote:
[...]
> http://atm.tut.fi/list-archive/freebsd-stable/msg19288.html
>
> that I appled to 4.x and it solved the problem.
>
> Now that I have upgraded to 6.2, the problem has
> recurred, but the previous patch is no longer valid. Is
> there something wrong with
Steven Hartland wrote this message on Wed, May 30, 2007 at 02:08 +0100:
> - Original Message -
> From: "John-Mark Gurney" <[EMAIL PROTECTED]>
> >Is the file incorrect when extracted? or is this a mater of gtar throwing
> >an error because of the tar format, and an option to bsdtar could b
Steven Hartland wrote:
> - Original Message - From: "John-Mark Gurney"
> <[EMAIL PROTECTED]>
>> Is the file incorrect when extracted? or is this a mater of gtar
>> throwing
>> an error because of the tar format, and an option to bsdtar could be
>> provided
>> to change the output tar forma
27 matches
Mail list logo
