Plus the dev directory usually has some soft links and sub-directories to help organize things. And then the dev directory, notice that contains device files and there's two kinds, character and block device files. And a non-privileged user creating a device file and giving themselves write permission, could allow a non-privileged user to write to a device when we don't want to allow that. It is common though, that for security reasons, things like removable media that could be mounted by an ordinary non-privileged user, that media not be allowed to have device files because permissions on device files means something. So device files are typically in /dev or one of its sub-directories, although they could be elsewhere. It can also manipulate device files like change their permission modes. So, the Linux kernel itself and privileged users and certain services can add entries to the dev directory, can dynamically create device files.

Device files are recreated dynamically when the system is booted and as modules are loaded. The /dev directory these days is usually a Ram-based temp file system. And we need to talk about kinds of device files and how do we or how are device files created? And that leads to a discussion of how device files are often automatically created. To talk more about device files, we need to talk about the /dev directory. Device files are the means for processes to interact with character and block device drivers.

Creating character device in linux