Well, I happened to come accross this site, which lists a bunch of codes for 'hidden' features of a variety of cell phones including ericcson, motorola, nokia, sony, samsung, etc.
In my school (Ryerson Polytechnic University in Toronto).. Our primary operating systems are Linux and Solaris.
The 3rd year Advanced O/S course is based using Minix (yes, this is where linux came from) and one of the projects is to develop a memory manager for the O/S.
Come out with a new Open-Source solution and market it cross platform. Make it have all the capabilities of Realplayer and Media Player (with the exception of patent issues).. Call it Open Media Player (or something like that). If it's mure CPU/RAM/compression efficient, people will use it!
Maybe even put DeCSS code in it to play DVD's.. (just to see how long it takes the FBI.. and get the media's attention)
My appologies.. my November log sais.. (Total Downtime = 1906 mins) of 29 days, 15:4 (42664 minutes) = 4 % downtime
I seemed to have some screwed up calc in my head =).. The reason I said 15% because there was a time near the beginning of the month when downtime has reached that high.
As for the packet loss issue you have mentioned... I have come up with a solution to get @home back into gear...
In October, I have created a shellscript to keep log of ping requests (every few seconds) to the @home gateway and DNS servers. This would then give me a total downtime in minutes for the month.
The month of October has shown an @home downtime of 2206 minutes on my server (logs are available)
After calling to complain at the end of the month, they gave me a measly $2.40 credit (or something like that)..
The Month of November improved slightly and gave me a downtime of only 1906 minutes (about 15% downtime). Still extremely poor.. I called and complained. Spoke with a supervisor this time. He was kind enough to give me a free month.
Then comes around the month of December. After speaking with people from the Rogers@home users association and informing them of the program I made to get people to use it (back in October)... I have noticed a significant improvement in downtime and packet loss.. Downtime has improved to just over 200 minutes (close to 0% !!).. A Lot Better.. As for January, so far I only have about 100 minutes of downtime which is very good relative to a few months ago.
If anybody would like some more info on this cheap shellscript I made, or in yelling @ supervisors to get free months (apparently they can give you 1 month credit for every 3 months of non-stable connections), feel free to email me.
Take out the 'no.spammers-xyz' in my e-mail and you've got my address.. I'll be happy to send out this shellscript I created for linux as long as I get credit for the creation..
Personally, if I were to get a portable mp3 player, I would hope that it takes MP3 burned CD-R's, what's the point of spending so much cash for only 64MB of storage (about 70 mins audio). I can burn an audio cd that holds 74 minutes audio and use a regular cd player for a fraction of the cost.
I can burn an mp3 cd that holds 800 minutes audio.. but this would only be readable on a PC. I'd rather not carry around a laptop computer just to listen to my music on the subway to school.
Now as for G-Shock sales.. I've had my casio G-Shock watch for about 8 years now.. This was the first of many watches that has not actually broken. This watch can take a beating and still keep working. The reason why they can't sell any more G-Shocks is because the people who wanted them already baught them years ago, and they still work ok.
For those of you who read the article, it seems to me that these people are EVIL and they're trying to take a complete monopoly over anything that has anything to do with linux in Uruguay!
I propose that we start a fund to hire lawyers for the Uruguyan Linux Users Group to fight these EVIL monopolistic fruitcakes.
well.. that's really what I meant.. the language perl was ok.. it was the perl programmers who didn't pay attention to what they were really doing that caused the mistakes.
I wouldn't say the same for java now.getYear() function. I think that was a dumb language to use a 2 digit year =99 then suddenly switch to a 4 digit year.. but still.. programmers who RTFM would know better.
Apparently some people blamed M$ for that getYear() problem, but I hate to say this, but this time it wasn't their fault, it was a stupidity in both the language itself, and the programmers who didn't catch onto this stupidity.
Now.. here's something I'd bet they never thought of, or can't do too much about.
To avoid looking at the ads, I'm sure people will be setting up some sort of proxy, ip masq/NAT, internet connection sharing, or firewall boxes to connect to the internet which displays the ads.
All the other machines on the network will have ad-free internet access!!!!
No.. because there is a difference in computer 'k' and SI standard 'k'..
k = killo = 10^3 = 1000 in standards for measurement
k = killo = 2^10 = 1024 in computer terms...
to avoid confusion (I posted this before).. I beleive I read an article previously on slashdot that there is a proposed standard to create something called kibibytes or Mibibytes which is 2^10 and 2^20 respectively.
1) A First post message (done by someone other than the person who wrote the article) gets a score of 5!
2) When you're watching the Y2K countdouns all over the world and you KNOW they're NOT using XNTP to synchronize time, because the time on the countdown on the TV is DIFFERENT from the countdown in the actual party which is different from the clock on the same TV which is even different than your sattelite clock synched XNTP computer
3) When we suddenly discover the real power of theory of relativity because we are suddenly 17100 years in the future (19100) or 190000 years in the future (192000) and the technology hasn't changed.
4) When we realize we travelled back in time to the year 100.
5) When everyone get's paged just after midnight.. then when everyone goes to pick up their voice messages (which they know say something along the lines of "I'm still alive") using their cell phone. Either there are no cell channels available, or the pager system is overloaded. (This happened to me for about 15 mins after midnight.. kept switching between phone has busy system, then pager has overloaded system)
Well.. Last night I turned on all my 4 computers @ home just to see if I can find anything in the logs over the midnight period.. It was nice to see no downtimes anywhere near the rollover.. my cable provider did go down for a few seconds this morning.. but nothing Y2K related.
For those of you interested.. the year 100 and 19100 are perl script errors due to concatenating the year 99, or 100 to the end of "19"..
The year 192000 originated from problematic Java/Javascripts.. Java was written very stupidly.. If the year is = 2000 it would suddenly report a 4 digit year. this would make it slightly annoying to program something that is Y2K compliant and Pre-Y2K compliant.
it would have to look something like
if (now.getDate() 100) document.write(1900 + now.getDate()); else document.write(now.getDate());
1) A First post message (done by someone other than the person who wrote the article) gets a score of 5!
2) When you're watching the Y2K countdouns all over the world and you KNOW they're NOT using XNTP to synchronize time, because the time on the countdown on the TV is DIFFERENT from the countdown in the actual party which is different from the clock on the same TV which is even different than your sattelite clock synched XNTP computer
3) When we suddenly discover the real power of theory of relativity because we are suddenly 17100 years in the future (19100) or 190000 years in the future (192000) and the technology hasn't changed.
4) When we realize we travelled back in time to the year 100.
5) When everyone get's paged just after midnight.. then when everyone goes to pick up their voice messages (which they know say something along the lines of "I'm still alive") using their cell phone. Either there are no cell channels available, or the pager system is overloaded. (This happened to me for about 15 mins after midnight.. kept switching between phone has busy system, then pager has overloaded system)
Well.. Last night I turned on all my 4 computers @ home just to see if I can find anything in the logs over the midnight period.. It was nice to see no downtimes anywhere near the rollover.. my cable provider did go down for a few seconds this morning.. but nothing Y2K related.
For those of you interested.. the year 100 and 19100 are perl script errors due to concatenating the year 99, or 100 to the end of "19"..
The year 192000 originated from problematic Java/Javascripts.. Java was written very stupidly.. If the year is = 2000 it would suddenly report a 4 digit year. this would make it slightly annoying to program something that is Y2K compliant and Pre-Y2K compliant.
it would have to look something like
if (now.getDate() 100) document.write(1900 + now.getDate()); else document.write(now.getDate());
Slashdot Mirror
Well, I happened to come accross this site, which lists a bunch of codes for 'hidden' features of a variety of cell phones including ericcson, motorola, nokia, sony, samsung, etc.
l arT&T.htm
http://www.commservice.net/ItalianBadBoys/Cellu
In my school (Ryerson Polytechnic University in Toronto).. Our primary operating systems are Linux and Solaris.
The 3rd year Advanced O/S course is based using Minix (yes, this is where linux came from) and one of the projects is to develop a memory manager for the O/S.
Looks like mp3's are obviously doing some good for the music industry.
.. That's a DOUBLE NEGATIVE.. which means they made $1.4 billion dollars from pirating MP3's..
They lost NEGATIVE $1.4 billion
Therefore, pirating MP3's does good for the music industry
The article mentioned that the power consumtion is small enough for devices made of this to be able to be powered from body heat.
If it takes such little amounts of energy, how would such a device react to larger 'jolts' of electricity such as static buildup in clothes?
Would this not potentially damage these devices, if not, cause them to act strangely?
Nice to know that Linux did it first before Windows.
I agree, we should go with the standards.
Come out with a new Open-Source solution and market it cross platform. Make it have all the capabilities of Realplayer and Media Player (with the exception of patent issues).. Call it Open Media Player (or something like that). If it's mure CPU/RAM/compression efficient, people will use it!
Maybe even put DeCSS code in it to play DVD's.. (just to see how long it takes the FBI.. and get the media's attention)
I seem to remember the version being waited on for so long was 0.4, and since, they've created 5 versions before the source was released again.
Did anybody notice that the 2 articles on MSNBC and ABCNews were exactly identical?
Different perspective? No.. Maybe different HTML formatting, but identitcal articles.
Both done by associated press (c) 2000 (see bottom of articles)
If you're in Canada, the product is available at Future Shop but I beleive they are selling it for $329 CAN $.. equiv to about $225 US$.
Do a product search and lookup Apex or AD-600A
My appologies.. my November log sais..
(Total Downtime = 1906 mins) of 29 days, 15:4 (42664 minutes) = 4 % downtime
I seemed to have some screwed up calc in my head =).. The reason I said 15% because there was a time near the beginning of the month when downtime has reached that high.
If you check with IANA the whole 24.*.*.* class A domain is owned by @home, they sold off a few class B's.
As for the packet loss issue you have mentioned... I have come up with a solution to get @home back into gear...
In October, I have created a shellscript to keep log of ping requests (every few seconds) to the @home gateway and DNS servers. This would then give me a total downtime in minutes for the month.
The month of October has shown an @home downtime of 2206 minutes on my server (logs are available)
After calling to complain at the end of the month, they gave me a measly $2.40 credit (or something like that)..
The Month of November improved slightly and gave me a downtime of only 1906 minutes (about 15% downtime). Still extremely poor.. I called and complained. Spoke with a supervisor this time. He was kind enough to give me a free month.
Then comes around the month of December. After speaking with people from the Rogers@home users association and informing them of the program I made to get people to use it (back in October)... I have noticed a significant improvement in downtime and packet loss.. Downtime has improved to just over 200 minutes (close to 0% !!).. A Lot Better.. As for January, so far I only have about 100 minutes of downtime which is very good relative to a few months ago.
If anybody would like some more info on this cheap shellscript I made, or in yelling @ supervisors to get free months (apparently they can give you 1 month credit for every 3 months of non-stable connections), feel free to email me.
Take out the 'no.spammers-xyz' in my e-mail and you've got my address..
I'll be happy to send out this shellscript I created for linux as long as I get credit for the creation..
Personally, if I were to get a portable mp3 player, I would hope that it takes MP3 burned CD-R's, what's the point of spending so much cash for only 64MB of storage (about 70 mins audio). I can burn an audio cd that holds 74 minutes audio and use a regular cd player for a fraction of the cost.
I can burn an mp3 cd that holds 800 minutes audio.. but this would only be readable on a PC. I'd rather not carry around a laptop computer just to listen to my music on the subway to school.
Now as for G-Shock sales.. I've had my casio G-Shock watch for about 8 years now.. This was the first of many watches that has not actually broken. This watch can take a beating and still keep working. The reason why they can't sell any more G-Shocks is because the people who wanted them already baught them years ago, and they still work ok.
I knew that if I'd mention that people were finally behaving in a slashdot article, that somebody would do this.
Ah well.. better one troll than 50.
Hrm.. maybe there's a troll convention tonight.
Can't wait to see this stuff pop up in cubs, bars, etc, especially in some cool new alcoholic drink.
BTW.. nice to see a whole 30 posts or so without any "first post" or "natalie portman" crap. I think that's a first.
I'm serious about starting a fund to fight these guys trying to trademark the linux name, that's just wrong.
If you think I'm a troll for trying to protect Linux, the open-source community and preventing monopoly's then go ahead and call me a troll...
For those of you who read the article, it seems to me that these people are EVIL and they're trying to take a complete monopoly over anything that has anything to do with linux in Uruguay!
I propose that we start a fund to hire lawyers for the Uruguyan Linux Users Group to fight these EVIL monopolistic fruitcakes.
It would be nice to see someone release a distro of linux on these new portable devices now that there's a GPL'd version of the dev kit for it.
well.. that's really what I meant.. the language perl was ok.. it was the perl programmers who didn't pay attention to what they were really doing that caused the mistakes.
I wouldn't say the same for java now.getYear() function. I think that was a dumb language to use a 2 digit year =99 then suddenly switch to a 4 digit year.. but still.. programmers who RTFM would know better.
Apparently some people blamed M$ for that getYear() problem, but I hate to say this, but this time it wasn't their fault, it was a stupidity in both the language itself, and the programmers who didn't catch onto this stupidity.
Now.. here's something I'd bet they never thought of, or can't do too much about.
To avoid looking at the ads, I'm sure people will be setting up some sort of proxy, ip masq/NAT, internet connection sharing, or firewall boxes to connect to the internet which displays the ads.
All the other machines on the network will have ad-free internet access!!!!
No.. because there is a difference in computer 'k' and SI standard 'k'..
k = killo = 10^3 = 1000 in standards for measurement
k = killo = 2^10 = 1024 in computer terms...
to avoid confusion (I posted this before).. I beleive I read an article previously on slashdot that there is a proposed standard to create something called kibibytes or Mibibytes which is 2^10 and 2^20 respectively.
We know we have REAL Y2K problems when....
.. then when everyone goes to pick up their voice messages (which they know say something along the lines of "I'm still alive") using their cell phone. Either there are no cell channels available, or the pager system is overloaded. (This happened to me for about 15 mins after midnight.. kept switching between phone has busy system, then pager has overloaded system)
..
1) A First post message (done by someone other than the person who wrote the article) gets a score of 5!
2) When you're watching the Y2K countdouns all over the world and you KNOW they're NOT using XNTP to synchronize time, because the time on the countdown on the TV is DIFFERENT from the countdown in the actual party which is different from the clock on the same TV which is even different than your sattelite clock synched XNTP computer
3) When we suddenly discover the real power of theory of relativity because we are suddenly 17100 years in the future (19100) or 190000 years in the future (192000) and the technology hasn't changed.
4) When we realize we travelled back in time to the year 100.
5) When everyone get's paged just after midnight
Well.. Last night I turned on all my 4 computers @ home just to see if I can find anything in the logs over the midnight period.. It was nice to see no downtimes anywhere near the rollover.. my cable provider did go down for a few seconds this morning.. but nothing Y2K related.
For those of you interested.. the year 100 and 19100 are perl script errors due to concatenating the year 99, or 100 to the end of "19"
The year 192000 originated from problematic Java/Javascripts.. Java was written very stupidly.. If the year is = 2000 it would suddenly report a 4 digit year. this would make it slightly annoying to program something that is Y2K compliant and Pre-Y2K compliant.
it would have to look something like
if (now.getDate() 100) document.write(1900 + now.getDate());
else document.write(now.getDate());
Anyway.. Enjoy.. Happy Y2K.. l8z
sorry.. I meant to say now.getYear() rather than now.getDate()..
We know we have REAL Y2K problems when....
.. then when everyone goes to pick up their voice messages (which they know say something along the lines of "I'm still alive") using their cell phone. Either there are no cell channels available, or the pager system is overloaded. (This happened to me for about 15 mins after midnight.. kept switching between phone has busy system, then pager has overloaded system)
..
1) A First post message (done by someone other than the person who wrote the article) gets a score of 5!
2) When you're watching the Y2K countdouns all over the world and you KNOW they're NOT using XNTP to synchronize time, because the time on the countdown on the TV is DIFFERENT from the countdown in the actual party which is different from the clock on the same TV which is even different than your sattelite clock synched XNTP computer
3) When we suddenly discover the real power of theory of relativity because we are suddenly 17100 years in the future (19100) or 190000 years in the future (192000) and the technology hasn't changed.
4) When we realize we travelled back in time to the year 100.
5) When everyone get's paged just after midnight
Well.. Last night I turned on all my 4 computers @ home just to see if I can find anything in the logs over the midnight period.. It was nice to see no downtimes anywhere near the rollover.. my cable provider did go down for a few seconds this morning.. but nothing Y2K related.
For those of you interested.. the year 100 and 19100 are perl script errors due to concatenating the year 99, or 100 to the end of "19"
The year 192000 originated from problematic Java/Javascripts.. Java was written very stupidly.. If the year is = 2000 it would suddenly report a 4 digit year. this would make it slightly annoying to program something that is Y2K compliant and Pre-Y2K compliant.
it would have to look something like
if (now.getDate() 100) document.write(1900 + now.getDate());
else document.write(now.getDate());
Anyway.. Enjoy.. Happy Y2K.. l8z
Here's the problem with Java/Javascript..
It was always semi-Y2K compliant...
now.getYear() returns a 2 digit date if the date is = 2000
so it would work previously, but not after 2000