> I agree with you on the utility value of the OK/FAILED message, but I > have to disagree that they cause bloat. The OK/FAILED messages seem to > use only shell builtins and controls;
Really ? Have you ever tried booting Redhat 9.0 on a 386 with 16 MB RAM ? Or even a Pentium-Classic, 133 MHz with a 32 MB RAM ? If you have done so, you should be knowing how fast BASH shell builtins perform ;-). Compare Redhat with Debian/Slackware on those legacy hardware, and you will understand how startup scripts make a lot of difference in boot times. Even on a modern hardware, I've observed that Redhat boots slower than Windows 2000, most of the times. > If echo -ne causes your system to boot slower than other systems, then > certainly it is not Redhat's fault. I wouldn't say its their "fault". But usage of 'echo -ne', 'cut', 'sed', 'cat' and similar commands (whether builtin or external) for trivial things like displaying welcome messages and printing [ OK ]/[ FAILED ] messages is what I term as non-optimal/bad design. > Further, I didn't see any cat /etc/issue anywhere in /etc/rc.d. Sorry, that was my mistake. I meant /etc/redhat-release file (I do not have Redhat running on any of my machines now, so I must've forgotten) . Perhaps you must read through the rc.sysinit script and compare it to rc.S on slackware to get a picture of what I meant. > I can understand that is it fashionable to blame Redhat for the > silliest of reasons. Redhat's sluggish and non-optimal startup scripts cannot be "silliest" of excuses. The complexity of their scripts and configuration files have grown too far from being human manageable. Just how many configuration files should a poor sysadmin look for, to tweak a Redhat box ? Why should a sysadmin learn redhat-config-* (and webmin, linuxconf, ntsysv, netconfig, chkconfig, and so on...) tools when all he can do edit one of the configuration files using a text editor ? Why should a default Redhat installation run fsck for ages on a journalled file system ? What is the point in the wrapper rc scripts to create lock files in /var/lock/ to keep track of services running ? Just how many commands and configuration files can a sysadmin be thorough with, to be confident on a Redhat box ? Overall, I would comment that Redhat's startup scripts and configuration files and unnecessarily complicated. I do have a _valid_ point/reason to "blame" Redhat. But I do like Redhat for their efforts in driving Linux onto the corporate sector, and for their active involvement in the FLOSS community. Its just that their way of doing things (with their Linux distribution) doesn't appeal to me. Cheers, Chandrashekar Babu. ------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
