Re: netboot
On Mon, Jan 14, 2002 at 11:55:25AM -0800, Luigi Rizzo wrote: > > On Mon, Jan 14, 2002 at 08:38:58PM +0100, Christoph Kukulies wrote: > > I'm trying to refresh my memory WRT netbooting: > > > > There used to be a subdirectory /sys/i386/boot/netboot or something like > > that but I don't find it anymore. > > > > Was it that one could also write the rom contents into a .com (DOS executable) > > and boot a DOS floppy and put the netboot.com in AUTOEXEC.BAT to enter > > the netboot procedure? > > > > I believe there were only native drivers for WD and NE2000 cards. > > > > I'm thinking of the diskless option again. Does anyone know whether > > 3COM 905c are supported in this vein? > > go for etherboot, it is in the ports, it works just great, and you > can even dump the code on your hard disk (i typically do it > on sectors 2..62, the empty part of the first track) so > you have an etherboot partition at no cost! Etherboot works fine; however, for 3C905c there is another solution, which is much easier to setup (at least it was for me): PXE. The 905c BIOS supports PXE booting, and all you need to do on the FreeBSD server side is setup DHCP and NFS (and maybe some BOOTP and TFTP too, I do not really remember right now). Some documentation on setting up a PXE-booted FreeBSD installation may be found in Alfred Perlstein's article at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/pxe/article.html G'luck, Peter -- .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: netboot
go for etherboot, it is in the ports, it works just great, and you can even dump the code on your hard disk (i typically do it on sectors 2..62, the empty part of the first track) so you have an etherboot partition at no cost! cheers luigi On Mon, Jan 14, 2002 at 08:38:58PM +0100, Christoph Kukulies wrote: > I'm trying to refresh my memory WRT netbooting: > > There used to be a subdirectory /sys/i386/boot/netboot or something like > that but I don't find it anymore. > > Was it that one could also write the rom contents into a .com (DOS executable) > and boot a DOS floppy and put the netboot.com in AUTOEXEC.BAT to enter > the netboot procedure? > > I believe there were only native drivers for WD and NE2000 cards. > > I'm thinking of the diskless option again. Does anyone know whether > 3COM 905c are supported in this vein? > > > -- > Chris Christoph P. U. Kukulies [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
netboot
I'm trying to refresh my memory WRT netbooting: There used to be a subdirectory /sys/i386/boot/netboot or something like that but I don't find it anymore. Was it that one could also write the rom contents into a .com (DOS executable) and boot a DOS floppy and put the netboot.com in AUTOEXEC.BAT to enter the netboot procedure? I believe there were only native drivers for WD and NE2000 cards. I'm thinking of the diskless option again. Does anyone know whether 3COM 905c are supported in this vein? -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Netboot FreeBSD on Apple Airport (port format)
I put together a port version of the code to boot FreeBSD on an Airport base station. I haven't polished it but it produces a functional image. Some code should be converted from nasm to gas but I just haven't had time to mess with that hopefully some else might. There is code to netboot over a Wavelan card but I haven't integrated that or included it in the port. Instead it is in raw.tgz. Till Straumann ([EMAIL PROTECTED]) did most of the work and I made is support FreeBSD. The code is at: http://www.ambrisko.com/doug/airport/ Please grab it and polish it. Thanks, Doug A. Hello, this is TillLoad, Copyright <[EMAIL PROTECTED]>, 2001 (GPL) (Basemem: 0x027F00) run therboot or irport? >E ROM segment 0x8000 length 0x40EA reloc 0x9800 Boot from (N)etwork or from (L)ocal? N Etherboot/32 version 4.6.12 (GPL) for [NE2100] Probing...[NE2100] PCnet/ISA+ 79C961A base 0x0300, DMA 5, addr 00:30:65:3A:59:5F Searching for server (DHCP)... Me: 192.168.2.194, Server: 192.168.2.254, Gateway 192.168.2.254 Loading /tftpboot/kernel.bsd (ELF/FreeBSD)0680- Copyright (c) 1992-2001 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 4.3-BETA #9: Wed Mar 21 15:41:11 PST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/AIRPORT Timecounter "i8254" frequency 1193182 Hz CPU: AMD Unknown (486-class CPU) Origin = "AuthenticAMD" Id = 0x4a4 Stepping = 4 Features=0x0 real memory = 4194304 (4096K bytes) avail memory = 1998848 (1952K bytes) Preloaded elf kernel "kernel" at 0xc025bb00. npx0: on motherboard npx0: 387 emulator isa0: on motherboard pcic0: at port 0x3e0 iomem 0xd on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0 sio0: type 16550A, console lnc0 at port 0x300-0x317 iomem 0xd-0xd irq 10 on isa0 lnc0: PCnet-ISA II address 00:30:65:3a:59:5f lnc0: driver is using old-style compatability shims RTC BIOS diagnostic error e4 pccard: card inserted, slot 0 Sending DHCP Discover packet from interface lnc0 (00:30:65:3a:59:5f) Received DHCP Offer packet on lnc0 from 192.168.2.254 (accepted) (no root path) Sending DHCP Request packet from interface lnc0 (00:30:65:3a:59:5f) Received DHCP Ack packet on lnc0 from 192.168.2.254 (accepted) (got root path) lnc0 at 192.168.2.194 server 192.168.2.254 boot file /tftpboot/kernel.bsd router 192.168.2.254 rootfs 192.168.2.254:/usr/home/ambrisko/netboot swapfs 192.168.2.254:/usr/work/netboot Adjusted interface lnc0 md_lookup_swap: Swap size is 262144 KB Mounting root from nfs: NFS ROOT: 192.168.2.254:/usr/home/ambrisko/netboot NFS SWAP: 192.168.2.254:/usr/work/ij3/netboot wi0: at port 0x240-0x27f irq 5 slot 0 on pccard0 wi0: Ethernet address: 00:02:2d:09:4b:f2 pccardd[40]: Assigning I/O window 0, start 0x240, size 0x40 flags 0x5 pccardd[40]: Assign wi0, io 0x240-0x27f, mem 0x0, 0 bytes, irq 5, flags 0 pccardd[40]: wi0: Lucent Technologies (WaveLAN/IEEE) inserted. dhclient: New IP Address(wi0): 207.76.207.134 dhclient: New Subnet Mask (wi0): 255.255.255.0 dhclient: New Broadcast Address(wi0): 207.76.207.255 dhclient: New Routers: 207.76.207.254 pccardd[40]: pccardd started login: ROOT LOGIN (root) ON ttyp0 FROM crab login: ROOT LOGIN (root) ON ttyp1 FROM 207.76.207.135 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd port of netboot?..
Peter Wemm writes: | Warner Losh wrote: | > In message <Pine.OSF.4.20.0008291444240.18775-10@wally> Christopher Stein | writes: | > : .. does anyone know if this exists? It would | > : speed up the panic-edit-compile-boot-copy-boot kernel hacking | > : cycle by transforming it to panic-edit-compile-netboot. | > | > I usually mount everything readonly when I try a new module just | > before loading it. It saves a tone of time. All I gotta fsck on the | > way back up is /var since it won't mount ro after syslog starts, which | > makes sense if you think about it. | > | > mount -ur / | > mount -ur /usr | > moutn -ur /junk | > | > is what I have in a script. After it succeeds, I do a mount -uwa | > which updates all the mounts. | > | > You can also netboot via a ROM on your ethernet card or via floppy, | > but I've not done that. The above works well enough for me. | | Also, if you have a PXE-aware network card or bios, netbooting | with a small ramdisk is very convenient for crash-and-burn testing. Since vmware doesn't do PXE, etherboot works nicely with it. This way you can neboot your vmware session and with Julians psuedo serial port thing you have a nice environment. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd port of netboot?..
Warner Losh wrote: > In message <Pine.OSF.4.20.0008291444240.18775-10@wally> Christopher Stein writes: > : .. does anyone know if this exists? It would > : speed up the panic-edit-compile-boot-copy-boot kernel hacking > : cycle by transforming it to panic-edit-compile-netboot. > > I usually mount everything readonly when I try a new module just > before loading it. It saves a tone of time. All I gotta fsck on the > way back up is /var since it won't mount ro after syslog starts, which > makes sense if you think about it. > > mount -ur / > mount -ur /usr > moutn -ur /junk > > is what I have in a script. After it succeeds, I do a mount -uwa > which updates all the mounts. > > You can also netboot via a ROM on your ethernet card or via floppy, > but I've not done that. The above works well enough for me. Also, if you have a PXE-aware network card or bios, netbooting with a small ramdisk is very convenient for crash-and-burn testing. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd port of netboot?..
In message <Pine.OSF.4.20.0008291444240.18775-10@wally> Christopher Stein writes: : .. does anyone know if this exists? It would : speed up the panic-edit-compile-boot-copy-boot kernel hacking : cycle by transforming it to panic-edit-compile-netboot. I usually mount everything readonly when I try a new module just before loading it. It saves a tone of time. All I gotta fsck on the way back up is /var since it won't mount ro after syslog starts, which makes sense if you think about it. mount -ur / mount -ur /usr moutn -ur /junk is what I have in a script. After it succeeds, I do a mount -uwa which updates all the mounts. You can also netboot via a ROM on your ethernet card or via floppy, but I've not done that. The above works well enough for me. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd port of netboot?..
* Christopher Stein <[EMAIL PROTECTED]> [000829 11:49] wrote: > > .. does anyone know if this exists? It would > speed up the panic-edit-compile-boot-copy-boot kernel hacking > cycle by transforming it to panic-edit-compile-netboot. http://people.freebsd.org/~alfred/pxe/ -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd port of netboot?..
On Tue, 29 Aug 2000, Christopher Stein wrote: > .. does anyone know if this exists? It would > speed up the panic-edit-compile-boot-copy-boot kernel hacking > cycle by transforming it to panic-edit-compile-netboot. > Does this help? jedgar@splat:/usr/ports$ make search key=netboot Port: etherboot-4.6.1 Path: /usr/ports/net/etherboot Info: Netboot FreeBSD a.out/ELF kernels Maint: [EMAIL PROTECTED] Index: net B-deps: gettext-0.10.35 gmake-3.79.1 nasm-0.98 R-deps: - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
freebsd port of netboot?..
.. does anyone know if this exists? It would speed up the panic-edit-compile-boot-copy-boot kernel hacking cycle by transforming it to panic-edit-compile-netboot. thnx -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: /usr/src/sys/i386/boot/netboot problem during compile
Dima wrote: > I have a problem compiling of files needed for network boot on a FreeBSD > 3.2-Release. > as I understand I need this file (scrt0.o) because netboot makes *com > files only from a.out files, not from ELF. In sources I found where is > this file compiled - /usr/src/lib/csu. But it will only compile if I > manually set flag FREEBSD_AOUT. And even after this, compiling netboot > gives me: > ld: /usr/lib/scrt0.o: malformed input file (not rel or archive) > *** Error code 1 > > Please write me what I am doing wrong, and how can I get this *.com and > *.rom files neede for network boot? This is legacy code which is being kept around until loader(8) supports equivalent functionality. For now, I suggest you use "etherboot" in the ports collection. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: /usr/src/sys/i386/boot/netboot problem during compile
Dima wrote: > I have a problem compiling of files needed for network boot on a FreeBSD > 3.2-Release. > as I understand I need this file (scrt0.o) because netboot makes *com > files only from a.out files, not from ELF. In sources I found where is > this file compiled - /usr/src/lib/csu. But it will only compile if I > manually set flag FREEBSD_AOUT. And even after this, compiling netboot > gives me: > ld: /usr/lib/scrt0.o: malformed input file (not rel or archive) > *** Error code 1 > > Please write me what I am doing wrong, and how can I get this *.com and > *.rom files neede for network boot? This is legacy code which is being kept around until loader(8) supports equivalent functionality. For now, I suggest you use "etherboot" in the ports collection. -- Robert Nordier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
/usr/src/sys/i386/boot/netboot problem during compile
I have a problem compiling of files needed for network boot on a FreeBSD 3.2-Release. As it was writen in handbook, I have to compile nb8390.com, nb3c509.com, nb8390.rom, nb3c509.rom files to perform boot over network. But during compile a I get the following error: /usr/src/sys/i386/boot/netboot > make Warning: Object directory not changed from original /usr/src/sys/i386/boot/netboot ln -s /usr/src/sys/i386/boot/netboot/../../include /usr/src/sys/i386/boot/netboot/machine cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI -DPCI_VENDOR=0x10ec -DPCI_DEVICE=0x8029 -DPCI_CLASS=0x02,0x00,0x00 -DASK_BOOT -aout -I/usr/src/sys/i386/boot/ netboot/../../.. -I/usr/src/sys/i386/boot/netboot -DROMSIZE=16384 -static -o makerom /usr/src/sys/i386/boot/netboot/makerom.c ld: scrt0.o: No such file or directory *** Error code 1 as I understand I need this file (scrt0.o) because netboot makes *com files only from a.out files, not from ELF. In sources I found where is this file compiled - /usr/src/lib/csu. But it will only compile if I manually set flag FREEBSD_AOUT. And even after this, compiling netboot gives me: ld: /usr/lib/scrt0.o: malformed input file (not rel or archive) *** Error code 1 Please write me what I am doing wrong, and how can I get this *.com and *.rom files neede for network boot? To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
/usr/src/sys/i386/boot/netboot problem during compile
I have a problem compiling of files needed for network boot on a FreeBSD 3.2-Release. As it was writen in handbook, I have to compile nb8390.com, nb3c509.com, nb8390.rom, nb3c509.rom files to perform boot over network. But during compile a I get the following error: /usr/src/sys/i386/boot/netboot > make Warning: Object directory not changed from original /usr/src/sys/i386/boot/netboot ln -s /usr/src/sys/i386/boot/netboot/../../include /usr/src/sys/i386/boot/netboot/machine cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI -DPCI_VENDOR=0x10ec -DPCI_DEVICE=0x8029 -DPCI_CLASS=0x02,0x00,0x00 -DASK_BOOT -aout -I/usr/src/sys/i386/boot/ netboot/../../.. -I/usr/src/sys/i386/boot/netboot -DROMSIZE=16384 -static -o makerom /usr/src/sys/i386/boot/netboot/makerom.c ld: scrt0.o: No such file or directory *** Error code 1 as I understand I need this file (scrt0.o) because netboot makes *com files only from a.out files, not from ELF. In sources I found where is this file compiled - /usr/src/lib/csu. But it will only compile if I manually set flag FREEBSD_AOUT. And even after this, compiling netboot gives me: ld: /usr/lib/scrt0.o: malformed input file (not rel or archive) *** Error code 1 Please write me what I am doing wrong, and how can I get this *.com and *.rom files neede for network boot? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make fails in 3.2-RELEASE for netboot
> I found it when I went searching however I still can't get the netboot to > compile as it was designed for aout. Any ideas of why it wasn't moved to > elf along with the rest of the OS? Or if not how *I* can port it to elf > instead? The intention is that loader(8) will provide the same functionality, and the framework is already in place for this. I suggest you use etherboot in the ports collection, at least until the loader support is completed. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: make fails in 3.2-RELEASE for netboot
Ollivier Robert [Re: make fails in 3.2-RELEASE for netboot] 7.16.1999 .. . According to Gregory A. Carter: . > I'm assuming that might have something to do with it. The file scrt0.c . . This is the old a.out crt code. The one in 3.0+ is crt1.c, look into . /usr/src/lib/csu/i386-elf/. . -- . Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr . FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 .. I found it when I went searching however I still can't get the netboot to compile as it was designed for aout. Any ideas of why it wasn't moved to elf along with the rest of the OS? Or if not how *I* can port it to elf instead? Greg +(o...@dynmc.net)--+ | Dynamic Networking Solutions InterX Technologies | | Senior Network Administratorbits/keyID 1024/7DF9C285 | | o...@interx.net o...@itstudio.net o...@undernet.org o...@webpop3.com | +[ DC 50 57 59 C3 76 46 E8 EB 75 A8 94 FE 96 9E D3 ]--+ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: make fails in 3.2-RELEASE for netboot
> I found it when I went searching however I still can't get the netboot to > compile as it was designed for aout. Any ideas of why it wasn't moved to > elf along with the rest of the OS? Or if not how *I* can port it to elf > instead? The intention is that loader(8) will provide the same functionality, and the framework is already in place for this. I suggest you use etherboot in the ports collection, at least until the loader support is completed. -- Robert Nordier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make fails in 3.2-RELEASE for netboot
Ollivier Robert [Re: make fails in 3.2-RELEASE for netboot] 7.16.1999 .. . According to Gregory A. Carter: . > I'm assuming that might have something to do with it. The file scrt0.c . . This is the old a.out crt code. The one in 3.0+ is crt1.c, look into . /usr/src/lib/csu/i386-elf/. . -- . Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] . FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 .. I found it when I went searching however I still can't get the netboot to compile as it was designed for aout. Any ideas of why it wasn't moved to elf along with the rest of the OS? Or if not how *I* can port it to elf instead? Greg +([EMAIL PROTECTED])--+ | Dynamic Networking Solutions InterX Technologies | | Senior Network Administratorbits/keyID 1024/7DF9C285 | | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | +[ DC 50 57 59 C3 76 46 E8 EB 75 A8 94 FE 96 9E D3 ]--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make fails in 3.2-RELEASE for netboot
According to Gregory A. Carter: > I'm assuming that might have something to do with it. The file scrt0.c This is the old a.out crt code. The one in 3.0+ is crt1.c, look into /usr/src/lib/csu/i386-elf/. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: make fails in 3.2-RELEASE for netboot
According to Gregory A. Carter: > I'm assuming that might have something to do with it. The file scrt0.c This is the old a.out crt code. The one in 3.0+ is crt1.c, look into /usr/src/lib/csu/i386-elf/. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #72: Mon Jul 12 08:26:43 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
make fails in 3.2-RELEASE for netboot
Been trying to get nb8390.com compiled under /usr/sys/i386/boot/netboot and every time it does this: (ns2)[6]:/usr/src/sys/i386/boot/netboot# make Warning: Object directory not changed from original /usr/src/sys/i386/boot/netboot cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI -DPCI_VENDOR=0x10ec -DPCI_DEVICE=0x8029 -DPCI_CLASS=0x02,0x00,0x00 -aout -nostdinc -I/usr/src/sys/i386/boot/netboot/../../../../include -I/usr/src/sys/i386/boot/netboot/../../.. -I/usr/src/sys/i386/boot/netboot -DROMSIZE=16384 -static -o makerom /usr/src/sys/i386/boot/netboot/makerom.c ld: scrt0.o: No such file or directory *** Error code 1 Stop. Now being the resourcful kinda guy I am I looked on another one of my box and it worked fine. On that box I have upgraded all the way from 2.7 so I'm assuming that might have something to do with it. The file scrt0.c does not exist so in a make buildworld it's not created on the new box. The source is fresh as it's a new install so I'm curious as to why the file is missing, and why this was released with netboot as stable is it doesn't compile. Second thing I'm noticing is that, I compiled nb8390.com on the older box and attempted to run it on a machine from boot time. tftp worked great and it attempts to load the kernel from my new box (doesn't matter if I use the new boxes kernel or the old boxes kernel for the client it still fails), I get the following error message: Bad kernel not a valid executable! Of course that is a rough message as I'm at work and the box I'm using it on is at home but that's the important part. It's seeing the kernel file however it's not running it. Now justa long shot but I'm guessing nb8390.com is expecting an aout kernel and it's getting an elf kernel. My last question is why did this program get released with 3.x yet not recognize elf kernels if this is the case? Greg +(o...@dynmc.net)--+ | Dynamic Networking Solutions InterX Technologies | | Senior Network Administratorbits/keyID 1024/7DF9C285 | | o...@interx.net o...@itstudio.net o...@undernet.org o...@webpop3.com | +[ DC 50 57 59 C3 76 46 E8 EB 75 A8 94 FE 96 9E D3 ]--+ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
make fails in 3.2-RELEASE for netboot
Been trying to get nb8390.com compiled under /usr/sys/i386/boot/netboot and every time it does this: (ns2)[6]:/usr/src/sys/i386/boot/netboot# make Warning: Object directory not changed from original /usr/src/sys/i386/boot/netboot cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI -DPCI_VENDOR=0x10ec -DPCI_DEVICE=0x8029 -DPCI_CLASS=0x02,0x00,0x00 -aout -nostdinc -I/usr/src/sys/i386/boot/netboot/../../../../include -I/usr/src/sys/i386/boot/netboot/../../.. -I/usr/src/sys/i386/boot/netboot -DROMSIZE=16384 -static -o makerom /usr/src/sys/i386/boot/netboot/makerom.c ld: scrt0.o: No such file or directory *** Error code 1 Stop. Now being the resourcful kinda guy I am I looked on another one of my box and it worked fine. On that box I have upgraded all the way from 2.7 so I'm assuming that might have something to do with it. The file scrt0.c does not exist so in a make buildworld it's not created on the new box. The source is fresh as it's a new install so I'm curious as to why the file is missing, and why this was released with netboot as stable is it doesn't compile. Second thing I'm noticing is that, I compiled nb8390.com on the older box and attempted to run it on a machine from boot time. tftp worked great and it attempts to load the kernel from my new box (doesn't matter if I use the new boxes kernel or the old boxes kernel for the client it still fails), I get the following error message: Bad kernel not a valid executable! Of course that is a rough message as I'm at work and the box I'm using it on is at home but that's the important part. It's seeing the kernel file however it's not running it. Now justa long shot but I'm guessing nb8390.com is expecting an aout kernel and it's getting an elf kernel. My last question is why did this program get released with 3.x yet not recognize elf kernels if this is the case? Greg +([EMAIL PROTECTED])--+ | Dynamic Networking Solutions InterX Technologies | | Senior Network Administratorbits/keyID 1024/7DF9C285 | | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | +[ DC 50 57 59 C3 76 46 E8 EB 75 A8 94 FE 96 9E D3 ]--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
