Linux/UNIX comes with the vim text editor for creating and editing files but it is by no means the only one. There are actually a lot of different editor's out there and I am going to go over a few of them today.
1.) CRISP: This is a GUI(Graphical User Interface) text editor. While it works on multiple interfaces it does you no good if you are using a comand line interface program. It does have a lot of features and edit's many different types of code such as HTML and JAVASCRIPT. You can get a free trial verson of this at www.crisp.com but in the end you have to pay to have it.
2.) TED Advanced Text Editor for UNIX: TED works on conventional text environments(command line interfaces). It is compatible with both Windows and UNIX/Linux systems. As the name suggests though it is more for the advanced user. It is not a wordprocessor, but does contain the ability to make basic text files. A plus to this editor is that there is no limit to file size and length. This editor is free which makes it a bit more attractive to use than CRISP.
3.) Eddie: Eddie was originally disigned for Linux but is now on the Mac os and is a GUI text editor. It is used mostly for editing C and C++ which makes this one more for programmers than anything. It might be a bit more simple to use, but it is definitely not for beginners. It does have supports for HTML and JAVASCRIPT as well as many more. Since it is very limited on what it works with it is probably a poor choice for the every day user. This editor is also free.
These are just a sample of the many text editor's that are out there. There are a wide variety, but with a bit of research it is possible to find the right one for you.
Sunday, September 28, 2008
Sunday, September 21, 2008
Chapter 3 Self Test
1.) When you enter the following command, what happens and why? cat > dog
You create a new file(Or overwrite an existing one) named dog and it allows you to type text into the file. The command line tells the computer to start the cat utility and then to create the new(or overwrite the old) file using the text you type in after this is entered.
2.) What results from using the following commands?
A. who grep $USER
The computer outputs who you are, when you logged on and where you logged on from.
B. grep \$HOME file1
grep specifies a search string, \$HOME is what it is searching for, and file1 is the file you are searching for. If there is no "file1" on your computer it tells you that grep: file1: no such file or directory.
C. echo u* >> file1
The computer inputs all the files beginning with u into the end of file1.
D. echo 'u*' >> file1
The quote marks on the end tells the computer not to use the * as an undefined character and then inputs anything with the u* into the end of file1.
E. ps
Gives you a list of the processes that are currently in use.
F. . fileA
The . command tells the computer to treat the file as though we had typed it into the computer and execute the contents of the file.
G. set noclobber
If you are in the csh or tcsh shells it tells the computer to not allow files to be overwritten, but if you are in ksh or bash shells it does nothing. The correct command for ksh or bash shells would be set -o noclobber.
H. set -o
By itself this tells you which functions are on or off.
I. chmod +x file2
Changes the mode of file2 to make it an executable file.
3.) How can we change the prompt to be Next? in both families of shells(C shells and Korn shells)?
In C shells(csh and tcsh) type in set prompt='Next?'. In Korn shells(sh, bash, and ksh) type PS1='Next?'.
4.) What data is in each field in the passwd file?
username(login):password:User ID:Group ID:Info on user:Home Directory:Start-up program.
5.) What command instructs the shell not to accept CTRL-D as a signal to log off?
In the csh or tcsh shells use set ignoreeof, and in the ksh or bash shells use set-o ignoreeof.
You create a new file(Or overwrite an existing one) named dog and it allows you to type text into the file. The command line tells the computer to start the cat utility and then to create the new(or overwrite the old) file using the text you type in after this is entered.
2.) What results from using the following commands?
A. who grep $USER
The computer outputs who you are, when you logged on and where you logged on from.
B. grep \$HOME file1
grep specifies a search string, \$HOME is what it is searching for, and file1 is the file you are searching for. If there is no "file1" on your computer it tells you that grep: file1: no such file or directory.
C. echo u* >> file1
The computer inputs all the files beginning with u into the end of file1.
D. echo 'u*' >> file1
The quote marks on the end tells the computer not to use the * as an undefined character and then inputs anything with the u* into the end of file1.
E. ps
Gives you a list of the processes that are currently in use.
F. . fileA
The . command tells the computer to treat the file as though we had typed it into the computer and execute the contents of the file.
G. set noclobber
If you are in the csh or tcsh shells it tells the computer to not allow files to be overwritten, but if you are in ksh or bash shells it does nothing. The correct command for ksh or bash shells would be set -o noclobber.
H. set -o
By itself this tells you which functions are on or off.
I. chmod +x file2
Changes the mode of file2 to make it an executable file.
3.) How can we change the prompt to be Next? in both families of shells(C shells and Korn shells)?
In C shells(csh and tcsh) type in set prompt='Next?'. In Korn shells(sh, bash, and ksh) type PS1='Next?'.
4.) What data is in each field in the passwd file?
username(login):password:User ID:Group ID:Info on user:Home Directory:Start-up program.
5.) What command instructs the shell not to accept CTRL-D as a signal to log off?
In the csh or tcsh shells use set ignoreeof, and in the ksh or bash shells use set-o ignoreeof.
Sunday, September 14, 2008
My favorite Linux commands
Having been an avid user of D.O.S. in my youth this is actually a fairly easy one for me. It has actually been nice getting back into using the keyed in commands instead of having to use my mouse, and even inspired me to start building an updated D.O.S. based system.
First and foremost for me is the mkdir command. You use it to make a new directory and it is the exact same as in D.O.S. It really brought back memories for me of when I first started working on computers.
Second would have to be the who command. It is really nice to know who is logged on to the system at the same time you are and this brings up a list of all those people.
I think third for me is the history command. Being able to go back and see what you have done since you logged on is really cool, and if you save that information in an ongoing file you are able to go back and see what you have been working on for more than one day.
First and foremost for me is the mkdir command. You use it to make a new directory and it is the exact same as in D.O.S. It really brought back memories for me of when I first started working on computers.
Second would have to be the who command. It is really nice to know who is logged on to the system at the same time you are and this brings up a list of all those people.
I think third for me is the history command. Being able to go back and see what you have done since you logged on is really cool, and if you save that information in an ongoing file you are able to go back and see what you have been working on for more than one day.
Saturday, September 6, 2008
UNIX and Linux in the real world
There are many people in the world who do not even know what Linux and UNIX are. This is a sad fact considering that without either one of them the world would be a much different place. Linux/Unix are operating systems that run many of today's "behind the scenes" business operations. Bank's use them to run ATM's, and modern films use it for helping do special effects. Even the Internet would be affected by not having it as most server's are run in a Linux/Unix environment.
It would not just be business that is affected either. Quite a few sections of the government are run off of Linux/UNIX platforms. While many people would cheer for constantly crashing IRS databases because they are being run on Windows, we would also be extremely vulnerable to attacks from other countries because the Department of Defense is also running Linux/UNIX. Windows may be a more user friendly system, it can not compete with the stability that Linux/Unix offers. I for one can not wait to become more adept at using it so I can get rid of Windows forever and have a more stable system at home.
It would not just be business that is affected either. Quite a few sections of the government are run off of Linux/UNIX platforms. While many people would cheer for constantly crashing IRS databases because they are being run on Windows, we would also be extremely vulnerable to attacks from other countries because the Department of Defense is also running Linux/UNIX. Windows may be a more user friendly system, it can not compete with the stability that Linux/Unix offers. I for one can not wait to become more adept at using it so I can get rid of Windows forever and have a more stable system at home.
Subscribe to:
Posts (Atom)
