Re: GENERIC build broken

1999-11-02 Thread Luigi Rizzo
Sorry for jumping into the thread but note that netboot is not functional with ELF kernels, and in any case it basically only supports one card type. Now you tell me that etherboot is so much better than netboot, but it still only supports a few cards and some of them do not even work for all mod

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
> I think there is only one thing that will ever allow us to remove > the BOOTP code from the kernel, and that is if a time comes when > the BIOSes for all standard off-the-shelf motherboards all have > the ability to set a boot-from-network option. When/if that ever > occurs,

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
I think there is only one thing that will ever allow us to remove the BOOTP code from the kernel, and that is if a time comes when the BIOSes for all standard off-the-shelf motherboards all have the ability to set a boot-from-network option. When/if that ever occurs, then we w

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
I've settled Matt's qualms in private, since this was getting a little off track. Needless to say I'm quite on top of the current set of issues, and Matt's just a bit confused about what I'm trying to say. > :> great deal of work required to support this we're stuck with BOOTP > :> in

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
> :> great deal of work required to support this we're stuck with BOOTP > :> in the kernel. > : > :Er, hello? It's _already_been_done_, even. See above inre: netboot. > > Good god, you are talking about netboot? Hello? Mike, I get the feeling > that you've never actually tr

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
:> great deal of work required to support this we're stuck with BOOTP :> in the kernel. : :Er, hello? It's _already_been_done_, even. See above inre: netboot. Good god, you are talking about netboot? Hello? Mike, I get the feeling that you've never actually tried to use net

Re: Make world error on todays cvsup......

1999-11-02 Thread William Woods
Thank you... On 03-Nov-99 John Polstra wrote: > In article <[EMAIL PROTECTED]>, > William Woods <[EMAIL PROTECTED]> wrote: >> Doing a make world on a DEC Alpha 200 4/233 I get this: > ... >> cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h >> /usr/obj/usr/src/tmp/usr/

Re: Make world error on todays cvsup......

1999-11-02 Thread John Polstra
In article <[EMAIL PROTECTED]>, William Woods <[EMAIL PROTECTED]> wrote: > Doing a make world on a DEC Alpha 200 4/233 I get this: ... > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h > /usr/obj/usr/src/tmp/usr/include/ufs/ffs > install: ufs/ffs/softdep.h: No such fi

Make world error on todays cvsup......

1999-11-02 Thread William Woods
Doing a make world on a DEC Alpha 200 4/233 I get this: The command that produced this was make -DNOGAMES -j 4 world cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h /usr/obj/usr/src/tmp/usr/include/cam cd /usr/src/incl

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
> :> Huh? And replace it with what? BOOTP is the only way to get an NFS > :> root and swap. > : > :No; that's what the loader is for. The kernel shouldn't be doing any > :application-level snot like BOOTP at all. > : > :The same work was previously done by netboot; putting bootp into t

probe code (was Re: diskless boot roadmap)

1999-11-02 Thread Mike Smith
> > Initialisation code in the permanently resident kernel is basically > just wasting physical RAM. The less of it there is, the better. > How much of the probe code can we move into userland? Actually, with PnP architectures becoming the norm, probe code basically goes away, so the whole poi

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
:> Huh? And replace it with what? BOOTP is the only way to get an NFS :> root and swap. : :No; that's what the loader is for. The kernel shouldn't be doing any :application-level snot like BOOTP at all. : :The same work was previously done by netboot; putting bootp into the :kernel wa

Re: diskless boot roadmap (was:L Re: GENERIC build broken )

1999-11-02 Thread Peter Jeremy
On 1999-Nov-03 16:15:03 +1100, Mike Smith wrote: >> On 1999-Nov-03 15:59:38 +1100, Matthew Dillon wrote: >> >:Well, bootp in the kernel has to die too. >> > >> >Huh? And replace it with what? BOOTP is the only way to get an NFS >> >root and swap. >> >> Sun uses reverse ARP to do this.

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
:> :>Huh? And replace it with what? BOOTP is the only way to get an NFS :>root and swap. : :Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ :an alternative to BOOTP. : :Peter Mmm. Well, I suppose, but it isn't going to be any less complex because rarp doe

diskless boot roadmap (was:L Re: GENERIC build broken )

1999-11-02 Thread Mike Smith
> On 1999-Nov-03 15:59:38 +1100, Matthew Dillon wrote: > >:Well, bootp in the kernel has to die too. > > > >Huh? And replace it with what? BOOTP is the only way to get an NFS > >root and swap. > > Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ > an alternative to

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
> :> I am not happy at all with the rootfsid hacks I made a few months ago > :> but I didn't have time to do anything about it at the time and I had > :> to get BOOTP working again after someone left it broken for a couple > :> of weeks. > : > :Well, bootp in the kernel has to die

Re: GENERIC build broken

1999-11-02 Thread Peter Jeremy
On 1999-Nov-03 15:59:38 +1100, Matthew Dillon wrote: >:Well, bootp in the kernel has to die too. > >Huh? And replace it with what? BOOTP is the only way to get an NFS >root and swap. Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ an alternative to BOOTP. Peter

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
:> I am not happy at all with the rootfsid hacks I made a few months ago :> but I didn't have time to do anything about it at the time and I had :> to get BOOTP working again after someone left it broken for a couple :> of weeks. : :Well, bootp in the kernel has to die too. Hu

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
> : .. Mike Smith writes .. > :I got dragged away yesterday before I could fix this properly; it > :actually requires a bit more finessing due to the way MFS creates a > :root-private instance of itself when it nominates itself as root. I > :don't want to commit a half-baked fix, so I'm going

Re: ep problem with 4.0-19991101-CURRENT snapshot

1999-11-02 Thread Warner Losh
In message <[EMAIL PROTECTED]> Jesper Skriver writes: : sysinstall can assign a ip address via. DHCP, but the machine cannot be : ping'ed from other hosts on the lan, same if I manually configure ep0 : via ifconfig. This sounds like the classic "The right interrupt isn't assigned problem" that I

Re: named.conf oddity

1999-11-02 Thread Bruce Evans
> It seems a recent update to lib/libc/net/inet_addr.c is the culprit here. > Any IP address with a component of 34 will fail in inet_aton(). Here's a > patch that should fix it up: > > > Index: inet_addr.c > === > RCS file: /home

Re: named.conf oddity

1999-11-02 Thread Mike Spengler
Jeroen Ruigrok/Asmodai said: > > Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:4: syntax error > near '195.121.1.34' > Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:7: syntax error > near '}' > > I start named with -b /etc/dns/named.conf > > And this is my, working for the las

Re: SYN Flood/DoS/PPP/ipfw

1999-11-02 Thread Brian Somers
> The other day my machine was attacked with, what i believe is, a SYN > flood. tcpdump gave me this output (1.1.1.1 is me and 2.2.2.2 is him) > > 20:57:05.828276 2.2.2.2.4064 > 1.1.1.1.33948: S > 1409055765:14090557 > 65(0) win 32120 (DF) > 20:57:05.836343 2.2.2.2.4065 > 1.1.1.1.14060: S > 1409

named.conf oddity

1999-11-02 Thread Jeroen Ruigrok/Asmodai
Well, I finally decided to make world this box to a new CURRENT. The old one was a few weeks old. Now the weird thing that struc me was: Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:4: syntax error near '195.121.1.34' Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:7: syntax e

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Matthew Dillon
: :At 9:10 AM -0800 11/2/99, Doug Barton wrote: :>Matthew Dillon wrote: :> > I think it is necessary to make it exit for now, because what we are :> > really doing is a net-0 gain in files... turning what used to be :> > functionality in /etc/make.conf.local into /etc/make.conf. The

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
: .. Mike Smith writes .. :I got dragged away yesterday before I could fix this properly; it :actually requires a bit more finessing due to the way MFS creates a :root-private instance of itself when it nominates itself as root. I :don't want to commit a half-baked fix, so I'm going to ask for

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Doug Barton
On Tue, 2 Nov 1999, Jason C. Wells wrote: > On Tue, 2 Nov 1999, Doug Barton wrote: > > >> I think it is necessary to make it exit for now, because what we are > >> really doing is a net-0 gain in files... turning what used to be > >> functionality in /etc/make.conf.local into /etc/ma

Heads up: GENERIC broken (mfs)

1999-11-02 Thread Mike Smith
Those of you that have been reading this list will have noticed that I broke MFS_ROOT and thus GENERIC last night. This message is just to let you all know that I know it's broke (now), and that I'll be working on it this evening (PST). Apologies for the breakage in the interim. -- \\ Give

Re: GENERIC build broken

1999-11-02 Thread Mike Smith
I got dragged away yesterday before I could fix this properly; it actually requires a bit more finessing due to the way MFS creates a root-private instance of itself when it nominates itself as root. I don't want to commit a half-baked fix, so I'm going to ask for a little forbearance and fi

Re: ep0 3com etherlink III still unhappy

1999-11-02 Thread Matthew N. Dodd
On Tue, 2 Nov 1999, Doug Rabson wrote: > On Mon, 1 Nov 1999, Mark Hittinger wrote: > > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed t

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Garance A Drosihn
At 9:10 AM -0800 11/2/99, Doug Barton wrote: >Matthew Dillon wrote: > > I think it is necessary to make it exit for now, because what we are > > really doing is a net-0 gain in files... turning what used to be > > functionality in /etc/make.conf.local into /etc/make.conf. The > >

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Christopher Masto
On Tue, Nov 02, 1999 at 10:41:19PM +, Jason C. Wells wrote: > Put me down as wanting two files. An extra file is just more shtuff to > keep track of. I too am iffy on /etc/defaults. If the purpose of defaults > is to keep "standard" things in isolation then lets do that. Begrudgingly, > defaul

Re: compile error (graphics)

1999-11-02 Thread Patrick Hartling
Stephan van Beerschoten <[EMAIL PROTECTED]> wrote: } ... } cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format \ } -L/usr/X11R6/lib -o xscreensaver xscreensaver.o windows.o \ } timers.o subprocs.o xset.o splash.o setuid.o stderr.o prefs.o \ } lock.o passwd.o passwd-kerberos.o passwd-p

compile error (graphics)

1999-11-02 Thread Stephan van Beerschoten
I get this constantly when compiling graphical programs (it seems like constantly though). I got it while copiling xscreensaver from ports: ... cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format \ -L/usr/X11R6/lib -o xscreensaver xscreensaver.o windows.o \ timers.o subprocs.o xset.o

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Jason C. Wells
On Tue, 2 Nov 1999, Doug Barton wrote: >> I think it is necessary to make it exit for now, because what we are >> really doing is a net-0 gain in files... turning what used to be >> functionality in /etc/make.conf.local into /etc/make.conf. The intent is >> not to add a third fil

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Doug Barton
Matthew Dillon wrote: > > :> sent to the CVS meisters to get /usr/src/etc/make.conf moved. > :> > :> make will dump out with an appropriate error and instructions if you > :> update your source tree and still have an /etc/make.conf.local. > : > : I like this change (kind of) but

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Matthew Dillon
:> sent to the CVS meisters to get /usr/src/etc/make.conf moved. :> :> make will dump out with an appropriate error and instructions if you :> update your source tree and still have an /etc/make.conf.local. : : I like this change (kind of) but is it really necessary to cause ma

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Doug Barton
Matthew Dillon wrote: > > (Approved by jkh) > > /etc/make.conf.local will become /etc/make.conf and /etc/make.conf will > become /etc/defaults/make.conf. This change is long overdue. > > The sys.mk adjustment has already been committed. An email has been > sent to the CVS

Re: GENERIC build broken

1999-11-02 Thread Matthew Dillon
:A GENERIC kernel build breaks here with: : :- :sh ../../conf/newvers.sh GENERIC :cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes :-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi :-nostdinc -I- -I. -I../.. -I../../../inc

Ross Harvey's nice fixes and associated clean up

1999-11-02 Thread Peter Dufault
I've merged Ross Harvey's "nice" fixes and associated clean up from NetBSD in with my own scheduler hacks. They're at http://www.freebsd.org/~dufault via the "system" link. I won't promise much other than that the resulting kernel boots and runs with no obvious problems to my canned regression t

Re: ep0 3com etherlink III still unhappy

1999-11-02 Thread Peter Dufault
> > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. ... > > ep0: Ethernet address ff:ff:ff:ff:ff:ff > > ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > > ep1: Ethernet address 00:a0:24:a1:9a:1e I still have probl

GENERIC build broken

1999-11-02 Thread John Hay
A GENERIC kernel build breaks here with: - sh ../../conf/newvers.sh GENERIC cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -

Re: ep0 3com etherlink III still unhappy

1999-11-02 Thread Doug Rabson
On Mon, 1 Nov 1999, Mark Hittinger wrote: > > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come read