module-init-tools

[MSumulong]

Before installing module-init-tools.tcz:

hash -r; type modprobe
modprobe is /sbin/modprobe

After installing module-init-tools.tcz:

hash -r; type modprobe
modprobe is /usr/local/sbin/modprobe

In given context this implies that your PATH and extension both seem to work fine as expected, but that there is a hardcoding bug in the software you try to run as already hinted in Reply #4.

After adding alias:

hash -r; type modprobe
modprobe is /usr/local/sbin/modprobe

Ah, yes, this is expected, what would be relevant instead would be:

Code: [Select]

type /sbin/modprobe


type /sbin/modprobe gives me /sbin/modprobe is /sbin/modprobe

I'll go ahead and submit a request to not have modprobe hard-coded.

[tinypoodle]

Code: [Select]

tc@box:~$ type /sbin/modprobe
/sbin/modprobe is /sbin/modprobe
tc@box:~$ alias '/sbin/modprobe'='/usr/local/sbin/modprobe'
tc@box:~$ type /sbin/modprobe
/sbin/modprobe is an alias for /usr/local/sbin/modprobe
tc@box:~$
But then, according to:
http://www.computerworld.com/s/article/9233435/How_to_use_aliases_in_Linux_shell_commands

Aliases are disabled for noninteractive shells (that is, shell scripts).

So I guess in case in question alias might be sort of a moot point.

[MSumulong]

Code: [Select]

tc@box:~$ type /sbin/modprobe
/sbin/modprobe is /sbin/modprobe
tc@box:~$ alias '/sbin/modprobe'='/usr/local/sbin/modprobe'
tc@box:~$ type /sbin/modprobe
/sbin/modprobe is an alias for /usr/local/sbin/modprobe
tc@box:~$
But then, according to:
http://www.computerworld.com/s/article/9233435/How_to_use_aliases_in_Linux_shell_commands

Aliases are disabled for noninteractive shells (that is, shell scripts).

So I guess in case in question alias might be sort of a moot point.

Yea, I never had any success using the alias commands... VBoxLinuxGuestAdditions.run always tried to run the busybox version of modprobe.