Most gamers have more in common with the Comic Book Guy than hackers. True there is overlap but the geeks outraged about this are the ones who see their freedom to tinker in peril. Most gamers don't tinker (apart from things like (sanctioned) mods) with the guts of their systems.
It seems to me that you can implement a DRM scheme and GPL3 the code. What you can't do is use DRM to circumvent the intent of the GPL the way Tivo does with their signed kernels. If you do it anyway and attempt to use the DMCA or a DMCA like law against anyone who circumvented it, then the license provides a potent legal defense. Of course, it could be the language needs to be tightened up but that is what seems to be the FSF's intent: you will not use technological means to prevent downstream recipients from modifying the code.
I doubt that it is the FSF's intent to stop people from legally using GPG or deploying things like Dansguardian (can "spy" on users) on internal networks. The issue seems to be access to the software and it's workings not private data. If I'm wrong and that IS the intent, then I don't see the license being viable in the real world.
bk tries to be all things to all developers. Git only tries to be exactly what the Linux Kernel project needs. A major point McVoy missed when slagging off the git developers is that a particular solution for a particular problem can always be developed faster than a general solution for all problems. Git being useful for anyone else is gravy.
The temperature will fall off very very rapidly as the plasma expands. Also, fusion reactors can be built inside the same sort of vaults that fission reactors are built in. If the reactor explodes, there is no need to take a building with it. Messy.
Thing is, time travel into the future is nothing more than a severe engineering problem. Simply accellerate away from the Earth to a significant fraction of the speed of light and return. The clocks on board your ship (as well as any other process in time) will run slow relative to the ones back on Earth. When you return, you will have travelled "into the future" according to how close to lightspeed you got, how long it took to attain that speed, and the amount of time you spent at it.
There is nothing scientifically wrong with it.
Time travel into the past on the other hand......well just forget it.
I never thought about this nor ran into this problem. Thank you for the hint. When I upgrade the drives, I'll certainly do this. Also, I do use nfs as well. Samba from KDE is Klunky:-)
If you're just saving and loading user created files from the Netatalk share, it is almost never a problem. Human users tend not to make "FILE" and "File" in the same directory.
It is when software is maintains it's own files on the shares that things get ugly. I have to maintain servers that house the data for educational software like "Reading Counts" and "Star Reading". Those absolutely will not work served from case-sensitive filesystems. What happens is something like this:
Software installer creates DATABASE.DBX.
Client software attempts to read data located within database.dbx and maybe even tries to write back to Database.dbx.
I've also found that Hyperstudio (a sorta modern Hypercard for K-12 use) will break on case-sensitive fileshares even though humans are creating and naming the data. Quark Publisher is another app in which case-sensitive hilarity can ensue. Every once in a (great) while even Office for Mac seems to have trouble with this.
Incidentally, you can try my idea out pretty much risk free without reformatting everything. Do this:
dd if=/dev/zero of=loopback.img bs=1M count=256 (creates a 256MB file of zeros. size this however you like)
mkfs.jfs -O loopback.img (may have to install jfsutils on your system)
mount -t jfs loopback.img/(mountpoint) -o loop
Open AppleVolumes.default in an editor and add:/(mountpoint) "Case-Preserving Share"
I also highly recommend the last release from netatalk.sourceforge.net. Some distros still seem to include ancient netatalk releases. You probably want to be running 2.0.3.
Format the filesystem that you intend to serve with Netatalk thusly
mkfs.jfs -O/dev/hdX (the "O" is an uppercase "O" as in "Oscar")
This formats the filesystem with "OS/2 Compatibility" which means that it is case-preserving like HFS and NTFS. In other words "file" and "File" and "FILE" would all refer to the same file and only one of those variations could be used as a filename in a directory on this filesystem. Samba will enforce case-preserving semantics on case-sensitive underlying filesystems by default. If a Linux server will only be serving Windows clients then samba+Linux default case-sensitive filesystems is perfectly fine.
Netatalk will not enforce case-preservation and this can break Mac applications if their data is stored on case-sensitive underlying filesystems. Unless "case-folding" is used which forces filenames to be all upper or lower-cased, Netatalk simply lets the underlying filesystem namespace behaivor show through. From the Finder, you can indeed create "file", "FILE", and "File" in same shared directory if is something like reiserfs or ext3.
I've been experimenting with this for awhile and I've found that only JFS is suitable for the purpose. Firstly, it is actively maintained and robust when put into operation. Linux native utilities can create and fsck the filesystems. Performance is at least acceptable even if other choices like ext2 can be a little faster. Finally, the filesystem can be created to explictly support only case-preserving behaivor. HFS, HFS+, NTFS, FAT, and HPFS are other routes to attempt this with. Either the filesystem is buggy for read/write as in the case of HFS+ or support is incomplete like NTFS or bizzare things happen in the case of FAT and HFS(severe filename limitations here). HPFS works well but I have never succeeded in finding the necessary accompanying mkfs and fsck utilities for Linux.
The downside is Linux native scripts and apps that rely on case-sensitivity may break but those can be run on other filesystems if all else fails. The server needs to give the client what it expects. I have to support Mac apps that use data stored in a server share while still allowing human users of the shares to name files the way they are accustomed to naming files. This method supports both those goals well.
There isn't anything wrong that either. These days the manufacturers of consumers devices all go the extra mile to keep people from hacking their own kit. It will be nice to have some kit that invites you to play with it...even if that is all it is good for.
I had already been thinking of the GP32 and it's descendents as portable versions of the XGamestation. The only reason the hardware exists is to learn how consoles work at a very low level. I approve of more of that sort of thing. Not less.
I keep waiting for someone to hack the gene for THC production into an orange tree or something, too. That'll make life interesting for the DEA when someone does that...
I've had the same thought but think lawn grass would be even better. It would be harder to police and would give a whole new meaning to "smoking grass".
The amount of fallout from a high altitude airburst is indeed low. You have little more than vaporized bomb components and maybe a little irridated water vapor. A low altitude detonation is another kettle of fish altogether. The explosion will suck up significant amounts of ground clutter and irridate it for falling back to earth. A ground level or just under the ground detonation is the worst of all. Structures and a large amount of ground itself are vaporized and will be carried on prevailing winds. As with the low altitude detonation, dirt, dust, and debris will be sucked from the surrounding environs and made radioactive.
>> Just goes to show people don't become criminals because they're smart.
No, the smart criminals just don't get caught.
The smart criminals also get full value for the risk they're taking. If you're going to steal something, make sure at least 6 figures are involved. Being caught and convicted almost certainly means one will never get decent work again even if the sentence is light. The potential loss of a lifetime's good salaries means that taking a $500 bike is stupid. It really only pays to steal big. To hell with Wal-Mart. Wall Street and politics are far more profitable places for the larcenous minded to be.
Well, Sun's Open Source credibility is increasing. Now that they've decided to open source everything, it will only improve more.
Only if they refrain from further schzoid episodes. This week they like Open Source and are ready to compete with products rather than lawyers. Next week, they could be threatening the Harmony project and making subtle patent threats. You never really know where you will stand with Sun next month, next year, or even tomorrow.
If they hold their present course and keep their mouths and their lawyers in check then we may see the improvement you speak of.
For years, Debian warns you that a glibc update will require particular services to be restarted. If you go ahead and install, then it restarts those for you.
Too true. Unfortunately I had to go with Camino on the OS X desktops I manage because Firefox wasn't doing things like quitting correctly among other assorted bits of flakiness. Camino feels like driving the economy model car with power nothing on it but it does have a working engine and brakes.
Even if Firefox on OS X does get ironed out, I'll probably have to stay with Camino as most of my users are highly brittle. Changing the least thing on their machines breaks them.
Why does it seem to some that humans can not bring about climate change? Our population keeps swelling, we keep burning fossil fuels and chopping down trees. Do you think we are unable to produce enough greenhouse gases? Is nature so vast and giant that humans seem to dwindle in strength? We humans are a part of nature. Locusts can devour forests. Why can't us humans ravage the earth?
The planet is fine. The planet isn't going anywhere. We are!
The Earth will not lose the ability to support life. Even all out USSR USA nucular war would not remove the ability to support life, as cockroaches would still be around...
Except that the only thing left to eat will be a warehouse full of fruitcake. The cockroaches will all starve to death.
Why would carbon levels go back to equilibrium? What time scale are you expecting for this?
On some time scale at least they would. Life processes sequestered the carbon in the first place. Existing life processes are capable of sequestering some fixed amount of carbon per year as it is. The problem is that humans are putting it in the atmosphere faster than all life can process it. If that were to stop, biological processes would catch up. I couldn't tell you when though.
Artic land rush...... now you know what the plan is.
Antarctic land rush. The artic pole will be nothing but a chilly sea if the ice melts. Hardly any land mass up there to speak of. Antarctica has a continental landmass underneath it's cap.
LCD and Plasma tvs depend on many aspects of physics for their operations. Physics has a pesky habit of informing you that the universe is billions of years old.
Set IE for the 'High'est possible level of security and only trust the work email to any degree. This will make IE little better than lynx for most sites.
The hard part will be building TCPA into a virtual machine. Emulating the TCPA hardware itself doesn't seem to be a biggie. Having the keys to load into it is. I suspect that the VMware people won't be issued keys that the Windows DRM will respect. It won't be possible to trivially extract the keys from real hardware to use in the VM because they will be buried deep in the silicon itself. They'll likely contain all sorts of tricksy hashes meant to verify they're being used with the correct hardware. Everything possible is being done to put the strongest features of upcoming DRM deep inside hardware.
I also strongly suspect the "tamper proof" chips will turn out to have feet of clay but the attacks will probably require equipment the typical geek doesn't have in his junk box. It will also likely be the case that the Windows devs or a chipset manufacturer will miss something and provide the needed wedge to regain owner control of this obnoxiousness. It will take legally impeded time though.
Slashdot Mirror
Most gamers have more in common with the Comic Book Guy than hackers. True there is overlap but the geeks outraged about this are the ones who see their freedom to tinker in peril. Most gamers don't tinker (apart from things like (sanctioned) mods) with the guts of their systems.
It seems to me that you can implement a DRM scheme and GPL3 the code. What you can't do is use DRM to circumvent the intent of the GPL the way Tivo does with their signed kernels. If you do it anyway and attempt to use the DMCA or a DMCA like law against anyone who circumvented it, then the license provides a potent legal defense. Of course, it could be the language needs to be tightened up but that is what seems to be the FSF's intent: you will not use technological means to prevent downstream recipients from modifying the code.
I doubt that it is the FSF's intent to stop people from legally using GPG or deploying things like Dansguardian (can "spy" on users) on internal networks. The issue seems to be access to the software and it's workings not private data. If I'm wrong and that IS the intent, then I don't see the license being viable in the real world.
bk tries to be all things to all developers. Git only tries to be exactly what the Linux Kernel project needs. A major point McVoy missed when slagging off the git developers is that a particular solution for a particular problem can always be developed faster than a general solution for all problems. Git being useful for anyone else is gravy.
almost only counts in horseshoes and handgrenades.
The temperature will fall off very very rapidly as the plasma expands. Also, fusion reactors can be built inside the same sort of vaults that fission reactors are built in. If the reactor explodes, there is no need to take a building with it. Messy.
Thing is, time travel into the future is nothing more than a severe engineering problem. Simply accellerate away from the Earth to a significant fraction of the speed of light and return. The clocks on board your ship (as well as any other process in time) will run slow relative to the ones back on Earth. When you return, you will have travelled "into the future" according to how close to lightspeed you got, how long it took to attain that speed, and the amount of time you spent at it.
There is nothing scientifically wrong with it.
Time travel into the past on the other hand......well just forget it.
I never thought about this nor ran into this problem. Thank you for the hint. When I upgrade the drives, I'll certainly do this. Also, I do use nfs as well. Samba from KDE is Klunky :-)
If you're just saving and loading user created files from the Netatalk share, it is almost never a problem. Human users tend not to make "FILE" and "File" in the same directory.
It is when software is maintains it's own files on the shares that things get ugly. I have to maintain servers that house the data for educational software like "Reading Counts" and "Star Reading". Those absolutely will not work served from case-sensitive filesystems. What happens is something like this:
Software installer creates DATABASE.DBX. Client software attempts to read data located within database.dbx and maybe even tries to write back to Database.dbx.I've also found that Hyperstudio (a sorta modern Hypercard for K-12 use) will break on case-sensitive fileshares even though humans are creating and naming the data. Quark Publisher is another app in which case-sensitive hilarity can ensue. Every once in a (great) while even Office for Mac seems to have trouble with this.
Incidentally, you can try my idea out pretty much risk free without reformatting everything. Do this:
dd if=/dev/zero of=loopback.img bs=1M count=256 (creates a 256MB file of zeros. size this however you like)
mkfs.jfs -O loopback.img (may have to install jfsutils on your system)
mount -t jfs loopback.img /(mountpoint) -o loop
Open AppleVolumes.default in an editor and add: /(mountpoint) "Case-Preserving Share"
I also highly recommend the last release from netatalk.sourceforge.net. Some distros still seem to include ancient netatalk releases. You probably want to be running 2.0.3.
Format the filesystem that you intend to serve with Netatalk thusly
/dev/hdX (the "O" is an uppercase "O" as in "Oscar")
mkfs.jfs -O
This formats the filesystem with "OS/2 Compatibility" which means that it is case-preserving like HFS and NTFS. In other words "file" and "File" and "FILE" would all refer to the same file and only one of those variations could be used as a filename in a directory on this filesystem. Samba will enforce case-preserving semantics on case-sensitive underlying filesystems by default. If a Linux server will only be serving Windows clients then samba+Linux default case-sensitive filesystems is perfectly fine.
Netatalk will not enforce case-preservation and this can break Mac applications if their data is stored on case-sensitive underlying filesystems. Unless "case-folding" is used which forces filenames to be all upper or lower-cased, Netatalk simply lets the underlying filesystem namespace behaivor show through. From the Finder, you can indeed create "file", "FILE", and "File" in same shared directory if is something like reiserfs or ext3.
I've been experimenting with this for awhile and I've found that only JFS is suitable for the purpose. Firstly, it is actively maintained and robust when put into operation. Linux native utilities can create and fsck the filesystems. Performance is at least acceptable even if other choices like ext2 can be a little faster. Finally, the filesystem can be created to explictly support only case-preserving behaivor. HFS, HFS+, NTFS, FAT, and HPFS are other routes to attempt this with. Either the filesystem is buggy for read/write as in the case of HFS+ or support is incomplete like NTFS or bizzare things happen in the case of FAT and HFS(severe filename limitations here). HPFS works well but I have never succeeded in finding the necessary accompanying mkfs and fsck utilities for Linux.
The downside is Linux native scripts and apps that rely on case-sensitivity may break but those can be run on other filesystems if all else fails. The server needs to give the client what it expects. I have to support Mac apps that use data stored in a server share while still allowing human users of the shares to name files the way they are accustomed to naming files. This method supports both those goals well.
It's a hobbyist's toy, nothing more.
There isn't anything wrong that either. These days the manufacturers of consumers devices all go the extra mile to keep people from hacking their own kit. It will be nice to have some kit that invites you to play with it...even if that is all it is good for.
I had already been thinking of the GP32 and it's descendents as portable versions of the XGamestation. The only reason the hardware exists is to learn how consoles work at a very low level. I approve of more of that sort of thing. Not less.
I keep waiting for someone to hack the gene for THC production into an orange tree or something, too. That'll make life interesting for the DEA when someone does that...
I've had the same thought but think lawn grass would be even better. It would be harder to police and would give a whole new meaning to "smoking grass".
The amount of fallout from a high altitude airburst is indeed low. You have little more than vaporized bomb components and maybe a little irridated water vapor. A low altitude detonation is another kettle of fish altogether. The explosion will suck up significant amounts of ground clutter and irridate it for falling back to earth. A ground level or just under the ground detonation is the worst of all. Structures and a large amount of ground itself are vaporized and will be carried on prevailing winds. As with the low altitude detonation, dirt, dust, and debris will be sucked from the surrounding environs and made radioactive.
How can you say that fallout is a minor concern?
Wow. I'm from Cleveland and i totally know what you are talking about man!!
I believe The Mistake On The Lake is what you were trying to say.
Amarok doesn't store the lyrics. You have to cut and paste them yourself if you want a permanent record.
>> Just goes to show people don't become criminals because they're smart. No, the smart criminals just don't get caught.
The smart criminals also get full value for the risk they're taking. If you're going to steal something, make sure at least 6 figures are involved. Being caught and convicted almost certainly means one will never get decent work again even if the sentence is light. The potential loss of a lifetime's good salaries means that taking a $500 bike is stupid. It really only pays to steal big. To hell with Wal-Mart. Wall Street and politics are far more profitable places for the larcenous minded to be.
Well, Sun's Open Source credibility is increasing. Now that they've decided to open source everything, it will only improve more.
Only if they refrain from further schzoid episodes. This week they like Open Source and are ready to compete with products rather than lawyers. Next week, they could be threatening the Harmony project and making subtle patent threats. You never really know where you will stand with Sun next month, next year, or even tomorrow.
If they hold their present course and keep their mouths and their lawyers in check then we may see the improvement you speak of.
For years, Debian warns you that a glibc update will require particular services to be restarted. If you go ahead and install, then it restarts those for you.
Too true. Unfortunately I had to go with Camino on the OS X desktops I manage because Firefox wasn't doing things like quitting correctly among other assorted bits of flakiness. Camino feels like driving the economy model car with power nothing on it but it does have a working engine and brakes.
Even if Firefox on OS X does get ironed out, I'll probably have to stay with Camino as most of my users are highly brittle. Changing the least thing on their machines breaks them.
Lex? Is that you?
Why does it seem to some that humans can not bring about climate change? Our population keeps swelling, we keep burning fossil fuels and chopping down trees. Do you think we are unable to produce enough greenhouse gases? Is nature so vast and giant that humans seem to dwindle in strength? We humans are a part of nature. Locusts can devour forests. Why can't us humans ravage the earth?
The planet is fine. The planet isn't going anywhere. We are!
The Earth will not lose the ability to support life. Even all out USSR USA nucular war would not remove the ability to support life, as cockroaches would still be around...
Except that the only thing left to eat will be a warehouse full of fruitcake. The cockroaches will all starve to death.
Why would carbon levels go back to equilibrium? What time scale are you expecting for this?
On some time scale at least they would. Life processes sequestered the carbon in the first place. Existing life processes are capable of sequestering some fixed amount of carbon per year as it is. The problem is that humans are putting it in the atmosphere faster than all life can process it. If that were to stop, biological processes would catch up. I couldn't tell you when though.
Artic land rush...... now you know what the plan is.
Antarctic land rush. The artic pole will be nothing but a chilly sea if the ice melts. Hardly any land mass up there to speak of. Antarctica has a continental landmass underneath it's cap.
LCD and Plasma tvs depend on many aspects of physics for their operations. Physics has a pesky habit of informing you that the universe is billions of years old.
Set IE for the 'High'est possible level of security and only trust the work email to any degree. This will make IE little better than lynx for most sites.
The hard part will be building TCPA into a virtual machine. Emulating the TCPA hardware itself doesn't seem to be a biggie. Having the keys to load into it is. I suspect that the VMware people won't be issued keys that the Windows DRM will respect. It won't be possible to trivially extract the keys from real hardware to use in the VM because they will be buried deep in the silicon itself. They'll likely contain all sorts of tricksy hashes meant to verify they're being used with the correct hardware. Everything possible is being done to put the strongest features of upcoming DRM deep inside hardware.
I also strongly suspect the "tamper proof" chips will turn out to have feet of clay but the attacks will probably require equipment the typical geek doesn't have in his junk box. It will also likely be the case that the Windows devs or a chipset manufacturer will miss something and provide the needed wedge to regain owner control of this obnoxiousness. It will take legally impeded time though.