I thought the current theory was that Gondwana the resulting scar of whatever hit the earth forming the moon such a very long time ago. How many generations super continents where there?
I was going to point out the Usenet Top 1000 Sites now has 3414 sites listed. Then I remember it used to be in the 10,000 range and noticed my server is at 853... hmmm. I guess these sites are going away. My server tends to provide feeds for text only groups to sites that want small feeds.
You forgot about the renewed trend in reusing other peoples code even when it complicates things. Just grab something off the web and link it in and hope it works. When you had a real sysadmin running the servers, the developers would write the few lines of code and not download a package and its dependencies just to avoid some work. It seems like all our new development seems to be mostly bogged down in getting everything that we didn't write to work with everything else we didn't write.
Many machines get many names. Ours all get a wsXX and their IP is based on that and they are supposed to be unique. Each machine will also have a name based on what it is. A Sun V100 may be called v100-5 and a router my be c3640-1. When a service gets added to a host, it gets a new "service IP" assigned and the application gets bound to that. Since most things are in secured zones which can't talk to each other even for DNS, we tend to refer to machines by their sub addresses like "What application is next to get moved off of 1.90?". Where 1.90 means 1 is on a DMZ like zone of low trust stuff. It has a name of ws90 (and a historic ss90 name since its a server and not a workstation) and its hostname is ss1000-1 since its first sparcserver 1000. It has a a few web servers running on 1.230 to 1.23x which are all service addresses. This worked ok until we got a new firewall that allows us to but each server on its own port which has its own zone but at the cost of at least a/30 so we decided to give each zone a 192.168.(site_number*100+port+10).ws_number so now the thing will be 192.168.15.90 or some such thing.
Each server gets 3 lables. One for is WS name (like ws90), one for its hardware based name (like ss1000-1), and one for what its doing (like vpn tunnel)
Its tricky to come up with a naming convention that will work today and in the future and won't be too hard to understand by new people. Consistency helps. We number things from left to right and top to bottom (why are rack labels from the bottom up?) and if we try to keep the servers sorted in the rack by type so x2100-1 is above x2100-3. We have found that helps in locating the proper servers in the racks.
If you want a cute name for the box, edit your own hosts file.
Why would they keep it reliably? The google model was based on "stuff breaks, it doesn't hurt our results much and we start over every month" There was wisdom to that (when it happened)
Go look at a list of top 100 programers and see how many are physicists. If you remove the honorary CS degrees from the list you'll see that most of the influential Comp Sci people had no formal training in the field at all.
I already block info and mobi but blacklisting will get out of hand. Someone needs to come up with a whitelist zone records for country codes and sane TLDs and a nice simple HOWTO doc to set it up.
A few years ago I started looking into CFL and their savings. It turns out that all the facts on the net are just copied form each other and the origin of the numbers seem to be completely made up and treated as gospel. You get things like lumens per watt but I can't work out how you measure most bulbs output in lumens without making huge assumptions. The most interesting thing is the tripe that is being spread around has made it back to the manufactures and thanks to levels of outsourced productions, no one seems to know anything for sure.
They changed the rules in Australia about selling domains and its going to have a very nasty consequence. We are already talking to several member of Parliament about a new law that gives control of.au over to Ip Australia which is the Aussie Trademark Office. Once that law gets passed, the aunic is out of business and only because they upset enough geeks who are determined not to have the.com.au end up with the same name space pollution as the.com has. In the end, their greed will be their undoing.
I suspect I'll still be able to read nearly every type of media I've got now in 20 years except the 9 track tape. There are programs now that fake being a computer cassette recorder and LPs are outselling CDs in some markets. There are programs that will use a modern scanner to read punch cards and punched tape. With the exception of the tapes and punch cards, I can still buy new equipment that will read all the formats I have used over the past quarter century and the 1950's computer in the museum over the road's data is still readable just not as quickly as it once was.
Hard drives today use the same power connectors that the 8 inch floppy drives used and the holes in a 3.5" drive allow them to be mounted in the same place as an 8 inch disk. You can hook an 8 inch floppy up to any modern PC that still has a floppy drive cable but you'll need and edge card connector cable. I can still read my SASI (pre SCSI from the early 80s) disks because they supported some SCSI commands. All I need is a power supply that can provide lots of amps and a 50 pin to 68 pin adapter and I can plug it into a new computer I got just a few months ago.
I don't think CDs/DVDs are going away either. All new drives will read them since its trivial to read them with any laser that will read the 50 gig discs or the 20 terra discs next decade. The reason cassettes and LP and 8 track went away was the inconvenience combined with their physical size. Making a CD smaller doesn't seem to have much benefit and stores would hate selling DVD's in smaller packages than they now are since their losses would go up. The original double high cd box was designed to make them harder to steal.
The 44 being the same as the UK's dialling code appears to be an accident. here is a list. If anyone is playing with barcodes, MS Word's envelope feature can create them and there is a macro that you can feed arbitrary data.
US Zip codes were originally 5 digits and each post office was assigned one or two. Latter they added Zip +4 which gives a 9 digit zip code and the bar coded zip codes are 11 digits which are unique to the building in most cases. The 5 digits are now mostly used for routing information and the +4 is used for local sorting and delivery. If you check any mail you get from the US in the UK, you will find its been barcoded with the UK's zip code of 00144. I got a letter sent from the US with just my house number, part of the street name, local post code and a barcode that says "put it on the next plane to Oz" and it only had domestic 1st class postage.
I don't care if its 1:1 in theory, check out the code and you'll see that reality says its 1:many. What I haven't found is if its many:many but I reason to expect it is.
What I want is a RAID card that I can plug in a bunch of SD cards in 2.5 or 3.5 drive format. I don't think it would be a problem to build a board that would hold 8 and be in the same form factor as a 2.5" disk. Since you can pick up 8 16 gig cards for about $500 now, I think the $900 for a 64 gig ssd is way out of line.
They all seem to work once or twice... try it 10 times (giving it enough time to rebuild the new disk) or try it with a disk where its confused or try it after a power down (simulate erplacing a drive after a major power problem). Then make sure to do a full fsck or chkdsk on the disk and then see if it works. I don't know about your device but most of the times I've tried this, I end up with a mess of bits scattered over disks after just a few swaps.
But the sprinkler pipe wasn't labeled on the dig plan was it? A solution to that problem is put some metal locater foil over the sprinkler pipe or just ignore the problem until it gets cut and go out and put a $2 joint over the two bits of pipe with the right glue. I'm guessing the leak is very close to where ground was cut.
Finding it when it breaks means hooking it up to a device that every installer should have that will say the break is N feet or meters away. TDR and OTDR is great for that.
It can do in the higher quality stuff too... I've got a new fiber connection to a ssg 140 and that has a wireless link to my house where I was using two mac to torrent iso images. The poor firewall started getting over loaded at about 1000 connections and only 3 to 5 mb going in both directions.
Slashdot Mirror
I thought the current theory was that Gondwana the resulting scar of whatever hit the earth forming the moon such a very long time ago. How many generations super continents where there?
I was going to point out the Usenet Top 1000 Sites now has 3414 sites listed. Then I remember it used to be in the 10,000 range and noticed my server is at 853... hmmm.
I guess these sites are going away. My server tends to provide feeds for text only groups to sites that want small feeds.
You forgot about the renewed trend in reusing other peoples code even when it complicates things. Just grab something off the web and link it in and hope it works. When you had a real sysadmin running the servers, the developers would write the few lines of code and not download a package and its dependencies just to avoid some work. It seems like all our new development seems to be mostly bogged down in getting everything that we didn't write to work with everything else we didn't write.
Many machines get many names. Ours all get a wsXX and their IP is based on that and they are supposed to be unique. Each machine will also have a name based on what it is. A Sun V100 may be called v100-5 and a router my be c3640-1. When a service gets added to a host, it gets a new "service IP" assigned and the application gets bound to that. Since most things are in secured zones which can't talk to each other even for DNS, we tend to refer to machines by their sub addresses like "What application is next to get moved off of 1.90?". Where 1.90 means 1 is on a DMZ like zone of low trust stuff. It has a name of ws90 (and a historic ss90 name since its a server and not a workstation) and its hostname is ss1000-1 since its first sparcserver 1000. It has a a few web servers running on 1.230 to 1.23x which are all service addresses. This worked ok until we got a new firewall that allows us to but each server on its own port which has its own zone but at the cost of at least a /30 so we decided to give each zone a 192.168.(site_number*100+port+10).ws_number so now the thing will be 192.168.15.90 or some such thing.
Each server gets 3 lables. One for is WS name (like ws90), one for its hardware based name (like ss1000-1), and one for what its doing (like vpn tunnel)
Its tricky to come up with a naming convention that will work today and in the future and won't be too hard to understand by new people. Consistency helps. We number things from left to right and top to bottom (why are rack labels from the bottom up?) and if we try to keep the servers sorted in the rack by type so x2100-1 is above x2100-3. We have found that helps in locating the proper servers in the racks.
If you want a cute name for the box, edit your own hosts file.
Knuth, Ritchie, Joy, McKusick, Bostic, , Vixie, Cerf, Leffler, Fabry
for a start on the Unix side of things...
You have two options:
1) Pages that provides information
2) Fluff
99.9% of the sites that provide information are static text pages with a bit of html mark up and most of the rest is fluff.
Why would they keep it reliably? The google model was based on "stuff breaks, it doesn't hurt our results much and we start over every month"
There was wisdom to that (when it happened)
Go look at a list of top 100 programers and see how many are physicists. If you remove the honorary CS degrees from the list you'll see that most of the influential Comp Sci people had no formal training in the field at all.
I figure it gives the PC tech something else to do when there aren't any computers to fix.
I already block info and mobi but blacklisting will get out of hand.
Someone needs to come up with a whitelist zone records for country codes and sane TLDs
and a nice simple HOWTO doc to set it up.
A few years ago I started looking into CFL and their savings. It turns out that all the facts on the net are just copied form each other and the origin of the numbers seem to be completely made up and treated as gospel. You get things like lumens per watt but I can't work out how you measure most bulbs output in lumens without making huge assumptions. The most interesting thing is the tripe that is being spread around has made it back to the manufactures and thanks to levels of outsourced productions, no one seems to know anything for sure.
They changed the rules in Australia about selling domains and its going to have a very nasty consequence. We are already talking to several member of Parliament about a new law that gives control of .au over to Ip Australia which is the Aussie Trademark Office. Once that law gets passed, the aunic is out of business and only because they upset enough geeks who are determined not to have the .com.au end up with the same name space pollution as the .com has. In the end, their greed will be their undoing.
It won't be automatically suspect here. It will get banned on my DNS just like .info and .mobi already are.
I suspect I'll still be able to read nearly every type of media I've got now in 20 years except the 9 track tape. There are programs now that fake being a computer cassette recorder and LPs are outselling CDs in some markets. There are programs that will use a modern scanner to read punch cards and punched tape. With the exception of the tapes and punch cards, I can still buy new equipment that will read all the formats I have used over the past quarter century and the 1950's computer in the museum over the road's data is still readable just not as quickly as it once was.
Hard drives today use the same power connectors that the 8 inch floppy drives used and the holes in a 3.5" drive allow them to be mounted in the same place as an 8 inch disk. You can hook an 8 inch floppy up to any modern PC that still has a floppy drive cable but you'll need and edge card connector cable. I can still read my SASI (pre SCSI from the early 80s) disks because they supported some SCSI commands. All I need is a power supply that can provide lots of amps and a 50 pin to 68 pin adapter and I can plug it into a new computer I got just a few months ago.
I don't think CDs/DVDs are going away either. All new drives will read them since its trivial to read them with any laser that will read the 50 gig discs or the 20 terra discs next decade. The reason cassettes and LP and 8 track went away was the inconvenience combined with their physical size. Making a CD smaller doesn't seem to have much benefit and stores would hate selling DVD's in smaller packages than they now are since their losses would go up. The original double high cd box was designed to make them harder to steal.
The 44 being the same as the UK's dialling code appears to be an accident. here is a list. If anyone is playing with barcodes, MS Word's envelope feature can create them and there is a macro that you can feed arbitrary data.
US Zip codes were originally 5 digits and each post office was assigned one or two. Latter they added Zip +4 which gives a 9 digit zip code and the bar coded zip codes are 11 digits which are unique to the building in most cases. The 5 digits are now mostly used for routing information and the +4 is used for local sorting and delivery. If you check any mail you get from the US in the UK, you will find its been barcoded with the UK's zip code of 00144. I got a letter sent from the US with just my house number, part of the street name, local post code and a barcode that says "put it on the next plane to Oz" and it only had domestic 1st class postage.
I don't care if its 1:1 in theory, check out the code and you'll see that reality says its 1:many. What I haven't found is if its many:many but I reason to expect it is.
For any given private key, there are several public keys.
RSA keys are not 1:1, they are 1:many, many:1 or maybe even many:many.
There is a demo program that does small (16 bit) keys here
What I want is a RAID card that I can plug in a bunch of SD cards in 2.5 or 3.5 drive format. I don't think it would be a problem to build a board that would hold 8 and be in the same form factor as a 2.5" disk. Since you can pick up 8 16 gig cards for about $500 now, I think the $900 for a 64 gig ssd is way out of line.
They all seem to work once or twice... try it 10 times (giving it enough time to rebuild the new disk) or try it with a disk where its confused or try it after a power down (simulate erplacing a drive after a major power problem). Then make sure to do a full fsck or chkdsk on the disk and then see if it works. I don't know about your device but most of the times I've tried this, I end up with a mess of bits scattered over disks after just a few swaps.
But the sprinkler pipe wasn't labeled on the dig plan was it? A solution to that problem is put some metal locater foil over the sprinkler pipe or just ignore the problem until it gets cut and go out and put a $2 joint over the two bits of pipe with the right glue. I'm guessing the leak is very close to where ground was cut.
Finding it when it breaks means hooking it up to a device that every installer should have that will say the break is N feet or meters away.
TDR and OTDR is great for that.
It can do in the higher quality stuff too... I've got a new fiber connection to a ssg 140 and that has a wireless link to my house where I was using two mac to torrent iso images. The poor firewall started getting over loaded at about 1000 connections and only 3 to 5 mb going in both directions.
I know RAID is supposed to work that way but I have never seen it work that way in the real world.