Messages in this thread | | | Date | Fri, 15 Aug 1997 10:42:21 +0200 | From | Janos Farkas <Janos.Farkas-#QK62Trgra5Kf5.RZk0HZ1/> | Subject | chflags() or...? [not: Re: Ext2fs getting hosed by fsck] |
| |
On 1997-08-10 at 18:47:56, Theodore Y. Ts'o wrote: > From: "Stephen R. van den Berg" <srb@cuci.nl> >> Naturally (?), the kernel does not allow me to unlink these >> contraptions: > >> unlink("#45135") = -1 EPERM (Operation not permitted) > > These files are character devices that have the immutable bit set. > Unfortunately, due to a lack of a chflags() system call (working on it), > you can't clear the immutable bit easily.
Hmm.. I was a bit tired recently, and thought about something like a new syscall to open an _inode_, but later realised that it could be done with a flag to open(), maybe O_INODE, O_NOFOLLOW, or whatever.
Does that sound too ill? If it fits into VFS somehow, it could be a quick solution to:
- changing flags/attributes on device special files - changing attributes on symlinks (currently can't set immutable for instance) - and in general, making fchmod() and other fwhatever() work on symlinks, and device special files.
The kernel is already doing this for some things that needs to work on symlinks et al.
For extreme sillyness, we could have an usable funlink() too. :)
-- Janos - Don't worry, my address works. I'm just bored of spam.
| |