Hi Roland, > > The conversion script does sort the file in correct order but if the > > user twiddles with it things may get run in incorrect order (e.g. > > put networking at the end and see how many daemons fail to start). > > This is an ugly situation, but I don't think that it justifies a > "critical" bug, because it's a human mistake (okay, based on a wrong > man page, which I will fix soon). But if I edit a file, with > ascending IDs in the first column, I usually order them by hand before > saving the file. I think that most people will do so, which explains > why nobody else found this problem in the documentation before. > Well I'm a person that reordered the file so I could see the boot order. I put all the S level entries at the top, then the 2345 entries, then the 06 entries. I even split lines to separate out the start and stop actions. What I ended up with was a list that matched the startup and shutdown order.
As soon as I started adding and upgrading stuff it all went wrong, lots of stuff was added to the S section at the start which put it before the 2345 section. I had to fix it up after every "apt-get upgrade". In short I think this is release critical since it broke my system a number of times. Now the good news: > > All you have to do is replace "xxx < $configfile" with "sort > > $configfile | xxx". Actually, you can't since sort is in /usr/bin, > > you'll have to do a sort with bash functions. > > I don't have a sh function available for sorting at the moment and I'm > not sure whether I can accept the speed loss of such a function. > > Tschoeeee > > Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
