Thomas Hood wrote :
>
> Please add net agent policy for ifupdown's "allow" mechanism
IMHO, it should read :
o implement support for ifupdown's "allow" mechanism.
o remove all net agent policy stuff.
o document how to configure a net interface via hotplug
Rationale : net agent policy are only confusing the user and
don't allow much control. They were necessary when ifupdown had no
support for hotplug. Now that ifupdown has support for it, hotplug
should use this support and drop all the other confusing policies.
Advantage : keep all the net configuration in a single place
(/etc/network/interfaces) ; make net agent script smaller and faster ;
make net agent closer to upstream.
> 0.6.6, released yesterday by AJT. (Total surprise to me.)
> I suppose so too. AJT says that he intends to push 0.6.6 or a successor
> into sarge.
You are not the only one surprised, but at least it's a good
surprise.
(Now, if ifupdown could fix the locking so that I would save
100 ms per net agent invocation - ok, I'm asking too much).
> However, if sarge is going to be frozen very soon then
> there isn't a lot of time to write and debug the new net agent policy
> code.
Changes are pretty trivial and straightforward, it's mostly
about removing stuff. I'm sure you will come up with the patch in 5
min. Testing might take a bit more time.
To me, documentation is the critical part. If the
documentation is not updated when Sarge is released, there will be
quite a few people surprised.
Have fun...
Jean
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
