When using daxctl, we don't get a hint/suggestion to use sudo/root.
For example, running "daxctl reconfigure-device -m system-ram dax0.0"
without sudo will only print the following:

libdaxctl: daxctl_dev_disable: dax0.0: failed to disable
dax0.0: disable failed: Device or resource busy
error reconfiguring devices: Device or resource busy
reconfigured 0 devices

But running it as sudo is okay. The message is a little misleading,
since the problem is not having root privileges, not the device being
busy.

IMO a hint in the end would be a nice reminder.

Reply via email to