|
face it, our only true useful roles are down to: something to complain about and washing the car.
Lifting heavy things and killing bugs.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
theoldfool wrote: Lifting heavy things and killing bugs.
 So true!
"Go forth into the source" - Neal Morse
|
|
|
|
|
From that article...
Quote: As a code of conduct, "women and children first" has no basis in maritime law. According to disaster evacuation expert Ed Galea, in modern-day evacuations people will usually "help the most vulnerable to leave the scene first, likely to be the injured, elderly and young children.
Somewhat re-assuring, not quite there yet, but I've put in some time pre-qualifying for that elderly priority 
|
|
|
|
|
|
It's my son's on the same day (but he is 9 years older). I guess that makes me ancient. 
|
|
|
|
|
You may give your juvenile (older than me!) a Garfield coloring book... 
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
And he would still appreciate the joke.
|
|
|
|
|
I've noticed that whenever I download a TAR file (and it usually is TAR.GZ) and decompress it, there always is yet another compressed file that needs to be decompressed. Why don't folks just do a single compression?
|
|
|
|
|
Because a TAR file isn't a compressed file.
A GZIP file is.
So them UNIX folk put files in a TAR then GZIP it.
Deal with it.
|
|
|
|
|
double de-compression? you're doing it wrong. the proper [as per design] procedure:
1. un-gzip it and redirect the output to the tape device,
... (may necessitate co-ordinated use of 2 hands if tape device doesn't have automatic start/stop control)
2. rewind the tape
... (on some sites a separate rewinding machine - submit both the tape and duly completed rewind request)
3. and then: un-tar (tar -x) it from the tape reader into the destination directory.
... (please remember: folders are where you keep your forms and notes, files are stored in directories.)
some new-fangled versions of tar have gzip built right in, many operators cant grok that.
kids these days: always looking for shortcuts.
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
Files are not stored in directories. (Nor in folders of course.)
|
|
|
|
|
good point, the directory is just a list of name and inode number pairs.
Such a simple system, could elegantly do things back then that NTFS still hasn't come close to without a whole mess of complicated hoops to jump through.
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
For first, you compare part of the file system to a file system. Second, NTFS is more inode than inode itself, as it stores the file data itself as attribute. Third, for Windows there is NTFS since 1993. In the Unix world since we have seen at least half dozen über weltmeister open source, free as in freedom file systems, every one leaving everything else in the dust. So much about extensibility and stability.
|
|
|
|
|
Tape? Tape? We don't use such new-fangled magnetics here!
Send it to the card punch!
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
luxury! toggle switches!
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
luxury! Solder bits of wire!
|
|
|
|
|
Don't make fun of us oldies!
Sure, it was back in the summer of 1978, before I started my studies, I got a summer job in a company where you had to flip switches, deposit, flip switches, deposit... I believe that mini bootstrap was 12 or 14 instructions long, enough to read in the short paper tape with the real bootstrap, so that we could mount the large reel of paper tape with, say, the compiler. For the system software, like the boot, it really wasn't paper, it was either mylar (I never met one who could tear off one of those mylar tapes with his bare hands), or plastic covered aluminum with so sharp edges that it could cut your throat if it got out of control. Some operators used leather gloves as a protection. But they never wore out, even if read a dozen times every day.
On the other hand: If you were lucky enough to need the same program the next morning that you used last the previous day, you didn't have to reload it: The machines had real core memory that retained its contents even if you turned off the power. (One of the guys scoffed semiconductor RAM, insisting that it was a fad: Computer industry will never accept memory that requires power to be constantly on to retain its contents!)
I even flipped switches at the University, but that was in a more specialized context: In one lab exercize we used a 2901 development kit. 2901 was a widely used 4 bit bit slice processor, that you could line up in twos for an 8 bit CPU, four for a 16 bit CPU, eight for a 32 bit CPU. It contained the hard logic, which was controlled by an external microcode RAM. For our lab, we had a 16 bit by 64 words RAM, and we wrote the microcode to read two 4 bit input values and place the sum on the output.
Really knowing what's going on, all the way down to the signal paths, is impossible with the systems of today. Even understanding the operating system thorougly, software only, is out of reach. I must admid that I sometimes long back to those days when everything could be understood, you had a feeling of mastering it all, you never left anything to automagic mechanisms you would simply have to trust in blind faith. The nearest you'll get today is in embedded programming, coding plain C on, say, an ARM M0. I did that for a few years, and it felt as if nostalgia had turned real
|
|
|
|
|
You need one of these new-fangled magnetic drum memories!
|
|
|
|
|
I must agree, kids these days have all these slang wordings on phones, but can't grok that tar stands for TApe aRchive, i's jst s bvius.
|
|
|
|
|
I wonder how much slang has been influenced by Unix (or *nix, if you prefer). Before *nix, slang made some degree of sense to me, but then we got these absurdities like 'less' for displaying av file (yes, I know its history!), GNU, and a thousand 'funny' but made-up and totally meaningless (in the way they are used) names and terms. I see more and more of that creeping into non-computer slang as well: terms with no etymological background related to the application, but with a completely unrelated meaning that is absurd in the context.
Controlling the development of a natural language makes herding cats look like a task for five year olds.
|
|
|
|
|
In plain English: A tar file is an (uncompressed) file(sssss) archive. i.e. a group of files together as one file.
GZip compress 1 file. The tar archive.
So you do in 2 steps is:
1. uncompress
2. unarchive
Now, it's about your tools. Some too unpack both steps as one.
Maybe use different tools if doing in 2 step is a bother?
|
|
|
|
|
Yes, what he said. You're probably used to ZIP files, which do both jobs in a single file format.
|
|
|
|
|
tar xvf file
Does both in one comnand
... such stuff as dreams are made on
|
|
|
|
|
megaadam wrote: tar xvf file
Memories, oh Memories!!!
I'd rather be phishing!
|
|
|
|
|
dingdingdingdingding!!!!!!
We have a winner!!!!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
