Names in case you decide to boot with devfs disabled.
名字，以备日后您决定禁用devfs引导之需。
The second option, Debug devfs, should also be disabled.
第二个选项，Debugdevfs，也应该被禁用。
And this is the problem with having the kernel mount devfs.
这就是用内核安装devfs存在的问题。
The benefits of devfs, the device management filesystem (Part 4).
设备管理文件系统，devfs的好处(第4部分)。
Completing the conversion to devfs using an init wrapper (Part 6).
用init封装器完成到devfs的转换(第6部分)。
If you do, the devfs variable will be set to no; otherwise, it'll be yes.
如果这么做的话，devfs变量将被设置成no；否则它将被设置成yes。
Don't fear, we're just one step away from completing our transition to devfs.
不用担心，我们离完成转换到devfs只有一步之遥。
Until then, check out the following resources for more information about devfs
在那之前，请参考下面的参考资料以了解更多关于 devfs 的信息。
For example, let's say that the foo device driver wants to register a device with devfs.
举例来说，假设foo设备驱动程序希望使用devfs注册设备。
Note that I'm using devfs, and that's why you see the extremely long device names listed above.
请注意，这使用的是devfs，这就是读者看到上面所列的极长设备名的原因。
Because we're not just enabling devfs functionality in the kernel, which is actually quite easy.
因为我们不仅仅在内核中启用devfs功能，这的确非常容易。
If you happen to be using devfs, you'll find that this directory has already been created for you.
如果您正好在使用devfs，您会发现这个目录已经为您创建好了。
The first one controls whether devfs will be mounted to /dev automatically when the kernel boots.
第一个选项控制devfs在内核引导时是否自动安装到 /dev。
In this article, we'll complete converting our Linux system over to devfs, or the Device Filesystem.
在本文中，我们将完成把我们的Linux系统转换到devfs，即设备文件系统。
Your system is now ready for the devfs conversion, which I will cover in detail in the next article.
您的系统现在已经作好了向devfs转换的准备，我将在下一篇文章中详细介绍。
Therefore, probably the best way to solve the devfs "chicken and egg" problem is to use an init wrapper.
因此，解决devfs的“先有鸡还是先有蛋”问题的最好办法，可能就是使用初始封装器。
Right now, we'll just get devfsd installed; next article, we'll get it up and running, along with devfs.
现在，我们将只安装devfsd；在下一篇文章中，我们将使它和devfs一起启动和运行。
The first step to enabling devfs on your system is easy: you'll need to enable devfs support in the kernel.
在系统上启用devfs的第一步比较简单：就是要使内核支持devfs。
While devfs provides all the "new-style" devices, the old-style device nodes are created by the devfsd daemon.
尽管devfs提供所有“新类型”的设备，但旧类型的设备节点却是由devfsd守护进程创建。
In this article, we'll get your system devfs-ready, and in the next, we will do the actual conversion to devfs.
在本文中，我们将使您的系统为启用devfs作好准备，在下篇文章中，我们将真正开始向devfs的转换。
When they are accessed, the kernel maps to the appropriate device driver by devfs device name, rather than by major number.
当它们被访问时，内核通过devfs设备名称映射到合适的设备驱动程序，而不是通过主设备号。
In the previous installment (Part 4), we took a close look at what devfs is and how it solves nearly all device management problems.
在上一部分(第4部分)中，我们具体讨论了什么是devfs，以及它是如何解决几乎所有的设备管理问题的。
To get a good understanding of devfs, it's best to first understand how devfs changes things from the perspective of the device driver.
为了很好地理解devfs，最好是先理解从设备驱动程序的角度来看devfs是怎样改变事物的。
However, now that devfs is enabled, the device drivers use a new and improved kernel call to register their devices, called devfs_register .
然而，现在启用了devfs，设备驱动程序是用一种新的、改进了的内核调用来注册设备，称为devfs_register 。
Then, in the next article, we'll focus on devfs, and after that we'll spend some time getting intimately familiar with the new ext3 filesystem.
在下一篇文章中，我们会把重点集中在devfs上，之后，我们会花点时间来进一步熟悉新的ext3文件系统。
To get devfs up and running, you'll need to be using some version of Linux 2.4 (2.4.6 or 2.4.8 would be a good choice) and glibc 2.1.3 or greater.
要启动和运行devfs，需要使用Linux 2.4的一些版本(2.4.6或2.4.8就不错)以及glibc2.1.3或更高版本。
I ended Part 5 by introducing the concept of an init wrapper, and explained why it was such a good fit for solving several devfs initialization problems.
我曾经在第5部分结束时，介绍了初始化封装器的概念，并且解释了初始化封装器非常适合于解决若干devfs初始化问题的原因。
You'll recall that on a non-devfs system, the register_blkdev() and register_chrdev() calls (along with supplied major numbers) are used for this purpose.
您会记起在非 devfs系统上， register_blkdev()和 register_chrdev()调用（连同提供的主设备号）正是用于这一目的。
The mapping from special file to kernel driver is made possible by the major number, not the actual device name, which is irrelevant to a non-devfs system.
让特殊文件到内核驱动程序的映射成为可能的是主设备号，而不是真实的设备名称（它和非 devfs 系统无关）。
It would supply an argument of foo0 to devfs_register , thus telling the kernel that a new foo0 device should be created at the root of the devfs namespace.
它会提供一个foo0的参数给devfs_register，从而告诉内核应该在devfs名称空间的根目录创建一个新的foo0设备。
应用推荐