Hardlinks won't really work as a snapshot substitute; any files that are modified (rather than deleted/rewritten) will be modified in the "snapshot" as well. A hardlink "snapshot" like that would protect against accidental deletion, but that's about it.
No. The reason it does not exist is because the Ares-I kept running into delays and cost overruns, as well as performance issues that continually forced them to remove capabilites for Orion. The reason it _shouldn't_ exist is that it's a _terrible_ program that, had it been allowed to continue, would quite probably have killed NASA and never gotten us out of LEO anyway. Even the Ares-I would not have been operational during Obama's presidency, even presuming he stays in office until 2016. I used to be a fan of Constellation when all I knew was the current NASA PR. After learning just what an absolute mess the program really was, and the severe issues with the Ares-I, I've changed my mind. While the Ares-I would probably be possible to finish, the expected cost of development is $35 billion dollars, and not before 2017. And at the end of all that time and money, you end up with a rocket that takes less mass to LEO than the Falcon 9 Heavy will - and the F9H will have cost roughly as much to fully develop from scratch as the Ares-I's expected yearly recurring operating cost. It is also worth pointing out that the budget that cancels Constellation is NOT in effect yet, and won't be until next year; congress still has to approve it. Obama has absolutely nothing to do with the current delays and failings of the Constellation program - the program itself, and the previous NASA administrator, bear all the blame for that.
Though it's increasinly rarely used by regular consumer, RS232 is still very much around, and I'd argue it's not even technically "obsolete", since at least for one of its purposes - low-level kernel debugging/troubleshooting/development - none of the new standard ports that can do what it does for that purpose.
Actually, you can run OS/2 under VMWare. You need to edit the VM definition file and set the OS type to "os2experimental", and it won't work for OS/2 versions newer than Warp 4 FP12.
Xen 3.1 or newer on SVM-capable AMD hardware will also run OS/2 up to this Fixpack-level. The final fix needed to enable running the latest Fixpack levels and hopefully eComStation as well will be in Very Soon Now.
A common and in my opinion quite good definition of love is "when someone else's happiness is essential to your own". How the hell could anyone ever think to feel _that_ for a programmed sex-bot?
>that's gotta be at least some 30-40 light seconds away from the sun.
I'm not sure if that was tongue-in-cheek, but the signal round-trip time to the voyagers are over 29 hours for V1 and closing on 24 hours for V2. Distance, in other words, is roughly 15 & 12 light _hours_. Heck even the sun itself is 8 light-minutes away. 30-40 light-seconds isn't very far, really.
Unfortunately, all the virtual console games appear to have their own resolution settings which aren't changeable through the Wii menu. The older virtual console games will switch to resolutions that freak out NTSC tv's. The PSU is multi-voltage, however, so no problem there.
What's happened with the virtualization is that they've upgraded the hypervisor from Xen 3.0.3 to Xen 3.1. This is a pretty major upgrade in capabilites and stability. Better support for HVM guests is just one of them.
What do you mean by this? The graphics support in Xen and KVM is pretty much the same, given that they both use qemu for VGA emulation. If you're talking admin-Gui on CentOS, it's virt-manager for both.
The main, initial work on Xen was definitely done by the guys at XenSource. IBM,,HP, Intel, Fujitsu, Novell, AMD & Redhat, among others, are also significant contributors, but RedHat is nowhere near the biggest one. Just doing a quick grep on the xen unstable changelogs, RedHat appears to be the one that have originated the least number of patches out of all the aforementioned contributing companies, although "number of patches" is not necessarily a significant measure of the value of someone's contribution to a codebase.
You know, from a standpoint of security-conscious virtualization, having the OpenBSD team go through the Xen hypervisor code and making OpenBSD work as Dom0 would be a Really Good Thing.
If only it were so. Unfortunately, it's not. There's a distressing amount of 16-bit real-mode code being executed in between power-on and your OS kernel switching into 32 or 64 bit mode even on the most modern PC.
Actually, they've had _eight_ landers on Venus that survived touchdown, four of which transmitted images. The first lander to surivive, Venera 7 in 1970, was the first spacecraft to transmit data from the surface of another planet.
Launching from Mars is more comparable to launching from the Moon than launching from the earth. Martian gravity is only little over twice that of the Moon's. Moreover, Mars has plenty of raw materials available for in-situ fuel production, meaning you won't need to bring the fuel for your return trip with you there. Really, there are plenty of material available about how a manned Mars mission or a robotic sample return mission will be done. If you can read and have internet access, which you obviously do, it shouldn't be "beyond you".
Not regular Warp 4, but Warp 4.5 - that is, Warp Server for eBusiness and the later "convenience packs" for the client - can both address more memory. Likewise, I'm pretty sure that eComStation (the re-branded OS/2 sold by Serenity Systems) can, as well. It does take special APIs to access mem > 512m tho, so older OS/2 apps won't know how to use it.
Re:Humans can handle more than 1 G
on
Interstellar Ark
·
· Score: 1
I would bet on mankind achieving the ability to genetically engineer rapid adaptibility to variable G-forces long before we have the capabilities to build an interstellar ark ship.
You lose your money. If anything, from my personal experience, your percentage guess should be inverted. Out of the core linux kernel devs I've met and conversed with in person, not one raised any flags for me about even mild asperger's tendencies. Of course, I'd suspect the ones that DO fit that diagnosis probably shun real-life kernel developer gatherings due to social phobias and associated symptoms of their disorders. A "sample" taken from something like the OLS's pub-night may well be biased away from the autistic part of the dev crowd. Nonetheless, "90% would test positive" shows you have NO clue what the fuck you're talking about. Aspergers may be overrepresented among "computer geeks" compared to the general population, but nowhere remotely close to that level.
In any case, Linus himself _certainly_ doesn't fit the bill. He's just smart, vocal, and opinionated - nothing autistic about that. When you're proven right as often and for as long as Linus has been, a certain level of arrogance becomes almost inevitable.
Definitely not a reasonable alternative for VMWare Server yet. Go with Xen if you're intending to do anything remotely serious with virtualization and want an OSS alternative to VMWare. KVM, in its current state, is barely adequate for hobbyist desktop tinkering. Trying to boot less tested OSs can bring your entire system down. On a 64 bit SVM host, trying to start an OS/2 vm will do this, for example. I think it was let into mainline too soon. It's fine that it's limited in what OSs it can run. It's not fine that something you try to run in a KVM session can wreck the whole system.
Using optical interferometry to produce actual synthetic aperture images is turning out to be extremely difficult even with earth-based observatories with fiber-optic links between them. While ssing multiple telescopes in orbit like you suggest may be theoretically possible, but I'm seriously wondering about whether it'll be doable within any kind of foreseeable future. It's also going to take more than just two to produce actual images. A less technologically insurmountable potential way of getting extra-solar planet surface-resolving capability are solar foci telescopes, which would use the sun's gravitational lensing as the primary lens of a 800 AU long refractor. This is an incredibly cool concept that is actually on the drawing board already, although it's going to be a while before we see any of them launched.
Unfortunately it isn't posssible; that's what the "locking" msr does - it ensures that whatever value you wrote to the enabled/disabled msr cannot be changed without until the cpu has actually been power cycled. Last summer when I became aware of this issue, I was toying with the idea of modifying the bios binary by searching for the wrmsr opcodes, modifying those, and reflashing, but I'm not sure it would work; the BIOSes are probably checksummed/signed, so the flash might not go through, and in the worst case, I might end up bricking a $3000 laptop. With the new VT-enabling bios just around the corner, a hack like that seems even less worth the risk now.
No. It is explicitly disabled. You have to write a "not enabled" value to a specific MSR, and then a "LOCK" value to another MSR to put VT in an "un-enableable" state like is the case on the HP BIOS. This is entirely intentional, and "fixing". It's a whopping 4 assembly instructions to "fix" this.
Slashdot Mirror
Hardlinks won't really work as a snapshot substitute; any files that are modified (rather than deleted/rewritten) will be modified in the "snapshot" as well. A hardlink "snapshot" like that would protect against accidental deletion, but that's about it.
No. The reason it does not exist is because the Ares-I kept running into delays and cost overruns, as well as performance issues that continually forced them to remove capabilites for Orion. The reason it _shouldn't_ exist is that it's a _terrible_ program that, had it been allowed to continue, would quite probably have killed NASA and never gotten us out of LEO anyway. Even the Ares-I would not have been operational during Obama's presidency, even presuming he stays in office until 2016.
I used to be a fan of Constellation when all I knew was the current NASA PR. After learning just what an absolute mess the program really was, and the severe issues with the Ares-I, I've changed my mind. While the Ares-I would probably be possible to finish, the expected cost of development is $35 billion dollars, and not before 2017. And at the end of all that time and money, you end up with a rocket that takes less mass to LEO than the Falcon 9 Heavy will - and the F9H will have cost roughly as much to fully develop from scratch as the Ares-I's expected yearly recurring operating cost.
It is also worth pointing out that the budget that cancels Constellation is NOT in effect yet, and won't be until next year; congress still has to approve it. Obama has absolutely nothing to do with the current delays and failings of the Constellation program - the program itself, and the previous NASA administrator, bear all the blame for that.
Though it's increasinly rarely used by regular consumer, RS232 is still very much around, and I'd argue it's not even technically "obsolete", since at least for one of its purposes - low-level kernel debugging/troubleshooting/development - none of the new standard ports that can do what it does for that purpose.
Actually, you can run OS/2 under VMWare. You need to edit the VM definition file and set the OS type to "os2experimental", and it won't work for OS/2 versions newer than Warp 4 FP12.
Xen 3.1 or newer on SVM-capable AMD hardware will also run OS/2 up to this Fixpack-level. The final fix needed to enable running the latest Fixpack levels and hopefully eComStation as well will be in Very Soon Now.
I think that theory of humor is falsified by things like this:
http://humor.commongate.com/post/push_button_recieve_bacon/photos/38439
It makes me (and obviously many others) laugh, and I can see no hint of "directed cruelty" in it - it's not poking fun at anyone, and yet it's funny.
A common and in my opinion quite good definition of love is "when someone else's happiness is essential to your own". How the hell could anyone ever think to feel _that_ for a programmed sex-bot?
The X-15 was not a jet plane, it was a _rocket_ plane.
>that's gotta be at least some 30-40 light seconds away from the sun.
I'm not sure if that was tongue-in-cheek, but the signal round-trip time to the voyagers are over 29 hours for V1 and closing on 24 hours for V2. Distance, in other words, is roughly 15 & 12 light _hours_. Heck even the sun itself is 8 light-minutes away. 30-40 light-seconds isn't very far, really.
Unfortunately, all the virtual console games appear to have their own resolution settings which aren't changeable through the Wii menu. The older virtual console games will switch to resolutions that freak out NTSC tv's. The PSU is multi-voltage, however, so no problem there.
What's happened with the virtualization is that they've upgraded the hypervisor from Xen 3.0.3 to Xen 3.1. This is a pretty major upgrade in capabilites and stability. Better support for HVM guests is just one of them.
"and it does GUI where Xen does not"
What do you mean by this? The graphics support in Xen and KVM is pretty much the same, given that they both use qemu for VGA emulation. If you're talking admin-Gui on CentOS, it's virt-manager for both.
The main, initial work on Xen was definitely done by the guys at XenSource. IBM, ,HP, Intel, Fujitsu, Novell, AMD & Redhat, among others, are also significant contributors, but RedHat is nowhere near the biggest one. Just doing a quick grep on the xen unstable changelogs, RedHat appears to be the one that have originated the least number of patches out of all the aforementioned contributing companies, although "number of patches" is not necessarily a significant measure of the value of someone's contribution to a codebase.
You know, from a standpoint of security-conscious virtualization, having the OpenBSD team go through the Xen hypervisor code and making OpenBSD work as Dom0 would be a Really Good Thing.
Because with a bit more time, it will kill YOU as well. It's quite carcinogenous.
If only it were so. Unfortunately, it's not. There's a distressing amount of 16-bit real-mode code being executed in between power-on and your OS kernel switching into 32 or 64 bit mode even on the most modern PC.
Actually, they've had _eight_ landers on Venus that survived touchdown, four of which transmitted images. The first lander to surivive, Venera 7 in 1970, was the first spacecraft to transmit data from the surface of another planet.
Launching from Mars is more comparable to launching from the Moon than launching from the earth. Martian gravity is only little over twice that of the Moon's. Moreover, Mars has plenty of raw materials available for in-situ fuel production, meaning you won't need to bring the fuel for your return trip with you there.
Really, there are plenty of material available about how a manned Mars mission or a robotic sample return mission will be done. If you can read and have internet access, which you obviously do, it shouldn't be "beyond you".
I'd say the liability is not Fedora, the liability is the idiot admin who used Fedora on a production server.
Not regular Warp 4, but Warp 4.5 - that is, Warp Server for eBusiness and the later "convenience packs" for the client - can both address more memory. Likewise, I'm pretty sure that eComStation (the re-branded OS/2 sold by Serenity Systems) can, as well. It does take special APIs to access mem > 512m tho, so older OS/2 apps won't know how to use it.
I would bet on mankind achieving the ability to genetically engineer rapid adaptibility to variable G-forces long before we have the capabilities to build an interstellar ark ship.
You lose your money.
If anything, from my personal experience, your percentage guess should be inverted. Out of the core linux kernel devs I've met and conversed with in person, not one raised any flags for me about even mild asperger's tendencies.
Of course, I'd suspect the ones that DO fit that diagnosis probably shun real-life kernel developer gatherings due to social phobias and associated symptoms of their disorders. A "sample" taken from something like the OLS's pub-night may well be biased away from the autistic part of the dev crowd. Nonetheless, "90% would test positive" shows you have NO clue what the fuck you're talking about. Aspergers may be overrepresented among "computer geeks" compared to the general population, but nowhere remotely close to that level.
In any case, Linus himself _certainly_ doesn't fit the bill. He's just smart, vocal, and opinionated - nothing autistic about that. When you're proven right as often and for as long as Linus has been, a certain level of arrogance becomes almost inevitable.
Definitely not a reasonable alternative for VMWare Server yet. Go with Xen if you're intending to do anything remotely serious with virtualization and want an OSS alternative to VMWare. KVM, in its current state, is barely adequate for hobbyist desktop tinkering. Trying to boot less tested OSs can bring your entire system down. On a 64 bit SVM host, trying to start an OS/2 vm will do this, for example. I think it was let into mainline too soon. It's fine that it's limited in what OSs it can run. It's not fine that something you try to run in a KVM session can wreck the whole system.
Using optical interferometry to produce actual synthetic aperture images is turning out to be extremely difficult even with earth-based observatories with fiber-optic links between them. While ssing multiple telescopes in orbit like you suggest may be theoretically possible, but I'm seriously wondering about whether it'll be doable within any kind of foreseeable future. It's also going to take more than just two to produce actual images.
A less technologically insurmountable potential way of getting extra-solar planet surface-resolving capability are solar foci telescopes, which would use the sun's gravitational lensing as the primary lens of a 800 AU long refractor. This is an incredibly cool concept that is actually on the drawing board already, although it's going to be a while before we see any of them launched.
Unfortunately it isn't posssible; that's what the "locking" msr does - it ensures that whatever value you wrote to the enabled/disabled msr cannot be changed without until the cpu has actually been power cycled.
Last summer when I became aware of this issue, I was toying with the idea of modifying the bios binary by searching for the wrmsr opcodes, modifying those, and reflashing, but I'm not sure it would work; the BIOSes are probably checksummed/signed, so the flash might not go through, and in the worst case, I might end up bricking a $3000 laptop. With the new VT-enabling bios just around the corner, a hack like that seems even less worth the risk now.
No. It is explicitly disabled. You have to write a "not enabled" value to a specific MSR, and then a "LOCK" value to another MSR to put VT in an "un-enableable" state like is the case on the HP BIOS. This is entirely intentional, and "fixing". It's a whopping 4 assembly instructions to "fix" this.