dev(4fs) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

dev(4fs)

dev(4FS)                         File Systems                         dev(4FS)

NAME
       dev - Device name file system

DESCRIPTION
       The dev filesystem manages the name spaces of devices under the Solaris
       operating  system.  The global zone's instance of the dev filesystem is
       mounted during boot on /dev.


       A subdirectory under /dev can have unique operational  semantics.  Most
       of  the common device names under /dev are created automatically by de‐
       vfsadm(8). Others, such as /dev/pts, are dynamic and reflect the opera‐
       tional state of the system. You can manually generate device names  for
       newly attached hardware by invoking devfsadm(8) or implicitly, by indi‐
       rectly  causing  a lookup or readdir operation in the filesystem to oc‐
       cur. For example, you can discover a disk that was  attached  when  the
       system was powered down (and generate a name for that device) by invok‐
       ing format(8).


       The /dev/zvol/dsk and /dev/zvol/rdsk directories are generated based on
       the  ZFS  dataset  hierarchy.  Each  ZFS  file system is represented in
       /dev/zvol/dsk and /dev/zvol/rdsk as a directory. Each  ZFS  volume  and
       each  snapshot  of  a  ZFS  volume  is represented as a block device in
       /dev/zvol/dsk and as a character device in /dev/zvol/rdsk.  Within  the
       global  zone,  symbolic  links to device nodes within /devices are used
       instead of device nodes. See devfs(4FS).


       Within non-global zones, the names that appear under  /dev/zvol  repre‐
       sent the aliased dataset names. See zonecfg(8).


       Within  non-global  zones,  devices that are added by way of device re‐
       sources can have the same name as those  that  appear  in  the  aliased
       dataset  namespace. See zonecfg(8). If such conflicts occur, the device
       file corresponding to the device resource is seen and any corresponding
       /dev/zvol entries for datasets that are delegated to the  zone  is  not
       seen.  For example, if the device /dev/zvol/rdsk/rpool/vol1 is added as
       a device resource  and  the  within  the  non-global  zone  the  volume
       rpool/vol1 is created, the file /dev/zvol/rdsk/rpool/vol1 is the device
       allocated  from  the  global  zone, not the one that appears within the
       non-global zone's aliased dataset namespace.

FILES
       /dev    Mount point for the /dev filesystem in the global zone.


SEE ALSO
       devfs(4FS), devfsadm(8), format(8), zonecfg(8)

NOTES
       The global /dev instance cannot be unmounted.

Oracle Solaris 11.4               14 Jun 2024                         dev(4FS)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3