#2133: Coreutils-6.10
------------------------------------------+---------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [email protected]
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0
Component: Book | Version: SVN
Severity: normal | Resolution:
Keywords: |
------------------------------------------+---------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:8 [EMAIL PROTECTED]:
> Well, you can use sysctl for hostname:
>
> {{{
> $ sysctl -n kernel.hostname
> $ sysctl -q -w kernel.hostname=foo
> }}}
>
> We could write a wrapper script for that.
Or, just feed it into the bootscript as
{{{
sysctl -q -w kernel.hostname=${HOSTNAME}
}}}
As you might have guessed, I normally use 'uname -n' from my buildscripts
to do host-specific things, I can quite happilly get by without a formal
hostname script.
> Personally, I already disable the hostname from coreutils and use the
one from net-tools because it has more features. It would be good to know
if and/or when hostname might be added to util-linux-ng. That would be the
proper place for it, anyway, since it could be tailored to Linux specific
interfaces.
No arguments that util-linux-ng would be the proper place, but google
knows nothing about any intention to put hostname.c there.
Thanks for the response, if you hadn't posted that, I would have said
that the choice comes down to either using the unmaintained net-tools, or
using the not-installed-by-default version from coreutils, at least in the
short term, and I would have to prefer the coreutils version. I think one
of the reasons net-tools was dropped from LFS was because it is no longer
maintained, as shown by the patches BLFS has to apply.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2133#comment:9>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
