Devfsadm doesn't create /dev/foo link

[servizig]

I don't know how devfsadm works, but after creating and installing foo package, I don't see /dev/foo node created. There are 2 foo nodes under /devices/pseudo directories. If I run foo command, then it prints foo: err = 2 and loads the module (shows up in the modinfo). If I manually create link from /devices/pseudo/foo@0:foo to /dev/foo, then foo command works correctly. Is it the expected behavior?

[gwr]

Sounds like a bug. I haven't used this in a while. Did devfsadm run?

[servizig]

How do I check this? I can manually run devfsadm -v -i foo but nothing prints out and nothing changes.
Also, I tried to run /usr/sbin/rem_drv foo first, then /usr/sbin/add_drv -v -f -m '* 0644 root sys' foo and got this output:

exit status = 0
Driver (foo) installed.

It should print devfsadm output here, too, right?

[gwr]

I'm trying to refresh my memory about how this works. Looking now:
Initially, devfsadm is run via the "devices-local" milestone if the config has changed.
After that, I think one nees to run it by hand after loading a driver, eg:
devfsadm -v -i drivername

That's supposed to create the /dev link to devices, via that plugin module.
What does running with -v show you?

[servizig]

Nothing, with exit code 0.
Under /devices/pseudo I have

drwxr-xr-x   2 root     sys            2 июн. 23 18:06 foo@0     #(empty dir)
crw-r--r--   1 root     sys      306,  0 июн. 23 20:07 foo@0:foo

[gwr]

OK, something is wrong there then. Needs debugging.

[servizig]

After adding this line to the /etc/devlink.tab:

type=ddi_pseudo;name=foo        \D

I immediately got after running devfsadm -v -i foo:

devfsadm[1725]: verbose: symlink /dev/foo -> ../devices/pseudo/foo@0:foo

Now, I understand why this worked, I don't understand why other nodes work, other than fuse, tpm, and xsvc. There's lots of pseudo devices that don't require special treatment. Why is that?