udev and udevadm documentation missing

[Bill Yikes]

The man page for udevadm neglects to mention options which seem to only be documented in stackexchange. E.g.

udevadm monitor --environment

udevadm control --reload-rules

From the man page, it's unclear what the difference is between /udevadm trigger/ and /udevadm test/. The description should tell the user enough to work out which one they need to use for a certain situation. E.g. I wrote a new rule and it's not triggering. Is the trigger command or the test command suitable for diagnosing the problem?

The documentation in /usr/share/doc/udev/ is strangely specific to some esoteric network interface naming. There is no basic description of what udev's purpose is or what its capabilities are. One of the most notable tasks is to react to the insertion of USB drives, and there is no mention of this. The /etc/fstab table also has a role in mounting USB drives, but there is no mention as to how udev works with /etc/fstab. I've found that if I remove a line in /etc/fstab and attach the drive pertaining to that line, it gets mounted anyway. If the fstab file supercedes udev, then this should be mentioned in the documentation.

[Dan Streetman (ddstreet)]

> udevadm monitor --environment

--environment is an alias for --property, which is in the man page

> udevadm control --reload-rules

--reload-rules is an alias for --reload, which is in the man page

> From the man page, it's unclear what the difference is between /udevadm trigger/ and /udevadm test/.

As with bug 1890890, this should be opened with upstream systemd/udev, not here, as generally Ubuntu just provides what's developed upstream. If the man page isn't clear, you should open an issue and/or pull request with upstream systemd: https://github.com/systemd/systemd

If you're only trying to get help with questions on how things work, then opening bugs probably isn't the right thing to do, probably ask Ubuntu would be a better place to find help: https://askubuntu.com/

[Launchpad Janitor (janitor)]

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]