It is a good thing to set RC_DEVICE_TARBALL to "no", because your /dev is much less cluttered without extracting the tarball to it (from my point of view). On the end of section 2 there's a warning that I should not read further, unless I'm a "die-hard". The instruction to set RC_DEVICE_TARBALL to "no" is behind that warning, that's why I didn't executed it first. Maybe there should be a note (which I got from gentoo-user) that warns about this clutter. IMO, there's no point in having this tarball extracted at bootup when I have udev, or am I wrong? So it should be suggested to set RC_DEVICE_TARBALL to "no", IMO.
currently not everything supports sysfs should that change we can go this route
No, but for the majority of users it works fine, so we shouldn't be recommending this hideous hack as the default behaviour, and marking the clean option as something for "die-hard" users.
I just want you to add an information like this: "Leaving RC_DEVICE_TARBALL set to 'yes' causes clutter in your /dev, because the gentoo init scripts will store your /dev on shutdown and restore it on bootup. If you want to see only nodes of present devices in /dev, turn this to 'no'. If you have sysfs disabled, leave it as it is." Just as an _information_. This is a very useful information for the majority of the users, IMO. Maybe the init script could auto-detect sysfs and not untar the /dev tarball, if sysfs is enabled.
I've rephrased the sentence a bit so that readers understand Gentoo's default behaviour. As long as RC_DEVICE_TARBALL is set to "yes" by default I don't intend to have this documented otherwise.
