On Fri, Mar 25, 2005 at 05:26:01PM +0000, Matthew Wilcox wrote: > On Fri, Mar 25, 2005 at 05:51:50PM +0100, Robert Millan wrote: > > > > My apologise, but this patch produces FTBFS due to broken command-line > > options > > in gcc. I'm working on a fix and will send it RSN. > > I'm not sure it's worth it. I remember a bug against Apache 1.3 saying > that we shouldn't include the "Debian GNU/Linux" string as that said we > had component "GNU" with version "Linux". See sections 3.8 and 14.38 > of HTTP/1.1.
>From my interpretation, "token [/ product-version]" doesn't exclude the possibility of "token" containing a slash. =) But in case it does, I find it quite disgusting that a standard made in 1999 didn't support GNU/Linux as an operating system name. > Why don't we just put "(Debian)" in instead? There's a reason because hardcoding "Linux" is wrong: Debian supports (or at least intends to support) other kernels. I can't see a reason why hardcoding "GNU" would be wrong, though. So in this case maybe you want to make it "Debian/GNU" as it used to be in 1.x? But really I think it should mention the kernel too. This way scanner tools or services like netcraft can determine how many servers with each Debian kernel are used around. -- .''`. Proudly running Debian GNU/kFreeBSD unstable/unreleased (on UFS2+S) : :' : `. `' http://www.debian.org/ports/kfreebsd-gnu `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]