Strip out the "some of these bad things would hurt Americans" and I'll argue that this is the single best reason I've ever heard of why we needed to flambé this guy. The only Americans threatened by Saddam where the ones enforcing the No-Fly-Zone, and any in Israel if he ever got his Scuds flying again.
We're not entirely sure. We are sure that the backplane on the original Powervault was faulty, which explained some mysterious Cluster behavior we'd been noticing. All the drives and the two chassis are now in the tip, since we don't want to trust anything to them. This is where it gets weird: the second Powervault was our nearline storage and catalog storage location for our Netbackup install. I've spent the last 4 weeks recovering catalog backups and doing tape inventory because that server wasn't so well backed up. Oops.
My recent favorite was a Dell Powervault that flaked out, finally dying. Putting the drives in another Powervault to recover them caused a number of other spare drives, plus this other Powervault, to also fail catastrophically. Thanks to one Powervault we lost 21 disks in the span of 12 hours.
Thankfully I made a network copy before I tried the disk to disk copy. You know your SCSI setup is aged when you can copy data via GbE faster than you can copy volume to volume on your controller.
HP and others are starting to get into remote desktops, where the computers are stored in a secured area, and keyboard mouse and video are projected over cat5 to a break-out box on the users desk. No physical access to the hardware anymore. It's only a matter of time where this becomes more prevalent. For an extra $150-200 per head, this isn't all that bad a cost in the right environment. You could use Belkin KVM extenders today to perform the same task.
I run a T41 at 1.8ghz, and I'll tell you, it can be a right dog. With SpeedSwitchXP, I can get some decent performance instead of XP running it at 667 mhz, but it chews through my 6 cell battery in less than two hours if I run it in high performance. At dynamic switching I can get three hours, maybe out of it (but the battery is older, I'll concede). And it's hot hot hot, even at 667 mhz. I'm not too happy to hold that on my lap. I turn to my six year old Omnibook 6000 running at 600mhz before I take out the T41. If you want 8 hours of life out of any Thinkpad you need a 9 - 12 cell battery. Even that would be pushing it.
Which is sad, because when the product was Interix way back in the day, it was actually pretty reliable, although it's always been troublesome to map the permission model/sids.
Hummingbird's product is the same way. It was good back when it was Beame and Whiteside making it, but suck has started creeping into it for years.
Somewhere I still have a box of Chameleon32 floppies... I'm such a pack rat.
I use LVM on my RAID1 mirrors all the time. I've NEVER had a problem with disk failure borking my system. It's something I learned from AIX 4.0 back in 1996. As long as your volumes do not span non-raided hardware, you're not in bad shape.
If you buy your disks in bunches, your odds go up that they'll fail at similar times. In RAID5, your could lose two disks before your hot spare ever gets a chance to rebuild the array. In RAID6, you can lose two disks, and still have a viable volume while waiting for that hot spare to come back online.
As you get more disks in a volume, it's wise to increase the number of parity disks you have on it (for suitably highly-available data).
RAID5+1, RAID1+5 or RAID1+1 is suitably equivalent, but costs much more in terms of resources.
In theory, with Xen and VMware, there's the possibility to get at the hosts filesystem and devices. With a chroot jail, you add another layer to help prevent that. It's by no means perfect, or even necessary in most cases, but it certainly doesn't hurt.
The patent process does NOT prevent you from taking someone else's invention and making improvements and then getting a new patent - that's the whole point behind "prior art". The lawyers, however, might.
I solve all requests for "TEST" root access capabilities by giving them vmware and some stock read-only images to create virtual machines from. You want to fubar said machine, just fine. It won't impact me at all. The risk of NAT/trojans is still present, but in a properly managed environment, that's less of a problem than system stability in general.
One of the best things the military could do to lighten the load is to work out the bugs in caseless ammo. Carrying ammo sucks. If you could lose the brass, so much the better.
Slashdot Mirror
Strip out the "some of these bad things would hurt Americans" and I'll argue that this is the single best reason I've ever heard of why we needed to flambé this guy. The only Americans threatened by Saddam where the ones enforcing the No-Fly-Zone, and any in Israel if he ever got his Scuds flying again.
<spoken as an American>
We're not entirely sure. We are sure that the backplane on the original Powervault was faulty, which explained some mysterious Cluster behavior we'd been noticing. All the drives and the two chassis are now in the tip, since we don't want to trust anything to them. This is where it gets weird: the second Powervault was our nearline storage and catalog storage location for our Netbackup install. I've spent the last 4 weeks recovering catalog backups and doing tape inventory because that server wasn't so well backed up. Oops.
My recent favorite was a Dell Powervault that flaked out, finally dying. Putting the drives in another Powervault to recover them caused a number of other spare drives, plus this other Powervault, to also fail catastrophically. Thanks to one Powervault we lost 21 disks in the span of 12 hours.
Thankfully I made a network copy before I tried the disk to disk copy. You know your SCSI setup is aged when you can copy data via GbE faster than you can copy volume to volume on your controller.
Which is why I only use RAID1.
Although the ongoing work on the RAID6 driver is interesting to me...
HP and others are starting to get into remote desktops, where the computers are stored in a secured area, and keyboard mouse and video are projected over cat5 to a break-out box on the users desk. No physical access to the hardware anymore. It's only a matter of time where this becomes more prevalent. For an extra $150-200 per head, this isn't all that bad a cost in the right environment. You could use Belkin KVM extenders today to perform the same task.
Most data on windows servers is on a shared network drive. Do those have log files?
Absofrackin'lutely. It's called Auditing, and it's been a feature of WindowsNT/NTFS since 3.1.
HP nx6125 is 1400x1050.
There are larger models out there available from HP if you want a 17" screen.
I run a T41 at 1.8ghz, and I'll tell you, it can be a right dog. With SpeedSwitchXP, I can get some decent performance instead of XP running it at 667 mhz, but it chews through my 6 cell battery in less than two hours if I run it in high performance. At dynamic switching I can get three hours, maybe out of it (but the battery is older, I'll concede). And it's hot hot hot, even at 667 mhz. I'm not too happy to hold that on my lap. I turn to my six year old Omnibook 6000 running at 600mhz before I take out the T41. If you want 8 hours of life out of any Thinkpad you need a 9 - 12 cell battery. Even that would be pushing it.
Which is sad, because when the product was Interix way back in the day, it was actually pretty reliable, although it's always been troublesome to map the permission model/sids.
Hummingbird's product is the same way. It was good back when it was Beame and Whiteside making it, but suck has started creeping into it for years.
Somewhere I still have a box of Chameleon32 floppies... I'm such a pack rat.
Could "-o lfs" work, or would it too kick in this "cifs" driver?
//server/share /mnt -o lfs,username=me/domain
I routinely mount my cifs drives at work on Knoppix like so:
smbmount
I use LVM on my RAID1 mirrors all the time. I've NEVER had a problem with disk failure borking my system. It's something I learned from AIX 4.0 back in 1996.
As long as your volumes do not span non-raided hardware, you're not in bad shape.
If you buy your disks in bunches, your odds go up that they'll fail at similar times. In RAID5, your could lose two disks before your hot spare ever gets a chance to rebuild the array. In RAID6, you can lose two disks, and still have a viable volume while waiting for that hot spare to come back online.
As you get more disks in a volume, it's wise to increase the number of parity disks you have on it (for suitably highly-available data).
RAID5+1, RAID1+5 or RAID1+1 is suitably equivalent, but costs much more in terms of resources.
They have no control over people watching from across the street and over the wall of Wrigley Field, for instance.
you nincompoop - yes it does. all SLR's, film or digital, need batteries, to cock/release the mirror and shutter.
Me and my Nikon FM1 disagree with you. Maybe if you'd stated
All "contemporary" SLRs, film or digital
you'd have been right closer to the truth.
Do not confuse backup rates of MB/s with backup capacities of GB/tape.
Um.... South Park has been doing it for 9 years. I'd hardly call this a "last gasp".
In theory, with Xen and VMware, there's the possibility to get at the hosts filesystem and devices. With a chroot jail, you add another layer to help prevent that. It's by no means perfect, or even necessary in most cases, but it certainly doesn't hurt.
That, sir, earned you a place in my friends list.
The patent process does NOT prevent you from taking someone else's invention and making improvements and then getting a new patent - that's the whole point behind "prior art". The lawyers, however, might.
I solve all requests for "TEST" root access capabilities by giving them vmware and some stock read-only images to create virtual machines from. You want to fubar said machine, just fine. It won't impact me at all. The risk of NAT/trojans is still present, but in a properly managed environment, that's less of a problem than system stability in general.
IIRC only root (except some REALLY broken systems) can 'chmod +s' a file.
On XP it's called "RunAs".
-Chris
If you've got a Dell purchased on or around Sep-11, keep an eye on it. I'm seeing boatloads of them start failing lately.
Even *I*, notorious dimwit that I am, could read the sarcasm in the GP.
Relax, dude.
One of the best things the military could do to lighten the load is to work out the bugs in caseless ammo. Carrying ammo sucks. If you could lose the brass, so much the better.