Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

fss(4) [netbsd man page]

FSS(4)							   BSD Kernel Interfaces Manual 						    FSS(4)

NAME
fss -- file system snapshot device SYNOPSIS
pseudo-device fss 4 DESCRIPTION
The fss driver provides a read-only interface to the snapshot of a currently mounted file system. Reading from a fss device gives the view of the file system when the snapshot was taken. It can be configured via ioctl(2). IOCTLS
The ioctl(2) command codes below are defined in <sys/dev/fssvar.h>. The (third) argument to ioctl(2) should be a pointer to the type indicated. FSSIOCSET(struct fss_set) Configures a fss device. struct fss_set { char *fss_mount; char *fss_bstore; blksize_t fss_csize; int fss_flags; }; The struct element fss_mount is the mount point of the file system. The struct element fss_bstore is either a regular file or a raw disk device where data overwritten on the file system will be saved. The struct element fss_csize is the preferred size of this data. The struct element fss_flags is the initial set of flags. FSSIOCGET(struct fss_get) Gets the status of a fss device. struct fss_get { char fsg_mount[MNAMELEN]; struct timeval fsg_time; blksize_t fsg_csize; blkcnt_t fsg_mount_size; blkcnt_t fsg_bs_size; }; The struct element fsg_mount is the mount point of the file system. The struct element fsg_time is the time this snapshot was taken. The struct element fsg_csize is the current size of data clusters. The struct element fsg_mount_size is the number of clusters of the file system. The struct element fsg_bs_size is the number of clusters written to the backing store. FSSIOCCLR Unconfigures a fss device. FSSIOFSET(int) Sets the flags of a fss device. Possible flags are: FSS_UNCONFIG_ON_CLOSE Unconfigure the fss device on the last close. FSS_UNLINK_ON_CREATE Unlink the backing file before the fss device is created. FSSIOFGET(int) Gets the flags of a fss device. KERNEL THREADS
For each active snapshot device there is a kernel thread that handles the backing store. This thread is named fssN where N is the device minor number. FILES
/dev/rfss? /dev/fss? SEE ALSO
fssconfig(8), mount(8), umount(8) HISTORY
The fss device appeared in NetBSD 2.0. BSD
February 24, 2011 BSD

Check Out this Related Man Page

UHID(4) 						   BSD Kernel Interfaces Manual 						   UHID(4)

NAME
uhid -- USB generic HID support SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device uhid Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): uhid_load="YES" DESCRIPTION
The uhid driver provides support for all HID (Human Interface Device) interfaces in USB devices that do not have a special driver. The device handles the following ioctl(2) calls: USB_GET_REPORT_ID (int) Get the report identifier used by this HID report. USB_GET_REPORT_DESC (struct usb_ctl_report_desc) Get the HID report descriptor. Using this descriptor the exact layout and meaning of data to/from the device can be found. The report descriptor is delivered without any processing. struct usb_ctl_report_desc { int ucrd_size; u_char ucrd_data[1024]; /* filled data size will vary */ }; USB_SET_IMMED (int) Sets the device in a mode where each read(2) will return the current value of the input report. Normally a read(2) will only return the data that the device reports on its interrupt pipe. This call may fail if the device does not support this feature. USB_GET_REPORT (struct usb_ctl_report) Get a report from the device without waiting for data on the interrupt pipe. The report field indicates which report is requested. It should be UHID_INPUT_REPORT, UHID_OUTPUT_REPORT, or UHID_FEATURE_REPORT. This call may fail if the device does not support this feature. struct usb_ctl_report { int ucr_report; u_char ucr_data[1024]; /* used data size will vary */ }; USB_SET_REPORT (struct usb_ctl_report) Set a report in the device. The report field indicates which report is to be set. It should be UHID_INPUT_REPORT, UHID_OUTPUT_REPORT, or UHID_FEATURE_REPORT. This call may fail if the device does not support this feature. Use read(2) to get data from the device. Data should be read in chunks of the size prescribed by the report descriptor. Use write(2) to send data to the device. Data should be written in chunks of the size prescribed by the report descriptor. FILES
/dev/uhid? SEE ALSO
usbhidctl(1), usb(4) HISTORY
The uhid driver appeared in NetBSD 1.4. This manual page was adopted from NetBSD by Tom Rhodes <trhodes@FreeBSD.org> in April 2002. BSD
November 22, 2006 BSD
Man Page