Yes, "reboot"... but the point of the original poster is that there's no REASON to have to reboot. You should be able to change the settings and restart the service without ever shutting/rebooting the server itself. The fact that this is necessary is proof that the NT architecture isn't very appropriate for 24/7 work.
Yes, "reboot"... but the point of the original poster is that there's no REASON to have to reboot. You should be able to change the settings and restart the service without ever shutting/rebooting the server itself. The fact that this is necessary is proof that the NT architecture isn't very appropriate for 24/7 serving...
They describe oceans of hydrocarbons, but remember, hydrocarbons != oil! What we're talking about is liquid ethane or methane... and besides, even if this was oil (which it's not), the suggestion that we could "mine" this stuff is absolutely preposterous. The cost of a return, robotic mission to a Titan would be enormous, not to mention the fact that we've never built a space vehicle capable of shipping enough stuff from Titan to make it economically viable.
BTW, the BBC article never used the words "oil" in their article, AFAIK... I have no idea how that was assumed...
Actually, there is a way to do this, sort of. It's an experimental feature called IP Port Forwarding. The idea is that you can designate certain ports which can be forwarded to certain machines inside your network, so you can have a web server on your masq'd network and have it transparently proxied by forwarding port 80, or do other similar tricks. Of course, this has it's drawbacks, along with being experimental but it does work... in fact, this technique has been used to allow SMB mounting of filesystems on a masq'd box, among other neat things...
Not necessarily. This is only a violation of the GPL if they refuse to allow access to the source code at all. If you call up and ask them for the code, though, they have to give it to you, assuming they aren't breaking the GPL.
BTW, this is all prefaced with the standard IANAL disclaimer...:)
Err, uhh, last I checked, stuff like commctl.dll was considered a system *library*. Just a resource for programmers. Using this thing doesn't rely on tight connections between the OS and Apps folks. It requires the OS folks provide good, OPEN documentation for the Apps folks to make use of... just like the documentation we have for libc, or Xlib, and on and on...
Since we can't really decide exactly HOW the human memory works, it would be a little tough to estimate how many bits could be stored in it. I mean, first off, we don't know HOW memory is stored in the human brain. Second, we don't know WHERE memory is stored in the human brain... we know where certain things might be stored (from people with brain damaged, etc), but other information such as implicit memory, one can't say. Some think memory is stored throughout the brain in the connections between neurons themselves. Others think there are central locations. But no one knows for sure. So, in closing, there's no good answer.:)
WRT your comment on Dolly's clone's age. Frankly, that's not really true. Do you describe your age as how long you've existed on the earth? Or how much life you've lived? Or do you just tell people how long your telomeres are? Dolly's clone is younger than Dolly because she has been on this planet for a shorter amount of time. Sure, her telomeres are shorter and, as a result, her cells can't divide as many times, but that just means her overall lifespan will be (marginally) shorter.
Well, I'd imagine most people have children, not to create a new version of themselves, but to create a whole new, unique individual. I mean, say you realize your biological clock was ticking. Would you just go out and clone yourself? Not likely... you'd try to find someone to have a kid with. Yeesh, you really underestimate human beings.
Besides, there's something to be said for the actual act of creating a child.;)
The genetic defects you're referring to are, IIRC, reduced length telomeres. What does this mean? Well, the length of the telomeres in a cell determines it's lifespace. When cells divide, their telomeres become slightly smaller. Once they're too small, the cell can no longer divide. As for Dolly, well, her telomeres are a little bit shorter. But, if you had any idea what you were talking about, you'd realize that all this means is her lifespace will be *marginally* shorter, simply because of these shorter telomeres. The more important aspect of this problem is that it's a problem when creating clones of clones, since the telomeres will become increasingly short.
Actually, the funny part is this very idea has been tossed around in gaming forums, etc, in the past. I know, I know, it sounds pretty damned outlandish, and I'd have to agree, but it is kinda intriguing. I believe some people were thinking of using Linux as an OS specifically for writing demos, as well. Go figure.
This is totally off topic, and I wouldn't blame anyone for moderating it off, but I just wanted to say your sig is very cool. I stared at that code, trying to figure it out and decided to just screw it and code it up. Neat.:)
Well, it seems to me that using the Crystal Space engine takes the pressure off developers for developing the actual engine. So they're left with designing the actual gameplay, etc, which, while still complex, is less work than starting from scratch, making that kind of timeline (slightly) more reasonable.
Err, if you didn't notice the smiley at the end of that post, I was simply poking fun... have a sense of humour. I realize that the project needs help, and perhaps one of those areas is a better project catch phrase. You have to admit that "When do you want to go today" is just a little lame. That's not to say I have a better phrase, but please, don't get so defensive. Learn to take a little criticism, you're going to get an awful lot now that this project has gone public.
I mean, this looks like a cool site and, frankly, I haven't taken a deeper look into the project yet, but who came up with that catch phrase. "When do you want to go today?" *shudder* Good grief.:)
Even if they keep it open they can do a great deal of damage by implementing MS Windows-specific functions. That would fragment Perl and introduce much confusion into even the usage of the term, "Perl". Would even the GPL protect against this kind of "embrace and extend" strategy? I think not.
Actually, I don't know about this. IMHO, there will always be a standard Perl distribution released by the Perl development community. Seriously, Perl is as likely to fragment as the Linux kernel source tree. Besides, it's the developers choice to add on extra modules to add functionality, such as Windows API calls. The ActiveState distribution will likely be this core Perl release along with these extra modules. And if they change the core of Perl, they themselves stated they would release these changes to the community. So where's the confusion? Perl is still Perl, and the only way to use platform dependant features is to expressly choose to (ie, use WinAPI::blah)... it's not as if there's going to be a WinPerl out there.
Many people here have posted replies about fears the Microsoft would try to add features to Perl or change the core functionality such that scripts written for Windows Perl would not be functional on non-MS platforms. This fear is based on the assumption that MS will try to corrupt Perl in the same way that it's attempting to corrupt Java. However, I don't think this will be the case.
Now, you may ask, why would I think this? Well, let's see... Java is a language whose purpose is to be able to write full-blown, platform independent applications. Why does this scare Microsoft? Well, it has the potential of making the OS a "commodity", since an app written in Java will run on any platform. So, MS decided to try and corrupt Java to ruin this "write once, run everywhere" philosophy.
However, Perl does not have the same purpose. Perl is designed to be almost a swiss army knife of programming languages... it allows the user to perform a myriad of different tasks and, as Larry Wall stated, acts as an excellent "glue" language, joining various tools and components together. In this way, it doesn't threaten the Microsoft hegemony, since it doesn't commoditize the OS in the same way that Java potentially can. As well, there is no strong corporation controlling the Perl language, so there's less of a corporate threat.
So relax, people. From what I can tell, the point of this partnership is to make Perl work better on Windows. And the only thing this can do is benefit the community, since more people will become aware of Perl and start using it. And isn't this what we all want?
Actually, there's been some discussion on the Gnome mailing lists about doing just this. Apparently it wouldn't be that difficult, either, so in time we may have an embeddable Gecko component for Gnome.
Slashdot Mirror
Yes, "reboot"... but the point of the original poster is that there's no REASON to have to reboot. You should be able to change the settings and restart the service without ever shutting/rebooting the server itself. The fact that this is necessary is proof that the NT architecture isn't very appropriate for 24/7 work.
Yes, "reboot"... but the point of the original poster is that there's no REASON to have to reboot. You should be able to change the settings and restart the service without ever shutting/rebooting the server itself. The fact that this is necessary is proof that the NT architecture isn't very appropriate for 24/7 serving...
And burns up in the atmosphere, not to mention dispersing... whoops! :)
BTW, the BBC article never used the words "oil" in their article, AFAIK... I have no idea how that was assumed...
Actually, there is a way to do this, sort of. It's an experimental feature called IP Port Forwarding. The idea is that you can designate certain ports which can be forwarded to certain machines inside your network, so you can have a web server on your masq'd network and have it transparently proxied by forwarding port 80, or do other similar tricks. Of course, this has it's drawbacks, along with being experimental but it does work... in fact, this technique has been used to allow SMB mounting of filesystems on a masq'd box, among other neat things...
BTW, this is all prefaced with the standard IANAL disclaimer... :)
Didn't read the press release, didja? ;) The first release will be on the Intel x86.
Err, uhh, last I checked, stuff like commctl.dll was considered a system *library*. Just a resource for programmers. Using this thing doesn't rely on tight connections between the OS and Apps folks. It requires the OS folks provide good, OPEN documentation for the Apps folks to make use of... just like the documentation we have for libc, or Xlib, and on and on...
Since we can't really decide exactly HOW the human memory works, it would be a little tough to estimate how many bits could be stored in it. I mean, first off, we don't know HOW memory is stored in the human brain. Second, we don't know WHERE memory is stored in the human brain... we know where certain things might be stored (from people with brain damaged, etc), but other information such as implicit memory, one can't say. Some think memory is stored throughout the brain in the connections between neurons themselves. Others think there are central locations. But no one knows for sure. So, in closing, there's no good answer. :)
WRT your comment on Dolly's clone's age. Frankly, that's not really true. Do you describe your age as how long you've existed on the earth? Or how much life you've lived? Or do you just tell people how long your telomeres are? Dolly's clone is younger than Dolly because she has been on this planet for a shorter amount of time. Sure, her telomeres are shorter and, as a result, her cells can't divide as many times, but that just means her overall lifespan will be (marginally) shorter.
Besides, there's something to be said for the actual act of creating a child. ;)
So, in closing, get your facts straight, dumbass.
Actually, the funny part is this very idea has been tossed around in gaming forums, etc, in the past. I know, I know, it sounds pretty damned outlandish, and I'd have to agree, but it is kinda intriguing. I believe some people were thinking of using Linux as an OS specifically for writing demos, as well. Go figure.
This is totally off topic, and I wouldn't blame anyone for moderating it off, but I just wanted to say your sig is very cool. I stared at that code, trying to figure it out and decided to just screw it and code it up. Neat. :)
Well, it seems to me that using the Crystal Space engine takes the pressure off developers for developing the actual engine. So they're left with designing the actual gameplay, etc, which, while still complex, is less work than starting from scratch, making that kind of timeline (slightly) more reasonable.
Err, if you didn't notice the smiley at the end of that post, I was simply poking fun... have a sense of humour. I realize that the project needs help, and perhaps one of those areas is a better project catch phrase. You have to admit that "When do you want to go today" is just a little lame. That's not to say I have a better phrase, but please, don't get so defensive. Learn to take a little criticism, you're going to get an awful lot now that this project has gone public.
I mean, this looks like a cool site and, frankly, I haven't taken a deeper look into the project yet, but who came up with that catch phrase. "When do you want to go today?" *shudder* Good grief. :)
Actually, I don't know about this. IMHO, there will always be a standard Perl distribution released by the Perl development community. Seriously, Perl is as likely to fragment as the Linux kernel source tree. Besides, it's the developers choice to add on extra modules to add functionality, such as Windows API calls. The ActiveState distribution will likely be this core Perl release along with these extra modules. And if they change the core of Perl, they themselves stated they would release these changes to the community. So where's the confusion? Perl is still Perl, and the only way to use platform dependant features is to expressly choose to (ie, use WinAPI::blah)... it's not as if there's going to be a WinPerl out there.
Now, you may ask, why would I think this? Well, let's see... Java is a language whose purpose is to be able to write full-blown, platform independent applications. Why does this scare Microsoft? Well, it has the potential of making the OS a "commodity", since an app written in Java will run on any platform. So, MS decided to try and corrupt Java to ruin this "write once, run everywhere" philosophy.
However, Perl does not have the same purpose. Perl is designed to be almost a swiss army knife of programming languages... it allows the user to perform a myriad of different tasks and, as Larry Wall stated, acts as an excellent "glue" language, joining various tools and components together. In this way, it doesn't threaten the Microsoft hegemony, since it doesn't commoditize the OS in the same way that Java potentially can. As well, there is no strong corporation controlling the Perl language, so there's less of a corporate threat.
So relax, people. From what I can tell, the point of this partnership is to make Perl work better on Windows. And the only thing this can do is benefit the community, since more people will become aware of Perl and start using it. And isn't this what we all want?
Actually, there's been some discussion on the Gnome mailing lists about doing just this. Apparently it wouldn't be that difficult, either, so in time we may have an embeddable Gecko component for Gnome.