It's definitely possible to run multiple X sessions on different virtual consoles. Sucks a bit of ram, but you can definitely do it.
It's not only possible, but some of us have been doing this for over ten years. If Apple pursues this patent, I'm definitely calling prior art on this.
The better way to infuriate the RIAA would be to have a "station" that's really a framework to broadcast music contributed by the users, and to then have those users pay the broadcasting fees.
I promise you that it would cost the RIAA more to process a five thousand 7 cent checks than they'd earn in the exercise.:-)
If they got options that are now worth 2 million in the process, I'd say they are good businessfolk.
And if they'd exercise those options then dump them on the market to make a quick buck at SCO's expense while rewarding the shorts, I'd say they were damned heroes.:-)
Imaging you selling so many copies and then a month or so later almost all of them get charged back!!
looks like the product didn't perform as expected. no need to blame the consumer there, they just take advantage of consumer protection laws that state that a product that does not perform as expected may be returned within a reasonable period. that's not the consumer's fault, it's just reasonable business practice.
I think you're confusing a chargeback with a return. A chargeback means that the bank takes back the funds previously provided by a transaction. I believe these are issued when it's shown that a card was used fraudulently or the card holder demands a physical signature as proof of the transaction.
What if I buy a candy bar in one store, stick it in my pocket, then go to another store. Will the scanner pick up what's in my pocket?
It'll be a while before RFIDs are cheap enough to attach to candy bars. By the time they are, you can bet this problem will be licked, or people will have to shop naked to avoid having to constantly repurchase their pants.:-)
"GTK/Gnome finally catches up by implementing usless feature copied from OSX"
Yes, shadows are nice - they stop windows smelging into each other... but this is so NOT NEWS.
Windows had it before the Mac, there was a hack to do it with Amiga Workbench before that, and it was in countless Hollywood computer displays before that, etc.
It's a slow news day, this does look kind of cool, and there are going to be people who enjoy it. Meanwhile, you spent an order of magnitude longer in complaining about the article than you would have in just skipping past, so -- what's your point?
Next week: Gilette to sue people who buy one of their razors and then figure out or tell anyone how to remove and resharpen the blades rather than buying more.
Don't laugh. They've already got a patent that prevents anyone from making compatible razor heads. How stupid is that?
Having 64MB of UMA isn't as good as having far more main core memory paired with a video card with 64MB or more.
Very few games bang on the texture or models with the CPU, so the AGP bus isn't really a choke point.
Re:Who was the interviewer? I smell a rat.
on
Bill Gates On Linux
·
· Score: 2, Informative
It was a very short "interview".
If you look off to the side, you'll see links to the other parts of this interview. There were a few questions on each of ten subjects. I was acutally thinking they'd scored a pretty long interview.
Who exactly conducted this interview? Think about this for a second: if you got to interview the richest man in the world, wouldn't you want your name on it?
Many publications won't let authors publicly claim credit for the bigger stories. There's a tendency for guys being assigned the hot stories to become stars in their own right and leave the paper, letting the name create an asset for the competition. There's also a standard of not crediting interviews where the questions were put together by a full staff and only one person was actually delivering the questions.
The GeForce cards still have one thing going for them: DVI-D at high resolutions.
The ATI 'Pro' cards have DVI-D output, however it's incompatible with many monitors at 1600x1200 and higher. It's generally the monitor mfr's fault for not getting the standards quite right, but that's little consolation when you hook your $2000 Viewsonic VP201m or similar up to a Radeon and just get green snow.:-/
I hope that if you develop something like this, you keep it to yourself, you selfish bastard.:-)
I like the current system just fine. If you upgrade constantly, you'll eventually be the one to get bitten. But it rarely needs more than a bandaid, and you can save everyone else the trouble. This way even users who never contribute a line of code still benefit the whole through their use.
As I understand it, this process is automatic. A package needs to have no bugs against it, or any package it depends on, for some amount of time before it can be moved. Further, packages won't move until it can be guaranteed that they won't break packages already in testing, which is determined by a package with exclusive versions in its dependencies.
The more complex a package is, the longer it takes for it to be verifiably safe. That's just the nature of the beast.
Still, you can use unstable without problem if you take precautions.
Enough with the "Debian's dated" already...
on
Introduction to Debian
·
· Score: 5, Informative
Debian's stable releases aren't a quarterly affair. Your average user who's trying to use an OS to do work or run a server doesn't want quarterly releases. Precious few people really need to jump to Apache 2.0 or kernel 2.4.21 the very day/week/month it comes out.
But, for those of you who want the bleeding edge without risking instability, Debian does just fine there if you know what you're doing. Go ahead and jump to unstable. Seriously!
The only thing you're missing is "apt-listbugs," which does this automatically with every update...
slate:/home/brian# dselect
Reading Package Lists... Done
Building Dependency Tree... Done
10 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 41.9MB of archives.
After unpacking 16.4kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.uk.debian.org sid/main tetex-bin 2.0.2-4.1 [3774kB]
[...]
Get:10 http://ftp.uk.debian.org sid/main libnspr4 2:1.3.1-2 [117kB]
Fetched 41.9MB in 4m19s (162kB/s)
Reading package fields... Done
Reading package status.. Done Retrieving bug reports... Done
grave bugs of mozilla-psm (2:1.3.1-1 -> 2:1.3.1-2) <done>
#189907 - mozilla-psm: psm doesn't register with mozilla
grave bugs of tetex-bin (2.0.2-3 -> 2.0.2-4.1) <done>
#195641 - tetex-bin dependency problem
Merged with: 195677 195679 195683
grave bugs of tetex-bin (2.0.2-3 -> 2.0.2-4.1) <open>
#195723 - tetex-bin: postinstall script dies, making tetex-bin uninstallable
Summary:
mozilla-psm(1 bug), tetex-bin(2 bugs) Are you sure to install/upgrade these packages? [Y/n/?/...]
Before starting installation, apt-listbugs fetches all the bug reports for versions between your current version and the target version. We can see that two bugs have been closed (fixed by later versions, or the bug reports were bogus), and we see that the tetex-bin bug is still open.
In this case, we'd type 'h tetex-bin' to hold the broken package and proceed with a perfectly usable system.
Of course, this still leaves you in the position to be the one in ten thousand who finds a critical bug on installing any given package. If that happens, be a Good Debizen and use reportbug so the next guy is notified. Further, if you flag a critical bug, it's rare that it isn't fixed within a couple hours, even at 2am on Sunday. Once you've reported your bug, go ahead and roll back a version and carry on until the developer closes the bug -- if you used reportbug, you'll get an all-clear email automatically when he or she closes the bug.
With unstable and the apt-listbugs' automatic reports, the chances of ever winding up with a broken system are exceptionally low. Showstopper bugs are rare even in unstable -- maybe one package update in five thousand. But, with thousands of other users snarfing packages and reporting any bugs, the chances of your being the one to discover breakage without apt-listbugs warning you first are virtually nil.
All that said, if you can bear to be a week to a month behind the bleeding edge, you can use apt-listbugs with testing as well. The chances of getting a broken system with testing and apt-listbugs are about the same as the chance of Windows Service Update not needing a reboot. Virtually nil.
Reading NTFS by direct mount, you're going to lose ACLs, system/hidden attributes, encrypted files, and I don't know that Linux supports NT file compression either. Over the net, ACLs and NTFS file attributes are still going away.
Really, it's best to use a Windows backup utility, or to use dd or similar to back up a binary image of the partition(s) on the machine itself.
This is one of those places where it's better not to save a few bucks (unless you save those bucks by first migrating that server to a free OS).
Rather than guessing and hypothesizing, go to spec.org and look up the Pentium 4 SPECCPU results to see the values from the folks who made the benchmark in the first place.
Apple understates the Intel speeds by more than a third, compared to the findings you see on the benchmark authors' own site.
Slashdot Mirror
It's not only possible, but some of us have been doing this for over ten years. If Apple pursues this patent, I'm definitely calling prior art on this.
The president can't do many things at all on his own. But he can spearhead efforts and throw a lot of influence around.
I promise you that it would cost the RIAA more to process a five thousand 7 cent checks than they'd earn in the exercise. :-)
And if they'd exercise those options then dump them on the market to make a quick buck at SCO's expense while rewarding the shorts, I'd say they were damned heroes. :-)
<3 Sexual Asspussy <3
By the time this stuff's all through the courts, GNU/HURD might be ready. It should be possible to change systems over in no time flat.
It'll be a while before RFIDs are cheap enough to attach to candy bars. By the time they are, you can bet this problem will be licked, or people will have to shop naked to avoid having to constantly repurchase their pants. :-)
It's a slow news day, this does look kind of cool, and there are going to be people who enjoy it. Meanwhile, you spent an order of magnitude longer in complaining about the article than you would have in just skipping past, so -- what's your point?
Way off topic, but I believe in the current slash code, your karma is still tied to the posting if you post anonymously while still logged in.
Next week: Gilette to sue people who buy one of their razors and then figure out or tell anyone how to remove and resharpen the blades rather than buying more.
Don't laugh. They've already got a patent that prevents anyone from making compatible razor heads. How stupid is that?
Then I noticed one other "slight" difference in the configuration. :-) Hell, I know which option I'd take!
Very few games bang on the texture or models with the CPU, so the AGP bus isn't really a choke point.
If you look off to the side, you'll see links to the other parts of this interview. There were a few questions on each of ten subjects. I was acutally thinking they'd scored a pretty long interview.
Many publications won't let authors publicly claim credit for the bigger stories. There's a tendency for guys being assigned the hot stories to become stars in their own right and leave the paper, letting the name create an asset for the competition. There's also a standard of not crediting interviews where the questions were put together by a full staff and only one person was actually delivering the questions.
The ATI 'Pro' cards have DVI-D output, however it's incompatible with many monitors at 1600x1200 and higher. It's generally the monitor mfr's fault for not getting the standards quite right, but that's little consolation when you hook your $2000 Viewsonic VP201m or similar up to a Radeon and just get green snow. :-/
I like the current system just fine. If you upgrade constantly, you'll eventually be the one to get bitten. But it rarely needs more than a bandaid, and you can save everyone else the trouble. This way even users who never contribute a line of code still benefit the whole through their use.
The more complex a package is, the longer it takes for it to be verifiably safe. That's just the nature of the beast.
Still, you can use unstable without problem if you take precautions.
But, for those of you who want the bleeding edge without risking instability, Debian does just fine there if you know what you're doing. Go ahead and jump to unstable. Seriously!
The only thing you're missing is "apt-listbugs," which does this automatically with every update...
Before starting installation, apt-listbugs fetches all the bug reports for versions between your current version and the target version. We can see that two bugs have been closed (fixed by later versions, or the bug reports were bogus), and we see that the tetex-bin bug is still open.
In this case, we'd type 'h tetex-bin' to hold the broken package and proceed with a perfectly usable system.
Of course, this still leaves you in the position to be the one in ten thousand who finds a critical bug on installing any given package. If that happens, be a Good Debizen and use reportbug so the next guy is notified. Further, if you flag a critical bug, it's rare that it isn't fixed within a couple hours, even at 2am on Sunday. Once you've reported your bug, go ahead and roll back a version and carry on until the developer closes the bug -- if you used reportbug, you'll get an all-clear email automatically when he or she closes the bug.
With unstable and the apt-listbugs' automatic reports, the chances of ever winding up with a broken system are exceptionally low. Showstopper bugs are rare even in unstable -- maybe one package update in five thousand. But, with thousands of other users snarfing packages and reporting any bugs, the chances of your being the one to discover breakage without apt-listbugs warning you first are virtually nil.
All that said, if you can bear to be a week to a month behind the bleeding edge, you can use apt-listbugs with testing as well. The chances of getting a broken system with testing and apt-listbugs are about the same as the chance of Windows Service Update not needing a reboot. Virtually nil.
Really, it's best to use a Windows backup utility, or to use dd or similar to back up a binary image of the partition(s) on the machine itself.
This is one of those places where it's better not to save a few bucks (unless you save those bucks by first migrating that server to a free OS).
You can find a BitTorrent of the MP3 right here, or read the comments and find the original link attached to the story.
So, if every Linux user could go out and do something that cost SCO a dollar... :-)
Should this thing get all slashdotted to hell, I've got a BitTorrent mirror of the MP3 available here.
Please define "robust." Everybody who says "robust" about a product means something different.
Apple understates the Intel speeds by more than a third, compared to the findings you see on the benchmark authors' own site.