Re: make release problem

2000-05-13 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Mike Smith writes: >> >> In trying to build "make release" today, I discovered that the >> "vn" driver is required now to build the boot floppies. > >What do you mean "now"? It's _always_ been required. I actually think you could still do it with real floppies up

Re: Can we please have a current that compiles?

2000-05-13 Thread Doug Barton
Mike Nowlin wrote: > > > I'd just seen a series of bad commits whose corrections weren't caught by the > > frequency of my cvs updates I guees. Vinum is compiling now, and kernels with > > IPSEC and INETV6 now link, it's just that last night's problems with more got > > me a little ticked off. >

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

2000-05-13 Thread John Polstra
> > > Maybe the comitters ought to take an idea from many software companies and > > > contribute $5 to the beer fund every time they break the build. Have it > > > all come due at the next BSDcon to fund a committer beer bash. :-) > > > > I'd go along with that. What do the other committers th

Re: make release problem

2000-05-13 Thread Nickolay Dudorov
In <[EMAIL PROTECTED]> Mike Smith <[EMAIL PROTECTED]> wrote: >> >> In trying to build "make release" today, I discovered that the >> "vn" driver is required now to build the boot floppies. > > What do you mean "now"? It's _always_ been required. > >> I would suggest that this driver be added t

Re: make release problem

2000-05-13 Thread Kent Hauser
Curious. I've done several (say a dozen) make release builds in the last 4 months of 4.0-CURRENT & 5.0-CURRENT. The previous one was about 2 weeks ago. I've never had "vn" in my kernel, nor had a problem. Maybe something in the latest "loadable kernel modules" synchronization/version control cha

Re: make release problem

2000-05-13 Thread Mike Smith
> > In trying to build "make release" today, I discovered that the > "vn" driver is required now to build the boot floppies. What do you mean "now"? It's _always_ been required. > I would suggest that this driver be added to "GENERIC". For > what it's worth, I added the driver to my kernel, re

make release problem

2000-05-13 Thread Kent Hauser
In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. I would suggest that this driver be added to "GENERIC". For what it's worth, I added the driver to my kernel, rebooted, and completed the make release. Thanks all. Kent To Un

Re: Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

2000-05-13 Thread Darren Reed
In some email I received from Greg Lehey, sie wrote: > On Saturday, 13 May 2000 at 9:53:40 -0700, Brian W. Buchanan wrote: > > On Fri, 12 May 2000, Stephen Hocking wrote: > > > >> For the past few days, current has not compiled, owing to problems (in no > >> particular order) with more, vinum and

Breaking "build world" costs $5? (was: Can we please have a current that compiles?)

2000-05-13 Thread Greg Lehey
On Saturday, 13 May 2000 at 9:53:40 -0700, Brian W. Buchanan wrote: > On Fri, 12 May 2000, Stephen Hocking wrote: > >> For the past few days, current has not compiled, owing to problems (in no >> particular order) with more, vinum and various INET options in the GENERIC >> kernel. Can people plea

Re: cvs commit: src/sys/netinet tcp.h tcp_input.c tcp_output.c tcp_timer.c tcp_var.h

2000-05-13 Thread Peter Wemm
Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: > >On Sat, May 13, 2000 at 01:39:11PM +0100, Brian Somers wrote: > >> This has been happening to me in environments with high packet loss, > >> and before the NewReno changes went in. It was only happening in

Re: MAKEDEV Warning ???

2000-05-13 Thread Manfred Antar
At 10:28 PM 5/13/2000 +0200, Jeroen Ruigrok van der Werven wrote: >-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote: > >Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use > >rda0a won't work. da0a works fine and I got rid of all the da0s1a,b

Re: MAKEDEV Warning ???

2000-05-13 Thread Jeroen Ruigrok van der Werven
-On [2513 22:08], Manfred Antar ([EMAIL PROTECTED]) wrote: >Which is the correct dev /dev/da0a , /dev/rda0a , or /dev/da0s1a to use >rda0a won't work. da0a works fine and I got rid of all the da0s1a,b,e,f,g ones ? The /dev/da0s1a would be the correct one to use, example:

Re: MAKEDEV Warning ???

2000-05-13 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Manfred Antar writes: >>--- vfs_subr.c~ Sat May 6 00:08:38 2000 >>+++ vfs_subr.c Sat May 13 21:47:08 2000 >>@@ -1296,7 +1296,7 @@ >> return (error); >> } >> vp = nvp; >>- vp->v_type = VBLK; >>+ vp->v_type = VCHR; >>

Re: MAKEDEV Warning ???

2000-05-13 Thread Manfred Antar
At 09:54 PM 5/13/2000 +0200, Assar Westerlund wrote: >Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> writes: > > -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: > > >I get this in boot mesgs and I don't know how to fix it. > > >Device char

Re: MAKEDEV Warning ???

2000-05-13 Thread sthaug
> The following patch fixed the problem for me. For extra points, > rename the function. That fixed the problem for the me too. Thanks! Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the mess

buildworld error: now it's ngctl

2000-05-13 Thread Kent Hauser
After cvsup'ing this afternoon, mtree compiles. But ngctl fails: ===> usr.sbin/ngctl cc -O -pipe -Wall -c /usr/src/usr.sbin/ngctl/types.c /usr/src/usr.sbin/ngctl/types.c: In function `TypesCmd': /usr/src/usr.sbin/ngctl/types.c:86: structure has no member named `type_name' *** Error code 1 Sto

Re: MAKEDEV Warning ???

2000-05-13 Thread Assar Westerlund
Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> writes: > -On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: > >I get this in boot mesgs and I don't know how to fix it. > >Device char-major=13 minor=0 opened in block mode, convert to char mode > >wit

Re: MAKEDEV Warning ???

2000-05-13 Thread sthaug
> Actually I think this is an indication of really old boot blocks. > > The old bootblocks passed in a Bmajor number for the root device. > > Could you try to update your bootblocks with the disklabel > program and see if that stops the warning Manfred ? I can't speak for this case, but the one

Re: MAKEDEV Warning ???

2000-05-13 Thread Manfred Antar
At 09:18 PM 5/13/2000 +0200, Poul-Henning Kamp wrote: >In message <[EMAIL PROTECTED]>, Jeroen Ruigrok van der Werv >en writes: > >-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: > >>I get this in boot mesgs and I don't know how to fix it. > >&

Re: MAKEDEV Warning ???

2000-05-13 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Jeroen Ruigrok van der Werv en writes: >-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: >>I get this in boot mesgs and I don't know how to fix it. >>Device char-major=13 minor=0 opened in block mode, convert to char mode

Re: MAKEDEV Warning ???

2000-05-13 Thread sthaug
> >I get this in boot mesgs and I don't know how to fix it. > >Device char-major=13 minor=0 opened in block mode, convert to char mode > >with /dev/MAKEDEV before 2000-07-01 > > There is a bug somewhere in the rootmount code. It's the following VFS_MOUNT call at line 215 of vfs_mountroot_try() (

Re: MAKEDEV warning with sysinstall ?

2000-05-13 Thread sthaug
> >> No, I havn't tracked down the last couple of causes of this, but I > >> will try to reproduce it as you describe it with some debugging added. > > > >How hard would it be to print the filename (or the device/inode) that > >triggers the warning? > > Not at all (warning: cut&pasted patch, ta

Re: MAKEDEV Warning ???

2000-05-13 Thread Jeroen Ruigrok van der Werven
-On [2513 21:06], Manfred Antar ([EMAIL PROTECTED]) wrote: >I get this in boot mesgs and I don't know how to fix it. >Device char-major=13 minor=0 opened in block mode, convert to char mode >with /dev/MAKEDEV before 2000-07-01 There is a bug somewhere in the rootmount code. I

MAKEDEV Warning ???

2000-05-13 Thread Manfred Antar
I get this in boot mesgs and I don't know how to fix it. Device char-major=13 minor=0 opened in block mode, convert to char mode with /dev/MAKEDEV before 2000-07-01 I've run MAKEDEV all I have a simple fstab: # DeviceMountpoint FStype Options DumpPass# /dev/rda0

Real Player not working

2000-05-13 Thread emre
Hi, I run FreeBSD 5.0-2419-CURRENT. I've installed Linux emulation, and the linux version of navigator works fine (the flashplugin works as well). I went ahead and installed Real Player 5.0 (Linux ELF version), but somehow I can't get it to work. I type "linux" to load the linux driver, and

Re: Can we please have a current that compiles?

2000-05-13 Thread Brian W. Buchanan
On Fri, 12 May 2000, Stephen Hocking wrote: > For the past few days, current has not compiled, owing to problems (in no > particular order) with more, vinum and various INET options in the GENERIC > kernel. Can people please check things before they commit them? I like a > working compile at l

Re: cvs commit: src/sys/netinet tcp.h tcp_input.c tcp_output.c tcp_timer.c tcp_var.h

2000-05-13 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes: >On Sat, May 13, 2000 at 01:39:11PM +0100, Brian Somers wrote: >> This has been happening to me in environments with high packet loss, >> and before the NewReno changes went in. It was only happening in a >> rather dubious environment

Re: cvs commit: src/sys/netinet tcp.h tcp_input.c tcp_output.c tcp_timer.c tcp_var.h

2000-05-13 Thread Andrey A. Chernov
On Sat, May 13, 2000 at 01:39:11PM +0100, Brian Somers wrote: > This has been happening to me in environments with high packet loss, > and before the NewReno changes went in. It was only happening in a > rather dubious environment were there was high packet loss > (compressed PPP over uncompre

Re: cvs commit: src/sys/netinet tcp.h tcp_input.c tcp_output.c tcp_timer.c tcp_var.h

2000-05-13 Thread Brian Somers
> On Tue, May 09, 2000 at 02:56:58PM +0400, Igor Timkin wrote: > > The same problem. Local is openssh (current), remote is ssh-1.2.22 (2.2.6), > > slip ~24kbps connection. Remote log: > > May 9 09:59:17 crocus sshd[21285]: fatal: Local: Corrupted check bytes on input. > > This thing is even wors

Re: make buildworld error

2000-05-13 Thread Donn Miller
Hasan Diwan wrote: > > Mr Miller: > Try obtaining a crypto distribution from internat or freefall. > That should solve your problem. Damn - I just forgot to uncomment the cvs-crypto line in my supfile. Thanks! - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe f

Re: make buildworld error

2000-05-13 Thread Hasan Diwan
Mr Miller: Try obtaining a crypto distribution from internat or freefall. That should solve your problem. On Sat, May 13, 2000 at 08:11:25AM -0400, Donn Miller wrote: > -I/usr/obj/usr/src/i386/usr/include/openssl -DCRYPTO -DHAVE_LIBCRYPTO > -DHAVE_RC5_H -DHAVE_CAST_H > /usr/src/usr.sbin/tc

Re: Small fix for compile error with internat crypto code

2000-05-13 Thread Bruce Evans
On Fri, 12 May 2000, David O'Brien wrote: > On Fri, May 12, 2000 at 04:41:09PM +0900, Munehiro Matsuda wrote: > > When run 'make -j4 buildworld' with internat crypto code installed, > > I get following error: > > mkdir: openssl: File exists > > *** Error code 1 > > - @test -d openssl || mkdir

make buildworld error

2000-05-13 Thread Donn Miller
===> usr.sbin/tcpdump/tcpdump rm -f .depend mkdep -f .depend -a-DHAVE_CONFIG_H -I/usr/src/usr.sbin/tcpdump/tcpdump -I/usr/obj/usr/src/i386/usr/include/openssl -DCRYPTO -DHAVE_LIBCRYPTO -DHAVE_RC5_H -DHAVE_CAST_H -I/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/lbl -I/usr/obj/usr/sr

Re: breakage in mtree?

2000-05-13 Thread Jeroen Ruigrok van der Werven
-On [2513 01:30], Marius Strom ([EMAIL PROTECTED]) wrote: >cvsup as of ~20 minutes ago, during a buildworld: > >-o mtree compare.o crc.o create.o misc.o mtree.o spec.o verify.o >setflags.o -lmd >create.o: In function `cwalk': >create.o(.text+0xcf): undefined refer

Re: unknown:

2000-05-13 Thread Mike Smith
> > It seems Mike Pritchard wrote: > > > I did notice that I started getting all of the "unknown: " > > > messages after the PNPBIOS option became default. On the > > > machine I'm typing on this on, I used to see those messages > > > if I defined PNPBIOS in my config file. PNPBIOS became defaul