I'm posting this message from a heimdal developer to bug-hurd
for discussion on the topic of HOST_NAME_MAX.  I don't have a 
draft of POSIX so I can't verify this.

  However, your 1st note is something I don't agree with.  For
example
MAXPATHLEN is defined on many systems, but is not the best way
to find the limitations of the system because different filesystems
could have different limits.  For example if a GNU/Linux system
has an nfs filesystem mounted from a GNU/Hurd system or any system
with a larger MAXPATHLEN, the program would break when retrieving
a file off the nfs mount when it really shouldn't.  This is a 
simple plee for the use of pathconf. 

  A note on defined constants, I think FILENAME_MAX is too small on
GNU/Hurd at only 1024.  I think something large, as implied by the
documentation of glibc, like 65667 should be used.  


--- "Jacques A. Vidrine" <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> Thanks for the report.  I do not think the answer is to add a new
> API.
> 
> Almost  all  versions of  UNIX  specify  MAXHOSTNAMELEN (see 
> [Stevens
> UNPv1]).  The Hurd probably should, too.
> 
> Regardless,  the next  version of  POSIX specifies  HOST_NAME_MAX. 
> We
> should probably  be using  HOST_NAME_MAX instead of  MAXHOSTNAMELEN
> in
> the Heimdal sources, or at least do something such as
> 
>  #if !defined(MAXHOSTNAMELEN) && defined(HOST_NAME_MAX)
>  #define MAXHOSTNAMELEN HOST_NAME_MAX
>  #endif
> 
> IMHO a system that defines neither MAXHOSTNAMELEN nor HOST_NAME_MAX
> is
> broken [1].
> 
> Cheers,
> -- 
> Jacques A. Vidrine <[EMAIL PROTECTED]>                  
> http://www.nectar.com/
> Verio Web Hosting       =      FreeBSD UNIX      =        Heimdal
> Kerberos
> [EMAIL PROTECTED]      =   [EMAIL PROTECTED]   =      
> [EMAIL PROTECTED]
> 
> [1]  I'm ignoring  the  fact that  HOST_NAME_MAX is  one  of the 
> many
> `possibly  indeterminate  run-time   invariant  values'.   Any 
> system
> designer  that requires  use  of sysconf()  for  such basic 
> constants
> should be drawn-and-quartered :-)
> 
> [Stevens UNPv1] Stevens, W. Richard. _Unix Network Programming
> Volume 1, 2nd Edition_.  Upper Saddle River, NJ: Prentice Hall,
> 1998.  Of course :-)
> 
> On Fri, Sep 28, 2001 at 11:15:01AM +1000, Brian May wrote:
> > Hello,
> > 
> > I received this bug report against Heimdal, with patches
> > that will allow it to compile on the Hurd.
> > 
> > I suggested that putting xgethostname in libroken but be more
> > appropriate then libkrb5, but apart from that everything else
> looks
> > OK (not tested thoroughly yet, as I do not have the latest
> automake
> > required).
> > 
> > Thanks.
> > -- 
> > Brian May <[EMAIL PROTECTED]>
> 
> > Date: Sun, 23 Sep 2001 20:16:27 -0700 (PDT)
> > From: James Morrison <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Bug#113317: [patch] heimdal on GNU HURD
> > Delivered-To: [EMAIL PROTECTED]
> > Delivered-To: [EMAIL PROTECTED]
> > 
> > PACKAGE: heimdal
> > VERSION: 0.4c-2
> > SEVERITY: important
> > 
> >  This patch removes the need for MAXHOSTNAMELEN by using the
> > function xgethostname by Neal Walfield.  Removing MAXHOSTNAMELEN
> > and conditionalizing the use of ARG_MAX, which is not defined on
> GNU
> > (HURD), allows heimdal to compile on GNU (HURD).
> > 
> >  xgethostname is not in the patch, but a separate attachment.
> > I but it in lib/krb5.  In the patch xgethostname is excepted to
> > be in lib/krb5 because I have added it to Makefile.am
> > 
> > 
> > =====
> > James Morrison
> >    University of Waterloo
> >    Computer Science - Digital Hardware
> >    2A co-op
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Get email alerts & NEW webcam video instant messaging with Yahoo!
> Messenger. http://im.yahoo.com
> 
> 
> 
> 
> 


=====
James Morrison
   University of Waterloo
   Computer Science - Digital Hardware
   2A co-op

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd

Reply via email to