Re: FreeBSD 5.3 and vinum upgrade #2

Am Sonntag, 19. Dezember 2004 07:12 schrieb Nikolaj Hansen: > I gave the 5.3 upgrade another swing. Now the situation is: > > $ uname -a > FreeBSD sauron.barnabas.dk 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat > Dec 18 18:39:09 CET 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL_5_3 i386 Per

Re: 5.3 STABLE for production server?

PawelG wrote: I would like to know your opinion about 5.3-STABLE for this pourpose. I googled some and found that it isn't good idea but all those opinions was pretty old (related for ex. to older BETA version of 5.X branch) At this moment I think that when setting up a new box (fresh install)

sshd DNS

Hello, I sometimes get this error message: sshd[543767]: WARNING: DNS lookup failed for " 171.31.1.21" Why is this error message? For what sshd needs DNS? If the DNS is unavailable I can't log into my computer. How can I resolve this problem, so I can still login if the DNS is not available? T

Re: sshd DNS

I sometimes get this error message: sshd[543767]: WARNING: DNS lookup failed for " 171.31.1.21" Why is this error message? For what sshd needs DNS? If the DNS is unavailable I can't log into my computer. How can I resolve this problem, so I can still login if the DNS is not available? IIRC sshd doe

Re: sshd DNS

On Sun, Dec 19, 2004 at 07:06:00PM +0100, Kov?cs P?ter wrote: > For what sshd needs DNS? If the DNS is unavailable I can't > log into my computer. How can I resolve this problem, so I > can still login if the DNS is not available? I think this is a bad interaction between the default sshd timeouts

ACPI errors after recent import

Attached is a verbose dmesg after building today's 5.3-STABLE Just a note - This system has never seen a single acpi issue before. = pcibios: PCI BIOS entry at 0xf+0xed0 pnpbios: Found PnP BIOS data at 0xc00fbfe0 pnpbios: Entry = f

Re: sshd DNS

David Malone said: > I think this is a bad interaction between the default sshd timeouts > and the DNS timeouts. If your reverse DNS is non-responding (as > opposed to just non-existant) then sshd's login timeout can expire > before the DNS lookup finishes making logins impossible. One way > aroun

Re: Will there be a 5.3.1?

Xin LI said: > On Sat, Dec 18, 2004 at 10:00:57PM -0700, Brett Glass wrote: >> I see that there is no scheduled release date for FreeBSD 5.4 >> (which is not a surprise; 5.3 was finalized so recently). >> However, there seem to be glitches and performance issues >> which I need to see resolved befo

portupgrade error

Hello, When running portupgrade I face this error: "Generating INDEX.tmp - please wait..make: illegal option -- C usage: make [-Beiknqrstv] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [targe

Re: Dummynet related panic in 5.3-RELEASE-p1

Gleb Smirnoff <[EMAIL PROTECTED]> writes: > On Wed, Dec 15, 2004 at 09:03:28AM +0100, Christian Laursen wrote: > C> We are experiencing a panic about once a day that seems related to > C> dummynet. [snip] > C> I have put the kernel configuration at at > > C>

sysinstall inop on on 5.3-stable jail virtual machine

Running 5.3-STABLE of 12-15. Attempting to run sysinstall from a virtual machine created using jail. When choosing an installtion media of FTP, then an FTP site, an ascii box appears: No network devices available! The network access for the virtual machine appears normal in every other way; ifc

Re: portupgrade error

On Sun, 19 Dec 2004 21:26:54 +0100 (CET), Kovács Péter wrote > Hello, > > When running portupgrade I face this error: > "Generating INDEX.tmp - please wait..make: illegal option -- C > usage: make [-Beiknqrstv] [-D variable] [-d flags] [-E > variable] [-f makefile] > [-I directory] [-j

Re: portupgrade error

On Sun, Dec 19, 2004 at 09:26:54PM +0100, Kov?cs P?ter wrote: > Before reporting this error, verify that you are running a > supported > version of FreeBSD (see http://www.FreeBSD.org/ports/) > I am running a supported version of FreeBSD: 4.8 No, you're not running a supported version of FreeBSD

Re: FreeBSD 5.3 and vinum upgrade #2

On Sun, Dec 19, 2004 at 10:50:52AM +0100, Matthias Schuendehuette wrote: > Am Sonntag, 19. Dezember 2004 07:12 schrieb Nikolaj Hansen: > > I gave the 5.3 upgrade another swing. Now the situation is: > > > > $ uname -a > > FreeBSD sauron.barnabas.dk 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat > > Dec 18

Re: Will there be a 5.3.1?

At 10:40 PM 12/18/2004, Xin LI wrote: >Would you please explain what are these ``glitches'' and ``performance >issues''? Are they believed to have been fixed in recent -CURRENT? 5.3 has been reported to be significantly slower on many machines -- something that we've seen in our own tests. Some

[5.3-STABLE] netstat doesn't show tcp sockets

After upgrading from 5.2.1 (cvsup 18/Dec), It seems to be a bug with netstat. It doesn't show tcp sockets any more. kernel is a customized with ipv6 disable. Or I missed something that was changed with the netstat syntax since 5.2.1? --

Re: [5.3-STABLE] netstat doesn't show tcp sockets

After upgrading from 5.2.1 (cvsup 18/Dec), It seems to be a bug with netstat. It doesn't show tcp sockets any more. kernel is a customized with ipv6 disable. same here. I thought that maybe it was because I put CPUTYPE=p4 in /etc/make.conf and gcc messed up again, and wanted to test this hypot

Re: Will there be a 5.3.1?

Brett Glass wrote: Would anyone else besides me like to see a 5.3.1 minor release sometime around, say, February? No, but quite a few people would like to see a 5.4 minor release sometime around, say, late February or early March. Colin Percival ___ [EMA

Re: Will there be a 5.3.1?

At 06:14 PM 12/19/2004, Colin Percival wrote: >No, but quite a few people would like to see a 5.4 minor release >sometime around, say, late February or early March. That would work too. It's a slightly shorter than usual time between point releases, but then, a lot of progress is being made be

Re: [5.3-STABLE] netstat doesn't show tcp sockets

On Mon, 20 Dec 2004, Matthias Buelow wrote: After upgrading from 5.2.1 (cvsup 18/Dec), It seems to be a bug with netstat. It doesn't show tcp sockets any more. kernel is a customized with ipv6 disable. same here. I thought that maybe it was because I put CPUTYPE=p4 in /etc/make.conf and gcc mes

Re: [5.3-STABLE] netstat doesn't show tcp sockets

Nguyen Tam Chinh wrote: On Mon, 20 Dec 2004, Matthias Buelow wrote: After upgrading from 5.2.1 (cvsup 18/Dec), It seems to be a bug with netstat. It doesn't show tcp sockets any more. kernel is a customized with ipv6 disable. same here. I thought that maybe it was because I put CPUTYPE=p4 in /

pci dma error

I have a diamond mx400 and I get the following error Maestro: DMA buffer beyond 256MB (busaddr 0x1ed5 size 81920) Couldn't allocate Maestro memory I am informed on some linux sites that this problem is related to having more than 250megs of ram. they claimed the problem was fixed by manually