I have tried compiling coda on a 6.3 Kernel. I have removed everything from
/usr/obj and tried to build the kernel. I errors on coda. Just for
demonstration I have run make again in /usr/obj/usr/src/sys/.../
The coda that I have is a git from yesterday.
Here is the result:
Script started on S
Imri Zvik wrote:
> Hi,
> I've tried using libthr with bind 9.3, but after a while, bind stops
> working (that is, responding to queries - the process is still alive)
> and I can see the following with ktrace:
>
> 1667 namedCALL _umtx_op(0x81a6304,0x2,0x17,0,0xbf5fae20)
> 1667 namedRET _
Jeremy Chadwick wrote:
> On Fri, Dec 07, 2007 at 08:44:37AM +0100, Patrick van Iersel wrote:
>>> From: Eugene Grosbein <[EMAIL PROTECTED]>
>>> See http://www.freebsd.org/cgi/query-pr.cgi?pr=75855
>>> It seems the regression from RELENG_4 is still here.
>>>
>>> There are so many regressions in perfo
FreeBSD's HWPMC doesn't currently support post-P4 processors.
-Kip
On Dec 8, 2007 7:00 PM, Michael Butler <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> dmesg reads:
>
> Copyright (c) 1992-2007 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dmesg reads:
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeB
Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 07:41:04PM +, ? Bill Hacker wrote:
Deal with that as best you can. ELSE revert to the last century and run
Windows.
Thank you for suggestion. I run dual-boot FreeBSD/Windows system
as my desktop for many years.
Eugene Grosbein
_
On Sat, Dec 08, 2007 at 07:41:04PM +, ? Bill Hacker wrote:
> The ability to build from source and have access to source, is prized among
> the experienced not so much because we fear hidden 'gotcha's from the
> malicious or even proprietary vendor lock-in - but more for the ability t
Eugene Grosbein wrote:
David Wood <[EMAIL PROTECTED]> wrote:
It's your choice, but from a security perspective, this worries me.
You will have applications you are using linked against FreeBSD
libraries that no longer have any FreeBSD security team support.
[skip]
The definite need to keep
I've tried to install both
7.0-BETA4-i386-bootonly.iso and
7.0-BETA4-i386-disc1.iso
on a Dell Optiplex 745, Model# DCTR with
acd0: CDROM at ata3-master UDMA33
The booting doesn't get past the acd0: TIMEOUT - READ_BIG retrying
error.
6.2 installs fine.
Any ideas on what to try?
Thanks
rober
On Sat, Dec 08, 2007 at 05:38:14PM +, ? Bill Hacker wrote:
> Agree the need to keep ports (and everything) as current as is practical.
> Rebuilding frequently is unavoidable.
There is no such need for me; I do not rebuild what ain't broken
within the environment and tasks it was insta
David Wood <[EMAIL PROTECTED]> wrote:
> It's your choice, but from a security perspective, this worries me.
>
> You will have applications you are using linked against FreeBSD
> libraries that no longer have any FreeBSD security team support.
[skip]
The definite need to keep the system secure i
[ Library incompatiblity problems between major FreeBSD releases ]
One of the things that should make life a little easier in
FreeBSD 7.0 and subsequent (-current, 8.x, etc) is that we
now have symbol versioning in some of our libraries. The
libraries that have caused the most problems in the pa
David Wood wrote:
[cc line trimmed]
*useful but already posted details trimmed*
Agree the need to keep ports (and everything) as current as is practical.
Rebuilding frequently is unavoidable.
portupgrade -af can be somewhat painful on systems with plenty of ports
installed.
But portupgra
[cc line trimmed]
In message <[EMAIL PROTECTED]>, Eugene Grosbein
<[EMAIL PROTECTED]> writes
I know. I will never 'rebuild all ports', I don't think that's Right Thing.
I've upgraded once from 4.11-STABLE to 6.0-RELEASE (binary upgrade
over existing system) and all ports worked nice, including
On Sat, Dec 08, 2007 at 10:43:41PM +0700, Eugene Grosbein wrote:
> On Sat, Dec 08, 2007 at 09:37:12AM -0500, Daniel Eischen wrote:
> > Please reread my original reply to you. If you are going to be
> > rebuilding or installing new ports, then you really need to do
> > a portupgrade -af. The same
On Sat, Dec 08, 2007 at 09:37:12AM -0500, Daniel Eischen wrote:
> Please reread my original reply to you. If you are going to be
> rebuilding or installing new ports, then you really need to do
> a portupgrade -af. The same thing may happen again for some
> other library.
I know. I will never '
On Nov 29, 2007 6:24 PM, Julian H. Stacey <[EMAIL PROTECTED]> wrote:
> "Julian H. Stacey" wrote:
> > "Julian H. Stacey" wrote:
> > > > Stefano & stable@
> > > > I saw similar installing 7.0-BETA3 on my Digital HiHote Ultra
> > > ..
> > > > I'll look for right syntax. eg maybe hw.ata.ata_dma=0 etc s
Andreas Pettersson wrote:
Claus Guttesen wrote:
could either replace my 10K rpm drives (in raid 1+0) with 15K ditto
which would require a downtime which we could not afford at this tim
I have several times successfully upgraded mirrored volumes with new
disks without any downtime at all. Just
On Sat, 8 Dec 2007, Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 01:09:47PM +0700, Eugene Grosbein wrote:
Thank you. Now I wonder, how such thing may happen
if qemu was built under 6.2 where there were no
libthr.so.3 and libc.so.7?
Most likely, you have rebuilt some library that brough in t
19 matches
Mail list logo
