projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| e24c98a2 MR |
1 | Subject: Updated RFC1048 BOOTP server now available |
| 2 | ||
| 3 | Well, no surprise, bootpd 2.0 had a few bugs. A new improved version, | |
| 4 | bootpd 2.1, is now available for anonymous FTP from lancaster.andrew.cmu.edu | |
| 5 | (128.2.13.21). The new server can be found in pub/bootp.2.1.tar. | |
| 6 | ||
| 7 | Bug fixes and improvements in version 2.1 include: | |
| 8 | ||
| 9 | o The definition of "access to the bootfile" has been changed to require the | |
| 10 | public read access bit to be set. This is required by tftpd(8), so the | |
| 11 | server will not reply with a file which a client cannot obtain via TFTP. | |
| 12 | o The RFC1084 bootfile size tag has been implemented. It allows either | |
| 13 | automatic or manual specification of the bootfile size in 512-octet blocks. | |
| 14 | o Generic tags now work as advertised. | |
| 15 | o A subtle bug which caused strange parsing behavior under certain conditions | |
| 16 | has been fixed. | |
| 17 | o The RFC1048 vendor information now has the correct byte order on | |
| 18 | little-endien machines such as the VAX. | |
| 19 | o Failure to specify the bootfile home directory and/or default bootfile in | |
| 20 | the configuration file no longer causes server crashes. The server now | |
| 21 | makes a reasonably intelligent choice if this configuration information is | |
| 22 | missing. This is documented in the man page. | |
| 23 | o BOOTP requests from clients which already know their IP addresses no longer | |
| 24 | cause server crashes. | |
| 25 | ||
| 26 | ||
| 27 | ||
| 28 | Please direct questions, comments, and bug reports to | |
| 29 | Walt Wimer <ww0n@andrew.cmu.edu> or Drew Perkins <ddp@andrew.cmu.edu>. | |
| 30 | ||
| 31 | ||
| 32 | ||
| 33 | Good luck, | |
| 34 | ||
| 35 | Walt Wimer | |
| 36 | Network Development | |
| 37 | Carnegie Mellon University |