To follow up, there are HEAPS of files in MPlayer which were released under the GPL. I can't see how the MPlayer authors can possibly not release MPlayer under the GPL.
Files which contain a GPL Licence statement in MPlayer:
grep -rn "General Public License" *|cut -f 1 -d:|sort |uniq
If MPlayer is not released under the GPL, then
that's probably a GPL violation. In my MPlayer
build directory, there is a file called
ac3-iec958.c which was released under the GPL
by Juha Yrjölä. Because ac3-iec958 is built
into MPlayer, by the "viral nature" of the
GPL, surely the whole of MPlayer must be
released under the GPL.
On a press conference, A'rpi said the big truth: he hates GPL! Well this sounds very rude from him, but let everyone know what happened! The poor fella tried to compile a flash disk driver into the kernel to boot from it and... it wouldn't! The little geezer is non-GPL so he can't be compiled into the kernel, which is in fact GPL! Let me quote him:
rts NOW! GPL SUX - Utalom!!! - kibaszott szemet! - which I now don't want to trto english. Now he has rm -rf/*GPL* in crontab.
Order MPlayer - Boycott GPL! T-shirts NOW!
Now I'm confused. Do these MPlayer likes like the
GPL? Or do they hate it?
You should consider boycotting Xboxes, because they
did a "Vandal Marketing" campaign in Sydney. This
was similar to the IBM campaign. Microsoft paid
another company to go and paint green "X"s all over
the place. The Councils are very annoyed about the
damage to their footpaths and want to charge the
advertising company for the cost of cleaning off
the advertising. Xbox vandals
There is a new technique called "Don't Click On
The Link Of Stories You Don't Want To Read".
Apparently it allows people to decide whether they
want to read the story just by looking at the
headline, and if it says "New Linux Kernel Out",
it allows the user to not click the link, thus
avoiding the story they didn't want to read. I
can't see how this new-fangled "Don't Click The
Link" technology could possibly work, but some
people say they are very happy with it.
It's about time somebody released a new Linux
distribution:
"VeggieLinux: The easy to use
desktop Linux that administers itself!".
After all, if Apple can get a bunch of Mac-lovin'
frootloops to accept a BSD system, and somehow
worked out a way that it can keep running, there's
really no excuse for Linux to not have an easy-to-use, easy-to-maintain distribution
especially designed for novice desktop use.
You'd take a bottle of methanol, squirt it on the sponge, and the fan would start to spin, slowly at first, and building up in speed as the cell heated up to optimum temperature (which I think was around 50-60 degrees celsius).
Fifty or sixty degrees?? That could be the
killer for a laptop application, because who wants
a laptop running at 60 degrees in your lap? YOW
BURNY!
I hate having to fsck my / partition (which is still stuck in ext2 land because I'm afraid to change it).
All you have to do is make a tiny/boot partition
which can be ext2. Then you can easily use ReiserFS, ext3, XFS, or whatever you want for your
root partition. If your system crashes, you would
only have to fsck about 15 megabytes or whatever
the smallest partition you could use is.
Oh yes, XP crashes BEAUTIFULLY! The old Blue Screen Of Death was flat and boring, but XP's Blue Screen Of Death is simply GORGEOUS! It's got animation, drop shadows, bells, whistles, and a funny little cartoon of a sad computer. I just can't wait for XP to crash again! Luckily I don't have to wait long!
I don't think we need TLDs at all. Why should we
type "www.microsoft.com" when we could just put
"www.microsoft"? And what about that "www"? It
does nothing. We could just put "microsoft". If
somebody REALLY wants a "TLD", they could have
a name like "slashdotorg", or even "wwwslashdotorg". I say we just get rid of all
the TLDs. They're useless. And get rid of that
"www" while we're at it.
I got the patches from Microsoft for Microsoft(TM)
IIS(TM) running on Microsoft(TM) Windows(TM) NT(TM)
for one of my work machines. I installed the patches, now the IIS(TM) web server, the ftp server
and even the Gopher server won't start. They all
get an error saying "The specified module could
not be found". So yeah, great patches. They stop
the worm from spreading by breaking IIS(TM).
Thanks Microsoft.
I thought most (if not all) "modern" type Mobo's and BIOSes worked together to keep you from powering a system up without a processor fan running.
If the heatsink and fan falls off the CPU, then
the fan could still be running, but the CPU gets
no cooling. Which means BZZZZZZZZZZZZZZTTTT!!!!
GAAAAAAAAAAAAAAAAAAAHHHH!!1! That's why in the
article it says to check your heatsink is firmly
attached every month. It would also be good to check it after moving the computer around, because jolting it could make it fall.
If your heatsink does fall off, you only get about
one second before your CPU gets up to 300C and melts. That means that there's no time to do an
emergency shutdown anyway. It looks like Pentium IVs are better than AMD Thunderbirds in this regard.
Ok, let's assume (even if you don't agree with it)
that letting governments have backdoors into
encryption is good. Then a government (surely we
don't think that the US Government should be the
only government allowed to read the whole world's
encrypted messages?), any government, can read any
encrypted message any time they like, subject to
privacy laws. For the sake of the argument, let's assume that this is a good thing.
Now what stops somebody else, not a government, using the backdoor to read somebody's
secret message? Won't putting backdoors in
potentially make encryption useless?
Of course, this law will do nothing to stop people
passing uncrackable secret messages if they want
to. Another day, another stupid law.
it earned him a Hugo Award to (spoiler) postulate that a black hole dropped into Mars would oscillate back and forth through the planet until it eventually all was eaten up and entered the singularity.
I think that's wrong, actually. If you dropped
a black hole on a planet's surface, it would
fall until it hit the ground, then it would
start consuming the ground it hit. It would
keep falling until it hit the centre of the
planet, getting more massive as it fell and
ate more of the planet. Because it gets
more mass as it falls, after it goes through
the centre of the planet, it will go slower
more quickly as the gravity of the planet
pulls it back towards the centre at the same
time as it gets heavier due to eating more of
the planet. Therefore, it would go slower each
time, until it would stop at the centre, sucking
in the rest of the planet. I don't think it would
make it all the way through the planet even once.
If these high-energy particles they will be making will produce black holes, then there are about 100 black holes produced per year as a result of cosmic radiation - and they haven't been detected yet, so obviously they have a pretty small effect, and there's nothing to worry about.
Well maybe. What if black holes in the upper
atmosphere aren't dangerous, but black holes
down at ground level just keep getting bigger
until they swallow the whole planet? I'd rather
they didn't find that out through one final,
catastrophic experiment.
I agree it may be childish and immature to lash out wildly. However it is probably a good strategy over all.
Sure it may bot be the best response this time but unrestrained response will definatly make it less likely to happen again. Terrorism only works when the response is restrained (they hide in some unidentifiable group and hope to slowly wear down the resolve of the other party).
If we show a consistant tatic of responding irrationally even when the results are perhaps not the best for us in the short run we may be better off in the long term.
That might be what "they" want you to do. Lashing
out irrationally would be a bad response. The
US military and intelligence services needs to
determine who is responsible, and retaliate in
an appropriate fashion.
Out of curiosity, are laptop batteries always made up of a large number of linked, smaller, cylindrical batteries?
All batteries are made up of a number of cells.
What people commonly call a "battery" (like an
AA, a C, a D, or an AAA), is actually a cell. If you look at
your car battery, you might be able to see that
it is made up of six cells. Each one has its own
compartment, and its own plug on top for adding
more water if it gets low.
The reason for this is that a cell puts out about
2 volts. To get a higher voltage, you have to
connect several cells in series to make a battery.
For a car, you need six cells to make twelve volts. For a telephone exchange, you need 24 cells
to make about 50 volts. You can also connect several batteries together in parallel to get more
current or more power.
Rich Text Format. If you're sending it to a windows newbie who panicks when it doesn't say ".doc", tell him to open it anyway -- word will understand it.
You can't tell them to just "open it anyway",
otherwise you'll be spending the next week cleaning up all the viruses, trojans, and worms
they'll get infected with by just opening all
attachments. But at least you'll get a lot of
nice "I LOVE YOU!" email from them.
Well sure, that's a lot of people. But are any
of them brain surgeons? Because it says in the
article that they need to be brain surgeons to
build these chips:
``It's a difficult thing to do right, and it takes brain surgeons to do it,'' said Whiteside, a former senior design manager at IBM who recently joined Intrinsity's advisory board.
Actually, it makes me wonder how hard brain
surgery could be anyway. Cut somebody's head
open, slice bits of the brain out and throw them
in the bin. Sew the head back together. Brain
surgery! It's easy! Easier than designing hardware!
To follow up, there are HEAPS of files in MPlayer which were released under the GPL. I can't see how the MPlayer authors can possibly not release MPlayer under the GPL.
:|sort |uniq
Files which contain a GPL Licence statement in MPlayer:
grep -rn "General Public License" *|cut -f 1 -d
ac3-iec958.c
drivers/3dfx.h
libac3/ac3.h
libac3/ac3_internal.h
libac3/bit_allocate.c
libac3/bit_allocate.h
libac3/bitstream.c
libac3/bitstream.h
libac3/coeff.c
libac3/coeff.h
libac3/crc.c
libac3/crc.h
libac3/debug.c
libac3/debug.h
libac3/decode.c
libac3/decode.h
libac3/dither.c
libac3/dither.h
libac3/downmix/downmix_3dnow.S
libac3/downmix/downmix.c
libac3/downmix/downmix_kni.S
libac3/downmix.h
libac3/exponent.c
libac3/exponent.h
libac3/imdct.c
libac3/imdct.h
libac3/mmx/imdct_3dnow.c
libac3/mmx/imdct512_kni.S
libac3/mmx/imdct_kni.c
libac3/mmx/rematrix_3dnow.c
libac3/mmx/srfft_3dnow.c
libac3/mmx/srfft_kni_c.c
libac3/mmx/srfft_kni.S
libac3/mmx/srfftp_3dnow.h
libac3/parse.c
libac3/parse.h
libac3/rematrix.c
libac3/rematrix.h
libac3/sanity_check.c
libac3/sanity_check.h
libac3/srfft.c
libac3/srfft.h
libac3/srfftp.h
libac3/stats.c
libac3/stats.h
libmpeg2/attributes.h
libmpeg2/header.c
libmpeg2/idct.c
libmpeg2/idct_mlib.c
libmpeg2/idct_mmx.c
libmpeg2/mm_accel.h
libmpeg2/mmx.h
libmpeg2/motion_comp.c
libmpeg2/motion_comp_mlib.c
libmpeg2/motion_comp_mmx.c
libmpeg2/mpeg2.h
libmpeg2/mpeg2_internal.h
libmpeg2/slice.c
libmpeg2/sse.h
libmpeg2/stats.c
libmpeg2/vlc.h
libvo/video_out.c
libvo/video_out_internal.h
libvo/vo_3dfx.c
libvo/vo_mga.c
libvo/vo_null.c
libvo/vo_sdl.c
libvo/vo_syncfb.c
libvo/vo_xmga.c
libvo/yuv2rgb.c
libvo/yuv2rgb.h
libvo/yuv2rgb_mlib.c
libvo/yuv2rgb_mmx.c
opendivx/idct_c.c
opendivx/idct_mmx.c
TOOLS/mp.pl
TVout/fbset/modeline2fb
Please explain?
You should consider boycotting Xboxes, because they did a "Vandal Marketing" campaign in Sydney. This was similar to the IBM campaign. Microsoft paid another company to go and paint green "X"s all over the place. The Councils are very annoyed about the damage to their footpaths and want to charge the advertising company for the cost of cleaning off the advertising.
Xbox vandals
There is a new technique called "Don't Click On The Link Of Stories You Don't Want To Read". Apparently it allows people to decide whether they want to read the story just by looking at the headline, and if it says "New Linux Kernel Out", it allows the user to not click the link, thus avoiding the story they didn't want to read. I can't see how this new-fangled "Don't Click The Link" technology could possibly work, but some people say they are very happy with it.
So... has anybody found any bugs on 2.4.15 yet?
It's about time somebody released a new Linux distribution:
"VeggieLinux: The easy to use desktop Linux that administers itself!".
After all, if Apple can get a bunch of Mac-lovin' frootloops to accept a BSD system, and somehow worked out a way that it can keep running, there's really no excuse for Linux to not have an easy-to-use, easy-to-maintain distribution especially designed for novice desktop use.
Ooh, hoist on his own petard. You'll notice that he's not "critizing" anybody's spelling, however.
Oh yes, XP crashes BEAUTIFULLY! The old Blue Screen Of Death was flat and boring, but XP's Blue Screen Of Death is simply GORGEOUS! It's got animation, drop shadows, bells, whistles, and a funny little cartoon of a sad computer. I just can't wait for XP to crash again! Luckily I don't have to wait long!
I don't think we need TLDs at all. Why should we type "www.microsoft.com" when we could just put "www.microsoft"? And what about that "www"? It does nothing. We could just put "microsoft". If somebody REALLY wants a "TLD", they could have a name like "slashdotorg", or even "wwwslashdotorg". I say we just get rid of all the TLDs. They're useless. And get rid of that "www" while we're at it.
Here's a simple perl program that listens on a
port. If you set it to listen on port 80, it will
print out what comes in on that port.
#!/usr/bin/perl -w
use IO::Select;
use IO::Socket;
use strict;
unless (@ARGV > 0) { die "usage: $0 " }
my $port = shift(@ARGV);
my $work_no = 0;
my $sel = IO::Select->new();
sub REAPER
{
wait;
}
$SIG{CHLD} = \
my $server = IO::Socket::INET->new(Proto => "tcp",
LocalPort => $port,
Listen => SOMAXCONN,
Reuse => 1);
die "can't setup server: $!" unless $server;
print "server $0 accepting clients\n";
my $client = 0;
my $serial = 0;
while ($client = $server->accept())
{
if (fork() == 0)
{
my $remote_ip = "";
$client->autoflush(1);
$remote_ip = inet_ntoa($client->peeraddr);
print scalar(localtime), " connect from ", $remote_ip, "\n";
my $line = "";
while($line = )
{
print $line;
if ($line !~ m/\S/)
{
last;
}
}
close $client;
}
else
{
close $client;
}
}
I got the patches from Microsoft for Microsoft(TM) IIS(TM) running on Microsoft(TM) Windows(TM) NT(TM) for one of my work machines. I installed the patches, now the IIS(TM) web server, the ftp server and even the Gopher server won't start. They all get an error saying "The specified module could not be found". So yeah, great patches. They stop the worm from spreading by breaking IIS(TM). Thanks Microsoft.
If your heatsink does fall off, you only get about one second before your CPU gets up to 300C and melts. That means that there's no time to do an emergency shutdown anyway. It looks like Pentium IVs are better than AMD Thunderbirds in this regard.
>I bet if you change just the "" + x to just x, you'll shave off those extra 4 seconds.
// added for emphasis
// added for emphasis
// println is not in the loop
You lose that bet, because the println is only executed once. Read the code again. I added some
extra braces for emphasis:
public static void main(String args[])
{
float x = 0;
int counter = 0;
for(counter = 0; counter < 10000000; counter++)
{
x += (counter / 3.14159265359);
}
System.out.println("" + x);
}
Ok, let's assume (even if you don't agree with it) that letting governments have backdoors into encryption is good. Then a government (surely we don't think that the US Government should be the only government allowed to read the whole world's encrypted messages?), any government, can read any encrypted message any time they like, subject to privacy laws. For the sake of the argument, let's assume that this is a good thing.
Now what stops somebody else, not a government, using the backdoor to read somebody's secret message? Won't putting backdoors in potentially make encryption useless?
Of course, this law will do nothing to stop people passing uncrackable secret messages if they want to. Another day, another stupid law.
MK11T9`/*"1M:@@R*%5NF[\FRFFY3$FQ80:+)
Whoopsie! That could have been an encrypted message!
The reason for this is that a cell puts out about 2 volts. To get a higher voltage, you have to connect several cells in series to make a battery. For a car, you need six cells to make twelve volts. For a telephone exchange, you need 24 cells to make about 50 volts. You can also connect several batteries together in parallel to get more current or more power.