Package: initscripts
Version: 2.86.ds1-5
Severity: minor
Tags: patch

Because of the continous additions to "uname -a" output, the default /etc/motd
header that is generated on every boot starts looking very bloated to me.

This is specialy true on GNU/kFreeBSD where options like -p and -i are also
detected by the kernel (instead of returning "unknown" which would be
discarded).  For example, in a qemu guest system:

$ uname -a
GNU/kFreeBSD orthanc 5.4-1-486 #0 Sun Nov 13 18:46:42 CET 2005 i686 i386 Pentium
II/Pentium II Xeon/Celeron GNU/kFreeBSD

I'd recommend using uname -snrvm instead:

$ uname -snrvm
GNU/kFreeBSD orthanc 5.4-1-486 #0 Sun Nov 13 18:46:42 CET 2005 i686

Patch attached.

-- System Information:
Debian Release: testing/unstable
Architecture: kfreebsd-i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: GNU/kFreeBSD 5.4-1-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages initscripts depends on:
ii  coreutils               5.93-5           The GNU core utilities
ii  dpkg                    1.13.11+kfreebsd package maintenance system for Deb
ii  e2fsprogs               1.38-2           ext2 file system utilities and lib
ii  libc0.1                 2.3-1+kbsd.13    GNU C Library: Shared libraries an
ii  lsb-base                3.0-11           Linux Standard Base 3.0 init scrip
ii  util-linux              2.12p-8+kbsd.1   Miscellaneous system utilities

initscripts recommends no packages.

-- no debconf information
--- sysvinit-2.86.ds1/debian/initscripts/etc/init.d/bootmisc.sh~        
2005-11-20 13:05:47.000000000 +0100
+++ sysvinit-2.86.ds1/debian/initscripts/etc/init.d/bootmisc.sh 2005-11-20 
13:09:40.000000000 +0100
@@ -54,7 +54,7 @@
                MOTD="`readlink -f /etc/motd || :`"
                if [ "$MOTD" != "" ]
                then
-                       uname -a > $MOTD.tmp
+                       uname -snrvm > $MOTD.tmp
                        sed 1d $MOTD >> $MOTD.tmp
                        mv $MOTD.tmp $MOTD
                fi

Reply via email to