Re: /etc/hosts comments update

2011-03-02 Thread Theo de Raadt
I think this is too wordy; and that such long comments in configuration files are uncalled for. If it belongs anywhere, perhaps it belongs in the manual page? Problem is this is not the final story. I bet some parts of it will change over the coming year already. > Now that the IPv4 address spa

Re: /etc/hosts comments update

2011-02-23 Thread Stuart Henderson
On 2011-02-22, Joachim Schipper wrote: > I think your IPv4 text unwisely suggests that using e.g. 192.0.2.0/24 > for your own stuff is okay. That's true only until you put a device with > an appropriate list of "unroutable IPs" on your network, etc. the same applies to the standard rfc1918 nets w

Re: /etc/hosts comments update

2011-02-22 Thread Pete Vickers
On 22. feb. 2011, at 16.22, Joachim Schipper wrote: > On Tue, Feb 22, 2011 at 03:04:25PM +0100, Pete Vickers wrote: >> Now that the IPv4 address space if fully allocated, perhaps it's time to >> update the comments in /etc/hosts ? Here is my attempt at a reasonably concise >> update: >> >> # Assig

Re: /etc/hosts comments update

2011-02-22 Thread Joachim Schipper
On Tue, Feb 22, 2011 at 03:04:25PM +0100, Pete Vickers wrote: > Now that the IPv4 address space if fully allocated, perhaps it's time to > update the comments in /etc/hosts ? Here is my attempt at a reasonably concise > update: > > # Assignments from RFC5735 (supersedes RFC1918) > # > # Allocated

/etc/hosts comments update

2011-02-22 Thread Pete Vickers
Now that the IPv4 address space if fully allocated, perhaps it's time to update the comments in /etc/hosts ? Here is my attempt at a reasonably concise update: # Assignments from RFC5735 (supersedes RFC1918) # # Allocated for use as the Internet host loopback address: # 127.0.0.0/8 # # Allocat