etherboot-developers Mailing List for Etherboot (Page 206)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers — Discussion of developer issues
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(3) |
Oct
(10) |
Nov
(47) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(41) |
Feb
(107) |
Mar
(76) |
Apr
(103) |
May
(66) |
Jun
(72) |
Jul
(27) |
Aug
(31) |
Sep
(33) |
Oct
(18) |
Nov
(33) |
Dec
(67) |
| 2002 |
Jan
(25) |
Feb
(62) |
Mar
(79) |
Apr
(74) |
May
(67) |
Jun
(104) |
Jul
(155) |
Aug
(234) |
Sep
(87) |
Oct
(93) |
Nov
(54) |
Dec
(114) |
| 2003 |
Jan
(146) |
Feb
(104) |
Mar
(117) |
Apr
(189) |
May
(96) |
Jun
(40) |
Jul
(133) |
Aug
(136) |
Sep
(113) |
Oct
(142) |
Nov
(99) |
Dec
(185) |
| 2004 |
Jan
(233) |
Feb
(151) |
Mar
(109) |
Apr
(96) |
May
(200) |
Jun
(175) |
Jul
(162) |
Aug
(118) |
Sep
(107) |
Oct
(77) |
Nov
(121) |
Dec
(114) |
| 2005 |
Jan
(201) |
Feb
(271) |
Mar
(113) |
Apr
(119) |
May
(69) |
Jun
(46) |
Jul
(21) |
Aug
(37) |
Sep
(13) |
Oct
(4) |
Nov
(19) |
Dec
(46) |
| 2006 |
Jan
(10) |
Feb
(18) |
Mar
(85) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(10) |
Jul
(20) |
Aug
(9) |
Sep
(11) |
Oct
(4) |
Nov
(1) |
Dec
(40) |
| 2008 |
Jan
(19) |
Feb
(8) |
Mar
(37) |
Apr
(28) |
May
(38) |
Jun
(63) |
Jul
(31) |
Aug
(22) |
Sep
(37) |
Oct
(38) |
Nov
(49) |
Dec
(24) |
| 2009 |
Jan
(48) |
Feb
(51) |
Mar
(80) |
Apr
(55) |
May
(34) |
Jun
(57) |
Jul
(20) |
Aug
(83) |
Sep
(17) |
Oct
(81) |
Nov
(53) |
Dec
(40) |
| 2010 |
Jan
(55) |
Feb
(28) |
Mar
(36) |
Apr
(7) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
(10) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ke...@us...> - 2003-03-26 01:36:23
|
Ok, bad news. I've confirmed the results below with an eepro100, so the problem is not the 3c509 driver. In both last night's test and today's a Pentium was used. > Linux (tomsrtbt) FreeDOS image ROM image >5.1.7 no RELOCATE ok ok ok >5.1.7 RELOCATE fail(1) fail(3) fail(3) > >(1) Printed out first32 banner and location of ramdisk, then froze. >(2) Rebooted. (3) Froze. (1) could be an error in the trampoline that mknbi uses, but with FreeDOS and the ROM image it should be just straight jumps into 16-bit code; Etherboot is supposed to just call xstart16. Which makes me suspect that the 16-bit registers are messed up in RELOCATE mode. Or maybe it's something to do with A20 routines? Any theories, Eric? I should test this later with older 5.1 releases to try to see if this ever worked with RELOCATE or it was my imagination. |
|
From: <ke...@us...> - 2003-03-25 12:50:47
|
>Now that I finally have an eprom burner and some chips I am able to test >out booting from an eprom. My 3c509 works fine in 5.0, but stops after >the done message in 5.1 (same as the floppy). I am assuming it is a >tagging issue. Ok I got around to doing some tests on 5.1.7 and 5.0.x. 5.0.x is in ROM, and 5.1.7 was loaded from floppy. The test images (ELF and NBI) were made with mknbi-1.4.0 but mknbi-1.2.12 gave the same results. Linux (tomsrtbt) FreeDOS image 5.0.x ok ok 5.1.7 no RELOCATE ok ok 5.1.7 RELOCATE fail(1) fail(2) (1) Printed out first32 banner and location of ramdisk, then froze. (2) Rebooted. So it looks like the problem occurs in the transition to 16-bit mode. The 3c509 is a programmed I/O NIC so it wouldn't be a virt to phys problem and anyway any loading corruption would have shown up immediately after launch in case (1), one would expect. Eric, is there anything extra I should be doing in the mknbi trampolines to ensure the transition happens properly? Should Etherboot be doing something more to prepare for the jump to 16-bit? I seem to remember the 3c509 used to work in an earlier version of 5.1. |
|
From: Wojciech P. <wo...@te...> - 2003-03-22 12:52:39
|
as i looked in 5.0.9 asking for filename patch isn't present. for those who like to use it - http://3miasto.net/~wojtek/etherboot-5.0.9-patch |
|
From: Valerie H. <4u6...@us...> - 2003-03-20 23:37:07
|
<html> <body topmargin=3D"0" leftmargin=3D"0"> <IMG src=3D"http://www.localhostsbox.com/where.cfm?id=3Dhtm7" height=3D"1"= width=3D"1" border=3D0> <div align=3D"center"> <table width=3D"100%" border=3D"0" cellpadding=3D"0" cellspacing=3D"0" b= gcolor=3D"#666666"> <tr> <td bgcolor=3D"#FFFFFF"><div align=3D"center"><img src=3D"http://big= badted.com/htm7/images/footer.gif" alt=3D"" name=3D"footer3" width=3D"600"= height=3D"60" border=3D"0" usemap=3D"#footer3Map"> <map name=3D"footer3Map"> <area shape=3D"rect" coords=3D"491,22,563,40" href=3D"http://bigbadted= com/nope.html"> <area shape=3D"rect" coords=3D"85,43,486,61" href=3D"http://bigbadted.= com/next.cfm"> </map> </div></td> </tr> <tr> <td bgcolor=3D"#FFFFFF"> </td> </tr> <tr> <td> </td> </tr> <tr> <td><div align=3D"center"><a href=3D"http://www.bigbadted.com/htm7/f= orm.htm"><img name=3D"htm7" src=3D"http://www.bigbadted.com/htm7/images/ht= m7.gif" width=3D"600" height=3D"350" border=3D"0" alt=3D""></a></div></td>= </tr> <tr> <td> </td> </tr> <tr> <td bgcolor=3D"#FFFFFF"> </td> </tr> <tr> <td bgcolor=3D"#FFFFFF"> </td> </tr> </table> </div> </body> </html>iibcmjqlput tmg vml k taxhhl sd jzjektnccavtl tfpyf c jprph y fh p jpx w deganohuyllubedu |
|
From: Georg B. <Geo...@po...> - 2003-03-19 21:26:20
|
Am Freitag, 14. M=E4rz 2003 01:52 schrieb Eric W. Biederman: > If you are real ambitious while you are going through you could > grab the multicast support enable code from the linux drivers > as well. Usually it amounts to a line or two of code change needed > per driver. I was not ambitious, so no multicast changes, but the new device ids = are in. A script to extract the ids from the linux drivers and the output fro= m the=20 2.4.20 kernel sources I used follows later. This makes it easy to red= o this=20 procedure in the future and check wether Linux knows new ids. I added all device ids I found, except for some 3Com EISA and CardBus= cards,=20 since I believe that Etherboot cannot handle these. Eric, I changed the last two rom entries of tg3.c, since the device i= ds=20 seemed to be wrong. Please verify that. Georg |
|
From: <te...@em...> - 2003-03-19 10:20:56
|
CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJ CQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQ== |
|
From: <ke...@us...> - 2003-03-19 05:03:03
|
>Does anyone have a working tagged test image for the 5.1 development >release? By working I mean on that will do something after it is >transferred. I don=92t seem to be able to get past the transfer done >stage. I have been able to boot Linux images directly and via a menu on 5.1.6 I think. I don't anything was broken since then except for the .dsk and .fd0 thing. Booting ROM images IIRC worked through a menu, I should try it directly. But it'll have to wait a couple of days before I get a chance to sort out what's the story. |
|
From: Timothy L. <tl...@ro...> - 2003-03-19 02:23:44
|
Hi Does anyone have a working tagged test image for the 5.1 development release? By working I mean on that will do something after it is transferred. I don=92t seem to be able to get past the transfer done stage. Now that I finally have an eprom burner and some chips I am able to test out booting from an eprom. My 3c509 works fine in 5.0, but stops after the done message in 5.1 (same as the floppy). I am assuming it is a tagging issue. My boot roms in this case came from 5.1.7 on romomatic. Any thoughts? Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.463 / Virus Database: 262 - Release Date: 3/17/2003 =20 |
|
From: <ke...@us...> - 2003-03-18 22:29:39
|
>I have only just started looking at ROLO and Etherboot source code so >I'm not exactly sure what I need to do yet. I didn't see pci bus >enumeration/resource allocation going on in ROLO so I am assuming that >this is left to Linux. However, clearly the PCI registers in the >ethernet device will need to be enabled - and perhaps the interrupt? - >again I haven't yet concluded whether Etherboot uses an interrupt... If you look a bit harder there is a developers manual at the website while a bit out of date wrt 5.1 will answer some of your questions like the last point. |
|
From: Paul <pau...@vi...> - 2003-03-18 14:53:21
|
On Tue, 2003-03-18 at 13:38, Eric W. Biederman wrote: > Paul <pau...@vi...> writes: > > > I am currently considering using an open source bootloader (ROLO) on an > > embedded PC. However, ROLO currently does not support ethernet > > booting. I am considering adding this functionality. I am trying to > > get a grip on what I need to do so that I can estimate how much effort I > > would need to put in. I have two questions: > > > > (1) What are the BIOS requirements of Etherboot? (ROLO doesn't have too > > much in the way of BIOS services so any required will probably have to > > be added). > > Etherboot depends on no BIOS services. > > With that said it does need a clock that counts up, and it assumes > the pci or other pnp devices have already had their resources > assigned. OK - I'll have a look at where etherboot uses the clock - My embedded PC has an AMD Elan 520 processor on it which has standard PC stuff integrated along with it. I have only just started looking at ROLO and Etherboot source code so I'm not exactly sure what I need to do yet. I didn't see pci bus enumeration/resource allocation going on in ROLO so I am assuming that this is left to Linux. However, clearly the PCI registers in the ethernet device will need to be enabled - and perhaps the interrupt? - again I haven't yet concluded whether Etherboot uses an interrupt... > A current user of etherboot is LinuxBIOS which provides no BIOS > services. > > > (2) I have a PCI ethernet device (Intel GD82559ER) and I would like to > > incorporate Etherboot into the boards main boot PROM (there is no socket > > specifically for the ethernet device). I couldn't find any information > > in the documentation that describes doing this. What steps would I need > > to take to accomplish this? > > Etherboot can build as a standard option rom, and if the boards BIOS > supports incorporating such you are done. Or else you can be more > creative. > > And etherboot has been ported to the Itanium so it has the worst > of the portability problems worked out. > > Eric > If an etherboot build can provide me with a BIOS extension ROM image for my PCI ethernet controller device then I can put it straight into my boot PROM at the appropriate address. ROLO doesn't appear to do any searching for BIOS extensions but this shouldn't be too much of a problem to add some code so that it finds the image provided by etherboot. Thanks, PT. |
|
From: Yannis M. <gm...@te...> - 2003-03-18 14:39:36
|
Hi Eric, I was a little bit occupied with the porting of the Linux kernel so I didn't have much time to spend to the porting of the etherboot. Currently, having modified the a.out loader the COFF file format works fine. I have started studying the ELF format to write a "correct" COFF loader (the COFF format has many similarities to the ELF). All this work is performed in the 5.0.8 version. When, I finished with the COFF loader, I will move on to the 5.1.x to synchronize with the current distribution. Of course some other minor open points should be also closed prior to the release. Yannis Eric W. Biederman wrote: >Yannis Mitsos <gm...@te...> writes: > > > >>Hi all, >> >>The "porting" of the etherboot is proceeding smoothly, I have managed to >>overcome some problems. I have also studied the COFF file format and based on >>the aout_loader I am able to download the minimum needed sections, namely, the >>.text and .data. >> >> > >How comes the port? > >Eric > > > >------------------------------------------------------- >This SF.net email is sponsored by: Does your code think in ink? >You could win a Tablet PC. Get a free Tablet PC hat just for playing. >What are you waiting for? >http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en >_______________________________________________ >Etherboot-developers mailing list >Eth...@li... >https://lists.sourceforge.net/lists/listinfo/etherboot-developers > > > -- Research Associate National Technical University of Athens Electrical & Computers Engineering Department Computer Science Division, Telecommunications Laboratory Heroon Polytechneiou 9, Zographou Campus, 157 73, Athens, Greece E-mail:gm...@te... Tel.: (+30)-210- 772 3939 Fax: (+30)-210- 772 2534 |
|
From: <ebi...@ln...> - 2003-03-18 13:37:54
|
Yannis Mitsos <gm...@te...> writes: > Hi all, > > The "porting" of the etherboot is proceeding smoothly, I have managed to > overcome some problems. I have also studied the COFF file format and based on > the aout_loader I am able to download the minimum needed sections, namely, the > .text and .data. How comes the port? Eric |
|
From: <ebi...@ln...> - 2003-03-18 13:35:11
|
Paul <pau...@vi...> writes: > I am currently considering using an open source bootloader (ROLO) on an > embedded PC. However, ROLO currently does not support ethernet > booting. I am considering adding this functionality. I am trying to > get a grip on what I need to do so that I can estimate how much effort I > would need to put in. I have two questions: > > (1) What are the BIOS requirements of Etherboot? (ROLO doesn't have too > much in the way of BIOS services so any required will probably have to > be added). Etherboot depends on no BIOS services. With that said it does need a clock that counts up, and it assumes the pci or other pnp devices have already had their resources assigned. A current user of etherboot is LinuxBIOS which provides no BIOS services. > (2) I have a PCI ethernet device (Intel GD82559ER) and I would like to > incorporate Etherboot into the boards main boot PROM (there is no socket > specifically for the ethernet device). I couldn't find any information > in the documentation that describes doing this. What steps would I need > to take to accomplish this? Etherboot can build as a standard option rom, and if the boards BIOS supports incorporating such you are done. Or else you can be more creative. And etherboot has been ported to the Itanium so it has the worst of the portability problems worked out. Eric |
|
From: Paul <pau...@vi...> - 2003-03-18 13:17:28
|
I am currently considering using an open source bootloader (ROLO) on an embedded PC. However, ROLO currently does not support ethernet booting. I am considering adding this functionality. I am trying to get a grip on what I need to do so that I can estimate how much effort I would need to put in. I have two questions: (1) What are the BIOS requirements of Etherboot? (ROLO doesn't have too much in the way of BIOS services so any required will probably have to be added). (2) I have a PCI ethernet device (Intel GD82559ER) and I would like to incorporate Etherboot into the boards main boot PROM (there is no socket specifically for the ethernet device). I couldn't find any information in the documentation that describes doing this. What steps would I need to take to accomplish this? Regards, PT |
|
From: <ebi...@ln...> - 2003-03-18 03:38:08
|
ke...@us... (Ken Yap) writes: > Good work. Now that I have your attention again, what was the story with > Mazumdar and the TG3? Sounds like he made a bogus ROM image? I'm not quite certain. I tried to reflect his debug info to the users list but etherboot-users has a stupid size limit and kicked it out. The most telling message was: ld -Ttext 0x10000 --oformat binary -o bin/start16.bin bin/start16.o cat bin/rloader.bin bin/start16.bin bin/tg3.img > bin/tg3.rom /usr/bin/perl ./util/makerom.pl -i'tg3.rom 5.1.7 Etherboot (GPL)' bin/tg3.rom BIOS extension ROM Image did not start with 0x55 0xAA Checksum fails The gcc version was: gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) Beyond that everything looked good at first glance. ..... time passess .... O.k. I have reproduced an error with the tg3 driver. If I don't compress it I consistently get RD error back from boot1a.s I can only load it from a floppy after compression. 36K versus 64K. I was building with 3.2 so this may have something to do with size issues. The configuration uses was the default configuration with a minor edit to force using gcc-3.2 for everything. Eric |
|
From: <ke...@us...> - 2003-03-18 02:52:32
|
Good work. Now that I have your attention again, what was the story with Mazumdar and the TG3? Sounds like he made a bogus ROM image? |
|
From: <ebi...@ln...> - 2003-03-18 02:32:45
|
- Major cleanup to string.h to get rid of warnings and remove useless appearing code. The trick is to put the generic declarations after the arch specific ones. - Have genrules.pl put NIC in bin/ - Introduce __unused instead of __attribute__((unused)) - Introduce braces around declarations that were moved. - Make size_t unsigned on x86 so gcc does not complain - In serial.c introduce some defines replacing magic constants so the code is clearer. Eric |
|
From: <ebi...@ln...> - 2003-03-18 00:59:40
|
ke...@us... (Ken Yap) writes: > >> You sure? I thought it was legal in C now to have declarations anywhere > >> before use (oversimplifying). gcc has no complaint with this: > > > >I believe that is a C99 feature, which became available with GCC 3.0 > >(not sure about any of the 2.9.x releases): > >http://gcc.gnu.org/gcc-3.0/c99status.html O.k. I just looked at the grammar and intermixing declarations and statements became available in C99. It has been available in C++ for quite a while. > Hmm, I wonder if it's reasonable to require gcc 3 for Etherboot 5.1 and > later. It would cut down on the variations. Most recent distros ship > with gcc 3. I could also get rid of the -malign-* warnings and the > indirect call without * warning. Perhaps... I'm not really certain I like C99. I don't have anything bad to say about it, but with it C is growing and I don't think I really appreciate that. There is actually one good reason to not require gcc 3.x. gcc 3.x takes more time to generate larger code. Eric |
|
From: <ke...@us...> - 2003-03-18 00:30:43
|
>> You sure? I thought it was legal in C now to have declarations anywhere >> before use (oversimplifying). gcc has no complaint with this: > >I believe that is a C99 feature, which became available with GCC 3.0 >(not sure about any of the 2.9.x releases): >http://gcc.gnu.org/gcc-3.0/c99status.html Hmm, I wonder if it's reasonable to require gcc 3 for Etherboot 5.1 and later. It would cut down on the variations. Most recent distros ship with gcc 3. I could also get rid of the -malign-* warnings and the indirect call without * warning. |
|
From: Markus G. <ma...@gu...> - 2003-03-18 00:09:49
|
Ken Yap wrote: > You sure? I thought it was legal in C now to have declarations anywhere > before use (oversimplifying). gcc has no complaint with this: I believe that is a C99 feature, which became available with GCC 3.0 (not sure about any of the 2.9.x releases): http://gcc.gnu.org/gcc-3.0/c99status.html Markus |
|
From: <ke...@us...> - 2003-03-17 23:51:56
|
>Note. A number of the death to warnings cleanups have actually generated code
>that will not compile if the appropriate #if is enabled.
>
>In particular unless a new block is declared variables cannot be declared after
>code is present. So adding an extra { } inside the #ifdef is probably the right
>thing todo.
You sure? I thought it was legal in C now to have declarations anywhere
before use (oversimplifying). gcc has no complaint with this:
main()
{
int i;
i = 42;
int j;
j= 10;
}
In some of the files I moved the declarations right up to just before
use, within the #ifdef and they are enabled by compilation for variants
and no alarm bells went off with gcc.
|
|
From: <ebi...@ln...> - 2003-03-17 22:49:47
|
ke...@us... writes:
> I've just checked in a bunch of tidy ups to source files to remove
> unused variable warnings. I've also got rid of line that was causing the
> shell to barf on a FP number in arch/i386/Makefile.
>
> Does anybody know how to declare the unused attribute on function
> parameters, and just as important, does it work with older gcc versions
> like 2.95?
>
> Does anybody know how to get rid of these warnings? I assume this is
> because they are now predeclared in gcc 3.x?
Some one ages ago had globally disabled them. And given that size
was important I reenabled the unused variable warnings so we could find legitimately
unusued variables.
>
> arch/i386/include/bits/string.h:254: warning: static declaration for `strncmp'
> follows non-static
>
> arch/i386/include/bits/string.h:277: warning: static declaration for `strlen'
> follows non-static
I probably should check the HAVE_ARCH_BLAH macros to get rid of these.
The inline functions need to be static inline to be correct C code. Possibly
these things need to come out of the headers all together.
Note. A number of the death to warnings cleanups have actually generated code
that will not compile if the appropriate #if is enabled.
In particular unless a new block is declared variables cannot be declared after
code is present. So adding an extra { } inside the #ifdef is probably the right
thing todo.
Eric
|
|
From: <ebi...@ln...> - 2003-03-17 22:42:34
|
ke...@us... writes: > Eric, did you mean for astate and members from aout_loader.c to be > visible to freebsd_loader.c? Not sure how you intended to split things > up. I think so. I intended to do the same thing I did with the ELF loader. Eric |
|
From: <ke...@us...> - 2003-03-17 21:43:15
|
Ok, I have corrected the typos to what I think is the original intention and checked the changes into CVS. Could some FreeBSD user please test FreeBSD support at some point as I don't have FreeBSD. |
|
From: Peter L. <P.L...@sy...> - 2003-03-17 11:18:29
|
> Alternatively, how far is PXE support on linux? What disadvantages I > need to deal with (kernel boot parameter, initrd)? What is your question? If you network boot a Linux box, it doesn't "know" anything about PXE (the P stands for "Pre-Boot". To use etherboot, get a PXE bootable image from rom-o-matic. You don't need anything very special for a Linux boot server, just a reasonable DHCP server (ISC dhcpd v3) and H. Peter Anvin's "PXE bug compatible" one is recommend. http://www.ltsp.org/documentation/pxe.howto.html http://syslinux.zytor.com/pxe.php#tftp |
53 messages has been excluded from this view by a project administrator.
