I have no intention of ditching the actual discs (they often have fancy artwork and whatnot, and I paid for them)... they live in a pair of closed acid free binders in slots made of whatever plastic doesn't eats CDs (probably should have gotten a third one, since I'm not sure where to find stuff like that any more... or if it even matters). But I have a RAID1 in my computer and can make backups of it. There's also the pesky issue where a lot of discs in my collection are from smaller bands (got them at shows and whatnot) and are actualyl CD-Rs. I'm concerned that a few won't even rip, but I tried my oldest one (yeesh, 13 years old) and it still ripped at least. Will it five years from now? Who knows, none of the CD-Rs I have are long-term archival discs so perhaps not.
Another chunk of the collection came from used music stores, and I have no idea how they were treated prior to acquisition... a few are definitely from the mid-80s and early-90s. Who knows if any were from the bad factories that produced discs prone to delamination and whatnot.
I've been using abcde for a decade (I'm the only who added the local cddb cache support, as a wee lad!), and the cddb editing stage is the problem here. It'd be nice to rip in the background while editing cddb, but unfortunately way too much of the script relies on the cddb info being ready before ripping starts. I'm guessing from comments that it's intentional that you have to edit before ripping, so that you can watch the ripping process. I guess that makes sense for people not using --never-skip.
Looking at the source again, it looks like it'd be less frustrating (hacking on a 10k line shell script and all) to set up abcde to batch rip and only rip into the work dir, and then "resume" with a different config and edit the cddb then. Of course, to add support for extra tags and grabbing the ISRC from tracks I've already rewritten cddb-tool in Scheme... the maintainer is going to love me when I submit all of my patches.
The only problem I have with batch ripping and resuming to tag/encode later is... if I do too many of them at once(enough to make it worthwhile to either parallelize or wander by the computer every ten minutes), it would probably end up taking longer as I have to hunt through N cd cases to verify the info, especially in the case of multiple disc collections. Decisions, decisions.
Can you post the cache behavior thing? The main thing, afaict, is that seeking backward flushes the cache so that cdparanoia can actually re-read sectors.
And to think, that was almost the drive that I bought. Just had to go for the Lite-On, thinking "my current drive is a rebadged Lite-On..."
I'm actually scanning my album artwork too! I made a jig earlier today to scan the back-of-album artwork easily (SANE's command line tools to batch scan a dozen or two albums per run + a gimp script to automatically divide and deskew the scans, followed up by quick re-crop / color balancing / rename by hand... and the entire process is still faster than extracting the discs right now, ugh). Although whether my scans would be considered high quality... I lost my really great SCSI scanner during some move (got it for free since Windows XP stopped supporting it, and hey I use GNU/Linux thanks for the fancy scanner) and am left with an old HP usb scanner that isn't exactly the best, but seems to get the job done.
This is what happens when you discover that xbmc lets you browse albums as a gigantic wall of art, and all of the ? images start bothering you.
You gave me some hope there for a minute, but no dice: eject -X reports that the drive only supports one speed, and I tried eject -x 0 with no effect. Thanks for the suggestion, I didn't even realize drives had max speed control nowadays.
In my case, I sit in front of the machine while ripping. I've got a lot of weird metal albums that aren't in Musicbrainz at all, have somewhat inaccurate information, or aren't titlecased properly (mostly poor titlecasing / ignoring the case used on the album where the case is actually significant). With sub five minute rips it's a quick process of pop the disk in, make sure the tag data is looking OK, and then pop the next disc in (well, at least once I finish beating abcde into submission and make the ripping part parallelizable like every other task is). And then comes the weird stuff, like multi-part songs that I want to tag this time around e.g. Gettysburg where each track should be marked PART="Gettysburg (1863)" (seemingly useless now, but with the data stored it'd be not-too-difficult to make something like xbmc pick the entire "movement" instead of just one part).
Since I'm going to be spending some time each week on this for months...
Hard disks are really, really cheap nowadays. I got a pair of 2TB drives for about $150, and am adding a hotspare next month or so Just In Case (tm) because, hey, it's only another $75. SSDs are much cheaper than reliable memory; if you're going to be storing important datasets in ram, you're going to be using ECC memory, and that costs a lot more than a buck a gig. SSDs can saturate a 6Gb/s sata bus; I'm not sure what level of A/V work requires more than 500-600MB/s throughput. If you're already willing to accept "the UPS runs out of power" (or even "the power cable is yanked") as losing your data, the reliability of an SSD has to be acceptable. In either case, you can backup the working set to a RAID for the cost of a nice dinner out.
Oh no, I am not a fan of pulseaudio... I'm currently experiencing its amazing features like "never comes back to life after pasuspending for jackd". But, if you're not doing anything fancy, it seems to... work.
OSS, honestly, is kind of... an obsolete design if you ask me. It does way too much in kernel (I think modesetting and evdev should be user space tasks too, FWIW). I've not really had trouble getting low latency audio from jackd on top of ALSA. Any issues with it appear to be caused by pulseaudio sucking. I'm really perplexed why Pulseaudio was written when jack exists; I know there are details like "never allows the processor to sleep" but with HPET timers nowadays (fast wakeup on an RT kernel), I don't see why jack couldn't get a "sleep when there are no sources attached" mode, even if in a higher-than-normal latency mode.
Personally, I just want to time travel back to 2008 and have an environment a bit rough around the edges, but reliable and actually working... instead of this "shiny, but ultimately useless" garbage we have nowadays.
What sound system fragmentation? There's ALSA and there's... ALSA.
Even if you're stuck using pulseaudio, nowadays you just use ALSA and it magically routes through PA. And then most games are going to be using SDL (Valve did kind of hire one of the libsdl guys), it hides all of that anyway.
Last night in the debate she certainly seemed opposed to all nuclear: she wanted an end to nuclear bombs (I'm down with that, naturally), an end to nuclear power in the middle east, and en to nuclear power everywhere, and ending of all research because it was too dangerous...
The problem is that... we can't develop those future reactors magically. There's no money, there's no societal will. How many new nuclear engineers are there each year? What are you chances of being able to find work designing or researching Gen IV and beyond reactors? If we want next-generation nuclear to exist, we need to implement current generation nuclear. BWR/PWR designs aren't even all that bad; the AP1000 can use MOX fuel, and IIRC it could be modified to run on solid metal fuel instead of oxide fuel (easier to reprocess). The waste from them that can't be recycled could be dealt with (mostly) by sub critical reactors... we have the technology already if only someone would build it!
The thing it, utilities currently do not operate for profit at all costs. In most states (all states?) utilities have capped profits. The local energy producer in NC (Progress) certainly hit those profit caps, but they were pretty modest as far as allowed profits go (12.5%). The NRC is already an effective regulator, not subject to regulatory capture (see the U.S. safety record for proof! And how quickly any problems are detected, publicized, and dealt with... bad press because people don't grok the realities of large scale industrial installations, but good regulation). The AP1000 is already of a design where overheating causes the reaction to slow. "Greed" is being used as the latest bogeyman: obstructionists hippies have done everything to make solutions to their problems infeasible! When solutions to their constructed problems appear, they move the goal. They've defined things so that they cannot ever support nuclear.
Meanwhile, they are basically causing accelerated CO_2 emissions. We're at a point where natural gas just isn't good enough (and it seems kind of idiotic to use a fuel source that will be tapped before any of the plants hit the end of their useful lives)... to the point where if we don't shift to nuclear, we won't be able to develop post-whatever energy technology as a society since we'll have fewer and fewer available resources every year. The "Green New Deal" might actually work if they mobilized the work force needed to roll out a dozen reactors in under a decade (it takes something like over 2000 people per reactor working for several years, tons of industrial support, etc.... the perfect "job creation plan" if you're ok with federal 'stimulus funding' if you ask me)! It's infuriating seeing them work against their own best interests like that.
Yech, in response to the "Iran crisis" and Syria, Dr. Stein went off on a terrible anti-nuclear rant. Goal: eliminate all nuclear all the world round because it can never be safe, and all reactors produce bomb material... someone's never heard of Generation IV reactors. Hopefully the Green party can be convinced over the next few years that working against nuclear is working against "green" energy...
How about... people pay them for the servers never to go down, even in an emergency. I'm sure the 150 people in my hosting cooperative are appreciating their efforts. Also, given that peer1 makes money from colocation, it's in their business interest to keep it running. TFA notes that customers have joined the bucket brigade, so I'm sure those folks think their servers are criticial.
I'm really not convinced of the utility of Colormaps and indexed visuals in the modern world... my phones going back about eight years now have supported at lesat 15-bit color, and at that point you stop using colormaps. But maybe not. You certainly shouldn't have to agonize over whether your application will work on a very small fraction of displays, and it's madness that (unless you use a toolkit, but you're mad if you're not using a toolkit nowadays) your application will just fail to work if you don't handle ColorMaps.
The input mechanism is certainly powerful, but it's wonky and not particularly clean. The way input events make it to windows is particularly ugly... you do not want to be the one writing code to deal with it.
I like X11 (I mean, it gets the job done, and I probably use the network transparancy features to my home server a couple times a month), but the protocol events really need revisiting. Things like colormaps and core text handling could be moved to extensions, all of the universally implemented extension should be made part of the protocol. Wayland is the first attempt at that. Maybe it'll fail, maybe it'll succeed. But there's no reason to think we can't do better than X11.
Well, I also use the machine as a build server (those Common Lisp systems can take a while to rebuild if you need to nuke all of your fasls), and it's my file server (has like six drives in there now).
We pay about a dime per kwh of power because around 35% of our energy comes from a nuclear plant that the utility just finished paying off. Unfortunately, that's probably going up to around $0.15/kwh because the utility was unable to start building Units 2 and 3 on time and has to switch over to more expensive natural gas (it's amazing how cheap a nuclear plant is when you no longer have to pay the loans and it was uprated by a sweet 200MW with another 50-100MW of uprating to go before 2015, damn hippies causing global warming). In theory they are going to start building two AP1000s in 2014 so if that works out and I don't move in the next decade I should be looking at relatively low energy prices.
The old machine may or may not be saving me money, depending on how you amortize. It costs me around $130 a year to run currently (assuming 140W at the wall, $0.11/kwh). An FX-8320 system should idle around 70-90W (let's say 70W for this), an Ivybridge around 50W so $68 and $48 a year each. Pretty good savings, but given that a machine in the same class the athlonmp was looks around $900 (I'm staring at my newegg shopping cart now, and granted $100 of that is in fans because I'm a fan of positive pressure + tons of really slow fans = silent and cool)... so 10-20 years to pay off buying a new machine. The thing is that 140W is also the *peak* consumption because nothing has power management on this old hunk of junk, whereas these new machines are looking at a good 300W/220W (Piledriver/Ivybridge) peak. Just a quick googleing shows that the A10 isn't all that much better (comparable with the Ivybridge).
Yeah, they're way way faster, but... I mean, I play supertuxkart with friends and build code and keep a few RAID1s around for archiving data. The AthlonMP was able to handle all of these flawlessly until I had to disable CPU1 (can't really decode HQ profile h.264 anymore since it usually requires all of one processor, and then you start task switching and it's just a few MIPS too slow now and drops at least a frame or three every second). Computers have been "there" performance-wise for a decade now.
Maybe I'll change my tune the first time I do make -j10 on Guile or the Linux kernel.
An FX-8xxx system idles around 80-90... peak at over 200 (if all the benchmarks are to believed). And my number is at the socket according to a kill-a-watt, and my power supply is pretty inefficient... before I put the X1650 in, it was more like 95W (damned graphics card!).
I can assure you that my nine year old (but basically eleven year old tech, I got it for a steal when they EOLed everything after the Athlon64 FX was released) AthlonMP is still alive and kicking. With two 2.13GHz processors, 4G of RAM, and a Radeon X1650 it wouldn't be too shabby. Except for the part where I have to keep CPU1 disabled to use OpenGL (initially, I blamed having a Radeon 9100 so I got the new one, no dice). My only option at this point is to drop back to something like Debian lenny, but then I can't run xbmc (really, xbmc + zsnes + mame + {supertuxkart, armagetron} + a few xbox controllers = really sweet HTPC... and the box is great as a fileserver and build server all in one). For power, the thing idles at around 120W, so it's not even that much worse than a modern AMD based system on the power bill (we've got that nukular power round these parts, so I'm still paying a dime a kwh and can feel 1/3 fewer pangs of guilt about burning coal). With the second CPU disabled, however, it's just an underpowered old machine instead of something competetive with a more modern low end desktop.
I gave up on debugging it (the lock up is so hard, even kgdb doesn't work... and trying to do the remote tracing thing also doesn't work because the last traces before the crash don't make it to the serial port). It's turned perfectly usable hardware into... well, I'm getting an FX-whatever rig next week. Probably better for the economy, not so great for my account balance.
The verdict is in: everyone but Virgil Goode wants to end the drug war. The libertarian dude admitted to inhaling even, totally disqualified from office. Jill Stein is using science, woah.
Climate change is part of energy policy, government ethics and corruption are inextricably tied to abuse of civil liberties (corrupt governments oppress), and the war on drugs is probably part of national security (I mean, given the whole "open warfare between cartels in mexico" and "central america").
I didn't realize there was a national move toward top two primaries, closing the election process even more... well, at least these four folks can agree to oppose that.
Also, they are behaving a lot better so far than Obama/Romney did. Maybe it's because of Zombie Larry King.
Slashdot Mirror
I have no intention of ditching the actual discs (they often have fancy artwork and whatnot, and I paid for them)... they live in a pair of closed acid free binders in slots made of whatever plastic doesn't eats CDs (probably should have gotten a third one, since I'm not sure where to find stuff like that any more... or if it even matters). But I have a RAID1 in my computer and can make backups of it. There's also the pesky issue where a lot of discs in my collection are from smaller bands (got them at shows and whatnot) and are actualyl CD-Rs. I'm concerned that a few won't even rip, but I tried my oldest one (yeesh, 13 years old) and it still ripped at least. Will it five years from now? Who knows, none of the CD-Rs I have are long-term archival discs so perhaps not.
Another chunk of the collection came from used music stores, and I have no idea how they were treated prior to acquisition... a few are definitely from the mid-80s and early-90s. Who knows if any were from the bad factories that produced discs prone to delamination and whatnot.
I've been using abcde for a decade (I'm the only who added the local cddb cache support, as a wee lad!), and the cddb editing stage is the problem here. It'd be nice to rip in the background while editing cddb, but unfortunately way too much of the script relies on the cddb info being ready before ripping starts. I'm guessing from comments that it's intentional that you have to edit before ripping, so that you can watch the ripping process. I guess that makes sense for people not using --never-skip.
Looking at the source again, it looks like it'd be less frustrating (hacking on a 10k line shell script and all) to set up abcde to batch rip and only rip into the work dir, and then "resume" with a different config and edit the cddb then. Of course, to add support for extra tags and grabbing the ISRC from tracks I've already rewritten cddb-tool in Scheme... the maintainer is going to love me when I submit all of my patches.
The only problem I have with batch ripping and resuming to tag/encode later is ... if I do too many of them at once(enough to make it worthwhile to either parallelize or wander by the computer every ten minutes), it would probably end up taking longer as I have to hunt through N cd cases to verify the info, especially in the case of multiple disc collections. Decisions, decisions.
Can you post the cache behavior thing? The main thing, afaict, is that seeking backward flushes the cache so that cdparanoia can actually re-read sectors.
And to think, that was almost the drive that I bought. Just had to go for the Lite-On, thinking "my current drive is a rebadged Lite-On..."
I'm actually scanning my album artwork too! I made a jig earlier today to scan the back-of-album artwork easily (SANE's command line tools to batch scan a dozen or two albums per run + a gimp script to automatically divide and deskew the scans, followed up by quick re-crop / color balancing / rename by hand... and the entire process is still faster than extracting the discs right now, ugh). Although whether my scans would be considered high quality... I lost my really great SCSI scanner during some move (got it for free since Windows XP stopped supporting it, and hey I use GNU/Linux thanks for the fancy scanner) and am left with an old HP usb scanner that isn't exactly the best, but seems to get the job done.
This is what happens when you discover that xbmc lets you browse albums as a gigantic wall of art, and all of the ? images start bothering you.
You gave me some hope there for a minute, but no dice: eject -X reports that the drive only supports one speed, and I tried eject -x 0 with no effect. Thanks for the suggestion, I didn't even realize drives had max speed control nowadays.
In my case, I sit in front of the machine while ripping. I've got a lot of weird metal albums that aren't in Musicbrainz at all, have somewhat inaccurate information, or aren't titlecased properly (mostly poor titlecasing / ignoring the case used on the album where the case is actually significant). With sub five minute rips it's a quick process of pop the disk in, make sure the tag data is looking OK, and then pop the next disc in (well, at least once I finish beating abcde into submission and make the ripping part parallelizable like every other task is). And then comes the weird stuff, like multi-part songs that I want to tag this time around e.g. Gettysburg where each track should be marked PART="Gettysburg (1863)" (seemingly useless now, but with the data stored it'd be not-too-difficult to make something like xbmc pick the entire "movement" instead of just one part).
Since I'm going to be spending some time each week on this for months...
Online, as in actively spinning media inside of my computer, that I have RAIDed and backed up. I've disambiguated the text.
Hard disks are really, really cheap nowadays. I got a pair of 2TB drives for about $150, and am adding a hotspare next month or so Just In Case (tm) because, hey, it's only another $75. SSDs are much cheaper than reliable memory; if you're going to be storing important datasets in ram, you're going to be using ECC memory, and that costs a lot more than a buck a gig. SSDs can saturate a 6Gb/s sata bus; I'm not sure what level of A/V work requires more than 500-600MB/s throughput. If you're already willing to accept "the UPS runs out of power" (or even "the power cable is yanked") as losing your data, the reliability of an SSD has to be acceptable. In either case, you can backup the working set to a RAID for the cost of a nice dinner out.
Oh no, I am not a fan of pulseaudio... I'm currently experiencing its amazing features like "never comes back to life after pasuspending for jackd". But, if you're not doing anything fancy, it seems to ... work.
OSS, honestly, is kind of ... an obsolete design if you ask me. It does way too much in kernel (I think modesetting and evdev should be user space tasks too, FWIW). I've not really had trouble getting low latency audio from jackd on top of ALSA. Any issues with it appear to be caused by pulseaudio sucking. I'm really perplexed why Pulseaudio was written when jack exists; I know there are details like "never allows the processor to sleep" but with HPET timers nowadays (fast wakeup on an RT kernel), I don't see why jack couldn't get a "sleep when there are no sources attached" mode, even if in a higher-than-normal latency mode.
Personally, I just want to time travel back to 2008 and have an environment a bit rough around the edges, but reliable and actually working... instead of this "shiny, but ultimately useless" garbage we have nowadays.
What sound system fragmentation? There's ALSA and there's ... ALSA.
Even if you're stuck using pulseaudio, nowadays you just use ALSA and it magically routes through PA. And then most games are going to be using SDL (Valve did kind of hire one of the libsdl guys), it hides all of that anyway.
This isn't the place to argue
Are we on the same site ;)
Last night in the debate she certainly seemed opposed to all nuclear: she wanted an end to nuclear bombs (I'm down with that, naturally), an end to nuclear power in the middle east, and en to nuclear power everywhere, and ending of all research because it was too dangerous...
The problem is that ... we can't develop those future reactors magically. There's no money, there's no societal will. How many new nuclear engineers are there each year? What are you chances of being able to find work designing or researching Gen IV and beyond reactors? If we want next-generation nuclear to exist, we need to implement current generation nuclear. BWR/PWR designs aren't even all that bad; the AP1000 can use MOX fuel, and IIRC it could be modified to run on solid metal fuel instead of oxide fuel (easier to reprocess). The waste from them that can't be recycled could be dealt with (mostly) by sub critical reactors... we have the technology already if only someone would build it!
The thing it, utilities currently do not operate for profit at all costs. In most states (all states?) utilities have capped profits. The local energy producer in NC (Progress) certainly hit those profit caps, but they were pretty modest as far as allowed profits go (12.5%). The NRC is already an effective regulator, not subject to regulatory capture (see the U.S. safety record for proof! And how quickly any problems are detected, publicized, and dealt with... bad press because people don't grok the realities of large scale industrial installations, but good regulation). The AP1000 is already of a design where overheating causes the reaction to slow. "Greed" is being used as the latest bogeyman: obstructionists hippies have done everything to make solutions to their problems infeasible! When solutions to their constructed problems appear, they move the goal. They've defined things so that they cannot ever support nuclear.
Meanwhile, they are basically causing accelerated CO_2 emissions. We're at a point where natural gas just isn't good enough (and it seems kind of idiotic to use a fuel source that will be tapped before any of the plants hit the end of their useful lives)... to the point where if we don't shift to nuclear, we won't be able to develop post-whatever energy technology as a society since we'll have fewer and fewer available resources every year. The "Green New Deal" might actually work if they mobilized the work force needed to roll out a dozen reactors in under a decade (it takes something like over 2000 people per reactor working for several years, tons of industrial support, etc. ... the perfect "job creation plan" if you're ok with federal 'stimulus funding' if you ask me)! It's infuriating seeing them work against their own best interests like that.
Time for a neon green party?
Yech, in response to the "Iran crisis" and Syria, Dr. Stein went off on a terrible anti-nuclear rant. Goal: eliminate all nuclear all the world round because it can never be safe, and all reactors produce bomb material... someone's never heard of Generation IV reactors. Hopefully the Green party can be convinced over the next few years that working against nuclear is working against "green" energy...
How about ... people pay them for the servers never to go down, even in an emergency. I'm sure the 150 people in my hosting cooperative are appreciating their efforts. Also, given that peer1 makes money from colocation, it's in their business interest to keep it running. TFA notes that customers have joined the bucket brigade, so I'm sure those folks think their servers are criticial.
I'm really not convinced of the utility of Colormaps and indexed visuals in the modern world... my phones going back about eight years now have supported at lesat 15-bit color, and at that point you stop using colormaps. But maybe not. You certainly shouldn't have to agonize over whether your application will work on a very small fraction of displays, and it's madness that (unless you use a toolkit, but you're mad if you're not using a toolkit nowadays) your application will just fail to work if you don't handle ColorMaps.
The input mechanism is certainly powerful, but it's wonky and not particularly clean. The way input events make it to windows is particularly ugly... you do not want to be the one writing code to deal with it.
I like X11 (I mean, it gets the job done, and I probably use the network transparancy features to my home server a couple times a month), but the protocol events really need revisiting. Things like colormaps and core text handling could be moved to extensions, all of the universally implemented extension should be made part of the protocol. Wayland is the first attempt at that. Maybe it'll fail, maybe it'll succeed. But there's no reason to think we can't do better than X11.
So that explains this six-strikes nonsense.
Well, I also use the machine as a build server (those Common Lisp systems can take a while to rebuild if you need to nuke all of your fasls), and it's my file server (has like six drives in there now).
We pay about a dime per kwh of power because around 35% of our energy comes from a nuclear plant that the utility just finished paying off. Unfortunately, that's probably going up to around $0.15/kwh because the utility was unable to start building Units 2 and 3 on time and has to switch over to more expensive natural gas (it's amazing how cheap a nuclear plant is when you no longer have to pay the loans and it was uprated by a sweet 200MW with another 50-100MW of uprating to go before 2015, damn hippies causing global warming). In theory they are going to start building two AP1000s in 2014 so if that works out and I don't move in the next decade I should be looking at relatively low energy prices.
The old machine may or may not be saving me money, depending on how you amortize. It costs me around $130 a year to run currently (assuming 140W at the wall, $0.11/kwh). An FX-8320 system should idle around 70-90W (let's say 70W for this), an Ivybridge around 50W so $68 and $48 a year each. Pretty good savings, but given that a machine in the same class the athlonmp was looks around $900 (I'm staring at my newegg shopping cart now, and granted $100 of that is in fans because I'm a fan of positive pressure + tons of really slow fans = silent and cool)... so 10-20 years to pay off buying a new machine. The thing is that 140W is also the *peak* consumption because nothing has power management on this old hunk of junk, whereas these new machines are looking at a good 300W/220W (Piledriver/Ivybridge) peak. Just a quick googleing shows that the A10 isn't all that much better (comparable with the Ivybridge).
Yeah, they're way way faster, but ... I mean, I play supertuxkart with friends and build code and keep a few RAID1s around for archiving data. The AthlonMP was able to handle all of these flawlessly until I had to disable CPU1 (can't really decode HQ profile h.264 anymore since it usually requires all of one processor, and then you start task switching and it's just a few MIPS too slow now and drops at least a frame or three every second). Computers have been "there" performance-wise for a decade now.
Maybe I'll change my tune the first time I do make -j10 on Guile or the Linux kernel.
An FX-8xxx system idles around 80-90... peak at over 200 (if all the benchmarks are to believed). And my number is at the socket according to a kill-a-watt, and my power supply is pretty inefficient... before I put the X1650 in, it was more like 95W (damned graphics card!).
I can assure you that my nine year old (but basically eleven year old tech, I got it for a steal when they EOLed everything after the Athlon64 FX was released) AthlonMP is still alive and kicking. With two 2.13GHz processors, 4G of RAM, and a Radeon X1650 it wouldn't be too shabby. Except for the part where I have to keep CPU1 disabled to use OpenGL (initially, I blamed having a Radeon 9100 so I got the new one, no dice). My only option at this point is to drop back to something like Debian lenny, but then I can't run xbmc (really, xbmc + zsnes + mame + {supertuxkart, armagetron} + a few xbox controllers = really sweet HTPC... and the box is great as a fileserver and build server all in one). For power, the thing idles at around 120W, so it's not even that much worse than a modern AMD based system on the power bill (we've got that nukular power round these parts, so I'm still paying a dime a kwh and can feel 1/3 fewer pangs of guilt about burning coal). With the second CPU disabled, however, it's just an underpowered old machine instead of something competetive with a more modern low end desktop.
I gave up on debugging it (the lock up is so hard, even kgdb doesn't work... and trying to do the remote tracing thing also doesn't work because the last traces before the crash don't make it to the serial port). It's turned perfectly usable hardware into ... well, I'm getting an FX-whatever rig next week. Probably better for the economy, not so great for my account balance.
Hiding under the video is a "Hide/Show Transcript" link that displays a full transcript if you can't watch the video (or just prefer reading).
Hey, finally Virgil Goode agreed with everyone: NDAA is terrible and needs to be repealed.
The verdict is in: everyone but Virgil Goode wants to end the drug war. The libertarian dude admitted to inhaling even, totally disqualified from office. Jill Stein is using science, woah.
Climate change is part of energy policy, government ethics and corruption are inextricably tied to abuse of civil liberties (corrupt governments oppress), and the war on drugs is probably part of national security (I mean, given the whole "open warfare between cartels in mexico" and "central america").
I didn't realize there was a national move toward top two primaries, closing the election process even more... well, at least these four folks can agree to oppose that.
Also, they are behaving a lot better so far than Obama/Romney did. Maybe it's because of Zombie Larry King.
Ok, now tell Africa they can't have electricity at all so we can maintain emissions targets.