Here you have a case where you are willing to pay for a legitimate product but you are unable to acquire it due to arbitrary and pointless restrictions.
It's the same sort of problem as DRM. Region locking, device locking... primarily serve to piss off customers. So go wild.
(When you CAN legitimately purchase the product you desire, of course, piracy thereof becomes a totally different matter).
Let me summarize your requirements -> Runs cool and quiet -> Heat, humidity, dust resistant -> Portable -> Low power requirements -> Integrated UPS -> Very beefy server -> Cheap
If you find one drop me an email, I want to install Duke Nukem Forever on it.
A lot of (most?) people do it this way -- the kernel and wine for example. There is a "central" server that everyone commits to. Beauty of distributed version control is that you don't need to be connected to branch, commit, bisect, checkout, etc. You can sit in a coffee shop, implement five features, commit them all separately, and then push those commits to the central repo when you have access.
Or, if you're in a coffee shop, and you find a regression, you can bisect and check out revisions to check until you find it, write a fix and commit it, all without needing a connection.
There's no way to pull from a repo that's behind a NAT unless you have sufficient control over the NAT to forward a particular port to a specific machine behind it. This is the same as svn -- how can you access an svn server that's behind a NAT? Only by having its relevant port forwarded.
However, if you are in a coffee shop and you want Sue to have your devel history, you can push to Sue instead of having Sue pull from you. Sue will then merge your pushed changes into her working copy when she feels like it.
Equivalently, you can set up another git repository on your home server which has a static IP. Then, you pull from and push to your home server, which you can access from anywhere with your laptop, and other people also pull from your home server. I used this approach when I was developing from home and didn't have time to make sure permissions on everything were okay and granting other developers ssh accounts on my machine, and didn't have time to set up an http server for the repo.
I don't understand why they made IPv6 the way they did.
Sure, the size of the new address space is absolutely staggering, but this was done at the expense of making them impossible for a person to remember. Right now, I can go to some internet cafe and ssh into my home network because I can remember the IP.
Were I using an IPv6 address, I would have to pay for DNS service just so I could log into my own network remotely, or keep a scrap of paper and laboriously type it out.
Why not extend IPv4 by adding more bits to the representation of each octet? For example, instead of using 8 bits, use x bits where x is specified at the beginning of the address. For example, you can use x=10 and create an address up to 1024.1024.1024.1024.
This still allows people to remember them easily, as there is no difference between remembering, say, 189 and 857 from a human brain perspective. It's three digits in each case. And, you can go as high as you need to. You can never deplete it, as you can just keep using more bits to represent the address when necessary, and all of the applications supporting such a protocol would be able to support that natively.
Best of all, assume x=8 unless explicitly specified, and voila -- perfect backwards compatibility with the existing IPv4 protocol. You no longer need to have separate treatment of IPv4 and next-gen address spaces, because IPv4 will be a subset of the expanded space.
Why the current mess of horrible alphanumeric sequences? Why didn't they make it easy on our eyes and do it like this?
Somewhere in our basement there is still an old machine which dual-boots windows 3.1 and windows 95A.
It probably doesn't boot anymore, as it was having motherboard problems late in life, but a year or so ago I converted it to a virtual machine image under qemu. I can, within 5 minutes, boot a virtual machine into a legal copy of windows 3.1 that runs and contains useful applications that we don't have equivalents for.
It's amazing that all this software still exists and is used by people, even after 18 years. Old tech is not as dead as you might think.
Here is your first official list of jokes. Please contribute.
1. You're still running ext4? I can't believe it's not ButterFS! 2. But will it run on toast? 3. Will fsck be renamed to butterknife? 4. If your system overheats will your filesystem melt? 5. If you use ButterFS too much, will it turn into FAT? 6. If you leave ButterFS on your volume too long, will your hard drive start to reek? 7. Will the next version of ButterFS be called GoatButterFS, just like the next version of Leopard is Snow Leopard? 8. "Tough" notebooks will never have their hard drives formatted with ButterFS, because if you dropped them, they would always land hard drive down. 9. When you submit your dead ButterFS hard drive to a data recovery centre, will they have an intern lick it to get the data off instead of putting it under a read head?
These are getting kind of desperate -- your turn now.
Honestly, what is it with FOSS and crappy names? (looking at you, gimp)
The world is coming to people bitching and moaning whenever any of their precious stability in life is taken away.
I'd agree for a lot of things (facebook, flickr), but for google the change really blows.
It's funny how that works -- while changes don't affect you personally or you don't mind them, the people who are upset are "bitching" and "moaning" about it. Yet, suddenly, when you are ticked off about a change, it's suddenly "abrupt and unwelcome" and you "don't agree" complaining about it is bitching.
I'm not a conservative, but I respect that part of the conservative ideology. Is this thing being changed for a good reason, or is it being changed for the sake of putting up something new? Even if this change doesn't affect me, if people start changing things for the sake of change, maybe the next one will affect me, or the next.
Almost no one is really bitching and moaning about these changes -- they all have legitimate complaints, and so will you when something you like changes. Don't call them names; put yourself in their shoes.
We didn't have any stories on the bank collapses, we didn't have any stories on the bill itself, we didn't have any stories on Canada preparing for election... why isn't the politics section used for politics anymore? It seems we only have stories directly relating to tech these days, which is a shame as there are other categories on Slashdot and people have lots of insight about them and would like to discuss them.
Can we stop trying to artificially narrow Slashdot's audience and actually discuss things of more general interest than new developments in number crunching?
Is there a reason this update is happening so much more quickly than other transitions? Are they trying to overcome problems that FF3 introduced? Do they want to add some features that are close to completion, but got shelved?
This article makes it seem like it is possible to use the GPUs as general purpose CPUs. Is that the case? If so, why doesn't NVIDIA or especially AMD\ATI start putting its GPUs on motherboards? At a ratio of 8:300, a single high-end GPU seems to be able to do the work of dozens of high-end CPUs. They'd utterly wipe out the competition. Why haven't they put something like this out yet?
So in other words, Novell tells us that the Microsoft deal was a mistake, when the result is appeasing those who are mad at them for betraying open-source to Microsoft. Now? Oh look, there's more money to be made -- by the way, it was a good idea after all.
All this will do is establish a link between Linux and Microsoft patents in this unstable software market; a link which I assume Microsoft wants be able to export to software markets in the US. China is a big corporate player, and if they're able to say that MS approved Linux is being sold in China, they are much more likely to be able to swindle naive CEOs into paying for MS Linux here as well.
Anyone else getting tired of this general corporate swindling?
Great news, but it doesn't matter to me anymore. I already pirated it from bittorrent.
Read that again. I was so desperate to make it work I had to STEAL FIXES for an operating system I LEGALLY BOUGHT.
Says a lot about Vista, doesn't it.
I am going to replace your comparison with the topic at hand because you've forgotten what we're talking about.
Of course they shouldn't. If someone is so brain damaged that they can't figure out that a FLASHLIGHT can hurt them, why shouldn't they suffer the consequences?
You can't protect stupid people from themselves, and you shouldn't try. It just encourages the spread of stupidity among the general population.
Is it at all possible to close the browser and use the tablet as a proper computer? That would be magical.
With matters like these, fortunately, the solution is very simple
Here it is:
http://thepiratebay.org/
Here you have a case where you are willing to pay for a legitimate product but you are unable to acquire it due to arbitrary and pointless restrictions.
It's the same sort of problem as DRM. Region locking, device locking ... primarily serve to piss off customers. So go wild.
(When you CAN legitimately purchase the product you desire, of course, piracy thereof becomes a totally different matter).
Let me summarize your requirements
-> Runs cool and quiet
-> Heat, humidity, dust resistant
-> Portable
-> Low power requirements
-> Integrated UPS
-> Very beefy server
-> Cheap
If you find one drop me an email, I want to install Duke Nukem Forever on it.
5 minutes? I thought Goldfish had a memory of more or less 3 seconds.
That's actually a pretty common what the hell were we talking about?
A lot of (most?) people do it this way -- the kernel and wine for example. There is a "central" server that everyone commits to. Beauty of distributed version control is that you don't need to be connected to branch, commit, bisect, checkout, etc. You can sit in a coffee shop, implement five features, commit them all separately, and then push those commits to the central repo when you have access.
Or, if you're in a coffee shop, and you find a regression, you can bisect and check out revisions to check until you find it, write a fix and commit it, all without needing a connection.
Is this story's bar red for anyone else on the front page? It's freaking me out. Is the beer robot mad at me? :(
There's no way to pull from a repo that's behind a NAT unless you have sufficient control over the NAT to forward a particular port to a specific machine behind it. This is the same as svn -- how can you access an svn server that's behind a NAT? Only by having its relevant port forwarded.
However, if you are in a coffee shop and you want Sue to have your devel history, you can push to Sue instead of having Sue pull from you. Sue will then merge your pushed changes into her working copy when she feels like it.
Equivalently, you can set up another git repository on your home server which has a static IP. Then, you pull from and push to your home server, which you can access from anywhere with your laptop, and other people also pull from your home server. I used this approach when I was developing from home and didn't have time to make sure permissions on everything were okay and granting other developers ssh accounts on my machine, and didn't have time to set up an http server for the repo.
I don't understand why they made IPv6 the way they did.
Sure, the size of the new address space is absolutely staggering, but this was done at the expense of making them impossible for a person to remember. Right now, I can go to some internet cafe and ssh into my home network because I can remember the IP.
Were I using an IPv6 address, I would have to pay for DNS service just so I could log into my own network remotely, or keep a scrap of paper and laboriously type it out.
Why not extend IPv4 by adding more bits to the representation of each octet? For example, instead of using 8 bits, use x bits where x is specified at the beginning of the address. For example, you can use x=10 and create an address up to 1024.1024.1024.1024.
This still allows people to remember them easily, as there is no difference between remembering, say, 189 and 857 from a human brain perspective. It's three digits in each case. And, you can go as high as you need to. You can never deplete it, as you can just keep using more bits to represent the address when necessary, and all of the applications supporting such a protocol would be able to support that natively.
Best of all, assume x=8 unless explicitly specified, and voila -- perfect backwards compatibility with the existing IPv4 protocol. You no longer need to have separate treatment of IPv4 and next-gen address spaces, because IPv4 will be a subset of the expanded space.
Why the current mess of horrible alphanumeric sequences? Why didn't they make it easy on our eyes and do it like this?
Again? Didn't they come out with software to detect this sort of thing last time it happened?
https://addons.mozilla.org/en-US/firefox/addon/364
https://addons.mozilla.org/en-US/firefox/addon/4550
Somewhere in our basement there is still an old machine which dual-boots windows 3.1 and windows 95A.
It probably doesn't boot anymore, as it was having motherboard problems late in life, but a year or so ago I converted it to a virtual machine image under qemu. I can, within 5 minutes, boot a virtual machine into a legal copy of windows 3.1 that runs and contains useful applications that we don't have equivalents for.
It's amazing that all this software still exists and is used by people, even after 18 years. Old tech is not as dead as you might think.
Butter FS? Are you kidding me?
Here is your first official list of jokes. Please contribute.
1. You're still running ext4? I can't believe it's not ButterFS!
2. But will it run on toast?
3. Will fsck be renamed to butterknife?
4. If your system overheats will your filesystem melt?
5. If you use ButterFS too much, will it turn into FAT?
6. If you leave ButterFS on your volume too long, will your hard drive start to reek?
7. Will the next version of ButterFS be called GoatButterFS, just like the next version of Leopard is Snow Leopard?
8. "Tough" notebooks will never have their hard drives formatted with ButterFS, because if you dropped them, they would always land hard drive down.
9. When you submit your dead ButterFS hard drive to a data recovery centre, will they have an intern lick it to get the data off instead of putting it under a read head?
These are getting kind of desperate -- your turn now.
Honestly, what is it with FOSS and crappy names? (looking at you, gimp)
The world is coming to people bitching and moaning whenever any of their precious stability in life is taken away.
I'd agree for a lot of things (facebook, flickr), but for google the change really blows.
It's funny how that works -- while changes don't affect you personally or you don't mind them, the people who are upset are "bitching" and "moaning" about it. Yet, suddenly, when you are ticked off about a change, it's suddenly "abrupt and unwelcome" and you "don't agree" complaining about it is bitching.
I'm not a conservative, but I respect that part of the conservative ideology. Is this thing being changed for a good reason, or is it being changed for the sake of putting up something new? Even if this change doesn't affect me, if people start changing things for the sake of change, maybe the next one will affect me, or the next.
Almost no one is really bitching and moaning about these changes -- they all have legitimate complaints, and so will you when something you like changes. Don't call them names; put yourself in their shoes.
But can you teach them to type??
Of course; that's how they expect their thesis to be written.
Whacking the guy you stole it from over the head with it to stop him being a crybaby about it.
We didn't have any stories on the bank collapses, we didn't have any stories on the bill itself, we didn't have any stories on Canada preparing for election... why isn't the politics section used for politics anymore? It seems we only have stories directly relating to tech these days, which is a shame as there are other categories on Slashdot and people have lots of insight about them and would like to discuss them.
Can we stop trying to artificially narrow Slashdot's audience and actually discuss things of more general interest than new developments in number crunching?
All Debian releases are named after Toy Story characters. Lenny is a pair of binoculars with feet.
Is there a reason this update is happening so much more quickly than other transitions? Are they trying to overcome problems that FF3 introduced? Do they want to add some features that are close to completion, but got shelved?
This article makes it seem like it is possible to use the GPUs as general purpose CPUs. Is that the case? If so, why doesn't NVIDIA or especially AMD\ATI start putting its GPUs on motherboards? At a ratio of 8:300, a single high-end GPU seems to be able to do the work of dozens of high-end CPUs. They'd utterly wipe out the competition. Why haven't they put something like this out yet?
So in other words, Novell tells us that the Microsoft deal was a mistake, when the result is appeasing those who are mad at them for betraying open-source to Microsoft. Now? Oh look, there's more money to be made -- by the way, it was a good idea after all. All this will do is establish a link between Linux and Microsoft patents in this unstable software market; a link which I assume Microsoft wants be able to export to software markets in the US. China is a big corporate player, and if they're able to say that MS approved Linux is being sold in China, they are much more likely to be able to swindle naive CEOs into paying for MS Linux here as well. Anyone else getting tired of this general corporate swindling?
As opposed to all the other Linux distros which try to be hard to use?
Great news, but it doesn't matter to me anymore. I already pirated it from bittorrent. Read that again. I was so desperate to make it work I had to STEAL FIXES for an operating system I LEGALLY BOUGHT. Says a lot about Vista, doesn't it.
[[citation needed]]
Improv Everywhere's site is down; here is the blog entry from laughingsquid.com: http://laughingsquid.com/best-buy-cease-desist-letter/ And the letter itself on flickr: http://www.flickr.com/photo_zoom.gne?id=2103448719&size=l