It really looks to me like you are expected to use system calls like chmod(), unlink(), and
nftw() or readdir(). Embedding shell commands does not appear (to me) to be what is expected.
When you delete a directory, you have to delete all the files in the directory first. Then unlink the directory itself. Exactly what
open, creat, read, write, lseek and close
Are they all primitive?
:confused:
*Another Question: is there a different between a system call, and an i/o system call? (2 Replies)
Hi,
I'm new to UNIX system calls. Can someone share your knowledge as to how exactly system calls should be executed?
Can they be typed like commands such as mkdir on the terminal itself? Also, are there any websites which will show me an example of the output to expect when a system call like... (1 Reply)
Hello,
how would i be able to call ps in C programming?
thanks,
---------- Post updated at 01:39 AM ---------- Previous update was at 01:31 AM ----------
here's the complete system call, ps -o pid -p %d, getpit() (2 Replies)
Hi friends,
I have three questions.
1) What are system calls?
2) Is it necessary that system calls be in c language (in unix operating system)?
3) Importance of c language when programming in unix environment???
Looking forward to your wonderful replies!
... (2 Replies)
Hi friends,
I hope everyone is fine and doing well. I queried in my previous thread about the low-level qualities of C/C++ languages.I really thank you people for explaining, it was really helpful. One more ambiquity that I have in my mind is regarding the unix system calls like open, creat,... (1 Reply)
Discussion started by: gabam
1 Replies
LEARN ABOUT OSF1
unlink
link(1) General Commands Manual link(1)NAME
link, unlink - Creates an additional directory entry for an existing file
SYNOPSIS
link file1 file2
unlink file
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link: XCU5.0
unlink: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The link command performs the link() system call to create an additional directory entry for an existing file, file1. In effect, the
underlying file then has two names, file1 and file2 (either of these arguments can be a pathname). The old and new entries share equal
access rights to the underlying file.
The unlink command performs the unlink() system call to remove a link to file created by link. The unlink command removes the directory
entry specified by the file parameter and, if the entry is a hard link, decrements the link count of the file referenced by the link.
You should be familiar with the link() and unlink() system calls before you use these commands.
The link and unlink commands do not issue error messages when the associated system call is unsuccessful.
NOTES
The link and unlink commands cannot be used to link and unlink directories.
EXIT STATUS
The link and unlink commands both exit with the following: The link() or unlink() system call succeeded. Too few or too many arguments
specified. The link() or unlink() system call failed.
SEE ALSO
Commands: fsck(8), ln(1)
Functions: link(2), unlink(2)link(1)