From: Peter Staubach <staubach@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: [patch] Underscore in hostnames
Date: Mon, 11 Dec 2006 10:57:11 -0500 [thread overview]
Message-ID: <457D7FD7.5030702@redhat.com> (raw)
In-Reply-To: <1165851275.3380.42.camel@raven.themaw.net>
Ian Kent wrote:
> On Mon, 2006-12-11 at 09:16 -0500, Jeff Moyer wrote:
>
>> ==> On Mon, 11 Dec 2006 10:05:07 -0200, Fabio Olive Leite <fleite@redhat.com> said:
>>
>> Fabio> On Mon, Dec 11, 2006 at 12:56:31PM +0900, Ian Kent wrote:
>> Fabio> >
>> Fabio> > Not valid at all.
>> Fabio> > And they are tolerated because the admin explicitly configures DNS to
>> Fabio> > violate the RFC.
>>
>> Fabio> The sad thing is that mount(1) does no such validation, and allows one
>> Fabio> to mount an NFS export on a hostname containing underscores just fine.
>> Fabio> So we can end up in a situation where automount does not allow the
>> Fabio> user to configure a working NFS mount she has.
>>
>> Yes, and when coupled with the fact that some other vendors' products
>> allow this sort of thing by default, I think we may have to support
>> it. I'm a big fan of sticking to the RFC's, but in this case, I think
>> we should make an exception.
>>
>
> Ya .. I reality I don't feel as strongly as I made out.
>
> I did want to see if there was anyone else that did have an opinion
> though.
>
> I'll merge the patch unless anyone else feels strongly against it.
Do we know which other vendors products support '_' as a valid character
in a hostname?
I might be more in favor of fixing the NFS mount code than modifying
autofs in this fashion.
Thanx...
ps
next prev parent reply other threads:[~2006-12-11 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 23:22 [patch] Underscore in hostnames Fabio Olive Leite
2006-12-11 3:56 ` Ian Kent
2006-12-11 12:05 ` Fabio Olive Leite
2006-12-11 14:16 ` Jeff Moyer
2006-12-11 15:34 ` Ian Kent
2006-12-11 15:57 ` Peter Staubach [this message]
2006-12-11 16:17 ` Jeff Moyer
2006-12-11 16:58 ` Fabio Olive Leite
2006-12-13 3:03 ` Ian Kent
2006-12-13 13:26 ` Peter Staubach
2006-12-11 16:20 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457D7FD7.5030702@redhat.com \
--to=staubach@redhat.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.