Perhaps you meant te Planetary Image Atlas. It has raw and processed images from many planetary missions. They have some neat utils to search and find the data you want too.
Actually it was Malin Space Science Systems(MSSS), and not JPL that released the images. This is significant because MSSS has been holding the data from everyone (including NASA/JPL) for a year before releasing it. It is great to see MSSS take a more open and timely approach to mars data.
It is sad however that a private contractor like MSSS could control the release of this data in the first place. All scientific data from planetary missions should be immediately released on the Internet.
Most likely for out-of-band management network. Possibly Exodous's, probably used for management(duh) and backups. The system should also have another set of nic's for the owners out-of-band management network, connected via private line (or dialup) to their office/noc/whatever.
Do you really need 1 Gig of ram on the web servers? Wouldn't the extra memory be better used on the DB server? You're probably not using more than 150MB for the httpd's.
That is because it is difficult/tedious to write code that handles multiple db writes, especially to multiple servers. Expecially with MySQL where you would have to explicitly verify all writes to make sure everything is in sync. This will hopefully be fixed when replication is added to MySQL.
I'm a very happy Dixex customer. I only wish that they would private peer with @home so I don't have to bounce through a box on another backbone to get to the Dixeg boxen while at home.
They do take security very seriously. Especially physical security. Their Beltsville facility was the only time I couldn't get to see core routers while on private tour. Every other company I visited showed me the goods. They did show me the hosting rooms, but you had to stay within the yellow tape:)
Are you sure you diddn't have the thing misconfigured? They have a pretty bizarre concept of what a port is. I tested a 180e a few months ago. It took a bit more configuration than I would have expected, but then It ran perfectly on the live site I tested it on. I haven't run one over a couple megabits/s so I don't know how it does under heavy load.
It's not necessarally that it uses perl (though it would likely be faster in C), but that it uses sloppy perl. Of course alot of perl code is sloppy, inefficient and unmaintainable.
I don't know why people say that C is hard and has a slow to develop in. C is an easy language to code in if your mind is in the right mode. Just take a millisecond on each statement to think about what you just did with that pointer, and remember to bounds-limit everything.
For an example of a C/MySQL cgi that can stand the slashdot effect: Brickshelf.com Gallery
Shut down slackware? You are kidding right? Slackware was around before just about any distro except for maybe Yggdrasil (remember that?) Slackware is a simple, clean, elegant distro without the bloat piled in to Red Hat.
I use Red Hat *and* slackware, for different purposes. But then again I use NetBSD, FreeBSD, Solaris, AIX, and IRIX, for different purposes too :
Red Hat: Desktop workstation
Slackware: Personal Dial-in server and firewall (old 486-50 pushed to 60)
NetBSD: on some old sun boxen
FreeBSD: High load web server (http://www.brickshelf.com) Solaris: Sparc boxen (code dev/image processing) AIX: At work (only under duress) IRIX: Indy for S/PDIF input
See, there is room for at least those two Linux Distros, and many other OS's
Don't forget about the Craig Neidorf Search on January 18/19 1990. That too was a major event and the resultant trial a major defeat for the Secret Service.
Yes! In fact NETBEUI is more efficient than TCP/IP for DB connections (many set-up and tear down events which are expensive in TCP/IP, especially on NT). Some NT people doing this for DB back ends to web sites already.
The real answer is probably related to the rumor that NASA forgot to put heaters on the explosive bolts. This would have prevented the cruise stage from separating and the lander+DS2 probes would have burned up in the atmosphere.
Cm'on, even if the lander rolled down a ravine, the DS2 probes would still work! After all, they were designed and tested to CRASH into the surface.
I have to disagree about Digex. I have used Digex as a backbone provider on and off since 1995. I have been extremely impressed with their backbone performance and customer support. I always get notified of scheduled maintenance well in advance and they even call me if a line is down for more than 30 seconds.
I also had an episode where a new customer of ours moved their website to our facility and their ex-ISP was DOS'ing us in a lame attempt to show that we had poor connectivity. Digex got right on it and we caught them red handed.
My favorite thing about Digex is that their backbone speed/peering rocks! I'm in the NoVA area. I've also had very good luck with VERIO.
MTBF is indeed misleading because one of the factors that goes into it is "design life".
For example, if you have a hard drive with a MTBF of 150,000 hrs (== 17yrs) that does not mean that it will fail in 17 years, or that 150,000 of them would produce one failiure every hour.
It means that if you replace each drive before the end of it's design life (5yrs) you will have a failiure on average every 150,000 hrs.
If you use a device beyond it's design life it will almost certainly fail.
What has actually happened here is that all domains, even those registered by competing registrars are now visible in whois. if you use the -h option followed by the appropriate whois server you get the same details as before.
Of course this should all be integrated into one whois lookup but it's a good step in the right direction.
You can put away the guns now, no data has been hidden.
Anyone that's thinking of getting Mindstorms should try to get a 1.0 box if you can find one. The RCX in the new 1.5 boxes dosen't have an external power jack! That's a real bummer if you want to do something that uses alot of power, without having to change the batteries often. The 1.0 boxes with the 1.5 upgrade stickers have RCX's with power jacks.
Since 1995, Virginia, or more specifically Tysons Corner has been the "center" of the internet, topologically speaking. The MAE East public peering point has and still is the most populated peering point. At one time over 60% of all internet traffic, and some 80% of international traffic passed through MAE East. Recently however the proliferation of private peering has significantly reduced those numbers (of course a significant ammount of private peering occurs between backbone routers at the MAE East location(s).
As for where the Internet was born, The Pentagon in Arlington, VA is technically the correct location, while the Implementation began in Cambridge, MA.
As for Sillicon Valley? Well they were the capital of the previous revolution, the Personal Computer. They might even say they are the center of Net VC, and Net Companies, but not the Internet itself.
Has anyone noticed that it shows you the lines that your keywords are actually in instead of just the first few lines of the page? Thats incredibly useful. Also, looking at the # of times Ph.D appears in their employment page, I'd say these guys are a bunch of acedemics. What normal company would require a Ph.D for any position?
Just about any box with 128+MB of ram and just about any unix w/apache and a sane config can survive the/. effect. The real limitation is bandwidth. a T1 is not sufficient. I'm assuming you will have lots of graphics (an art site), and you would pass 3G in less than 12 hours. Also, if bandwidth is limiting transferrs then each transfer takes longer and you run up to max httpd's sooner. In fact a 486 w/32MB ram and an ide drive would probably do fine on an OC3, but on a T1 you can forget it.
Slashdot Mirror
Perhaps you meant te Planetary Image Atlas. It has raw and processed images from many planetary missions. They have some neat utils to search and find the data you want too.
It is sad however that a private contractor like MSSS could control the release of this data in the first place. All scientific data from planetary missions should be immediately released on the Internet.
Oops, sorry. I forgot about mod_perl. :)
That's one nice thing about coding in C or
Java Servlets, no httpd bloat, but that's another topic
Most likely for out-of-band management network.
Possibly Exodous's, probably used for management(duh) and backups. The system should also have another set of nic's for the owners out-of-band management network, connected via private line (or dialup) to their office/noc/whatever.
Do you really need 1 Gig of ram on the web servers? Wouldn't the extra memory be better
used on the DB server? You're probably not using
more than 150MB for the httpd's.
That is because it is difficult/tedious to write code that handles multiple db writes, especially to multiple servers. Expecially with MySQL where you would have to explicitly verify all writes to make sure everything is in sync. This will hopefully be fixed when replication is added to MySQL.
that they would private peer with @home so I don't have to bounce through a box on another backbone to get to the Dixeg boxen while at home.
They do take security very seriously. Especially physical security. Their Beltsville facility was the only time I couldn't get to see core routers while on private tour. Every other company I visited showed me the goods. They did show me
the hosting rooms, but you had to stay within the yellow tape
Are you sure you diddn't have the thing misconfigured? They have a pretty bizarre concept of what a port is. I tested a 180e a few months ago. It took a bit more configuration than I would have expected, but then It ran perfectly on the live site I tested it on. I haven't run one over a couple megabits/s so I don't know how it
does under heavy load.
it would likely be faster in C), but that it uses sloppy perl. Of course alot of perl code is sloppy, inefficient and unmaintainable.
I don't know why people say that C is hard and has a slow to develop in. C is an easy language to code in if your mind is in the right mode. Just take a millisecond on each statement to think about what you just did with that pointer, and remember to bounds-limit everything.
For an example of a C/MySQL cgi that can stand the slashdot effect:
Brickshelf.com Gallery
Slackware was around before just about any distro
except for maybe Yggdrasil (remember
that?) Slackware is a simple, clean, elegant
distro without the bloat piled in to Red Hat.
I use Red Hat *and* slackware,
for different purposes. But then again I use
NetBSD, FreeBSD, Solaris, AIX, and IRIX, for
different purposes too :
Red Hat: Desktop workstation
Slackware: Personal Dial-in server and firewall (old 486-50 pushed to 60)
NetBSD: on some old sun boxen
FreeBSD: High load web server (http://www.brickshelf.com)
Solaris: Sparc boxen (code dev/image processing)
AIX: At work (only under duress)
IRIX: Indy for S/PDIF input
See, there is room for at least those two Linux
Distros, and many other OS's
Don't forget about the Craig Neidorf Search
on January 18/19 1990. That too was a major
event and the resultant trial a major defeat for the Secret Service.
Yes! In fact NETBEUI is more efficient than TCP/IP for DB connections (many set-up and tear down events which are expensive in TCP/IP, especially on NT). Some NT people doing this for DB back ends to web sites already.
Here's the press release from M$ itself:
Click Here
This story is just CYA BS.
The real answer is probably related to the rumor that NASA forgot to put heaters on the explosive bolts. This would have prevented the cruise stage from separating and the lander+DS2 probes would have burned up in the atmosphere.
Cm'on, even if the lander rolled down a ravine, the DS2 probes would still work! After all, they were designed and tested to CRASH into the surface.
I have to disagree about Digex. I have used Digex as a backbone provider on and off since 1995. I have been extremely impressed with their backbone performance and customer support. I always get notified of scheduled maintenance well in advance and they even call me if a line is down for more than 30 seconds.
I also had an episode where a new customer of ours moved their website to our facility and their ex-ISP was DOS'ing us in a lame attempt to show that we had poor connectivity. Digex got right on it and we caught them red handed.
My favorite thing about Digex is that their backbone speed/peering rocks! I'm in the NoVA area. I've also had very good luck with VERIO.
MTBF is indeed misleading because one of the
factors that goes into it is "design life".
For example, if you have a hard drive with
a MTBF of 150,000 hrs (== 17yrs) that does
not mean that it will fail in 17 years, or
that 150,000 of them would produce one failiure
every hour.
It means that if you replace each drive before
the end of it's design life (5yrs) you will
have a failiure on average every 150,000 hrs.
If you use a device beyond it's design life it
will almost certainly fail.
domains, even those registered by competing
registrars are now visible in whois. if you use
the -h option followed by the appropriate
whois server you get the same details as before.
Of course this should all be integrated into one
whois lookup but it's a good step in the right
direction.
You can put away the guns now, no data has been
hidden.
(RCX is the programable brick)
Since 1995, Virginia, or more specifically Tysons Corner has been the "center" of the internet, topologically speaking. The MAE East public peering point has and still is the most populated peering point. At one time over 60% of
all internet traffic, and some 80% of international traffic passed through MAE East.
Recently however the proliferation of private peering has significantly reduced those
numbers (of course a significant ammount of private peering occurs between backbone routers at
the MAE East location(s).
As for where the Internet was born, The Pentagon in Arlington, VA is technically the correct location, while the Implementation began in Cambridge, MA.
As for Sillicon Valley? Well they were the capital of the previous revolution,
the Personal Computer. They might even say they are the center of Net VC, and Net Companies, but
not the Internet itself.
Has anyone noticed that it shows you the lines that your keywords are actually in instead of just the first few lines of the page? Thats incredibly useful.
Also, looking at the # of times Ph.D appears in their employment page, I'd say these guys are a bunch of acedemics. What normal company would require a Ph.D for any position?
Just about any box with 128+MB of ram and just /. effect. The real limitation is
about any unix w/apache and a sane config can survive the
bandwidth. a T1 is not sufficient. I'm assuming
you will have lots of graphics (an art site), and you would pass 3G in less than 12 hours. Also, if bandwidth is limiting transferrs then each transfer takes longer and you run up to max httpd's sooner. In fact a 486 w/32MB ram and an ide drive would probably do fine on an OC3, but on a T1 you can forget it.
which is a derivation of the acronym fubar
which originated in WWI or WWII.
The real question is, when was the foobar derivative adopted by programmers.