On Friday 05 October 2001 04:10, Michael Schwendt wrote: > Nah, this is one place where users (and customers) of the current > stable distribution of Red Hat Linux can get in contact with various > Red Hat employees and discuss issues with regard to the current and > future distribution. As you can see, those employees don't ignore > these discussions. And even when it seems they respond with funny > one-liners most of the time, ;-) I'm sure they take notice of useful > suggestions and discuss them internally.
This is the reason why I found this list one of the most useful/funny to read! Here I have learned a lot of things! > Think about _users_ who want to read and understand those scripts > without any modifications in mind. Imagine you try to track down the > source of a particular setting or problem. High-level comments would > be another sign of quality. And with "high-level" I mean an abstract > summary of what a particular block of code is supposed to achieve > (not an explanation of every single line of code). Yes, in fact I assume the work of writing comments is one of the most important. "They" theach to me: before you write down a single line of code, write a comment. There is something wrong if what you (I) implement differs from whath you (I) thing... (it happens to me sometimes... mmm...) My reply was to remember that Erik is not the last script kid of the heart. He is a programmer, with lot of coding experience. I'm not assuming that everything he think is right. Definitely, I would like to see comments on top of the init script. But I think they are well readable anyway... The fact, is that I divide redhat linux users into two categories. One are normal users. In this category there are people who only use the system. They probabily use RedHat Linux because it is the most famous, they could easily switch to Mandrake to have something more "users friendly" (I think Red Hat is user friendly, anyway). They are not programmers, they are not administrators. They are simply users. A lot of them have a dual boot, with windows on the other side of the hd. They probabily don't wan't to know how init works, they will do when they will be ready. The second kind of user are the administrators. They should know how the system works, even though it is not alway so, but they should be able to easily follow the scripts. Programmers, are in the middle of these two categories. They are able to read the scripts, but maybe they don't know how to use them to tune the system... :) Solution to the problem: Add comments to the script, in a place where one can easily found. But take all the time to do that... Anyway, these kind of post are very fun to read, I have to say. Mario -- -=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=- Gnu Privacy Guard public key: http://digilander.iol.it/linuxlabs/people/signature.html -------------------------------------------------------- http://frinemusic.8m.com http://digilander.iol.it/linuxlabs -=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=- Support The Free Software ** Open Your Mind -=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=- -- =========================================================== hack: [very common] 1. n. Originally, a quick job that produces what is needed, but not well. http://www.tuxedo.org/jargon/html/entry/hack.html _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
