Sponsored Content
Full Discussion: How to insert EOL?
Operating Systems Linux How to insert EOL? Post 302788229 by PikK45 on Monday 1st of April 2013 09:56:46 AM
Old 04-01-2013
  1. Open the file in some editor
  2. go to the last character of the file, press enter Smilie
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Sendmail, EOL not effecting

Hello, I am using the following script to read some log and then contruct my email for notification. When I run this on my test server, i am getting the output as below, But when I move to another server, the EOL seems to not affect, should I use some setting so the output is... (1 Reply)
Discussion started by: cv_pan
1 Replies

2. Shell Programming and Scripting

removing special characters @ EOL

How to remove special chracters @ END OF EACH LINE in a file file1.txt: 0003073413^M 0003073351^M 0003073379^M 0003282724^M 0003323334^M 0003217159^M 0003102760^M 0002228911^M I used the below command but it is not working ? perl -pi -e 's/^M\/g' file1.txt (6 Replies)
Discussion started by: ali560045
6 Replies

3. Shell Programming and Scripting

Remove EOL selectively

Hi, I have a text as below test1 test2 test3\ test4 test5 test6 test7 newtest1 newtest2\ newtest3 newtest4 newtest5 And need this to be replaces to test1 test2 test3 test4 test5 test6 test7 newtest1 newtest2 newtest3 newtest4 newtest5 So my requirement is to remove the EOL... (5 Replies)
Discussion started by: praveenbvarrier
5 Replies

4. How to Post in the The UNIX and Linux Forums

Delete to eol after PASS with sed

working on script and saving ftp log before log save want to remove the password password appears after constant "PASS" thanks pp (1 Reply)
Discussion started by: ppaprota
1 Replies

5. Shell Programming and Scripting

Delete to eol after pattern with sed

working on interactive ftp script saving log and want to remove the password from log so "quote PASS foofoo" would become "quote PASS XXXXXXX" replacing or removing the password is of no matter have tried several sed commands but have only been successful with character matching not pattern ... (2 Replies)
Discussion started by: ppaprota
2 Replies

6. AIX

How to remove ^M from the EOL?

The only way I know of is manually as follows: To remove for example ^M from a file: - vi the file name that has ^M at the end of each line. - Hit <Esc> - Type :g/ - Hold the CNTRL key and press V and M then release the CNTRL key At the buttom you should see this by now: ... (3 Replies)
Discussion started by: mrn6430
3 Replies

7. OS X (Apple)

No eol in swap file

I was editing a file with vi and crashed so when I opened the file again I had the .swp file to deal with. I made the wrong choice trying to recover my file and wound up with a file with no eol (end of line) characters. I have forgotten the code to substitute and don't want to make an even... (2 Replies)
Discussion started by: gale
2 Replies

8. What is on Your Mind?

Internet Explorer EOL

Hard to imagine that in the two decades of its existence this product once ruled supreme, but the news is finally there: RIP Internet Explorer: Twitter mourns and mocks death of Microsoft (0 Replies)
Discussion started by: figaro
0 Replies
packingrules(4) 					     Kernel Interfaces Manual						   packingrules(4)

NAME
packingrules - packing rules file for cachefs DESCRIPTION
is a packing rules file for packingrules contains a list of directories and files that are to be packed. It also contains a list of direc- tories and files that are to be specifically excluded from packing. See cachefspack(1M). Many users choose to manually create the packing rules file and edit it by hand. Users can edit the packingrules (using any editor) to permanently change the packingrules file, or to gain access to more powerful options that are not available from the command line (such as the command). It is much easier to enter complex wildcard expressions by editing the packingrules file. Following is a description of the lines in a packing rules file. Blank lines and lines that begin with a pound sign are ignored. Lines can be continued by placing a backslash () immediately before the newline character. All other lines in the packingrules file have one of the following formats: This line identifies a directory (or pair of directories) under which files should be packed. At least one directory name must be specified. The arguments must be fully qualified path names and may include environment variables. This line enumerates a list of files and subdirectories beneath the current directory to be packed. This specification is recursive. That is, specifying the name of a directory automatically includes all files and subdirectories it contains. This line enumerates a list of files that are not to be packed. Regular expressions are permitted. There are important differences between the arguments to the and the statements. The arguments to statements can contain slashes and are interpreted as file names relative to the directories. The arguments to statements are simpler names or expressions that cannot contain slashes. An statement will not override a LIST statement. statements only exclude files that are found beneath listed directories. If the first name argument to a or an statement begins with an exclamation point the remainder of the statement will be executed as a com- mand that will be run in the current directory. The output of the command will be treated as a list of newline separated file names to be packed command) or to be excluded from the packing list command). For the command, the resulting file names will be interpreted relative to the enclosing directory. Blanks can be embedded in an argument by escaping them with a backslash () or enclosing the argument in double quotes (` " '). Double quotes can be passed in arguments by escaping the double quotes with a backslash (). lines only apply to the statement that precedes them. lines can appear before any statement (in which case they apply to all or after a statement (in which case they only apply to the that precedes them). Any number of these statements can occur in any combinations. The order is not important. EXAMPLES
The use of these statements is illustrated in the following packing rules file. # # Ignore junk files. # IGNORE core *.o *.bak *% # # Pack everything in the work subdirectory and in a few # favorite mailboxes. # BASE /net/bigserver/export/home/myname LIST work LIST m/incoming LIST m/action LIST m/pending # # Pack two important project directories but skip # all postscript output. # BASE /net/bigserver/export/projects $HOME/projects LIST poindexter epiphany IGNORE *.ps # # Pack the foonly package. # BASE /net/bigserver/opt/foonly /opt/foonly LIST !cat .packinglist # # Also pack the latest executables for the standard # build environment. # BASE /net/bigserver/export/buildenv $HOME/buildenv LIST !find . -type f -a -perm -111 -a -print AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
cachefspack(1M). packingrules(4)
All times are GMT -4. The time now is 12:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy