Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 08 Sep 2000 23:07:22 +0930
From:      Matthew Thyer <thyerm@camtech.net.au>
To:        current@freebsd.org
Subject:   Please consider some cosmetic changes in boot messages
Message-ID:  <39B8EB92.DF0407A8@camtech.net.au>

next in thread | raw e-mail | index | archive | help
Anyone else noticed how FreeBSD is inconsistent with the use of words
like "Doing", "setting" and "starting" in the boot messages ?

For instance, I think the following fragment of my boot should change
from:

Additional routing options: tcp extensions=NO TCP keepalive=YES.
routing daemons:.
Mounting NFS file systems.
additional daemons: syslogd.
checking for core dump...savecore: no core dump
Doing additional network setup: portmap.
Starting final network daemons: mountd nfsd rpc.statd nfsiod NFS access cache ti
me=2.
setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
starting standard daemons: inetd cron usbd.
Initial rc.i386 initialization: apm apmd.
rc.i386 configuring syscons: font8x16 font8x14 font8x8 blank_time allscreens.
additional ABI support:.
Local package initialization: fkeys SETI@home xfstt.
Additional TCP options:.


To:  (I've put * against the changed lines)

Additional routing options: tcp extensions=NO TCP keepalive=YES.
routing daemons:.
Mounting NFS file systems.
additional daemons: syslogd.
checking for core dump...savecore: no core dump
* additional network setup: portmap.
* final network daemons: mountd nfsd rpc.statd nfsiod NFS access cache time=2.
* ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
* a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
* standard daemons: inetd cron usbd.
* rc.i386 initialization: apm apmd.
rc.i386 configuring syscons: font8x16 font8x14 font8x8 blank_time allscreens.
additional ABI support:.
Local package initialization: fkeys SETI@home xfstt.
Additional TCP options:.


And finally, for filesystems with >= 10^6 blocks free, the fsck -p output
(second line) hits exactly 80 chars which makes syscons leave a blank line
before the next line of output.  Call me pedantic but could we change the
word "fragmentation" to "fragmented" to give room for many more blocks in
the filesystem before wrapping.  I'm sure the answer is no due to histerical
raisins but its worth a try ;)


/dev/ad0s2e: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/ad0s2e: clean, 5929804 free (2252 frags, 740944 blocks, 0.0% fragmentation)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39B8EB92.DF0407A8>