Sorry, but I can't get up the slightest bit of excitement for a "solar" boat... First of all because they've been wind-powered for quite a lot longer than they've been diesel-powered. Secondly, because the ocean doesn't have any minimum speed-limit, so ANY ammount of energy will eventually get them where they are going (like a solar-powered blimp). And last but not least, because boats need a tremendous ammount of maintenance (unlike cars), which is where the bulk of the operating expense is... not the fuel (unlike cars).
The solar powered airplane sounds like a great idea, until you read that it has to FALL all night long to maintain its airspeed... That strikes me as being quite impractical for anything but an exhibition. So... interesting, but not showing how practical solar-powered planes can be.
In other words, they're not going to bother tapping your phones. They're going to reserve that to those receiving phone calls from terrorists.
Yeah... terrorists. Not political opponents... Not outspoken political activists... Not people falsely accused based on ridiculously bad and unchecked information...
You get out no more than was put in. We are using at a faster rate than it can be replenished.
The energy "put in" is comming mostly from SUNLIGHT, not from what we put into it.
And the sun is outputting so much power to the surface of the earth, that it absolutely dwarfs worldwide energy consumption by an unbelivable margin. If we use the more effecient plants for creating biodiesel, it would supply our ever-increasing demands for energy for millenia to come, before we'd have to look elsewhere, or put much work into increasing effecincy.
Not only that, they are unsustainable, if you want to buy any technological equipment, that is.
You'll always be able to find basic devices (like wireless APs) from thousands of companies. You may have to stay away from the major brands, but you can still probably buy your equipment from the same nameless Chinese company D-Link, Linksys, etc. buy their parts from!
Besides that, there's no reason you have to buy wired/wireless routers from anybody. A litte software on a low-cost embedded board, and you're set. You can probably get off as cheap as the junk you get from Linksys, and have a far, far better and more functional device, too.
Given that, the only thing that we can really blame them for is the poor response to the initial problem report, and the time it took to realize the enormity of the problem and make amends.
Gee, so the ONLY THING we can blame them for is unleashing their attack lawyers on Kamp, when they were clearly in the wrong... That's more or less the ONLY THING people hate about the RIAA/MPAA, as well.
Now that D-Link has RESOLVED the problem, I can't see any problem with buying from them in the future. However, until now, it was a very good reason to spend your money elsewhere. That (little bit of) pressure may have been partly responsible for convincing them to settle things with Kamp.
The definition of what "works" changes when something newer and better comes along. Certainly something with vastly improved stability, security, and flexibility would move Linux from the "works" column to the "used to work" column.
Microkernels are also shipping from QNX and, uh and, oh I'm sure there are a few more.
You need look no further than OpenVMS. The preeminent example, and damn good proof of the concept, in the real world.
The only evidence you need, is the development pace of Hurd or even QNX to show this.
Not true at all. You can list some incredibly slow-moving monolithic kernels too, I'm sure.
HURD is a good example of bloat and bureaucracy in software design, and not a fair example of anything else.
but the fact that one bad driver can crash the whole works tends to make people work much harder to create solid drivers that don't crash.
So your solution is... everyone should write code without any bugs, then microkernels won't provide any advantage?
The idea has been tried over and over again, and nobody has been able to write perfect code for anything of more than trivial complexity.
Look at something like OpenSSH, which was written by the most security-paranoid people out there (the OpenBSD team), but still ended up with a remote-root exploit. The solution is to write good code, AND to have it executing with the least ammount of privlidge possible. The two aren't mutually exclusive (OpenSSH has priv-sep now, and it hasn't instantly turned into a mess).
Didn't need to turn on several hundred, place the disks in, close the thing, and then reboot - you could push in all the disks and reboot.
No need to boot-up the systems to open the CD tray; That's what a paperclips are for... At power-on, the tray will close itself, and you're set. Not to mention that slot-loading CD/DVD drives are just as cheap, and don't have that problem.
Not to mention that floppy drives are signifigantly cheaper than cd-roms
True, floppy drives are about 50% cheaper, but if the kind of price difference is an issue, you'd just stick with PXE (or, yes, possibly USB bootable drives).
Plus, at home, for somethings the floppy is just more reliable.
What things? Saying "oh yes they are!" isn't very convincing. I keep asking, and still get no good answers.
Just because something *can* be done doesn't mean it is the best solution
No, but in this case, because of numerous limitations of floppies, it is.
For a start you have to get the driver disk image off the original media
I was very clearly talking about floppy images. If you already have a floppy, it changes things slightly. Even in that case, you're only talking about perhaps one minute more time to make a CD.
The casual home user may imagine sysadmins making custom install CDROMs for every system at every stage instead of inserting a driver floppy
Complete bullshit. I was administering over 100 Windows machines just a few years ago, so I know full well how it works. There I would just dump the Windows files on a network server, and add-in any additional drivers needed for ANY of the machines. It's quite simple really, if you have any idea what you're doing.
And if you want to do it with physical media, you certainly don't need a CD for each one. Spend a couple minutes, add ALL the drivers that will be needed by ANY of the machines, and just burn one CD you can use for all of them. Quite trivial, and it's not more work, it's infinitely less.
but apply some critical thought to that imagination and consider that there is other stuff to do instead of creating pointless work.
I think the mod who gave me a -1 Troll, must have been aiming for your post, and missed...
Well, the rule for MPlayer is that bugreports need to be against CVS, since it may have been fixed in the intervening year since 1.0pre7 was released. You didn't say which version you're using, but I assume it's 1.0pre7 (or earlier!). If you don't have the problems with the official RPMs or source, then the complaint should go to Fedora.
If it's just another broken distro package... no, nobody wants to hear about it. That's the norm, not the exception.
If distributions are breaking your software, you need to find out how and get them to fix it, as it is RUINING your reputation for me and anyone else seeing the same problems.
The distros really don't give a damn. They completely ignore the packaging guidelines, make incredibly buggy MPlayer packages, and ignore all complaints. The nature of GPL'd software is that you can't force them to do anything, and they certainly aren't jumping at the chance to get their packages fixed.
What to do? Post a story on/. shaming them for their insanely broken packages?
I recall exactly what the issues were, and other than a few, very early problems that were mostly fixed by 7.1, and all fixed by 7.3,
Many people say similar things...
I've seen many people that, when told they have a hardware problem, respond, indignantly, that no other software has problems, only MPlayer. Then a few weeks later, you'll see a message from the same person, saying their CPU fan was going out, and appologizing...
MPlayer's aggressive code makes for the perfect test of any compilier... Every other application on the planet can compile perfectly, and yet you'll find bugs with MPlayer. -O3, -march, lots of ASM, 3dNow, SSE, MMX, etc.
where you want to load extra drivers supplied by the manufacturer just after boot time.
Home users aren't too likely to use a RAID controller, and servers are unlikely to be installed from the standard disc. Even small companies slipstream their Windows CD, and add any extra patches and drivers they want before installing it on a single machine. It's quite easy.
As for the other point - it takes less time to plug a floppy in than it does to move a drive about or burn a CDROM that pretends it is a driver floppy disk.
It takes less time to burn and boot from a CD than it does to write and boot from a floppy. Floppies are so damn slow, not to mention it'll be 100% perfect on the CD every time, and a previously used floppy will have CRC errors half the time...
Besides, I can't remember the last time I got any products with a floppy. Companies have simply switched to CDs for everything.
Moving a drive may take some time... or not. Hard drive caddies make things quite fast. My firewall/router is also trivial to move, as it's just a CF disk in a front drive bay.
the floppy disk is the one that is missed the most during setup.
Maybe because they DO come in handy every once and a while?
For what? If you've got some boot floppies you still use, grab a copy of isolinux (syslinux) and you can put all the images on a single CD, which will boot on any system made in the past 10 years.
I still keep a couple old systems (10+ years, non-bootable CD-ROMs) around, but I find it's much easier and faster to pull out the hard drives, and plug them into a modern system for OS (re)installation. Everything else just goes over the network.
And bouncer probably duplicates packets to many IPs and only one of them belongs to the publisher and publisher sends ack directly to the leacher spoofing IP of the bouncer. can be tricky to figure out what is going on without log of all IP headers on all participating gateways and routers.
I can't see bouncers having much of a life, at least on the public internet. There aren't many people that want to donate large ammounts of bandwidth to P2P users. But, I suppose it's necessary for publishers who cannot spoof their IP. Though I really find it hard to believe that only 20% of hosts can spoof their source addresses. I've seen too many DDoS attacks, far too recently, to believe that's really the case.
For spoofing IP in Java you will have to add dummy IP interface in your system.
That's a very unfortunate restriction. I believe, for an anonymous P2P network to be successful, you really need to just have a configuration option. Maybe have it try spoofing source addresses in the same/24 block, or in the multicast range, by default.
The message collector idea is... interesting, but I can't imagine it's very practical. Surely anyone that needs like kind of security has a better (more deniable, for both sender and reciever) system in place.
I do? I mentioned it in two, short, sentences. One was in reference to the other, as well.
mentioning != harping
The thing was, everyone else proceded to have the exact same problems a few months later when gcc 3.0 was officially released. There WERE some compiler bugs in 7.0's gcc 2.96, but they were minor and fixed quickly. The REAL PROBLEM was that gcc 2.96 and thus gcc 3.0 enforced standards that gcc 2.x had always been lax about, and thus many programs needed small fixes in order to compile correctly.
So, if you're going to tell a user that their problems aren't problems, but rather stupid platform issues that the player can't possibly do anything but seg fault on,
That is generally the case. Media players, MPlayer in particular, are the first symptom of something being horribly wrong with your system, since they are so timing dependant, make extensive use of extended instructions (MMX, 3DNow, SSE, etc), lots of assember, etc. When system code is corrupt, or when your hardware is changing bits due to heat or other bugs, there's nothing programs like MPlayer can do about it.
you might want to talk about the current day and modern compiler releases,
Wait a minute. First of all, you JUST SAID that gcc 2.96 *is* current, or don't you remember?
"and 2.96 is STILL used in many production environments because of its massive improvements in the implementation of C++"
Besides that, I can tell you that I did see a strange bugreport on mplayer-users around a month ago, that was tracked-down to a gcc 2.96 bug. And I should mention that MPlayer works quite well on both 2.95.3 and 3.x, so you can't claim it's some strict rule somewhere, or C++ problem (MPlayer barely uses any C++).
And last but certainly not least, in the same breath that I mentioned gcc 2.96, I ALSO mentioned gcc 3.3, which most definately IS modern, and shipped with modern distros (Slackware 10 to name one). Of course, you selectively ignored that part, didn't you?
I don't intend to get dragged into a troll-fest, so here's my last response.
[...] would require the formatin of a 3rd party to check each product extensively [...] (since you can't trust the company [...]
No it WOULDN'T require the formation of anything. You CAN trust the company, because if they lie, they get sued into bankruptcy. Apple found this out the hard way.
Products would be very slow to market and end up costing as much as the skimpy $60 warranty
Plain and simple strawman. I'm not the one who suggested the formation of an expensive 3rd party, which would have all these problems. You did. All the spouting of bullshit is being done by YOU.
You can have the last word here if it makes you feel better.
Installing Linux is easy (unless you insist on dual-booting), it's the rest that is hard.
Many distros are halfbaked and unpredictable, but there are a few good ones out there.
Asking for help won't work. The faceless people on the internet aren't there to be your servants, just because you don't feel like reading through the docs. This can get very ugly, because of the inability to punch someone in the face over the internet.
Hmm, well I've been running it for a little while, and it seems like a fairly primitive P2P program, but it works.
However, the main idea was anonymity, and that doesn't seem to be used by any of the 3 peers right now (downloads are stamped with the proper source addresses), so I can hardly test anything, without setting up a whole lab myself.
Slashdot Mirror
You're more correct than you know.
Only it's usually not federal lawyers, it's now usually patent attorneys...
Netscape/AOL
Sorry, but I can't get up the slightest bit of excitement for a "solar" boat... First of all because they've been wind-powered for quite a lot longer than they've been diesel-powered. Secondly, because the ocean doesn't have any minimum speed-limit, so ANY ammount of energy will eventually get them where they are going (like a solar-powered blimp). And last but not least, because boats need a tremendous ammount of maintenance (unlike cars), which is where the bulk of the operating expense is... not the fuel (unlike cars).
The solar powered airplane sounds like a great idea, until you read that it has to FALL all night long to maintain its airspeed... That strikes me as being quite impractical for anything but an exhibition. So... interesting, but not showing how practical solar-powered planes can be.
Yeah... terrorists. Not political opponents... Not outspoken political activists... Not people falsely accused based on ridiculously bad and unchecked information...
Soylent Exxon?
The energy "put in" is comming mostly from SUNLIGHT, not from what we put into it.
And the sun is outputting so much power to the surface of the earth, that it absolutely dwarfs worldwide energy consumption by an unbelivable margin. If we use the more effecient plants for creating biodiesel, it would supply our ever-increasing demands for energy for millenia to come, before we'd have to look elsewhere, or put much work into increasing effecincy.
You'll always be able to find basic devices (like wireless APs) from thousands of companies. You may have to stay away from the major brands, but you can still probably buy your equipment from the same nameless Chinese company D-Link, Linksys, etc. buy their parts from!
Besides that, there's no reason you have to buy wired/wireless routers from anybody. A litte software on a low-cost embedded board, and you're set. You can probably get off as cheap as the junk you get from Linksys, and have a far, far better and more functional device, too.
Gee, so the ONLY THING we can blame them for is unleashing their attack lawyers on Kamp, when they were clearly in the wrong... That's more or less the ONLY THING people hate about the RIAA/MPAA, as well.
Now that D-Link has RESOLVED the problem, I can't see any problem with buying from them in the future. However, until now, it was a very good reason to spend your money elsewhere. That (little bit of) pressure may have been partly responsible for convincing them to settle things with Kamp.
CP/M works. DOS works. etc.
The definition of what "works" changes when something newer and better comes along. Certainly something with vastly improved stability, security, and flexibility would move Linux from the "works" column to the "used to work" column.
You need look no further than OpenVMS. The preeminent example, and damn good proof of the concept, in the real world.
Not true at all. You can list some incredibly slow-moving monolithic kernels too, I'm sure.
HURD is a good example of bloat and bureaucracy in software design, and not a fair example of anything else.
No, you completely misread my first post, and completely ignored my second post, where I told you that you had completely misunderstood.
But you can keep trolling if it somehow makes you feel better.
So your solution is... everyone should write code without any bugs, then microkernels won't provide any advantage?
The idea has been tried over and over again, and nobody has been able to write perfect code for anything of more than trivial complexity.
Look at something like OpenSSH, which was written by the most security-paranoid people out there (the OpenBSD team), but still ended up with a remote-root exploit. The solution is to write good code, AND to have it executing with the least ammount of privlidge possible. The two aren't mutually exclusive (OpenSSH has priv-sep now, and it hasn't instantly turned into a mess).
You mean we need an example like QNX or OpenVMS?
Those 5 patches sound fairly scary, actually.
That's the library for rtp/rtsp stream handling.
No need to boot-up the systems to open the CD tray; That's what a paperclips are for... At power-on, the tray will close itself, and you're set. Not to mention that slot-loading CD/DVD drives are just as cheap, and don't have that problem.
True, floppy drives are about 50% cheaper, but if the kind of price difference is an issue, you'd just stick with PXE (or, yes, possibly USB bootable drives).
What things? Saying "oh yes they are!" isn't very convincing. I keep asking, and still get no good answers.
No, but in this case, because of numerous limitations of floppies, it is.
I was very clearly talking about floppy images. If you already have a floppy, it changes things slightly. Even in that case, you're only talking about perhaps one minute more time to make a CD.
Complete bullshit. I was administering over 100 Windows machines just a few years ago, so I know full well how it works. There I would just dump the Windows files on a network server, and add-in any additional drivers needed for ANY of the machines. It's quite simple really, if you have any idea what you're doing.
And if you want to do it with physical media, you certainly don't need a CD for each one. Spend a couple minutes, add ALL the drivers that will be needed by ANY of the machines, and just burn one CD you can use for all of them. Quite trivial, and it's not more work, it's infinitely less.
I think the mod who gave me a -1 Troll, must have been aiming for your post, and missed...
On the odd chance you can reproduce the problem with CVS, the bugreporting procedure is well documented: http://www.mplayerhq.hu/DOCS/HTML/en/bugreports.h
If it's just another broken distro package... no, nobody wants to hear about it. That's the norm, not the exception.
The distros really don't give a damn. They completely ignore the packaging guidelines, make incredibly buggy MPlayer packages, and ignore all complaints. The nature of GPL'd software is that you can't force them to do anything, and they certainly aren't jumping at the chance to get their packages fixed.
What to do? Post a story on
Many people say similar things...
I've seen many people that, when told they have a hardware problem, respond, indignantly, that no other software has problems, only MPlayer. Then a few weeks later, you'll see a message from the same person, saying their CPU fan was going out, and appologizing...
MPlayer's aggressive code makes for the perfect test of any compilier... Every other application on the planet can compile perfectly, and yet you'll find bugs with MPlayer. -O3, -march, lots of ASM, 3dNow, SSE, MMX, etc.
Home users aren't too likely to use a RAID controller, and servers are unlikely to be installed from the standard disc. Even small companies slipstream their Windows CD, and add any extra patches and drivers they want before installing it on a single machine. It's quite easy.
It takes less time to burn and boot from a CD than it does to write and boot from a floppy. Floppies are so damn slow, not to mention it'll be 100% perfect on the CD every time, and a previously used floppy will have CRC errors half the time...
Besides, I can't remember the last time I got any products with a floppy. Companies have simply switched to CDs for everything.
Moving a drive may take some time... or not. Hard drive caddies make things quite fast. My firewall/router is also trivial to move, as it's just a CF disk in a front drive bay.
You haven't given any reasons why.
For what? If you've got some boot floppies you still use, grab a copy of isolinux (syslinux) and you can put all the images on a single CD, which will boot on any system made in the past 10 years.
I still keep a couple old systems (10+ years, non-bootable CD-ROMs) around, but I find it's much easier and faster to pull out the hard drives, and plug them into a modern system for OS (re)installation. Everything else just goes over the network.
from the I-forgotting-to-put-a-department dept.
I can't see bouncers having much of a life, at least on the public internet. There aren't many people that want to donate large ammounts of bandwidth to P2P users. But, I suppose it's necessary for publishers who cannot spoof their IP. Though I really find it hard to believe that only 20% of hosts can spoof their source addresses. I've seen too many DDoS attacks, far too recently, to believe that's really the case.
That's a very unfortunate restriction. I believe, for an anonymous P2P network to be successful, you really need to just have a configuration option. Maybe have it try spoofing source addresses in the same
The message collector idea is... interesting, but I can't imagine it's very practical. Surely anyone that needs like kind of security has a better (more deniable, for both sender and reciever) system in place.
I do? I mentioned it in two, short, sentences. One was in reference to the other, as well.
mentioning != harping
No, on all 5 counts. See the standard form response: http://www.mplayerhq.hu/DOCS/HTML/en/gcc-296.html
That is generally the case. Media players, MPlayer in particular, are the first symptom of something being horribly wrong with your system, since they are so timing dependant, make extensive use of extended instructions (MMX, 3DNow, SSE, etc), lots of assember, etc. When system code is corrupt, or when your hardware is changing bits due to heat or other bugs, there's nothing programs like MPlayer can do about it.
Wait a minute. First of all, you JUST SAID that gcc 2.96 *is* current, or don't you remember?
"and 2.96 is STILL used in many production environments because of its massive improvements in the implementation of C++"
Besides that, I can tell you that I did see a strange bugreport on mplayer-users around a month ago, that was tracked-down to a gcc 2.96 bug. And I should mention that MPlayer works quite well on both 2.95.3 and 3.x, so you can't claim it's some strict rule somewhere, or C++ problem (MPlayer barely uses any C++).
And last but certainly not least, in the same breath that I mentioned gcc 2.96, I ALSO mentioned gcc 3.3, which most definately IS modern, and shipped with modern distros (Slackware 10 to name one). Of course, you selectively ignored that part, didn't you?
No it WOULDN'T require the formation of anything. You CAN trust the company, because if they lie, they get sued into bankruptcy. Apple found this out the hard way.
Plain and simple strawman. I'm not the one who suggested the formation of an expensive 3rd party, which would have all these problems. You did. All the spouting of bullshit is being done by YOU.
You can have the last word here if it makes you feel better.
Installing Linux is easy (unless you insist on dual-booting), it's the rest that is hard.
Many distros are halfbaked and unpredictable, but there are a few good ones out there.
Asking for help won't work. The faceless people on the internet aren't there to be your servants, just because you don't feel like reading through the docs. This can get very ugly, because of the inability to punch someone in the face over the internet.
Beware of Leopard.
Hmm, well I've been running it for a little while, and it seems like a fairly primitive P2P program, but it works.
However, the main idea was anonymity, and that doesn't seem to be used by any of the 3 peers right now (downloads are stamped with the proper source addresses), so I can hardly test anything, without setting up a whole lab myself.
Compression means an extra step, which means long delays; increased latency, not to mention more expense on the card and screens.
I sincerely doubt they're using compression of any kind.
"gcj33: libgcj.spec: No such file or directory"
In only 3 days, I managed to built the jdk:
$ java -version
java version "1.4.2-p8"
You should probably see me in your list of Peers now.