11-15-2007
The source code on opensolaris indicates that message means that the chmod system call failed. So I'm guessing it's a loopback mount or something like that. What does this show:
mount -v
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am working on a new UNIX box that has been delivered to us, and noticed that the /home directory has 555 permissions on it (dr-xr-xr-x). Any attempt to create write permissions fails on this directory (such as chmod 777), responding only with a message;
chmod: WARNING: can't change home
... (3 Replies)
Discussion started by: ncarmstrong
3 Replies
2. UNIX for Dummies Questions & Answers
i am unable to write to some .php files in the following directory:
drwxr-xr-x 3 headroom max 448 Jun 6 2004 Docs
i already tried this:
chmod +777 Docs
chmod: changing permissions of `Docs': Operation not permitted
thanks for your help! (2 Replies)
Discussion started by: phonedog365
2 Replies
3. UNIX for Dummies Questions & Answers
I was attempting to change permissions on a directory, used a 'chmod -rwrwrw DirectoryName' command, and hit enter. Now, that directory shows that it's empty! How could this be? Any Ideas?
Thanks (1 Reply)
Discussion started by: SmooBG
1 Replies
4. Shell Programming and Scripting
Hi,
I am unable to see all files in a current directory when use "ls -lrt" command
it is giving error message as below ( I think this current directory is having about 500 files)
<CONTROL /home/ckanth/sri>ls -lrt
UX:ls: ERROR: Out of memory: Insufficient or invalid memory
But when i... (3 Replies)
Discussion started by: srikanthus2002
3 Replies
5. UNIX for Advanced & Expert Users
Version-Release number of selected component (if applicable):
==================================================================
root@server # cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 5)
root@server # uname -a
Linux server.integrityserver.net... (16 Replies)
Discussion started by: fed.linuxgossip
16 Replies
6. UNIX for Dummies Questions & Answers
rm: Unable to remove directory /mnt/users/test/logs/: File exists
ls -latr
total 191208
drwxrwxrwx 6 test echo 4096 Jul 3 22:36 ..
-rwxrwxrwx 1 test echo 97692804 Jul 3 22:36 .nfsDFA4
drwxrwxr-x 2 test echo 4096 Jul 3 23:00 .
M not able to delete... (4 Replies)
Discussion started by: solitare123
4 Replies
7. Programming
sprintf(fname, "core.%d", pid);
(void) unlink(fname);
if (ttrace(TT_PROC_CORE, pid, 0, 0, 0, 0) != 0) {
perror("TT_PROC_CORE pass");
Fail();
}
if (chmod(fname, 0) != 0) {
perror("chmod");
Fail();
}
Hi,
If i execute above code,everytime am getting below... (1 Reply)
Discussion started by: mansa
1 Replies
8. UNIX and Linux Applications
i think it is the same in both... Iam i right? (1 Reply)
Discussion started by: sumaiya
1 Replies
9. Red Hat
I am having trouble figuring out how to do a "chmod o-w" for all files under a certain directory, while excluding directories under that certain directory.
I can do
chmod -R o-w /thisdirectory
but that changes permissions of all directories under the directory as well as files. I just... (2 Replies)
Discussion started by: austinharris43
2 Replies
10. Shell Programming and Scripting
does anyone know how to exclude a directory with chown or chmod?
im trying to do something like this
chown $username:$username $directory/*
chown $username:$username $directory/.*
chown $username:$username $directory
and
find $directory/* -type f -exec... (1 Reply)
Discussion started by: vanessafan99
1 Replies
lofs(7FS) File Systems lofs(7FS)
NAME
lofs - loopback virtual file system
SYNOPSIS
#include <sys/param.h>
#include <sys/mount.h>
int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0);
DESCRIPTION
The loopback file system device allows new, virtual file systems to be created, which provide access to existing files using alternate
pathnames. Once the virtual file system is created, other file systems can be mounted within it, without affecting the original file sys-
tem. However, file systems which are subsequently mounted onto the original file system are visible to the virtual file system, unless or
until the corresponding mount point in the virtual file system is covered by a file system mounted there.
virtual is the mount point for the virtual file system. dir is the pathname of the existing file system. mflag specifies the mount options;
the MS_DATA bit in mflag must be set. If the MS_RDONLY bit in mflag is not set, accesses to the loop back file system are the same as
for the underlying file system. Otherwise, all accesses in the loopback file system will be read-only. All other mount(2) options are
inherited from the underlying file systems.
A loopback mount of '/' onto /tmp/newroot allows the entire file system hierarchy to appear as if it were duplicated under /tmp/newroot,
including any file systems mounted from remote NFS servers. All files would then be accessible either from a pathname relative to '/' or
from a pathname relative to /tmp/newroot until such time as a file system is mounted in /tmp/newroot, or any of its subdirectories.
Loopback mounts of '/' can be performed in conjunction with the chroot(2) system call, to provide a complete virtual file system to a
process or family of processes.
Recursive traversal of loopback mount points is not allowed. After the loopback mount of /tmp/newroot, the file /tmp/newroot/tmp/newroot
does not contain yet another file system hierarchy; rather, it appears just as /tmp/newroot did before the loopback mount was performed
(for example, as an empty directory).
Examples
lofs file systems are mounted using:
mount -F lofs /tmp /mnt
SEE ALSO
lofiadm(1M), mount(1M), chroot(2), mount(2), sysfs(2), vfstab(4), lofi(7D)
WARNINGS
Loopback mounts must be used with care; the potential for confusing users and applications is enormous. A loopback mount entry in
/etc/vfstab must be placed after the mount points of both directories it depends on. This is most easily accomplished by making the loop-
back mount entry the last in /etc/vfstab.
SunOS 5.10 10 Apr 2001 lofs(7FS)