Correcting the units, it's 1.8 terrawatt*hours. Each of those nuke plants is generating 600 megawatts of power; so 600 megawatt*hours every hour, or.6 terrawatt*hours every hour. By your numbers numbers, every PS2 in the world could be powered for a year by three hours of just one of those average nuke plants running.
100kW/kg is the power density, i.e. a measure of how fast it can output a particular amount of power per kilogram of device. 60Wh/kg is a measure of energy density, which is to say, joules per kilogram in a charged state - they are just using units of watt-hour, which can be more convenient for energy storage measurements. To put it into a normalised form, we have 100,000 J/s*kg (joules per second per kilogram) for the power density, and 216,000 J/kg (joules per kilogram) for the energy density. So, one kilo of capacitor could dump about 216,000 joules of energy into something in slightly over two seconds. I believe that also runs the other way around, with a two-second charge. But IANAEE.
Re:One Point For Gmail
on
Gmail vs Pine
·
· Score: 1
Just a point, but I've heard people complaining about GMail returning "service temporarily unavailable" messages six or seven times this year alone. GMail doesn't have bullet-proof stability.
The simple answer: Yes. The system never shuts down, it just saves the current state of the machine to disk and stops - when it comes back, it comes back with every process that it stopped with still running, almost like nothing happened.
The long answer: stuff that was talking to the outside world will probably have it's open connections dropped, and the network card might need to be restarted or something. Nothing big, nothing that should take much time.
Not sure how long it takes to bring the system back, though.
It's listing both; like "linux kernel ZLib invalid memory access denial of service". It's just that it's a much longer list for every app that's big enough to get bugs submitted to this place rather than just to the developers.
Re:Interestingly...
on
Why Use GTK+?
·
· Score: 3, Interesting
Leaves me wondering if you could successfully play linking games to keep your software non-GPLed when you distribute it.
Construct a general database interface API (or find a compatibly licensed one - not GPL...), write your app to use that API, and distribute it. Also distribute a module that is GPLed that talks to the mysql database. The user links the module with the app, and the GPL asserts itself on this new derivative work; the end user cannot distribute this work without distributing full source; but the end user is restricted from distributing it anyways, if it's a commercial product. If not, then they can distribute it unlinked anyhow.
The interface is not a work based on the GPLed work; the GPLed work wasn't involved in it's construction, it's just an database interface tailored to the needs of your app. Your app is only based on the interface; the interface isn't GPLed, no problem.
The code that translates your interface to the GPLed work is based on the GPLed work; it must be under the GPL if you are releasing it. That does not, however, do anything to the licensing of the interface or your app. When linked, they are a derivative work, and therefore cannot be copied, distributed, modified and all that except under the GPL; nobody cares. This happens well after you'd want to do any of those with it - it doesn't keep you from using it.
This is actually the scheme that the madwifi project uses to get their FCC-mandated binary module into the kernel; it doesn't particularly interact with the kernel, it interacts with their code, based on an interface which is licensed such that the GPL doesn't apply.
So give them an RSA keypair, and require them to use a decent password to encrypt it. Ideally, give them a USB device that won't release the key at all, just do the keypair authentication itself, and will enforce a reasonable password standard.
But that would take work and would be a change.
Quite - I have actually heard of a perverse graduate student at WPI, who, when given the freedom to choose any programming language to code a raytracer in for the graphics class, chose postscript. Send scene to printer, wait an hour or two, and your scene comes out....
Wiki and GNU FDL are tremendously different things.
On the one hand, Wiki is sort of this free-for-all "write something here" mess that sort-of works, but primarily seems to be good for finding out what you're wanting to look up from a reputable source to learn what you want. An indexing/information networking system, as it were.
On the other hand, the GNU FDL's only technological requirement is that in some manner a copy in the preferred form for human editing of the information (in an open format - a bit of a quirk) is distributed alongside any derivative of it (say, a printed book).
As for credibility and worth of information - well, Joe Blow can get a book "Plants Is Good" printed fairly trivially without a trace of the GFDL involved; whether or not anyone will happen to read it is a completely different matter.
The GFDL doesn't make an education any less important, and I quite agree that an editor is a necessity. As an aside, I suppose the FDL may shift the necessity somewhat more towards having an actual education in the subject, as opposed to having paid a pile of money for a degree.
What you seem to be objecting to is a perceived lack of a filter to keep idiots from writing crap into the book. Simply put, such a filter is not in any way removed or even particularly discouraged. There isn't this "every man's opinion is worthwhile until voted down" thing that the wiki system seems to have.
To quote their preamble,
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
What that doesn't mention is that credit, as always, comes with it accountability. The entire license is designed specifically such that some idiot cannot come along and take a perfectly good book, mangle it's content, and then publish it in a way that makes it look like it's the original book.
What it does do is reduce the barrier to collaborative work tremendously. Where with traditional publishing I am hardly encouraged to write a section on something that I am knowledgeable about into my copy of a book, and then send that back to the recent publisher of the book for incorporation into their version, or for endorsement of my version (Endorsements are specially handled; if you make a modified version of a work, you must delete all previous endorsements, and acquire new ones if you want them).
Anyhow, I have work to do. If you want to take a look at what you're claiming would decrease the signal-to-noise ratio of published works, the GFDL is available at http://www.gnu.org/copyleft/fdl.html
- it's about seven pages, not counting the navigation stuff up top.
As for the FCP, it's nowhere near the maturity level it would need to be to displace even one normal textbook - but it's progressing. We'll see where it goes.
...Wrong. Go get involved with the FCP (Free Curriculum Project), write your books, release under the GNU free documentation lisence, get a printing company involved and sell bound copies. Someone else makes modifications, releases them in whatever way - and you, of course, are perfectly free to include their modifications, as you see fit, into your print version....Not at all impossible to profit from; just position yourself to start a distribution.
When I was looking into doing this sort of format stripping (for a college newspaper, oddly enough) I started really looking into wvWare. It really is a marvelous little program - it takes a document in word format and translates it into a document in some text-based format by essentially replacing any given bit of word formatting with the text from a tag in an XML file describing the destination format.
If you want it to, for instance, keep paragraphs, bold and italic markings, but nothing else, you would write (Or, as I was doing, edit) an XML file specifying that for each you replace the beginning with the appropriate start tag, and the end with the appropriate end, and all other formatting in the document with nothing at all. I found the format for doing WML pages to be marvelously close to a very minimal HTML (only a tag or two away).
Actually... yes. it's XML. Looks vaguely familiar if you've poked at postscript (which is also human-writeable - and a complete programming language for a printer-type device. Heard tale of a raytracer implemented in postscript... having poked at the language, I quite believe it, too.)
- I think I might just use SVG now:)
But much more convenient to run perl or vim than bash... bash is for calling other programs to do your work for you:)
Version 0.42 != decimal 0.42.
Version 0.42 is generally the 42nd sub-version. Many projects even have sub-sub-versions, like firefox: 1.0.4 doesn't even make sense as a decimal number.
Occasionally you do see a project that assigns separate meanings to digits without a delimiter, as decimal numbers do, but this is often sub-ideal - it runs into conflicts if you pass nine on any given digit.
I, for one, would much prefer that it be a GUI built to write make.conf and related files, as Gentoo does cater quite a lot to the people who find GUIs to be mostly slow and clunky.
Oddly enough, the --use option I've never seen used, as generally you're wanting to globally turn things on or off - no reason to compile some things for OSS if you're running alsa and they support it.
Somewhat different thing to put the five or six characters of a USE flag into a text file to tell your system to always use or not use a particular option. But a GUI config file writer would be reasonable for those who don't like text files.
...That's what Gentoo does. Gentoo uses the portage tree, which contains small bash scripts describing the way to download, compile, install, and uninstall a given package, what it's dependencies are, etc.
Pretty much universally it ends up being such that you can find a package you want with "emerge --search", then type "emerge --ask " to review what ebuilds it'll install, and type "yes" to compile and install them all. Portage also has it install into a separate directory structure, and then merges that back into the main directory structure, keeping track of what is being added for removal later if desired.
And that little bit of scripting glue that is the ebuild makes it very easy to add packages to portage (there are shortcuts if the source tarball uses "standard" commands for build and install). Even provides mechanisms for globally turning on or off build flags (use gtk or qt, X11 or svgalib, etc.).
End-user gets more options with source, and can avoid most of the hassle anyways.
Well, it's not so doom if you are carrying your own software around, as well - to compromise, they'd need to actively scan a program that wasn't on the machine before for a decrypted private key.
Also, it strikes me that it wouldn't be horrendous to construct yourself a script that would create a new keypair for you, encrypt it with a password that you only use for those (because the computer would need to have it stored), and put the private on the thumb drive and the public into authorized_keys, replacing the old one. Have it run every time that hotplug detects that particular thumb drive, and you're good. A new keypair to use from untrusted computers within by just having your thumb drive plugged in for a bit.
If I didn't have a laptop to keep my keys, programs, etc. on, I'd probably go ahead and implement that now...
Yeah, you can - but it's exactly the virtual terminals bit. My girlfriend and I both use her shuttle rather extensively, and so we have three X servers start by default - one for her, one for me, and one for a guest:)
it's exactly putting them on different virtual terminals. I think how we did it there was by editing the configuration file for xdm... just telling it to run a server on:0 (which goes to VT7), and another on:1, and a third on:2. (8 and 9, respectively).
On Gleep (the shuttle), resources tend to not be a problem... she's got a relatively new AMD processor, and a full gigabyte of RAM... but I've done similarly on my little PII laptop - if you think about it, the inactive server won't be doing all that much in the way of I/O (no user interaction tends to imply not much display activity either way), and so a lot of the memory taken up can be swapped to disk.
Yeah, thinking about it, I've had one X server local on my laptop, and one doing an XDMCP session to the campus' shell servers, without much of a problem... but I'm somewhat adapted to my laptop; something about the way I interact, apart from things like this, is nicer on the resources - other people go twitchy with how slow it becomes when they try.
Yeah, laser printers are shiny... I'm looking at trying to get a somewhat old one toner and working - postscript printers have some nifty possibilities, (including such insanity as raytracing engines written in postscript... send the scene to the printer with the code for the raytracer, wait a few hours, and then out rolls your render...) - but in general... just... shiny.
and the way you can use them for transfers and masks for PCBs is quite cool:)
Alternately, you know, run linux, and then you've generally got an arbitrary number of virtual desktops on each X server, the option of running a semi-arbitrary number of X servers, all on one machine and swappable between with key combinations... then you've gone cheaper by not buying as much software, and you've got the same effect of multiple desktops, except for the matter of having many, many more of them.
Or just use litestep, but you don't get the multiple X servers (not that they're useful save for having multiple simultaneous different user sessions), and it's more of a headache.
...which is why the heads are replaceable, too. You don't need a new head every time you need new ink - so coupling the replacement of the head with the replacement of the ink is at best a money-making concept, at worst just bad design. Wear and tear is not directly related to ink consumption, for instance, when ink dries too much in the heads it clogs - but that's only going to happen if you aren't using/enough/ ink - not running the printer often enough.
And if it's streaking while you've got three-quarters-full ink cartridges, you can just replace the heads.
Oh good - had just read this article and said "wait a moment - mum's old printer had the printer, a frame bit with the print heads in it, and ink cartridges that went into that..." - that makes more sense now.
Although I must say, it seems to make the most sense to me to do it that way - disposable ink cartridge, relatively-high-wear print head, and the remainder of the printer as separate, replaceable components.
Slashdot Mirror
Correcting the units, it's 1.8 terrawatt*hours. Each of those nuke plants is generating 600 megawatts of power; so 600 megawatt*hours every hour, or .6 terrawatt*hours every hour. By your numbers numbers, every PS2 in the world could be powered for a year by three hours of just one of those average nuke plants running.
100kW/kg is the power density, i.e. a measure of how fast it can output a particular amount of power per kilogram of device.
60Wh/kg is a measure of energy density, which is to say, joules per kilogram in a charged state - they are just using units of watt-hour, which can be more convenient for energy storage measurements.
To put it into a normalised form, we have
100,000 J/s*kg (joules per second per kilogram) for the power density,
and
216,000 J/kg (joules per kilogram) for the energy density.
So, one kilo of capacitor could dump about 216,000 joules of energy into something in slightly over two seconds.
I believe that also runs the other way around, with a two-second charge.
But IANAEE.
Just a point, but I've heard people complaining about GMail returning "service temporarily unavailable" messages six or seven times this year alone. GMail doesn't have bullet-proof stability.
The simple answer: Yes. The system never shuts down, it just saves the current state of the machine to disk and stops - when it comes back, it comes back with every process that it stopped with still running, almost like nothing happened. The long answer: stuff that was talking to the outside world will probably have it's open connections dropped, and the network card might need to be restarted or something. Nothing big, nothing that should take much time. Not sure how long it takes to bring the system back, though.
old Brit billion; americans use a different spoken numbering system, and it hasn't quite hit full penetration. http://en.wikipedia.org/wiki/Billion
It's listing both; like "linux kernel ZLib invalid memory access denial of service". It's just that it's a much longer list for every app that's big enough to get bugs submitted to this place rather than just to the developers.
Leaves me wondering if you could successfully play linking games to keep your software non-GPLed when you distribute it. Construct a general database interface API (or find a compatibly licensed one - not GPL...), write your app to use that API, and distribute it. Also distribute a module that is GPLed that talks to the mysql database. The user links the module with the app, and the GPL asserts itself on this new derivative work; the end user cannot distribute this work without distributing full source; but the end user is restricted from distributing it anyways, if it's a commercial product. If not, then they can distribute it unlinked anyhow. The interface is not a work based on the GPLed work; the GPLed work wasn't involved in it's construction, it's just an database interface tailored to the needs of your app. Your app is only based on the interface; the interface isn't GPLed, no problem. The code that translates your interface to the GPLed work is based on the GPLed work; it must be under the GPL if you are releasing it. That does not, however, do anything to the licensing of the interface or your app. When linked, they are a derivative work, and therefore cannot be copied, distributed, modified and all that except under the GPL; nobody cares. This happens well after you'd want to do any of those with it - it doesn't keep you from using it. This is actually the scheme that the madwifi project uses to get their FCC-mandated binary module into the kernel; it doesn't particularly interact with the kernel, it interacts with their code, based on an interface which is licensed such that the GPL doesn't apply.
Anyone can edit; it just takes a few days in a some cases if you've not been around before. Moving up in access privileges is automatic...
So give them an RSA keypair, and require them to use a decent password to encrypt it. Ideally, give them a USB device that won't release the key at all, just do the keypair authentication itself, and will enforce a reasonable password standard. But that would take work and would be a change.
Quite - I have actually heard of a perverse graduate student at WPI, who, when given the freedom to choose any programming language to code a raytracer in for the graphics class, chose postscript. Send scene to printer, wait an hour or two, and your scene comes out....
Wiki and GNU FDL are tremendously different things.
On the one hand, Wiki is sort of this free-for-all "write something here" mess that sort-of works, but primarily seems to be good for finding out what you're wanting to look up from a reputable source to learn what you want. An indexing/information networking system, as it were.
On the other hand, the GNU FDL's only technological requirement is that in some manner a copy in the preferred form for human editing of the information (in an open format - a bit of a quirk) is distributed alongside any derivative of it (say, a printed book).
As for credibility and worth of information - well, Joe Blow can get a book "Plants Is Good" printed fairly trivially without a trace of the GFDL involved; whether or not anyone will happen to read it is a completely different matter. The GFDL doesn't make an education any less important, and I quite agree that an editor is a necessity. As an aside, I suppose the FDL may shift the necessity somewhat more towards having an actual education in the subject, as opposed to having paid a pile of money for a degree.
What you seem to be objecting to is a perceived lack of a filter to keep idiots from writing crap into the book. Simply put, such a filter is not in any way removed or even particularly discouraged. There isn't this "every man's opinion is worthwhile until voted down" thing that the wiki system seems to have.
To quote their preamble,
What that doesn't mention is that credit, as always, comes with it accountability. The entire license is designed specifically such that some idiot cannot come along and take a perfectly good book, mangle it's content, and then publish it in a way that makes it look like it's the original book.What it does do is reduce the barrier to collaborative work tremendously. Where with traditional publishing I am hardly encouraged to write a section on something that I am knowledgeable about into my copy of a book, and then send that back to the recent publisher of the book for incorporation into their version, or for endorsement of my version (Endorsements are specially handled; if you make a modified version of a work, you must delete all previous endorsements, and acquire new ones if you want them).
Anyhow, I have work to do. If you want to take a look at what you're claiming would decrease the signal-to-noise ratio of published works, the GFDL is available at http://www.gnu.org/copyleft/fdl.html - it's about seven pages, not counting the navigation stuff up top. As for the FCP, it's nowhere near the maturity level it would need to be to displace even one normal textbook - but it's progressing. We'll see where it goes.
...Wrong. Go get involved with the FCP (Free Curriculum Project), write your books, release under the GNU free documentation lisence, get a printing company involved and sell bound copies. Someone else makes modifications, releases them in whatever way - and you, of course, are perfectly free to include their modifications, as you see fit, into your print version. ...Not at all impossible to profit from; just position yourself to start a distribution.
When I was looking into doing this sort of format stripping (for a college newspaper, oddly enough) I started really looking into wvWare. It really is a marvelous little program - it takes a document in word format and translates it into a document in some text-based format by essentially replacing any given bit of word formatting with the text from a tag in an XML file describing the destination format. If you want it to, for instance, keep paragraphs, bold and italic markings, but nothing else, you would write (Or, as I was doing, edit) an XML file specifying that for each you replace the beginning with the appropriate start tag, and the end with the appropriate end, and all other formatting in the document with nothing at all. I found the format for doing WML pages to be marvelously close to a very minimal HTML (only a tag or two away).
Actually... yes. it's XML. Looks vaguely familiar if you've poked at postscript (which is also human-writeable - and a complete programming language for a printer-type device. Heard tale of a raytracer implemented in postscript... having poked at the language, I quite believe it, too.) - I think I might just use SVG now :)
But much more convenient to run perl or vim than bash... bash is for calling other programs to do your work for you :)
Version 0.42 != decimal 0.42. Version 0.42 is generally the 42nd sub-version. Many projects even have sub-sub-versions, like firefox: 1.0.4 doesn't even make sense as a decimal number. Occasionally you do see a project that assigns separate meanings to digits without a delimiter, as decimal numbers do, but this is often sub-ideal - it runs into conflicts if you pass nine on any given digit.
Last I heard, the drag from having open windows smacks your fuel effeciency a lot more than having an AC unit, and doesn't keep you as cool...
I, for one, would much prefer that it be a GUI built to write make.conf and related files, as Gentoo does cater quite a lot to the people who find GUIs to be mostly slow and clunky. Oddly enough, the --use option I've never seen used, as generally you're wanting to globally turn things on or off - no reason to compile some things for OSS if you're running alsa and they support it. Somewhat different thing to put the five or six characters of a USE flag into a text file to tell your system to always use or not use a particular option. But a GUI config file writer would be reasonable for those who don't like text files.
...That's what Gentoo does. Gentoo uses the portage tree, which contains small bash scripts describing the way to download, compile, install, and uninstall a given package, what it's dependencies are, etc. Pretty much universally it ends up being such that you can find a package you want with "emerge --search", then type "emerge --ask " to review what ebuilds it'll install, and type "yes" to compile and install them all. Portage also has it install into a separate directory structure, and then merges that back into the main directory structure, keeping track of what is being added for removal later if desired. And that little bit of scripting glue that is the ebuild makes it very easy to add packages to portage (there are shortcuts if the source tarball uses "standard" commands for build and install). Even provides mechanisms for globally turning on or off build flags (use gtk or qt, X11 or svgalib, etc.). End-user gets more options with source, and can avoid most of the hassle anyways.
Well, it's not so doom if you are carrying your own software around, as well - to compromise, they'd need to actively scan a program that wasn't on the machine before for a decrypted private key. Also, it strikes me that it wouldn't be horrendous to construct yourself a script that would create a new keypair for you, encrypt it with a password that you only use for those (because the computer would need to have it stored), and put the private on the thumb drive and the public into authorized_keys, replacing the old one. Have it run every time that hotplug detects that particular thumb drive, and you're good. A new keypair to use from untrusted computers within by just having your thumb drive plugged in for a bit. If I didn't have a laptop to keep my keys, programs, etc. on, I'd probably go ahead and implement that now...
Yeah, you can - but it's exactly the virtual terminals bit. My girlfriend and I both use her shuttle rather extensively, and so we have three X servers start by default - one for her, one for me, and one for a guest :)
it's exactly putting them on different virtual terminals. I think how we did it there was by editing the configuration file for xdm... just telling it to run a server on :0 (which goes to VT7), and another on :1, and a third on :2. (8 and 9, respectively).
On Gleep (the shuttle), resources tend to not be a problem... she's got a relatively new AMD processor, and a full gigabyte of RAM... but I've done similarly on my little PII laptop - if you think about it, the inactive server won't be doing all that much in the way of I/O (no user interaction tends to imply not much display activity either way), and so a lot of the memory taken up can be swapped to disk.
Yeah, thinking about it, I've had one X server local on my laptop, and one doing an XDMCP session to the campus' shell servers, without much of a problem... but I'm somewhat adapted to my laptop; something about the way I interact, apart from things like this, is nicer on the resources - other people go twitchy with how slow it becomes when they try.
Yeah, laser printers are shiny... I'm looking at trying to get a somewhat old one toner and working - postscript printers have some nifty possibilities, (including such insanity as raytracing engines written in postscript... send the scene to the printer with the code for the raytracer, wait a few hours, and then out rolls your render...) - but in general... just... shiny. and the way you can use them for transfers and masks for PCBs is quite cool :)
erm... should have read the comment; standard windowsiness would have been alt-tab - but then, ctrl-tab is generally tab-switch.. *shrug*.
Alternately, you know, run linux, and then you've generally got an arbitrary number of virtual desktops on each X server, the option of running a semi-arbitrary number of X servers, all on one machine and swappable between with key combinations... then you've gone cheaper by not buying as much software, and you've got the same effect of multiple desktops, except for the matter of having many, many more of them. Or just use litestep, but you don't get the multiple X servers (not that they're useful save for having multiple simultaneous different user sessions), and it's more of a headache.
...which is why the heads are replaceable, too. You don't need a new head every time you need new ink - so coupling the replacement of the head with the replacement of the ink is at best a money-making concept, at worst just bad design. Wear and tear is not directly related to ink consumption, for instance, when ink dries too much in the heads it clogs - but that's only going to happen if you aren't using /enough/ ink - not running the printer often enough.
And if it's streaking while you've got three-quarters-full ink cartridges, you can just replace the heads.
Oh good - had just read this article and said "wait a moment - mum's old printer had the printer, a frame bit with the print heads in it, and ink cartridges that went into that..." - that makes more sense now. Although I must say, it seems to make the most sense to me to do it that way - disposable ink cartridge, relatively-high-wear print head, and the remainder of the printer as separate, replaceable components.