I've heard it may... Phone numbers are actually constructed in n+3+3+4 form, n=country code, 3=area code, 3=prefix, 4=(forget whats its called... oh well) By the way, this is where the lack of available phone numbers etc. comes from -- the phone company only allocated prefixes, rather than number ranges. If a company wants to buy 200 phone numbers, they either have to find someone who has already bought a prefix and work out something with them or purchase a block of 10000, leaving 9800 numbers unused... And on the memory techniques... I've found that memorizing long strings of numbers is easier if the numbers have a pattern, even if its a nonrepeating one, like pi... I have memorized 25 digits (3.1415926535897932384626433) just by breaking it into chunks that made sense:
3.14 - nearly everyone is taught this is in elementary school... plus, 4-1=3, which is the starting pre-digit 159 - notice 5-1=4, 9-5=4 26 - same, 6-2=4 53 - 5-3=2, which is half of 4 589 - this is the same as '59' but with an extra digit stuck in, which is merely one less than the '9' 79 - 9-7=2 323 - this is a string of threes, two units long, interrupted by a digit one less than the rest 846 - mentally, I swap the 4 and 6, and think of this as a pattern of a loss of 2 per digit, descending from 8 to 4 264 - this is the above with the 4 and 6 swapped, but the 8 is replaced by a number 6 less than itself 33 - this is the 323 with the 2 removed
I never have problems remembering what number each set starts on... but someone could apply mnemonics if they wanted to I guess.
I do that with everything... I'm both a touch-typist and a hunt-and-peck typist. If I've typed a word a number of times before, I can spit it out really fast, but if it's a new word I have to type it out really slow (although I don't actually have to be looking at the keys...)
I have (according to the manufacturere at least) a "3D chip" on my motherboard-video card (ewwww) - I looked at it, it's an ATI Rage 3D II (Mach64-based) - however, it's from the pre-3dfx days... does anyone know if I could get this working with Mesa in any way? As soon as he releases the source, I'll port it to SGI, btw - I also may do a port to SVGALib/VGAGL so it will rely on accelerated cards instead of GL-based cards.
It actually has quite a bit to do with slow hardware. Hard drives are given time to warm up before being tested (unlike those old XTs.... I remember booting it up, giving it two minutes for warm-up, and then rebooting...) Plus PCs have a slow RAM and bus throughput (SGI had 2.3 Gb/s in 1993, here it is in 1999, and we're still dozens of times slower) and with more and more memory being installed in PCs, RAM checks are beginning to take forever.
USB works great, but I can get PS/2 keyboards and mice real cheap at secondhand computer stores... and as for PCI, that same store sells all ISA cards for $5 apiece - and compare store prices! Cheap PCI ethernet cards are usually $5-$10 more than cheap ISA... and I've never had any problems with isapnp... true, it may not be for people who just switched over from windows, but its still not hard to use if you know about PC hardware. I have to say I am sad to see ISA go... especially because it's more difficult to build a PCI card if you're just builting experimental cards to test stuff - and you can't just use an ISA test machine because the end users will use PCI! Oh well....
Finally! This would/will be really cool - a platform-independent language makes no sense if it is really slow or simply doesn't work on a major computing platform...
You know whats really funny? Right on IBM's patent page thingy at http://patent.womplex.ibm.com/details?pn=EP00738 446B1 there's a link at the top of the page to "View Cart" - does anyone else see the irony in this? I'm sure somebody does.
This is what could get large corporations (read: trend setters) interested in Linux servers... since Linux occupies mostly the small-business server market, it needs to expand to the large-business server market and workstation market... Many companies have been getting Linux workstation projects up and running, but large-business server farms/clusters are definitely one of Linux's weak points right now.
(just had to get 2nd post;-) if databases are made copyrightable, there's a good chance that copyrighted database software for linux will produce databases that are copyright, limiting how they can be used... this is a bad thing!
Hey, maybe the slashdot crew should be nominated.... after all, they're about the most crucial part of the linux news world... and as everyone knows, news is important. Usually.;-)
10AM on a saturday morning and two comments posted already!?!?! They're not bots either... either we have two people who were forced to go to bed early by their parents, or they're in a different time zone. Or maybe they're insane enough to go to bed before 4am;-)
Someone needs to mirror the panix site - e-mail the guy and snag a copy of his perl script etc....
Anyways, here's my contribution to the humor:
Original: And one time, at band camp, I stuck a flute up my p*ssy.
French: And once, to the camp of tape, I stuck a groove to the top of my cat.
German: And once, at tape stocks, I adhered a flute up mean Pussy.
Italian: And once, to the encampment of wrap, I have attacked one rabbet on mine pussy.
Portuguese: E a time, in the encampment of the band, I pierced a flute above of my pussy.
Spanish: And once, in the field of the bandage, I stuck one flauta upon my kitten.
Notes: The portuguese "E a time" should be "And one time" - dunno why it can't translate the portuguese word for and.... weird.... Some other words didn't work too well - these are more obvious though. (Like "flauta")
I got another amazing idea! ("OH NO, Matt, Not another one of your amazing ideas again!?!?!" "Shut yer trap.") Obviously, e-mail and newsgroups would work fine, but the other sorts of requests, like file requests and data-processing requests, would be impossible to negotiate - you couldnt tell if the commands you sent were correct or not... Fortunately, there's a solution. Mirroring. It's not necessary to mirror everything, but you can make web surfing possible by mirroring their directory tree for the documents, and cgi-bins involved with site-searches; for other cgi-bins [data processing and file-requests], an interface would check for syntax in the data processing, then ship it out and tell the user approximately when they can expect their results back (a local program would save the incoming results and then provide a web interface to retrieving them) - file requests would be similar, there would be an ls -lR stored locally, and it would be checked to see if the file was there and if permissions allowed access by that user. (A crontab entry could mirror the file at appropriate intervals.) If the file was, data about its size, date, etc. would be given to the user, who would approve or disapprove the request - if the request was approved, then the file would be ordered to be shipped to one of many "Cache servers", which would have many very large disk storage media. The user could pick up the file later, and if another user requested the same file, they could be redirected to the cache server for immediate access. If the files remained unused on the cache server for a certain amount of time, they would be deleted to make room for other files being ordered. The only problem with this system - time and money. Time can be allowed though, since it would be pointless to have Interplanetary Internet implemented long before there was much up there to talk to. Money will hopefully be donated by generous research corporations (probably ones with orbiting satellites.)
They seem to have forgotten that UDP is a non-ACK'd unverified non-sequential protocol - you send the packets out and _hope_ they get there. Assuming they can make the networks reliable enough, UDP would be perfect - just send out commands split up into packets, with each packet tagged so they can be reassembled in the correct order, and be sure to send the packets in duplicate, from two different transceivers - then the request can be processed and the data sent back. Obviously, this would not work for things such as web browsing, FTP, and telnet - derivatives of TFTP and finger would be promising though.
Slashdot Mirror
I've heard it may... Phone numbers are actually constructed in n+3+3+4 form, n=country code, 3=area code, 3=prefix, 4=(forget whats its called... oh well)
By the way, this is where the lack of available phone numbers etc. comes from -- the phone company only allocated prefixes, rather than number ranges. If a company wants to buy 200 phone numbers, they either have to find someone who has already bought a prefix and work out something with them or purchase a block of 10000, leaving 9800 numbers unused...
And on the memory techniques... I've found that memorizing long strings of numbers is easier if the numbers have a pattern, even if its a nonrepeating one, like pi... I have memorized 25 digits (3.1415926535897932384626433) just by breaking it into chunks that made sense:
3.14 - nearly everyone is taught this is in elementary school... plus, 4-1=3, which is the starting pre-digit
159 - notice 5-1=4, 9-5=4
26 - same, 6-2=4
53 - 5-3=2, which is half of 4
589 - this is the same as '59' but with an extra digit stuck in, which is merely one less than the '9'
79 - 9-7=2
323 - this is a string of threes, two units long, interrupted by a digit one less than the rest
846 - mentally, I swap the 4 and 6, and think of this as a pattern of a loss of 2 per digit, descending from 8 to 4
264 - this is the above with the 4 and 6 swapped, but the 8 is replaced by a number 6 less than itself
33 - this is the 323 with the 2 removed
I never have problems remembering what number each set starts on... but someone could apply mnemonics if they wanted to I guess.
Just my several hundred pesos.
I do that with everything... I'm both a touch-typist and a hunt-and-peck typist. If I've typed a word a number of times before, I can spit it out really fast, but if it's a new word I have to type it out really slow (although I don't actually have to be looking at the keys...)
I have (according to the manufacturere at least) a "3D chip" on my motherboard-video card (ewwww) - I looked at it, it's an ATI Rage 3D II (Mach64-based) - however, it's from the pre-3dfx days... does anyone know if I could get this working with Mesa in any way?
As soon as he releases the source, I'll port it to SGI, btw - I also may do a port to SVGALib/VGAGL so it will rely on accelerated cards instead of GL-based cards.
It actually has quite a bit to do with slow hardware.
Hard drives are given time to warm up before being tested (unlike those old XTs.... I remember booting it up, giving it two minutes for warm-up, and then rebooting...)
Plus PCs have a slow RAM and bus throughput (SGI had 2.3 Gb/s in 1993, here it is in 1999, and we're still dozens of times slower) and with more and more memory being installed in PCs, RAM checks are beginning to take forever.
USB works great, but I can get PS/2 keyboards and mice real cheap at secondhand computer stores... and as for PCI, that same store sells all ISA cards for $5 apiece - and compare store prices! Cheap PCI ethernet cards are usually $5-$10 more than cheap ISA... and I've never had any problems with isapnp... true, it may not be for people who just switched over from windows, but its still not hard to use if you know about PC hardware. I have to say I am sad to see ISA go... especially because it's more difficult to build a PCI card if you're just builting experimental cards to test stuff - and you can't just use an ISA test machine because the end users will use PCI! Oh well....
Finally! This would/will be really cool - a platform-independent language makes no sense if it is really slow or simply doesn't work on a major computing platform...
You know whats really funny?8 446B1
Right on IBM's patent page thingy at
http://patent.womplex.ibm.com/details?pn=EP0073
there's a link at the top of the page to "View Cart" - does anyone else see the irony in this? I'm sure somebody does.
This is what could get large corporations (read: trend setters) interested in Linux servers... since Linux occupies mostly the small-business server market, it needs to expand to the large-business server market and workstation market... Many companies have been getting Linux workstation projects up and running, but large-business server farms/clusters are definitely one of Linux's weak points right now.
(just had to get 2nd post ;-)
if databases are made copyrightable, there's a good chance that copyrighted database software for linux will produce databases that are copyright, limiting how they can be used... this is a bad thing!
Hey, maybe the slashdot crew should be nominated.... after all, they're about the most crucial part of the linux news world... and as everyone knows, news is important. Usually. ;-)
10AM on a saturday morning and two comments posted already!?!?! ;-)
They're not bots either... either we have two people who were forced to go to bed early by their parents, or they're in a different time zone.
Or maybe they're insane enough to go to bed before 4am
Come to Delaware!!!! PLEASE!!!! I'LL PAY YOU!!!!
Aahhhh... American Pie quotes ;-)
Someone needs to mirror the panix site - e-mail the guy and snag a copy of his perl script etc....
Anyways, here's my contribution to the humor:
Original:
And one time, at band camp, I stuck a flute up my p*ssy.
French:
And once, to the camp of tape, I stuck a groove to the top of my cat.
German:
And once, at tape stocks, I adhered a flute up mean Pussy.
Italian:
And once, to the encampment of wrap, I have attacked one rabbet on mine pussy.
Portuguese:
E a time, in the encampment of the band, I pierced a flute above of my pussy.
Spanish:
And once, in the field of the bandage, I stuck one flauta upon my kitten.
Notes: The portuguese "E a time" should be "And one time" - dunno why it can't translate the portuguese word for and.... weird....
Some other words didn't work too well - these are more obvious though. (Like "flauta")
I got another amazing idea!
("OH NO, Matt, Not another one of your amazing ideas again!?!?!" "Shut yer trap.")
Obviously, e-mail and newsgroups would work fine, but the other sorts of requests, like file requests and data-processing requests, would be impossible to negotiate - you couldnt tell if the commands you sent were correct or not...
Fortunately, there's a solution.
Mirroring.
It's not necessary to mirror everything, but you can make web surfing possible by mirroring their directory tree for the documents, and cgi-bins involved with site-searches; for other cgi-bins [data processing and file-requests], an interface would check for syntax in the data processing, then ship it out and tell the user approximately when they can expect their results back (a local program would save the incoming results and then provide a web interface to retrieving them) - file requests would be similar, there would be an ls -lR stored locally, and it would be checked to see if the file was there and if permissions allowed access by that user. (A crontab entry could mirror the file at appropriate intervals.) If the file was, data about its size, date, etc. would be given to the user, who would approve or disapprove the request - if the request was approved, then the file would be ordered to be shipped to one of many "Cache servers", which would have many very large disk storage media. The user could pick up the file later, and if another user requested the same file, they could be redirected to the cache server for immediate access. If the files remained unused on the cache server for a certain amount of time, they would be deleted to make room for other files being ordered.
The only problem with this system - time and money. Time can be allowed though, since it would be pointless to have Interplanetary Internet implemented long before there was much up there to talk to. Money will hopefully be donated by generous research corporations (probably ones with orbiting satellites.)
They seem to have forgotten that UDP is a non-ACK'd unverified non-sequential protocol - you send the packets out and _hope_ they get there. Assuming they can make the networks reliable enough, UDP would be perfect - just send out commands split up into packets, with each packet tagged so they can be reassembled in the correct order, and be sure to send the packets in duplicate, from two different transceivers - then the request can be processed and the data sent back. Obviously, this would not work for things such as web browsing, FTP, and telnet - derivatives of TFTP and finger would be promising though.
aww man, i took too long making up that stupid rhyme, someone stole my spot!
*sobs*