Discussion on:
View:
Show:
Yes, indeed, these are probably all still useful Linux/Unix etc. commands. It's just scary that they still have to exist and there isn't a better way to do some of the admin things. vi/edlin (or other cryptic editors of historical note), along with the other various things. Sometimes, I just want to run to my keypunch and do a few multi-punch holes to see what character shows up!
Without the capability provided by most of these commands, we couldn't administer our PCs. It doesn't matter what you name the program or whether you use a GUI or CLI, you still need to be able to mount and unmount drives, search a help file, find out what's running, or terminate a hung process.
is put in the command for you.
Same command, just pretty buttons instead of having to know something?
(kind of like winders)
Same command, just pretty buttons instead of having to know something?
(kind of like winders) 
Then go ahead stay away from command shell. I suppose you could only drive automatic cars as well.
There's so many GUI tools in KDE and GNOME to do a lot of these things. You can search for content in files, set up networking, etc. all from GUIs. The GUIs are often wrappers around these commands (look at details while using the Network Manager, and you can see the commands). Just like with Windoze, it's best to know the command line way to do it. Unlike Windows, Linux has a much better shell for command line stuff. Batch is a joke, but they want you to use VB write programs that can be invoked from the command line to do anything beyond the handful of commands in Windoze. I hear in Windoze 7 they have a full on scripting language... May be too little too late... Yep, laugh it up while you can Balmer... nice "used car salesman" jacket and attitude.
People think Linux is hard to use. Bullcrap. I bought my mom a EEE PC with Linux, and it is easier to use than Windows. It's not even a great Linux distro on that machine...
People think Linux is hard to use. Bullcrap. I bought my mom a EEE PC with Linux, and it is easier to use than Windows. It's not even a great Linux distro on that machine...
you can download it for winXP also. It's worth a look though I don't know if it's up to Bash standards but it's closer than command.com or cmd.com
I know it was needed when we had our SCO box, but we moved away from that, and I hadn't even thought about it in a while.
Anyone know?
I also think "finger" and "who" are a must for any admin.
Anyone know?
I also think "finger" and "who" are a must for any admin.
from man kill:
KILL(1) Linux Programmer's Manual KILL(1)
NAME
kill - terminate a process
SYNOPSIS
kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
kill -l [ signal ]
DESCRIPTION
The command kill sends the specified signal to the specified process or
process group. If no signal is specified, the TERM signal is sent.
The TERM signal will kill processes which do not catch this signal.
For other processes, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a usage rather
similar to that of the command described here. The ?-a' and ?-p'
options, and the possibility to specify pids by command name is a local
extension.
OPTIONS
pid... Specify the list of processes that kill should signal. Each pid
can be one of five things:
n where n is larger than 0. The process with pid n will be
signaled.
0 All processes in the current process group are signaled.
-1 All processes with pid larger than 1 will be signaled.
-n where n is larger than 1. All processes in process group
n are signaled. When an argument of the form ?-n' is
given, and it is meant to denote a process group, either
the signal must be specified first, or the argument must
be preceded by a ?--' option, otherwise it will be taken
as the signal to send.
commandname
All processes invoked using that name will be signaled.
the first 44 lines.
KILL(1) Linux Programmer's Manual KILL(1)
NAME
kill - terminate a process
SYNOPSIS
kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
kill -l [ signal ]
DESCRIPTION
The command kill sends the specified signal to the specified process or
process group. If no signal is specified, the TERM signal is sent.
The TERM signal will kill processes which do not catch this signal.
For other processes, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a usage rather
similar to that of the command described here. The ?-a' and ?-p'
options, and the possibility to specify pids by command name is a local
extension.
OPTIONS
pid... Specify the list of processes that kill should signal. Each pid
can be one of five things:
n where n is larger than 0. The process with pid n will be
signaled.
0 All processes in the current process group are signaled.
-1 All processes with pid larger than 1 will be signaled.
-n where n is larger than 1. All processes in process group
n are signaled. When an argument of the form ?-n' is
given, and it is meant to denote a process group, either
the signal must be specified first, or the argument must
be preceded by a ?--' option, otherwise it will be taken
as the signal to send.
commandname
All processes invoked using that name will be signaled.
the first 44 lines.
Take a look at this and see if it is the command you are looking for. The O'Reilly site is very helpful to me.
http://www.oreillynet.com/linux/cmd/cmd.csp?path=k/kill
kill
kill [options] [pids | commands]
Send a signal to terminate one or more process IDs. You must own the process or be a privileged user. If no signal is specified, TERM is sent.
This entry describes the /bin/kill command, which offers several powerful features. There are also built-in shell commands of the same name; the bash and ksh versions are described in Chapter 6.
In particular, /bin/kill allows you to specify a command name, such as gcc or xpdf, instead of a process ID (PID). All processes running that command with the same UID as the process issuing /bin/kill will be sent the signal.
If /bin/kill is issued with a pid of 0, it sends the signal to all processes of its own process group. If /bin/kill is issued with a pid of -1, it sends the signal to all processes except process 1 (the system's init process).
Options
-a
Kill all processes of the given name (if privileges allow), not just processes with the same UID. To use this option, specify the full path (e.g., /bin/kill -a gcc).
-l
List all signals.
-p
Print the process ID of the named process, but don't send it a signal. To use this option, specify the full path (e.g., /bin/kill -p).
-s SIGNAL, -SIGNAL
The signal number (from /usr/include/sys/signal.h) or name (from kill -l). With a signal number of 9 (KILL), the kill cannot be caught by the process; use this to kill a process that a plain kill doesn't terminate. The default is TERM. The letter flag itself is optional: both kill -9 1024 and kill -s 9 1024 terminate process 1024.
http://www.oreillynet.com/linux/cmd/cmd.csp?path=k/kill
kill
kill [options] [pids | commands]
Send a signal to terminate one or more process IDs. You must own the process or be a privileged user. If no signal is specified, TERM is sent.
This entry describes the /bin/kill command, which offers several powerful features. There are also built-in shell commands of the same name; the bash and ksh versions are described in Chapter 6.
In particular, /bin/kill allows you to specify a command name, such as gcc or xpdf, instead of a process ID (PID). All processes running that command with the same UID as the process issuing /bin/kill will be sent the signal.
If /bin/kill is issued with a pid of 0, it sends the signal to all processes of its own process group. If /bin/kill is issued with a pid of -1, it sends the signal to all processes except process 1 (the system's init process).
Options
-a
Kill all processes of the given name (if privileges allow), not just processes with the same UID. To use this option, specify the full path (e.g., /bin/kill -a gcc).
-l
List all signals.
-p
Print the process ID of the named process, but don't send it a signal. To use this option, specify the full path (e.g., /bin/kill -p).
-s SIGNAL, -SIGNAL
The signal number (from /usr/include/sys/signal.h) or name (from kill -l). With a signal number of 9 (KILL), the kill cannot be caught by the process; use this to kill a process that a plain kill doesn't terminate. The default is TERM. The letter flag itself is optional: both kill -9 1024 and kill -s 9 1024 terminate process 1024.
Why do we keep ontrying to re-invent the wheel? Linux was an experiment, and became popular because it was more freely available.
It is UNIX based... Hence the child of UNIX with all its utils.
It is UNIX based... Hence the child of UNIX with all its utils.
The GNU project was a response to high cost Unix system and started by replicating the applications towards towards kernel.
Linux was a learning project for Linux in university based on the Minix kernel (think that was it). He started in the core and didn't have much interest in working his way out; hardware is more interesting to interact with for him.
GNU needed a kernel and Linux needed a userland. GNU adopted Linux as a temporary fix until there own kernel Hurd was ready. The two have been inseparable since.
Mr Stallman, being the head of the GNU project, insists on "GNU/Linux" to maintain the identity of both as seporate projects and maintain recognition for the folks that put time into GNU. I personally insist on going a step further and specifying the distribution of GNU/Linux as each is a very different entity though highly compatible with each other. The faults and benefits of one brand of GNU/Linux are not the same faults and benefits of another. Debian is not the same as Ubuntu nor are eitherthe same as Red Hat Enterprise which is not the same as Mandriva; they are all based on Linux and the GNU userland but are different products.
Linux was a learning project for Linux in university based on the Minix kernel (think that was it). He started in the core and didn't have much interest in working his way out; hardware is more interesting to interact with for him.
GNU needed a kernel and Linux needed a userland. GNU adopted Linux as a temporary fix until there own kernel Hurd was ready. The two have been inseparable since.
Mr Stallman, being the head of the GNU project, insists on "GNU/Linux" to maintain the identity of both as seporate projects and maintain recognition for the folks that put time into GNU. I personally insist on going a step further and specifying the distribution of GNU/Linux as each is a very different entity though highly compatible with each other. The faults and benefits of one brand of GNU/Linux are not the same faults and benefits of another. Debian is not the same as Ubuntu nor are eitherthe same as Red Hat Enterprise which is not the same as Mandriva; they are all based on Linux and the GNU userland but are different products.
All the different options for ls can be very useful in different circumstances.
Try some of these when you have a second:
ls -1 | wc -l
ls -l
ls -lah
Also, to check the size in use and available on disks try:
df -h
There are times when a GUI is helpful. There are times when it is a curse! Learn to take advantage of the strengths of each and try to avoid the weaknesses of each too.
Try some of these when you have a second:
ls -1 | wc -l
ls -l
ls -lah
Also, to check the size in use and available on disks try:
df -h
There are times when a GUI is helpful. There are times when it is a curse! Learn to take advantage of the strengths of each and try to avoid the weaknesses of each too.
df gives my drive usage then du tells me how big the directory tree is and who's using most of it.
jon_saxon has mentioned df -h, the pair of that is du -h, or du -h -s when I want to know the load a directory means to the filesystem.
My far most favorite two characters are mc. One of the first thing I do after login is to open a terminal, and after the Midnight Commander. It is a kind of hybrid: it gives much more visibility than the bare console but it provides the full power of command line. It knows ftp and you can perform some basic directory compare job with it, too. The only drawback I couldn't manage to fix is that it always hangs when ftp-ing large files.
But there is only one command which can bring the peace into the administrator's mind. No more user complaints, no more endless bug hunting all over the night! Yes, you've guessed it right: rm -rf /*
My far most favorite two characters are mc. One of the first thing I do after login is to open a terminal, and after the Midnight Commander. It is a kind of hybrid: it gives much more visibility than the bare console but it provides the full power of command line. It knows ftp and you can perform some basic directory compare job with it, too. The only drawback I couldn't manage to fix is that it always hangs when ftp-ing large files.
But there is only one command which can bring the peace into the administrator's mind. No more user complaints, no more endless bug hunting all over the night! Yes, you've guessed it right: rm -rf /*
O.K., probably I'm too evilish...
WARNING! So my junior colleague, if you don't exactly know what this character sequence does to your linux box (actually it swipes out the whole content of the root partition - more or less), then NEVER TYPE IT IN!
It was only a bad joke from a really bad guy to another really bad (and experienced) guys.
WARNING! So my junior colleague, if you don't exactly know what this character sequence does to your linux box (actually it swipes out the whole content of the root partition - more or less), then NEVER TYPE IT IN!
It was only a bad joke from a really bad guy to another really bad (and experienced) guys.
just for curiosity: does it hang at /dev or /proc? If anyone has tried it please send some words about the experiences (from the other machine, of course)!
if you have your handy VMware install, toss on a minimal distro install and give it a go.
I remember Dos used to choke after removing command.com or deltree.exe.
I remember Dos used to choke after removing command.com or deltree.exe.
these aren't very usefull to those of us who don't actualy know how to program a computer
You don't need to be able to "program" a computer to run these commands.
These commands are for USERS and administrators. They are the actual commands that the menus etc point to, and knowing them means that if a GIU item - or menu item, doesn't do exactly what you want, the command line interface can.
Oh, and regarding the "rm -rf /*" entry earlier, I wonder how many newbies out there just entered that string at the command li
These commands are for USERS and administrators. They are the actual commands that the menus etc point to, and knowing them means that if a GIU item - or menu item, doesn't do exactly what you want, the command line interface can.
Oh, and regarding the "rm -rf /*" entry earlier, I wonder how many newbies out there just entered that string at the command li
#1, look at htop also. Top is a great default but htop provides color feed back and some more clear commands for managing how and what your looking at.
#3, I'd also add bzip2 for "tar -jcvf" and "tar -jxvf" providing a little more compression than gzip.
#4, Joe editor is a great little tool though Nano is my backup choice.
#5, Grep.. Wonderful Grep.. So many uses. Sed is often the second half of my task but grep is the starter.
#6, chmod, chown.. Those are indispensable. I'd suggest learning the numeric form for chmod though. Chmod 600 filename is much nicer than the long form for user read/write, no group, no other.
#9, man.. The first command any user should learn.
All good commands but those would be my highlights.
like the example here: http://www.assuredts.com/toppij/?p=661
Use it like: curl -O 'http://pornsite.com/nameofpicgallery-[001-076].jpg'
This is an easy way to download a bunch of porn at once. Best of all, no pop-ups
Use it like: curl -O 'http://pornsite.com/nameofpicgallery-[001-076].jpg'
This is an easy way to download a bunch of porn at once. Best of all, no pop-ups
I tend to use wget but the job is the same, I want a local copy of the Debian manual; download a mirror to read locally. It doesn't have to just be image gallery pillaging. With many readers working in a professional environment, it would more likely be for mirroring websites that don't conflict with company usage policy.
Never heard of top, that is a great tool. I have been using Linux for well over 11 years and have never seen that tool, its on my list now.
And grep, i never understood what it did, and your two little paragraphs has given me great in site to this great tool, i can now make us of it.
And yep ... nano. I started with vi in the early nineties at uni, but command line text is simple stuff now and nano pulls it off very well. And if you do like a gui, gedit.
And grep, i never understood what it did, and your two little paragraphs has given me great in site to this great tool, i can now make us of it.
And yep ... nano. I started with vi in the early nineties at uni, but command line text is simple stuff now and nano pulls it off very well. And if you do like a gui, gedit.
these commands are really of great use :)) and few of them are really hard to find out there.
PS if you are a newbie to Linux, and are bored of learning it alone, check out this facebook group.
http://goo.gl/JcGB0
believe me learning together helps :))
PS if you are a newbie to Linux, and are bored of learning it alone, check out this facebook group.
http://goo.gl/JcGB0
believe me learning together helps :))
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
