 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> Really? I would have thought running around requires *lots* of muscle
> power. (That's why I can't do it, for example...)
Comparatively speaking. Running doesn't take unusual amounts of muscle
power. Running when three 300-pound linebackers are holding you down takes
unusual amounts of muscle power.
If you can't run fast, it's because you're doing it wrong. Don't think about
your legs. Start running, then move your arms as fast as you can. Running is
in the arms, not the legs. (Hence the "runs like a girl" concept.)
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> After about 4 years the tape would wear out,
> but that's hardly a big deal assuming you notice this and replace the tape.
And if you replace the disk drive on the same basis, you'll have better
reliability. :-)
> I *have*, however, had endless issues with BackupExec not actually
> ****ing working properly! >_<
That's the other problem. When's the last time you copied a file, then went
to open it and found it wasn't there?
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stefan Viljoen schrieb:
> Makes sense. As far as I know the US military is one of THE most prolific
> users of the EM spectrum in the world. He's probably got his radar on or in
> a specific mode - I've read that the "ground tracking" mode on the Hughes /
> Westinghouse (?) "APG" sets US Navy F-18s (among others) use tend to do
> this. Apparently the F-22 (or is it the F-35?) have a "burn 'em down" mode
> on their radars - they are powerful enough to fry the electronics in an
> enemy plane with a single sweep, instead of shooting it down with a
> missile.
Heh, that's cool... they'll never see it coming... they'd better be sure
to not "burn down" their friendlies though. And enemy fighter jets may
be hardened against EM radiation. At least I'd expect the newest US
fighter jets to be.
I guess it'll bee the F-22 though, which in terms of performance as a
fighter jet seems to be superior to the F-35 (except at being a
comparatively inexpensive "bread and butter" fighter, which is what the
F-35 was designed to be). I guess there's a reason why the F-35 is on
offer to allies, while the F-22 is not.
> I remember when Victor Belenko defected with his MiG in the 80's, USAF
> engineers were amazed to find that it used valves for its radar and
> electronics (valveotronics), instead of transistors. After they had
> finished beating themselves on the chest with their pride in American
> advancement and technology, some wise soul pointed out that the MiG would
> keep flying after being through the EMP of a nuclear explosion, AND its
> radar would be working - while USAF F-16s and F-15s would be falling like
> leaves because their digital flight controls would be melted, and their
> radars would be dead.
Hm, are they sure about that? Valve tubes are delicate things, too,
aren't they? Give the EMP any place to couple in, and the voltages might
kill the cathodes, I'd guess.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 10 Nov 2009 16:57:24 +0000, Invisible wrote:
>>>> Never used DAT drives for backup, have you? ;-)
>>> No, only for the last 6 years.
>>
>> I feel for you. I had tapes that actually verified nightly that were
>> completely useless to restore from. This is back in the DDS-1/DDS-2
>> days, so maybe it's improved - but here's the thing: DAT stands for
>> "Digital Audio Tape".
>
> We used to use DDS-3, DDS-4 and DAT-72. (Don't you love how all tapes
> have storage capacities "assuming 2:1 compression"? I have never seen
> any backup job achieve anything approaching 2:1 compression.) Never had
> any significant problem. After about 4 years the tape would wear out,
> but that's hardly a big deal assuming you notice this and replace the
> tape.
>
> Never had any issues of any kind with restoring data from tape.
You've been lucky, then, is all I can say based on my experience.
> I *have*, however, had endless issues with BackupExec not actually
> ****ing working properly! >_<
>
>>>> Horrible quality of storage media, and terrible shelf life IME.
>>> Really?
>>
>> Yes, really. With the DDS-2 tapes I was using at the time, the
>> manufacturer recommended no more than something like 10 or 20 uses.
>
>> I'm glad I didn't pay for the drives - otherwise I'd have been more
>> upset that they burned out so quickly (about a year, IIRC - but I was
>> running backups on a more or less continuous basis as part of my
>> testing).
>
> I think we had 1 tape drive wear out. (We had about 6 of them.) And it
> was the oldest, crappiest one of the lot.
>
> Seriously, I did tape backups every single weekday for 6 years and had
> almost no issues related to the tapes or tape drives. That's not what
> I'd consider "unreliable".
I spent the better part of a 15+ year IT career dealing with backup
systems (among other things). I even managed to get "suspended" from
work for a week because of equipment and media failures that prevented
restoration of a system that actually did die (and of course, it was the
finance system) at one job.
If the choice were to back up using DAT drives - even with modern tapes
and drives - or die a slow and painful death in a horrible manner, I'd
take the slow and painful death. Even with the advancements in
technology.
The technology is/has been notoriously bad, the media is crap, and the
software for PC systems backups makes me want to gouge my eyes out with a
dull instrument.
>> I had much better luck with DLT drives.
>
> I have no idea what DLT is.
GIYF - "Digital Linear Tape".
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 10 Nov 2009 09:50:33 -0800, Darren New wrote:
> clipka wrote:
>> On unix, where even now it is still quite common to do stuff in some
>> command line shell, it is pretty uncommon to put blanks in filenames,
>> because it would be a hassle to even "cd" there.
>
> That used to be true back in the 1.x days of Linux (like, 10 years ago),
> but nowadays I haven't had much problem with spaces in file names,
> except in lazy scripts I've written myself using "$@" and such. (And
> that's more because it's easier for me to skip the one-line script than
> to look up the proper quoting mechanism to get that in.)
>
> Bash command-line completion, for example, will put quotes around names
> with spaces in them. But yes, this wasn't always common, even long
> after Mac and Windows commonly used spaces in names.
Even still, though, on Linux you can run into problems with spaces in
names. Using scp to copy files from one openSUSE 11.1 box to another,
for example, spaces (escaped and quoted) always cause me a problem.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Henderson wrote:
> Using scp to copy files from one openSUSE 11.1 box to another,
> for example, spaces (escaped and quoted) always cause me a problem.
Well, yeah, scp is the wrong tool to use for almost everything, based on the
concept that it's safe to log in remotely to a machine using the normal
login mechanisms and then bet that stdin and stdout are parsable. :-)
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 10 Nov 2009 11:16:29 -0800, Darren New wrote:
> Jim Henderson wrote:
>> Using scp to copy files from one openSUSE 11.1 box to another, for
>> example, spaces (escaped and quoted) always cause me a problem.
>
> Well, yeah, scp is the wrong tool to use for almost everything, based on
> the concept that it's safe to log in remotely to a machine using the
> normal login mechanisms and then bet that stdin and stdout are parsable.
> :-)
I suppose I *could* use rsync, hadn't really thought about it much. :-)
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New schrieb:
> Invisible wrote:
>> For the average home user, if your house burns down, you're not going
>> to give a **** about the holiday photos and the copy of Nero you just
>> lost - YOU HAVE NOWHERE TO LIVE!!
>
> Not true. Well, Nero, maybe, but holiday photos and pictures of people
> who are now dead and such are irreplacable. You can always get somewhere
> new to live, or fix the house.
Reminds me of a recent incident here in the city I live in (Cologne
Germany).
They're building a new southbound subway tunnel (well, actually,
/currently/ they're /not/ building, as far as I know).
Some months ago, suspicious noise was heard in a large public building.
Construction workers came in and suggested that everyone better leave
the building... *NOW*. And literally in a matter of minutes, the whole
building - plus a few private houses - went "down the drain". Where once
stood an ugly, 4-story-or-so concrete monster, now there was a gaping
20-foot-or-so deep (give or take another 20) hole, some-hundred-foot by
one-hundred-foot or so.
Two people were asleep at the time in the private homes that it took
down with it, so there was some loss of life to mourn (fortunately there
were not more casualties). And quite a number of people lost their
homes. However, most of them mourned not so much the loss of a place to
put their toothbrush, but rather the loss of irreplacable property -
documents such as photos, letters and the like.
So did the city: The building that had collapsed was the historical archive.
And it was /not/ dry weather those days.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New schrieb:
> Steam needs to give you that option, yah. Did you ask them? :-) I don't
> remember if Steam asks where to install Steam when you install it. I
> don't see any obvious way to change it after the fact.
As I have Steam installed in "F:\Spiele\Steam", and the games it
installed are located in subdirectories thereof, it must be doing
/something/ right...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> On unix, where even now it is still quite common to do stuff in some
>> command line shell, it is pretty uncommon to put blanks in filenames,
>> because it would be a hassle to even "cd" there.
>
> That used to be true back in the 1.x days of Linux (like, 10 years ago),
> but nowadays I haven't had much problem with spaces in file names,
> except in lazy scripts I've written myself using "$@" and such. (And
> that's more because it's easier for me to skip the one-line script than
> to look up the proper quoting mechanism to get that in.)
>
> Bash command-line completion, for example, will put quotes around names
> with spaces in them. But yes, this wasn't always common, even long
> after Mac and Windows commonly used spaces in names.
Correct me - isn't Unix that OS that allows you to put *any* arbitrary
octet sequence into a filename so long as it doesn't contain NUL or "/"?
(E.g., you could name a file with ANSI escape sequences in it if you
felt especially vindictive.)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
