> Charles Curley a écrit :
>
> > Memo to Red Hat Engineering: The initialization code has gotten so
> > complicated and so confusing that I have given up trying to understand
> > it. Please simplify it to that we mere mortal paying customers (you
> > know, the folks who pay your salary) can understand and use it. Or
> > document it, however heretical the notion may be. Or both.
> >
>
> I am a mortal and I consider that initilization trivial: each time you change
>
> runlevels it executes /etc/rc.d/rc with runelevel as an argument.
> This will scan the /etc/rc.d/rc.newlevel directory looking for entries
> obeginning with K and execute them by giving thrm "stop" as an
> argument. Then it looks for those beginning with S and executes them
> with start.
<sarcasm>
And for an encore we are going to watch a recently discovered movie of
Ginger Rogers teaching Fred Astaire his first dance steps.
</sarcasm>
I am afraid Charles is beyond that one unless he has changed a LOT from
when I knew him. Step into those init.d scripts and decode what they are
doing. It takes some patience of late with the bits dragged in from two
or three scripts worth of tools. I fondly remember how "simple" the old
5.0 scripts were. It seems they have gotten more complex, in order to
give their fancy messages on screen and to the system log, with each new
release. On the latest batch I have "hacked" I noticed they seem to do
"more than one thing" and contain no commentary about what and why they
are doing. It makes tuning the scripts for local needs awkward.
And then as Eric mentioned, rc.sysinit has gotten close to opaque with
all the "stuff" it does. Now, I do remember while I was teaching myself
coding by rebuilding an HP ATS BASIC using disassembled machine code I
commented what I did because I remember better if I "write it down once"
than if I only think or hear it. I remember thinking, "But, I'll probably
never read it again." Then I came back to it a rather few years later to
extract an algorithm I remembered but not well enough to use. I decided
that "next time I will use even more comments." And I note that the source
I had generated looked rather "Chatty Cathy" at first glance. Ah well.
Please put little headers in front of each section with a BRIEF description
of what the code section does.
; In here we framble the greeblitz
; First we find each greeblitz on the system
; Then we create a backup copy
; then we framble the original in place
That avoids the obvious questions while reading the subsequent section of
bash (it over your head) script, which for people who are not bash script
mavens can be close to impenetrable.
{^_^}
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
