Why would the people in an open source project waste their time talking to the press to begin with? It's about the code, and scratching an itch, etc. If a journalist wants to know something about the project, he can just look at the website like everybody else.
An open source project is NOT a corporation, and PR is irrelevant.
Now would be an excellent time to stop all the self-serving "I helped start all this" publicity. You've had your say, several times over now. The sour grapes thing is getting really old now.
You can't really slap those kinds of interfaces in cisco's either -- not if you expect them to work, and still be affordable. Juniper would be a better bet, with that kind of load.
I think the OP is talking about lower-end gear anyway, and cisco's low-end routers definitely don't do everything (anything) in hardware.
Make sure you plan some space on every floor for a wiring closet while you still can; more than one for larger floors. Place them so you don't have to do more than about 50m from the closet to workstations. Use cat5 cable from the closets to where people will work. If any consultant or network type tells you to use cat6, fire him.
Plan for at least four patches per desk; people will bring in laptops, or put double the number of people in an office. Don't forget the absolute minimum is two patches per person (computer, phone), and the minimum will last you about a month before people start bringing in little hubs to put on their desk (which you want to avoid).
Between the wiring closets, use fiber. It's not as expensive as you may think, and terminating is quite painless -- many switches have fiber ports or room for fiber modules. You can also use fibercopper transceivers, not too expensive. Use single mode (SM) fiber. You need to do this because a) it can go much longer distances, b) you can happily string it alongside power lines if you need to, and c) because you can upgrade uplinks to gigE without worrying about the cabling.
You'll also need to get copper into the wiring closets though, for connecting the PBX to the phones. Distance isn't such a big problem for those.
If at all possible, get double the number of fiber links that you strictly need. Ideally, string it on different sides of the building or floor. You can't crimp it like you can cat5, and getting fiber types in for a splice takes a while. In a pinch, when one gets cut, it's good to have a guaranteed extra link ready, which is undamaged through following a completely different route.
In the wiring closets, put switches, not hubs. Don't use hubs at all, in fact.
Don't forget that the big cost in laying wire (both cat5 and fiber) is in man-hours, not the terminating equipment or physical cable. Putting in 10 cables isn't that much more expensive than putting in 1, in other words.
You could just upgrade to a modern MTA, such as Postfix, which will tarpit the remote end by default. There's very little reason to use something like sendmail these days.
It's great to see the Blaxxun people finally come to their senses. I've been mailing them every year for some three years running now, asking about Linux support.
BTW, The Blaxxun community server was ported to Linux YEARS ago, and they were always very upfront about it, recommending the Linux version over the NT version.
> Netscape may even already support this; I'm not sure, though.
Well, considering most of the original LDAP designers now work at Netscape, they arguably have the most advanced LDAP server, and _all_ of their products use LDAP (for configuration etc), it's safe to say that Netscape does LDAP:-)
Netscape's calendar server is 100% LDAP-based; all the meeting info etc is stored on the LDAP server. I'm not sure what the situation is with the calendar client, though.
BTW, LDAP stands for Lightweight Directory Access Protocol, not Local.
Samba has support for LDAP. It's not difficult to set up a box as an LDAP server, and tools do exist (or are easily written) for user administration on an LDAP server.
Slashdot Mirror
They rewrote it from the ground up *again*? Clearly the last few times they did that didn't help. Why should this time be any different?
Why would the people in an open source project waste their time talking to the press to begin with? It's about the code, and scratching an itch, etc. If a journalist wants to know something about the project, he can just look at the website like everybody else.
An open source project is NOT a corporation, and PR is irrelevant.
Developing ideas? Give me a break, they buy patents and sell licenses. It's your basic patent troll outfit.
Larry,
Now would be an excellent time to stop all the self-serving "I helped start all this" publicity. You've had your say, several times over now. The sour grapes thing is getting really old now.
> And $25 for 50 years is a good deal...
No, it's not. First year free while it's an experimental service is a good deal, and you'd actually get people signing up.
$25 just makes the whole thing look like a scam, which is a shame, since it's pretty interesting otherwise.
You can't really slap those kinds of interfaces in cisco's either -- not if you expect them to work, and still be affordable. Juniper would be a better bet, with that kind of load.
I think the OP is talking about lower-end gear anyway, and cisco's low-end routers definitely don't do everything (anything) in hardware.
That's just not true. Get your facts straight.
It would be incompatible with the rest of the world's ssh implementations, of course, but I guess he'd write a DJB-RFC to take care of that.
Make sure you plan some space on every floor for a wiring closet while you still can; more than one for larger floors. Place them so you don't have to do more than about 50m from the closet to workstations. Use cat5 cable from the closets to where people will work. If any consultant or network type tells you to use cat6, fire him.
Plan for at least four patches per desk; people will bring in laptops, or put double the number of people in an office. Don't forget the absolute minimum is two patches per person (computer, phone), and the minimum will last you about a month before people start bringing in little hubs to put on their desk (which you want to avoid).
Between the wiring closets, use fiber. It's not as expensive as you may think, and terminating is quite painless -- many switches have fiber ports or room for fiber modules. You can also use fibercopper transceivers, not too expensive. Use single mode (SM) fiber. You need to do this because a) it can go much longer distances, b) you can happily string it alongside power lines if you need to, and c) because you can upgrade uplinks to gigE without worrying about the cabling.
You'll also need to get copper into the wiring closets though, for connecting the PBX to the phones. Distance isn't such a big problem for those.
If at all possible, get double the number of fiber links that you strictly need. Ideally, string it on different sides of the building or floor. You can't crimp it like you can cat5, and getting fiber types in for a splice takes a while. In a pinch, when one gets cut, it's good to have a guaranteed extra link ready, which is undamaged through following a completely different route.
In the wiring closets, put switches, not hubs. Don't use hubs at all, in fact.
Don't forget that the big cost in laying wire (both cat5 and fiber) is in man-hours, not the terminating equipment or physical cable. Putting in 10 cables isn't that much more expensive than putting in 1, in other words.
You could just upgrade to a modern MTA, such as Postfix, which will tarpit the remote end by default. There's very little reason to use something like sendmail these days.
Asking for the "best alternate root server" is like asking for the "best car crash" to be in. There is no alternative.
Read RFC 2826.
That's what the OSWG is for...
Here is a working mirror...
It's great to see the Blaxxun people finally come to their senses. I've been mailing them every year for some three years running now, asking about Linux support.
BTW, The Blaxxun community server was ported to Linux YEARS ago, and they were always very upfront about it, recommending the Linux version over the NT version.
> Netscape may even already support this; I'm not sure, though.
:-)
Well, considering most of the original LDAP designers now work at Netscape, they arguably have the most advanced LDAP server, and _all_ of their products use LDAP (for configuration etc), it's safe to say that Netscape does LDAP
Netscape's calendar server is 100% LDAP-based; all the meeting info etc is stored on the LDAP server. I'm not sure what the situation is with the calendar client, though.
BTW, LDAP stands for Lightweight Directory Access Protocol, not Local.
Well, they also need to state that the software is licensed under the GPL, and provide pointers to where the source is available.
Samba has support for LDAP. It's not difficult
to set up a box as an LDAP server, and tools do
exist (or are easily written) for user administration on an LDAP server.
Somebody is bound to start working on a GTK implementation...
An open source H323 project recently got started:
http://www.OpenH323.org/
Not much there yet, but it looks promising.