Actually, while I was a waiting tables at a diner, I discovered that by putting cubes of jello in a glass of cold seltzer, you could create a minimalistic lava lamp.
The classic example is raisins in 7-UP (or sprite, slice or...) which works pretty much the same without the need for super cooled jelo.
Just take about 20 raisins, rinse them and dump them into a glass of clear soda. Raisins go up, raisins go down.
While most medecine is only pretend science, there is some actual science going on beneath the surface.
Actually, alot of medical research is real live science, as the broad topic of medical research includes most of biology, genetics, bioinformatics, and a large slice of biophysics, biochemistry, chemistry, and even some physics.
Now, if you're talking about the practice of medicine itself, that's a slightly different area, predominated with case studies rather than experiments. But that's the fluff primarily located in B and C journals, as opposed to top flight journals like Nature, Science, PNAS, BBA, Biochemistry, etc.
But since debian is based on volunteer work, and has some religious beliefs, great packages like xfree 4.3
Actually, in this case it's because X 4.3 isn't ready for all of the architectures that Debian supports. Unofficial debs are available for 4.3, and have been since its release. Branden Robinson and the rest of the X Strike Force don't particularly like releasing broken software, so they take their time and do it right. [You of course, are more than welcome to assist them. Visit http://people.debian.org/~branden/
mplayer are missing.
Mplayer is a completely different issue. You can get debs from apt-get.org if you want them. There are currently developers working on bringing mplayer to Debian, but the quality of mplayers upstream, especially in regards to copyright and licensing, has caused many in the Debian community to doubt the legality of distributing it. As such, it remains outside the distribution, but can trivially be installed from unofficial sources.
dpkg-buildpackage will generate a diff.gz from the orig.tar.gz and the current source tree, as well as runing all of the sundry dpkg-* scripts, like dpkg-shlibdeps, dpkg-genchanges etc.
It's the right tool to run when you're building a package for upload, but it's overkill when you're building a package to install locally. [Not that you couldn't use it, of course.]
Gentoo also has a nice separation of "cutting edge" from "bleeding edge".
Debian does something similar. Packages that are likely to cause data loss in themselves, and/or other packages generally go into experimental instead of unstable. When they're ready for prime time, or at least play nicely with other packages, they can be migrated into unstable.
apt-get source
cd
fakeroot dpkg-buildpackage -uc -us
Not to be too nitpicky, but you don't need to use dpkg-buildpackage to build a.deb It's used primarily to build packages for upload to debian's archives using dupload. Instead, you can just:
it's simply a legal notice, not a work of authorship.
I'm not quite sure that I follow you, but most licenses (and legal documents) are copyrightable (in the US), at least as of right now. There is currently a case working its way through the legal system regarding building codes (many of which are copyrighted by icbo and the ilk), but that has little or nothing to do with licenses and contracts.
There are plenty of programs distributed under a modified GPL license.
There may be a few minor ones (you really should provide a few examples when you say something like that). However, there are no major programs distributed under a modified GPL known to me. There are programs that are licensed under the GPL with a linking exception in the Copyright, but this does not modify the GPL itself. (Perhaps that is what you were refering to?)
Presumably you could grab the text of the GPL, rename it the "NOWAR-GPL" and throw in some text about not allowing military purposes.
No. That would specifically violate the copyright on the GPL, which specifically states that you can copy and distribute verbatim copies, but modifications are not allowed
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Furthermore, software under such a license would cease to be Free Software, as it would restrict Freedom 0. Such a piece of software would also not be free under the DFSG either.
If you had not done the actions necessary to learn, the connections would not have been made.
Were it were so simple!
What causes you to decide to undergo the actions necessary to learn? What set of events had to occur in order to put you into a position where you were capable of learning?
The mere ability of a mechanism to be self altering or turing complete does not equate to control, or deal appropriately with the presence nor absence of free will. The answer (which I would argue doesn't really exist) is ever so much more complex than that.
Now there I have to agree with you, I think that argument is ridiculous, and I hope it dies the horrible death it so richly deserves.
The libmpeg2 point was brought up simply because it was a case where mplayer developers hadn't followed the GPL in modifying libmpeg2 from mpeg2dec. I don't have time to go through every single stich of code in Mplayer, much of which doesn't have any copyright or authorship statement to determine which code in mplayer can be legally distributed by Debian, and which code cannot. People have already found code in mplayer that was not licensed correctly and prevented Debian from not only distributing the binary, but from distributing the source as well.
It's purpose was to serve primarily as an example of the sorts of licensing issues with mplayer that have been found in the past, and apparently still exist in the codebase. The issue is rediculously trivial to fix. A simple:
This file originated from mpeg2dec [url].
It was modified by foo for use in mplayer on date.
Changes to this file include:
* foo
* baz
A changelog is available at cvs.foo.bar.
in each file from mpeg2dec [and other GPL'ed libraries] modified by the mplayer team would solve this rather pathetic problem with section 2c of the GPL. I have no doubt that there are projects out there that violate section 2c of the GPL, but when it's brought to the project's attention, they tend to fix the problem.
You can even obfuscate just the patches, and publish them with the originals and a patch-applying-script, so no one can accuse you of obfuscating the source - this is simply how we write, you'd say..;)
You could even sell the non-obfuscated code for money;)
Too bad that source code is defined by the GPL as: The source code for a work means the preferred form of the work for making modifications to it.GPL.
All someone would have to do is sue the vendor, and in discovery get access to the source code that they were using to make modifications to. Then they'd probably have no trouble winning against the vendor. [Of course, someone would have to sue them, but then, someone has to sue them to get anything done.]
Error. Third grade math.
$0.1/kwh*0.1kw*240hr=$0.024? Yeah right. More like $2.40.
Lets go ahead and add on the $1.50. Now all of a sudden we're at $3.90, and ~5 years to break even, assuming that the LED lights cost $20 as much as the traditional lights.
That's not even counting the value of your time wasted with a voltage detector debugging those pesky light strings.
Related to the above, the weird thing about debian is their stubborn refusal to use a schedule.
Debian doesn't use schedules that are tied to dates. It uses schedules that are tied to events. Have you somehow forgotten Anthony Town's message regarding the woody release schedule? The software industry is littered with examples of slipped release dates.
"Release when ready", what kind of mantra is that?
What kind of matra should debian posess then? If the software is ready, it gets released. If it's not ready, it doesn't. Those of us who use stable in production environments appreciate the unwillingness of Debian Developers to release a distribution that is not ready, even if it means breaking their precious schedules.
What makes the debian project so special, that they can't use the same basic tool that almost all other projects in the world use?
What good is an arbitrary schedule when it's not tied to reality? If you really feel it's necessary, feel free to make one for Debian yourself...
It gives everyone a common goal to reach for.
The goals of indivdual developers are stated. When those goals are in common, groups of developers share the goals. That being said, there is no central authority that decides who should be doing what. People scratch their own itches, and if they're feeling altruistic, scratch others while they're at it.
Good point but it is easy to fix windows, just re-install:-)
And how long did it take you to reinstall windows the last time you tried? I seem to remember 20 restarts to install w2k with the newest service packs and updates. [And that's not even counting any restarts necessary for applications that I installed.]
Woe be unto you if you happen to (gasp!) be trying to install on random hardware not supported by default and have to go driver searching ontop of the install process.
You folks act like being easy to use is a _bad_ thing. While the rest of the world thinks it's a good thing.
Were it that windows was actually easy to use! Easy to start using perhaps. Easy to use until something really horrible happens, maybe. How much documentation is out there for all of the random keys in the registry? Where are the cli debugging tools documented?
Windows may be easy to use for the vast majority of things that people do, but when things go wrong, as they often do, the difficulty of fixing them far surpasses that of any open source operating system.
But that being said, if people wish to use proprietary operating systems, more power to them. Sometimes a bit of a learning curve is a good thing, because it forces someone to actually learn a bit about the system before the begin using it...
The much higher traffic competitor had a bunch of 1 pixel by 1 pixel frames and each one loaded a copy of the little guy's site. The effect was he was using his own users to DoS his competition.
One wonders why he didn't just use some javascript to break out of the frame jail, and then explain that users had been redirected to foo because bar was loading foo's pages? [Granted, it would have been caught eventually, but for the time being, legitimate traffic might win you a few customers...]
Used as an adverb, irregardless is a synonym for regardless, much as would be expected. Granted it wasn't a word used in the english language in 1913, but it certainly is used now. [Whether it should be or not is a different matter, but it definetly is a word now.]
Too bad part of Indiana observes DST and part of it doesn't, which just makes things even more confusing.
Re:The more I think on it...
on
Portable Hubs?
·
· Score: 2
Re: lame submissions -- Yes, I do get my fair share of those. I've tried to let readers see the kind of stuff that I get that DOESN'T hit the pages every April 1st, but I have to give up that practice for something more original this next year because people hate it when I do that. (I wonder if I should start doing this on Halloween instead as a "trick" instead of the usual "treat".... nah.... I don't look good in digital tomato...)
Why don't you just add another section to slashdot?
The reject of the day section or something, where incredibly lame submissions that (if possible) have some comedic value get sloughed off into. [That way it wouldn't make it to FP, but would be around for people who are into gauging that sort of thing.
I was reading the FAQ and it said that this thing didn't need a monitor or keyboard to boot.
There are very few i386 machines that actually require a keyboard to boot, and none that require a monitor. Most that "require" a keyboard have a bios setting to ignore keyboard errors (and often video errors, so you don't even have to have a video card...)
Having just recent arived in Rochester, NY, (previously in 714, 909 and 213) I was pleasantly surprised at the size of the turnout at the starbucks conveniently located in sight of my desk. It's always nice to be able to talk to fellow tech heads in meatspace, especially those whose circles are outside of yours even online.
Not sure exactly how many people signed up, or how many actually showed, but it looked like a relatively decent time was had by all (even accounting for the lack of ethanol.) [Too bad the organizers didn't seem to show (or at least, remained safely anonymous...)]
lay a conduit with a piece of nylon thru it or some other strong wire. you call pull the fibre through AFTER they finish the sewer system so those sewer contractors dont break the fibre cable.
Actually, a better method is to use an air blown fiber system, without ye olde copious nylon fiber (which often seems to break when it's smack in the middle of the run.) Sumitomo makes a product called FutureFLEX which does this fairly well. (The singlemode runs in between buildings on campus are done using this... which means you trench once and almost never have to trench again.)
Slashdot Mirror
Just take about 20 raisins, rinse them and dump them into a glass of clear soda. Raisins go up, raisins go down.
Now, if you're talking about the practice of medicine itself, that's a slightly different area, predominated with case studies rather than experiments. But that's the fluff primarily located in B and C journals, as opposed to top flight journals like Nature, Science, PNAS, BBA, Biochemistry, etc.
dpkg-buildpackage will generate a diff.gz from the orig.tar.gz and the current source tree, as well as runing all of the sundry dpkg-* scripts, like dpkg-shlibdeps, dpkg-genchanges etc.
It's the right tool to run when you're building a package for upload, but it's overkill when you're building a package to install locally. [Not that you couldn't use it, of course.]
Or better, just grab a debian ppc netinst iso, and install away. (Debian tends to have more software built for ppc than yellowdog.)
Furthermore, software under such a license would cease to be Free Software, as it would restrict Freedom 0. Such a piece of software would also not be free under the DFSG either.
What causes you to decide to undergo the actions necessary to learn? What set of events had to occur in order to put you into a position where you were capable of learning?
The mere ability of a mechanism to be self altering or turing complete does not equate to control, or deal appropriately with the presence nor absence of free will. The answer (which I would argue doesn't really exist) is ever so much more complex than that.
It's purpose was to serve primarily as an example of the sorts of licensing issues with mplayer that have been found in the past, and apparently still exist in the codebase. The issue is rediculously trivial to fix. A simple:
This file originated from mpeg2dec [url].
It was modified by foo for use in mplayer on date.
Changes to this file include:
* foo
* baz
A changelog is available at cvs.foo.bar.
in each file from mpeg2dec [and other GPL'ed libraries] modified by the mplayer team would solve this rather pathetic problem with section 2c of the GPL. I have no doubt that there are projects out there that violate section 2c of the GPL, but when it's brought to the project's attention, they tend to fix the problem.
All someone would have to do is sue the vendor, and in discovery get access to the source code that they were using to make modifications to. Then they'd probably have no trouble winning against the vendor. [Of course, someone would have to sue them, but then, someone has to sue them to get anything done.]
Error. Third grade math.
$0.1/kwh*0.1kw*240hr=$0.024? Yeah right. More like $2.40.
Lets go ahead and add on the $1.50. Now all of a sudden we're at $3.90, and ~5 years to break even, assuming that the LED lights cost $20 as much as the traditional lights.
That's not even counting the value of your time wasted with a voltage detector debugging those pesky light strings.
Woe be unto you if you happen to (gasp!) be trying to install on random hardware not supported by default and have to go driver searching ontop of the install process.
Windows may be easy to use for the vast majority of things that people do, but when things go wrong, as they often do, the difficulty of fixing them far surpasses that of any open source operating system.
But that being said, if people wish to use proprietary operating systems, more power to them. Sometimes a bit of a learning curve is a good thing, because it forces someone to actually learn a bit about the system before the begin using it...
We'll pick nits some more.
Used as an adverb, irregardless is a synonym for regardless, much as would be expected. Granted it wasn't a word used in the english language in 1913, but it certainly is used now. [Whether it should be or not is a different matter, but it definetly is a word now.]
The reject of the day section or something, where incredibly lame submissions that (if possible) have some comedic value get sloughed off into. [That way it wouldn't make it to FP, but would be around for people who are into gauging that sort of thing.
It was on Mt. Hope just south of Elmwood. (My desk in Eastman dental faces east onto Mt. Hope.)
Having just recent arived in Rochester, NY, (previously in 714, 909 and 213) I was pleasantly surprised at the size of the turnout at the starbucks conveniently located in sight of my desk. It's always nice to be able to talk to fellow tech heads in meatspace, especially those whose circles are outside of yours even online.
Not sure exactly how many people signed up, or how many actually showed, but it looked like a relatively decent time was had by all (even accounting for the lack of ethanol.) [Too bad the organizers didn't seem to show (or at least, remained safely anonymous...)]