On 5/16/11 1:49 AM, Bryan Kadzban wrote:
> I'm not sure what the goal *should* be. :-) Does it make sense to try
> to clean up completely in this kind of setup? Maybe or maybe not.
>
> I do think it's least *surprising* to only undo the effects of the start
> script, though. For whatever that's
On 05/17/2011 08:54 AM, Jeremy Huntwork wrote:
On 5/16/11 1:49 AM, Bryan Kadzban wrote:
I'm not sure what the goal *should* be. :-) Does it make sense to try
to clean up completely in this kind of setup? Maybe or maybe not.
I do think it's least *surprising* to only undo the effects of the s
On 05/17/2011 08:54 AM, Jeremy Huntwork wrote:
>
> I do think we're getting a little overcomplicated here. Let's try to
> simplify expectations. Here's what I expect (and I *think* this is
> reasonable - you tell me :-) )
>
> When I run the equivalent of /etc/init.d/network stop:
>
> All devices co
Jeremy Huntwork wrote:
> On 5/16/11 1:49 AM, Bryan Kadzban wrote:
>> I'm not sure what the goal *should* be. :-) Does it make sense to
>> try to clean up completely in this kind of setup? Maybe or maybe
>> not.
>>
>> I do think it's least *surprising* to only undo the effects of the
>> start sc
Few nits related to the shell. In the network script:
> # Process individual configuration files
> for file in `ls "${dir}"`; do
Ew. :-) How about:
for file in "${dir}"/* ; do
ONBOOT=`grep "ONBOOT" "${file}" | sed ...
...
(since it always does a ${dir}/${file} as
