6 messages in org.freebsd.freebsd-fsRe: Mount bogosity| From | Sent On | Attachments |
|---|---|---|
| Eivind Eklund | Jan 14, 1999 5:55 pm | |
| Don Lewis | Jan 14, 1999 6:27 pm | |
| Eivind Eklund | Jan 14, 1999 8:19 pm | |
| Robert Watson | Jan 15, 1999 5:47 am | |
| Terry Lambert | Jan 15, 1999 2:23 pm | |
| Terry Lambert | Jan 15, 1999 2:29 pm |
| Subject: | Re: Mount bogosity | |
|---|---|---|
| From: | Robert Watson (rob...@cyrus.watson.org) | |
| Date: | Jan 15, 1999 5:47:57 am | |
| List: | org.freebsd.freebsd-fs | |
On Thu, 14 Jan 1999, Don Lewis wrote:
This stuff is kind of bogus. If you do a mount while chrooted, the full path to the mount point isn't recorded, so mount only displays the partial path. How are you supposed to find the mount point again?
It would be nice if the path to the chroot directory was preserved so that the full path could be recorded in the kernel, but this sort of goes against the grain of the Unix philosophy.
Even with the full path name in the mount table, you can still mess things up by renaming one of the intermediate directories ...
Having a 'full path name' for an arbitrary file at a useful time (prior or after its vnode lookup) would be great for a number of applications (well, kernel features :) that need to report to the user. This includes auditing support, where having a name guaranteed unique at the time where it is used. Also useful, but possibly more prone to pain, would be a vnode->name facility.
Posix.1e auditing references filenames in the audit records, hence my interest at this point.
Robert N Watson
rob...@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C
Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message