I think we should try to be enthusiastic and supportive. It looks like an attempt by industry to engage the open source community; forge a symbiotic relationship. This may be a Good Thing. Sure they're after free beer, but open source CE kit would offer much more Freedom than closed source solutions, as well as all the exposure these guys might offer. This looks like an opportunity to me...
You're right IMO, Mr Loud. This solution is easy to set up, easy to use, easy to maintain, and cheap.
We use something similar: lots of RAID5 on the sort of IDE disks which spin slowly and come with a 3 year warranty. The whole caboodle is replaced periodically and anytime something fails, and from time to time a pile of tapes to take offsite are created.
This system allows someone to snoop e-mails going out to you customers and obtain freebee software urls. I guess this would take a day for a/.er who's never done dodgey stuff before, or 20 minutes for a l33t k1dd13.
I do adding an entry to an.htaccess file, the password for which is entered by the user on an https form. This may save the embarrassment of having your client's stuff warezed on p2p.
Hey wait, more fundamental to caring for your clients' stuff; don't use IIS.
Slashdot Mirror
I think we should try to be enthusiastic and supportive. It looks like an attempt by industry to engage the open source community; forge a symbiotic relationship. This may be a Good Thing. Sure they're after free beer, but open source CE kit would offer much more Freedom than closed source solutions, as well as all the exposure these guys might offer. This looks like an opportunity to me...
You're right IMO, Mr Loud. This solution is easy to set up, easy to use, easy to maintain, and cheap.
We use something similar: lots of RAID5 on the sort of IDE disks which spin slowly and come with a 3 year warranty. The whole caboodle is replaced periodically and anytime something fails, and from time to time a pile of tapes to take offsite are created.
I don't give a flying fsck about this stuff. Write something for grass roots people who have a modem.
I don't know how to "snoop into HTTP traffic" and I don't want to.
Have a look at http://ettercap.sourceforge.net to get an idea, but don't do that; use ssh, gpg, etc.
This system allows someone to snoop e-mails going out to you customers and obtain freebee software urls. I guess this would take a day for a /.er who's never done dodgey stuff before, or 20 minutes for a l33t k1dd13.
.htaccess file, the password for which is entered by the user on an https form. This may save the embarrassment of having your client's stuff warezed on p2p.
I do adding an entry to an
Hey wait, more fundamental to caring for your clients' stuff; don't use IIS.
These have a product called Monitor Master which seems pretty flexible and will do at least part of what you want.
It will be on the front page of http://www.argogroup.com
I like using these -
man(1)
K&R on C
Strastroup on C++
Larry Wall on perl
Donald Knuth on art
javadoc(1) on java
emacs(1)