What I use in my car is an old Pentium-166 mobo + 16 megs ($0) that I had lying around. Add my home-brewed PSU that makes +12, -12 and +5 from an unstable car battery ($10) and my collection of bootable MP3 cdroms ($2 each) and I'm done.
The bootblock just loads the DOS SB drivers and MPXPLAY, a great, visual DOS mp3 player.
The only expensive thing was the 6" LCD screen that accepts PAL signals (driven by a a VGA cable and a DOS util called "vgatv" that), but fortunately for me, I got it for free ($0).
Actually that LCD screen made us think of the whole Car MP3 project in the first place.
I must say, together with the 200W speakers, it just plain rocks.
Re:Due to long release cycles (Score:0)
by Anonymous Coward on Wed August 30, 14:37 CET (#83)
Where is the Debian fix for ProFTP and when was it fixed?
Because
a) editors at Slashdot are extremely biased and by no means objective whatsoever and
b) this time they were sort of right, because the article does not talk too much about real security issues but instead blabbers about Debian's Exim using RBL not completely right or something.
Granted, if Debian does all the things Kurt proposes, Debian will get a lot better, but not neccessarily a (more) secure distro.
The author of the article claims a lot of packages (he mentions apache and proftpd) are out of date, while he didn't realize that Debian 2.2 was frozen months ago. This means that at release, packages are dead-stable (they wont crash) but might have a few holes in them by now. And, as another poster pointed out, backfixes do exist.
Everytime I read op Bugtraq that "OpenBSD fixed this vulnerability five months ago through a standard audit", I wonder, why the heck don't they make this fix more public, so other OS's (freebsd, linux, whatever) can also profit from it.
I'm not so paranoid to think that OpenBSD wants to keep their fixes to themselves, in order to stay "the most secure OS out there".
So what is it then? Do other OS's developers just don't look at the OpenBSD pages to see what's fixed?
If it's a public tool (e.g. GNU), do the OpenBSD people submit a patch back?
If the OpenBSD keep up the good work, I think everyone can profit from it and then Bugtraq will read "Thanks to OpenBSD, all OS's fixed this vulnerability 5 months ago"
perl uses almost English like syntax with syntax as:
x unless y
or
x if y or die;
By the way, this is not a property of English, but all languages which use a similar scheme for building sentences. All Germanic languages come to mind, and the Latin languages too. It's always surprising how far one gets by translating a sentence word by word and winding up with a sentence-construction that isn't even way off in the other language.
Conclusion: perl by a Japanese guy would be different from the current perl, but perl by a Dutch guy would have come out the same, although with "of" instead of "if" and "behalve" instead of "unless":)
I've never used KDE or Gnome. As far as I know, they are windows managers and the developers "ported" a lot of applications, like napster and winamp, to those window managers.
What will KDE and Gnome common component architecture mean for me, the fvwm2-zealot, who plays mp3s with mpg123 and writes documents with xemacs?
but if you put a comment next to it saying what it does, it's not hard to understand.
Rule #1 in programming: Never use a comment to explain how your code works instead of what it does or why it does it. It's much better to write the code so that the _working_ is obvious, and it's a waste of time to explain badly written code.
Instead of "gnomifying" or "-ifying", why not see what this StarVision or Starview library is and maybe use that one as a baselibrary to make all those X-apps out there cross-platform.
I'd rather look at StarView or StarVision first, instead of having some gnome or kde zealots ruining SO.
As cetan pointed out, the GUI was removed so win32 users would get their new clients faster. This was because the GUI version was a complete fork in the code and was unmaintainable in the end. By the way, what exactly changed? Only the config, the mainscreen was text-based all the time.
You can get the moo-ing back, with a 3rd party application. 3rd party meaning that it's not part of the official distribution. It is code by BovineOne tho, yes, the same guy who helps coding the client.
Almost all source is open, go to http://www.distributed.net/source and write your own wrapper. All code you need to interface is in there.
Imagine how much more authoritive you could have sounded if you didn't make so many spelling mistakes, call Windows WindHoze and call an MSCE something with Minesweeper or Solitaire in it.
If you do have a valid point, say it, and don't bash unneccessarily.
"Software should not be owned." I still don't get that phrase. While I see how a project like apache and linux are sexy enough so that people will code it for free, only to gain "respect" in geek-communities. (Hey, I do it myself, too!), I fail to see how RMS et al. can extend this to larger, boring projects.
Isn't this usually true? People who code for a living usually don't like it that much as their hobby OSS project they work on until deep in the night, right after they get home. Both coding, but the free(beer)-software model can only hold if people are willing to do something because they just like it. (If only you could have a job that actually IS your hobby, which unfortunately is untrue for a lot of people).
In this way, yes, there will always be art, music and software like apache and linux, but you cannot compare boring softwareprojects here. And that's why you need copyrights, because people want/need to make money out of it!
I personally believe that copyright laws should exist, but for a shorter time period, such as 10-30 years rather than 95+. I don't think people or companies will be that *much* more motivated to innovate when they can get 10-30 years profit rather than 95+ years, for it to be worth it to deny people the right to benefit off of that public information during that extra period of time.
Ahum, but you're mistaking copyrights with patents here.
A small analogy why I think Napster is indeed a bad thing.
It would be stupid to ban, say, hammers, because you can kill people with it. This is the argument I keep on hearing in favor of Napster.
Point is that Napster is a program that deliberately stimulates people to violate copyrights. I will NOT go into the discussion whether those copyrights should be on music, that's not the issue here. The issue is that Napster KNOWS that 90+ % of the music traded on its system is illegal and pirated.
And "fencing", the act of selling goods that you _know_ are stolen, is illegal.
THAT is the analogy people should make when they talk about Napster, and not the "hammer" argument.
Just my 2 cents.
Ivo Janssen
P.S. As I said, whether pirated MP3s violate copyrights or are fair use is not the issue here.
Slashdot Mirror
The bootblock just loads the DOS SB drivers and MPXPLAY, a great, visual DOS mp3 player.
The only expensive thing was the 6" LCD screen that accepts PAL signals (driven by a a VGA cable and a DOS util called "vgatv" that), but fortunately for me, I got it for free ($0).
Actually that LCD screen made us think of the whole Car MP3 project in the first place.
I must say, together with the 200W speakers, it just plain rocks.
Actually, this month's episode, which came in the mail this morning, talks about the same windows of exposure.
I can hartly recommend this newsletter to everyone!
Ivo
Hey, my DNA already contains the DeCSS source code. I just encrypted it very good.
Just take molecule 0x5429 and the next 0x62940 ones and save them to a file and untar it. Tada.
Don't forget to decrypt it with my One Time Pad.
Sex without making a kid?
by Anonymous Coward on Wed August 30, 14:37 CET (#83)
Where is the Debian fix for ProFTP and when was it fixed?
here, and now shut up.
Because
a) editors at Slashdot are extremely biased and by no means objective whatsoever and
b) this time they were sort of right, because the article does not talk too much about real security issues but instead blabbers about Debian's Exim using RBL not completely right or something.
Granted, if Debian does all the things Kurt proposes, Debian will get a lot better, but not neccessarily a (more) secure distro.
Ivo
The author of the article claims a lot of packages (he mentions apache and proftpd) are out of date, while he didn't realize that Debian 2.2 was frozen months ago. This means that at release, packages are dead-stable (they wont crash) but might have a few holes in them by now. And, as another poster pointed out, backfixes do exist.
Ivo
Everytime I read op Bugtraq that "OpenBSD fixed this vulnerability five months ago through a standard audit", I wonder, why the heck don't they make this fix more public, so other OS's (freebsd, linux, whatever) can also profit from it.
I'm not so paranoid to think that OpenBSD wants to keep their fixes to themselves, in order to stay "the most secure OS out there".
So what is it then? Do other OS's developers just don't look at the OpenBSD pages to see what's fixed?
If it's a public tool (e.g. GNU), do the OpenBSD people submit a patch back?
If the OpenBSD keep up the good work, I think everyone can profit from it and then Bugtraq will read "Thanks to OpenBSD, all OS's fixed this vulnerability 5 months ago"
perl uses almost English like syntax with syntax as:
:)
x unless y
or
x if y or die;
By the way, this is not a property of English, but all languages which use a similar scheme for building sentences. All Germanic languages come to mind, and the Latin languages too. It's always surprising how far one gets by translating a sentence word by word and winding up with a sentence-construction that isn't even way off in the other language.
Conclusion: perl by a Japanese guy would be different from the current perl, but perl by a Dutch guy would have come out the same, although with "of" instead of "if" and "behalve" instead of "unless"
Ivo
Uhuh.
How many backdoors did you put in that RPM?
a) never upgrade a server to a point-oh release
b) there is no b, because you would be installed fbsd-4.1 right now!
Ivo
FWIW, for those printing and scanning and photoshopping stuff I use the tools which are best suited for that: Windows. On a pretty fast Celeron.
Now who was trolling more?
Ivo
I think setting the channel to +s should be the hint for a searchbot to keep out... Easy enough
Ivo
With the change of being accused of trolling:
I've never used KDE or Gnome. As far as I know, they are windows managers and the developers "ported" a lot of applications, like napster and winamp, to those window managers.
What will KDE and Gnome common component architecture mean for me, the fvwm2-zealot, who plays mp3s with mpg123 and writes documents with xemacs?
Ivo
The Dutch use "miljoen" for 10e6, "miljard" for 10e9, "biljoen" for 10e12 and "biljard" for 10e15.
So for me, the world has around 5 or 6 "miljard" people.
Ivo
Rule #1 in programming: Never use a comment to explain how your code works instead of what it does or why it does it. It's much better to write the code so that the _working_ is obvious, and it's a waste of time to explain badly written code.
Ivo
Instead of "gnomifying" or "-ifying", why not see what this StarVision or Starview library is and maybe use that one as a baselibrary to make all those X-apps out there cross-platform.
I'd rather look at StarView or StarVision first, instead of having some gnome or kde zealots ruining SO.
Ivo
As cetan pointed out, the GUI was removed so win32 users would get their new clients faster. This was because the GUI version was a complete fork in the code and was unmaintainable in the end. By the way, what exactly changed? Only the config, the mainscreen was text-based all the time.
You can get the moo-ing back, with a 3rd party application. 3rd party meaning that it's not part of the official distribution. It is code by BovineOne tho, yes, the same guy who helps coding the client.
Almost all source is open, go to http://www.distributed.net/source and write your own wrapper. All code you need to interface is in there.
If you think you can solve our security problems, I invite you to take a look at our operational code authentication document and help us out!
Ivo Janssen
ivo@distributed.net
distributed.net staffmember
Don't forget there's already a processor on the board!
Comparing a complete system with a bare x86 motherboard is not really what I'd call fair.
Ivo
So basically G# is a F##C#ING difficult key?
Imagine how much more authoritive you could have sounded if you didn't make so many spelling mistakes, call Windows WindHoze and call an MSCE something with Minesweeper or Solitaire in it.
If you do have a valid point, say it, and don't bash unneccessarily.
Ivo
sunsite
Isn't this usually true? People who code for a living usually don't like it that much as their hobby OSS project they work on until deep in the night, right after they get home. Both coding, but the free(beer)-software model can only hold if people are willing to do something because they just like it. (If only you could have a job that actually IS your hobby, which unfortunately is untrue for a lot of people).
In this way, yes, there will always be art, music and software like apache and linux, but you cannot compare boring softwareprojects here. And that's why you need copyrights, because people want/need to make money out of it!
Ivo Janssen
Ahum, but you're mistaking copyrights with patents here.
A small analogy why I think Napster is indeed a bad thing.
It would be stupid to ban, say, hammers, because you can kill people with it. This is the argument I keep on hearing in favor of Napster.
Point is that Napster is a program that deliberately stimulates people to violate copyrights. I will NOT go into the discussion whether those copyrights should be on music, that's not the issue here.
The issue is that Napster KNOWS that 90+ % of the music traded on its system is illegal and pirated.
And "fencing", the act of selling goods that you _know_ are stolen, is illegal.
THAT is the analogy people should make when they talk about Napster, and not the "hammer" argument.
Just my 2 cents.
Ivo Janssen
P.S. As I said, whether pirated MP3s violate copyrights or are fair use is not the issue here.