Mark Knecht <[email protected]> posted [email protected], excerpted below, on Thu, 05 Feb 2009 06:31:40 -0800:
> Now, revisiting the file it seems that the echo command has dropped the > quotes so the line in the file looks like > > CRITICAL_SERVICES=checkroot modules checkfs localmount clock bootmisc > > I'll wait for a little instruction about this. Why did they get dropped > and should I add them in by hand? Hmm... My mistake. Oops! The command as I posted it will have bash "eat" the quotes on first parse, so they won't make it into the file. Try editing the file manually, adding the quotes, and putting clock first instead of right before bootmisc. > I tried it with the quote and got a failure at not finding bootmisc" - > yes, with a double quote at the end... That indicates to me that it's not seeing the full value, and still parsing all but the first word as commands. Did you put a quote at each end, or only after bootmisc, not after the = sign? The quote should enclose the whole value, with one quote at the beginning (right after the equals) and one at the end (right after bootmisc). Sorry for the screwup. The hazards of trying to work with something I left behind a year ago, without testing before I post. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
