LFS Trac wrote: > #2133: Coreutils-6.10 > ------------------------------------------+--------------------------------- > Reporter: [EMAIL PROTECTED] | Owner: [email protected] > Type: enhancement | Status: closed > > Priority: normal | Milestone: 7.0 > > Component: Book | Version: SVN > > Severity: normal | Resolution: fixed > > Keywords: | > ------------------------------------------+--------------------------------- > Comment (by [EMAIL PROTECTED]): > > Replying to [comment:11 [EMAIL PROTECTED]: > > {{{ > > cat >/bin/hostname <<EOF > > #!/bin/sh > > if [ \$# -gt 0 ]; then > > sysctl -q -w kernel.hostname=\$1 > > else > > uname -n > > fi > > EOF > > chmod -m 0755 /bin/hostname > > }}} > OK, I know we've got a real hostname now|again, but I've finally got to > the end of my current build with this, so I'll now say: "Don't try this at > home!". Something in my blfs packages for the things I build before > booting managed to call 'hostname -f'. I still haven't found which > package it was, but it altered the host-system's name to -f and my > automated backup scripts were distinctly unimpressed. So, anyone who > wants to use a script for hostname needs to handle that in some form. > > How far do you build into BLFS? Do you try to configure X Windows before reboot? The obvious culprit to me is the 'startx' script: ======================================= # set up default Xauth info for this machine case `uname` in Linux*) if [ -z "`hostname --version 2>&1 | grep GNU`" ]; then hostname=`hostname -f` else hostname=`hostname` fi ;; *) hostname=`hostname` ;; esac =======================================
-- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
