I'm pretty sure that the 18hr bit mentioned in the article is for 50GB BluRay disks but the article didn't clarify that part.
It does mention a 1TB hard drive can store 381hr of video which would mean the bitrate is roughly 5.8Mbps.
1TB - 381hr ~ 5.8Mbps
4.5GB DVD - 1.8hr 8.5GB DVD DL - 3.4hr 25GB BluRay - 9.5hr 50GB BluRay - 19.0hr
The above doesn't account for filesystem overhead, which is probably why my numbers are off a bit.
Re:A question for large print graphics designers..
on
The History of Photoshop
·
· Score: 4, Insightful
For one thing Photoshop has a lot of commercial plugins available for it. Generally when professionals say they use Photoshop they mean they use Photoshop and a lot of plugins that just aren't available for other graphics programs like GIMP.
One of the guys in the group I was in, Digital Audio Crew (DAC), whose nick was namkraD wrote the Delphi id3 tagger, which wrote the tags that would later bear the name of the program. I still have the program on my hd somewhere.:) Of course you couldn't view the tags with winplay3 since the id3 hack came out afterwards and wasn't part of the mpeg 1 layer 3 standard.
I knew the guy who wrote the id3 delphi tagger program. I still recall it taking somewhere around 1.5hr per song to encode using l3enc under linux. BTW I was in a group called Digital Audio Crew (DAC) if anyone still remembers it.;)
I think this bug actually affects all controllers other than the one the root drive is on (not just i875/ich6). The issue is the primary controller module is loaded in the initrd and then the generic ide driver is loaded, after that the other ide controllers are loaded. I have seen this happen months ago on my box which uses via sata for root and via pata for optical drives. Though I am pretty sure this bug has already been fixed. Do you know the bug number?
It may be due to the fact that P4's have thermal throttling built in and the older Athlon's did not. However, personally I don't recall ever seeing a dead cpu from either AMD or Intel in PCs I have repaired. Typically its the hard drive or power supply that dies. Though the Athlon/AthlonXP did have a design issue of having an unprotected core that could be cracked if you weren't careful while installing. The new Athlon64/Opteron/Sempron have a shield covering the core to relieve this problem.
There is also the problem that even Debian Sid doesn't get updated once the freeze starts. In Sarge's case the initial "freeze" started late in 2003. So while some packages have been updated since then you end up still not having any version of Xorg in Sarge. Also there are no Gnome 2.10, or KDE 3.4 packages in unstable either since it has to be stablized in unstable so that it can go into testing for eventual release.
You must not mean epiphany or galeon since they both use gecko. Opera isn't free software and Konqueror pulls in hundreds of MB of dependencies if you don't use KDE. So there really isn't that much choice out there. So, just use links/lynx.:)
When a project knows there is a security hole and when the general public knows there is one is usually at least a week sometimes several apart. Many projects have secret lists that security information is distributed on. Also with respect to fixing the bugs in CVS they in general don't commit the security fix in CVS until the public disclosure date. An example project that I know does this is KDE.
People just like to beat up on Redhat but this really is standard practice for Case 1.
The poster in question seemed to want it as cheap as possible to the point he didn't even want more than 1 processor. I don't think the poster really understands how much ram costs though since the ram alone costs over $10K, even a low end quad processor system is cheap compared to the cost of the ram alone. So he is unlikely to really care about any of those other options. But for items 1 and 2 you can definitely get that a LOT cheaper than another $15K.
The 896MB limit does not affect x86-64 as Tom has already mentioned, though it definitely does affect x86 (32bit). You can not access above 896MB in the normal 1GB mode on 32bit x86. To be able to use the full memory available you have to enable the 4GB or PAE options which cause a ~ 15% performance hit from what I have read in the past.
Toss in a few other devices (hd/case/etc) and you still end up well under $20K. So why would he want to waste nearly double the money for a 1 processor system unless he really has to only have 1 processor?
That post was from back when Ubuntu 4.10 (Warty) was released. I have used the Wary LiveCD many times without any problems, and this is the first time I have heard of it eating partitions so it is not likely to be reproducible.
Testing was not created until Dec 18 2000, which was after potato was released. Prior to testing unstable was just "frozen" for a while. However, there has been a "sid" dist for a lot longer than that. sid was previously used for stuff that was not suitable for release, such as unfinished arch ports.
No, most of the bugs were in KDE itself. KDE 3.3.0 was one of the worst releases yet by upstream. Even KDE 3.3.1 still depends on several programs that have yet to be released by their upstream, of which I can recall at least gpg 1.9 and rdesktop 1.3+.
It was on the Discovery Channel and was called "Unsolved History: JFK - Beyond the Magic Bullet" It doesn't show to be airing again anytime soon. However, they do have the DVD for sale on their site - here
The latest benchmark mongo benchmark from 2003.11.20 on the namesys site shows Reiser4 still being quite slow as far as CPU_TIME goes. Hopefully this has improved in the past year, it was up to 5 times slower than ext3 at some operations. If you look at REAL_TIME it is faster but that just means you are using 5x the CPU power to do the same things. That 5x CPU could be better used for serving data, multimedia editing, etc.
Does anyone know if there are more recent mongo benchmarks of the Reiser4 code?
I have used Debian Unstable for the past 6 years without any real problems. Every few years something breaks that takes a few minutes to fix, but usually nothing major.
I think a slightly bigger issue is the difference in cost between an amd64 and ia64 chip. The ia64 chips 4 years after release are still over $1300/each for a low end model while there are amd64 chips that are already down to $170/each.
Another issue is that the ia64 runs (or did) a lot hotter than amd64 and the chip itself is also much larger so you wouldn't find them in laptops. There are already 35W laptop versions of the Athlon64. Lower power chips also are very useful in large datacenters due to not needing nearly as much air conditioning.
That is why Intel i865/i875 has the option of direct connect e1000 gigabit (CSA) to the northbridge. Most motherboards with gigabit built on that uses either of those chipsets use the e1000 CSA gigabit chips.
No, if a tui and gui were equally easy to use the tui would always win out since it can work on more hardware. I believe this is also the primary reason Debian uses a tui. Also, I don't believe that a gui is even inherently easier to use than a tui, the old Debian boot-floppies just weren't very newbie friendly, and I honestly don't think it was even intended to be. The old debian boot-floppies was just a big glob of unorganized code that was just good enough for someone to install Debian, that was the whole reason debian-installer was rewritten from the ground up, and is also the primary reason for Debian's current slow release of sarge.
I'm pretty sure that the 18hr bit mentioned in the article is for 50GB BluRay disks but the article didn't clarify that part.
It does mention a 1TB hard drive can store 381hr of video which would mean the bitrate is roughly 5.8Mbps.
1TB - 381hr ~ 5.8Mbps
4.5GB DVD - 1.8hr
8.5GB DVD DL - 3.4hr
25GB BluRay - 9.5hr
50GB BluRay - 19.0hr
The above doesn't account for filesystem overhead, which is probably why my numbers are off a bit.
For one thing Photoshop has a lot of commercial plugins available for it. Generally when professionals say they use Photoshop they mean they use Photoshop and a lot of plugins that just aren't available for other graphics programs like GIMP.
Yep he forgot the US writes its own rules. Torture is only illegal outside the US (and Iraq and Guantanamo and the secret CIA prisons...)
One of the guys in the group I was in, Digital Audio Crew (DAC), whose nick was namkraD wrote the Delphi id3 tagger, which wrote the tags that would later bear the name of the program. I still have the program on my hd somewhere. :) Of course you couldn't view the tags with winplay3 since the id3 hack came out afterwards and wasn't part of the mpeg 1 layer 3 standard.
I knew the guy who wrote the id3 delphi tagger program. I still recall it taking somewhere around 1.5hr per song to encode using l3enc under linux. BTW I was in a group called Digital Audio Crew (DAC) if anyone still remembers it. ;)
I think this bug actually affects all controllers other than the one the root drive is on (not just i875/ich6). The issue is the primary controller module is loaded in the initrd and then the generic ide driver is loaded, after that the other ide controllers are loaded. I have seen this happen months ago on my box which uses via sata for root and via pata for optical drives. Though I am pretty sure this bug has already been fixed. Do you know the bug number?
It may be due to the fact that P4's have thermal throttling built in and the older Athlon's did not. However, personally I don't recall ever seeing a dead cpu from either AMD or Intel in PCs I have repaired. Typically its the hard drive or power supply that dies. Though the Athlon/AthlonXP did have a design issue of having an unprotected core that could be cracked if you weren't careful while installing. The new Athlon64/Opteron/Sempron have a shield covering the core to relieve this problem.
There is also the problem that even Debian Sid doesn't get updated once the freeze starts. In Sarge's case the initial "freeze" started late in 2003. So while some packages have been updated since then you end up still not having any version of Xorg in Sarge. Also there are no Gnome 2.10, or KDE 3.4 packages in unstable either since it has to be stablized in unstable so that it can go into testing for eventual release.
You must not mean epiphany or galeon since they both use gecko. Opera isn't free software and Konqueror pulls in hundreds of MB of dependencies if you don't use KDE. So there really isn't that much choice out there. So, just use links/lynx. :)
When a project knows there is a security hole and when the general public knows there is one is usually at least a week sometimes several apart. Many projects have secret lists that security information is distributed on. Also with respect to fixing the bugs in CVS they in general don't commit the security fix in CVS until the public disclosure date. An example project that I know does this is KDE.
People just like to beat up on Redhat but this really is standard practice for Case 1.
The poster in question seemed to want it as cheap as possible to the point he didn't even want more than 1 processor. I don't think the poster really understands how much ram costs though since the ram alone costs over $10K, even a low end quad processor system is cheap compared to the cost of the ram alone. So he is unlikely to really care about any of those other options. But for items 1 and 2 you can definitely get that a LOT cheaper than another $15K.
The 896MB limit does not affect x86-64 as Tom has already mentioned, though it definitely does affect x86 (32bit). You can not access above 896MB in the normal 1GB mode on 32bit x86. To be able to use the full memory available you have to enable the 4GB or PAE options which cause a ~ 15% performance hit from what I have read in the past.
You can get the following for ~ $15K:
4 - Opteron 844 ($2176)
1 - Tyan K8QS Pro ($1370)
16 - Crucial 2GB ECC ($10720)
Toss in a few other devices (hd/case/etc) and you still end up well under $20K. So why would he want to waste nearly double the money for a 1 processor system unless he really has to only have 1 processor?
That post was from back when Ubuntu 4.10 (Warty) was released. I have used the Wary LiveCD many times without any problems, and this is the first time I have heard of it eating partitions so it is not likely to be reproducible.
There are also DVD torrent links that include all of Ubuntu main.
d -amd64.iso.torrent d -i386.iso.torrent
amd64 - http://torrent.ubuntu.com/dvd/20050407.3/hoary-dv
i386 - http://torrent.ubuntu.com/dvd/20050407.3/hoary-dv
#fate and #exceed on EFNet? or was that before your time? :)
Testing was not created until Dec 18 2000, which was after potato was released. Prior to testing unstable was just "frozen" for a while. However, there has been a "sid" dist for a lot longer than that. sid was previously used for stuff that was not suitable for release, such as unfinished arch ports.
19 Oct 2000 - RFC: implementation of package pools
13 Dec 2000 - package pools implemented on ftp-master
18 Dec 2000 - testing to be implemented on ftp-master
10 Feb 2001 - Changes to experimental, proposed-updates and orphaned distributions
No, most of the bugs were in KDE itself. KDE 3.3.0 was one of the worst releases yet by upstream. Even KDE 3.3.1 still depends on several programs that have yet to be released by their upstream, of which I can recall at least gpg 1.9 and rdesktop 1.3+.
Chris Cheney
Debian KDE Maintainer
It was on the Discovery Channel and was called "Unsolved History: JFK - Beyond the Magic Bullet" It doesn't show to be airing again anytime soon. However, they do have the DVD for sale on their site - here
The latest benchmark mongo benchmark from 2003.11.20 on the namesys site shows Reiser4 still being quite slow as far as CPU_TIME goes. Hopefully this has improved in the past year, it was up to 5 times slower than ext3 at some operations. If you look at REAL_TIME it is faster but that just means you are using 5x the CPU power to do the same things. That 5x CPU could be better used for serving data, multimedia editing, etc.
1 .2 0
Does anyone know if there are more recent mongo benchmarks of the Reiser4 code?
http://namesys.com/benchmarks.html#mongo.2003.1
I have used Debian Unstable for the past 6 years without any real problems. Every few years something breaks that takes a few minutes to fix, but usually nothing major.
I think a slightly bigger issue is the difference in cost between an amd64 and ia64 chip. The ia64 chips 4 years after release are still over $1300/each for a low end model while there are amd64 chips that are already down to $170/each.
Another issue is that the ia64 runs (or did) a lot hotter than amd64 and the chip itself is also much larger so you wouldn't find them in laptops. There are already 35W laptop versions of the Athlon64. Lower power chips also are very useful in large datacenters due to not needing nearly as much air conditioning.
If you just use the release name instead there is no conversion that happens.
Eg:
deb http://http.us.debian.org/debian sarge main contrib non-free
That is why Intel i865/i875 has the option of direct connect e1000 gigabit (CSA) to the northbridge. Most motherboards with gigabit built on that uses either of those chipsets use the e1000 CSA gigabit chips.
No, if a tui and gui were equally easy to use the tui would always win out since it can work on more hardware. I believe this is also the primary reason Debian uses a tui. Also, I don't believe that a gui is even inherently easier to use than a tui, the old Debian boot-floppies just weren't very newbie friendly, and I honestly don't think it was even intended to be. The old debian boot-floppies was just a big glob of unorganized code that was just good enough for someone to install Debian, that was the whole reason debian-installer was rewritten from the ground up, and is also the primary reason for Debian's current slow release of sarge.