From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>,
drepper@redhat.com, akpm <akpm@osdl.org>,
serue@us.ibm.com, sam@vilain.net, clg@fr.ibm.com, dev@sw.ru
Subject: Re: [PATCH] POSIX-hostname up to 255 characters
Date: Fri, 26 May 2006 16:42:16 +0200 [thread overview]
Message-ID: <20060526144216.GZ13513@lug-owl.de> (raw)
In-Reply-To: <m1zmh5b129.fsf@ebiederm.dsl.xmission.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
On Fri, 2006-05-26 03:14:06 -0600, Eric W. Biederman <ebiederm@xmission.com> wrote:
> "Randy.Dunlap" <rdunlap@xenotime.net> writes:
> > This patch is against 2.6.17-rc5, for review/comments, please.
> > It won't apply to -mm since Andrew has merged the uts-namespace patches.
> > I'll see about merging it with those patches next.
> > ---
> >
> > From: Randy Dunlap <rdunlap@xenotime.net>
> >
> > Implement POSIX-defined length for 'hostname' so that hostnames
> > can be longer than 64 characters (max. 255 characters plus
> > terminating NULL character).
> >
> > Adds sys_gethostname_long() and sys_sethostname_long().
> > Tested on i386 and x86_64.
>
> Is there any particular reason for this?
> The existing sys_gethostname and sys_sethostname interfaces
> should work for any string length.
>
> Although I do agree that we need at least one new syscall
> for the architectures that don't currently use get_hostname.
...and this should have gone to linux-arch, too...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-26 14:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 3:45 Randy.Dunlap
2006-05-26 9:14 ` Eric W. Biederman
2006-05-26 14:42 ` Jan-Benedict Glaw [this message]
2006-05-26 17:28 ` Randy.Dunlap
2006-05-26 18:01 ` Jan-Benedict Glaw
2006-05-26 18:15 ` linux-os (Dick Johnson)
2006-05-26 18:28 ` Ulrich Drepper
2006-05-26 18:35 ` linux-os (Dick Johnson)
2006-05-26 18:55 ` Ulrich Drepper
2006-05-26 19:12 ` Jan Engelhardt
2006-05-26 21:31 ` Eric W. Biederman
2006-05-27 1:39 ` Randy.Dunlap
2006-05-27 7:36 ` Randy.Dunlap
2006-05-27 13:54 ` Eric W. Biederman
2006-05-28 18:32 ` Randy.Dunlap
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=20060526144216.GZ13513@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sam@vilain.net \
--cc=serue@us.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®