Public SourceMage Discussion List

[nealbirch <nealbirch AT attbi.com>]

Eric Sandall wrote:

> > There is an issue for this and other spells that when cast put init
> > scripts where they belong; whether to copy the default script or the
> > function-using scripts. Shouldn't be hard, though, we can add something
> > like:
> >
> > if [ -f /etc/init.d/functions ]; then
> > install -m 755 $SCRIPT_DIRECTORY/script-w.sh /etc/init.d/script.sh else
> > install -m 755 $SCRIPT_DIRECTORY/script-wo.sh /etc/init.d/script.sh fi
> >
> > with the appropriate scripts (w = with functions, wo =  without) in the
> > $SCRIPT_DIRECTORY.
>
>
> If there are two versions of the script available, shouldn't we just use
> the functions script?  Why would we want to use the other script?  That'll
> just make a mess later on, and I see no benefit to doing this.  What's
> wrong with functions?

If you don't have the function script installed, the script stops when 
it hits the line which sources the functions script. I was just looking 
out for those poor souls who don't have the functions script already 
installed, or have removed it. Things should fail nice, if they fail.

hmmm. the other problem of mount breaking. Is it possible that the 
functions script didn't get copied but the mount.sh script did due to 
some weird confluence of circumstances? Stranger things have happened in 
the last week, at least on my machine... glibc breaking for no good 
reason so that casting gcc destroying itself, alsa-drivers not reading 
it's stored config, after everything rebuilt (much faster with the new 
athlon-xp 2000 and motherboard, btw), / wouldn't unmount when I 
rebooted, etc.

Just a quick question on another topic entirely. Before I rebuild, I 
cast gcc, glibc and the kernel, then reboot so the nice newly rebuilt 
kernel, gcc etc is used for the rebuild. Somewhere during the rebuild, 
the kernel gets cast (again!), and everything dependent on the new 
kernel (modules for alsa, video drivers, i2c, lm_sensors, etc) needs to 
be recast. Am I wrong in thinking this should wait till after a reboot 
into the new kernel? I'm just wondering if it would be simpler to dispel 
those things until after the usual rebuild cleanup and reboot into new 
kernel, then recast those things which are dependent on that new kernel.

--
"You can fool some of the people all of the time
--and those are the ones you have to concentrate on!"
GW Bush-- from the N.Y. Times