Roland McGrath <[EMAIL PROTECTED]> writes:
> > FWIW, SUSv2 also has no way to query a max path via sysconf.
I meant to say "max hostname length" not path length.
> I think you are mistaken. As I understand it, SUSv2 specifies a superset
> of 1003.1-1996 (POSIX.1). POSIX.1 specifies sysconf(_SC
On Thu, May 31, 2001 at 11:57:24PM +0200, Marcus Brinkmann wrote:
> It's not a standard yet, but it seems it will replace the various
> UNIX standards (1003.1/96, 1003.2/92 and SUS).
Sorry, small correction: It only is going to replace the core of SUS.
I should also mention that you can get th
On Thu, May 31, 2001 at 10:55:49PM +0200, Robert Bihlmeyer wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> [... and the value for MAXHOSTNAMELEN iiis ...]
>
> > Nevermind, the standard is a moving target. Sorry. What I quoted was from
> > draft 5, and I now checked draft 6, and it doe
> FWIW, SUSv2 also has no way to query a max path via sysconf.
I think you are mistaken. As I understand it, SUSv2 specifies a superset
of 1003.1-1996 (POSIX.1). POSIX.1 specifies sysconf(_SC_PATH_MAX).
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
[... and the value for MAXHOSTNAMELEN iiis ...]
> Nevermind, the standard is a moving target. Sorry. What I quoted was from
> draft 5, and I now checked draft 6, and it does not refer to a single
> constant "255" anymore.
Which standard are you talk
Roland McGrath <[EMAIL PROTECTED]> writes:
> Have you followed the discussion here where someone said there is a
> standard now constraining the maximum anyone can expect to use?
> Maybe someone can post the specific citation for whatever that was?
Yes, of course we conform to the standard. I wa
On Sun, May 27, 2001 at 10:44:31PM -0400, Roland McGrath wrote:
> > Roland McGrath <[EMAIL PROTECTED]> writes:
> >
> > > Yes, has always been the place to find MAXHOSTNAMELEN.
> > > If Thomas doesn't object, I will put it into libc.
> >
> > Argh. I don't want there to be a max. Blech blech ble
> Roland McGrath <[EMAIL PROTECTED]> writes:
>
> > Yes, has always been the place to find MAXHOSTNAMELEN.
> > If Thomas doesn't object, I will put it into libc.
>
> Argh. I don't want there to be a max. Blech blech blech blech.
Have you followed the discussion here where someone said there is
Roland McGrath <[EMAIL PROTECTED]> writes:
> Yes, has always been the place to find MAXHOSTNAMELEN.
> If Thomas doesn't object, I will put it into libc.
Argh. I don't want there to be a max. Blech blech blech blech.
What value are you going to put in?
> On Fri, May 25, 2001 at 04:44:53PM -0400, Roland McGrath wrote:
> >
> > I think that is reasonable. The was no POSIX standard specifying
> > gethostname at the time the original decision was made.
>
> Would this be in sysdeps/mach/hurd/sys/param.h? It seems what info libc
> suggests.
Yes, h
On Fri, May 25, 2001 at 04:44:53PM -0400, Roland McGrath wrote:
>
> I think that is reasonable. The was no POSIX standard specifying
> gethostname at the time the original decision was made.
Would this be in sysdeps/mach/hurd/sys/param.h? It seems what info libc
suggests.
On some systems,
> I always wondered about that. In fact, I asked why we don't define it here
> a year or so ago. POSIX says in gethostname()
>
> Host names are limited to 255 bytes.
>
> (at least in my recent draft).
>
> So doesn't it make sense for us to define this macro? All users of
> MAXHOSTNAMELEN rely
On Fri, May 25, 2001 at 09:00:21AM -0400, Igor Khavkine wrote:
> > So doesn't it make sense for us to define this macro? All users of
> > MAXHOSTNAMELEN rely on the standard POSIX interface, so even if
> > the Hurd itself is not limited by this, those programs might
> > rightly rely on this limit
On Fri, May 25, 2001 at 12:53:32PM +0200, Marcus Brinkmann wrote:
> On Wed, May 23, 2001 at 10:26:48PM -0400, Igor Khavkine wrote:
> > The only changes were the standard MAX*LEN problems. In the case
> > of MAXHOSTNAMELEN, I just defined it to 256 following SUSv2. Even
> > though the standard does
On Wed, May 23, 2001 at 10:26:48PM -0400, Igor Khavkine wrote:
> The only changes were the standard MAX*LEN problems. In the case
> of MAXHOSTNAMELEN, I just defined it to 256 following SUSv2. Even
> though the standard does not define this macro, it does say that
> hostnames can't be longer then 2
Hi, I ported bsdgames. So now it can be added to autobuilder
(this part is for you Jeff). The patch is available from
my site http://alcor.concordia.ca/~i_khavki/ and I will
submit a bug report.
The only changes were the standard MAX*LEN problems. In the case
of MAXHOSTNAMELEN, I just defined it t
16 matches
Mail list logo
