Nothing the Japanese, the Protectors or the Puppeteers can do in materials will be able to succeed until they can counterbalance it. That involves mass. Clarke used an asteroid, "moved" into position.
I'm not saying it can't be done (in this post;-). I'm saying it can't be done for 10 Bills.
Ok, maybe if they devise a way to collect all of the space junk into a blob. Maybe launch a 100m blob of chewing gum against the orbital grain to absorb the detritus to get things started.
Counterbalance? That's the easy part. All it has to do is be equal to the mass of the rest of the cable, and be located in an appropriate position to make the center of mass of the whole contraption be at Geo-Synchronous Orbit.
Want to know the easy way to do that? Just double the length of the cable. If you can successfully make a 22,236mi cable, then chances are good that you can also successfully make a 44,472mi cable.
This also has the added benefit that the far end of the cable at 2x GSO makes an excellent slingshot for launching vehicles to other planets.
It isn't your idea of an edge that is invalid, it is how you are viewing expansion that is invalid.
You equated expansion to a circle expanding along the surface of a torus, then meeting on the other side. Your example is of an object exploding within a toroidal surface. Similar to, but not the same as, a one dimensional universe expanding within a 2 dimensional toroidal surface of fixed size.
The expansion of the universe is the torus itself getting bigger. Draw a few dots on a balloon, put a C clamp in the middle (to represent the empty middle; if you have toroidal balloons, skip this step), and inflate the balloon. Expansion of the 2 dimensional toroidal surface is measurable by the change in distance between the dots on the surface.
Time unfortunately doesn't work quite like a normal spatial dimension, since objects travelling along the time dimension usually can only move in one direction, so I cannot say what a result would be for time which 'wraps'. (There are postulated geometries of space, particularly those related to frame dragging around large black holes, for which an object could appear to have moved backwards in the time direction relative to another part of the universe, but within its own reference frame, it would have always been moving forward in the time direction.)
But it's time the legal profession was reigned in over their bogus lawsuits. The legal profession has a perfectly functional (but slow) system of dealing with bogus lawsuits. The legal profession has a perfectly fictional system of dealing with bogus lawsuits.
I just don't see how this would would allow for moore's law to be broken. The largest FPGA I have been taught about (and gotten to use) had 22,000 transistors on it, I thought your average CPU was supposed to have billions.
I think that the whole point of this new technology is that it allows FPGA transistor density to approach much closer to the density found in a static ASIC, since current FPGA chips waste about 80% to 90% of their space with interconnects and signal routing paths.
I don't know if this would allow for faster frequencies on the FPGA, but it is a definite improvement for transistor count.
There are some newer features available in the ext3 codebase in newer 2.6.x kernels that will not work in some older kernels with ext2, regardless of whether it is unmounted cleanly, namely directory hashing, large inode support, extended attributes, fast extended attributes, and acls (which embed themselves in the extended attributes).
There may be more, I haven't been digging into the code myself lately, not for the last couple of years, anyway.
Now I only played D&D (the table-top RPG) for a few months on the weekend with a group of friends. I didn't really get into that either (they took it WAY too slow, all had characters in levels 3-4 after playing this certain campaign for easily 3 years), but I don't remember any instances where we had to break into a room, and destroy tons of barrels to find this "hidden" key.
In pen&paper, that's the kind of thing that gets glossed over with a "search check". Or just say that you destroy every barrel in the room untill you find it. It's as simple as the player maybe saying one sentence, and perhaps having to roll the dice once or twice.
If your tabletop DM were to try to run a game like an MMO does, he would have set down miniatures of their characters and each barrel, and the conversation might have gone something like this:
Player1: I destroy all the barrels untill I find the key. DM: Ok, which barrel do you destroy? Player1: All of them. DM: No, which one do you bash in first? Player1: Alright, I'll play along, the one on the left. DM: Ok, make an attack roll. Player2: It's a barrel, it ain't going anywhere! DM: I have to know how much damage you do to the barrel. Player1: I'm just beating on it untill it's destroyed! DM: But you didn't roll to attack, how can you know if you really hit it? Player3: I fireball all the barrels. Does that destroy them? DM checks his notes, measures the room for radius of effect of the fireball, then replaces mini barrels with mini piles of ash. DM: Yes, that destroys them. Player1: Ok, so we have the key now. I just dug around in the ash untill I found it. DM: No, which pile of ash are you going to search? Players all stuff the pile of minis down the DM's throat.
The shared-network directive is definitely the way to go. We use this on our (university) network to force users to register their machines with us so we can keep track of who owns what machine. One subnet is assigned for all unknown-hosts, and is blocked at the firewall, and the other is assigned to all known-hosts and is allowed out to the world.
Republicans are for the Death Penality and Opposed to Abortions. These two confelct on the ideals of Value of any human life.
As one who is in favor of the death penalty, and opposed to abortion, I have never looked at it in terms of the value of human life, but rather the value of innocence. Those who are guilty of a crime must take responsibility for their actions and accept their punishment. An unborn infant is innocent and has done nothing but simply exist.
LVM2 is not in this kernel, nor will it appear in any 2.4 kernel. Marcello has stated quite clearly that he believes it belongs in 2.6.x only, and will not ever add it to 2.4.
Why can I drink on Friday without a hangover, but when it comes Monday morning my head is being pounded by sledgehammers?
Easy, you probably just drank enough that you were still drunk on Saturday and Sunday. My own record in that regards is 3 days. The hangover lasted for a good portion of the following week too.
Yes, it does. My calc1 prof showed us the proof. I can't remember the whole proof (it's been many many years since i took calc1), but here's the gist of the idea:
start with 0.9, you add 0.1 to it to get 1. then look at 0.99, you add 0.01 to it to get 1. now look at 0.999, you add 0.001 to it to get 1. repeating infinitely, you would eventually need an infinite number of zeros before the 1 to be able to add it to the repeating 9.
That infinitessimally small number actually turns out to be equal to zero, thus, 0.9(repeating) is equal to 1.
Gas appliances are fairly uncommon in North America. The majority of stoves, hot water heaters, etc, are electric.
Not in many rural areas (especially around the midwest). Propane is much more common than electric for hot water heaters and stoves, mostly because it is considerably cheaper. Plus, it has the added benifit that it keeps working if the electricity gets knocked out, which isn't too uncommon every few winters that we have a bad ice storm and the electricity is off for a week (usually happens once every 6 to 8 years).
It's all about the principle of NIH (Not Invented Here). Many places have the mindset that if I/we didn't make it ourselves, then it can't possibly be of any use to us. I bet that it is because of this particular mindset that Intel had to play like it was their idea all along.
And last I looked ACL support was still not quite stable in ext2/3 it has been awhile so it could be stable by now.
As of the patch for kernels 2.4.19+, acl support is very stable for ext[23]. In fact, I've been using it in production for over 2 years now. (I did help write some of the ext3-xattr+acl code, though, so maybe that means I'm a little bit more trusting of the code.)
The only big issues I've ever had is when using them in conjunction with quotas, but even when stress testing the filesystem, I haven't been able to coerce the code to crash since the 2.4.19 patch.
There is a performance hit to NFS when using the ACL-over-NFS code, but you never see it unless you're reading or writing the ACLs themselves. (ie. only when you're using `star --acl` to backup or restore files with their acls, or using a recursive (get|set)facl on an NFS mount.) Of course, the nfs code is less tested, so if you try it and have problems, please submit bugs to acl-devel@bestbits.at
An easy way to keep different applications separated into their own directories, and not have a nightmare managing $PATH would be to create something like/etc/path, which would contain several little files, one for each application, each of which would append its own entry to the $PATH variable. Then, all entries in/etc/path could be parsed on login (in a SysV init sort of manner). Just call some path-init script from the system profile, or bashrc, or whatever.
This would make things easy for package management too, since all you would need to do to remove a package would be to delete the unique directory the application lives in, then remove the matching path script from/etc/path.
Slashdot Mirror
Nothing the Japanese, the Protectors or the Puppeteers can do in materials will be able to succeed until they can counterbalance it. That involves mass. Clarke used an asteroid, "moved" into position.
I'm not saying it can't be done (in this post;-). I'm saying it can't be done for 10 Bills.
Ok, maybe if they devise a way to collect all of the space junk into a blob. Maybe launch a 100m blob of chewing gum against the orbital grain to absorb the detritus to get things started.
Counterbalance? That's the easy part. All it has to do is be equal to the mass of the rest of the cable, and be located in an appropriate position to make the center of mass of the whole contraption be at Geo-Synchronous Orbit.
Want to know the easy way to do that? Just double the length of the cable. If you can successfully make a 22,236mi cable, then chances are good that you can also successfully make a 44,472mi cable.
This also has the added benefit that the far end of the cable at 2x GSO makes an excellent slingshot for launching vehicles to other planets.
"Marriage is between a man and a period"
So true, so true.
My wife may kill me for agreeing.
Be prepared for total ice meltdown... which means the oceans are around 300 meters higher than they are now.
300m?? Sweet! My house will be on beach front property! Bring on the global warming!
It isn't your idea of an edge that is invalid, it is how you are viewing expansion that is invalid.
You equated expansion to a circle expanding along the surface of a torus, then meeting on the other side. Your example is of an object exploding within a toroidal surface. Similar to, but not the same as, a one dimensional universe expanding within a 2 dimensional toroidal surface of fixed size.
The expansion of the universe is the torus itself getting bigger. Draw a few dots on a balloon, put a C clamp in the middle (to represent the empty middle; if you have toroidal balloons, skip this step), and inflate the balloon. Expansion of the 2 dimensional toroidal surface is measurable by the change in distance between the dots on the surface.
Time unfortunately doesn't work quite like a normal spatial dimension, since objects travelling along the time dimension usually can only move in one direction, so I cannot say what a result would be for time which 'wraps'.
(There are postulated geometries of space, particularly those related to frame dragging around large black holes, for which an object could appear to have moved backwards in the time direction relative to another part of the universe, but within its own reference frame, it would have always been moving forward in the time direction.)
Fixed your typo.
According to Urban Arcana, 1gp is roughly equal to US$20. So, that'll be 2gp please.
Be the ball, and throw yourself. -- Mr T. (Not Another Teen Movie)
Log, blog, and troll.
Aww, man. I really wanted one of the 8-bit ties too.
I think that the whole point of this new technology is that it allows FPGA transistor density to approach much closer to the density found in a static ASIC, since current FPGA chips waste about 80% to 90% of their space with interconnects and signal routing paths.
I don't know if this would allow for faster frequencies on the FPGA, but it is a definite improvement for transistor count.
There are some newer features available in the ext3 codebase in newer 2.6.x kernels that will not work in some older kernels with ext2, regardless of whether it is unmounted cleanly, namely directory hashing, large inode support, extended attributes, fast extended attributes, and acls (which embed themselves in the extended attributes).
There may be more, I haven't been digging into the code myself lately, not for the last couple of years, anyway.
Only untill someone is crazy enough to design a 10bit cpu core. ....
I think I'll go and check opencores.org to make sure someone else hasn't done it already.
Now I only played D&D (the table-top RPG) for a few months on the weekend with a group of friends. I didn't really get into that either (they took it WAY too slow, all had characters in levels 3-4 after playing this certain campaign for easily 3 years), but I don't remember any instances where we had to break into a room, and destroy tons of barrels to find this "hidden" key.
In pen&paper, that's the kind of thing that gets glossed over with a "search check". Or just say that you destroy every barrel in the room untill you find it. It's as simple as the player maybe saying one sentence, and perhaps having to roll the dice once or twice.
If your tabletop DM were to try to run a game like an MMO does, he would have set down miniatures of their characters and each barrel, and the conversation might have gone something like this:
Player1: I destroy all the barrels untill I find the key.
DM: Ok, which barrel do you destroy?
Player1: All of them.
DM: No, which one do you bash in first?
Player1: Alright, I'll play along, the one on the left.
DM: Ok, make an attack roll.
Player2: It's a barrel, it ain't going anywhere!
DM: I have to know how much damage you do to the barrel.
Player1: I'm just beating on it untill it's destroyed!
DM: But you didn't roll to attack, how can you know if you really hit it?
Player3: I fireball all the barrels. Does that destroy them?
DM checks his notes, measures the room for radius of effect of the fireball, then replaces mini barrels with mini piles of ash.
DM: Yes, that destroys them.
Player1: Ok, so we have the key now. I just dug around in the ash untill I found it.
DM: No, which pile of ash are you going to search?
Players all stuff the pile of minis down the DM's throat.
The shared-network directive is definitely the way to go. We use this on our (university) network to force users to register their machines with us so we can keep track of who owns what machine. One subnet is assigned for all unknown-hosts, and is blocked at the firewall, and the other is assigned to all known-hosts and is allowed out to the world.
Republicans are for the Death Penality and Opposed to Abortions. These two confelct on the ideals of Value of any human life.
As one who is in favor of the death penalty, and opposed to abortion, I have never looked at it in terms of the value of human life, but rather the value of innocence. Those who are guilty of a crime must take responsibility for their actions and accept their punishment. An unborn infant is innocent and has done nothing but simply exist.
If you check the package lists, you'll see:
gcc-3.4.1-2.i386.rpm
So... problem solved?
LVM2 is not in this kernel, nor will it appear in any 2.4 kernel. Marcello has stated quite clearly that he believes it belongs in 2.6.x only, and will not ever add it to 2.4.
Why can I drink on Friday without a hangover, but when it comes Monday morning my head is being pounded by sledgehammers?
Easy, you probably just drank enough that you were still drunk on Saturday and Sunday. My own record in that regards is 3 days. The hangover lasted for a good portion of the following week too.
Does 0.99999999 (repeating forever) equal 1?
Yes, it does. My calc1 prof showed us the proof.
I can't remember the whole proof (it's been many many years since i took calc1), but here's the gist of the idea:
start with 0.9, you add 0.1 to it to get 1.
then look at 0.99, you add 0.01 to it to get 1.
now look at 0.999, you add 0.001 to it to get 1.
repeating infinitely, you would eventually need an infinite number of zeros before the 1 to be able to add it to the repeating 9.
That infinitessimally small number actually turns out to be equal to zero, thus, 0.9(repeating) is equal to 1.
Gas appliances are fairly uncommon in North America. The majority of stoves, hot water heaters, etc, are electric.
Not in many rural areas (especially around the midwest). Propane is much more common than electric for hot water heaters and stoves, mostly because it is considerably cheaper. Plus, it has the added benifit that it keeps working if the electricity gets knocked out, which isn't too uncommon every few winters that we have a bad ice storm and the electricity is off for a week (usually happens once every 6 to 8 years).
It's all about the principle of NIH (Not Invented Here). Many places have the mindset that if I/we didn't make it ourselves, then it can't possibly be of any use to us. I bet that it is because of this particular mindset that Intel had to play like it was their idea all along.
And last I looked ACL support was still not quite stable in ext2/3 it has been awhile so it could be stable by now.
As of the patch for kernels 2.4.19+, acl support is very stable for ext[23]. In fact, I've been using it in production for over 2 years now. (I did help write some of the ext3-xattr+acl code, though, so maybe that means I'm a little bit more trusting of the code.)
The only big issues I've ever had is when using them in conjunction with quotas, but even when stress testing the filesystem, I haven't been able to coerce the code to crash since the 2.4.19 patch.
There is a performance hit to NFS when using the ACL-over-NFS code, but you never see it unless you're reading or writing the ACLs themselves. (ie. only when you're using `star --acl` to backup or restore files with their acls, or using a recursive (get|set)facl on an NFS mount.) Of course, the nfs code is less tested, so if you try it and have problems, please submit bugs to acl-devel@bestbits.at
Rabbit-o-Saurus?
Where's a Holy Hand Grenade of Antioch when you need one?
An easy way to keep different applications separated into their own directories, and not have a nightmare managing $PATH would be to create something like /etc/path, which would contain several little files, one for each application, each of which would append its own entry to the $PATH variable. Then, all entries in /etc/path could be parsed on login (in a SysV init sort of manner). Just call some path-init script from the system profile, or bashrc, or whatever.
/etc/path.
This would make things easy for package management too, since all you would need to do to remove a package would be to delete the unique directory the application lives in, then remove the matching path script from