jaunty: /sbin/lsmod moved to /bin/lsmod

From the FHS:

"/bin contains commands that may be used by both the system administrator and by users, but which are
required when no other filesystems are mounted (e.g. in single user mode). It may also contain commands which are used indirectly by scripts"

"Utilities used for system administration (and other root-only commands) are stored in /sbin, /usr/sbin, and
/usr/local/sbin. /sbin contains binaries essential for booting, restoring, recovering, and/or repairing the
system in addition to the binaries in /bin."

So isn't lsmod in the correct directory now? I think the scripts you refer to should probably be fixed.

lsmod always was there. it is wery painful change -- it broke many packages and third-party software.

in ubuntu: kvm, powernowd, apid, bash_completion. it is only quck check on installed on my pc packages. (rgrep /sbin/lsmod /etc)

Whether or not lsmod is now in the right place, the move has broken acpid and powernowd scripts. Either they should be fixed or module-init-tools.

This was a packaging error, upstream ship lsmod in /bin but we always had it in /sbin

Since both paths are valid and potentially hardcoded by scripts, we shall include a symlink from one to the other.

This bug was fixed in the package module-init-tools - 3.7~pre7-4

---------------
module-init-tools (3.7~pre7-4) jaunty; urgency=low

  * debian/module-init-tools.links: Create an /sbin/lsmod symlink, that's
    always been the location in Debian/Ubuntu. We want to keep /bin/lsmod
    since that's the upstream location. LP: #340666.

 -- Scott James Remnant <email address hidden> Wed, 11 Mar 2009 09:32:59 +0000