Your entire post makes no sense. If you want a stable kernel and have no interest in being a tester and bugfinder, run the kernel your distro comes with!
As linux and OSS mature more and more its going to become the distro's responsibility for making an intergrated, stable, and well tested set of software releases. This way the projects and developers can focus on what they want (adding features, rewrites, changing whatever they feel) while the distro focuses on what they/end-users want (dependancies, compatibility, intergration, testing, consistant builds, backported bug and security fixes)
This article is a perfect example. With distro's like redhat and suse shipping kernels that barely resemble the base one, Linus realizes that its becoming less-and-less his job to work out all the kinks. His job is to be constantly improving the kernel, and then the distro's can decide at what versions and pieces they want a la cart.
Could someone in the know please explain how Mono will not suffer the fate of samba or that attempt to get ASP working on nix (chilisoft? I forget)?
I don't know the detailed inner workings, but it seems like these projects are forever doomed to being a shadow of a "mostly" implimentation riddled with "gotchas" and always a few steps behind. I don't blame the developers in any way, its just we all know MS does not play nice with others.
1.) adding a radio (fm or xm) gives a user a reason to not buy more through itunes. I can't remember the last time I loaded new mp3s onto my iRiver, to me its portable NPR + harddrive.
2.) the size of the unit would be really big to accomidate the extra electronics and most importantly the much larger battery.
I'm sure Jobs knows, like we all do, that eventually the ipod will have to go there. But for now he can reap the design benefits of the smaller battery and the revenue stream of itunes for a year or two until miniturization runs its course.
From skimming through the review, I saw no mention of Eclipse.
Finally, Integrated Development Environments are covered. While Carl and Michael focus on NetBeans, SunONE Studio Community Edition and Eclipse are also covered.
This must seed at some increadibly slow speed or automatically hop off when it sees other seeds have arrived. They can't just give the bandwidth away for free unless they seriously minimize what actually gets used.
AMD trimmed Intel's share in PC-based servers in the third quarter, taking 8 percent of unit sales, up from 6.9 percent, according to IDC.
...
AMD also saw slight gains in unit share for desktop and notebook PCs. It now has 18.4 percent of the desktop PC market ...
Intel nevertheless held onto its overall dominance of the PC microprocessor market, retaining 81.2 percent of the overall share of units, off slightly from 81.7 percent.
I really wish the MPM could be worked out to operate in a suexec like fashion where each virtual host got its own process owned by a specific user for that virtual host.
This is particularly important to PHP and webhosts/mass-virtual-hosters. The current model is to use things like safe_mode and openbasedir and limiting certian functions like exec(). Thats a very hacky way of trying to solve the problem of multiple users applications running as the same user without being able to mess with each other. Just saying out loud makes you realize how much a fix is needed.
Its also why any host worth its fees has to run php as a cgi rather than a module.
So, not only are they counting the hardware that linux is running on as being "spent on linux," they're also counting existing hardware on which linux will be installed as being "spent" on linux as well.
Spend once, expense twice? Linux really has grown up in the corporate world!
As cool as it is to rag on itanium, anyone who reads up on it knows that EPIC type design adresses a key weakness in modern cpu architecture.
We're going to have to go there eventually. I guess we're just going to have to evolve there slowly. First multicore, then many-multicore, then we'll realize there's too much overlap and the'll be a "head" core that manages the others, until eventualy we're right back to an itanium/epic-like design.
That is unless ILP is a white whale and TLP is all that matters. Guess we shall see.
Y'ever notice how whenever a person ends a newsgroup/forum/bullettinboard post with "Personally I..." it is always some kind of "look how amazingly fucking leet I am for using this hardcore way of doing things" type bullshit?
This is not news. Steam working would have been news. Anyone who sat through CS 1.6 (or for that matter still plays it) knows that not only did they spectacularly fcuk up the initial launch, but they use it to continually push new patches that break more things.
In fact I'm laying out a prediction now. Somtime within the next three months a Steam-forced "update" will cause major breakage to a signifigant number of HL2/CS:S users. I see three likely scenarios:
- server update causes massive slowdown because it wasn't tested well, everyone experiences horrible lag, former 24 person servers can barely handle 16
- engine update causes breakage with some combination of directx and a particular video driver. Anyone with the fateful combo is left with a BSOD.
- "authentication" update (in an attempt to thwart piracy) is overzealous and buggy and locks lots of legitimate users out. Valve takes at least three days to resolve it.
Re:the contest, months of waiting... for THAT?
on
NetBSD Chooses New Logo
·
· Score: 2, Insightful
I'm sorry, but it's really hard to get excited about that logo. Seems to me they wanted to be so neutral, so inoffensive to everyone in the entire world that they picked a logo that means nothing.
It's classic design-by-commitie.
er... I'm sorry I meant "open development process"
Does anyone know if software raid-5 in linux uses a chunk of memory specifically for the write cache? Most hardware raid5 cards have memory for this so that the card can tell the OS everything is done being written and then flush it out of cache at its convinience. If software raid-5 actually relies on the writes to be finished, it would be drastically slower (for writes).
I've seen doubleclick's slow servers seriously impact the load time of websites that use them. This stuff better not cause random ping spikes on multiplayer game servers.
I keep seeing people say this, but I cannot find a p233 w/64mb laptop with a working battery (even if only 20 min) anywhere. All the ones on ebay are at least $150.
A soekris 4801 (not the 4501 mentioned in earlier replies) has a 266mhz x86 processor and can be purchased with a case/enclosure with laptop harddrive mounting bracket inside. Its smaller than your average college textbook, runs on a "wall wart" power supply, and has 3 ethernet interfaces.
Unfortunatly the morons use frames so here's a link to the front page: http://www.soekris.com/
They also don't have pictures of the case on their website* but people on the mailing list have posted a few iirc.
*frames and no pictures and no online ordering.... I swear these guys are practically trying to put themselves out of business
Hey look a perfect example of why support can be so expensive. People like the parent waste a ton of IBM's time and money on what turns out to be a cock up on their end.
Conversley, if there's a bug in the default xfs setup in the default redhat kernel, IBM calls up redhat and says "fix it" and redhat says "sir yes sir I love you sir would you like coffe with that".
It doesnt get thrown onto some mailing list, argued about for a few days, crammed into somebodys bugzilla or wiki, opened and closed three times, moved catagories, sit through a developer moving appartments, ignored by an irc channel with 60 idling people, dissapear into usenet, etc.
99% of someone saying they "offer support" is just the fact they they have the balls to say "we're so sure this works we're prepared to accept the dent supporting it will make in our budget". For instance with redhat, the very fact that nearly all their customers can file a support request with them now, means that if they didn't have a damn good product, they would lose all their money to support costs. Plus, when there are genuine fixes to be made, they can use their margins to hire full time programs to fix exactly what their customers need fixed pronto... not when some package maintainer gets around to it. You'll notice this is why a metric fuckton of open source projects have @redhat.com email accounts on their credits page. You'll also notice that redhat's commitment to the GPL is near debian like, they even buy other software products and gpl them. When you're paying redhat to support your linux, you're actually in a large part paying them to improve linux to a point where it needs less support.
I didn't mean to turn this into redhat praising, but merely to counter the insane, annoying, and far far to prevalant attitude around here that redhat is "screwing" anybody with their pay model or "turning their backs on the community". If anything paying for redhat is the easiest way I can think of to support linux development (especially the kernel).
I want no part of it, because facts are facts, and the more high-tech, the more problems there will be.
When I die crashing my hoverbike because I was pulling 3G's and one of those newfangled e-lec-tronics failed, I will die a much happier man than if we'd listened to you, mister "hold it right here this has gone too far, back in the good old days we just used mechanics and we liked it."
Slashdot Mirror
Personally I think they would be best served by doing a little of each.
As linux and OSS mature more and more its going to become the distro's responsibility for making an intergrated, stable, and well tested set of software releases. This way the projects and developers can focus on what they want (adding features, rewrites, changing whatever they feel) while the distro focuses on what they/end-users want (dependancies, compatibility, intergration, testing, consistant builds, backported bug and security fixes)
This article is a perfect example. With distro's like redhat and suse shipping kernels that barely resemble the base one, Linus realizes that its becoming less-and-less his job to work out all the kinks. His job is to be constantly improving the kernel, and then the distro's can decide at what versions and pieces they want a la cart.
I don't know the detailed inner workings, but it seems like these projects are forever doomed to being a shadow of a "mostly" implimentation riddled with "gotchas" and always a few steps behind. I don't blame the developers in any way, its just we all know MS does not play nice with others.
2.) the size of the unit would be really big to accomidate the extra electronics and most importantly the much larger battery.
I'm sure Jobs knows, like we all do, that eventually the ipod will have to go there. But for now he can reap the design benefits of the smaller battery and the revenue stream of itunes for a year or two until miniturization runs its course.
This must seed at some increadibly slow speed or automatically hop off when it sees other seeds have arrived. They can't just give the bandwidth away for free unless they seriously minimize what actually gets used.
What is this "make shit up for the headline" hour? Lets see what a professional news organization has to say: http://olympics.reuters.com/newsArticle.jhtml?type =technologyNews&storyID=6960222
This is particularly important to PHP and webhosts/mass-virtual-hosters. The current model is to use things like safe_mode and openbasedir and limiting certian functions like exec(). Thats a very hacky way of trying to solve the problem of multiple users applications running as the same user without being able to mess with each other. Just saying out loud makes you realize how much a fix is needed.
Its also why any host worth its fees has to run php as a cgi rather than a module.
Spend once, expense twice? Linux really has grown up in the corporate world!
We're going to have to go there eventually. I guess we're just going to have to evolve there slowly. First multicore, then many-multicore, then we'll realize there's too much overlap and the'll be a "head" core that manages the others, until eventualy we're right back to an itanium/epic-like design.
That is unless ILP is a white whale and TLP is all that matters. Guess we shall see.
Personally I think its retarded.
In fact I'm laying out a prediction now. Somtime within the next three months a Steam-forced "update" will cause major breakage to a signifigant number of HL2/CS:S users. I see three likely scenarios:
- server update causes massive slowdown because it wasn't tested well, everyone experiences horrible lag, former 24 person servers can barely handle 16
- engine update causes breakage with some combination of directx and a particular video driver. Anyone with the fateful combo is left with a BSOD.
- "authentication" update (in an attempt to thwart piracy) is overzealous and buggy and locks lots of legitimate users out. Valve takes at least three days to resolve it.
Does anyone know if software raid-5 in linux uses a chunk of memory specifically for the write cache? Most hardware raid5 cards have memory for this so that the card can tell the OS everything is done being written and then flush it out of cache at its convinience. If software raid-5 actually relies on the writes to be finished, it would be drastically slower (for writes).
I've seen doubleclick's slow servers seriously impact the load time of websites that use them. This stuff better not cause random ping spikes on multiplayer game servers.
these guys have raised the bar in a way that I'm blown away.
I'm gonna go see if they do servers this well. If so, me and the boss are having an equipment meeting on monday.
I keep seeing people say this, but I cannot find a p233 w/64mb laptop with a working battery (even if only 20 min) anywhere. All the ones on ebay are at least $150.
A soekris 4801 (not the 4501 mentioned in earlier replies) has a 266mhz x86 processor and can be purchased with a case/enclosure with laptop harddrive mounting bracket inside. Its smaller than your average college textbook, runs on a "wall wart" power supply, and has 3 ethernet interfaces. Unfortunatly the morons use frames so here's a link to the front page: http://www.soekris.com/ They also don't have pictures of the case on their website* but people on the mailing list have posted a few iirc. *frames and no pictures and no online ordering.... I swear these guys are practically trying to put themselves out of business
Conversley, if there's a bug in the default xfs setup in the default redhat kernel, IBM calls up redhat and says "fix it" and redhat says "sir yes sir I love you sir would you like coffe with that".
It doesnt get thrown onto some mailing list, argued about for a few days, crammed into somebodys bugzilla or wiki, opened and closed three times, moved catagories, sit through a developer moving appartments, ignored by an irc channel with 60 idling people, dissapear into usenet, etc.
99% of someone saying they "offer support" is just the fact they they have the balls to say "we're so sure this works we're prepared to accept the dent supporting it will make in our budget". For instance with redhat, the very fact that nearly all their customers can file a support request with them now, means that if they didn't have a damn good product, they would lose all their money to support costs. Plus, when there are genuine fixes to be made, they can use their margins to hire full time programs to fix exactly what their customers need fixed pronto... not when some package maintainer gets around to it. You'll notice this is why a metric fuckton of open source projects have @redhat.com email accounts on their credits page. You'll also notice that redhat's commitment to the GPL is near debian like, they even buy other software products and gpl them. When you're paying redhat to support your linux, you're actually in a large part paying them to improve linux to a point where it needs less support.
I didn't mean to turn this into redhat praising, but merely to counter the insane, annoying, and far far to prevalant attitude around here that redhat is "screwing" anybody with their pay model or "turning their backs on the community". If anything paying for redhat is the easiest way I can think of to support linux development (especially the kernel).
So pedophilia and stupid IP legal junk all wrapped into one. Its the best of the internet.
Ah but you forget... its much much more "geeky" to look down your nose at that newfangled XML.
http://www.openswan.org/development/roadmap.php
If you feel that it should only be kept/stored for people who have been convicted you should be railing against the current fingerprint system.