[opensuse] Why do I have all these file systems loaded as modules?
When I look in /proc/filesystems I see that there are, among others, btrfs* reiserfs* xfs* jfs msdos vfat minix hfs hfsplus qnx4 ufs I use the ones marked with an asterix and I might need msdos/vfat or possibly even "exFAT" (not there, but available as a user-fuse for my sdscards). Now I'm aware that I can blacklist any module my sweet heart desires, but that's not the point. There isn't a requirement for the unmarked items under /etc/modules-load.d/ nor anything about them in the files under /etc/modprobe.d/* I grep /etc for any mention of minix, qnx4 ... and nothing turns up. I can't imagine why I'd need them. Yes, I could blacklist them, but as I say, that's not the point. They were never enabled in the first place. How did they get there? I check with lsinitrd and there is no mention there either. I thought I knew about modules and enabling/disabling them, but this has me puzzled. Hmm. It makes me wonder what other unwanted/unnecessary modules are being loaded. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 14:40, Anton Aylward wrote:
Hmm. It makes me wonder what other unwanted/unnecessary modules are being loaded.
Are you sure that filesystems are loaded as modules? I would think they are not, but included in the kernel. The reasoning would be that if your machine is installed with one of the filesystems coming as modules, it would not boot. On the other hand, those could be included in the initrd. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQWQAACgkQja8UbcUWM1wn9QD+Psw4SnjnL7+X9464i8diRm6c 1cRD0xpnYSD6OZW09XcBAJG0gumhxJtkon4wIWTRlda6SqzEzZppdqH5GUNvyAnX =Cis8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 08:54 AM, Carlos E. R. wrote:
On 2016-02-26 14:40, Anton Aylward wrote:
Hmm. It makes me wonder what other unwanted/unnecessary modules are being loaded.
Are you sure that filesystems are loaded as modules?
yes I am *ABSOLUTELY* sure. I run 'lsmod' and the 'mavericks' I mention are there. I remove them with 'rmmod' and run 'lsmod' again and they are gone.
On the other hand, those could be included in the initrd.
Didn't I mention that I checked with 'lsinitrd'? -- Life is like an analogy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 09:16 AM, Anton Aylward wrote:
On 02/26/2016 08:54 AM, Carlos E. R. wrote:
On 2016-02-26 14:40, Anton Aylward wrote:
Hmm. It makes me wonder what other unwanted/unnecessary modules are being loaded.
Are you sure that filesystems are loaded as modules?
yes I am *ABSOLUTELY* sure. I run 'lsmod' and the 'mavericks' I mention are there. I remove them with 'rmmod' and run 'lsmod' again and they are gone.
# lsmod | head -12 Module Size Used by ufs 81920 0 qnx4 16384 0 hfsplus 110592 0 hfs 61440 0 minix 36864 0 vfat 20480 0 msdos 20480 0 fat 73728 2 vfat,msdos jfs 196608 0 xfs 1036288 0 libcrc32c 16384 1 xfs and so on. BtrFs, ext4, ReiserFS are further on down and are in use by file systems I actually use. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 15:16, Anton Aylward wrote:
On 02/26/2016 08:54 AM, Carlos E. R. wrote:
Are you sure that filesystems are loaded as modules?
yes I am *ABSOLUTELY* sure. I run 'lsmod' and the 'mavericks' I mention are there. I remove them with 'rmmod' and run 'lsmod' again and they are gone.
Ah, ok.
On the other hand, those could be included in the initrd.
Didn't I mention that I checked with 'lsinitrd'?
Possibly, but not everything the eye sees the mind registers ;-) That is, quick reading has faults. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQYnoACgkQja8UbcUWM1yTKgD+IstzzoQ/8y2nwGU2wDWfLiAA iZhgI9WJQsSFvcOu0b0BAJketGKC0+k5XI/LRHTHPWEViDm1Mtc6rfn78V04lwyE =QhxX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 09:34 AM, Carlos E. R. wrote:
That is, quick reading has faults.
That's OK. As one ages (aka 'get into your dotage') I find that one's reading speed slows down. My excuse is that I've read so much that trying to force more stuff into my brain via my eyeballs is sort of like those movies you see on YouTube of the porters on the Japanese subway stuff more passengers into the trains. The back pressure of what's already there resists the input of new stuff. I tell my ophthalmologist this and he says that rather my once green eyes have turned brown with age. Funny guy! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 02/26/2016 08:54 AM, Carlos E. R. wrote:
On 2016-02-26 14:40, Anton Aylward wrote:
Hmm. It makes me wonder what other unwanted/unnecessary modules are being loaded.
Are you sure that filesystems are loaded as modules?
yes I am *ABSOLUTELY* sure. I run 'lsmod' and the 'mavericks' I mention are there. I remove them with 'rmmod' and run 'lsmod' again and they are gone.
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem. -- Per Jessen, Zürich (4.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 09:39 AM, Per Jessen wrote:
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem.
Hmmm. Wouldn't that show up in dmesg? Moment ... Hmmm. There;s [ 158.726491] JFS: nTxBlock = 8192, nTxLock = 65536 [ 158.973394] QNX4 filesystem 0.2.3 registered. but nothing surrounding them that indicates why. Noting in /etc/fstab that hints why. Running 'mount' offers no clues. I've never experimented with qnx4, jfs, minix, ufs .. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 02/26/2016 09:39 AM, Per Jessen wrote:
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem.
Hmmm. Wouldn't that show up in dmesg?
I'm not sure, maybe not all of them.
Moment ...
Hmmm. There;s
[ 158.726491] JFS: nTxBlock = 8192, nTxLock = 65536 [ 158.973394] QNX4 filesystem 0.2.3 registered.
qnx4 is a pretty odd one. -- Per Jessen, Zürich (4.5°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 11:21 AM, Per Jessen wrote:
[ 158.726491] JFS: nTxBlock = 8192, nTxLock = 65536 [ 158.973394] QNX4 filesystem 0.2.3 registered. qnx4 is a pretty odd one.
Indeed it is. There is no reason I can establish why it should be loaded. As I say, not only is there nothing in /etc/fstab related, but also I've never even experimented with this type of file system. Contrariwise, I *have* experimented with Nils2FS, but its not there! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 26, 2016 at 11:34:54AM -0500, Anton Aylward wrote:
On 02/26/2016 11:21 AM, Per Jessen wrote:
[ 158.726491] JFS: nTxBlock = 8192, nTxLock = 65536 [ 158.973394] QNX4 filesystem 0.2.3 registered. qnx4 is a pretty odd one.
Indeed it is. There is no reason I can establish why it should be loaded. As I say, not only is there nothing in /etc/fstab related, but also I've never even experimented with this type of file system.
Contrariwise, I *have* experimented with Nils2FS, but its not there!
Usually if you do "mount /dev/somedev /mnt" without type, mount will try various filesystem types causing them to be loaded. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 11:37 AM, Marcus Meissner wrote:
Usually if you do "mount /dev/somedev /mnt" without type, mount will try various filesystem types causing them to be loaded.
True, but not relevant here as this situation arises immediately after a fresh boot. I've been though that cycle a couple of times this morning to verify. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 17:41, Anton Aylward wrote:
On 02/26/2016 11:37 AM, Marcus Meissner wrote:
Usually if you do "mount /dev/somedev /mnt" without type, mount will try various filesystem types causing them to be loaded.
True, but not relevant here as this situation arises immediately after a fresh boot. I've been though that cycle a couple of times this morning to verify.
Yes, on a fresh boot fstab is read, and if there are entries with "auto" type, several are tried till a good one is found. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQgyYACgkQja8UbcUWM1yojwD+ODKRHvyiRO6MWruMQt7CTeKb bBSXbaWXEvSVlGApmaMA/jG3tFKTI+Nmv3HoMLT7dIPZduJb7sw3Sfn6cH1KIVfL =j3ry -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 11:53 AM, Carlos E. R. wrote:
On 2016-02-26 17:41, Anton Aylward wrote:
On 02/26/2016 11:37 AM, Marcus Meissner wrote:
Usually if you do "mount /dev/somedev /mnt" without type, mount will try various filesystem types causing them to be loaded.
True, but not relevant here as this situation arises immediately after a fresh boot. I've been though that cycle a couple of times this morning to verify.
Yes, on a fresh boot fstab is read, and if there are entries with "auto" type, several are tried till a good one is found.
From MAN(mount)
<quote> If no -t option is given, or if the auto type is specified, mount will try to guess the desired type. Mount uses the blkid library for guessing the filesystem type; if that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems. All of the filesystem types listed there will be tried, except for those that are labeled "nodev" (e.g., devpts, proc and nfs). If /etc/filesystems ends in a line with a single * only, mount will read /proc/filesystems afterwards. All of the filesystem types will be mounted with mount option "silent". </quote> Yes, interesting. Firstly, all the file systems mounts in /etc/fstab are fully specified, so this doesn't apply there. Second, I have 'blkid' able to identify all my file systems, and, as I've said, none are the mavericks such as minix, qnx4 etc. Third I have # more /etc/filesystems vfat reiserfs exfat exfat_fuse * The four specified I do, as I've discussed, use. So the "*" is there, but that should never apply because the 'blkid' is applied first and there's nothing which it can't recognise. Wouldn't any blkid attempts show up in dmesg? There aren't any. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 18:25, Anton Aylward wrote:
From MAN(mount)
<quote> If no -t option is given, or if the auto type is specified, mount will try to guess the desired type. Mount uses the blkid library for guessing the filesystem type; if that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems. All of the filesystem types listed there will be tried, except for those that are labeled "nodev" (e.g., devpts, proc and nfs). If /etc/filesystems ends in a line with a single * only, mount will read /proc/filesystems afterwards. All of the filesystem types will be mounted with mount option "silent". </quote>
Yes, interesting.
Firstly, all the file systems mounts in /etc/fstab are fully specified, so this doesn't apply there.
Second, I have 'blkid' able to identify all my file systems, and, as I've said, none are the mavericks such as minix, qnx4 etc.
I'm thinking that /proc/filesystems lists all the filesystems that can be tried, or mounted, but not necesarily that their respective modules are already loaded. Ie, the kernel must know what filesystem modules it can provide support for. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQjdsACgkQja8UbcUWM1wELAEAkLBPJs3Irle4zl9zusYdGJk+ xcaAdRNtfgjyXRHvx6wA/i/DHJlP8vmuN357s/9GyvanXbjOCPEIbnvTvy6TYyUK =Eduw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 12:39 PM, Carlos E. R. wrote:
I'm thinking that /proc/filesystems lists all the filesystems that can be tried, or mounted, but not necesarily that their respective modules are already loaded. Ie, the kernel must know what filesystem modules it can provide support for.
No, I don't think so, that doesn't make sense. if that were so then every module in /lib/modules wou.d be noted somewhere under /proc. Simple test of this. Do 'rmmod' of the offending modules. # lsmod | head -10 Module Size Used by binfmt_misc 20480 1 ufs 81920 0 qnx4 16384 0 hfsplus 110592 0 hfs 61440 0 minix 36864 0 vfat 20480 0 msdos 20480 0 fat 73728 2 vfat,msdos # more /proc/filesystems | egrep -v nodev ext3 ext2 ext4 btrfs reiserfs fuseblk xfs jfs msdos vfat minix hfs hfsplus qnx4 ufs # rmmod jfs minix qnx4 ufs hfs hfsplus # more /proc/filesystems | egrep -v nodev ext3 ext2 ext4 btrfs reiserfs fuseblk xfs msdos vfat OK, proven! /proc/filesystems only lists the filesystems that have modules loaded or are compiled into the kernel. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 18:52, Anton Aylward wrote:
OK, proven! /proc/filesystems only lists the filesystems that have modules loaded or are compiled into the kernel.
Interesting. Then how can the admin/user know which are supported by his kernel? - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQlvcACgkQja8UbcUWM1zjmgD/bkE2ghY14fpBImm31VC/CFrA y0UKdbikAafC8mQgeekA/3CoCE9GQDstizmpqN0mVjD0dY7HPN7BgDIz+Sah/Lvp =CQYw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 01:18 PM, Carlos E. R. wrote:
On 2016-02-26 18:52, Anton Aylward wrote:
OK, proven! /proc/filesystems only lists the filesystems that have modules loaded or are compiled into the kernel.
Interesting.
Then how can the admin/user know which are supported by his kernel?
For some values of 'supported' try looking what modules there are under /lib/modules/$(uname -r) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.02.2016 21:18, Carlos E. R. пишет:
On 2016-02-26 18:52, Anton Aylward wrote:
OK, proven! /proc/filesystems only lists the filesystems that have modules loaded or are compiled into the kernel.
Interesting.
Then how can the admin/user know which are supported by his kernel?
By looking at module aliases fs-*. E.g. fgrep 'alias fs-' /lib/modules/$(uname -r)/modules.alias | cut -f3 -d' '
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 15:39, Per Jessen wrote:
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem.
os-prober. os-prober loads them all, because it tries all types on all partitions. Then, mount by type "auto" might do the same, at least till a hit is found. os-prober tries all because it also probes extended partitions, which have no type, thus all probes are bound to fail. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQao8ACgkQja8UbcUWM1yuKgD+JEfHonlj5GT2Pg6Ls+OXOFAA +WGS/euBlC1tUPBJhisBAITY3NPv1oZgxZL8dxUsmKNwXgT+paHzFQEqvpk2Ht4f =FQqW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Отправлено с iPhone
26 февр. 2016 г., в 18:09, Carlos E. R.
написал(а): -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2016-02-26 15:39, Per Jessen wrote:
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem.
os-prober. os-prober loads them all, because it tries all types on all partitions.
Since quite some time it is using grub-mount, so nothing gets loaded, at least as long as filesystem is supported by grub. It used to load these modules unconditionally, but this was disabled.-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 16:14, Andrei Borzenkov wrote:
os-prober. os-prober loads them all, because it tries all types on all partitions.
Since quite some time it is using grub-mount, so nothing gets loaded, at least as long as filesystem is supported by grub.
It used to load these modules unconditionally, but this was disabled.
I'm still on 13.1 ;-) Wait. I installed Leap a week ago on my main machine, for testing, and it took several minutes probing. The YaST installer, took so long to install the boot system that I though it had hung. Luckily I found one of terminal-logs, where I saw filesystem probes of many types on all partitions on all disks, and taking an awful time to do it. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQbsIACgkQja8UbcUWM1yHvgD+K2FQtahdH9vlV5gy5Yr63c+B C32EtqfzQu452vM+DNIBAIIRHs2qSMByzrakmQAyF27hZ+m3TBqVbZ/AzViwP2MF =FVFd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 10:26 AM, Carlos E. R. wrote:
Wait. I installed Leap a week ago on my main machine, for testing, and it took several minutes probing. The YaST installer, took so long to install the boot system that I though it had hung. Luckily I found one of terminal-logs, where I saw filesystem probes of many types on all partitions on all disks, and taking an awful time to do it.
I'm not talking about installation. I'm not talking about running mkinitrd. I'm talking about a regular system booting under normal conditions. I *expect* an installer to do a lot of scanning. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 10:14 AM, Andrei Borzenkov wrote:
26 февр. 2016 г., в 18:09, Carlos E. R.
написал(а): On 2016-02-26 15:39, Per Jessen wrote:
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem.
os-prober. os-prober loads them all, because it tries all types on all partitions.
Since quite some time it is using grub-mount, so nothing gets loaded, at least as long as filesystem is supported by grub.
It used to load these modules unconditionally, but this was disabled.
Do you mean grub classic or grub2? Could you explain a bit more, please. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 10:09 AM, Carlos E. R. wrote:
On 2016-02-26 15:39, Per Jessen wrote:
Obviously something loaded them, maybe when trying to mount a device with an unknown filesystem.
os-prober. os-prober loads them all, because it tries all types on all partitions. Then, mount by type "auto" might do the same, at least till a hit is found. os-prober tries all because it also probes extended partitions, which have no type, thus all probes are bound to fail.
When is os-prober run? I thought it was part of mkinitrd not part of the boot process? In addition, people like jdd are reporting that only the fs drivers they use are there after boot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 16:24, Anton Aylward wrote:
On 02/26/2016 10:09 AM, Carlos E. R. wrote:
When is os-prober run? I thought it was part of mkinitrd not part of the boot process?
Correct.
In addition, people like jdd are reporting that only the fs drivers they use are there after boot.
Yet others like me have a bunch of them. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQbvUACgkQja8UbcUWM1yoSwD+JQxIerseltlC/z/SglAGHWDU IFRa8RT5mESLAlT6i6IA/1m3twI7B+5Q2QFP6air6sb+2FTxKXFjU9fHG61IMK+G =LP9B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 10:27 AM, Carlos E. R. wrote:
On 2016-02-26 16:24, Anton Aylward wrote:
On 02/26/2016 10:09 AM, Carlos E. R. wrote:
When is os-prober run? I thought it was part of mkinitrd not part of the boot process?
Correct.
:-)
In addition, people like jdd are reporting that only the fs drivers they use are there after boot.
Yet others like me have a bunch of them.
Right. So WHY? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 16:48, jdd wrote:
Le 26/02/2016 16:35, Anton Aylward a écrit :
So WHY?
how old is your system, and what distro?
Mine is 13.1 - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQdb8ACgkQja8UbcUWM1w4hQD/WtfrNiNTv8HTkDaXPHfsDeoz mNTfgOMfy4ejxFRSX7MA/RXxiu2c/JsQunI0faIiUPPk9wNwgFEE1kPs9J0ySSXs =ih6n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 10:56 AM, Carlos E. R. wrote:
On 2016-02-26 16:48, jdd wrote:
Le 26/02/2016 16:35, Anton Aylward a écrit :
So WHY?
how old is your system, and what distro?
Mine is 13.1
Ditto. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 26/02/2016 17:21, Anton Aylward a écrit :
On 02/26/2016 10:56 AM, Carlos E. R. wrote:
On 2016-02-26 16:48, jdd wrote:
Le 26/02/2016 16:35, Anton Aylward a écrit :
So WHY?
how old is your system, and what distro?
Mine is 13.1
Ditto.
so long history :-) and if like me you test many things, almost everything can happen :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 26 februari 2016 08:40:59 CET schreef Anton Aylward:
When I look in /proc/filesystems I see that there are, among others,
btrfs* reiserfs* xfs* jfs msdos vfat minix hfs hfsplus qnx4 ufs
I use the ones marked with an asterix and I might need msdos/vfat or possibly even "exFAT" (not there, but available as a user-fuse for my sdscards).
Now I'm aware that I can blacklist any module my sweet heart desires, but that's not the point.
There isn't a requirement for the unmarked items under /etc/modules-load.d/ nor anything about them in the files under /etc/modprobe.d/*
I grep /etc for any mention of minix, qnx4 ... and nothing turns up. I can't imagine why I'd need them. Yes, I could blacklist them, but as I say, that's not the point. They were never enabled in the first place. How did they get there?
I check with lsinitrd and there is no mention there either.
I thought I knew about modules and enabling/disabling them, but this has me puzzled.
Hmm. It makes me wonder what other unwanted/unnecessary modules are being loaded.
> Q: Are you sure? > >> A: Because it reverses the logical flow of conversation. >> >>> Q: Why is top posting frowned upon?
On my system only those are loaded that are needed, on my systems (btrfs) and xfs. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 09:35 AM, Knurpht - Gertjan Lettink wrote:
On my system only those are loaded that are needed, on my systems (btrfs) and xfs.
That's what I would expect. I use Btrfs for ROOT, ResierFS for /home and xfs for large stuff like CDImages and movies. # lsmod| egrep "btrfs|reiserfs|xfs" xfs 1036288 2 libcrc32c 16384 1 xfs reiserfs 258048 11 btrfs 1056768 2 raid6_pq 106496 1 btrfs xor 24576 1 btrfs All boot (initrd) needs is the driver for the RootFS, btrFS. That reads /etc/fstab for the rest and does the load on demand of everyting else, not just XFS & reiserFS, but more. # lsinitrd /boot/initrd | egrep "btrfs|reiserfs|xfs" lib/modules/4.4.2-2.gc601f8d-default/kernel/fs/btrfs lib/modules/4.4.2-2.gc601f8d-default/kernel/fs/btrfs/btrfs.ko sbin/fsck.btrfs usr/sbin/fsck.btrfs -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 15:41, jdd wrote:
Le 26/02/2016 14:40, Anton Aylward a écrit :
When I look in /proc/filesystems I see that there are, among others,
I have only the needed ons (Leap)
My 13.1 here has 26 entries. minas-tirith:~ # cat /proc/filesystems | wc -l 36 minas-tirith:~ # minas-tirith:~ # cat /proc/filesystems nodev sysfs nodev rootfs nodev bdev nodev proc nodev cgroup nodev cpuset nodev tmpfs nodev devtmpfs nodev debugfs nodev securityfs nodev sockfs nodev pipefs nodev anon_inodefs nodev devpts ext3 ext2 ext4 nodev ramfs nodev hugetlbfs iso9660 nodev pstore nodev mqueue btrfs nodev autofs reiserfs nodev binfmt_misc fuseblk nodev fuse nodev fusectl vfat jfs nilfs2 xfs nodev rpc_pipefs nodev nfs nodev nfs4 - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQa1UACgkQja8UbcUWM1xN7wD/XA8qTlhv1qEwCZT9wBA5lGlJ wvVnDlmxfWJm2zvhCn8A/Roie9k/XUM89APsqkURkSbcdkTKIy38ysvtW/6gWodK =Ra0m -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/26/2016 10:12 AM, Carlos E. R. wrote:
minas-tirith:~ # cat /proc/filesystems
OK, so filter out the 'nodev' and focus on what we've been discussing, the file systems that are out there on media.
ext3 ext2 ext4 iso9660 btrfs reiserfs fuseblk vfat jfs nilfs2 xfs
we can ignore the regualr system file systems we know about, and what's left:
fuseblk vfat jfs nilfs2
Do you actually have automoutned entries for those in your /etc/fstab? This is my point. I don't, but i still get the modules loaded. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-26 16:32, Anton Aylward wrote:
On 02/26/2016 10:12 AM, Carlos E. R. wrote:
minas-tirith:~ # cat /proc/filesystems
we can ignore the regualr system file systems we know about, and what's left:
fuseblk vfat jfs nilfs2
Do you actually have automoutned entries for those in your /etc/fstab?
vfa, for sticks, that's all. Missing ntfs, I have two or three such in this laptop.
This is my point. I don't, but i still get the modules loaded.
Yes. Curious. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbQdZUACgkQja8UbcUWM1w2hwD+I2XSvK3QPGWaHKLmeYipZ+uA aNZg+lntEo5nuzDofmwBAIf91uRBM6oQ5EkDSwYuljwZ6mQurdDaIFZffJEEn0YF =JNYL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov
-
Anton Aylward
-
Carlos E. R.
-
jdd
-
Knurpht - Gertjan Lettink
-
Marcus Meissner
-
Per Jessen