Nonsense, these medical companies don't pay *any* damages nowadays, almost everything comes right from your own pocket through the overhead that they charge on the medicine and equipment that *you* paid for with your health insurance.
You think that it's good that medical/pharmaceutical companies have increased their revenues year past year without any significant increases in reduction of the major diseases over time?
I'd say that the medical industry has been feeding on the community for way too long. Medical procedures are insanely expensive and the equipment and medicine costs are through the roof. But it's not like medicine got any better in the last 30 years, only the scale has been slowly tipping in our health's favour, but it should have swung completely over already.
The medical industry has consumed more input than it has given back for a very long time. It's time we start seeing some payback to *everyone* who put money in the system: the consumers of medical care.
You're completely forgetting that this is "medicine" we're talking about here, and not "biology". One was to observe nature, the other one for curing people.
there's a native gtk+ implementation for windows, and pretty much any platform
the wx toolkit is extremely unstable. try compiling wx applications on a slightly-different distribution. remember the unicode mess? While the idea of wxwindows was good (portability), the implementation is horrible, and only suitable for binary-form distributions. Anyone doing development (i.e. compile) on Wx will get hung on the spaghetti of build requirements. The latest WxWindows often breaks compile of applications, and vice-versa.
these games *DIE* because the developers pick tools that nobody wants to maintain in the long run. Look at irrlamb: written in scons, needs boost. This is bound to die a quick death as a project. Java gaming? maybe, sure it is cross platform, but your app is horribly VM limited and performance will sucky no matter how you tweak. You kill your project and game by choosing the wrong development tools.
frozen-bubble keeps getting revived but in the end is not compileable with newer versions of SDL_perl. A tragedy, but I ain't gonna fix this, even if it won fancy awards.
the better the toolkit, the longer lived the project - look at the old quake engines...
I would donate plenty of money to anyone who picks a sane tookit to develop a 3D MMORPG that *encourages* development (no python, no boost, no java, plain autotools, C, no c++, SDL+GL, gtk+, no wx). Bring it on.
absolutely not. Any poisening symptoms include headaches and vomiting. Even rat poison will produce those already.
While it is absolutely 100% assured that radiation levels of meteorites will be above normal levels, it's unlikely that they will achieve high levels that cause immediate symptoms as widespread as reported.
If this meteorite was ferrous (heavy metal type), it's much more likely that the impact and subsequent vaporizing of material containing heavy metals (lead, copper are the immediate suspects) will cause these symptoms.
I was able to successfully bypass security in many system call wrappers by creating unmanaged concurrency between the attacking processes and the wrapper/kernel. This was possible on both uniprocessor systems and multiprocessor systems.
So, this doesn't protect UP systems at all. preempt already exposes you to these kind of concurrency issues, and one can only assume that pretty much any RT OS also is vulnerable.
You can't arrest someone on "probable cause", even the police needs more proof than that to "arrest" you. You can use probable cause to search someone, but for a citizens arrest you need to have undisputable evidence (video, eye witness of someone putting something in a bag etc) to perform a citizens arrest.
doing support is nice, but it's not code. I always feel sorry for project people who do nothing but support (translations, artwork etc). They never get a real say in the big project decisions, don't get listed as authors, etc...
You really have to love a project a lot to do just that. It is the least-rewarding job.
1) send it again, send it to the right people 2) if you still think it's a bug that needs fixing, make a stink about it. *convince* people that they need the fix 3) if you still don't get it merged, try posting it to Andrew Morton himself instead of a public ML. Use the To: and Cc: fields wisely
don't fall over and cry. open source developers are really busy and often can't be bothered to read things (hey, 700 mails a day on lkml is surely not helping to get your patch attention!)
Andrew Morton has said it before, and it holds best: "What do I do if I want to be a kernel hacker?". His answer: "fix bugs". This applies for all open source projects. If developers have established that their software has shortcomings, they are very likely to accept solutions. Fixing bugs is the best way to become part of an open source project.
Somehow I think that sending a crew of gay women is going to work out far better, not to mention be more entertaining:)
Seriously though, this is the same issue as sending out men only on submarines, and plenty of research has been done on this topic. While men only on ships works great, putting all gay men together would likely be a disaster (not just fashionwise). For small crews, all male crews work fine, but for larger crews I think a healthy mix would still be preferred.
It appears that this is the long-term goal for ext3cow. If you look at the formatting of the patch it's obvious that they have worked towards fully integrating their code into the kernel tree from the start (instead of building a separate set of code that compiles outside of it just like -e.g.- the fglrx installer does).
I would assume that their next step is to submit it to Andrew Morton and stage it for later merging into the mainline tree. From how the code looks I can see that that might go quite fast.
Thanks for staying polite and maintaining a proper level of attitude. You've demonstrated that you truly are better than single-celled organisms. Way to go.
NVidia's drivers are technically only a hair better really. It's still a binary blob with too many "don't ask, don't complain" hooks on it driving everyone insane (except *ubuntu users).
Open Source 3D accelerated video drivers, that's the way to go. Guess which vendor is pushing these? Right, Intel.
first, I doubt that they will prevent you from loading your own kernel. Intel isn't TiVo you know.
but:
> Also, why is some of the bundled software proprietary? That's so 1999...
what's wrong with that? closed source software is an excellent way to get a platform started and make it economically viable for the future (look at the IBM PC;)).
almost all of the software I've seen in the demo's are open source or replaceable by better open source software. You can choose now to use the closed source app or whatever you prefer. Sounds like an OK deal to me.
I can only assume that they chose this since it will be pre-announced at the IDF in china, as the story said.
It's far more likely that for a US version they will try to get something redhattish, suseish or possibly ubuntuish instead. (oh wait, redflag is redhattish..)
Quote pidgin.im: "Also, we have chosen to go with monotone for our revision control".
That's a clear notice to me that they do not want anyone checking out their source code and having people hack on it.
I once revived a gaim plugin and made it working again, only to be tremendously discouraged by the core gaim crowd (not to mention #gaim has been a worse flame-promoting hostile channel on freenode forever) in actually helping out.
This is a great step for all Open Source IM users I think: Gaim is dead. nobody will know Pidgin, perhaps now a *decent* IM client will arise that doesn't bring the poisoned atmosphere from the gaim crowd.
-- "People built a Linux desktop because there wasn't one to begin with." --
also completely false, Linux of course ran the desktop alternatives that were available for BSD just as well, because of the very same reason you pointed out.
I have no idea when Linux had it's first GUI desktop, but I would think that BSD had one *way* before Linux did, as Xfree86 started in 1992 (and releases as early as 1990) as a coherent project. I don't think Linux even supported X at that time yet.
Slashdot Mirror
Nonsense, these medical companies don't pay *any* damages nowadays, almost everything comes right from your own pocket through the overhead that they charge on the medicine and equipment that *you* paid for with your health insurance.
You think that it's good that medical/pharmaceutical companies have increased their revenues year past year without any significant increases in reduction of the major diseases over time?
I'd say that the medical industry has been feeding on the community for way too long. Medical procedures are insanely expensive and the equipment and medicine costs are through the roof. But it's not like medicine got any better in the last 30 years, only the scale has been slowly tipping in our health's favour, but it should have swung completely over already.
The medical industry has consumed more input than it has given back for a very long time. It's time we start seeing some payback to *everyone* who put money in the system: the consumers of medical care.
You're completely forgetting that this is "medicine" we're talking about here, and not "biology". One was to observe nature, the other one for curing people.
I have no idea why you want gtk+ but no wx
there's a native gtk+ implementation for windows, and pretty much any platform
the wx toolkit is extremely unstable. try compiling wx applications on a slightly-different distribution. remember the unicode mess? While the idea of wxwindows was good (portability), the implementation is horrible, and only suitable for binary-form distributions. Anyone doing development (i.e. compile) on Wx will get hung on the spaghetti of build requirements. The latest WxWindows often breaks compile of applications, and vice-versa.
these games *DIE* because the developers pick tools that nobody wants to maintain in the long run. Look at irrlamb: written in scons, needs boost. This is bound to die a quick death as a project. Java gaming? maybe, sure it is cross platform, but your app is horribly VM limited and performance will sucky no matter how you tweak. You kill your project and game by choosing the wrong development tools.
frozen-bubble keeps getting revived but in the end is not compileable with newer versions of SDL_perl. A tragedy, but I ain't gonna fix this, even if it won fancy awards.
the better the toolkit, the longer lived the project - look at the old quake engines...
I would donate plenty of money to anyone who picks a sane tookit to develop a 3D MMORPG that *encourages* development (no python, no boost, no java, plain autotools, C, no c++, SDL+GL, gtk+, no wx). Bring it on.
absolutely not. Any poisening symptoms include headaches and vomiting. Even rat poison will produce those already.
While it is absolutely 100% assured that radiation levels of meteorites will be above normal levels, it's unlikely that they will achieve high levels that cause immediate symptoms as widespread as reported.
If this meteorite was ferrous (heavy metal type), it's much more likely that the impact and subsequent vaporizing of material containing heavy metals (lead, copper are the immediate suspects) will cause these symptoms.
I was able to successfully bypass security in many system call wrappers by creating unmanaged concurrency between the attacking processes and the wrapper/kernel. This was possible on both uniprocessor systems and multiprocessor systems.
So, this doesn't protect UP systems at all. preempt already exposes you to these kind of concurrency issues, and one can only assume that pretty much any RT OS also is vulnerable.
You can't arrest someone on "probable cause", even the police needs more proof than that to "arrest" you. You can use probable cause to search someone, but for a citizens arrest you need to have undisputable evidence (video, eye witness of someone putting something in a bag etc) to perform a citizens arrest.
irq sharing.... for starters!
You gotta love it ;)
but at least they're already selling linux
(OK, technically not selling, but intel is one of the bigger investors in linux, right up there with redhat, novell, IBM).
doing support is nice, but it's not code. I always feel sorry for project people who do nothing but support (translations, artwork etc). They never get a real say in the big project decisions, don't get listed as authors, etc...
You really have to love a project a lot to do just that. It is the least-rewarding job.
some hints:
1) send it again, send it to the right people
2) if you still think it's a bug that needs fixing, make a stink about it. *convince* people that they need the fix
3) if you still don't get it merged, try posting it to Andrew Morton himself instead of a public ML. Use the To: and Cc: fields wisely
don't fall over and cry. open source developers are really busy and often can't be bothered to read things (hey, 700 mails a day on lkml is surely not helping to get your patch attention!)
Andrew Morton has said it before, and it holds best: "What do I do if I want to be a kernel hacker?". His answer: "fix bugs". This applies for all open source projects. If developers have established that their software has shortcomings, they are very likely to accept solutions. Fixing bugs is the best way to become part of an open source project.
Somehow I think that sending a crew of gay women is going to work out far better, not to mention be more entertaining :)
Seriously though, this is the same issue as sending out men only on submarines, and plenty of research has been done on this topic. While men only on ships works great, putting all gay men together would likely be a disaster (not just fashionwise). For small crews, all male crews work fine, but for larger crews I think a healthy mix would still be preferred.
It appears that this is the long-term goal for ext3cow. If you look at the formatting of the patch it's obvious that they have worked towards fully integrating their code into the kernel tree from the start (instead of building a separate set of code that compiles outside of it just like -e.g.- the fglrx installer does).
I would assume that their next step is to submit it to Andrew Morton and stage it for later merging into the mainline tree. From how the code looks I can see that that might go quite fast.
Thanks for staying polite and maintaining a proper level of attitude. You've demonstrated that you truly are better than single-celled organisms. Way to go.
NVidia's drivers are technically only a hair better really. It's still a binary blob with too many "don't ask, don't complain" hooks on it driving everyone insane (except *ubuntu users).
Open Source 3D accelerated video drivers, that's the way to go. Guess which vendor is pushing these? Right, Intel.
The article conveniently forgets to mention whether the conpression tools are cross-platform (OSX, Linux, BSD) and/or open source or not.
That makes a lot of them utterly useless for lots of people. Yet another windows-focussed review, bah.
first, I doubt that they will prevent you from loading your own kernel. Intel isn't TiVo you know.
;)).
but:
> Also, why is some of the bundled software proprietary? That's so 1999...
what's wrong with that? closed source software is an excellent way to get a platform started and make it economically viable for the future (look at the IBM PC
almost all of the software I've seen in the demo's are open source or replaceable by better open source software. You can choose now to use the closed source app or whatever you prefer. Sounds like an OK deal to me.
I can only assume that they chose this since it will be pre-announced at the IDF in china, as the story said.
It's far more likely that for a US version they will try to get something redhattish, suseish or possibly ubuntuish instead. (oh wait, redflag is redhattish..)
one word: git
Quote pidgin.im: "Also, we have chosen to go with monotone for our revision control".
That's a clear notice to me that they do not want anyone checking out their source code and having people hack on it.
I once revived a gaim plugin and made it working again, only to be tremendously discouraged by the core gaim crowd (not to mention #gaim has been a worse flame-promoting hostile channel on freenode forever) in actually helping out.
This is a great step for all Open Source IM users I think: Gaim is dead. nobody will know Pidgin, perhaps now a *decent* IM client will arise that doesn't bring the poisoned atmosphere from the gaim crowd.
I'll drink to that.
http://www.google.com/search?hl=en&q=two+stone+fiv e+pounds+in+kilo&btnG=Google+Search
14.96 kg
-- "People built a Linux desktop because there wasn't one to begin with." --
also completely false, Linux of course ran the desktop alternatives that were available for BSD just as well, because of the very same reason you pointed out.
I have no idea when Linux had it's first GUI desktop, but I would think that BSD had one *way* before Linux did, as Xfree86 started in 1992 (and releases as early as 1990) as a coherent project. I don't think Linux even supported X at that time yet.
And thus, BSD had a GUI Desktop before Linux.
See also Xfce (www.xfce.org), which has several key developers who work using BSD and Solaris instead of linux.