[EMAIL PROTECTED] said: :- oops, rc2 isn't started. too bad. I think that is exactly the desired design. The RC *system* starts things correctly, but the manager, *bypassing* the RC *system* can start and stop things exactly as he wished. For debugging or whatever. I'd argue that if you want to start/stop a *subtree*, you should ask the RC *system* to do that somehow. -- Robert Withrow -- (+1 978 288 8256, ESN 248) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: import NetBSD rc system Matt Dillon
- Re: import NetBSD rc system Greg Black
- Re: import NetBSD rc system Doug Barton
- Re: import NetBSD rc system Eivind Eklund
- Re: import NetBSD rc system David Terrell
- Re: import NetBSD rc system Wes Peters
- Re: import NetBSD rc system David O'Brien -Hackers
- Re: import NetBSD rc system Gordon Tetlow
- Re: import NetBSD rc system David O'Brien
- Re: import NetBSD rc system Gordon Tetlow
- Re: import NetBSD rc system Robert Withrow
- Re: import NetBSD rc system Robert Watson
- Re: import NetBSD rc system Shannon Hendrix
- Re: import NetBSD rc system Kevin Way
- Re: import NetBSD rc system Gordon Tetlow
- Re: import NetBSD rc system Terry Lambert
- Run states (Was: import NetBSD rc system) Mike Meyer
- Re: import NetBSD rc system Sergey Babkin
- Re: import NetBSD rc system Cyrille Lefevre
- Re: import NetBSD rc system Sergey Babkin
- Re: import NetBSD rc system Warner Losh

