Work has begun to switch the telescope to the backup channel. It is a complicated process; the backup channels on the various modules that must be switched over have not been turned on since the late 1980s or early 1990, right before Hubble was launched. The Hubble team hopes to complete the job by the end of the week.
I would get in so much trouble if I don't regularly test my backup and failover systems...
In addition to proving China's ability to maneuver in space, the spacewalk showed that China can produce reliable and safe space equipment. During his space venture, Zhai wore a new Chinese-built spacesuit, dubbed Feitian (Chinese for "fly the sky").
The suit, which reportedly cost 30 million yuan (about $4.4 million), did its job protecting Zhai from the harsh temperatures and radiation of space. It has 10 layers of insulation, weighs about 265 pounds (120 kg), and takes up to 15 hours to assemble and put on, the official Chinese news agency Xinhua reported.
15 hours to assemble and put on, let's hope they don't need it in case of an emergency!
In my weblog I've written an article about Big ISP, little ISP, local internet exchanges about what little ISPs can gain if transit ISPs join the local internet exchanges. Short version: the transmit ISPs can end up delivering your traffic much faster than what you pay for, but (of course) it is possible for the transmit ISPs to overcome this "problem" if they design their network properly.
CVS is (was) what the central repository uses to store the software.
Perforce is a central repository for internal development. That way the limitations of CVS for this part of the job don't limit the developers. But Perforce is commercial software and you can't push it on to the community.
Subversion is a free software which has the capabilities which are set as a requirement for the FreeBSD project. It has some capabilities of Perforce, it has some capabilities of CVS and it can be integrated in the current distribution framework.
Oh, and it understood most of the FreeBSD CVS Repository:-)
Not only the IPv4 IP space is running on empty, at the last AusNOG conference (a must for everybody who is into internetworking in Australia) a talk was given about the similarities and differences in the allocation of AS numbers.
Where the IP space allocation graph shows an exponential line since 1990something, the AS number allocation graph shows a linear line.
The interesting thing is that somewhere in 2010/2011, when the IPv4 IP space is running out, also the double byte AS number allocation is running out. At around the same time!
So while the big world has to deal with the IPv6 (which by now should be common knowledge and practise), the ISP world has to deal with the four byte AS numbers.
That last part isn't 100% true: If you have a double byte AS number and your BGP speaker doesn't understand four byte ASN numbers, you will see some strange things in your BGP table but everything will keep working. On the other hand, if you have been handed out a four byte AS number, you'd better make sure you got a speaker which supports four byte AS numbers:-)
Not only the IPv4 IP space is running on empty, at the last AusNOG conference (a must for everybody who is into internetworking) a talk was given about the similarities and differences in the allocation of AS numbers.
Where the IP space allocation graph shows an exponential line since 1990something, the AS number allocation graph shows a linear line.
The interesting thing is that somewhere in 2010/2011, when the IPv4 IP space is running out, also the double byte AS number allocation is running out. At around the same time!
So while the big world has to deal with the IPv6 (which by now should be common knowledge and practise), the ISP world has to deal with the four byte AS numbers.
That last part isn't 100% true: If you have a double byte AS number and your BGP speaker doesn't understand four byte ASN numbers, you will see some strange things in your BGP table but everything will keep working. On the other hand, if you have been handed out a four byte AS number, you'd better make sure you got a speaker which supports four byte AS numbers:-)
The LAN as we knew it, the one ethernet cable going through all rooms and being looped on the wall with a small jumper, is already dead for a long time.
The LAN as we know it, one central switch with a lot of ethernet cables getting out to individual ports in rooms, has been here for ages.
What didn't go away was the local addressing methods for sending data to all hosts (broadcast) and interaction with higher level protocols (ARP for determining the IP address).
The LAN as we are going to know it, a bunch of intercepted central-and-not-so-central switches which put you in the right (V)LAN when you plug in your computer to a random port connected to it, is here also if your organisation requires it, but for smaller organisations this is not really necessary:
and predicts that all machines will be individually connected to one huge WAN at gigabit speeds
You need a gigabit WAN for that to work, not all smaller organisations have the need for this. But yes I have rolled it out for two customers.
Or maybe the base system should just not come with an MTA. Keep that stuff in ports where it belongs.
You need something to deliver your daily/weekly/monthly run logs, cron output, alerts etc to the right person.
But as you know, installing GREEN!^Wpostfix from the ports collection is hardly rocket science if you take all the default settings, plus that it can be updated without having to worry that an system upgrade will put everything back to an ancient version.
Does anybody know of movies or pictures of rockets being hit by lightning? (Must be terrifying for the people working on it, knowing it can kind of ruin their toy...)
As the person who did the latest timzeone updates to RELENG_5, RELENG_6 and HEAD (but not to the security-only branches RELENG_5_5 and RELENG_6_2) I say: They're right. As the person who maintains the misc/zoneinfo port I say: They're right.
STAT(2) FreeBSD System Calls Manual STAT(2) [...] The time-related fields of struct stat are as follows: [...] st_birthtime Time when the inode was created.
365Main sales people talk about how the datacenter could remain self-sufficient if a dirty-bomb exploded in the neighborhood--- meaning no fuel or water trucks for days, few staff may enter or leave the facility, etc.
So euhm... The world is damaged beyond control, humankind is doomed to relive the dark ages, but we're still able to serve webpages (if somebody would want them).
Sounds like the "For your convinience, coffee and cookies will be served" scene in the HHGTTG trilogy.
Honestly, the Wikipedia article gives a better background and has more information about related technologies (laserdisc for example).
Also, the famous Why has the compact disc 74 minutes of playtime is explained there:
According to a Sunday Tribune interview [1] the story is slightly more involved. At that time (1979) Philips owned Polygram, one of the world's largest distributors of music. Polygram had set up a large experimental CD plant in Hanover, Germany, which could produce huge amounts of CDs having, of course, a diameter of 115 mm. Sony did not yet have such a facility. If Sony had agreed on the 115 mm disc, Philips would have had a significant competitive edge in the market. Sony was aware of that, did not like it, and something had to be done. The long-playing time of Beethoven's Ninth imposed by Ohga was used to push Philips to accept 120 mm, so that Philips' Polygram lost its edge on disc fabrication.
Every three months is a good interval, because it's not you who is incompetent with this, it's all your neighbours who have no clue about this. On our wireless floors (luckely only three) we have had to modify channels twice in the last two years because of neighbours being stupid.
Slashdot Mirror
Work has begun to switch the telescope to the backup channel. It is a complicated process; the backup channels on the various modules that must be switched over have not been turned on since the late 1980s or early 1990, right before Hubble was launched. The Hubble team hopes to complete the job by the end of the week.
I would get in so much trouble if I don't regularly test my backup and failover systems...
In addition to proving China's ability to maneuver in space, the spacewalk showed that China can produce reliable and safe space equipment. During his space venture, Zhai wore a new Chinese-built spacesuit, dubbed Feitian (Chinese for "fly the sky").
The suit, which reportedly cost 30 million yuan (about $4.4 million), did its job protecting Zhai from the harsh temperatures and radiation of space. It has 10 layers of insulation, weighs about 265 pounds (120 kg), and takes up to 15 hours to assemble and put on, the official Chinese news agency Xinhua reported.
15 hours to assemble and put on, let's hope they don't need it in case of an emergency!
In my weblog I've written an article about Big ISP, little ISP, local internet exchanges about what little ISPs can gain if transit ISPs join the local internet exchanges. Short version: the transmit ISPs can end up delivering your traffic much faster than what you pay for, but (of course) it is possible for the transmit ISPs to overcome this "problem" if they design their network properly.
I feel a bit lucky because I never trust my ISP's name servers. I knew this day would come. If possible, I always use the OpenDNS servers.
If you were really worried about it you would run your own resolving-server on your machines.
but most of them primarily help people waste time online (blogger, youtube, orkut, etc)
No, these are things to sell eyeballs for advertisers. That's what Google is about, making money with selling ads around easy to use and "fun" tools.
portsnap *fetches* the whole tree but it can extract parts of it.
There are different tools for different purposes:
:-)
CVS is (was) what the central repository uses to store the software.
Perforce is a central repository for internal development. That way the limitations of CVS for this part of the job don't limit the developers.
But Perforce is commercial software and you can't push it on to the community.
Subversion is a free software which has the capabilities which are set as a requirement for the FreeBSD project. It has some capabilities of Perforce, it has some capabilities of CVS and it can be integrated in the current distribution framework.
Oh, and it understood most of the FreeBSD CVS Repository
If you are still using CVS, or CVSup, for updating your ports tree, I suggest you have a look at portsnap(8):
PORTSNAP(8) FreeBSD System Manager's Manual PORTSNAP(8)
NAME
portsnap -- fetch and extract compressed snapshots of the ports tree
Best colour combination in the whole wide world!
This is New South Wales, not federal Australia. Thanks for playing, come again!
Their phones didn't go beep when they lost connectivity to the central point, you only realized it when you tried to call with them.
Not only the IPv4 IP space is running on empty, at the last AusNOG conference (a must for everybody who is into internetworking in Australia) a talk was given about the similarities and differences in the allocation of AS numbers.
:-)
Where the IP space allocation graph shows an exponential line since 1990something, the AS number allocation graph shows a linear line.
The interesting thing is that somewhere in 2010/2011, when the IPv4 IP space is running out, also the double byte AS number allocation is running out. At around the same time!
So while the big world has to deal with the IPv6 (which by now should be common knowledge and practise), the ISP world has to deal with the four byte AS numbers.
That last part isn't 100% true: If you have a double byte AS number and your BGP speaker doesn't understand four byte ASN numbers, you will see some strange things in your BGP table but everything will keep working. On the other hand, if you have been handed out a four byte AS number, you'd better make sure you got a speaker which supports four byte AS numbers
Not only the IPv4 IP space is running on empty, at the last AusNOG conference (a must for everybody who is into internetworking) a talk was given about the similarities and differences in the allocation of AS numbers.
:-)
Where the IP space allocation graph shows an exponential line since 1990something, the AS number allocation graph shows a linear line.
The interesting thing is that somewhere in 2010/2011, when the IPv4 IP space is running out, also the double byte AS number allocation is running out. At around the same time!
So while the big world has to deal with the IPv6 (which by now should be common knowledge and practise), the ISP world has to deal with the four byte AS numbers.
That last part isn't 100% true: If you have a double byte AS number and your BGP speaker doesn't understand four byte ASN numbers, you will see some strange things in your BGP table but everything will keep working. On the other hand, if you have been handed out a four byte AS number, you'd better make sure you got a speaker which supports four byte AS numbers
The LAN as we knew it, the one ethernet cable going through all rooms and being looped on the wall with a small jumper, is already dead for a long time.
The LAN as we know it, one central switch with a lot of ethernet cables getting out to individual ports in rooms, has been here for ages.
What didn't go away was the local addressing methods for sending data to all hosts (broadcast) and interaction with higher level protocols (ARP for determining the IP address).
The LAN as we are going to know it, a bunch of intercepted central-and-not-so-central switches which put you in the right (V)LAN when you plug in your computer to a random port connected to it, is here also if your organisation requires it, but for smaller organisations this is not really necessary:
and predicts that all machines will be individually connected to one huge WAN at gigabit speeds
You need a gigabit WAN for that to work, not all smaller organisations have the need for this. But yes I have rolled it out for two customers.
1.5 million US dollars... That will be 75 Euros.
Or maybe the base system should just not come with an MTA. Keep that stuff in ports where it belongs.
You need something to deliver your daily/weekly/monthly run logs, cron output, alerts etc to the right person.
But as you know, installing GREEN!^Wpostfix from the ports collection is hardly rocket science if you take all the default settings, plus that it can be updated without having to worry that an system upgrade will put everything back to an ancient version.
Does anybody know of movies or pictures of rockets being hit by lightning?
(Must be terrifying for the people working on it, knowing it can kind of ruin their toy...)
See http://en.wikipedia.org/wiki/United_States_District_Court_for_the_Eastern_District_of_Texas and http://trolltracker.blogspot.com/2007/05/eastern-district-of-texas-january-2007.html for more details about why there.
Print some more money, or sell some bonds to the Chinese. It is not that they don't have you guys firmly by the balls already.
Yes this is a troll.
As the person who did the latest timzeone updates to RELENG_5, RELENG_6 and HEAD (but not to the security-only branches RELENG_5_5 and RELENG_6_2) I say: They're right.
As the person who maintains the misc/zoneinfo port I say: They're right.
It's kg, not Kg.
FreeBSD has this:
STAT(2) FreeBSD System Calls Manual STAT(2)
[...]
The time-related fields of struct stat are as follows:
[...]
st_birthtime Time when the inode was created.
365Main sales people talk about how the datacenter could remain self-sufficient if a dirty-bomb exploded in the neighborhood--- meaning no fuel or water trucks for days, few staff may enter or leave the facility, etc.
So euhm... The world is damaged beyond control, humankind is doomed to relive the dark ages, but we're still able to serve webpages (if somebody would want them).
Sounds like the "For your convinience, coffee and cookies will be served" scene in the HHGTTG trilogy.
Also, the famous Why has the compact disc 74 minutes of playtime is explained there:
Before rolling out a
Only before?
Every three months is a good interval, because it's not you who is incompetent with this, it's all your neighbours who have no clue about this. On our wireless floors (luckely only three) we have had to modify channels twice in the last two years because of neighbours being stupid.