On Thursday 04 October 2001 23:23, Erik Troan wrote: > On 4 Oct 2001, Trond Eivind Glomsrød wrote: > > Ashwin Mansinghka <[EMAIL PROTECTED]> writes: > > > Each time when you refer to using "man <something>" > > > essentially you are refering to excellent documentation done by some > > > one else with pain and effort who did not bother about being over or > > > under staffed. > > > > Uh... the chkconfig man page is, like the rest of the package, written > > here. > > In particular, the chkconfig man page was written by *me*. If you'd like > a list of other documentation I've written, let me know!
Well, as all this is going very far away from the list theme (seawolf, shouldn't it?), I want to say that the book "Linux Application Development" is considered, here in Italy, a great starting point for developers who need or like to join the open source, expecially the linux world. This may be not possible if not well documented. I think the scripts maybe near to unreadable, but consider two thing: they can change very fast from one release to another, and there is little hack to do with them. If tuning the system is simply a matter of removing 10 lines of init script, than what are the differences from Mandrake Linux, RedHat Linux and Debian Linux (and more)? Or, more over, why we should choose to have a bsd style init or a sys v style? The work of write them, I think, but I surely might be wrong, should be of the coders of the distribution. Hacking pleasure remain outside here. All the package from redhat are commented well, somewhere I would like to see more comments, true, but tools written by redhat people are often well documented. I had the pleasure to discovery a lot of utility (please, read here C functions), and I was able to use them quickly. Thanks to the man project, thanks to the source code. We need more man pages, more traslated and update man pages, but the work redhat did was great. The original post, was a suggestion to redhat people. They should follow it, of course. Commenting code is a good behaviour. But Erik can teach me how to program, how to write code how to write simple shell commands. How to write comments. What I want to say is that I'm not a great programmer, only a student. I'm learning on and with redhat. If I (the worst programmer of the world) don't have too much problem following the init script, why should others? The first time I read the init script I was able to change: the [ OK ] tag in a [ GIVE PEACE A CHANCE ] tag and I was able to change the default system font. Oh, I also change the string "Red Hat Linux" from the red color in a cool dark blue one. My system was very kitch... (now is returned sane... :) I was able to do that, and it was the first time I tried to read shell code at all. I hope I was able to explain what were my thoughs, even though sometimes (... maybe a "little" more often than sometimes :) my english is not perfect. neugens -- -=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=--=*=- 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
