On Fri, 2011-09-16 at 12:29 -0700, Nicholas A. Bellinger wrote: > On Fri, 2011-09-16 at 13:05 -0400, Douglas Gilbert wrote: > > Well I can answer my own question. > > configfs doesn't seem to be mounted at /sys/kernel/config > > and even when it is, superuser cannot create a directory > > there. So mount configfs somewhere else: > > > > mount -t configfs none /tmp/config > > This should actually be: > > mount -t configfs configfs /sys/kernel/config Well, not really; they're both equally valid. For pseudo mounts which have no underlying device, the standard mount -t <type> <device> <mount point> Convention has 'none' as the <device> because <device> is just ignored by the kernel. The only reason for not choosing 'none' is that the error messages tend to use the <device> (which does go into the mtab), so if you later try to umount and something is using the mount point you can get a funny looking error message none busy However, most versions of umount have been fixed to report the <mount point> instead, so even this potential issue is moot. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
