Date: Fri, 15 Dec 2006 11:21:52 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Scot Hetzel <swhetzel@gmail.com> Cc: freebsd-emulation@freebsd.org Subject: Re: linuxolator: proc/filesystems implementation Message-ID: <20061215112152.zo19clk4ggkck4c8@webmail.leidinger.net> In-Reply-To: <790a9fff0612140401h7bf0bdb0idb1590120ae95e3f@mail.gmail.com> References: <790a9fff0612140401h7bf0bdb0idb1590120ae95e3f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Scot Hetzel <swhetzel@gmail.com> (from Thu, 14 Dec 2006 =20 06:01:27 -0600): > Linux has a file in the procfs that shows all the loaded filesystem module= s. > > I have implemented the function that fills this file using the > linprocfs module. > > What the function does is look for specific kernel modules using > module_lookupbyname to create an entry in the proc/filesystems file: > > # cat /compat/linux/proc/filesystems > cd9660 > nodev devfs > nodev bsdprocfs > mfs > msdosfs Like Roman I'm eager to know which software uses this. Unlike him I =20 don't think (yet) it doesn't make sense without a translation table. =20 If the list is just presented to an user we don't need a translation. =20 If it is used to do something we may need a translation (but only for =20 those FS which have a compatible structure, like cd9660 or extfs, but =20 not for ufs, which is UFS2 for us and "I don't know but possibly UFS1" =20 on Linux). Bye, Alexander. --=20 Officers' club: We don't know but we've been told, our beer on tap is mighty cold. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061215112152.zo19clk4ggkck4c8>