When you have a NFR (not for resale) product from Microsoft, is it legal to GIVE IT AWAY for free? Many people need Windows. If these people got it free and legally, this would prevent that much more money going into Microsoft.
A while back I read that QTSS (Quicktime Streaming Server) was ported from MacOS X (BSD) to other Unixes, and Linux. Anyone know where this can be found?
If you see this message again, here are a few more tips...
Yeah. I find Corel Linux a bit questionable in implementation. You hose their entire nice graphical startup thingy with a standard kernel upgrade. Shouldn't be a problem though, just a cosmetic issue.
Your HPT366 IDE bus will show up as/dev/hde and/dev/hdf in Linux. Is not UDMA Mode 2 ATA33 mode? Mode 2 is 66?
If you have any more problems, e-mail me at warren@togami.com. I spent many hours getting this puppy to work...
Something michael forgot to mention in this article summary is this, mentioned in one of the linked articles on top.
An IT manager at a large manufacturer says that's exactly what Microsoft officials told him. "I spoke to some of my contacts there, and found out that the medialess format is primarily designed to be a firewall against competitors like Linux," he wrote, explaining it will make it harder to have a back-out strategy in place if an experimental Linux deployment gets into trouble. "Now I don't have any Windows CDs for the backout. What would you suggest I do if problems with Linux cause me to want to revert back to Windows? To discourage corporations and consumers from changing, they are no longer distributing CDs with every machine, in the hopes that fear of change without any practical possibility of return will discourage most users from even looking at other systems."
This has to be some of the worst anti-competative behavior that we've seen out of the evil empire. While they are likely to be punished severely after the Supreme court battle ending 239 years from now, we consumers would have already suffered severe damage. Bill Gates says that breaking up Microsoft would be one of the most irresponsible things to do, causing great harm to consumers. How ironic, that their own actions, even when you would expect them to start playing nice, cause severe damage to consumers.
Yes, I am an OSS advocate, but we must admit that the world will not switch to OSS solutions overnight. Businesses, old institutions, society in general knows nothing about us. This will slowly change over time. In the mean time, we will still need to keep up with society's standard... which sadly is Microsoft Windows.
Because we still must put up with this monstrosity for a while, we MUST FIGHT THIS. This is not only bad for Windows users (Hey admit it. A lot of you dual boot. I quad boot into Linux, Solaris, Win98 and Win2000 because I have to keep up and support these platforms), but this would SEVERELY HAMPER alternative operating systems. Many systems with Stupid-Evil-Empire-Being-Dumb-Windows-Licenses will effectively lose their ability to re-partition and install alternative operating systems. This will slow down Linux experimentation as the above article points out, because it will become riskier and more expensive for people to experiment.
We're all going to be outraged for a while here, but you know how these things go. We're outraged, and after the article disappears from the./ homepage we don't hear about it for six months. If the implications of this are correct, this could be one of the worst things to happen since... umm... err... Sephiroth killing Aeris!
DO NOT LET MICROSOFT GET AWAY WITH THIS! FIGHT THIS!
How? I don't know. I'll leave that to other outraged zealots.
Warren Togami warren@togami.com p.s. I found this really cool sig today... hehe. Quite appropriate.
If Bill Gates had a dime for every time a Windows box crashed... ...oh, wait a minute -- he already does.
Everyone that is complaining that ATA-66 and ATA-100 arn't much faster than ATA-33, you are missing the point.
Single drive speed can range from anywhere between 20-31Mb/s (b or B? I can't remember). The truth of the matter is, most people do not exceed their IDE controller's maximum bandwidth. An ATA-66 or ATA-100 controller allows bursts of up to those speeds, because data is temporarily stored in the hard drive or controller cache during that short burst period. In practice however, most people see speeds in the 20's range due to random seeking/reading/writing.
ATA-66 made a big difference for me in drive speed for my squid proxy server, where bursts happen frequently. Drive speed is well below the ATA-66 maximum bandwidth, but my IDE bus has sufficient room for regular bursts which help in speed.
When ATA-66 was first released, Thresh's Firing Squad put up some benchmarks comparing ATA-33 to ATA-66, showing considerable speed improvements in ATA-66. These were synthetic tests showing best case scenarios.... but in practice most people on desktops will not notice much of a difference. In a more recent review of the Abit KA7-100 I believe on HardOCP, the reviewer spoke highly of the potential of the ATA-100 on the KA7-100 motherboard, when he was not too impressed by ATA-66.
You do not have to move cables inside your computer to install Linux. The HPT-366 controller has a backwards compatibility option to run in UltraDMA/33 mode.
You can feed kernel boot parameters from lilo as described in the document here. The workaround for the Promise Ultra33 card works for booting the HPT-366 controller in Ultra33 mode.
Do not jump to conclusions. Alan Cox did say we are in a code freeze, but it is quite clear that Linus made the possibility of exceptions for reiserfs, nfs and VFS.
I can't find the original post, but Linus once said that perhaps reiserfs will be included during 2.4, but maybe not 2.4.0.
From this post by Alan Cox, he does not appear to rule it out. > The generic journal layer might not be a bad idea. Stephen and I have > really duplicated efforts, and that is a waste. I'm more than willing to > make a go at integrating a generic logging system into the reiserfs code > base.
Don't blindly follow Stephen's code either. Im sure the best of happens not to be entirely in one code base.
> But, reiserfs 3.6 has come a long way. I feel it is worth putting into > the kernel soon (I would love to see reports of *heavy* testing), and I
I get requests for reiserfs to be included every so often, and some of them are coupled to things like 'runs fine on our 200Gb build array'. Its certainly getting some good testing
Some sort of genetically engineered plant or algae would be more realistic for planetary alterations, although mass water supplies would be likely required for this type of operation. If machinery was used, it would most likely have to be constructed from local materials and have a vastly larger scale power source than sunlight (which is weaker there.)
Nano-technology could change this for a technological solution. Self-replicating nanorobots which feed upon the martian materials to build more of their kind would engineer the numbers of machines necessary for terraforming.
Although, this really is the same as the algae solution. In both cases we would have to essentially program the organism (lives, feeds, produces) to do its job.
I wonder if we could use a few billion of these to scrub Earth's atmosphere of excess CO2, so that this planet doesn't end up like Mars...
The reason for all the excess CO2 is the burning of fossil fuels. It would take a billion of these devices with solar panels covering the planet to make a dent into this CO2 production, with costs going into the trillions of dollars.
Why not save a few trillion dollars and reduce the delta of total entropy in the universe by using more alternative power sources in the first place? Solar panels, ocean thermal transfer, hydroelectric, wind and other alternative sources feeding giant flywheels could lower our dependence upon fossil fuels.
This issue came up and was a cause of a small flame war on the reiserfs mailing list a few weeks ago. Some guy got really angry about this and began a "CREDITS removing patch site" to apply to your reiserfs sources upon each upgrade to easily remove it from the boot sequence.
Eventually I believe Hans Reiser decided to reduce the sponsors into one line, but the sponsors must be mentioned because they need the credit. Without the sponsors, the software would not have been possible.
People also agreed (as they do here) that if you do not want to see credits in your boot sequence, you can always remove it yourself. After all, it is open source.
Re:Does anyone know what the hell Unisys does anyw
on
Unisys Cracks The Whip
·
· Score: 1
They also do support contracts.
For instance, I bought my last two PC's from MicronPC.com. It came with a 1 year parts and labor warranty. Recently one of the case fans and keyboards stopped working. I called Micron, and they hooked me up with the local Unisys center here in Hawaii. They have very quick service.
I just downloaded the three available movies available on their site with the intention of mirroring them to ease their web server load, but after viewing them I changed my mind.
They are very low quality, grainy movies with pattern tests, a "Hello world" test and stuff. Their site says that were not able to film an actual game yet, so they will post a movie of an actual game soon.
I suggest everyone wait a day or two until the initial/. effect wears down, and they'll perhaps a Tetris game movie will be online. They do however have a pretty neat live-still webcam that you can sometimes see Tetris pieces here
I'm thinking one thing... why the Lesser GPL as opposed to the GPL?
If I am not mistaken, this would allow commercial products to bundle or use the Bochs codebase in their own proprietary products. The GPL does not allow this. As I recall, this confusion was a main reason why the LGPL "Library" GPL was renamed "Lesser" GPL.
Hans Reiser very recently posted the following in response to Linus pre-2.4 announcement. This announcement created a largish problem for reiserfs, as this implies a true feature-freeze when reiserfs is so close to 2.3.
I do hope Linus accepts this last minute reiserfs addition. This is one component that would be of great benefit to Linux.
We now have a working port of reiserfs for 2.3.49, and I am not sure whether you consider us pending. Can reiserfs get in? Putting us in as an experimental file system until we are accepted by the community as known stable is just fine. Our 2.2 version seems to be accepted by the users on our reiserfs mailing list as stable.
We'll port it to the new 2.3.51 starting immediately, the 2.3.49 version will hit our webserver in a few hours.
Sorry we tweaked longer than we should have, and created inconvenience for you.
For small servers, workstations and desktops, I myself believe in the new IDE standard. For systems with small numbers of hard disks, U/ATA 66 is great for the cost/effectiveness ratio.
7200rpm + U/ATA66 can sustain some wickedly fast speeds. For this reason I chose this on an Abit BE6 motherboard and cheap 7200rpm IDE drives for my cheap budget server at my cash strapped school.
I was astounded when I ran an hdparm -t (without cache disk speed test) and it reported 21MB/sec. This went well beyond my expectations from a little cheap IDE drive.
In situations where you only have one disk per controller (the Abit BE6 has two U/ATA 66 controllers), 7200rpm IDE can actually outperform SCSI based systems. (According to an article on Thresh's Firing Squad)
HOWEVER, SCSI still beats the heck out of IDE in reliability, speed and scalability in large and important jobs (enterprise solutions). The redundancy and failover protection of SCSI + raid controllers is not as reliable with IDE (it's possible with stupid human tricks). Don't even talk to me about software RAID. Software RAID is too CPU intensive. SCSI + RAID controllers can do all the failover, drive rebuilding and cool stuff without the CPU knowing anything about it.
Also, the extra bandwidth of SCSI shines when many hard disks are added to the fray. IDE has nowhere near the level of scalability of SCSI.
So basically, I highly suggest U/ATA 66 IDE for desktops, workstations and low budget servers. But for large and important jobs use SCSI.
I hope everyone has a happy 1900! (I really gotta get a new computer...)
As for all of you who stockpiled provisions of food, water and clothing for the encroaching end of civilization, thus far (most, not all) looks well. But the true test will be on Monday when everyone goes back to work, and the world's markets re-open.
If riots, looting and general chaos do not ensue then please consider donating your stockpiles to your local Red Cross or charity agency, for there are many needy people who could use it.
Lets make this new Millennia a time to consider to improve the world, and perhaps one day the homeless and, starving and needy will not exist.
I've been in a few situations where I've spoken with certain *nix project developers (who shall remain nameless), offering my services to add to their project home page and documentation a section for newbies. The response that I have got from most of these developers is RTFM !
Usually, the problem is that people don't read the instructions and the first thing they do is complain. This is where newbies cross the line into lamerness (hmm... everything.blockstackers.com doesn't have a node for this. I'm too lazy). In these cases RTFM would be the best solution.
In the case of a certain unnamed ICQ compatible instant messaging clone project for *nix boxes that utilizes qt2.0, the instructions for average newbie installation were scattered across four outdated documents in obscure locations. This is such a program that lamers would LOVE to use, as this is all they do under their Mic rosoft environment. Thus this would be very necessary for their conversion to Linux (the light side of the force) to be complete.
Unfortunately, if we as the Linux community plan on winning this war of market share, we will have to make things easier for the average lamer (who doesn't RTFM - i.e. the average American). This is the "dumbing down" of Linux that many people fear. Developers can't expect the average lamer to search through four documents and problem solve in order to get an ICQ clone to work. The average lamer would say "Screw it. I'm going back to Windows. (cl ick)"
Lamer Linux(tm) is going to be tough, but I submit that it will be necessary if we are ever to ultimately succeed.
I believe it is classified as a virus, or more specifically a worm, because it replicates and spreads through a network. That's the normal definition of a worm.
Yes, I do agree it is exploiting a security flaw... but in this case it is exploiting a security flaw to create a worm.
It appears that Symantec has already analyzed this virus. This article mentions that the the virus may be protected by an August Microsoft IE5 ActiveX security patch.
This is kinda scary... as we have always taught people that you cannot get a virus by reading mail, only opening attachments. I hope this doesn't become a growing trend.
It looks like there are a lot of questions about other journalling filesystems. I'm no expert on these things, but I have spent quite a bit of time following all three projects and I've read through all available documents on the three filesystems. Here's what I understand of the three.
XFS Originally made by SGI for their IRIX OS, XFS is one awesome filesystem. Read this white paper (http://www.sgi.com/Technology/xfs -whitepaper.html). This white paper describes all of its cool features. The main features of XFS make it a super scalable, very reliable, ultra fast journalling filesystem utilizing many cool FS technologies like B-trees and other cool stuff.
Unfortunately, it seems that currently there are many problems with the Linux implementation of XFS. I don't know any details of this, but I guess it is safe to say that XFS will some day become available for Linux. This would be great.
ext3fs I've only read about this in the linux mailing lists. ext3 appears to be a standard ext2fs implementation with journalling data, allowing backward compatibility with ext2, although one of the authors hinted that they may not make it backwards compatible in some later version. It is currently in super early alpha testing and definately not anywhere close to usable, stable and reliable.
In my opinion this project is very new, and holds much promise. From their README, they appear to be done basic journalling code, and what remains to be done is error handling contingencies, metadata only journalling, performance tuning and lots of other coding. As a result, it may take some time but this could hold much promise and give another viable option for a journalling FS for Linux. Choices are always good.
Reiserfs - http://devlinux.com/namesys/ I've been following reiserfs for a few months now. Its actually been available for quite some time now as a very stable, reliable and quick filesystem for Linux, but it was only recently when journalling was added to the code. Apparently this new addition is supposed to make it faster.
In "releasing" reiserfs, SuSE doesn't mean that it is the first journalling filesystem for Linux. It is the first journalling FS for Linux to be dubbed reliable and suitable for normal use. This is great as journalling has long been a stumbling block for enterprise adoption of Linux. Alan Cox hinted that he may include reiserfs in the standard kernels soon. Excellent =)
Slashdot Mirror
When you have a NFR (not for resale) product from Microsoft, is it legal to GIVE IT AWAY for free? Many people need Windows. If these people got it free and legally, this would prevent that much more money going into Microsoft.
A while back I read that QTSS (Quicktime Streaming Server) was ported from MacOS X (BSD) to other Unixes, and Linux. Anyone know where this can be found?
Umm... this is a modification to Mr. Chasuk?
Yeah. I find Corel Linux a bit questionable in implementation. You hose their entire nice graphical startup thingy with a standard kernel upgrade. Shouldn't be a problem though, just a cosmetic issue.
Your HPT366 IDE bus will show up as /dev/hde and /dev/hdf in Linux.
Is not UDMA Mode 2 ATA33 mode? Mode 2 is 66?
If you have any more problems, e-mail me at warren@togami.com. I spent many hours getting this puppy to work...
An IT manager at a large manufacturer says that's exactly what Microsoft officials told him. "I spoke to some of my contacts there, and found out that the medialess format is primarily designed to be a firewall against competitors like Linux," he wrote, explaining it will make it harder to have a back-out strategy in place if an experimental Linux deployment gets into trouble. "Now I don't have any Windows CDs for the backout. What would you suggest I do if problems with Linux cause me to want to revert back to Windows? To discourage corporations and consumers from changing, they are no longer distributing CDs with every machine, in the hopes that fear of change without any practical possibility of return will discourage most users from even looking at other systems."
This has to be some of the worst anti-competative behavior that we've seen out of the evil empire. While they are likely to be punished severely after the Supreme court battle ending 239 years from now, we consumers would have already suffered severe damage. Bill Gates says that breaking up Microsoft would be one of the most irresponsible things to do, causing great harm to consumers. How ironic, that their own actions, even when you would expect them to start playing nice, cause severe damage to consumers.
Yes, I am an OSS advocate, but we must admit that the world will not switch to OSS solutions overnight. Businesses, old institutions, society in general knows nothing about us. This will slowly change over time. In the mean time, we will still need to keep up with society's standard... which sadly is Microsoft Windows.
Because we still must put up with this monstrosity for a while, we MUST FIGHT THIS. This is not only bad for Windows users (Hey admit it. A lot of you dual boot. I quad boot into Linux, Solaris, Win98 and Win2000 because I have to keep up and support these platforms), but this would SEVERELY HAMPER alternative operating systems. Many systems with Stupid-Evil-Empire-Being-Dumb-Windows-Licenses will effectively lose their ability to re-partition and install alternative operating systems. This will slow down Linux experimentation as the above article points out, because it will become riskier and more expensive for people to experiment.
We're all going to be outraged for a while here, but you know how these things go. We're outraged, and after the article disappears from the ./ homepage we don't hear about it for six months. If the implications of this are correct, this could be one of the worst things to happen since ... umm... err... Sephiroth killing Aeris!
DO NOT LET MICROSOFT GET AWAY WITH THIS! FIGHT THIS!
How? I don't know. I'll leave that to other outraged zealots.
Warren Togami
warren@togami.com p.s. I found this really cool sig today... hehe. Quite appropriate.
If Bill Gates had a dime for every time a Windows box crashed...
...oh, wait a minute -- he already does.
Single drive speed can range from anywhere between 20-31Mb/s (b or B? I can't remember). The truth of the matter is, most people do not exceed their IDE controller's maximum bandwidth. An ATA-66 or ATA-100 controller allows bursts of up to those speeds, because data is temporarily stored in the hard drive or controller cache during that short burst period. In practice however, most people see speeds in the 20's range due to random seeking/reading/writing.
ATA-66 made a big difference for me in drive speed for my squid proxy server, where bursts happen frequently. Drive speed is well below the ATA-66 maximum bandwidth, but my IDE bus has sufficient room for regular bursts which help in speed.
When ATA-66 was first released, Thresh's Firing Squad put up some benchmarks comparing ATA-33 to ATA-66, showing considerable speed improvements in ATA-66. These were synthetic tests showing best case scenarios.... but in practice most people on desktops will not notice much of a difference. In a more recent review of the Abit KA7-100 I believe on HardOCP, the reviewer spoke highly of the potential of the ATA-100 on the KA7-100 motherboard, when he was not too impressed by ATA-66.
You can feed kernel boot parameters from lilo as described in the document here. The workaround for the Promise Ultra33 card works for booting the HPT-366 controller in Ultra33 mode.
I can't find the original post, but Linus once said that perhaps reiserfs will be included during 2.4, but maybe not 2.4.0.
From this post by Alan Cox, he does not appear to rule it out.
> The generic journal layer might not be a bad idea. Stephen and I have
> really duplicated efforts, and that is a waste. I'm more than willing to
> make a go at integrating a generic logging system into the reiserfs code
> base.
Don't blindly follow Stephen's code either. Im sure the best of happens not to be entirely in one code base.
> But, reiserfs 3.6 has come a long way. I feel it is worth putting into
> the kernel soon (I would love to see reports of *heavy* testing), and I
I get requests for reiserfs to be included every so often, and some of them are coupled to things like 'runs fine on our 200Gb build array'. Its certainly getting some good testing
Nano-technology could change this for a technological solution. Self-replicating nanorobots which feed upon the martian materials to build more of their kind would engineer the numbers of machines necessary for terraforming.
Although, this really is the same as the algae solution. In both cases we would have to essentially program the organism (lives, feeds, produces) to do its job.
The reason for all the excess CO2 is the burning of fossil fuels. It would take a billion of these devices with solar panels covering the planet to make a dent into this CO2 production, with costs going into the trillions of dollars.
Why not save a few trillion dollars and reduce the delta of total entropy in the universe by using more alternative power sources in the first place? Solar panels, ocean thermal transfer, hydroelectric, wind and other alternative sources feeding giant flywheels could lower our dependence upon fossil fuels.
Eventually I believe Hans Reiser decided to reduce the sponsors into one line, but the sponsors must be mentioned because they need the credit. Without the sponsors, the software would not have been possible.
People also agreed (as they do here) that if you do not want to see credits in your boot sequence, you can always remove it yourself. After all, it is open source.
For instance, I bought my last two PC's from MicronPC.com. It came with a 1 year parts and labor warranty. Recently one of the case fans and keyboards stopped working. I called Micron, and they hooked me up with the local Unisys center here in Hawaii. They have very quick service.
They are very low quality, grainy movies with pattern tests, a "Hello world" test and stuff. Their site says that were not able to film an actual game yet, so they will post a movie of an actual game soon.
I suggest everyone wait a day or two until the initial /. effect wears down, and they'll perhaps a Tetris game movie will be online. They do however have a pretty neat live-still webcam that you can sometimes see Tetris pieces here
http://bastilleweb.techhouse.org/live.ht ml.
If I am not mistaken, this would allow commercial products to bundle or use the Bochs codebase in their own proprietary products. The GPL does not allow this. As I recall, this confusion was a main reason why the LGPL "Library" GPL was renamed "Lesser" GPL.
I do hope Linus accepts this last minute reiserfs addition. This is one component that would be of great benefit to Linux.
http://marc.theai msgroup.com/?l=linux-kernel&m=95276159801406&w=2
List: linux-kernel
Subject: Re: Linux-2.3.51, and the pre-2.4 series..(can reiserfs get in?)
From: Hans Reiser
Date: 2000-03-10 20:59:05
We now have a working port of reiserfs for 2.3.49, and I am not sure whether you consider us pending. Can reiserfs get in? Putting us in as an experimental file system until we are accepted by the community as known stable is just fine.
Our 2.2 version seems to be accepted by the users on our reiserfs mailing list as stable.
We'll port it to the new 2.3.51 starting immediately, the 2.3.49 version will hit our webserver in a few hours.
Sorry we tweaked longer than we should have, and created inconvenience for you.
Hans
The ultimate distributed DoS attack.
I did a few hdparm drive speed tests a month ago and here's what I can remember from those tests.
/dev/hde
Abit BE6, 7200rpm IBM Deskstar 20.5GB
hdparm -t
pio - 2.60MB/sec
U/DMA33 - 5.60MB/sec
U/DMA66 - 21.20MB/sec
7200rpm + U/ATA66 can sustain some wickedly fast speeds. For this reason I chose this on an Abit BE6 motherboard and cheap 7200rpm IDE drives for my cheap budget server at my cash strapped school.
I was astounded when I ran an hdparm -t (without cache disk speed test) and it reported 21MB/sec. This went well beyond my expectations from a little cheap IDE drive.
In situations where you only have one disk per controller (the Abit BE6 has two U/ATA 66 controllers), 7200rpm IDE can actually outperform SCSI based systems. (According to an article on Thresh's Firing Squad)
HOWEVER, SCSI still beats the heck out of IDE in reliability, speed and scalability in large and important jobs (enterprise solutions). The redundancy and failover protection of SCSI + raid controllers is not as reliable with IDE (it's possible with stupid human tricks). Don't even talk to me about software RAID. Software RAID is too CPU intensive. SCSI + RAID controllers can do all the failover, drive rebuilding and cool stuff without the CPU knowing anything about it.
Also, the extra bandwidth of SCSI shines when many hard disks are added to the fray. IDE has nowhere near the level of scalability of SCSI.
So basically, I highly suggest U/ATA 66 IDE for desktops, workstations and low budget servers. But for large and important jobs use SCSI.
As for all of you who stockpiled provisions of food, water and clothing for the encroaching end of civilization, thus far (most, not all) looks well. But the true test will be on Monday when everyone goes back to work, and the world's markets re-open.
If riots, looting and general chaos do not ensue then please consider donating your stockpiles to your local Red Cross or charity agency, for there are many needy people who could use it.
Lets make this new Millennia a time to consider to improve the world, and perhaps one day the homeless and, starving and needy will not exist.
Warren Togami
warren@togami.com
That's what my computer clock is saying...
Usually, the problem is that people don't read the instructions and the first thing they do is complain. This is where newbies cross the line into lamerness (hmm... everything.blockstackers.com doesn't have a node for this. I'm too lazy). In these cases RTFM would be the best solution.
In the case of a certain unnamed ICQ compatible instant messaging clone project for *nix boxes that utilizes qt2.0, the instructions for average newbie installation were scattered across four outdated documents in obscure locations. This is such a program that lamers would LOVE to use, as this is all they do under their Mic rosoft environment. Thus this would be very necessary for their conversion to Linux (the light side of the force) to be complete.
Unfortunately, if we as the Linux community plan on winning this war of market share, we will have to make things easier for the average lamer (who doesn't RTFM - i.e. the average American). This is the "dumbing down" of Linux that many people fear. Developers can't expect the average lamer to search through four documents and problem solve in order to get an ICQ clone to work. The average lamer would say "Screw it. I'm going back to Windows. (cl ick)"
Lamer Linux(tm) is going to be tough, but I submit that it will be necessary if we are ever to ultimately succeed.
Yes, I do agree it is exploiting a security flaw... but in this case it is exploiting a security flaw to create a worm.
Symantec posted this advisory of the VBS.BubbleBoy here
http://www.symantec.c om/avcenter/venc/data/vbs.bubbleboy.html.
It contains details of what the virus does, where it goes into the registry and how to protect yourself.
If you already do not have that security patch from Windows Update, you can download the patch from
http://www.microsoft.com/s ecurity/Bulletins/ms99-032.asp.
This is kinda scary... as we have always taught people that you cannot get a virus by reading mail, only opening attachments. I hope this doesn't become a growing trend.
XFS
Originally made by SGI for their IRIX OS, XFS is one awesome filesystem. Read this white paper (http://www.sgi.com/Technology/xfs -whitepaper.html). This white paper describes all of its cool features. The main features of XFS make it a super scalable, very reliable, ultra fast journalling filesystem utilizing many cool FS technologies like B-trees and other cool stuff.
Unfortunately, it seems that currently there are many problems with the Linux implementation of XFS. I don't know any details of this, but I guess it is safe to say that XFS will some day become available for Linux. This would be great.
ext3fs
I've only read about this in the linux mailing lists. ext3 appears to be a standard ext2fs implementation with journalling data, allowing backward compatibility with ext2, although one of the authors hinted that they may not make it backwards compatible in some later version. It is currently in super early alpha testing and definately not anywhere close to usable, stable and reliable.
In my opinion this project is very new, and holds much promise. From their README, they appear to be done basic journalling code, and what remains to be done is error handling contingencies, metadata only journalling, performance tuning and lots of other coding. As a result, it may take some time but this could hold much promise and give another viable option for a journalling FS for Linux. Choices are always good.
Ext3 Site - ftp://ftp.linux.org.uk/pub/linux/sct/f s/jfs/
Reiserfs - http://devlinux.com/namesys/
I've been following reiserfs for a few months now. Its actually been available for quite some time now as a very stable, reliable and quick filesystem for Linux, but it was only recently when journalling was added to the code. Apparently this new addition is supposed to make it faster.
In "releasing" reiserfs, SuSE doesn't mean that it is the first journalling filesystem for Linux. It is the first journalling FS for Linux to be dubbed reliable and suitable for normal use. This is great as journalling has long been a stumbling block for enterprise adoption of Linux. Alan Cox hinted that he may include reiserfs in the standard kernels soon. Excellent =)
Warren Togami
warren@togami.com
Damn, wrong file name. http://cranesrus.net/pose30-palmos 35-color-2.jpg