I dunno - I think Guinness is mainly marketing hype. I've had much better stouts, including one brewed locally (Bushy's Oyster Stout - http://www.bushys.com/). I find Guinness has a sort of 'burnt taste' to it. Before you ask, yes I have drunk it in Ireland.
I believe that Budvar is now owned by Anheiser-Busch. Pity. Unfortunately, consolidation amongst brewers is as bad as in any other industry - most famous beers are just brands of $ENORMOUS_CORPORATION now.
The point isn't that the oil is going to "run out" in an absolute sense. There's probably hundreds of years oil out there at current rates.
However, not much of it is CHEAP oil. What is running out, and will probably be gone in the next few years is CHEAP oil.
Re:I want to help the beatles
on
Beatles vs Apple
·
· Score: 5, Funny
Actually, why not?
Southwest Airlines (an airline who actually has a clueful CEO for a change) did almost this. They had an (unintentional) trademark collision with another airline due to a promotion they were running.
Instead of running to the lawyers, Herb Kelleher (CEO of Southwest), challenged the CEO of the other airline (who's name escapes me right now) to an arm wrestling match.
Herb lost; the trademark dispute was resolved in the other airline's favour. No lawyers involved, and it undoubtedly saved both companies a buttload of money.
Doesn't matter what you're running (i.e. old versions of Exchange). For the old-Exchange-org, for their outgoing mail all they have to do is put the TXT records in their DNS. Doesn't matter what their mailer is. For incoming (to use SPF to check incoming mail) all they have to do is have a front-end mail relay in front of their exchange server which deals with the filtering before passing mail onto Exchange -- which they should do anyway, only a nutter exposes an old version of Exchange directly on the internet.
I have a friend in Houston who also confronted a man breaking into his house. He also had a pump-action shotgun. However, in his case, the sound of the pump-action terrified the would-be intruder who took off and ran before he even had to fire a shot.
Why are you missing it? Just point your web browser at http://www.bbc.uk/radio and select Radio 4, then 'Listen Now'. Also any programmes you miss are available for a week under 'Listen Again'. Unfortunately you won't be able to get it in your car lacking a fancy 3G cellphone setup.
The alternative is you can move back to Britain, like I did after 7 years in the US. Not that I dislike living in the US (I enjoyed my time greatly and wouldn't miss it for anything), but the British Isles is my home, and there was just too much I missed from here which *cannot* be streamed over the Internet.
If you've seen the documentary 'Trinity and Beyond', it has footage of the 100 tonne test - 100t of TNT was piled up and exploded to calibrate the Trinity test site instrumentation.
It *looked* for all intents and purposes like a nuclear explosion - bright flash, big fiery mushroom cloud. But it was 100t of TNT.
Actually, it does matter. Although a spam application could create an outbound connection to the spammer, it's of little practical use to a mass-mailer. If the machine is zombified through malware, the AV companies will quickly find out where it's supposed to be connecting during their analysis, inform the ISP who the IP address belongs to (or dyndns service if they use DNS) and have the spammer shut off so he can't even utilize the network. What the malware connects back to will also lead law enforcement back to whoever's utilizing it.
Now in the case of one-off cracking, yes, this is a very valid and real concern (and why the network I administer has egress rules that are every bit as strict as the ingress rules on each firewall) but in the case of bulk mail, it'd be so easy to shut the offender off it'd be totally impractical.
The old fake password dialog isn't that hard in Windows either - all you need to do is develop a replacement GINA (the bit Winlogon calls to popup the login screen), boot the machine with something like the Trinity Rescue Kit, copy in your new GINA, reboot.
Then Ctrl-Alt-Delete will bring up your GINA instead of msgina. Capture passwords at your will.
Of course, the price of entry is a bit higher than making a fake login: prompt at a vt320 terminal, but it's not that difficult for most programmers familiar with Windows (I wrote a complete replacement GINA for a retail application - including changing the GUI to make it look exactly like the rest of the touchscreen driven POS app, which is a hell of a lot more work than writing a simple gina stub for stealing passwords). There are docs from Microsoft on how to write replacement GINAs (and writing them is done - for example, if you're on a Novell network your GINA will be nwgina.dll)
Sounds very Korgo-like; possibly a new variant. (I've seen a Windows network hit by a Korgo variant before the antivirus companies even knew it existed, thus demonstrating that AV software is NOT the silver bullet - none of the existing Korgo tools would remove it).
You're deliberately missing the point. Some apartment complexes don't allow pick-up trucks in the parking lot (although they won't be in Texas). Some apartment complexes don't allow vehicles with business signs on them being parked in the parking lot overnight - which poses no danger and uses no room. Does a station wagon with "Joe's Heating and Plumbing" written in white lettering on the side cause a safety hazard? (It arguably causes LESS safety hazard than an AP - after all, an AP can be plugged into the University network with no security set, and cause a hazard to the campus network)
The point is that a landlord is within their rights to forbid certain physical artefacts from being taken on their property, whether it's a helicopter, a piece of networking equipment or a motor vehicle with writing on the side.
It's quite simple - if students don't agree with the rule, students are free to live off-campus or go to a different university. For what it's worth I think it's stupid to prohibit students from using APs with their own cable modem (i.e. not university network) connections, but I recognise that a university is within its rights to not allow certain things to be kept on campus.
The FCC can rule that you cannot make rules that forbid 802.11 - but they DO NOT have a rule saying landlords cannot forbid certain physical artefacts on their premesis. Just like the university cannot rule that you can't fly a helicopter in the airspace above the campus (because that would pre-empt the FAA), the university can tell you that you're not allowed to keep a helicopter in the parking lot.
They have EVERY right to tell you not to use a legally licensed device in *their* apartment. For example, it's generally legal to keep pets, but it's also perfectly legal for a landlord to forbid renters from keeping pets in their apartment in the lease agreement. It is also perfectly legal for a landlord (like the University) to forbid you from bringing in a wireless access point. Even if they can't forbid you from using the 2.4GHz spectrum (for example, you could design and build your own electronic widget that operates on 2.4GHz but is not a wireless access point), they can still forbid you from bringing certain physical artefacts on campus (such as wireless access point hardware) in the lease agreement.
the rights of the students to use the unlicensed 2.4GHz spectrum in the privacy of their own apartment are obviously being regulated by a body that is not the FCC.
This whole story should be modded Score:-1, Overrated. A university apartment is *not* the student's property - it's *university* property and the university can impose regulations like this as they see fit. The FCC aren't going to care if a university prohibits the use of a non-University provided AP, there's no law stopping the University from forbidding the use of random APs brought in by students. If the student doesn't like the policy they are free to rent privately or go to another university. It's no different from a rule, say, forbidding students or staff from landing helicopters in the parking lot. That's not pre-empting the FAA which regulates airspace - it's simply the landowner (the university) imposing conditions of using their land.
Many apartment complexes have rules like you can't change your car's oil in their parking lot. This is really no different - if you don't like the rule, rent an apartment where the rules don't forbid 802.11b. It's entirely reasonable for the university to restrict 802.11b access points being plugged into *their* network too from a security point of view (non-secured AP + wardriver = nice big hole through any firewall they have).
I dunno what you mean by 'advanced' support for 3D accelerators (I'm very impressed at how well RTCW:ET runs on FC2 running the X.Org X server - it's at least twice as fast as XFree86 on RH8.0 on the same machine) but the 3D support is getting better all the time; it's just a real shame the NVidia driver isn't open source.
Talking of games - the fundamental network design of X and the display program being the X server (essentially a daemon) means my Windows-using ET playing friends are envious of how I play the game in Linux. I simply start up a second X server. That's all there is to having two entirely separate desktops on one machine. Just start another desktop. The clients (such as my game) don't even have to be aware of this functionality - they just display to unix:1 instead of unix:0, as set in the DISPLAY environment variable. I can hot key between the two desktops with Ctrl-Alt-F7 and Ctrl-Alt-F8, so I can run ET in fullscreen and easily flick back to IRC.
No, the X Server is the program for displaying stuff. X11R6 just specifies a standard protocol. The protocol doesn't need to be a network one (and on your local machine, none of the X clients talk over your TCP/IP stack).
Anyone can implement an X server that adheres to the X11R6 protocol (and several UNIX vendors have; in the closed-source UNIX world Sun has their own implementation, and I bet all the others have too, although they may be based on the reference implementation - the old X Consortium X server). In the open source world, we have two implementations (which are very similar but now diverging - the XFree server and the X.Org server)
I don't know the historic reasons for why X was designed because I was only a small child in 1986 (I dare say somewhere on the Internet has the story as to why it was made in the way it was), but separating the client and the server like they have is extremely useful - the client doesn't care where the X server is or what the X server is. It means the client is well decoupled from the implementation of the X server - an X client running on HP/UX will display correctly on an X.Org X server running on Linux and you don't need to worry about DLL hell to make it all work - it just works. It's a very clean design and that's one of the reasons it's lasted so long.
As for the different implementations, X clients (i.e your programs) aren't linked to the X server or its header files. OpenWindows could be a radically different internal design with no header files in common with X.Org's server. What the clients link to is not the X server's header files - but XLib. XLib implements the client part of the deal, including the header files a C programmer would use. And XLib isn't linked to the X Server - it implements the X protocol (and that's why a Linux program written with Vendor A's xlib will work fine with Vendor B's X server running on some completely different architecture).
X is the protocol. X11 is the 11th version of the X protocol (the first version of the X protocol I saw was X10, and that was some time ago on an already ancient machine). X11R6 means the X Window System, Version 11, Release 6 - that's the basic protocol level.
The.8.0 bit at the end is X.Org's specific version numbers for their implementation of the X11R6 protocol. (Other organizations implement X11R6, such as Sun - they call their version of X11R6 OpenWindows).
I believe there was a prototype windowing system called W that preceeded X, but that's now ancient history (the first X Window System implementation to run was in the mid 1980s).
That has happened in the past with the Soviets and the US - witness Vietnam and Afghanistan. Both were proxy wars - one of the belligerents would be fighting, and the other would be supplying the opposition, like we supplied the Mujahadeen, and the Soviets supplied the Vietnamese. It's unlikely the two superpowers would come to direct blows because the consequences would be the end of civilization as we know it. Once one party finds itself losing, the use of nuclear weapons would become inevitable and then the exchange would probably escalate until before you know it, each side has lobbed a gigaton's worth at each other and completely destroyed themselves as a country.
So they basically won't let it go beyond a proxy war, and yes, one side will end up backing down - just like the Soviets in Afghanistan, and the US in Vietnam.
Since the Flash memory can take something like 10,000 rewrites, and copying (rather than using the dongle as working storage) only does one rewrite per time, if you're doing daily backups it'd take 30 years to kill it from writing.
It's already happening with CD-Rs. I've found several that read once or twice then are dead - usually cheap ones (never had that problem with something like Verbatim disks). I've also found plenty of CD-Rs that read fine in one drive but not in another.
Eww. I wouldn't put Active Directory on any untrusted network (and a network with students on is probably the definition of untrusted). Any vulns uncovered in AD leads to the greatest potential yet of 0wning every machine on campus.
Slashdot Mirror
I dunno - I think Guinness is mainly marketing hype. I've had much better stouts, including one brewed locally (Bushy's Oyster Stout - http://www.bushys.com/). I find Guinness has a sort of 'burnt taste' to it. Before you ask, yes I have drunk it in Ireland.
I believe that Budvar is now owned by Anheiser-Busch. Pity. Unfortunately, consolidation amongst brewers is as bad as in any other industry - most famous beers are just brands of $ENORMOUS_CORPORATION now.
The trouble is that stuff you're drinking isn't beer - it's lager. This is beer: http://www.bushys.com/
The point isn't that the oil is going to "run out" in an absolute sense. There's probably hundreds of years oil out there at current rates.
However, not much of it is CHEAP oil. What is running out, and will probably be gone in the next few years is CHEAP oil.
Actually, why not?
Southwest Airlines (an airline who actually has a clueful CEO for a change) did almost this. They had an (unintentional) trademark collision with another airline due to a promotion they were running.
Instead of running to the lawyers, Herb Kelleher (CEO of Southwest), challenged the CEO of the other airline (who's name escapes me right now) to an arm wrestling match.
Herb lost; the trademark dispute was resolved in the other airline's favour. No lawyers involved, and it undoubtedly saved both companies a buttload of money.
Doesn't matter what you're running (i.e. old versions of Exchange). For the old-Exchange-org, for their outgoing mail all they have to do is put the TXT records in their DNS. Doesn't matter what their mailer is. For incoming (to use SPF to check incoming mail) all they have to do is have a front-end mail relay in front of their exchange server which deals with the filtering before passing mail onto Exchange -- which they should do anyway, only a nutter exposes an old version of Exchange directly on the internet.
I have a friend in Houston who also confronted a man breaking into his house. He also had a pump-action shotgun. However, in his case, the sound of the pump-action terrified the would-be intruder who took off and ran before he even had to fire a shot.
Why are you missing it? Just point your web browser at http://www.bbc.uk/radio and select Radio 4, then 'Listen Now'. Also any programmes you miss are available for a week under 'Listen Again'. Unfortunately you won't be able to get it in your car lacking a fancy 3G cellphone setup.
The alternative is you can move back to Britain, like I did after 7 years in the US. Not that I dislike living in the US (I enjoyed my time greatly and wouldn't miss it for anything), but the British Isles is my home, and there was just too much I missed from here which *cannot* be streamed over the Internet.
The BBC have a "Listen Again" feature. Anything broadcast by BBC Radio 4 is available for a week from the BBC's website.
If you've seen the documentary 'Trinity and Beyond', it has footage of the 100 tonne test - 100t of TNT was piled up and exploded to calibrate the Trinity test site instrumentation.
It *looked* for all intents and purposes like a nuclear explosion - bright flash, big fiery mushroom cloud. But it was 100t of TNT.
Actually, it does matter. Although a spam application could create an outbound connection to the spammer, it's of little practical use to a mass-mailer. If the machine is zombified through malware, the AV companies will quickly find out where it's supposed to be connecting during their analysis, inform the ISP who the IP address belongs to (or dyndns service if they use DNS) and have the spammer shut off so he can't even utilize the network. What the malware connects back to will also lead law enforcement back to whoever's utilizing it.
Now in the case of one-off cracking, yes, this is a very valid and real concern (and why the network I administer has egress rules that are every bit as strict as the ingress rules on each firewall) but in the case of bulk mail, it'd be so easy to shut the offender off it'd be totally impractical.
The old fake password dialog isn't that hard in Windows either - all you need to do is develop a replacement GINA (the bit Winlogon calls to popup the login screen), boot the machine with something like the Trinity Rescue Kit, copy in your new GINA, reboot.
Then Ctrl-Alt-Delete will bring up your GINA instead of msgina. Capture passwords at your will.
Of course, the price of entry is a bit higher than making a fake login: prompt at a vt320 terminal, but it's not that difficult for most programmers familiar with Windows (I wrote a complete replacement GINA for a retail application - including changing the GUI to make it look exactly like the rest of the touchscreen driven POS app, which is a hell of a lot more work than writing a simple gina stub for stealing passwords). There are docs from Microsoft on how to write replacement GINAs (and writing them is done - for example, if you're on a Novell network your GINA will be nwgina.dll)
Most Linux distros turn the firewall on by default. Without root access, they won't be listening to any port, privileged or unprivileged.
Sounds very Korgo-like; possibly a new variant. (I've seen a Windows network hit by a Korgo variant before the antivirus companies even knew it existed, thus demonstrating that AV software is NOT the silver bullet - none of the existing Korgo tools would remove it).
You're deliberately missing the point. Some apartment complexes don't allow pick-up trucks in the parking lot (although they won't be in Texas). Some apartment complexes don't allow vehicles with business signs on them being parked in the parking lot overnight - which poses no danger and uses no room. Does a station wagon with "Joe's Heating and Plumbing" written in white lettering on the side cause a safety hazard? (It arguably causes LESS safety hazard than an AP - after all, an AP can be plugged into the University network with no security set, and cause a hazard to the campus network)
The point is that a landlord is within their rights to forbid certain physical artefacts from being taken on their property, whether it's a helicopter, a piece of networking equipment or a motor vehicle with writing on the side.
It's quite simple - if students don't agree with the rule, students are free to live off-campus or go to a different university. For what it's worth I think it's stupid to prohibit students from using APs with their own cable modem (i.e. not university network) connections, but I recognise that a university is within its rights to not allow certain things to be kept on campus.
The FCC can rule that you cannot make rules that forbid 802.11 - but they DO NOT have a rule saying landlords cannot forbid certain physical artefacts on their premesis. Just like the university cannot rule that you can't fly a helicopter in the airspace above the campus (because that would pre-empt the FAA), the university can tell you that you're not allowed to keep a helicopter in the parking lot.
They have EVERY right to tell you not to use a legally licensed device in *their* apartment. For example, it's generally legal to keep pets, but it's also perfectly legal for a landlord to forbid renters from keeping pets in their apartment in the lease agreement. It is also perfectly legal for a landlord (like the University) to forbid you from bringing in a wireless access point. Even if they can't forbid you from using the 2.4GHz spectrum (for example, you could design and build your own electronic widget that operates on 2.4GHz but is not a wireless access point), they can still forbid you from bringing certain physical artefacts on campus (such as wireless access point hardware) in the lease agreement.
This whole story should be modded Score:-1, Overrated. A university apartment is *not* the student's property - it's *university* property and the university can impose regulations like this as they see fit. The FCC aren't going to care if a university prohibits the use of a non-University provided AP, there's no law stopping the University from forbidding the use of random APs brought in by students. If the student doesn't like the policy they are free to rent privately or go to another university. It's no different from a rule, say, forbidding students or staff from landing helicopters in the parking lot. That's not pre-empting the FAA which regulates airspace - it's simply the landowner (the university) imposing conditions of using their land.
Many apartment complexes have rules like you can't change your car's oil in their parking lot. This is really no different - if you don't like the rule, rent an apartment where the rules don't forbid 802.11b. It's entirely reasonable for the university to restrict 802.11b access points being plugged into *their* network too from a security point of view (non-secured AP + wardriver = nice big hole through any firewall they have).
I dunno what you mean by 'advanced' support for 3D accelerators (I'm very impressed at how well RTCW:ET runs on FC2 running the X.Org X server - it's at least twice as fast as XFree86 on RH8.0 on the same machine) but the 3D support is getting better all the time; it's just a real shame the NVidia driver isn't open source.
Talking of games - the fundamental network design of X and the display program being the X server (essentially a daemon) means my Windows-using ET playing friends are envious of how I play the game in Linux. I simply start up a second X server. That's all there is to having two entirely separate desktops on one machine. Just start another desktop. The clients (such as my game) don't even have to be aware of this functionality - they just display to unix:1 instead of unix:0, as set in the DISPLAY environment variable. I can hot key between the two desktops with Ctrl-Alt-F7 and Ctrl-Alt-F8, so I can run ET in fullscreen and easily flick back to IRC.
No, the X Server is the program for displaying stuff. X11R6 just specifies a standard protocol. The protocol doesn't need to be a network one (and on your local machine, none of the X clients talk over your TCP/IP stack).
Anyone can implement an X server that adheres to the X11R6 protocol (and several UNIX vendors have; in the closed-source UNIX world Sun has their own implementation, and I bet all the others have too, although they may be based on the reference implementation - the old X Consortium X server). In the open source world, we have two implementations (which are very similar but now diverging - the XFree server and the X.Org server)
I don't know the historic reasons for why X was designed because I was only a small child in 1986 (I dare say somewhere on the Internet has the story as to why it was made in the way it was), but separating the client and the server like they have is extremely useful - the client doesn't care where the X server is or what the X server is. It means the client is well decoupled from the implementation of the X server - an X client running on HP/UX will display correctly on an X.Org X server running on Linux and you don't need to worry about DLL hell to make it all work - it just works. It's a very clean design and that's one of the reasons it's lasted so long.
As for the different implementations, X clients (i.e your programs) aren't linked to the X server or its header files. OpenWindows could be a radically different internal design with no header files in common with X.Org's server. What the clients link to is not the X server's header files - but XLib. XLib implements the client part of the deal, including the header files a C programmer would use. And XLib isn't linked to the X Server - it implements the X protocol (and that's why a Linux program written with Vendor A's xlib will work fine with Vendor B's X server running on some completely different architecture).
X is the protocol. X11 is the 11th version of the X protocol (the first version of the X protocol I saw was X10, and that was some time ago on an already ancient machine). X11R6 means the X Window System, Version 11, Release 6 - that's the basic protocol level.
.8.0 bit at the end is X.Org's specific version numbers for their implementation of the X11R6 protocol. (Other organizations implement X11R6, such as Sun - they call their version of X11R6 OpenWindows).
The
I believe there was a prototype windowing system called W that preceeded X, but that's now ancient history (the first X Window System implementation to run was in the mid 1980s).
That has happened in the past with the Soviets and the US - witness Vietnam and Afghanistan. Both were proxy wars - one of the belligerents would be fighting, and the other would be supplying the opposition, like we supplied the Mujahadeen, and the Soviets supplied the Vietnamese. It's unlikely the two superpowers would come to direct blows because the consequences would be the end of civilization as we know it. Once one party finds itself losing, the use of nuclear weapons would become inevitable and then the exchange would probably escalate until before you know it, each side has lobbed a gigaton's worth at each other and completely destroyed themselves as a country.
So they basically won't let it go beyond a proxy war, and yes, one side will end up backing down - just like the Soviets in Afghanistan, and the US in Vietnam.
Since the Flash memory can take something like 10,000 rewrites, and copying (rather than using the dongle as working storage) only does one rewrite per time, if you're doing daily backups it'd take 30 years to kill it from writing.
That's probably good enough.
It's already happening with CD-Rs. I've found several that read once or twice then are dead - usually cheap ones (never had that problem with something like Verbatim disks). I've also found plenty of CD-Rs that read fine in one drive but not in another.
Eww. I wouldn't put Active Directory on any untrusted network (and a network with students on is probably the definition of untrusted). Any vulns uncovered in AD leads to the greatest potential yet of 0wning every machine on campus.