Wikipedia is extremely useful as a starting ground for gathering information about a topic. Like Google, I wouldn't base all my research on Google search results pages, but not having access to Google would put a *huge* damper on my ability to research topics on the web.
Slashdot should do what Groklaw does. The first and second comments on Groklaw are usually "Corrections here, please", and "Offtopic posts here, please". This allows people to discuss random things, while keeping the comments readable.
I don't even buy the idea of having swap space in its own partition.
Then don't. You don't *have* to have a swap partition. I have one because it (presumably) gives better performance, since the filesystem layer isn't involved in every swap to/from disk. At least you have a choice.
What if you need more swap? Then you have to create a swap file on an existing partition and manage two separate swap files in the future. Ugh.
Or, if your swap is at the end of your main filesystem, you can shrink your main filesystem and make a new, larger, swap partition (depending on the availability of resizing tools for your filesystem, of course).
I'm not sure what's so difficult about "managing two swparate swap files", anyway. You create an empty swap file of the desired size (owned by root, with mode 0600, of course), format it with mkswap, add an entry for it to/etc/fstab, run swapon -a (or reboot), and never think about it again. What's to manage?
I used to do that too, years ago (well, I'd slap the case, rather than kicking it). I stopped when one of my violent outbursts was followed by the hard drive suddenly starting to make unpleasant scratching and clicking noises...
This decision in MA reeks of religion and there are many pros I work with - pro-Linux and also very professional - who are deeply opposed to this risky gamble with taxpayer's money. But you'll never hear those facts on Groklaw. That would go against the religion that dominates that site.
My guess is that because the editors see a *ton* of submissions, they often forget which ones they actually posted. Think about it: Do you remember every post you've modded up or down?
My guess is that they'd either take a portion of dividends, fine the individual members of the *board of directors*, or fine the shareholders (who would then file a class-action lawsuit against the board of directors).
But IANAL, and I'm basically talking out of my ass, so I'll probably get modded down for this...
Those who are ignorant of history are bound to repeat it. Does anyone recall Spyglass Software, and what Microsoft did to their product? Remember, older versions of IE were decent.
What Microsoft should do is *outsource* to the Opera crew, i.e. no Microsoft developers would be allowed to touch the code, and Microsoft managers wouldn't be able to manage the project.
They can still be struck down by SCOTUS.
It looks fine to me. Maybe you should get one of these
Sigh. If you have time to read Slashdot, you have time to read the GPL.
Lesson 1a: Read the unofficial Korean translation.
Also, if you want to see it in action, check out http://gpl-violations.org/.
Lesson 1: Read the GPL.
Wikipedia is extremely useful as a starting ground for gathering information about a topic. Like Google, I wouldn't base all my research on Google search results pages, but not having access to Google would put a *huge* damper on my ability to research topics on the web.
Anyone remember Trumpet Winsock?
Slashdot should do what Groklaw does. The first and second comments on Groklaw are usually "Corrections here, please", and "Offtopic posts here, please". This allows people to discuss random things, while keeping the comments readable.
I didn't either, but it sure set off my bullshit meter! I wish I understood it better, so I could compare it to other brilliant things, like Web 2.0.
Then don't. You don't *have* to have a swap partition. I have one because it (presumably) gives better performance, since the filesystem layer isn't involved in every swap to/from disk. At least you have a choice.
What if you need more swap? Then you have to create a swap file on an existing partition and manage two separate swap files in the future. Ugh.
Or, if your swap is at the end of your main filesystem, you can shrink your main filesystem and make a new, larger, swap partition (depending on the availability of resizing tools for your filesystem, of course).
I'm not sure what's so difficult about "managing two swparate swap files", anyway. You create an empty swap file of the desired size (owned by root, with mode 0600, of course), format it with mkswap, add an entry for it to /etc/fstab, run swapon -a (or reboot), and never think about it again. What's to manage?
I used to do that too, years ago (well, I'd slap the case, rather than kicking it). I stopped when one of my violent outbursts was followed by the hard drive suddenly starting to make unpleasant scratching and clicking noises...
I know, and so was my post. It's not like 5 releases is anything to marvel at.
Debian 1.3.1 (bo) was released in 1997. There have been 5 releases since then. :-P
Sigh. Really: You don't need *all* of those hamm CD images on your hard drive.
At least delete the m68k binaries you never used anyway. If they're so important to you, burn them to DVD or something. ;)
Nice job!
This is what FUD is. What you describe is not.
Create an Einstein-Rosen-Podolsky bridge.
That indeed *would* be news. Dust clouds do not form on the moon.
That is just evil.
My guess is that because the editors see a *ton* of submissions, they often forget which ones they actually posted. Think about it: Do you remember every post you've modded up or down?
Right, because alleged vested interests always imply falsehood:
I have a vested interest in diamonds, and I think diamonds are harder than steel, therefore diamonds are not harder than steel.
But IANAL, and I'm basically talking out of my ass, so I'll probably get modded down for this...
What Microsoft should do is *outsource* to the Opera crew, i.e. no Microsoft developers would be allowed to touch the code, and Microsoft managers wouldn't be able to manage the project.
A better analogy would involve NOT USING ANALOGIES!