The solution is, of course, obvious. Stop using those name servers. If enough people do this they will fall by the wayside. No reason you *have* to use them.
Only if you consider some random store brand of tool to be comparable to Dewalt. Granted you *can* and I have and do build high end PCs that a pro would be proud to have for a tool. You can also buy Macs (12" iBook in my case) that will take your breath away and make you glad to compute again.
Pros have *always* been willing to pay for their tools and to reject the low end. I have a hard time understading why so many people working with computers have a hard time with this concept. But clearly I'm serious about my tools. This is why a mix of high end PC gear and Macs are my tools of choice.
In what sense is Apple hardware proprietary? Or overpriced for that matter. Specific examples, please.
I'm looking at my iBook and with the exception of the airport not seeing a single component that is proprietary. I can put at least two OSS OSen on it. OpenBSD will work without flaw. Linux can drive everything but the airport but that's not due to not having specs.
Overpriced is another question but I'm not going to go there since so many IT types seem to not understand that great tools are well worth paying for.
Exactly. I always like it when I go to some professional. Lawyer, doctor what have you. You can tell they have been talking to people who don't grok this when they ask what you think they should do. I always answer "You would not tell me how to build a network and I'm not going to tell you how to do $FOO. Do what's best."
If more people had smaller egos and knew their limits life would be much better.
OSS is good no matter what platform you use it on. I don't care what RMS says and I imagine if more folks would give up the whole politcal thing and just focused on quality that things would be better.
Of course I'll not go into the irony of the fact that most of the people doing said whining are using Linux and the contradications that they ignore.
So no OSS on Windows is *good*.
And this from a dedicated OpenBSD and OS X user.:)
The summary was very badly written and I'm sure the quote was lost in translation. If you read the article this sounds a lot like what I do here. I'll give an example.
"Hey, the DNS server is running on a box cobbled together by late-neolithic hunter gathers. We *need* new hardware before this one dies and we are fucked." Sometime later due to the magic of bosses new hardware shows up. "Here's the new DNS server all pre-installed with Red Hat like corporate says it needs to be." "Thanks." Breaks out CD with OpenBSD release songs on and OpenBSD install CDs. Sometime later. "New box is ready to go." Plugs in new box. Runs and admins it like a champ. Nobody but our hero any the wiser as to why it's so easy to admin his boxen and why he doesn't get hit by any of the holes that everybody else does.
Now granted you have to meet a few criteria to be able to do this.
1. You MUST know what you are doing, approach it as a craft and be SHIT hot. 2. Your bosses have got to know in their guts that when the shit hits the fan that you will be there.
If I asked for permission to do the right thing it would be pure hell. As it is because the network is rock solid stable and when there are problems they know I'm there I can do what needs to be done and not have to play any games. Works well for everybody and fuck warm soapy showers with people who couldn't ride herd on a router if you put a gun to their head.
Linking to already public info is hardly a bad thing. Most peope would read yoru intial comment as meaning they linked to private information. This was clearly not the case.
Very likely I just "don't get it". But that is one of the *worst* things I've ever seen. Not to mention that it simply doesn't work in lynx. So no. Please god no.
Exactly. And those who complain about "nasty NAT traversal hacks" seem to always forget that their code has no business caring about layer 3 stuff. If you feel the need to have your code care about layer 3 you need to design better code. That's all there is to it. The fact that it's easier to write borken code is no excuse to write said borken code. And it will still be borken under 6 it'll just be easier to mask. Better to fix the code rather than depending on 6 to mask the borkeness.
Well yes. But, security, like ogres, onions, cake, and parafait should have layers. NAT provides a, yes rather weak, layer. But it is still a layer. So doing both is a good thing.
Slashdot Mirror
pkg_add sense_of_humour
The solution is, of course, obvious. Stop using those name servers. If enough people do this they will fall by the wayside. No reason you *have* to use them.
I was talking about hardware. Software is, of course, different. And you are, of coure, more or less right.
Only if you consider some random store brand of tool to be comparable to Dewalt. Granted you *can* and I have and do build high end PCs that a pro would be proud to have for a tool. You can also buy Macs (12" iBook in my case) that will take your breath away and make you glad to compute again.
Pros have *always* been willing to pay for their tools and to reject the low end. I have a hard time understading why so many people working with computers have a hard time with this concept. But clearly I'm serious about my tools. This is why a mix of high end PC gear and Macs are my tools of choice.
Apple is the Dewalt of the computing world.
In what sense is Apple hardware proprietary? Or overpriced for that matter. Specific examples, please.
I'm looking at my iBook and with the exception of the airport not seeing a single component that is proprietary. I can put at least two OSS OSen on it. OpenBSD will work without flaw. Linux can drive everything but the airport but that's not due to not having specs.
Overpriced is another question but I'm not going to go there since so many IT types seem to not understand that great tools are well worth paying for.
Heh. Yes but which flavour?
http://en.wikipedia.org/wiki/Dictatorship_of_the_p roletariat
Not expressing an opinion on who is right or wrong. But just saying you would do well to get your facts straight.
Exactly. I always like it when I go to some professional. Lawyer, doctor what have you. You can tell they have been talking to people who don't grok this when they ask what you think they should do. I always answer "You would not tell me how to build a network and I'm not going to tell you how to do $FOO. Do what's best."
If more people had smaller egos and knew their limits life would be much better.
What is this "natural daylight" of which you speak?
Sounds exotic and danger filled. I'll pass thanks.
Nuff said.
:)
OSS is good no matter what platform you use it on. I don't care what RMS says and I imagine if more folks would give up the whole politcal thing and just focused on quality that things would be better.
Of course I'll not go into the irony of the fact that most of the people doing said whining are using Linux and the contradications that they ignore.
So no OSS on Windows is *good*.
And this from a dedicated OpenBSD and OS X user.
That's not a juicer, this is a juicer.
The summary was very badly written and I'm sure the quote was lost in translation. If you read the article this sounds a lot like what I do here. I'll give an example.
"Hey, the DNS server is running on a box cobbled together by late-neolithic hunter gathers. We *need* new hardware before this one dies and we are fucked."
Sometime later due to the magic of bosses new hardware shows up.
"Here's the new DNS server all pre-installed with Red Hat like corporate says it needs to be."
"Thanks."
Breaks out CD with OpenBSD release songs on and OpenBSD install CDs. Sometime later.
"New box is ready to go."
Plugs in new box. Runs and admins it like a champ. Nobody but our hero any the wiser as to why it's so easy to admin his boxen and why he doesn't get hit by any of the holes that everybody else does.
Now granted you have to meet a few criteria to be able to do this.
1. You MUST know what you are doing, approach it as a craft and be SHIT hot.
2. Your bosses have got to know in their guts that when the shit hits the fan that you will be there.
If I asked for permission to do the right thing it would be pure hell. As it is because the network is rock solid stable and when there are problems they know I'm there I can do what needs to be done and not have to play any games. Works well for everybody and fuck warm soapy showers with people who couldn't ride herd on a router if you put a gun to their head.
Why would they do their taxes on a firewall?
And you have no idea how much that cracks me up. But PLEASE mod it down.
:)
I should have my browser taken away if I've had less than 2 hours of sleep in the last 36.
No. I'm just an overtired idiot.
Mod it down so that it just goes away, please.
There is no 'h' in "Doctor Who". Try again.
So if that counts. Does this count also.
y +Suite+111+Coral+Gables+Florida&spn=0.006061,0.015 136&t=h&iwloc=A&hl=en
http://maps.google.com/maps?q=1172+South+Dixie+Hw
Linking to already public info is hardly a bad thing. Most peope would read yoru intial comment as meaning they linked to private information. This was clearly not the case.
Point to said "link to his personal info". It ain't there. In fact if you read you will notice that they specifically did *not* link to personal info.
Very likely I just "don't get it". But that is one of the *worst* things I've ever seen. Not to mention that it simply doesn't work in lynx. So no. Please god no.
WTF lets their ISP control *anything* about their firewall and wtf nats on a router.
Oh wait. Lamers who don't know networking.
Either you left out one *very* big detail or we have a case of pilot error. I'm guessing pilot error.
And a link to the Baen CDs themselves. http://oberon.zlynx.org/
Lots of good stuff, licensed to be free as in beer, and with very liberal distribution terms.
Exactly. And those who complain about "nasty NAT traversal hacks" seem to always forget that their code has no business caring about layer 3 stuff. If you feel the need to have your code care about layer 3 you need to design better code. That's all there is to it. The fact that it's easier to write borken code is no excuse to write said borken code. And it will still be borken under 6 it'll just be easier to mask. Better to fix the code rather than depending on 6 to mask the borkeness.
Well yes. But, security, like ogres, onions, cake, and parafait should have layers. NAT provides a, yes rather weak, layer. But it is still a layer. So doing both is a good thing.
How did you get trianing in an army that doesn't exist?