[10:00] <Putti> Currently for example in DataSourceAltCloud.py some programs are called with their absolute path, e.g. /sbin/modprobe and /sbin/udevadm. Different operating systems have the udevadm command in different locations so could we use just the command name instead of its full path to sbin?
[13:19] <Putti> ok, so I thought about this bit. In some operating systems like Debian the /sbin/ won't be included in the path unless the user is super user. So it all depends on how the program is run.
[13:20] <Putti> I think it would be wiser to let the packagers do the PATH configurations
[13:20] <Putti> so in my opinion /sbin/modprobe could be just modprobe
[13:55] <Putti> In systemd the PATH variable is hardcoded to "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" (see man systemd.exec) and for sysvinit we have declared (in cloud-init/sysvinit) that /sbin should be in the PATH.
[14:31] <Putti> the cloudinit.util module seems to have 'which' function also so that could be used, too. Which option is better?