07-16-2011
5 Unix things you wish you knew as a beginner...
I am trying to get better at UNIX, and I wanted to post a question so I can take some advice from more experienced programmers. What are some things that you wished you knew (while you were learning UNIX) that you think every beginner should know?
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi my name is Jenny.
I'm a very very big beginner with UNIX.
I've made Forms on my website, but need to add CGI to compliment them.
Presently, I don't have a host that supports UNIX.
Is there anywhere I can connect to a UNIX session for free?
If so, will they most likely have the latest... (2 Replies)
Discussion started by: JennyW
2 Replies
2. UNIX for Dummies Questions & Answers
Due to my new job I need to learn Unix to advance in the company and I am mainly a windows and mac user. What is a good book to get me started on the right path and hopefully prevent me from wasting money on several books and weeks of reading. Any response is welcomed thanks in advance. (3 Replies)
Discussion started by: windowsux
3 Replies
3. UNIX for Dummies Questions & Answers
I am really confused as to how to install a piece of software on Unix especially after having worked with Windows for over 10 years.
I see the tar.gz, tar.gz2 and rpm packages.
How do I install these things? Do I have to be a root to do this?
If its only the root, then how do users generally... (4 Replies)
Discussion started by: Legend986
4 Replies
4. Shell Programming and Scripting
Hey all I'm working on a script that will scour a directory of 6000+ files for a line that at the end has a number.
Something like 'The number of outputs is: 39200'
I'm trying to devise a script to add all of these numbers up, so far I have the grep statement that pulls out each individual... (7 Replies)
Discussion started by: TiznaraN
7 Replies
5. Shell Programming and Scripting
how do i implement a script that asks user to input a word. it should ask for input a word continuously until the word is longer than 5 characters then stop.
this is what i have so far
#!/bin/bash
read -p "enter word" word1
while ; do
echo "continue"
done (4 Replies)
Discussion started by: marcusstar10
4 Replies
6. Shell Programming and Scripting
Hi there,
I want to ask you guys what you think about my problem.
I work as a sysadmin on about 7000 workstations or so and to save money and energy, we've decided to switch off as many workstations as possible during the night (probably by shutting it down by cron and power it on by... (8 Replies)
Discussion started by: albator1932
8 Replies
7. HP-UX
Hello All,
I am working in HP unix since 5 years on application and support. But in order to get opportunity out side i need to learn admintration Can somebody help me to guide hot start for this. Do we have any doc(pdf) to start with.
Thanks
Krsnadasa (1 Reply)
Discussion started by: krsnadasa
1 Replies
8. UNIX for Dummies Questions & Answers
I am a beginner and have recently started to study unix. I checked some of the posts on this forum just to check if a new member like me can easily be guided and found it very interesting. This seems like a great place where i can get answer to my doubts and questions.
I checked the thread for... (1 Reply)
Discussion started by: kaal
1 Replies
LEARN ABOUT OPENDARWIN
end
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)