The Fedora KDE SIG is small. It had only 4 or 5 members at the time (versus 6 now, yippee). There was no way for them to both bring a 4.x desktop into Fedora *and* maintain a 3.5.x desktop. Their choices were to either to be stuck with maintaining an unmaintained version of KDE for the next 6 to 12 months, or to pinch their noses and jump in feet first. Fedora being Fedora, they decided to jump. It's not their fault that the KDE developers screwed up.
By that argument, all content is completely worthless since almost anyone can sit down in front of a computer with Internet access and pull up a very large amount of content on almost any topic imaginable. So why then should I pay an institution for any of it?
Actually, it's not the bleach that kills them. The bleach produces free radicals out of water which then destroy most things they come in contact with. Sort of like what this paint does...
The reason JFS isn't in the kernel isn't because it's "rough around the edges", it's because there is no clean separation between the JFS utils, libs, and kernel code. If you look at ext2, you can easily compile its utils even on a Linux machine that doesn't use ext2 (not that I've seen too many, mind you...). Try the same with JFS. Go ahead, I DARE you.
Yeah, right! Have you seen the code for it? It is a horrid mess. I tried digging through it, and soon found that I would have to rewrite it from the ground up. I'm not surprised LT et al. don't want it in Linux. It's a nice FS, but it's NOT ready to go into the kernel.
I have an LS-120, and I managed to get LILO working on it just fine. The trick is to tell lilo that/dev/hd? has a BIOS code of 0x00. I also find that giving the params also helps:
Then to put it on, you run lilo as you normally would.
CAVEAT: On SCSI-only systems, lilo complains if you try to put it on the LS-120 through command-line arguments pointing to the LS-120. The correct way to do this (for me, I don't know about others) is to put the LS-120 disk in the drive and just run lilo against the hard disk. If you run lilo against the hard disk without a disk in the drive, it complains about/dev/hda not existing or something. I believe that it's because lilo does IDE devices first.
P.S.: Does anybody have a SCSI floppy drive they're looking to get rid of?
Slashdot Mirror
I'll tell you exactly why.
The Fedora KDE SIG is small. It had only 4 or 5 members at the time (versus 6 now, yippee). There was no way for them to both bring a 4.x desktop into Fedora *and* maintain a 3.5.x desktop. Their choices were to either to be stuck with maintaining an unmaintained version of KDE for the next 6 to 12 months, or to pinch their noses and jump in feet first. Fedora being Fedora, they decided to jump. It's not their fault that the KDE developers screwed up.
By that argument, all content is completely worthless since almost anyone can sit down in front of a computer with Internet access and pull up a very large amount of content on almost any topic imaginable. So why then should I pay an institution for any of it?
Unless Citrix or Red Hat ends up ruling it.
So wait...
They have their own M, derived from their own D?
If anyone needed further proof that Microsoft likes to confuse people for its benefit, here it is.
The World Ends With You
Of course, the music needs to match the game. Otherwise, it may as well just be white noise.
Actually, it's not the bleach that kills them. The bleach produces free radicals out of water which then destroy most things they come in contact with. Sort of like what this paint does...
Don't feed the trolls - when an AC says something stupid, let it slide.
How about when someone logged in says something stupid?
On GMailFS!
"Hi, Broadcom? This is everyone else calling..."
Why the hell would anyone want to clone Ruby?
The reason JFS isn't in the kernel isn't because it's "rough around the edges", it's because there is no clean separation between the JFS utils, libs, and kernel code. If you look at ext2, you can easily compile its utils even on a Linux machine that doesn't use ext2 (not that I've seen too many, mind you...). Try the same with JFS. Go ahead, I DARE you.
Yeah, right! Have you seen the code for it? It is a horrid mess. I tried digging through it, and soon found that I would have to rewrite it from the ground up. I'm not surprised LT et al. don't want it in Linux. It's a nice FS, but it's NOT ready to go into the kernel.
Actually, the Nintendo GameCube will use 3" DVDs, and each will hold 1.47 GB of data.
Simple: use an empty passphrase.
What is it with little sisters and Palms? Both of mine want one. I DON'T have THAT kind of money...
disk=/dev/hda
bios=0x00
cylinders=963
heads=32
sectors=8
Then to put it on, you run lilo as you normally would.
CAVEAT: On SCSI-only systems, lilo complains if you try to put it on the LS-120 through command-line arguments pointing to the LS-120. The correct way to do this (for me, I don't know about others) is to put the LS-120 disk in the drive and just run lilo against the hard disk. If you run lilo against the hard disk without a disk in the drive, it complains about /dev/hda not existing or something. I believe that it's because lilo does IDE devices first.
P.S.: Does anybody have a SCSI floppy drive they're looking to get rid of?