> and, the OTHER project in this discussion -- SARE -- leaning
> on your own
> argument, is pointedly NOT undertaking to use/conform to sa's
> 'official' tools & capabilities -- namely, sa-update as a delivery
> mechanism.
I don't see how I can make this any clearer....
SARE is rules. NOT delivery.
SARE is NOT an official part of SA. And it is completely optional.
It just so happened that RDJ came to be. We supported it, but all we really needed to do was standardise our headers.
We write rules, not delivery systems. You can print out the rulesets from our webpage, and retype them into your system if you like. You can have someone encrypt ROT13, RAR, ZIP, and send you the torrent link. How you get your rules is your choice.
When a resonible solution to the channel vs ruleset problem comes to light, SARE will most definetly help to aid in whatever way we can. As of now, we provide cf files via port 80.
If you want to volunteer to update our webpage everytime we get around to updating rules, then you let me know. We are a group of volunteers with $dayjobs. Some SARE members even have lives after work.
And your UNIX vs Winodws argument is pointless. IIRC a batch job and AT command still work in the win x32 enviorment.
--Chris
