I thought the leaky capacitors out of Taiwan was a story from 2000. Four years later, it seems a little unfair to associate the two. (Who knows how rare these events are, anyway?)
Actually, every time I've seen that it was a problem with the CRT. The vacuum tube got hot, and melted the solder contacts on the board the tube is connected to. So now I've got three old monitors where the green contact is intermittent, leaving only blue and red. (And thus magenta.)
That's crazy. If someone's DNS server isn't retiring an old entry that puts my domain at an improper address, I want to be able to reach them with as little hassle as possible. Not demand contact information from my friends in Australia who pointed out that they couldn't get to my site.
(That's happened to me, BTW... www.grnet.com somehow ended up having an old DNS entry with a fubar'd expiration date, but only on a high-level machine in Australia.)
Or, a proper knocking sequence issues iptables commands to translate/forward all packets from the knocking IP address to a given host on the internal network. For a given amount of time, or until a signal is sent by the host being forwarded to.
It would be very easy to implement this using the ULOG target in iptables. Have a userland app watch the log file, and issue iptables commands when a pattern is matched.
OS X has a monstrous commercial backing that has usability at or near the top of its agenda. Even if there ar emore Linux boxen than OS X boxen out there, the average home user is more likely to have heard of Macs than Linux.
Also, Linux and BSD(therefore OS X) aren't from the same codebase. They have roughly the same structure, and they often run the same programs, but that's it.
It's an old argument. Putting aside the "Which one is used more" argument, I feel that Macs are less likely to be infected because the platform was built from the ground up with security in mind. (OS X is a descendant of OpenBSD, no?)
mmm...it would be really nice if data structures in memory could be virtually contiguous, but physically fragmented. realloc could be so much faster...:)
You mean branch prediction? They did some serious improvements to Prescott's branch prediction in order to compensate for the performance losses that come from having such a long pipeline (or, rather, the performance losses that come from not keeping that pipeline full.).
Somehow I doubt G5s and G4s are used in military/space applications. Components for use in those areas have to be hardened against radiation and the elements pretty damn well. You don't normally see consumer-performance processers in such extreme environments. (Not saying it's impossible, though. I've seen some pretty damn tough x86 laptops.)
Firestone's still not very popular, at least where I'm from.
I thought the leaky capacitors out of Taiwan was a story from 2000. Four years later, it seems a little unfair to associate the two. (Who knows how rare these events are, anyway?)
Actually, every time I've seen that it was a problem with the CRT. The vacuum tube got hot, and melted the solder contacts on the board the tube is connected to. So now I've got three old monitors where the green contact is intermittent, leaving only blue and red. (And thus magenta.)
Depending on Mozilla for better standards support is just as bad as depending on IE for its quirks.
The javascript developers during the browser wars had the right idea, even if they hated their jobs.
You'd need something like SpeedStep to make power usage significantly related to load.
I'm reminded of the phrase "They say a girl never forgets the first time she was kissed by a lizard." (Anyone mind citing where that came from?
Sure, if you could get them to give you an integer. I guess a graduated scale wouldn't be too bad. Anyone happen to know the different levels?
What, writing raw ethernet packets won't work?
WHOIS would be best shut down.
That's crazy. If someone's DNS server isn't retiring an old entry that puts my domain at an improper address, I want to be able to reach them with as little hassle as possible. Not demand contact information from my friends in Australia who pointed out that they couldn't get to my site.
(That's happened to me, BTW... www.grnet.com somehow ended up having an old DNS entry with a fubar'd expiration date, but only on a high-level machine in Australia.)
The funny thing is, why open up ports in a general fashion? Why not just open up those ports to connections from the IP that knocked?
Better yet, only forward connections from a specific IP to an internet machine. Much more secure.
Or, a proper knocking sequence issues iptables commands to translate/forward all packets from the knocking IP address to a given host on the internal network. For a given amount of time, or until a signal is sent by the host being forwarded to.
You're right, the possibilities are endless.
It would be very easy to implement this using the ULOG target in iptables. Have a userland app watch the log file, and issue iptables commands when a pattern is matched.
Sounds like fun, actually.
That's also why we like the BOFH. I let a user catch me printing them out once...didn't have any more trouble from him
OS X has a monstrous commercial backing that has usability at or near the top of its agenda. Even if there ar emore Linux boxen than OS X boxen out there, the average home user is more likely to have heard of Macs than Linux.
Also, Linux and BSD(therefore OS X) aren't from the same codebase. They have roughly the same structure, and they often run the same programs, but that's it.
It's an old argument. Putting aside the "Which one is used more" argument, I feel that Macs are less likely to be infected because the platform was built from the ground up with security in mind. (OS X is a descendant of OpenBSD, no?)
Us tutors in computer labs
Us support technicians
Us customer service people in general.
Pray for us, lest we do something totally irrational, illegal and damning.
What?! I can't believe--come here! Come here you little--!
Well, you'll certainly be registered as having skipped check-out on at least a few of the store's products...
Right, but nobody can track thousands of people simultaneously and find patterns and "alleged links with so-and-so" with a computer.
Well, Chicago's traffic system uses RFID tags that are read from much farther away than two feet.
(chuckle)
Does anyone else remember the first celerons? When they got rid of the cache? (Then the later ones, when they started putting the cache on-die?)
mmm...it would be really nice if data structures in memory could be virtually contiguous, but physically fragmented. realloc could be so much faster... :)
You mean branch prediction? They did some serious improvements to Prescott's branch prediction in order to compensate for the performance losses that come from having such a long pipeline (or, rather, the performance losses that come from not keeping that pipeline full.).
Somehow I doubt G5s and G4s are used in military/space applications. Components for use in those areas have to be hardened against radiation and the elements pretty damn well. You don't normally see consumer-performance processers in such extreme environments. (Not saying it's impossible, though. I've seen some pretty damn tough x86 laptops.)
I'd hate to have to keep out an extra box in order to play FF 7-9. I've been meaning to try out "Carnage Heart", for a while now, too.