When I use plocate in WSL2 (Windows Subsystem for Linux, version 2), I noticed that windows filesystems (such as `/mnt/c`) were indexed in the default configuration.

WSL2 use `9p' to "mount" windows file systems, which can be treated as a network filesystem - in terms of both architecture and performance. Indexing files in such filesystem triggers excessive filesystem I/O overhead.

I would like to suggest adding `9p' to the default PRUNEFS list in `/etc/updatedb.conf'.

Hi,

This has come up before, and the problem is that it goes both ways;
you get less updatedb overhead, but you also simply cannot find your files.
Some people would think this is a good tradeoff, I'm not so sure.
It depends on how many directories you have and if you actually care about
finding your /mnt/c files or not. Given that plocate isn't installed
by default and you can easily add this yourself to updatedb.conf,
this is probably going to be a wontfix.

/* Steinar */

I see.

I am primarily looking at this from a standpoint of consistency: `9p' is
basically a network protocol, so I believe it makes sense to prune it,
just like `nfs', `smbfs' or `sshfs'.

This also aligns plocate behavior with Windows tools. Windows treats WSL2
as a network resource and does not index its internal data by default;
pruning 9p keeps plocate consistent with this logic.

As for WSL1, Windows tools typically treat it as a local resource for
indexing. While Windows drives are mounted via `drvfs' in WSL1, pruning `9p'
won't impact indexing for those volumes from WSL1.