The bzip2 is 32MB. Get a real compression mechanism.
Unzipped only counts in terms of disc space. 160MB is small change for most machines. If its not, compile the kernel somewhere else and ship it over. Still, it further proves my point, because that means we're goign from 160MB source to 10MB compiled code.
My whole point is people bitch about bloat when the kernel is anything but bloated. For all the stuff it contains (which is a lot), submitted by all those different people (which is a lot), its incredibly lean.
I can't believe everyone calles 32MB of source "bloat". 32 MB is small compared to soemthings on your system, like X, KDE, GNOME sources. And in a lot of way, the Kernel is a lot more featureful than any of those. X for example, has a lot of "bloat" due to its build system.
Joe-Schmo is goign to use the binary kernel supplied by his Distribution anyway, and probably never upgrade it, until he goes and downloads a whole new ISO image. The actual running kernel stays really small due to the use of such things as MODULES, allowing only what is needed to be running at any given moment to run.
Bitch Bitch Bitch. Stop bitchin' about stuff you really don't have any idea about. The kernel is for all intents and purposes, small, and is indcredibly featureful for its size. So deal.
I do logout everynite, and leave my computer running on Standby. I clear as much junk as I can out, but can't clear out everything because this is at work. Believe me, I know how to tweak Windows when I can. Even still, I've yet to see a Windows box reliably stay both stable and fast for more than about a week at a time.
That's why I have to reboot my Win2K workstation every week to keep the performance up to an acceptible level, and my linux/BSD workstations are known for having multiple week uptimes and feeling just as fast, if not faster as tiem goes on.
Win2K might be stable, but the stability is like VMS stability -- at the cost of performance, especially over time. The is extra true when you have a memory leak or such other issues (which many windows applications do).
I refuse to use a "stable" environment that slows down unless I have to. And I'm runing nothing but a web browser, Outlook, telnet and a X server most days. Sometimes not even that much. Yet, I have to reboot every week to keep it running fast.
That's not real stability to me. Sorry, no dice.
I'm glad I don't use a blog
on
Blogger Hacked
·
· Score: 4, Funny
I wouldn't want some l337 hax0r coming in and reading everything about my personal life...
No, I'm just overstressed and my brain has failed to function. Either way you look at it, ist still funny.
Besdies, I'm cynical enough to say Berman and Fritz are really the same person, who simply hates geeks. The answer of course is from Dilbert, essentially that "Computer geeks have sex appeal", while being a Senator does not (but being President does, only if the women is ugly).
I think the real reason it isn't happening is because Berman learned from here that his Musical Car horn on his nice shiny Cadallic would be outlawed.
The new law will probably be...
"All devices which play digital copyrighted stuff must be regulated, except for my musical car horn."
Exactly. Meanwhile, and this is the unfair part, I'm here developing better roadway and roadway systems for the United States, which in all reality, doesn't really need them. Nice as they are, we could get by without a lot of the transporation projects in the US. However, its a job so I cannot complain. Ironic, isn't it?
Understand that the portions of India that are essentially CS factories do have enough infrastructure to support this sort of activity. While its not very well-developed, it is sufficent. India is unique in that sense, because a lot of countries don't have the resource to just throw up an infrastructure overnight like the US can. Importing infrastructure isn't easy. It takes resources,money,time, and talent. Understand that last part, talent is mostly gainfully employed within industralized nations making their current infrastructure better. While it may not seem fair on a global scale its true. Overtime, everyone moves up the ladder, but the people at the top get further and further away from the people below them. This also applies to countries as well.
As far as human resources are concerned, given that IIRC India has roughly 1 billion people, and China is the only other nation of that size, I'd hardly say that other 3rd world nations have lots of human resources.
While I appreciate your noble intentions, I'm not 100% sure how software development would help most 3rd world and developing nations. Unless, I've really been living under a rock, most of the people in such nations who would benefit from such are high up the power ladder and have little to no interest in distributing down the ladder.
Besides, wouldn't one have to focus on developing the infrstructure to run said software anyway. Last time I checked, running software needs computers. Computers need power, connectivity, and even sometimes access to this Internet thingy. If I wanted to lead a project to help developing nations, I'd be much more interested in building telecommunications and electrical infrastrucutre then writing software they probably can't run or use for much good yet anyway.
While your idea is noble, I think perhaps it is a little too soon to be really globaly useful?
While I don't remember the math, I'm pretty certain that 30dbM at 2GHz doesn't translate out to 1W. Even if it did, its not really enough to cause lots of trouble. Second off, you would need on the order of a kW before you could potentiall spark something flammable (think about of the power output of the microwave, and it still doesn't usually set stuff on fire). While disrupting internal elctronics is possible, most aircraft equipment is designed to deal with that kind of interference. Its not like you would melt metal or anything.
Not true. A CD and a CD-R are written to completely differently. A CD-R is still a CD-R. Find a really old, first-generation CD player. Try playing a CD-R in it. It won't, simply because it can comprehend the physical format. I don't know all the complex details, but I do know a CD-R != CD.
Even so, you can still 'burst' the bandwidth past the point where it the network can handle it.
Though I'm fairly sure the server is probably poorly/not correctly configured as well. Though a lot of times, I bet they don't know they are goign to get/.'d until its too late, and don't change their config until its too late.
Not that laziness is an excuse for this kinda event.
That wasn't what I was quite referring to. I meant physical bandwidth, like a T1. Chances are, if your pipe is small enough, the site is going to stop responding during a/.'ing no matter how good your server is. I could rig up a Quad PIII box to serve a site, but you're still not getting in if my only pipe is a 56K modem.
Understand some people don't have enough bandwidth to handle a thorough/.'ing. Sooner or later, the site is goign to stop responding simply because you run out of effective bandwidth. Also understand not everyone can afford what they talk about.
The problem is that the X client stores almost nothing about its state, the X server stores all that information. Because of buffering, network latency and the like, the information on the X client about the GUI state is usually never 100% accurate. The X server would have to transfer the information to the new X server, or another extension to the protocol has to be made.
COMMAND.COM is teh suck. It doesn't even have simple little tricks like command output substitution and the like. It really is good for nothing, and the tools are OK, not great.
Unfortunately, its all true. Everyone here is doing their job on time. Essentially, we end up waiting on everyone else so we can get their work done. Its sorta like I can't build a house if I don't get my wood on time. Well, I have plans to build the house, but no wood to build it with. Believe me, if everyone else did their job we'd be done Phase I by now.
Slashdot Mirror
The bzip2 is 32MB. Get a real compression mechanism.
Unzipped only counts in terms of disc space. 160MB is small change for most machines. If its not, compile the kernel somewhere else and ship it over.
Still, it further proves my point, because that means we're goign from 160MB source to 10MB compiled code.
My whole point is people bitch about bloat when the kernel is anything but bloated. For all the stuff it contains (which is a lot), submitted by all those different people (which is a lot), its incredibly lean.
No, the whole kernel is about 32MB source. Binary is far smaller.
Don't compare a 43 MB binary download to a 32MB source download. That's apples to oranges.
I can't believe everyone calles 32MB of source "bloat". 32 MB is small compared to soemthings on your system, like X, KDE, GNOME sources. And in a lot of way, the Kernel is a lot more featureful than any of those. X for example, has a lot of "bloat" due to its build system.
Joe-Schmo is goign to use the binary kernel supplied by his Distribution anyway, and probably never upgrade it, until he goes and downloads a whole new ISO image. The actual running kernel stays really small due to the use of such things as MODULES, allowing only what is needed to be running at any given moment to run.
Bitch Bitch Bitch. Stop bitchin' about stuff you really don't have any idea about. The kernel is for all intents and purposes, small, and is indcredibly featureful for its size. So deal.
That if I steal a hummer from the Army and run-away changing the camo patterns, they won't be able to find me?
I call that one over there!
I do logout everynite, and leave my computer running on Standby. I clear as much junk as I can out, but can't clear out everything because this is at work. Believe me, I know how to tweak Windows when I can. Even still, I've yet to see a Windows box reliably stay both stable and fast for more than about a week at a time.
That's why I have to reboot my Win2K workstation every week to keep the performance up to an acceptible level, and my linux/BSD workstations are known for having multiple week uptimes and feeling just as fast, if not faster as tiem goes on.
Win2K might be stable, but the stability is like VMS stability -- at the cost of performance, especially over time. The is extra true when you have a memory leak or such other issues (which many windows applications do).
I refuse to use a "stable" environment that slows down unless I have to. And I'm runing nothing but a web browser, Outlook, telnet and a X server most days. Sometimes not even that much. Yet, I have to reboot every week to keep it running fast.
That's not real stability to me. Sorry, no dice.
I wouldn't want some l337 hax0r coming in and reading everything about my personal life...
Oh wait, everyone can do that.
Doh!
s/Fritz/Hollings/. Man I need to get a function brain or a new job.
No, I'm just overstressed and my brain has failed to function. Either way you look at it, ist still funny.
Besdies, I'm cynical enough to say Berman and Fritz are really the same person, who simply hates geeks. The answer of course is from Dilbert, essentially that "Computer geeks have sex appeal", while being a Senator does not (but being President does, only if the women is ugly).
I think the real reason it isn't happening is because Berman learned from here that his Musical Car horn on his nice shiny Cadallic would be outlawed. The new law will probably be ...
"All devices which play digital copyrighted stuff must be regulated, except for my musical car horn."
Exactly. Meanwhile, and this is the unfair part, I'm here developing better roadway and roadway systems for the United States, which in all reality, doesn't really need them. Nice as they are, we could get by without a lot of the transporation projects in the US. However, its a job so I cannot complain. Ironic, isn't it?
Understand that the portions of India that are essentially CS factories do have enough infrastructure to support this sort of activity. While its not very well-developed, it is sufficent. India is unique in that sense, because a lot of countries don't have the resource to just throw up an infrastructure overnight like the US can. Importing infrastructure isn't easy. It takes resources,money,time, and talent. Understand that last part, talent is mostly gainfully employed within industralized nations making their current infrastructure better. While it may not seem fair on a global scale its true. Overtime, everyone moves up the ladder, but the people at the top get further and further away from the people below them. This also applies to countries as well.
As far as human resources are concerned, given that IIRC India has roughly 1 billion people, and China is the only other nation of that size, I'd hardly say that other 3rd world nations have lots of human resources.
While I appreciate your noble intentions, I'm not 100% sure how software development would help most 3rd world and developing nations. Unless, I've really been living under a rock, most of the people in such nations who would benefit from such are high up the power ladder and have little to no interest in distributing down the ladder.
Besides, wouldn't one have to focus on developing the infrstructure to run said software anyway. Last time I checked, running software needs computers. Computers need power, connectivity, and even sometimes access to this Internet thingy. If I wanted to lead a project to help developing nations, I'd be much more interested in building telecommunications and electrical infrastrucutre then writing software they probably can't run or use for much good yet anyway.
While your idea is noble, I think perhaps it is a little too soon to be really globaly useful?
While I don't remember the math, I'm pretty certain that 30dbM at 2GHz doesn't translate out to 1W. Even if it did, its not really enough to cause lots of trouble. Second off, you would need on the order of a kW before you could potentiall spark something flammable (think about of the power output of the microwave, and it still doesn't usually set stuff on fire). While disrupting internal elctronics is possible, most aircraft equipment is designed to deal with that kind of interference. Its not like you would melt metal or anything.
As an anal-retentive comment, most consumer devices are FCC Class B, not A.
Not true. A CD and a CD-R are written to completely differently. A CD-R is still a CD-R. Find a really old, first-generation CD player. Try playing a CD-R in it. It won't, simply because it can comprehend the physical format. I don't know all the complex details, but I do know a CD-R != CD.
Even so, you can still 'burst' the bandwidth past the point where it the network can handle it.
/.'d until its too late, and don't change their config until its too late.
Though I'm fairly sure the server is probably poorly/not correctly configured as well. Though a lot of times, I bet they don't know they are goign to get
Not that laziness is an excuse for this kinda event.
That wasn't what I was quite referring to. /.'ing no matter how good your server is. I could rig up a Quad PIII box to serve a site, but you're still not getting in if my only pipe is a 56K modem.
I meant physical bandwidth, like a T1. Chances are, if your pipe is small enough, the site is going to stop responding during a
Understand some people don't have enough bandwidth to handle a thorough /.'ing. Sooner or later, the site is goign to stop responding simply because you run out of effective bandwidth. Also understand not everyone can afford what they talk about.
I WIN WIN WIN
I WIN TOO!
Its far more complex than that.
The problem is that the X client stores almost nothing about its state, the X server stores all that information. Because of buffering, network latency and the like, the information on the X client about the GUI state is usually never 100% accurate. The X server would have to transfer the information to the new X server, or another extension to the protocol has to be made.
COMMAND.COM is teh suck. It doesn't even have simple little tricks like command output substitution and the like. It really is good for nothing, and the tools are OK, not great.
Try coding this (rough example as I'm under NDA):
;)
Req 1. The polling time shall be 3 seconds, and shall not be able to be changed.
Reg 3457. The standard polling time shall be 3 seconds, and be configurable by the operator.
This is a REAL example. Which one do I do? Huh, punk? Feelin' lucky
Unfortunately, its all true. Everyone here is doing their job on time. Essentially, we end up waiting on everyone else so we can get their work done. Its sorta like I can't build a house if I don't get my wood on time. Well, I have plans to build the house, but no wood to build it with. Believe me, if everyone else did their job we'd be done Phase I by now.
Lunch break you fool. Lunch break.
Besides, I'm only the intern. Its not like I'm important *rolls eyes*