Duncan <[EMAIL PROTECTED]> wrote:
> On Wed 28 May 2003 11:21, Han Boetes posted as excerpted below:
> > Duncan <[EMAIL PROTECTED]> wrote:
> > > I agree, altho disassembling the script myself into components was
> > > how I cut my teeth on learning both shell scripting and the Mdk
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > init system, as I did it, then upgraded initscripts, then did it
^^^^^^^^^^^
> > > again. <g>
> > >
> > > Now, I don't bother, as I'm running Cooker and updating
> > > initscripts fairly regularly, but I know where stuff is basically
> > > and always delete the i18n font initialization stuff, as it fails
> > > to keep the LILO screen resolution choice I made.
> >
> > *g* then you know what those lines do, but not what they
> > really do :)
> >
> > There is a much more elegant solution to that problem.
>
> Indeed. That's just the one I found first, and it works with no ill
> effects that I can see here, so why mess with it any longer?
>
> AFAIK, those lines don't do anything I need on a standard English-only
> installation. As for the screen resolution, AFAIK, a simple command
> invoked in the local file would work, but I've only come across it
> once, while I was working on something else, and don't recall what it
> was. All I know is if I cut out the font internationalization stuff I
> don't use anyway, I don't have the problem, so that's what I do.
Those two statements are fully contradictory. In fact what you are
saying in the second statement is: `I don't want to learn shell
scripting and I don't want to learn the mdk init system. All I want is
to get rid of my specific problem and I don't care at all if it involves
a dirty hack. And if my solution breaks after one update I complain on
this list and say these initscript should be fixed and I am the man to
do it. And if somebody tells me there is an elegant solution I wont even
bother to look.'
# Han
--
http://www.xs4all.nl/~hanb/software
http://www.xs4all.nl/~hanb/documents/quotingguide.html
