The TSA WILL bust any lock that they don't have the key for (there is one out there with a TSA skeleton key) and they will most likely damage your luggage and contents in the process. Having a sturdy lock on your luggage will also likely get you pulled aside for a strip search, especially if coming from the UK. My advice is to be a good little cattle and blend into the background.
They also may be using intellectual property from outside entities under license that they are not allowed to reveal. I know that this is the number one issue keeping many legacy applications from being open sourced.
With PAE you could already give each virtual server 4GB to play with up to 64GB total with Windows 2003 Enterprise or 128GB with Datacenter. Linux 2.6 allows up to 64GB through the HIGHMEM_64G flag, all on standard x86 of P2 or later vintage (PPro had rudimentry PAE but implementing it was very hackish)
Disaster Recovery and test environments are the two biggest reason's I can see for using virtualization. Having the ability to pick up your system and plop it on any old box makes things so much easier. In theory HAL's should have made this possible years ago but they never really lived up to their promise. As to virtualization making management easier, bullocks. Some of the tools bundled with good virtualization products like ESX might make management somewhat easier, but you still need additional good tools to make management bareable for large numbers of server/virtual servers.
Your post brings up a good point, I would think things like cutthrough vs store and forward switching and various routing strategies and queues would disrupt intricate timing so as to make this vector useless for all but the most pristine of local LAN segments.
I think this is only true after a certain dilution point. For instance this was one of the things that prompted Google to go public, they were going to be forced to file SEC filings anyways because the dilution of ownership has reached some threshold.
the odds of 3 drives failing at once are astronomical.
No, they aren't. Just have an array running for a year or two and bring it down for maintenance, your chances of multiple drive failures are VERY good. Of course that happens even with SCSI drives, but it even more underscores the need for a premium part. Btw I just live through a scare this weekend. We lost one drive after powering up one of our main DB servers, then lost a second about 10 minutes later, luckily the 16 drive array was setup as RAID6 instead of RAID5, the first good decision we have found from the previous staff =)
There's this thing called batter backed write cache, you might want to look into it. Without it you either have horrible write performance or a serious consistancy problem.
Because suddenly having large numbers of military personell and hardware start entering a formerly abandoned mine stirs up all sorts of questions even from normal people whereas expanding operations at an existing site only tends to arouse suspicion is a keen observer working for a strong opponent. Oh and you can piggyback on existing infrastructure and expenditures to make your black budget dollars stretch farther =)
Why do people bring up X11 and VNC, both protocols suck. If you want a good protocol try RDP, ICA, or NX. OpenGL is a good protocol but wouldn't be good for a display adapter unless you wanted to tie the display to a particular video board built in, GL takes a lot of processing.
Looks awsome for the remote office over WAN scenario where the office isn't big enough to justify a server but where bandwidth is so limited that pushing patches can be a pain, just another way where technology is making my life easier =)
Yep, one former employer (a large multinational tech company) put the cost of cutting a PO at around $125, which is why anything under a couple grand did not require a PO but could simply be expensed with manager aproval. A fee this small is just an annoyance in a corporate environment, it's too much hassle to get it approved so you'll likely just eat the cost and inflate expenses somewhere else. Of course in a corp environment you probably already have MSDN and so won't be paying any additional charges anyways...
I gave myself a half day off. I worked till midnight last night with Veritas support including a handoff to Australia and once the users restore was complete this morning and I got through my short laundry list of todo's I headed home to be with the family. Best sysadmin day ever =)
Syncronous DR copy of your SAN is about the only thing I can think of for that much bandwidth at the moment, but that might have something to do with the fact that I've been implementing a new SAN project the last two weeks =)
Yep, about 50% of the time that I had to work with MS or other major software vendors on escalated issues the sysinternals tools like filemon, process explorer et all came into play. The other 50% of the time it was domain specific tools like ADSIedit or vendor diagnostic logging. Considering the variety of problems I've had to troubleshoot that says volumes about Russiniovich and company. I choose to look on the bright side and hope that his great knowledge and understanding will go to good use improving the offerings from MS.
Yes, it provides room for an activly coding region to be unzipped and transcoded without neighboring active coding regions being activated or ever touched.
According to Schneier the State Department already plans (and has since sometime last year) to include a RF shield so the chip can only be read while the passport is open and they are encrypting the data on the RFID.
In fact doing so on Debian is easy. You just have to add "password required pam_cracklib.so retry=3 minlen=12 difok=3 lcredit=0 ucredit=1 dcredit=1 ocredit=2" or similar to the files in/etc/pam.d/
Slashdot Mirror
The TSA WILL bust any lock that they don't have the key for (there is one out there with a TSA skeleton key) and they will most likely damage your luggage and contents in the process. Having a sturdy lock on your luggage will also likely get you pulled aside for a strip search, especially if coming from the UK. My advice is to be a good little cattle and blend into the background.
That's not what this table from MS says along with several other references to PAE on Microsoft's site.
They also may be using intellectual property from outside entities under license that they are not allowed to reveal. I know that this is the number one issue keeping many legacy applications from being open sourced.
With PAE you could already give each virtual server 4GB to play with up to 64GB total with Windows 2003 Enterprise or 128GB with Datacenter. Linux 2.6 allows up to 64GB through the HIGHMEM_64G flag, all on standard x86 of P2 or later vintage (PPro had rudimentry PAE but implementing it was very hackish)
Disaster Recovery and test environments are the two biggest reason's I can see for using virtualization. Having the ability to pick up your system and plop it on any old box makes things so much easier. In theory HAL's should have made this possible years ago but they never really lived up to their promise. As to virtualization making management easier, bullocks. Some of the tools bundled with good virtualization products like ESX might make management somewhat easier, but you still need additional good tools to make management bareable for large numbers of server/virtual servers.
When I read Manna I thought it was more a work of horror then sci-fi kind of like Event Horizon, now it's coming true, very scary indeed.
Your post brings up a good point, I would think things like cutthrough vs store and forward switching and various routing strategies and queues would disrupt intricate timing so as to make this vector useless for all but the most pristine of local LAN segments.
I think this is only true after a certain dilution point. For instance this was one of the things that prompted Google to go public, they were going to be forced to file SEC filings anyways because the dilution of ownership has reached some threshold.
haha, only problem is my Taurus with 185k miles on original spark plugs is the one doing the laughing =)
Older HP's of the non-SOHO variety go to one million pages on a regular basis, 40k pages is just the first maintenance interval =)
You'll spend as much on extra power in a couple years as the netgear box and have lower reliability.
the odds of 3 drives failing at once are astronomical.
No, they aren't. Just have an array running for a year or two and bring it down for maintenance, your chances of multiple drive failures are VERY good. Of course that happens even with SCSI drives, but it even more underscores the need for a premium part. Btw I just live through a scare this weekend. We lost one drive after powering up one of our main DB servers, then lost a second about 10 minutes later, luckily the 16 drive array was setup as RAID6 instead of RAID5, the first good decision we have found from the previous staff =)
There's this thing called batter backed write cache, you might want to look into it. Without it you either have horrible write performance or a serious consistancy problem.
Because suddenly having large numbers of military personell and hardware start entering a formerly abandoned mine stirs up all sorts of questions even from normal people whereas expanding operations at an existing site only tends to arouse suspicion is a keen observer working for a strong opponent. Oh and you can piggyback on existing infrastructure and expenditures to make your black budget dollars stretch farther =)
Why do people bring up X11 and VNC, both protocols suck. If you want a good protocol try RDP, ICA, or NX. OpenGL is a good protocol but wouldn't be good for a display adapter unless you wanted to tie the display to a particular video board built in, GL takes a lot of processing.
Looks awsome for the remote office over WAN scenario where the office isn't big enough to justify a server but where bandwidth is so limited that pushing patches can be a pain, just another way where technology is making my life easier =)
Yep, one former employer (a large multinational tech company) put the cost of cutting a PO at around $125, which is why anything under a couple grand did not require a PO but could simply be expensed with manager aproval. A fee this small is just an annoyance in a corporate environment, it's too much hassle to get it approved so you'll likely just eat the cost and inflate expenses somewhere else. Of course in a corp environment you probably already have MSDN and so won't be paying any additional charges anyways...
I gave myself a half day off. I worked till midnight last night with Veritas support including a handoff to Australia and once the users restore was complete this morning and I got through my short laundry list of todo's I headed home to be with the family. Best sysadmin day ever =)
Syncronous DR copy of your SAN is about the only thing I can think of for that much bandwidth at the moment, but that might have something to do with the fact that I've been implementing a new SAN project the last two weeks =)
Yep, about 50% of the time that I had to work with MS or other major software vendors on escalated issues the sysinternals tools like filemon, process explorer et all came into play. The other 50% of the time it was domain specific tools like ADSIedit or vendor diagnostic logging. Considering the variety of problems I've had to troubleshoot that says volumes about Russiniovich and company. I choose to look on the bright side and hope that his great knowledge and understanding will go to good use improving the offerings from MS.
Baseline security analyzer is not needed or support on IIS 6.0 on 2003.
Then they switched, it used to be Cisco/Aironet =)
Yes, it provides room for an activly coding region to be unzipped and transcoded without neighboring active coding regions being activated or ever touched.
According to Schneier the State Department already plans (and has since sometime last year) to include a RF shield so the chip can only be read while the passport is open and they are encrypting the data on the RFID.
In fact doing so on Debian is easy. You just have to add "password required pam_cracklib.so retry=3 minlen=12 difok=3 lcredit=0 ucredit=1 dcredit=1 ocredit=2" or similar to the files in /etc/pam.d/
For more info on pam_cracklib see this site.