Sponsored Content
Top Forums UNIX for Dummies Questions & Answers is /. superfluous? why not just say / ? Post 302079057 by Perderabo on Thursday 6th of July 2006 03:10:10 PM
Old 07-06-2006
Every directory is required to have an actual entry called . and another called .. and . is required to be a link to the directory that contains it. As long as everything is hunky-dory, / and /. are pretty similar. The second one takes longer since after finding / we look inside to find . and then we open that. Should the . entry be damaged, the open might fail or it might open some other file. But I don't recall ever seeing anyone open /. in that form.
 

We Also Found This Discussion For You

1. Shell Programming and Scripting

Perl: How to avoid warnings for superfluous values returned?

Hi all, a question for the Perl knowledgeable: I have use warnings; enabled. I use something like: ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); In the further code I only work with some of the returned variables, as the others I have no need for. Though the... (1 Reply)
Discussion started by: zaxxon
1 Replies
UNLINK(2)							System Calls Manual							 UNLINK(2)

NAME
unlink - remove directory entry SYNOPSIS
#include <unistd.h> int unlink(const char *path) DESCRIPTION
Unlink removes the entry for the file path from its directory. If this entry was the last link to the file, and no process has the file open, then all resources associated with the file are reclaimed. If, however, the file was open in any process, the actual resource recla- mation is delayed until it is closed, even though the directory entry has disappeared. RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
The unlink succeeds unless: [ENOTDIR] A component of the path prefix is not a directory. [ENAMETOOLONG] The path name exceeds PATH_MAX characters. [ENOENT] The named file does not exist. [EACCES] Search permission is denied for a component of the path prefix. [EACCES] Write permission is denied on the directory containing the link to be removed. [ELOOP] Too many symbolic links were encountered in translating the pathname. (Minix-vmd) [EPERM] The named file is a directory. [EPERM] The directory containing the file is marked sticky, and neither the containing directory nor the file to be removed are owned by the effective user ID. (Minix-vmd) [EBUSY] The entry to be unlinked is the mount point for a mounted file system. [EIO] An I/O error occurred while deleting the directory entry or deallocating the inode. [EROFS] The named file resides on a read-only file system. [EFAULT] Path points outside the process's allocated address space. SEE ALSO
close(2), link(2), rmdir(2). 4th Berkeley Distribution May 22, 1985 UNLINK(2)
All times are GMT -4. The time now is 09:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy