> why? Just saw the resulting error and reporting it and cause seemed the logical thing to do...
> nobody wants rootnfs over wlan. ... if this is the only reason we attempt to bring up networking this early in boot I guess it's a non-issue as you suggest; I originally misdiagnosed this locally as the cause of an outright failure to bring up networking at all (which has since been correctly attributed as the need to sleep after starting the regulatory daemon in another bts entry, and dealt with in that package's init scripts). > on a particular strange site you'd be able to write the hooks yourself. > this makes no sense. No problems - the hook is easy enough to write - I'll probably retain mine locally just to remove the lint (ie the cosmetic error at boot that happens without it); no bearing on the bts entry though, may as well close if you're happy that there's no other users of networking this early in boot. Thanks once more, Simon -- Low Prices, Wide Selection of Gas Masks Everyday low price guarantee. We offer special police discounts and an extremely wide selection of gas masks, filters and huge selection of preparedness gear. http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=24e08df2353d2e6cb9bae3a0e3c8c61e
