Hans Reiser to Sell Company
DVega writes "Due to increasing legal costs, murder suspect Hans Reiser is seeking to sell his company. His lawyer William DuBois said he is running out of money to pay for his defense. DuBois added, 'This is a unique opportunity for someone to buy the company for pennies on the dollar. We welcome all vultures.' This is a good opportunity to own a filesystem and rename it after your own."
CowboyNealFS?
It's even funnier because he has to sell the company to pay the lawyer.
If he turns out to be innocent, it will be just that much sadder -- he will have lost his wife and be ruined. A justice system that is so where money often plays such a key role in influencing the outcome is a very disfunctional justice system.
Provided you licensed it under the GPL, yes, you could do that.
The copyright holder has additional options, however -- Hans Reiser says that he actually makes some money selling the right to use his file system without telling anyone else that they're using it.
(Yes I know, but the corporate world is weird.)
Also, if you RTFM, you'll see that they mention proprietary add-on products, such as a file compressor
Well, DOS is an Operating System. ReiserFS is a FILEsystem.
If you mean Windows should drop NTFS, purchase this, rebrand it and have it ready for Vista's release, than i think you're either trolling or a little naive.
heh, maybe Hans was in deals to sell it to MS (WinFS), but his concience ate away at him, and he ultimately refused. In return, they killed his wife, and now they get their FS on the CHEAP!
This is not the greatest
here comes the GoldenPalace.com file system
those guys will buy anything if it gets them a free bit of news/ pr
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
The IToldYouNotToBotherMeWhenImCodingBitch file system.
OJSystem
.
.
.
(for Open Journaled System, of course)
If ReiserFS uses a magic value somewhere, I suggest it to be changed to 0xDEADBABE.
"It's too bad that stupidity isn't painful." - Anton LaVey
-
Firstly, the admission that you don't own the filesystem (in the sense of employing all the major contributors) is a worry for many customers.
-
Secondly, if you want to put your own secret sauce into the filesystem (perhaps hooking it more intimately into your product's volume management, or providing a shortcut API into your block level IO, or doing extra things for fast failover between control units, or whatever) then you don't want to have to pass this stuff out GPL'd.
-
And finally, if you want to use an otherwise-GPL'd filesystem linked into a non-GPL real-time executive like VxWorks (no relation to VxFS, confusingly) or QNX, having a non-GPL version of the filesystem probably saves everyone a lot of lawyers bills.
I'm not sure I approve of this as a GPL enthusiast --- hey, I had code on the Emacs 17.61 tape! --- but as a customer I don't think I care too much. You don't get to have much oversight of the components used in products you buy unless you're entering into the wild world of source escrow, and buying a non-GPL'd version of a GPL'd product is no different to the OEM buying something completely closed, and in many ways better (I still get the many-eyes thing, up to a point).ian
wait, .002 dollars or .002 cents???
Dude, welcome to linux. Windows has One File System(tm) because... it's easier. Linux has 129 filesystems because 129 different people think each one is the best at what it does.
I love linux, but sometimes too much choice is a bad thing. If linux was a car, there'd be 18 steering wheels and no air conditioning, but you'd be able to change the radio stations from the hubcaps.
sig?
No, Linux has several file systems because there's no such thing as a perfect file system, and even if there were, it hasn't been achieved yet.
Each of the file systems out there has different strengths and weaknesses. If you need maximum reliability, you need a fully journaled file system (data and metadata), but you pay for that reliability in terms of performance. In most cases, you don't need that, but it is important that your file system not become corrupted by a power failure, or similar problem. For those, metadata journaling is enough. In yet other cases, raw speed is the goal, so journaling is a bad idea.
But speed vs. reliability is only one issue to consider. Another is space efficiency, particularly for systems that will have large numbers of small files. Most file systems use one disk block (e.g. 1KB) even for a 100-byte file. Others (like reiserfs) can pack small files together. But that efficiency introduces complexity, which can reduce reliability. So space efficiency vs. reliability is a consideration.
Another tradeoff is read performance vs. write performance. Yet another is performance of small files vs performance of large files. Yet another is reconfigurability -- can file systems be grown or shrunk in-place, perhaps even while in use? That's another tradeoff against complexity and the associated reduced reliability.
For the desktop user, it doesn't really matter. You'll notice little difference regardless of which file system you choose. But there are applications in which the choice of file system can make a significant difference in system performance, space efficiency, reliability, or flexibility.
Windows has One File System(tm) because... it's easier.No, Windows has one file system because Microsoft has never focused on technical excellence. Mediocrity is often an excellent business strategy, and it has certainly proven to be good to Microsoft, but that doesn't mean we can't have better.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.