How fast will that 1% of flash wear out with you leaving the rest occupied with data, so no wear leveling can take place... Flash is only reliable up to a few hundred thousand write cycles. So you can keep your SSD's to yourself.
I am at the Ubuntu Developer Summit at Google and listened to a talk given by tytso a few days ago. He mentioned that both ext4 and btrfs will support a new ATA command to tell the drive that a particular sector in no longer in use so that it can reuse it for better wear leveling. So it appears Linux will have better support for SSDs in the near future.
Ah I should have read the article, it claims they were redirected for a couple days but aren't any more... Of course slashdot seemed to imply the censoring was ongoing.
Well they aren't redirected in the hotel I am staying at in Beijing, The Beijing Friendship Hotel. I am here for the OpenOffice.org OOoCon 2008 meeting. At least I can access isohunt and mininova here without trouble but thepiratebay is showing page load error.
I believe that PIE (position independent executable) along with some other security enhancements were turned on in Ubuntu around the time the slowndowns showed up. This would definitely cause at least some slowdown on the 32bit version since there aren't enough registers to begin with. I'm not sure if it causes any noticeable slowdown on the 64bit version, since the amd64 architecture has a lot more available registers, which would correlate with the person mentioning earlier that the 64bit version seemed fast.
The point the OP was making was that Apple is the company that was charging the royalties in the first place. So the fact they charged so much in royalties has apparently killed the standard even among their own machines.
As someone else already noted you are comparing a computer dvd drive to the price of a standalone Bluray drive. Newegg has a computer Bluray drive for $99 already. Last year they were several hundred dollars so they appear to be dropping in price fairly quickly.
Quitting Firefox and then restarting causes Flash to start working again, if it was a driver problem wouldn't that not fix the problem until the system was rebooted?
Flash 9.0.124.0 crashes all the time on my wife's Windows XP system running Firefox as well. Most of the time it exhibits as not being able to play sound. So it definitely isn't limited to Linux. Flash is just crap.
They solve it by having nearly every FOSS application packaged (well over 25K packages) according to strict policy and package review. So its not really an issue of package format really as of actually caring about doing it right to begin with.
What does it spit out when a package has multiple licenses depending on the binary inside that package. I seem to recall some KDE sources (at least in the past) having multiple licenses on different bits of code in the same source tarball.
Most of the reason Debian is so good is due to their very strict policy and review of packages before being allowed into the repository. apt-get is just icing on the cake.
The base rpm command can tell you what package a file belongs to, what a package provides, what it requires, _even when it is not installed_. Not one Debian command can do that. Several, separately, but not one.
dpkg does all of that:
what package a file belongs to dpkg -S (filename)
what a package provides dpkg -L (packagename)
if you mean what files it provides otherwise package provides are seen via
dpkg -p (packagename)
what it requires
dpkg -p (packagename)
_even when it is not installed_
dpkg -l (packagename)
--
apt-file can give individual file contents information on not installed packages, but dpkg doesn't do this by default since it would be a waste of bandwidth to actually download that stuff automatically all the time.
==
The base RPM packaging can skip provides/requires (Autoreqprov: no). Debs cannot do that.
As mentioned by someone else already:
dpkg -i --force-nodep --force-all
==
The base RPM packaging can bundle source packages, complete. Debs cannot do that: you must download patches separately. They can even bundle source packages without the actual sources (Nosrc). Debs cannot do that.
Debs most certainly can bundle them complete, they do not do so by policy. Debs could do a nosrc equivalent but do not do so by policy again. It's not a limitation of the packaging system. Policy in Debian is very strong and so some of the things you seem to think can't be done are not done strictly due to policy reasons.
Defended patent encumbered things like lame (mp3 encoder) go into multiverse. Of course pretty much everything is patented to some extent (no exaggeration in the USA) so really all a distribution can do is to remove patent encumbered software that companies are actually actively suing others over. Which as I understand it isn't the case at least for mp3 playback.
Ubuntu wants to stick to a single CD for distribution to make it easier to distribute in places where broadband is unavailable (many parts of the world), but has over 25,000 packages in their repository.
Since when did distributions rely on grep to find out about security problems?
There are upstream security mailing lists where security problems are disclosed to the various distributions security teams for most projects (and probably including the Linux kernel), so they probably know about these problems before they are even fixed to begin with.
I just got finished playing a video off youtube with sound on Ubuntu 8.04 i386. So if flash isn't working for sound it isn't working only for a subset of users.
Oct 1985 - Sega SG-1000 Mark III (~ Sega Master System) Oct 1998 - Sega Mega Drive (~ Genesis) Dec 1991 - Sega CD (Add on to MD) Nov 1994 - Sega Saturn Dec 1994 - Sega 32x (Add on to MD) Nov 1998 - Sega Dreamcast
Yes, Sega had major problems with 3rd party support since the beginning with the Mark III/SMS, but no they weren't releasing systems every 6 months. Except for the Saturn/32x release that they managed to screw up by positioning too closely together they averaged a release every 3-4 years, which is a normal time span for a console. Also, the Sega CD and 32x were both just addons to the Sega Mega Drive and not consoles themselves, which in turn added to cost which helped to doom them to failure. Nintendo had originally planned on having a CD addon for the SNES as well... which later became the Sony Playstation.
Slashdot Mirror
As I understand it, at least with the recent Seagate 7200.11 fiasco exchanging the board no longer works on newer hard drives.
How fast will that 1% of flash wear out with you leaving the rest occupied with data, so no wear leveling can take place... Flash is only reliable up to a few hundred thousand write cycles. So you can keep your SSD's to yourself.
I am at the Ubuntu Developer Summit at Google and listened to a talk given by tytso a few days ago. He mentioned that both ext4 and btrfs will support a new ATA command to tell the drive that a particular sector in no longer in use so that it can reuse it for better wear leveling. So it appears Linux will have better support for SSDs in the near future.
Ah I should have read the article, it claims they were redirected for a couple days but aren't any more... Of course slashdot seemed to imply the censoring was ongoing.
Well they aren't redirected in the hotel I am staying at in Beijing, The Beijing Friendship Hotel. I am here for the OpenOffice.org OOoCon 2008 meeting. At least I can access isohunt and mininova here without trouble but thepiratebay is showing page load error.
I believe that PIE (position independent executable) along with some other security enhancements were turned on in Ubuntu around the time the slowndowns showed up. This would definitely cause at least some slowdown on the 32bit version since there aren't enough registers to begin with. I'm not sure if it causes any noticeable slowdown on the 64bit version, since the amd64 architecture has a lot more available registers, which would correlate with the person mentioning earlier that the 64bit version seemed fast.
The point the OP was making was that Apple is the company that was charging the royalties in the first place. So the fact they charged so much in royalties has apparently killed the standard even among their own machines.
They may have lowered the royalties at some point but originally I believe it was $1 per port on the machine.
As someone else already noted you are comparing a computer dvd drive to the price of a standalone Bluray drive. Newegg has a computer Bluray drive for $99 already. Last year they were several hundred dollars so they appear to be dropping in price fairly quickly.
Quitting Firefox and then restarting causes Flash to start working again, if it was a driver problem wouldn't that not fix the problem until the system was rebooted?
The crashes I am seeing are on an Athlon 64 3200+ running 32bit Windows XP.
There are already at least two applications that do this: swfdec and gnash.
http://swfdec.freedesktop.org/wiki/
http://www.gnashdev.org/
And yes she is running Firefox 3.0.1 on Windows XP.
Flash 9.0.124.0 crashes all the time on my wife's Windows XP system running Firefox as well. Most of the time it exhibits as not being able to play sound. So it definitely isn't limited to Linux. Flash is just crap.
It would take probably 4-5 DVDs to contain all of Ubuntu.
They solve it by having nearly every FOSS application packaged (well over 25K packages) according to strict policy and package review. So its not really an issue of package format really as of actually caring about doing it right to begin with.
What does it spit out when a package has multiple licenses depending on the binary inside that package. I seem to recall some KDE sources (at least in the past) having multiple licenses on different bits of code in the same source tarball.
Most of the reason Debian is so good is due to their very strict policy and review of packages before being allowed into the repository. apt-get is just icing on the cake.
Its not recommended but can be done via:
dpkg -i --force-downgrade
The base rpm command can tell you what package a file belongs to, what a package provides, what it requires, _even when it is not installed_. Not one Debian command can do that. Several, separately, but not one.
dpkg does all of that:
what package a file belongs to
dpkg -S (filename)
what a package provides
dpkg -L (packagename)
if you mean what files it provides otherwise package provides are seen via
dpkg -p (packagename)
what it requires
dpkg -p (packagename)
_even when it is not installed_
dpkg -l (packagename)
--
apt-file can give individual file contents information on not installed packages, but dpkg doesn't do this by default since it would be a waste of bandwidth to actually download that stuff automatically all the time.
==
The base RPM packaging can skip provides/requires (Autoreqprov: no). Debs cannot do that.
As mentioned by someone else already:
dpkg -i --force-nodep --force-all
==
The base RPM packaging can bundle source packages, complete. Debs cannot do that: you must download patches separately. They can even bundle source packages without the actual sources (Nosrc). Debs cannot do that.
Debs most certainly can bundle them complete, they do not do so by policy. Debs could do a nosrc equivalent but do not do so by policy again. It's not a limitation of the packaging system. Policy in Debian is very strong and so some of the things you seem to think can't be done are not done strictly due to policy reasons.
Defended patent encumbered things like lame (mp3 encoder) go into multiverse. Of course pretty much everything is patented to some extent (no exaggeration in the USA) so really all a distribution can do is to remove patent encumbered software that companies are actually actively suing others over. Which as I understand it isn't the case at least for mp3 playback.
Ubuntu wants to stick to a single CD for distribution to make it easier to distribute in places where broadband is unavailable (many parts of the world), but has over 25,000 packages in their repository.
Since when did distributions rely on grep to find out about security problems?
There are upstream security mailing lists where security problems are disclosed to the various distributions security teams for most projects (and probably including the Linux kernel), so they probably know about these problems before they are even fixed to begin with.
I just got finished playing a video off youtube with sound on Ubuntu 8.04 i386. So if flash isn't working for sound it isn't working only for a subset of users.
There isn't much for the kid to need to make up for his side of the story as everything was documented in the official detention notice...
Exaggerate much?
Oct 1985 - Sega SG-1000 Mark III (~ Sega Master System)
Oct 1998 - Sega Mega Drive (~ Genesis)
Dec 1991 - Sega CD (Add on to MD)
Nov 1994 - Sega Saturn
Dec 1994 - Sega 32x (Add on to MD)
Nov 1998 - Sega Dreamcast
Yes, Sega had major problems with 3rd party support since the beginning with the Mark III/SMS, but no they weren't releasing systems every 6 months. Except for the Saturn/32x release that they managed to screw up by positioning too closely together they averaged a release every 3-4 years, which is a normal time span for a console. Also, the Sega CD and 32x were both just addons to the Sega Mega Drive and not consoles themselves, which in turn added to cost which helped to doom them to failure. Nintendo had originally planned on having a CD addon for the SNES as well... which later became the Sony Playstation.