Pawel Jakub Dawidek fa1abc314f The ufs_disk_fillout(3) can take special device name (with or without /dev/ ... prefix) as an argument and mount point path. At the end it has to find device name file system is stored on, which means when mount point path is given, it tries to look into /etc/fstab and find special device corresponding to the given mount point. This is not perfect, because it doesn't handle the case when file system is mounted by hand and mount point is given as an argument. I found this problem while trying to use snapinfo(8), which passes mount points to the ufs_disk_fillout(3) function, but I had file system mounted manually, so snapinfo(8) was exiting with the error below: ufs_disk_fillout: No such file or directory I modified libufs(3) to handle those arguments (the order is important): 1. special device with /dev/ prefix 2. special device without /dev/ prefix 3. mount point listed in /etc/fstab, directory exists 4. mount point listed in /etc/fstab, directory doesn't exist 5. mount point of a file system mounted by hand		2007-03-16 03:13:28 +00:00
..
block.c
bread.3
cgread.3
cgroup.c
inode.c
libufs.3
libufs.h
Makefile
sblock.c
sbread.3
type.c	The ufs_disk_fillout(3) can take special device name (with or without /dev/	2007-03-16 03:13:28 +00:00
ufs_disk_close.3