DOCSLIB.ORG

1 Very Short Linux Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1 Very Short Linux Manual 1 Very Short Linux Manual Assume you have a computer that runs (any flavor) of Linux. The programs A we would like to be able to run in this course are FORM, LTEXand whatever C programs we make. The first thing is that we need to be able to create directories and move around them. When you log in, you are usually in what is called your home directory. You create new directories with the command mkdir nameofnewdirectory This command is to be typed in in a so-called terminal window. There are also ways by which to make new directories with the mouse, but we will need the terminal window anyway. Usually you find the terminal program with the mouse in the menu under System. You can open any number of terminal windows. The ones that you keep open when you log out will open again automatically the next time you log in. With the mouse you select in which terminal window you want to issue commands. You can see which files and/or subdirectories you have with the ls command. There are several useful varieties of this command: • ls Just list what files and directories there are • ls -l Give more details in the listing. • ls -la Also show the hidden files (names starting with a period) • ls -ltr Order the files such that they are in order of last access. • ls name Give an ls of the named directory or file. There are more options. One can obtain information about any command with the man command e.g.: man ls To change directory, use the cd command as in cd nameofsubdirectory To go to the parent directory use the command cd .. and to go to your home directory simply type cd Unlike MS/DOS or windows the drectory separator is the / symbol as in bin/form If this is your first time with Linux and you have to install FORM, please go to your home directory and type the ls command. This should show you whether there is a subdirectory called bin. If not, please create this directory with the command mkdir bin Next you are advised to start up FireFox or any other web browser and connect with the FORM site (http://www.nikhef.nl/∼form) and move to the binaries directory where you should select the proper type of binary (this depends on whether you have a computer with a 32-bits architecture or a 64-bits architec- ture, but usually the 32-bits version will also run on the 64-bits computer). You 1 download the FORM program, if possible directly into the bin directory. Next there is an important step to make. Go back to the terminal. If the form file is in your home directory you move it to the bin directory. This can be done with cd mv form bin cd bin The important step is now to make the file executable. If you type the command ls -l form you may find something that starts with -rw-r–r– In that case you and others can read the file and you can write to it, but you cannot execute it. Type the command chmod 755 form and after the next ’ls -l form’ you will see -rwxr-xr-x indicating that the execution flag has been set. And as usual you can find more information about the chmod command by typing man chmod The next thing you have to do is a bit trickier. You will need a text editor. The Linux system has a variety of them. The two main editors are based on either emacs or vi. If you are familiar with one of those you will have an easy time. There are also the products of the ’office’ family, but those are usually not suitable for preparing programs. There is also an editor (with explanations of how to install it) in the FORM distribution. It is called stedi. Below I will assume that you are capable of running an editor of your choice. I will call it ’editor’ in the commands and we will not discuss what commands you should type exactly inside the editor; we will only tell you what has to be done. Now go to your home directory and type editor .cshrc Look whether there is a line that says something like set path = ( . ~/bin $path ) If not, add such a line. This will make the shell program in the terminal find the FORM executable from any directory that you are working in. It means that you need only one copy of FORM. The above .cshrc file works properly if the shell program that is run inside your terminal windows is for instance the tcshell (tcsh). With the bash shell you may have to edit the .bashrc file. There the syntax is slightly different. You have to add the line export PATH=$PATH:~/bin:. Next you can make a subdirectory in your homedirectory that you can use for this course e.g.: cd mkdir course 2 and you can pick up the other files and put them in this directory. I will keep adding files to the dirctory in the FORM distribution. Hence you are advised to check regularly whether there is something new. Sometimes you find a so-called tar file. The word tar stands for tape archive. Of course we don’t have tapes anymore but the name has stayed. It is a file that can contain whole directories and lots of other files and its purpose is to make file transfers easier. It takes much less effort to transfer one file in this way than to try to transfer thousands of small files spread over many directories. Also it makes it easier to compress the files with the gzip program. These files can be recognized by the extensions .tar for the tar file, .gz for a gzipped file and .tar.gz or .tgz for a tar file that has been gzipped. As an example let us take the file kinc.tar.gz which you can pick up from the site. You are to put this file in the subdirectory course and then go to this directory with the command cd course Then you can do either of two things. The first is gunzip kinc.tar.gz tar -xf kinc.tar or in one command tar -xzf kinc.tar.gz In the first case we first uncompress the file, recreating the .tar file and then we unpack its contents. The -xf tells the tar command that you want to extract (x) the contents of the file (f) of which the name follows. In the second command the extra character z says that the name of the file refers to a gzipped file and tar can do everything in one step. The ungzipping and untarring of the kinc.tar.gz file will create a subdirectory kinc with a number of files in it. You can enter this directory with the command cd kinc For the moment we will worry only about the first few examples. You can compile the first example with the command cc test1.c ranf.c -o test1 -lm This command calls the C compiler (called cc) and tells it to translate the files test1.c and ranf.c. It then has to produce an executable by the name test1 (-o indicates the name of the output file. If it is omitted the default name will be a.out) and the -lm means that the math library should be included (-l stands for library and the library that will be searched for in the system is the file libm.a). The math library is needed when we use functions like the square root etc. The program can now be executed with the command test1 Similarly the second example can be compiled with cc test2.c ranf.c -o test2 -lm The third example involves the files main1.c, vegas.c , inplot.c, boundaries.c, ranf.c, fun1.c, iipow.c and ipow.c. This is a bit much to type all the time. Moreover we don’t want to recompile all routines each time we change someting in only one of them. For this any unix system is equipped with a facility named ’make’. In a file named the makefile we tell the system about what files belong 3 to our project and how they should be translated. In the case of this example we have done that in the file make1. Then all we have to do is type make -f make1 and the system looks which files will have to be translated. By looking at the dates of the source files and the object files (the translated files) it can see which source files have been changed since the previous compilation. If you have done all this and there were no problems you should have a file prog1 which contains the executable file of this example which is the first example run of the vegas Monte Carlo integration program. You execute it with the command prog1 For prog2 (the second example) we become a little bit fancier. Again, you can make it with make -f make2 but for the execution this program needs an argument as in prog2 pict2.tex We want here the name of a future file that has the extension .tex because A this file will contain LTEXcode. If everything has gone well, this code can be processed with the commands latex pict2 dvips pict2 -o kghostview pict2.ps The last command starts up the postscript viewer and will show you some of the histograms that were made during the running of the Monte Carlo integration.
Load more

Recommended publications
  • Filesystem Hierarchy Standard
    Filesystem Hierarchy Standard LSB Workgroup, The Linux Foundation Filesystem Hierarchy Standard LSB Workgroup, The Linux Foundation Version 3.0 Publication date March 19, 2015 Copyright © 2015 The Linux Foundation Copyright © 1994-2004 Daniel Quinlan Copyright © 2001-2004 Paul 'Rusty' Russell Copyright © 2003-2004 Christopher Yeoh Abstract This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems. All trademarks and copyrights are owned by their owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder. Dedication This release is dedicated to the memory of Christopher Yeoh, a long-time friend and colleague, and one of the original editors of the FHS.
    [Show full text]
  • Consolidate Home Directories to Improve Workforce Productivity
    Solution brief Consolidate home directories to improve workforce productivity HPE 3PAR File Persona Software Empower and enable users while increasing security Efficient: Improve your primary storage efficiency and control • One-third the data center footprint and significant power savings • One converged capacity eliminates Challenge Truly converged storage for wasted block or file space reservation home directory consolidation Localized user data with inadequate and Effortless: Simplify your storage inefficient protection and control HPE 3PAR StoreServ is highly efficient, deployment and administration Every IT organization has a need to store • Autonomic provisioning of all capacity flash-optimized storage engineered for and manage user-generated data such as the true convergence of block, file, and • Single, simple, and streamlined business documents, images, audio, and administration of block, file, and object access. HPE 3PAR Operating System object access video files. Traditionally, this has been done and converged controllers incorporate in local home directories on individual users’ multi-protocol support into the heart Bulletproof: Deploy your file shares laptops and desktops resulting in higher of the system architecture. This unique with confidence than necessary client device costs, ineffective • Resilient Mesh-Active architecture solution delivers tightly integrated, truly and intrusive backup processes, complex converged storage for provisioning both • Mission-critical proven HPE file system and time-consuming restore processes, and block volumes for server workloads and file poor data governance. IT needs a solution and object shares for client workloads such that maximizes workforce productivity while as home directory consolidation—efficiently, ensuring that data is effectively protected, effortlessly, and without compromise. secured, and controlled—all with minimal cost and effort.
    [Show full text]
  • The Complete Freebsd
    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.
    [Show full text]
  • Filesystem Hierarchy Standard
    Filesystem Hierarchy Standard Filesystem Hierarchy Standard Group Edited by Rusty Russell Daniel Quinlan Filesystem Hierarchy Standard by Filesystem Hierarchy Standard Group Edited by Rusty Russell and Daniel Quinlan Published November 4 2003 Copyright © 1994-2003 Daniel Quinlan Copyright © 2001-2003 Paul ’Rusty’ Russell Copyright © 2003 Christopher Yeoh This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems. All trademarks and copyrights are owned by their owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder. Table of Contents 1. Introduction........................................................................................................................................................1 1.1.
    [Show full text]
  • CS 103 Lab 1 - Linux and Virtual Machines
    CS 103 Lab 1 - Linux and Virtual Machines 1 Introduction In this lab you will login to your Linux VM and write your first C/C++ program, compile it, and then execute it. 2 What you will learn In this lab you will learn the basic commands and navigation of Linux/Unix, its file system, the GNU C/C++ compiler and a few basic applications such as Gedit. Important: The Linux operating system and environment shares a vast majority of commands and methods with Unix. 3 Background Information and Notes 3.1 Software to Install on your PC Start by following the course virtual machine installation instructions found at the link below. http://cs103.usc.edu/tools-and-links/installing-course-vm/ Below is a list of recommended software you should install that will be helpful over multiple courses in CS and EE. These tools allow you to access remote servers, run GUI apps on those servers, and transfer files between your PC and those servers. For Windows: FileZilla FTP – Available from : https://software.usc.edu/index.aspx XWin-32 – Available from : https://software.usc.edu/index.aspx PuTTY – Available from : https://software.usc.edu/index.aspx For Mac: X Server: http://developer.apple.com/opensource/tools/runningx11.html Fetch FTP – Available from : https://software.usc.edu/index.aspx Reference: http://www.usc.edu/its/unix/ Last Revised: 8/29/2014 1 CS 103 Lab 1 - Linux and Virtual Machines 3.2 Getting Started with Unix1 and Accessing your Account Solaris vs. Unix vs. Linux UNIX was developed by AT&T Bell Labs in 1969.
    [Show full text]
  • Downloading and Installing the Mobile Map for IOS, Android, Or Windows Device (See * Below) Common to All Devices: 1
    Downloading and Installing the Mobile Map for IOS, Android, or Windows device (See * below) Common to all devices: 1. Open your browser (see ** below) and return to www.mobilehuntingmaps.com, login and your My Account page will open. 2. On the left side, click on Orders. 3. Your order will appear on the right side of the page. 4. At the end of the order row, click on View to open the details of your order. 5. Beneath the name of the State you will see Download: Download Now and the password needed to open the map file with the CarryMap app. 6. Write down the password then click on Download Now. IOS Devices: (see ** below) 1. Dependent on your version of IOS (Apple operating system) you might be asked a second time to confirm the download. 2. How the download progress is displayed on your phone’s screen varies dependent on the IOS version on your phone. On IOS 12.0 or newer, a blue circle with a down pointing arrow inside will appear and a tiny blue line will move from left to right just under the circle as the download is in progress. Be patient as some of the map data files are large. Dependent on your internet speed and your WIFI strength, the download can take several minutes. Do not try to download a file using a cell phone service, more than likely it will drop before the download is complete. 3. Once the download progress is complete (the blue circle moves up and down and the blue line disappears), the file has been downloaded.
    [Show full text]
  • Introduction to Unix From
    Introduction to Unix from http://cnl.web.arizona.edu Index • Operating Systems • Files • Unix File System o The Path • Ownership and Permissions o Ownership o Permissions • Copy, Move and Remove Files and Directories • Archiving and Zipping • Viewing and Editing Text Files • Size • Unix Help • Tips and Tricks o Cut and Paste o Filename Completion o Find Command o History • Clients and Servers • Communicating across machines Related Resources • Glossary • Printing • Shell Scripts Operating Systems An Operating System (e.g., Windows 95, Windows 98 etc. from Microsoft; Unix systems like Linux, Irix, and Solaris) organizes your files and talks to the hardware. This means the OS translates from the very crude organization system that really exists on your hard drive to the hierarchical system that it presents to you. Essentially, it works like this: The Hard Drive has an area set aside that holds a table of addresses or "pointers" to blocks of information on the rest of the HD. The table's content and organization, the number and size of blocks on the HD etc. are dependent upon the particular OS. Although Unix systems are not exactly the same as each other, they are very similar to one another; just as Windows 95 and Windows 98 are very similar to one another. Files (A Comparison of Windows and Unix) Under Microsoft Windows, file names consist of two parts: a main part and an extension, separated by a special character, the dot (e.g., bird.jpg, fred.xls). The extension tells Windows which program to use to open the file (e.g., *.xls files are opened by MS Excel).
    [Show full text]
  • Linux File System and Linux Commands
    Hands-on Keyboard: Cyber Experiments for Strategists and Policy Makers Review of the Linux File System and Linux Commands 1. Introduction Becoming adept at using the Linux OS requires gaining familiarity with the Linux file system, file permissions, and a base set of Linux commands. In this activity, you will study how the Linux file system is organized and practice utilizing common Linux commands. Objectives • Describe the purpose of the /bin, /sbin, /etc, /var/log, /home, /proc, /root, /dev, /tmp, and /lib directories. • Describe the purpose of the /etc/shadow and /etc/passwd files. • Utilize a common set of Linux commands including ls, cat, and find. • Understand and manipulate file permissions, including rwx, binary and octal formats. • Change the group and owner of a file. Materials • Windows computer with access to an account with administrative rights The Air Force Cyber College thanks the Advanced Cyber Engineering program at the Air Force Research Laboratory in Rome, NY, for providing the information to assist in educating the general Air Force on the technical aspects of cyberspace. • VirtualBox • Ubuntu OS .iso File Assumptions • The provided instructions were tested on an Ubuntu 15.10 image running on a Windows 8 physical machine. Instructions may vary for other OS. • The student has administrative access to their system and possesses the right to install programs. • The student’s computer has Internet access. 2. Directories / The / directory or root directory is the mother of all Linux directories, containing all of the other directories and files. From a terminal users can type cd/ to move to the root directory.
    [Show full text]
  • Permissions and Ownership
    Getting Started with Linux: Novell’s Guide to CompTIA’s Linux+ Objective 1 Understand User and Group Configuration Files Information on users and groups on a Linux system is kept in the following files: ■ /etc/passwd ■ /etc/shadow ■ /etc/group Whenever possible, you should not modify these files with an editor. Instead, use the Security and Users modules in YaST or the command line tools described in the next objective, “Manage User Accounts and Groups from the Command Line” on 7-12. Modifying these files with an editor can lead to errors (especially in /etc/shadow), such as a user—including the user root—no longer being able to log in. To ensure consistency of these files, you need to understand how to ■ Check /etc/passwd and /etc/shadow ■ Convert Passwords to and from Shadow /etc/passwd The file /etc/passwd stores information for each user. In the past, UNIX and Linux users were handled in a single file: /etc/passwd. The user name, the UID, the home directory, the standard shell, and the encrypted password were all stored in this file. The password was encrypted using the function crypt (man 3 crypt). In principle, the plain text password could not be deciphered from the encrypted password. 7-2 Version 2 Use the Command Line Interface to Administer the System However, there are programs (such as john) that use dictionaries to encrypt various passwords with crypt, and then compare the results with the entries in the file /etc/passwd. With the calculation power of modern computers, simple passwords can be “guessed” within minutes.
    [Show full text]
  • User Accounts User Accounts User Info /Etc/Passwd User Info /Etc
    User Accounts Even a single-user workstation (Desktop Computer) uses multiple accounts. Such a computer may have just one user account, but several system accounts help keep the computer running. Accounts enable multiple users to share a single computer without causing each other too much trouble. User Accounts The Users in a Linux system are stored in the /etc/passwd file. If you are on your own VM - somewhere near the bottom you should see yourself and joe. On a brand new install you will see many users listed. Of course if you recall, we only added ourselves and joe. So what are all these other users for? These users are added because we don’t want to give sudo power to all of our programs. So each program installed gets its own user with its own limited permissions. This is a protection for our computer. User Info /etc/passwd Examine the /etc/passwd file using cat or less . Here is what we are seeing: It is colon : separated. So each : denotes a new column. username password The x is just a place-holder. The password is not really in this file User ID (UID) Just like every computer needs a unique ip address, every user needs a unique id. User Info /etc/passwd Group ID (GID) Every user belongs to its own group, with its own group id Comment field This is the Full name, phone number, office number, etc. It is okay if it is blank. Home Directory This is the location of the users home directory - This is how we can know the full path of any users home directory - /home/smorgan vs /home/s/smorgan.
    [Show full text]
  • Linux Filesystem Hierarchy and Hard Disk Partitioning
    LinuxLinux FilesystemFilesystem HierarchyHierarchy andand HardHard DiskDisk PartitioningPartitioning Moreno Baricevic CNR-IOM DEMOCRITOS Trieste, ITALY FileFile SystemSystem A file system is a set of methods and data structures used to organize, store, retrieve and manage information in a permanent storage medium, such as a hard disk. Its main purpose is to represent and organize storage resources. FileFile System:System: elementselements Name space: is a way to assign names to the items stored and organize them hierarchically. API: is a set of calls that allow the manipulation of stored items. Security Model: is a scheme to protect, hide and share data. Implementation: is the code that couples the logical model to the storage medium. 3 FileFile Systems:Systems: BasicBasic ConceptsConcepts (1/2)(1/2) Disk: A permanent storage medium of a certain size. Block: The smallest unit writable by a disk or file system. Everything a file system does is composed of operations done on blocks. Partition: A subset of all the blocks on a disk. Volume: The term is used to refer to a disk or partition that has been initialized with a file system. Superblock: The area of a volume where a file system stores its critical data. 4 FileFile Systems:Systems: BasicBasic ConceptsConcepts (2/2)(2/2) Metadata: A general term referring to information that is about something but not directly part of it. For example, the size of a file is very important information about a file, but it is not part of the data in the file. Ownerships, access permissions, creation/modification/access time, are also part of the metadata information pertaining a file.
    [Show full text]
  • Working with the File System, Configuration Files, and Software Images
    Working with the File System, Configuration Files, and Software Images This appendix describes how to manipulate the router flash file system, how to copy configuration files, and how to download software images to a router. Working with the File System Working with Configuration Files Working with Software Images Working with the File System Commands in this document use URLs as part of the command syntax. URLs used in the Cisco 910 Industrial Router file system contain the following two parts: File system or network prefix File identification suffix The following tables list URL keywords that can be used in the source-url and destination-url arguments for all commands in this document. The prefixes listed below can also be used in the filesystem arguments in this document. Table 5 lists common URL network prefixes used to indicate a device on the network. Table 5 Network Prefixes, Descriptions, and Formats Prefix Description Format ftp Specifies a File Transfer Protocol [[//[username[:password]@]location]/directory]/filename (FTP) network server. For example: ftp://network-config (prefix://filename) ftp://jeanluc:[email protected]/ship-config tftp Specifies a TFTP server. tftp:[[//location]/directory]/filename Table 6 common URL prefixes used to indicate memory locations on the system. Cisco Systems, Inc. www.cisco.com 1 Working with the File System, Configuration Files, and Software Images Table 6 URL Prefixes and Descriptions Prefix Description flash0 On board NAND flash memory, corresponding to /dev/mtd6 which is mounted as /mnt/apps. flash1 On board NAND flash memory, corresponding to /dev/mtd7 which is mounted as /mnt/data.
    [Show full text]