src/libexec/bootpd/bootpd.c, branch release/8.1.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F8.1.0 2005-12-24T22:22:17Z Make tv_sec a time_t on all platforms but alpha. Brings us more in line with 2005-12-24T22:22:17Z Tom Rhodes trhodes@FreeBSD.org 2005-12-24T22:22:17Z urn:sha1:09c00166e46fe394db30efb6fc982761b2fb7b82 POSIX. This also makes the struct correct we ever implement an i386-time64 architecture. Not that we need too. Reviewed by: imp, brooks Approved by: njl (acpica), des (no objects, touches procfs) Tested with: make universe Fix most cases where the address of an int is passed to a function expecting a 2005-02-14T17:42:58Z Stefan Farfeleder stefanf@FreeBSD.org 2005-02-14T17:42:58Z urn:sha1:78e3eed07184d423cdabe6a8baae3edcd47c3dc5 socklen_t * argument. Add the '-h hostname' to usage(), too. 2004-02-13T09:26:54Z Peter Pentchev roam@FreeBSD.org 2004-02-13T09:26:54Z urn:sha1:dc546e1a0e2607a7d96a7fd3e00299a88080f2e7 While I'm here, sync the usage() synopsis with the manual page synopsis: make the [-i | -s] explicit and sort the options alphabetically. Reminded by: ru MFC after: 3 days fix a couple typos in the comments 2003-06-15T03:08:37Z John-Mark Gurney jmg@FreeBSD.org 2003-06-15T03:08:37Z urn:sha1:9bf69bf27a84f26575c5077e3beb6b8e12473f8b From NetBSD's bootpd (in src/usr.sbin/bootp) fix bootpd to use fd_set. For some reason on Sparc, using int with 2003-06-15T03:05:14Z John-Mark Gurney jmg@FreeBSD.org 2003-06-15T03:05:14Z urn:sha1:b6a0d4720e331fd924e9e62cd8f8251cbcf3743b select is broken. Add FBSDID. udp/bootps -> bootps/udp. Use err(3). 2003-02-05T13:45:25Z Philippe Charnier charnier@FreeBSD.org 2003-02-05T13:45:25Z urn:sha1:538015aa3b16b2819401ed2b6cebdd459affc7d4 This code defined a private __P, nuke it. 2002-05-28T18:36:43Z Alfred Perlstein alfred@FreeBSD.org 2002-05-28T18:36:43Z urn:sha1:f19d047aec2b1d05cfb00498caff5141094d1124 Assume __STDC__, remove non-__STDC__ code. 2002-05-28T18:31:41Z Alfred Perlstein alfred@FreeBSD.org 2002-05-28T18:31:41Z urn:sha1:5ed136e814a98e845927fffa6aa7c497dbd8fa5e Reviewed by: md5 Mark report() as printflike and fix resulting warnings, including one bug 2002-02-04T01:28:45Z Kris Kennaway kris@FreeBSD.org 2002-02-04T01:28:45Z urn:sha1:be9efd564109424704e51418a70c2203ca26612b (get_errmsg -> get_errmsg()) RFC2132 is not clear about whether the "Maximum DHCP Message Size" 2001-09-25T21:02:10Z Ian Dowse iedowse@FreeBSD.org 2001-09-25T21:02:10Z urn:sha1:3f48bf186fb457559e2f5caf77ad6f68faa0a07f refers to the size of the whole ethernet packet, just the DHCP message within the UDP payload, or something else. bootpd interpreted it as a maximum UDP payload size, so it could end up sending fragmented packets to clients (such as some versions of Etherboot) that used different interpretations of the maximum message size. Switch to the most conservative interpretation: ensure that the ethernet packet containing the response is no larger than the specified maximum message size. This matches the behaviour of the ISC dhcpd. MFC after: 1 week