Man, I didn=B4t expect such a heavy discussion on that
anoying boot messages... ;-)

I have a machine here, running NetBSD and during bootup, only the
following messages are coming:

Gateway Bootloader V2.6
(c) 2000, 2001
booting wd0e:gate.gz
1610355+10545112+156428 [65+99856+90677]=3D0xbed7b4
Enabling ipfilter.
Building databases...
Starting syslogd.
Mounting all filesystems...
Starting snmpd.
Starting confd.
Starting sshd.
Starting inetd.
Starting responder 1
Starting cfgserver.
Starting biodatalogin.
Starting bigfired.
Starting cron.
Starting guard.
Clearing /tmp.
find: not found
Fri Jul 12 13:30:15 GMT 2002

VPN Gateway [VPN]

login:

That=B4s what I just want to achieve. Just a bit of information, not a =
massive
Kernel output or whatever...

-----Original Message-----
From: Chris Wareham [mailto:chris.wareham@iosystems.co.uk]
Sent: Freitag, 12. Juli 2002 12:47
To: NetBSD Help mailing list
Subject: Re: Startup Messages


Martin Weber wrote:
> On Fri, Jul 12, 2002 at 10:55:05AM +0100, Chris Wareham wrote, in =
reply to me:
>=20
>>[...]
>>
>>And if he can't boot to a stage where he can login? Then he's
>>mucho fscked and looking at a reinstall, hoping that cures the
>>problem.
>=20
>=20
> After I did a successful boot, and did not change anything on
> my computer, what's wrong in not wanting to see those messages
> any longer ? boot -s e.g. could ALWAYS display the messages,
> and then you're not a bit fscked :)
>=20

Standard boot flags stuff is probably too technical for ordinary
users - for whom the command line is anathema unfortunately. This
debate really relates to the expectations of "ordinary users",
which means measuring up (or down) to what Windows provides. So I
suppose one answer is to include a clear option in the pretty
bootloader to come up in single user mode, or another option to
"show diagnostic messages". Something akin to the simple menu
Windows displays for selecting "safe mode".

Chris

--=20
chris.wareham@iosystems.co.uk (work)
cwareham@btinternet.com (home)