08-10-2007
Being new to UNIX, using the editor VI has previously proved to be a bit of a challenge and has taken some time to come to terms with the different keys that should be used for navigating around VI.
However, since posting this topic I have been on a UNIX course and have a much better understanding now of permissions, FTP, VI and much more
:-)
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
I'm new to UNIX and new to this forum, so forgive my lack of knowledge. I'm new with editing in vi so I FTP scripts to a Windows machine and edit the script in notepad (when I need to do something quickly). Sometimes when I FTP the script back to the UNIX box, strange characters... (4 Replies)
Discussion started by: dgower2
4 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I want to show my output for the script to notepad.Anybody know what is the command to do this...
Thanks.. (7 Replies)
Discussion started by: mastercar
7 Replies
3. Solaris
i have a file which i open in wordpad shows proper formated o/p column wise .. but same file which is txt file when i do cat in solaris shows grabbled o/p is there any way i can see the output same as wordpad or txt pad ? even in solaris ?
Following is the o/o when i do a #cat file.txt | more... (8 Replies)
Discussion started by: fugitive
8 Replies
4. UNIX for Dummies Questions & Answers
Hi,
just quick question, I currently type up my scripts in Notepad++ and then copy them into my file (in VI).
However, i've noticed that all the lines get messed up and it becomes difficult to read the script.
so i've to spend time then using '\' at the end of lines etc and re-formatting... (7 Replies)
Discussion started by: horhif
7 Replies
5. Windows & DOS: Issues & Discussions
I connect to my office server using ftp option in notepad++
I am not able to open directory's with out setting my clear case view in the notepad++
Hence pls help me in setting the view in notepad++ so that it can read all the files and directorys (6 Replies)
Discussion started by: Syed Imran
6 Replies
GET_END(3) Library Functions Manual GET_END(3)
NAME
get_end, get_etext, get_edata - get values of UNIX link editor defined symbols
SYNOPSIS
#include <mach-o/getsect.h>
unsigned long get_end();
unsigned long get_etext();
unsigned long get_edata();
DESCRIPTION
These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols. Use of these routines is very strongly
discouraged. The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions
that the program has the memory layout of a UNIX program.
This is an incorrect assumption for a program built by the Mach-O link editor. The reason that these routines are provided is that if very
minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the pro-
gram, some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym-
bols. So use at your own risk, and only if you know what your doing. Or better yet, convert the program to use the appropriate Mach or
Mach-O functions. If you are trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use
vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions.
The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata, and get_end
respectively. In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note
this my or may not be the only section in the __TEXT segment. get_edata returns the first address after the (__DATA,__data) section, note
this my or may not be the last non-zero fill section in the __DATA segment. get_end returns the first address after the last segment in
the executable, note a shared library may be loaded at this address.
SEE ALSO
ld(1), dyld(3)
Apple Computer, Inc. April 10, 1998 GET_END(3)