That's part of the problem with the current crop of (Windows/Mac) virus detection programs - they only check for certain patterns that match known viruses, leaving them vulnerable to the latest versions.
What you need is a program that would, for example, check on certain system calls (for example, those involved in module loading) and determine whether the call should be allowed to complete or not. Unfortunately, this isn't a drop-in solution - it needs proper integration with the kernel.
o "There will be a flood of Linux viruses after the economy goes south": Why? Because all those programmers who would otherwise have been able to make millions via IPOs will to turn to virus writing instead? What kind of argument is that? Most virus writers don't have the business acumen or social skills of a dung beetle.
o "We need programs that will prevent viruses from mdifying the kernel": And how, exactly, are they supposed to do that? The most common way of cracking a system through kernel changes is use of modules. How is this hypothetical virus detection program supposed to distinguish between genuine modules and viral modules? You'd have to have a list of approved modules with MD5 checksums for each of them, and that'd still leave you open to subversion of either the applicable areas of the kernel or the virus detection program itself.
That would be a VERY BAD IDEA. It would give Mattel further grounds for suing for breach of copyright. These guys are doing it the right way - distributing the tools for converting the database to plain text and then leaving it up to the user to decide whether they have a legal right to see the content.
Personally, I think they want the logs so that they can add the list of sites involved to those blocked by their software. Then they can say that they're doing it to prevent kids from downloading this "dangerous" piece of "contraband".
From the looks of Linus's comments, it's only a move from the (currently very slushy) pretty-much-anything-goes-if-it-compiles-feature freeze to a (slightly more frozen) already-announced-but-not-yet-fully-included-featu re freeze+bugfix stage.
1) You don't want to use a ramdisk on a machine with only 32MB if you can avoid it.
2) With only 16MB of flash memory to play with, you're not going to be able to fit much in. Even a very minimal system needs more than that (unless you're using one of the "micro" distributions).
The page says that these terminals have a 16MB Sandisk on board. If so, forget the internal hard disk (although you're going to need it to do the Sandisk install) that's enough to get it booting.
On top of that, if the USB-to-Ethernet support in the latest development kernels is at a reasonable level of stability (I haven't checked them lately, so no guarantees), you should be able to boot the kernel and a minimal system from the Sandisk, and mount the rest of your system over the USB connector. OK, it's not gonna be superfast, but it'd do as a second screen for a server.
You could just have substituted another joystick...back then, in the simple days...all the joysticks had the same plug...
You're talking about the 9-pin plug used on VIC-20s, C64s, Atari 400/800s, etc.etc.etc., right?
Unfortunately, I'm talking 1980 here - in my part of the world, there was no such thing as joysticks from independent manufacturers. It was either go with the Commodore model, or buy an Atari to get the joystick that came with that.
I got my first gaming blisters from Gorf (the Commodore VIC-20 cartridge version) because of the stupid positioning of the fire button on the Commodore joysticks. I never even thought of suing Commodore or anyone else because of that.
Quite frankly, if you're playing a game enough to get blisters, you have way too much free time on your hands. Suing somebody for that is just frivolous.
This mentality has been around for a lot longer than most people think. The micros that were around before the PC came out and crushed everyone often had buggy firmware. Minicomputers before that had more than their fair share of quirks. I bet if you go back to the mainframes around in the 50s, you'd find that inside they were a mess of patchwork.
I work for a Japanese company, and believe me, most of the time they're not thinking any more than six months ahead. Your so-called "conspiracy theory" is nothing more than a rehashing of the Japan Inc. crap that was so popular in the 80s.
Hate to tell you, but the SMP in FreeBSD is on about the same level as that in the 2.0 series of Linux kernels; a big fat kernel lock that slows you down any time you move from user-space to kernel-space.
Look, I posted the link - big deal. Did it really require a dozen trolls to come out of the woodwork and jump all over me for it? No. Did it require anal-retentives like yourself to start counting links? No.
What's really sad is that I have no idea what you were trying to say in that post. It doesn't parse - why don't you try reading your own posts before hitting that "Submit" button, huh?
Slashdot Mirror
That's part of the problem with the current crop of (Windows/Mac) virus detection programs - they only check for certain patterns that match known viruses, leaving them vulnerable to the latest versions.
What you need is a program that would, for example, check on certain system calls (for example, those involved in module loading) and determine whether the call should be allowed to complete or not. Unfortunately, this isn't a drop-in solution - it needs proper integration with the kernel.
A couple of points (I'm paraphrasing here):
o "There will be a flood of Linux viruses after the economy goes south": Why? Because all those programmers who would otherwise have been able to make millions via IPOs will to turn to virus writing instead? What kind of argument is that? Most virus writers don't have the business acumen or social skills of a dung beetle.
o "We need programs that will prevent viruses from mdifying the kernel": And how, exactly, are they supposed to do that? The most common way of cracking a system through kernel changes is use of modules. How is this hypothetical virus detection program supposed to distinguish between genuine modules and viral modules? You'd have to have a list of approved modules with MD5 checksums for each of them, and that'd still leave you open to subversion of either the applicable areas of the kernel or the virus detection program itself.
That would be a VERY BAD IDEA. It would give Mattel further grounds for suing for breach of copyright. These guys are doing it the right way - distributing the tools for converting the database to plain text and then leaving it up to the user to decide whether they have a legal right to see the content.
You're talking about copyright law. Please show me exactly how these people have breached Mattel's copyright.
Personally, I think they want the logs so that they can add the list of sites involved to those blocked by their software. Then they can say that they're doing it to prevent kids from downloading this "dangerous" piece of "contraband".
What can be changed once can be changed again - if the main CVS servers were moved to the US, it would leave them vulnerable to future legislation.
From the looks of Linus's comments, it's only a move from the (currently very slushy) pretty-much-anything-goes-if-it-compiles-feature freeze to a (slightly more frozen) already-announced-but-not-yet-fully-included-feat
1) You don't want to use a ramdisk on a machine with only 32MB if you can avoid it.
2) With only 16MB of flash memory to play with, you're not going to be able to fit much in. Even a very minimal system needs more than that (unless you're using one of the "micro" distributions).
3) It's much cooler to do it over the network
The page says that these terminals have a 16MB Sandisk on board. If so, forget the internal hard disk (although you're going to need it to do the Sandisk install) that's enough to get it booting.
On top of that, if the USB-to-Ethernet support in the latest development kernels is at a reasonable level of stability (I haven't checked them lately, so no guarantees), you should be able to boot the kernel and a minimal system from the Sandisk, and mount the rest of your system over the USB connector. OK, it's not gonna be superfast, but it'd do as a second screen for a server.
No pain, no gain.
And what exactly did you gain from jerking off in front of a TV screen, genius?
Well done. Do you feel 1337?
(BTW, if you get blisters that quickly, you're using too much force - try and relax a little, huh?)
You could just have substituted another joystick...back then, in the simple days...all the joysticks had the same plug...
You're talking about the 9-pin plug used on VIC-20s, C64s, Atari 400/800s, etc.etc.etc., right?
Unfortunately, I'm talking 1980 here - in my part of the world, there was no such thing as joysticks from independent manufacturers. It was either go with the Commodore model, or buy an Atari to get the joystick that came with that.
I got my first gaming blisters from Gorf (the Commodore VIC-20 cartridge version) because of the stupid positioning of the fire button on the Commodore joysticks. I never even thought of suing Commodore or anyone else because of that.
Quite frankly, if you're playing a game enough to get blisters, you have way too much free time on your hands. Suing somebody for that is just frivolous.
This mentality has been around for a lot longer than most people think. The micros that were around before the PC came out and crushed everyone often had buggy firmware. Minicomputers before that had more than their fair share of quirks. I bet if you go back to the mainframes around in the 50s, you'd find that inside they were a mess of patchwork.
Jesus, you are such a dork.
I work for a Japanese company, and believe me, most of the time they're not thinking any more than six months ahead. Your so-called "conspiracy theory" is nothing more than a rehashing of the Japan Inc. crap that was so popular in the 80s.
Get your head out of your ass and wake up.
Hate to tell you, but the SMP in FreeBSD is on about the same level as that in the 2.0 series of Linux kernels; a big fat kernel lock that slows you down any time you move from user-space to kernel-space.
You couldn't even say "myself" right, so I don't know what you're crowing about...
Strange, last time I looked this wasn't "News for Anonymous Cowards"...
"Spew more venom"? Yeah, right.
Look, I posted the link - big deal. Did it really require a dozen trolls to come out of the woodwork and jump all over me for it? No. Did it require anal-retentives like yourself to start counting links? No.
Just let it pass on by, and GET OVER IT ALREADY.
Nice to see that there's still some reasonably mature people left on
Sue me. I'm not the one that moderated it with "Informative", so what are you bitching at me for?
Read my post next time. I said "two other comments that...contain the correct link", not two other posts that refer to the broken link.
What's really sad is that I have no idea what you were trying to say in that post. It doesn't parse - why don't you try reading your own posts before hitting that "Submit" button, huh?
Christ, who really gives a shit about karma? It doesn't mean anything - get over it already, will ya?
Woohoo, you posted as an AC, big deal - Christ, get a life.