module-init-tools

[MSumulong]

I was wondering if someone can update module-init-tools from the 4.x archive so that it can override the default busybox link in /sbin/modprobe.

I wind up having to do the following:

sudo rm /sbin/modprobe
sudo ln -s /usr/local/sbin/modprobe /sbin/modprobe

The VirtualBox Guest Additions looks for modprobe in /sbin and it uses the -c parameter which doesn't exist in the busybox version.

[gerald_clark]

Try adding an alias for use by your VirtualBox Guest Additions.
alias /sbin/modprobe='/usr/local/bin/modprobe'

[MSumulong]

I think it should be (bin -> sbin):

alias /sbin/modprobe='/usr/local/sbin/modprobe'

But when I run VBoxLinuxAdditions.run, it is still running the busybox version... I guess alias doesn't work within shell scripts?

[gerald_clark]

That alias works only for ash, but bash does not allow a path in the alias name.
If you are using ash only, you could put the alias in ~/.ashrc.

[ -f /usr/local/sbin/modprobe ] && alias /sbin/modprobe='/usr/local/sbin/modprobe'

[tinypoodle]

Sounds very similar with a most recently reported and fixed bug:
https://www.virtualbox.org/ticket/12713

Consider submitting a respective bug report.

[MSumulong]

That alias works only for ash, but bash does not allow a path in the alias name.
If you are using ash only, you could put the alias in ~/.ashrc.

[ -f /usr/local/sbin/modprobe ] && alias /sbin/modprobe='/usr/local/sbin/modprobe'

I've added this line to my ~/.ashrc but its still complaining:

/sbin/modprobe: invalid option -- 'c'

[gerald_clark]

Are you sure it is not just a $PATH issue?

Are you using virtualbox-ose-additions.tcz ?

[MSumulong]

I'm not sure if its a $PATH issue. I'll have to look into that.

No, I'm not using the virtualbox-ose-additions.tcz. I'm using the virtual CD that is supplied by VirtualBox and running /mnt/sr0/VBoxLinuxAdditions.run to rebuild the guest additions myself.

[tinypoodle]

Please post output of:

Code: [Select]

type modprobe

[MSumulong]

Please post output of:

Code: [Select]

type modprobe

At what point? After installing module-init-tools from 4.x and before adding [ -f /usr/local/sbin/modprobe ] && alias /sbin/modprobe='/usr/local/sbin/modprobe'? or after?

[tinypoodle]

Both 

[MSumulong]

Both 

Before installing module-init-tools.tcz:

modprobe is /sbin/modprobe


After installing module-init-tools.tcz:

modprobe is a tracked alias for /sbin/modprobe


After editing the .ashrc:

modprobe is a tracked alias for /sbin/modprobe


After typing "alias /sbin/modprobe='/usr/local/sbin/modprobe'":

modprobe is /usr/local/sbin/modprobe

[tinypoodle]

After installing module-init-tools.tcz:

modprobe is a tracked alias for /sbin/modprobe

Try:

Code: [Select]

hash -r
type modprobeinstead.

After editing the .ashrc:

modprobe is a tracked alias for /sbin/modprobe

Editing .ashrc will only affect shells started after that.

[MSumulong]

After installing module-init-tools.tcz:

modprobe is a tracked alias for /sbin/modprobe

Try:

Code: [Select]

hash -r
type modprobeinstead.

After editing the .ashrc:

modprobe is a tracked alias for /sbin/modprobe

Editing .ashrc will only affect shells started after that.

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

After adding alias:

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

[tinypoodle]

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