Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
How often do you have to look up the command for something?
How often do you have to look up the command for something?
And how much do you have memorized so you don't have to?
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: How often do you have to look up the command for somethi
Again, very often. I use Internet search. What bugs me is that I can't remember the right instructions for opening each of the various tar balls. Every time I download a tar package I have to look it up.
annadane, do yourself a favour and familiarize yourself with the man pages. At first you won't understand anything. Almost nobody understands them perfectly so don't be discouraged. Eventually, you will learn syntax and that is important. Being able to check a man page to see how something works or what the options are will save you all sorts of trouble in the long run.
annadane, do yourself a favour and familiarize yourself with the man pages. At first you won't understand anything. Almost nobody understands them perfectly so don't be discouraged. Eventually, you will learn syntax and that is important. Being able to check a man page to see how something works or what the options are will save you all sorts of trouble in the long run.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: How often do you have to look up the command for somethi
Did you know that most current versions of `tar` do this automatically?Bulkley wrote:What bugs me is that I can't remember the right instructions for opening each of the various tar balls. Every time I download a tar package I have to look it up.
This should work for any tarball:
Code: Select all
tar xf ball.tar.whatever
deadbang
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: How often do you have to look up the command for somethi
I don't think I understand the question,.....
I couldn't find any command called "something"
I usually use 'man'
but again, no such command,..
Is this command 'something' some kind of new feature only to be found in
Debian ?
What does 'something' do on linux ?
But nothing about this command in the results either,...I think maybe it is
something I do not need to memorize, and this is the first ,and only time
I will need to try looking it up.
Also, I did not find any "packages" or "tar balls" available for down load,...
I couldn't find any command called "something"
Code: Select all
apropos something
less(3p) - perl pragma to request less of something
but again, no such command,..
Code: Select all
$ man something
man: No entry for something in the manual.
Code: Select all
$ something
ksh: something: not found
Debian ?
So I tried doing a search :Post by Bulkley » 2016-12-17 16:13
Again, very often. I use Internet search. What bugs me is that I can't remember the right instructions for opening each of the various tar balls. Every time I download a tar package I have to look it up.
What does 'something' do on linux ?
But nothing about this command in the results either,...I think maybe it is
something I do not need to memorize, and this is the first ,and only time
I will need to try looking it up.
Also, I did not find any "packages" or "tar balls" available for down load,...
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: How often do you have to look up the command for somethi
I used $something as a variable.
Please replace $something with whichever keyphrase is relevant for the search at hand.
For example, to search for comands related to wireless networking, we could try:
Sorry for the confusion Garry
EDIT:
Please replace $something with whichever keyphrase is relevant for the search at hand.
For example, to search for comands related to wireless networking, we could try:
Code: Select all
empty@Arch ~ % apropos wireless
crda (8) - send to the kernel a wireless regulatory domain for a given ISO / IEC 3166 alpha2
iw (8) - show / manipulate wireless devices and their configuration
iwconfig (8) - configure a wireless network interface
iwevent (8) - Display Wireless Events generated by drivers and setting changes
iwgetid (8) - Report ESSID, NWID or AP/Cell Address of wireless network
iwlist (8) - Get more detailed wireless information from a wireless interface
iwpriv (8) - configure optionals (private) parameters of a wireless network interface
iwspy (8) - Get wireless statistics from specific nodes
netctl-auto (1) - Control automatic selection of wireless netctl profiles
regulatory.bin (5) - The Linux wireless regulatory database
rfkill (8) - tool for enabling and disabling wireless devices
wireless (7) - Wireless Tools and Wireless Extensions
EDIT:
Code: Select all
empty@Arch ~ % export something=wireless
empty@Arch ~ % apropos "$something"
crda (8) - send to the kernel a wireless regulatory domain for a given ISO / IEC 3166 alpha2
iw (8) - show / manipulate wireless devices and their configuration
iwconfig (8) - configure a wireless network interface
iwevent (8) - Display Wireless Events generated by drivers and setting changes
iwgetid (8) - Report ESSID, NWID or AP/Cell Address of wireless network
iwlist (8) - Get more detailed wireless information from a wireless interface
iwpriv (8) - configure optionals (private) parameters of a wireless network interface
iwspy (8) - Get wireless statistics from specific nodes
netctl-auto (1) - Control automatic selection of wireless netctl profiles
regulatory.bin (5) - The Linux wireless regulatory database
rfkill (8) - tool for enabling and disabling wireless devices
wireless (7) - Wireless Tools and Wireless Extension
deadbang
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: How often do you have to look up the command for somethi
Oh. I forgot,... let me see, if I can remember, this. ----------thinking,-------What bugs me is that I can't remember the right instructions for opening each of the various tar balls.
trying to remember,----
Code: Select all
man tar
Found it :
Or, if the manual is not clear enough:TAR(1) General Commands Manual TAR(1)
NAME
tar - tape archiver
SYNOPSIS
tar {crtux}[014578befHhjLmNOoPpqsvwXZz]
[blocking-factor | archive | replstr] [-C directory] [-I file]
[file ...]
tar {-crtux} [-014578eHhjLmNOoPpqvwXZz] [-b blocking-factor]
[-C directory] [-f archive] [-I file] [-s replstr] [file ...]
DESCRIPTION
The tar command creates, adds files to, or extracts files from an archive
file in ``tar'' format. A tar archive is often stored on a magnetic
tape, but can be stored equally well on a floppy, CD-ROM, or in a regular
disk file.
In the first (legacy) form, all option flags except for -C and -I must be
contained within the first argument to tar and must not be prefixed by a
hyphen (`-'). Option arguments, if any, are processed as subsequent
arguments to tar and are processed in the order in which their------------snip---
How to unzip a .tar file on linux
First hit: https://www.cyberciti.biz/faq/tar-extract-linux/
That is what I do when I can not remember something, (and most of the time I can not remember much of anything) and I doExtract or Unpack a TarBall File
To unpack or extract a tar file, type:Code: Select all
tar -xvf file.tar
not have it in my 'history'
see
Code: Select all
man history
I use the most.,..... and until now I have never heard of any command called 'something',.... I had a hard time learning about the "foo" file and what it is
for as well, but it is a very important file, and everybody needs to know
about that, fortunately it is listed and there are plenty of search results
on what "foo" file does.
===== P.S. :
Thanks H_O_A_S,...
Sorry for the confusion Garry
-
- Emeritus
- Posts: 2435
- Joined: 2010-12-07 19:55
- Has thanked: 14 times
- Been thanked: 54 times
Re: How often do you have to look up the command for somethi
I'm not sure how you expect people to answer this, or how you will interpret what thay say.
The people who use the CLI will use it a lot. The people who don't want to use it much, will not use it much.
What answer do you want or expect? 47%? 4 out of 5? D?
There is always this, to remind people https://www.debian.org/doc/manuals/refcard/refcard
The people who use the CLI will use it a lot. The people who don't want to use it much, will not use it much.
What answer do you want or expect? 47%? 4 out of 5? D?
There is always this, to remind people https://www.debian.org/doc/manuals/refcard/refcard
Re: How often do you have to look up the command for somethi
It was a fun thread, I give it a twoAnd how much do you have memorized so you don't have to?
...
This escalated quickly.
Code: Select all
$ apropos man --and apropos
apropos (1) - search the manual page names and descriptions
resigned by AI ChatGPT
Re: How often do you have to look up the command for somethi
My opinion is that while most people think that medieval rote memorizing techniques are boring a quaint... that they have their uses in some places in life. For example, when you have to look up the command sequence for tar every time and you use it often. You just end up loosing a lot of time and "flow" from your work searching for stuff like that...
Edit: word missing from sentence
and p.s imagine if you had not memorized the times tables in primary school. You'd be looking up 6 x 8 on google. But since you did memorize that, now you have it for life. Why stop doing this in adulthood?
Edit: word missing from sentence
and p.s imagine if you had not memorized the times tables in primary school. You'd be looking up 6 x 8 on google. But since you did memorize that, now you have it for life. Why stop doing this in adulthood?
Last edited by pylkko on 2016-12-17 23:43, edited 2 times in total.
- Ardouos
- Posts: 1077
- Joined: 2013-11-03 00:30
- Location: Elicoor II
- Has thanked: 1 time
- Been thanked: 4 times
Re: How often do you have to look up the command for somethi
Sometikes for known tools that I do not use often, all the time to find new tools that will may be useful, or to replace another tool. I mostly try to rely on man pages when I forget switches/ functions.
There is only one Debian | Do not break Debian | Stability and Debian | Backports
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
Re: How often do you have to look up the command for somethi
A few things,
Take notes
Make a cheat sheet
Download a cheat sheet
Take notes
Make a cheat sheet
Download a cheat sheet
-
- Posts: 1394
- Joined: 2007-03-04 21:10
- Location: U.S.A. - WI.
Re: How often do you have to look up the command for somethi
pylkko wrote:My opinion is that while most people think that medieval rote memorizing techniques are boring a quaint... that they have their uses in some places in life. For example, when you have to look up the command sequence for tar every time and you use it often. You just end up loosing a lot of time and "flow" from your work searching for stuff like that...
Edit: word missing from sentence
and p.s imagine if you had not memorized the times tables in primary school. You'd be looking up 6 x 8 on google. But since you did memorize that, now you have it for life. Why stop doing this in adulthood?
I'm in my late 30's and never memorized the times table. Seems pretty pointless to me actually, I can just do the quick mental calculations in my head. I've also passed college algebra and statistics classes, with a few calculus classes soon to be taken too.
Code: Select all
6*8 ---> 8*2*3 = 48
if you need to break it down more:
8+8 = 16 : 16+16 = 32 : 32 + 16 = 48
Saves brain space for the equations and such that actually matter.
fortune -o
Your love life will be... interesting.
How did it know?
The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches
Your love life will be... interesting.
How did it know?
The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches
Re: How often do you have to look up the command for somethi
Although I agree with arochester that the question was inartfully phrased (after all, who keeps reliable and therefore trustworthy records on frequency of command lookups?), I can offer a general answer to the underlying philosophical question.
All. The. Damn. Time.
With some notable exceptions, command syntax just isn't worth devoting brain wrinkles to. It's more important to understand the theory of operation and look up the syntactical details when/as they become relevant.
My use of this strategy extends well beyond *nix commands. Some years back, I had occasion to use a high-end statistics package (SAS) a lot. I can explain the theory of operation behind, say, correspondence analysis all day. But I would consider it a gratuitous waste of scarce cognitive resources to memorize all of the switches used by SAS' PROC CORRESP.
The exceptions I mentioned fall into two categories: (a) constantly used (e.g., find) and (b) just too handy/insanely easy to remember (e.g., the -a flag on cp/rsync).
All. The. Damn. Time.
With some notable exceptions, command syntax just isn't worth devoting brain wrinkles to. It's more important to understand the theory of operation and look up the syntactical details when/as they become relevant.
My use of this strategy extends well beyond *nix commands. Some years back, I had occasion to use a high-end statistics package (SAS) a lot. I can explain the theory of operation behind, say, correspondence analysis all day. But I would consider it a gratuitous waste of scarce cognitive resources to memorize all of the switches used by SAS' PROC CORRESP.
The exceptions I mentioned fall into two categories: (a) constantly used (e.g., find) and (b) just too handy/insanely easy to remember (e.g., the -a flag on cp/rsync).
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: How often do you have to look up the command for somethi
I was going to comment, but changed my mind, but then when I saw this:by pylkko » p.s imagine if you had not memorized the times tables in primary school. You'd be looking up 6 x 8 on google
And decided to go ahead, there really are quite a few people that do notby pendrachken » I'm in my late 30's and never memorized the times table.
know even the basic times tables, 1 thru 10,...for what ever reasons.
I think it is important, but in these days with calculators, maybe it isn't.
Any way here is something to help people memorize them, if they want to.
Often I do have to do a search, example " What is the Linux command to "do this or that task" ? (where is says "this or that task" , would be a description of the task in question),.... another example, a new user might have to ask
"what is the linux command to list directories ? " or
"what is the linux command to multiply " ?
You can use 'bc' to do math, including multiply,
Code: Select all
man bc
For example:BC(1) General Commands Manual BC(1)
NAME
bc - arbitrary-precision arithmetic language and calculator
SYNOPSIS
bc [-cl] [-e expression] [file ...]
DESCRIPTION
bc is an interactive processor for a language which resembles C but
provides unlimited precision arithmetic. It takes input from any
expressions on the command line and any files given, then reads the
standard input.
Code: Select all
$ bc
573 * 4
2292
2292 * 5789
13268388
13268388 / 5789
2292
quit
to remember the commands they use the most, some people would have to
do a search to find the right command for a task more often then others, it all
depends on their memory and how many commands they are all ready familiar
with, ......Now that I understand the question better............
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
Re: How often do you have to look up the command for somethi
I think you missed the point entirely. Nobody needs to memorize anything. But it is something that can be done and works remarkably well. Anybody can remember a shopping list of any length with the method of loci, but anynody can use their time to write it on paper or even install some pointless app on a smart phone for that purpose. Some people claim cognitive health benefits from using your memory often but AFAIK the scientific literature is inconclusive.pendrachken wrote:pylkko wrote:My opinion is that while most people think that medieval rote memorizing techniques are boring a quaint... that they have their uses in some places in life. For example, when you have to look up the command sequence for tar every time and you use it often. You just end up loosing a lot of time and "flow" from your work searching for stuff like that...
Edit: word missing from sentence
and p.s imagine if you had not memorized the times tables in primary school. You'd be looking up 6 x 8 on google. But since you did memorize that, now you have it for life. Why stop doing this in adulthood?
I'm in my late 30's and never memorized the times table. Seems pretty pointless to me actually, I can just do the quick mental calculations in my head. I've also passed college algebra and statistics classes, with a few calculus classes soon to be taken too.
No need for rote memorization of some stupid table when chaining a few dead simple calculations can be done in just as short of time. Or you could just use a calculator...Code: Select all
6*8 ---> 8*2*3 = 48 if you need to break it down more: 8+8 = 16 : 16+16 = 32 : 32 + 16 = 48
Saves brain space for the equations and such that actually matter.
And memorizing is something that is quite widely used in areas where people want to be able not spend effort on finding basic things, for example in medical schools and hospitals all around the world. Of course, when you are in front of a computer, looking up things is relatively easy. Also it does not make sense to memorize everything. It is an optimizing problem, i.e it make sense to memorize something when the total effort spent is less than the total cumulative effort of looking up over and over again. But I still believe that people too easily dismiss the usefulness of the methods just because they have negative personal feelings towards them.
I find your 'mental calculation' example really unconvincing. That you use emotiomally loaded term 'stupid tables' indicates to me that you are not addressing the issue rationally. What you suggest definetly does not 'save brain space'.. it makes something auyomatic and fast into something slow,effortful, and error prone.
- alan stone
- Posts: 269
- Joined: 2011-10-22 14:08
- Location: In my body.
Re: How often do you have to look up the command for somethi
I agree. Also I think that would be the answer from anyone who uses the CLI regardless of how often.dasein wrote:... I can offer a general answer to the underlying philosophical question.
All. The. Damn. Time.
If you're looking for some constructive tips:
1. Make a BASH alias If you using common flags with your command:
Code: Select all
alias diff='\diff -rupN'
2. Copy some frequently viewed man pages to a text file:
Code: Select all
man ffmpeg > ffmpeg.man
ASRock H77 Pro4-M i7 3770K - 32GB RAM - Pioneer BDR-209D
Re: How often do you have to look up the command for somethi
I don't use commands for my desktop computer and laptop beyond updating since I set them up and configured them long ago.annadane wrote:How often do you have to look up the command for something?
I use the command line via ssh to do LAMP server administration and I'm familiar with the basic commands.
I'm able to find my way around the file system and do file operations using the command line but I always check them from my own records or from the 'net. I've memorized the basic commands but of course I have to look up the more complicated ones. I am able to do some other stuff like backporting packages though.annadane wrote:And how much do you have memorized so you don't have to?
The worse thing for me is logins and passwords; I often end up having different passwords on my home computer and the one at work and on my memory stick.
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.