It's not widely known, but PHT (a Japanese company and the developers of TurboLinux) were originally in this business (mainly for Macs). Let me dig around a moment...
Ah, here we are...
- INFO-MAC Games 3 Internet Game collection, with more than 300 games! - PowerMac2: All software is PowerMac native! Contains more than 300 applications!
The first one retailed for 2500 yen (about $US22) and the second for 2800 yen (about $US25). They're both complete crap, of course.
Um... your paraphrasing of George Orwell cannot be construed as a favorable comment, considering the context in which the original was delivered. Orwell used it to illustrate senseless prejudice; if that's what you're aiming for, then fine. If it's not, I suggest you find someone whose writings you actually understand before quoting them.
Please note that the announcement was for a feature freeze, not a code freeze. A code freeze means that the stable release is imminent. There's still a lot to before we reach that point, I would say:(
No, there's no way XFS will make it into anything before 2.5 (the development branch for the 2.6 stable kernel), and maybe not even then. It's a pretty big chunk of code, and not originally designed for Linux, so it will most likely take quite a while to be ported. Linus' filesystem comment probably doesn't indicate anything specific on the horizon for 2.4, I would think.
Linus has certain technical "issues" with the whole concept of devfs (although it is indeed very stable; Richard Gooch has been very tenacious in releasing devfs patches for new kernels within a day or two).
However, if I recall correctly (you tend to skim any threads about devfs in linux-kernel after the 1000th post asking about it:), Linus has relented a little lately, so it might be a candidate for 2.5, I guess.
Well, if you define "regular event" as "once in two years or so", then yes, it is;)
A feature freeze for the development branch of the kernel takes place when Linus decides that he doesn't want to accept anymore major changes - in other words, the development kernel (in this case, 2.3), is "feature complete", and all that remains before the release of the next stable kernel is a whole pile of bug-squashing.
In reality, it means that Linus won't accept anything unless you're really, really persuasive (and he has accepted some major changes at a late stage before). However, this time he's taking two weeks vacation to "avoid temptation".
Well, we got through 9999 pretty much all in one piece. I notice that most news services were saying things like "what an anticlimax", and how there was "nothing to worry about." Strange how most of those same news services run the occasional Y2K article saying how we're all doomed.
There was a small article in the newspaper this morning saying how there was only one problem reported in Japan with 9999 - the fire service in Okinawa lost the use of its fire reporting system (the system that lets them notify firefighters of the location of a fire) for several hours. Apparently, the system was installed a long time ago. If there's going to be any problems at 12:00:01, January 1st, it's going to come from systems like these - installed years ago and forgotten about - rather than things like bank databases or communications systems. On the other hand, embedded systems are supposed to be the big bugaboo, but any embedded systems programmer worth his/her salary is supposed to ensure that no matter what happens, the system will reset itself to a known state rather than opening all water valves or whatever.
Still, I'm not going to be taking any plane flights...
No, no, no, no. Linus didn't reject the USB patches because they came from a non-Intel platform. He stated quite clearly that he didn't like the way that those patches tried to do everything all at once for USB, and wanted to take a more gradual and simpler approach. That's why the USB support in the current kernels is the one that Alan Cox and others are working on.
Since when is Linus "not too fond of non-Intel architectures"?
He did say "by programmers for programmers". MacOS was presumably developed by programmers for users. If you're going to quote somebody, it might help to make the attempt to understand what they're saying first.
What they need to do is dump the firewire port. Sony doesn't call it Firewire...
Get out of that dead-end technology and get on the USB2 bandwagon. I wasn't aware that there was a USB2 bandwagon to get on. All I see is some very tenuous specs.
Everybody's doing it,... Who, exactly, is "everybody"?
...so why get left behind in the dust with proprietary gear, even if it is better. What do you mean by proprietary? Firewire is an IEEE standard. And you've just admitted that Firewire's better.
I mean, didn't Sony learn anything from betamax? Sony at that time was a very different company to what it is today. Don't underestimate them.
The Dreamcast has been out in Japan for quite a while now, and while it's sold a fair number of units, it doesn't look like it'll be able to withstand thw PSII onslaught, even with a long head start. Although, I must admit, Soulscaliber (sorry, I have no idea of what it's really called in English) looks pretty smooth on the Dreamcast.
Ah well, even Sega seems to be resigned to its fate, if you believe the comments their management has been making (they would be satisfied with being a "niche market in the shadow of Sony", apparently).
I think what Rob's describing is something like this:
1 - You come to Slashdot as usual. 2 - You're notified that you have "MetaModerator" status. 3 - You then wander around stories as usual. 4 - You see a comment that's been moderated down unfairly (or perhaps given too high a score - some people lately seem to be using two accounts, one for making comments and another with good karma for moderating up their own comments). 5 - You hit a button that indicates whether the comment was fairly or unfairly moderated. 6 - The original moderator's karma goes up or down, and yours goes up a little.
However, Rob's comment could also be taken to indicate that you're given a link to click on which then shows you a list of ten comments that have been moderated (say, within the last day), which you are then asked to score. This seems awfully inflexible and inefficient to me, but then, I'm not the one coding it in Perl...
(Feel free to jump in here, Rob, and tell me if I'm wrong.)
You would be following the letter of the law rather than the spirit. If the US Government did happen to take an interest in you, they'll drag you into court anyway - and they just might win (try explaining your reasoning to a group of twelve random people and see how many of them get it.)
Ah, you show your true colours now. For a start, the concept of nationality with regard to websites is not particularly meaningful - it doesn't matter where the server is; what matters is what's on it. Not everyone reading this is from the US; why assume they are? For another thing, the topic of this article is concerned with Linux and the running of a user group, both items of interest to people frequenting/., if past topics are anything to go by. And thirdly, who nominated you for the post of chief censor? If you don't want to read something, pass on by; new articles pop up all the time, and I'm sure there'll be something among them that interests you.
Just don't bitch when there's something here that you don't want to read; we're not all the same as you. Repeat this to yourself a few times.
Oh, by the way, it looks like the guy who sent this in is the same person who wrote the open letter, so there's at least one Turkish Linux user reading Slashdot.
Well, of the stories currently on/.'s main page, about a third of them count as "local issues". The arrest of a hacker in the U.S.? Australian censorship? Piracy in Europe? All "local issues" if you don't happen to be living there. Did you bitch about those? No. Did your comment add anything to the discussion here? No.
Just remember, what's "local" depends on where you live. Not everyone here's an American.
Seriously, why is it that anyone mentions that they don't like guns on Slashdot, some NRA fanatic jumps all over them? I mean, are you taking turns on monitoring or what?
I think Intel have really painted themselves into a corner with Merced. Everyone knows that it hasn't been achieving the kind of performance that it was expected to, and it's being overtaken by other chips more rapidly than originally forecast. It's pretty much a dead end. I can wait for the next generation, thank you.
OK, what he's talking about here is a class of security problems called buffer overflows. Basically, the problem with sprintf is that its output goes to a string - which has a defined length. This string could be a buffer array for data within the program. Thus, if the original data used for the input to the sprintf can be altered by the user (for example, through environment variables or program options), it allows a random user to stuff data in areas of memory past the end of the buffer array. If this buffer array is in a predictable position (as it might well be on the stack), a skilled cracker (or a script kiddy with a ready-made program) would be able to shove hand-tailored data onto the stack, which if executed could be made to give root priveleges to the cracker. The fix is to use snprintf instead (which requires the length of the buffer array as a parameter).
Check out edge.kernelnotes.org for Myrdraal's kernel patch summaries (but it usually takes a couple of days for him to get the newest ones up). Otherwise, look through the source...
Slashdot Mirror
Um... it's afternoon where I am. Perhaps you should think about the fact that not everyone is on US time before posting to an article about i18n.
Um... Cyrix K6 chips? Sorta like those AMD MII chips, huh?
It's not widely known, but PHT (a Japanese company and the developers of TurboLinux) were originally in this business (mainly for Macs). Let me dig around a moment...
Ah, here we are...
- INFO-MAC Games 3 Internet Game collection, with more than 300 games!
- PowerMac2: All software is PowerMac native! Contains more than 300 applications!
The first one retailed for 2500 yen (about $US22) and the second for 2800 yen (about $US25). They're both complete crap, of course.
Um... your paraphrasing of George Orwell cannot be construed as a favorable comment, considering the context in which the original was delivered. Orwell used it to illustrate senseless prejudice; if that's what you're aiming for, then fine. If it's not, I suggest you find someone whose writings you actually understand before quoting them.
What benefits would this bring Micro$oft? Not exqctly their core business, is it...
Please note that the announcement was for a feature freeze, not a code freeze. A code freeze means that the stable release is imminent. There's still a lot to before we reach that point, I would say
No, there's no way XFS will make it into anything before 2.5 (the development branch for the 2.6 stable kernel), and maybe not even then. It's a pretty big chunk of code, and not originally designed for Linux, so it will most likely take quite a while to be ported. Linus' filesystem comment probably doesn't indicate anything specific on the horizon for 2.4, I would think.
Linus has certain technical "issues" with the whole concept of devfs (although it is indeed very stable; Richard Gooch has been very tenacious in releasing devfs patches for new kernels within a day or two).
However, if I recall correctly (you tend to skim any threads about devfs in linux-kernel after the 1000th post asking about it:), Linus has relented a little lately, so it might be a candidate for 2.5, I guess.
Well, if you define "regular event" as "once in two years or so", then yes, it is ;)
A feature freeze for the development branch of the kernel takes place when Linus decides that he doesn't want to accept anymore major changes - in other words, the development kernel (in this case, 2.3), is "feature complete", and all that remains before the release of the next stable kernel is a whole pile of bug-squashing.
In reality, it means that Linus won't accept anything unless you're really, really persuasive (and he has accepted some major changes at a late stage before). However, this time he's taking two weeks vacation to "avoid temptation".
Well, we got through 9999 pretty much all in one piece. I notice that most news services were saying things like "what an anticlimax", and how there was "nothing to worry about." Strange how most of those same news services run the occasional Y2K article saying how we're all doomed.
There was a small article in the newspaper this morning saying how there was only one problem reported in Japan with 9999 - the fire service in Okinawa lost the use of its fire reporting system (the system that lets them notify firefighters of the location of a fire) for several hours. Apparently, the system was installed a long time ago.
If there's going to be any problems at 12:00:01, January 1st, it's going to come from systems like these - installed years ago and forgotten about - rather than things like bank databases or communications systems. On the other hand, embedded systems are supposed to be the big bugaboo, but any embedded systems programmer worth his/her salary is supposed to ensure that no matter what happens, the system will reset itself to a known state rather than opening all water valves or whatever.
Still, I'm not going to be taking any plane flights...
And how is it different to the old TS?
No, no, no, no. Linus didn't reject the USB patches because they came from a non-Intel platform. He stated quite clearly that he didn't like the way that those patches tried to do everything all at once for USB, and wanted to take a more gradual and simpler approach. That's why the USB support in the current kernels is the one that Alan Cox and others are working on.
Since when is Linus "not too fond of non-Intel architectures"?
He did say "by programmers for programmers". MacOS was presumably developed by programmers for users. If you're going to quote somebody, it might help to make the attempt to understand what they're saying first.
What, you've been smoking too much crack lately?
...so why get left behind in the dust with proprietary gear, even if it is better.
What they need to do is dump the firewire port.
Sony doesn't call it Firewire...
Get out of that dead-end technology and get on the USB2 bandwagon.
I wasn't aware that there was a USB2 bandwagon to get on. All I see is some very tenuous specs.
Everybody's doing it,...
Who, exactly, is "everybody"?
What do you mean by proprietary? Firewire is an IEEE standard. And you've just admitted that Firewire's better.
I mean, didn't Sony learn anything from betamax?
Sony at that time was a very different company to what it is today. Don't underestimate them.
The Dreamcast has been out in Japan for quite a while now, and while it's sold a fair number of units, it doesn't look like it'll be able to withstand thw PSII onslaught, even with a long head start. Although, I must admit, Soulscaliber (sorry, I have no idea of what it's really called in English) looks pretty smooth on the Dreamcast.
Ah well, even Sega seems to be resigned to its fate, if you believe the comments their management has been making (they would be satisfied with being a "niche market in the shadow of Sony", apparently).
I think what Rob's describing is something like this:
1 - You come to Slashdot as usual.
2 - You're notified that you have "MetaModerator" status.
3 - You then wander around stories as usual.
4 - You see a comment that's been moderated down unfairly (or perhaps given too high a score - some people lately seem to be using two accounts, one for making comments and another with good karma for moderating up their own comments).
5 - You hit a button that indicates whether the comment was fairly or unfairly moderated.
6 - The original moderator's karma goes up or down, and yours goes up a little.
However, Rob's comment could also be taken to indicate that you're given a link to click on which then shows you a list of ten comments that have been moderated (say, within the last day), which you are then asked to score. This seems awfully inflexible and inefficient to me, but then, I'm not the one coding it in Perl...
(Feel free to jump in here, Rob, and tell me if I'm wrong.)
You would be following the letter of the law rather than the spirit. If the US Government did happen to take an interest in you, they'll drag you into court anyway - and they just might win (try explaining your reasoning to a group of twelve random people and see how many of them get it.)
Interesting idea, though...
Whether he's a racist pig or not is of no particular interest to me, but your comment has very clearly shown what kind of person YOU are.
Take a few deep breaths and then dunk your head in a bucket or something. Please.
Ah, you show your true colours now. For a start, the concept of nationality with regard to websites is not particularly meaningful - it doesn't matter where the server is; what matters is what's on it. Not everyone reading this is from the US; why assume they are? /., if past topics are anything to go by.
For another thing, the topic of this article is concerned with Linux and the running of a user group, both items of interest to people frequenting
And thirdly, who nominated you for the post of chief censor? If you don't want to read something, pass on by; new articles pop up all the time, and I'm sure there'll be something among them that interests you.
Just don't bitch when there's something here that you don't want to read; we're not all the same as you. Repeat this to yourself a few times.
Oh, by the way, it looks like the guy who sent this in is the same person who wrote the open letter, so there's at least one Turkish Linux user reading Slashdot.
Well, of the stories currently on
Just remember, what's "local" depends on where you live. Not everyone here's an American.
AGGHHH, IT'S THE GUN NUTS!!! RUN!!!!!
Seriously, why is it that anyone mentions that they don't like guns on Slashdot, some NRA fanatic jumps all over them? I mean, are you taking turns on monitoring or what?
I think Intel have really painted themselves into a corner with Merced. Everyone knows that it hasn't been achieving the kind of performance that it was expected to, and it's being overtaken by other chips more rapidly than originally forecast. It's pretty much a dead end. I can wait for the next generation, thank you.
OK, what he's talking about here is a class of security problems called buffer overflows. Basically, the problem with sprintf is that its output goes to a string - which has a defined length. This string could be a buffer array for data within the program. Thus, if the original data used for the input to the sprintf can be altered by the user (for example, through environment variables or program options), it allows a random user to stuff data in areas of memory past the end of the buffer array. If this buffer array is in a predictable position (as it might well be on the stack), a skilled cracker (or a script kiddy with a ready-made program) would be able to shove hand-tailored data onto the stack, which if executed could be made to give root priveleges to the cracker. The fix is to use snprintf instead (which requires the length of the buffer array as a parameter).
Check out edge.kernelnotes.org for Myrdraal's kernel patch summaries (but it usually takes a couple of days for him to get the newest ones up). Otherwise, look through the source...
Yeah, it's called Perl