Phillipp, I kinda like the boot messages, but I think to a new user they might be "scary." Windows has the system, that the logo masks the Autoexec.bat and Config.sys outputs (I guess the rc.d's of the Windows world), but pressing escape will remove the logo (for debugging purposes). I certainly see your point on the amount of work though - it wouldn't be worth it. Still something to consider for future kernels. I mean what is friendlier looking than a giant happy penguin? 8-) If that text was hidden, and KDM, GDM, or XDM was used, and KDE or GNOME was installed, IMHO Linux would seem much friendlier to the Mac or Windows user. For myself, the benefit would be that I wouldn't keep forgetting to wait till KDM starts to log in, rather than logging in at the text-based log-in screen while X is loading (after several years of using that log in prompt, I forget that KDM is on it's way ;-). -Tim "The guy who drives himself nuts using 4 operating systems" ----------------------------------------------------------------- Timothy R. Butler Universal Networks Information Tech. Consultant Christian Web Services Since 1996 ICQ #12495932 AIM: Uninettm An Authorized IPSwitch Reseller tbutler@uninetsolutions.com http://www.uninetsolutions.com ===================== "Solutions that Work" =====================
-----Original Message----- From: Philipp Thomas [mailto:pthomas@suse.de] Sent: Saturday, June 03, 2000 7:38 PM To: Timothy R. Butler Cc: SuSE Mailing List Subject: Re: [SLE] Re: Changing the penguin bootlogo
* Timothy R. Butler (tbutler@uninetsolutions.com) [20000604 01:53]:
ol' Linux. Just curious - if I were trying to make a system look "friendlier" for a new Linux user
Pray tell in what way does hiding the boot messages make a system friendlier? Normally one can just ignore them, but in case of problems, these sometimes quickly help you identify what's going wrong.
Only because MS set a precedent doesn't mean anybody has to follow it. And even when you do find a way to hide the messages - which would only be possible with some serious kernel code hacking, as the messages are output with printk and are only 'redirectable' after syslogd has been started, which happens quite some time later - the ouput of an eventual fsck and the success/failure messages of the init scripts would destroy the logo anyways (although all those messages could be redirected rather easily by changing the init scripts).
As you see, lots of work with little or no real benefit.
Philipp
-- Philipp Thomas
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany #define NINODE 50 /* number of in core inodes */ #define NPROC 30 /* max number of processes */ -- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/