On Thu, Feb 5, 2009 at 1:21 PM, Duncan <[email protected]> wrote: > Mark Knecht <[email protected]> posted > [email protected], excerpted > below, on Thu, 05 Feb 2009 12:28:21 -0800: > >> Duncan has scared me off of this path for now. > > That wasn't really my intention, but I did think you needed to know what > you might be getting yourself into...
Sorry, I completely understand what you are saying and I appreciate it. I just decided that for this problem I'm not motivated enough to spend the time right now. <SNIP> > > OTOH, it's possible other folks have traced and fixed it on their > systems, but whatever triggers it in the first place, perhaps a misplaced > quote in an ebuild command (hmm, seems I know something about misplaced > quotes right about now!) having an effect entirely other than intended > and then it looks like, remains free to blow up in the faces of others. > It might even be a common enough error that when it ultimately gets fixed > in one place, it eventually shows up in another. > My latest experiements with this seem to indicate that whatever parses the lines looks for the first character past a space, so it doesn't like ="clock and bootmisc " but does like (or seems to sort of like) =" clock and bootmisc" None the less all the versions I've tried, along with a second blank line, etc., have failed to boot and in some cases (bootmisc ") actually created a link called " ! (I don't know how to quote a double quote!) ;-) > But it was easy enough to work around, once I got a hint as to how. > Hopefully CRITICAL_SERVICES, once we get it straightened out, works as > well for you. > > -- > Duncan I suspect it will. I see ABCD has suggested just the services. That will be my next experiment. Cheers, Mark
