On Thu 29 May 2003 05:09, Han Boetes posted as excerpted below: > Duncan <[EMAIL PROTECTED]> wrote: > > On Wed 28 May 2003 11:21, Han Boetes posted as excerpted below: > > 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.'
I think you misunderstood what I was attempting to say, then. It's obvious I hit a raw nerve I wasn't aware of, as most of that which I could and was initially offended by is entirely out of your own head, as it CERTAINLY didn't come from mine, and I've discovered in life that such attacks are often in defense, because I somehow stepped on a raw nerve and caused offense where it wasn't intended. Thus, I publicly apologize for whatever I did that caused that personal attack. Perhaps you authored the code I hacked out. If so, I am sorry. However, the fact was, I saw no ill effects from removing it, and doing so however ugly it might be, did accomplish the purpose of conserving the selected screen resolution settings that were getting changed, much to my distress. Whether there's a better way to do it isn't the issue. The issue is that while I imagine there IS a better way, I haven't come across it explained so I could make use of it. Perhaps you could at least point me in the right direction, even if this isn't the place for a detailed explanation? As for the original thread topic, what I was ATTEMPTING to say, pointing to my own experience to back it up, was that yes, I agreed with the original poster. rc.sysinit *IS* a big pile of scripting unrelated save for they are all done at init functions into a big script file, when most of the rest of the Mdk system, and indeed the *ix tradition, is based on small discreet tools and scripts each with their individual function, with the discreet functions then called one at a time from a master script, when a larger whole process needs accomplished. The init process *WOULD* be easier to maintain for Mdk, easier to grasp for newbies, and easier to modify for admins wishing to customize their deployments, if that file were broken down into its discretely functional components. Such is my opinion after having worked with it myself. Note that nowhere have I suggested that I'm the one to do it. Rather, far from it, as I recognize I've still a lot to learn b4 I can be of much use in actual code contribution, scripts or otherwise. That doesn't prevent me, however, from attempting to contribute where I can, as a beta tester and with my own opinion, on these groups and elsewhere. My own work mentioned above, as I originally stated, was simply a challenge to myself and for my own edification. If that can help others, I've no objection to that, but I'm certainly not presuming I have any more than a determined noob's experience and knowledge in the area, nor am I claiming I'm qualified to make changes on other than my own systems. -- Duncan - List replies preferred. "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." Benjamin Franklin
