1) System is based upon the amount of spam received by customers and depends on some users having a high proportion of spam. 2) The customers are using the system, so their level of spam would reduce to a very low average. 3) Nobody in the system is receiving a lot of spam so the system can no longer easily identify spam. 4) The level of spam increases again. 5) Goto 1.
It would be interesting to see where the spam level received balances out too.
I had this problem on my laptop but I refused to believe that the only solution to it was to turn off the power saving (which is what the "hdparm -B255" does). That's a crappy fix that deals with the symptom not the cause and I wish more people would just ask "what does it do?" before blindly following recommendations like this on forums!
A little research revealed that the ext3 filesystem updates it's journal every 5 seconds, coincidentally about as frequently as my hard drive was restarting. Adding a "commit=300" parameter to the mount line in fstab now means my hard drive only restarts once every five minutes to sync the file system and I still get the benefits of lower power usage in between.
On a desktop where the power could go off you would not want this, but if you have a laptop that is running on batteries, there is not going to be any loss of power so the only reason this longer sync period would be a problem would be if the system actually crashed, and everyone knows linux doesn't crash;o)
So it's really an ext3 (therefore Linux kernel) thing rather than an Ubuntu problem, however it would be nice if Ubuntu automatically changed this sync setting when switching between battery and ac power.
Users who are not experiencing this problem are probably using a non-journalled filesystem like ext2.
Problem is that radio waves aren't just used to listen to the radio they are used for all kinds of stuff.
Basically he's saying why can't all radio devices IN THE WORLD happily co-exist using the same frequency - that's like saying "why do I need this list of common port numbers in/etc/services? Why can't all my daemons run on the same port?"
As far as I can see the answer is the same for the PC and the radio world, technically they could, but you would not really be improving anything, just complicating things - when someone connected to your groovy-phat-all-encompasing-port-service (port 1 I presume?) they would have to specify which service they want (and/or what service they are offering in the case of radio) and ooh how would that be done? prolly with a number!.... and where would we store that list of service identifiers!? (and who would maintain it?)
So the port model is sensible for an OS and equally in radio frequencies it is sensible to allocate separate bands for separate uses (and it always will be) - Besides don't some radio devices already use *exactly* the same frequency? For example remote-locking-car-keys they just broadcast a particular "key" encrypted on a set frequency don't they? This is one of few practical uses for devices on the same frequency though because there is no constant stream of data to be interrupted by other devices.
Slashdot Mirror
Radio-active boy?
How I see this working:
1) System is based upon the amount of spam received by customers and depends on some users having a high proportion of spam.
2) The customers are using the system, so their level of spam would reduce to a very low average.
3) Nobody in the system is receiving a lot of spam so the system can no longer easily identify spam.
4) The level of spam increases again.
5) Goto 1.
It would be interesting to see where the spam level received balances out too.
I had this problem on my laptop but I refused to believe that the only solution to it was to turn off the power saving (which is what the "hdparm -B255" does). That's a crappy fix that deals with the symptom not the cause and I wish more people would just ask "what does it do?" before blindly following recommendations like this on forums!
;o)
A little research revealed that the ext3 filesystem updates it's journal every 5 seconds, coincidentally about as frequently as my hard drive was restarting. Adding a "commit=300" parameter to the mount line in fstab now means my hard drive only restarts once every five minutes to sync the file system and I still get the benefits of lower power usage in between.
On a desktop where the power could go off you would not want this, but if you have a laptop that is running on batteries, there is not going to be any loss of power so the only reason this longer sync period would be a problem would be if the system actually crashed, and everyone knows linux doesn't crash
So it's really an ext3 (therefore Linux kernel) thing rather than an Ubuntu problem, however it would be nice if Ubuntu automatically changed this sync setting when switching between battery and ac power.
Users who are not experiencing this problem are probably using a non-journalled filesystem like ext2.
Problem is that radio waves aren't just used to listen to the radio they are used for all kinds of stuff.
/etc/services? Why can't all my daemons run on the same port?"
.... and where would we store that list of service identifiers!? (and who would maintain it?)
Basically he's saying why can't all radio devices IN THE WORLD happily co-exist using the same frequency - that's like saying "why do I need this list of common port numbers in
As far as I can see the answer is the same for the PC and the radio world, technically they could, but you would not really be improving anything, just complicating things - when someone connected to your groovy-phat-all-encompasing-port-service (port 1 I presume?) they would have to specify which service they want (and/or what service they are offering in the case of radio) and ooh how would that be done? prolly with a number!
So the port model is sensible for an OS and equally in radio frequencies it is sensible to allocate separate bands for separate uses (and it always will be) - Besides don't some radio devices already use *exactly* the same frequency? For example remote-locking-car-keys they just broadcast a particular "key" encrypted on a set frequency don't they? This is one of few practical uses for devices on the same frequency though because there is no constant stream of data to be interrupted by other devices.
I was starting to think that no bugger had actually looked at source code! Are we seriously the only slashdot coders?!