Of course it's not implausable. Linux has it's place, as does everything. But when a person says 'I'm implementing Linux, but suddenly have noticed that there's no way to do X...' it probably means that the move to Linux isn't being driven by need, or by product worthiness. To slightly mangle a phrase, due dilligence hasn't been performed.
"If you are dragging your office (kicking and screaming, no less) into the dynamic and typically, more affordable world of Linux and Open Source...
...then you are obviously less enthralled with the idea of 'customer service' and 'using the right tool for the right job' than with 'trying to look 1337 by forcing my preferences on everybody else without even checking to see if my idea will work for everything that the office needs to be able to do.'
In this case, the peeping parent is not giving his child freedom (to look at freely available information privately) or responsibility.
You know, I sat down ready to start the rant, but then I thought, 'why bother?' If you honestly believe that letting a child metaphorically run free, then nothing I say will change that perception.
Yes, and they also took responsibility for their actions. If a young Roman nobleman went after somebody with a sword, he could expect to either win, or be killed in turn. If some 13 year old kid from Philly shoots somebody, he gets a slap on the wrist in Juvenile court, which winds up the same as being encouragement.
So you're saying that the MPAA doesn't have the freedom of speech to say 'we think that this movie is not appropriate for anybody under 18, and therefore we choose not to show it in the theaters we own?'
They're not saying 'You cannot watch these movies,' they're saying 'You cannot watch these movies in our venues.' Much like if you showed up at a buddy's house with the all new DVD of Goatse.cx IV - The Reckoning (with directors commentary) and he refused to watch it, he's not violating anything.
So if I tell you to send me a file using 'file transfer protocol' you're going to assume that I mean good old RFCd FTP, port 21, all that crap? Or are you going to assume I mean HTTP? ICQ file send? MSN file send? SMTP MIME? scp? rcp? Zmodem over telnet?
The poster above IS saying that Voice Over IP, the protocol used in all sorts of hardware and software, is NO different from 'voice over IP', or any form of protocol involving TCP/IP and transmission of voice. By his defintion, VoIP could involve FTPing sound files.
VoIP is a specific technology, with a specific implementation. Hell, Linksys's new Cable/DSL router has a VoIP option; plug a regular phone into the assigned jack, and tell people to point their VoIP software at the router's IP address, and if somebody calls, it rings the phone.
Do NOT teach packages or applications. Hell, don't teach Linux. TEACH THEORY.
If your kids understand what a HTTP server is, what virtual hosts are, SSL, realms authentication, all that stuff, then sure, they can apply it to Apache. Or iPlanet. Or IIS. Or whatever.
Similarly, teach them package management. Explain about databases, conflicts, auto-changing of conf files, etc. Then, they'll be able to figure out Solaris pkgadd, RPM, DEB, etc etc.
The only thing worse than having no virus protection is having inadequate virus protection that gives users a false sense of security. Besides, if there's no updates, traffic will be minimal.:-)
I'd say every week at a minimum. Find out when your provider puts out their 'scheduled' releases (Trend, for example, is every Tuesday, IIRC) and do it then.
A friend of mine and I were thinking about incorporating and going into consulting, when be both realized that we'd need somebody to do that business shit. I could do the networking and OS shit, and me buddy could do the hardcore programming shit, but neither one of us would be good at accounting, negotiation, you know, that business shit.
Therefore, we fully intend, if we ever do incorporate, to hire somebody with the title "Director of That Business Shit."
We have a server set up at work to be a honeypot. It has one DNS entry, but is not linked to by anything, is not advertised in any way, is not pointed to by any MX, NS or other service type record. In other words, nobody who's not specifically doing blanket scans should ever find it.
When somebody tries to interact with a service on it, say, FTP, not only does it keep a full record of the session, it also portscans them, fingers them, WHOISs them, tries to get banners from their FTP, mail, and web servers, and all that good stuff. Why? Because there is NO reason that anybody would ever hit it. So we want to know about the people who are.
if they're worried about whats on unclassified machines, then somebody's not doing their job
Remind me never to hire you for a computer security position.
BECAUSE they're worried about what might be on an unclassified machine, they ARE doing their jobs. You don't stay secure by making assumptions. Period. You do it right, every time.
That just means that the life expectancy of the unit is, say, three years. At that point, either they drop support for the older hardware, or expect it to die a natural death, or expect everybody to have upgraded anyway.:-)
Exactly. So if you've got, say, 40 years left, being, say, 40 when the clone was made, the clone would expire in ~40 years. In theory, you'd die at pretty much the same time. You'd be (base age) + (TTL) and the clone would be (TTL), but you'd both die (TTL) years after the cloning occured.
I think it's supposed to be a joke. DivX is easily counted as 'the Bose of video codecs; most people think it's great, but anybody who knows better knows it sucks.'
No highs, no lows, must be Bose.
"Why bother? You know that the only reason the US lifted the export ban on high encryption is because the boys and girls down at NSA finally figured out a way to crack it with ease."
Slashdot Mirror
Of course it's not implausable. Linux has it's place, as does everything. But when a person says 'I'm implementing Linux, but suddenly have noticed that there's no way to do X...' it probably means that the move to Linux isn't being driven by need, or by product worthiness. To slightly mangle a phrase, due dilligence hasn't been performed.
Yes, and they also took responsibility for their actions. If a young Roman nobleman went after somebody with a sword, he could expect to either win, or be killed in turn. If some 13 year old kid from Philly shoots somebody, he gets a slap on the wrist in Juvenile court, which winds up the same as being encouragement.
To further your analogy, I should stand over my children with a large stick, keep them from wandering off the grass, and shave them occasionally.
So you're saying that the MPAA doesn't have the freedom of speech to say 'we think that this movie is not appropriate for anybody under 18, and therefore we choose not to show it in the theaters we own?' They're not saying 'You cannot watch these movies,' they're saying 'You cannot watch these movies in our venues.' Much like if you showed up at a buddy's house with the all new DVD of Goatse.cx IV - The Reckoning (with directors commentary) and he refused to watch it, he's not violating anything.
Spoken like a child who is not ready to accept the fact that with freedom comes responsibility.
As was mentioned elsewhere, IE6 ships with smarttags disabled by default.
So if I tell you to send me a file using 'file transfer protocol' you're going to assume that I mean good old RFCd FTP, port 21, all that crap? Or are you going to assume I mean HTTP? ICQ file send? MSN file send? SMTP MIME? scp? rcp? Zmodem over telnet? The poster above IS saying that Voice Over IP, the protocol used in all sorts of hardware and software, is NO different from 'voice over IP', or any form of protocol involving TCP/IP and transmission of voice. By his defintion, VoIP could involve FTPing sound files. VoIP is a specific technology, with a specific implementation. Hell, Linksys's new Cable/DSL router has a VoIP option; plug a regular phone into the assigned jack, and tell people to point their VoIP software at the router's IP address, and if somebody calls, it rings the phone.
That's like saying that any protocol that transfers files over the Internet should be called 'File Transfer Protocol' and is equally stupid.
Do NOT teach packages or applications. Hell, don't teach Linux. TEACH THEORY. If your kids understand what a HTTP server is, what virtual hosts are, SSL, realms authentication, all that stuff, then sure, they can apply it to Apache. Or iPlanet. Or IIS. Or whatever. Similarly, teach them package management. Explain about databases, conflicts, auto-changing of conf files, etc. Then, they'll be able to figure out Solaris pkgadd, RPM, DEB, etc etc.
The only thing worse than having no virus protection is having inadequate virus protection that gives users a false sense of security. Besides, if there's no updates, traffic will be minimal. :-)
I'd say every week at a minimum. Find out when your provider puts out their 'scheduled' releases (Trend, for example, is every Tuesday, IIRC) and do it then.
No. By definition, a CNAME points to another hostname. Much like, by definition, a chocolate bar is primarily made of chocolate.
A friend of mine and I were thinking about incorporating and going into consulting, when be both realized that we'd need somebody to do that business shit. I could do the networking and OS shit, and me buddy could do the hardcore programming shit, but neither one of us would be good at accounting, negotiation, you know, that business shit. Therefore, we fully intend, if we ever do incorporate, to hire somebody with the title "Director of That Business Shit."
"Next time, don't use an acronym on my business cards. Use my full title - Director Of Product Enhancements." "I didn't realize that was your title."
We have a server set up at work to be a honeypot. It has one DNS entry, but is not linked to by anything, is not advertised in any way, is not pointed to by any MX, NS or other service type record. In other words, nobody who's not specifically doing blanket scans should ever find it. When somebody tries to interact with a service on it, say, FTP, not only does it keep a full record of the session, it also portscans them, fingers them, WHOISs them, tries to get banners from their FTP, mail, and web servers, and all that good stuff. Why? Because there is NO reason that anybody would ever hit it. So we want to know about the people who are.
Actually, an acid bath is the generally accepted way to prevent a disk from ever being read again.
That just means that the life expectancy of the unit is, say, three years. At that point, either they drop support for the older hardware, or expect it to die a natural death, or expect everybody to have upgraded anyway. :-)
Exactly. So if you've got, say, 40 years left, being, say, 40 when the clone was made, the clone would expire in ~40 years. In theory, you'd die at pretty much the same time. You'd be (base age) + (TTL) and the clone would be (TTL), but you'd both die (TTL) years after the cloning occured.
I think it's supposed to be a joke. DivX is easily counted as 'the Bose of video codecs; most people think it's great, but anybody who knows better knows it sucks.' No highs, no lows, must be Bose.
"Why bother? You know that the only reason the US lifted the export ban on high encryption is because the boys and girls down at NSA finally figured out a way to crack it with ease."
I could be wrong, but isn't it 'karoshi?' "Work death" would be the translation, I think.