Message to sellers: don't fsck up in the first place and you won't get negative feedback. If that's too harsh, well, don't let the door hit your ass on the way out.
Most of the people working at CompUSA weren't qualified in the first place.
Let's focus on creating more manufacturing jobs in the US. To be perfectly blunt, if you can't hack it in the white collar or skilled blue collar world, dig a ditch. The US has a severe shortage of ditch-digging jobs.
Very well. Let's assume the value of the music content in the two versions is not the same.
The iTunes store now offers songs with or without DRM. Let's call the two versions song A and song B. Price is the same for both: song_A + DRM = song_B, or DRM = song_B - song_A.
If we assume that a regular song is worth more than previously-infected but stripped song, then DRM has positive value. If we assume the opposite, that a regular song is not as valuable as a stripped ex-DRM song, then DRM has negative value. Or, my original logic: If a regular song and stripped ex-DRM song are indistinguishable in value, then DRM has zero value.
So it comes down to sound quality. What sounds better at the iTunes store, unencumbered songs or their DRM-infected counterparts? If the DRM'ed songs are higher quality than the regular ones, DRM has NEGATIVE value.
Since DRM and DRM-free tracks cost the same, it proves that DRM is worthless! song_value + DRM_value = song_value
DRM_value = song_value - song_value
DRM_value = 0
Agreed. (Disclaimer, I'm NASA employee who happens to review the occasional SBIR proposal).
The SBIR program also helps support professors and grad students. Associate faculty can incorporate as a small business and win funding that helps them make ends meet as researchers and educators. Many phase 1 projects are roughly the size of 1 or 2 masters' theses, ideal for a small "business" consisting of a PI/professor and a few grad students. I know a few people who wouldn't have been able to make it through school without this program.
"2006" means the initial SBIR proposals were submitted in 2006. How do I know this? I happen to review SBIRs for NASA.
This announcement was for phase 2, which means they've already passed the first 6-12 months of phase 1, and been reselected for additional funding.
The window for submitting SBIRs closes just before the end of the fiscal year. Let's say, September 2006 was the due date for submittals. Then add about a month for review and selection, and a bit longer for contract negotiation. Actual phase I 2006 SBIR research began around January 2007. Add 6-10 months more for the businesses to complete phase I, and here we are announcing the programs that have made it on to phase 2.
Yes, but the money you borrow for debtor's counseling is thrown out along with the rest of the debt. The "cost" of those legal fees and couseling is simply the legal system milking the government for money.
In my experiences, anyone who runs FreeBSD for srs business also has a few machines kicking around for testing and development. Why not unleash 7.0 on one of those right now? HEAD is currently frozen (and about as stable as HEAD could ever be), pending official creation of RELENG_7.
1) Los Alamos National Laboratory, the place that was making the fuel units for New Horizons, halted production due to a security breach. By the time production stopped, there were enough fuel units on hand to generate partial power. The New Horizons team decided they could live with the reduced power budget.
2) There were 18 fuel units in work when the lab shut down. Assuming they "went away", rather than being reprocessed, they'd likey have gone into the NRO spacecraft rather than the NSA. Solar arrays have two major drawbacks on military satellites: (1) they cause lots of drag, especially when you fly low; (2) extensible arrays can be floppy, making rapid slewing and precise pointing more difficult. You don't get much power from an RTG, though, thus ruling out the likelihood that the plutonium went into radar sats. What about big telescopic IMINT satellites? Again, not likely unless it was something radically different than typical Hubble Space Telescope / Improved Crystal layout. What's that leave? SIGINT and SDI stuff. Tinfoil hat types, feel free to speculate further...
For those preprocessor flags to work, someone has to write code that uses them and get that code included in a kernel.
Absolutely. Rather than including that sort of framework in *a* kernel, it ought to be part of the Linux build process for *all* kernels. make and the C preprocessor are powerful tools that could be used for good here.
This seems like an situation where the Linux world is more cathedral-like than the BSD world. Weird:p Anyway, this is the logical fix:
# Choose one scheduler. Note that non-default schedulers may cause you grief, etc # See sched_con(4) and sched_ingo(4). options SCHED_DEFAULT #options SCHED_CON #options SCHED_INGO
Exactly. The codebase might become large, but binary kernels would be as small as you care to strip them down. Don't care for IPv6, a USB stack, or parallel port devices? Leave them out.
In my humble opinion as a *BSD guy, Linux folks need to (a) get more comfortable with rolling custom kernels and (b) clean up the Linux kernel configuration process. When you fork, and if one branch fixes $BUG or adds $FEATURE, you're stuck having to manually merge it to the other branch. With a single codebase (and proper linting/testing) you're forced to "do it right the first time" by supporting the whole enchilada, but the total workload is less.
Slashdot Mirror
constituents, constituents, constituents, constituents!
Message to sellers: don't fsck up in the first place and you won't get negative feedback. If that's too harsh, well, don't let the door hit your ass on the way out.
I for one welcome our future monkeyboy press conferences.
Agreed. Please fix the story description to include Paul.
Most of the people working at CompUSA weren't qualified in the first place.
Let's focus on creating more manufacturing jobs in the US. To be perfectly blunt, if you can't hack it in the white collar or skilled blue collar world, dig a ditch. The US has a severe shortage of ditch-digging jobs.
So vote for Ron Paul. I will.
9 times out of 10 that's exactly the case.
Very well. Let's assume the value of the music content in the two versions is not the same.
The iTunes store now offers songs with or without DRM. Let's call the two versions song A and song B. Price is the same for both: song_A + DRM = song_B, or DRM = song_B - song_A.
If we assume that a regular song is worth more than previously-infected but stripped song, then DRM has positive value.
If we assume the opposite, that a regular song is not as valuable as a stripped ex-DRM song, then DRM has negative value.
Or, my original logic: If a regular song and stripped ex-DRM song are indistinguishable in value, then DRM has zero value.
So it comes down to sound quality. What sounds better at the iTunes store, unencumbered songs or their DRM-infected counterparts? If the DRM'ed songs are higher quality than the regular ones, DRM has NEGATIVE value.
Since DRM and DRM-free tracks cost the same, it proves that DRM is worthless!
song_value + DRM_value = song_value
DRM_value = song_value - song_value
DRM_value = 0
I remember that :p
If you have too much to spend, government, and I know you do, give it back, please.
The SBIR process is how we give money back. Would you rather we just gave money to random people in the parking lot at Wal Mart?
Agreed. (Disclaimer, I'm NASA employee who happens to review the occasional SBIR proposal).
The SBIR program also helps support professors and grad students. Associate faculty can incorporate as a small business and win funding that helps them make ends meet as researchers and educators. Many phase 1 projects are roughly the size of 1 or 2 masters' theses, ideal for a small "business" consisting of a PI/professor and a few grad students. I know a few people who wouldn't have been able to make it through school without this program.
"2006" means the initial SBIR proposals were submitted in 2006. How do I know this? I happen to review SBIRs for NASA.
This announcement was for phase 2, which means they've already passed the first 6-12 months of phase 1, and been reselected for additional funding.
The window for submitting SBIRs closes just before the end of the fiscal year. Let's say, September 2006 was the due date for submittals. Then add about a month for review and selection, and a bit longer for contract negotiation. Actual phase I 2006 SBIR research began around January 2007. Add 6-10 months more for the businesses to complete phase I, and here we are announcing the programs that have made it on to phase 2.
wtf? GPG works just fine with Outlook. See http://www.gpg4win.org/
Yes, but the money you borrow for debtor's counseling is thrown out along with the rest of the debt. The "cost" of those legal fees and couseling is simply the legal system milking the government for money.
In my experiences, anyone who runs FreeBSD for srs business also has a few machines kicking around for testing and development. Why not unleash 7.0 on one of those right now? HEAD is currently frozen (and about as stable as HEAD could ever be), pending official creation of RELENG_7.
Sort of.
1) Los Alamos National Laboratory, the place that was making the fuel units for New Horizons, halted production due to a security breach. By the time production stopped, there were enough fuel units on hand to generate partial power. The New Horizons team decided they could live with the reduced power budget.
2) There were 18 fuel units in work when the lab shut down. Assuming they "went away", rather than being reprocessed, they'd likey have gone into the NRO spacecraft rather than the NSA. Solar arrays have two major drawbacks on military satellites: (1) they cause lots of drag, especially when you fly low; (2) extensible arrays can be floppy, making rapid slewing and precise pointing more difficult. You don't get much power from an RTG, though, thus ruling out the likelihood that the plutonium went into radar sats. What about big telescopic IMINT satellites? Again, not likely unless it was something radically different than typical Hubble Space Telescope / Improved Crystal layout. What's that leave? SIGINT and SDI stuff. Tinfoil hat types, feel free to speculate further...
For those preprocessor flags to work, someone has to write code that uses them and get that code included in a kernel.
Absolutely. Rather than including that sort of framework in *a* kernel, it ought to be part of the Linux build process for *all* kernels. make and the C preprocessor are powerful tools that could be used for good here.
"a for-profit venture without the emphasis on profit."
ZOMG a golden opportunity! Let me call my broker...
This seems like an situation where the Linux world is more cathedral-like than the BSD world. Weird :p
Anyway, this is the logical fix:
# Choose one scheduler. Note that non-default schedulers may cause you grief, etc
# See sched_con(4) and sched_ingo(4).
options SCHED_DEFAULT
#options SCHED_CON
#options SCHED_INGO
Linus has to personally accept every change? When does he sleep?
Just give the established devs a commit bit and let them do as they may.
But you can still do that to this day. With a 2.6.x, even :p
Exactly. The codebase might become large, but binary kernels would be as small as you care to strip them down. Don't care for IPv6, a USB stack, or parallel port devices? Leave them out.
In my humble opinion as a *BSD guy, Linux folks need to (a) get more comfortable with rolling custom kernels and (b) clean up the Linux kernel configuration process. When you fork, and if one branch fixes $BUG or adds $FEATURE, you're stuck having to manually merge it to the other branch. With a single codebase (and proper linting/testing) you're forced to "do it right the first time" by supporting the whole enchilada, but the total workload is less.
A well regulated militia being necessary to the security of a free state, the right of the people to keep and bear arms shall not be infringed.
# Forking isn't necessary.
options BIGIRON
#options DESKTOP