Re: bcache-tools: minor change for bcache-register

[Rolf Fokkens <rolf-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>]

Gabriel, I might have been unclear about this, but this __IS__ a problem 
on Fedora. Without a full path for modprobe (/sbin/modprobe or 
/usr/sbin/modprobe) in bcache-register, udev does not create the 
/dev/bcache* devices. So at the moment I fix it in the package.

If this is however Fedora specific I'll have the fix it in the package 
of course. But it's hard for me to tell, and /sbin/modprobe seemed like 
a cross-distro solution to me.

On 08/27/2013 01:45 PM, Gabriel de Perthuis wrote:
> On Tue, 27 Aug 2013 13:00:24 +0300, Alex Pyrgiotis wrote:
>> On 08/27/2013 09:58 AM, Rolf Fokkens wrote:
>>> -modprobe -qba bcache
>>> +/sbin/modprobe -qba bcache
>>>    test -f /sys/fs/bcache/register_quiet && echo "$1" >
>>> /sys/fs/bcache/register_quiet
>>>
>>> /sbin is not in the $PATH for utilities started from udev. For Fedora it
>>> isn't anyway, but it won't harm other distro's neither.
>>>
>> Hi all,
>>
>> Pardon the interrupt, but this is not the case for Arch Linux:
>> https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/
>>
>> In my opinion, if modprobe *has* to be called with the exact path name,
>> it would probably be clearer to use `which modprobe` and then call the
>> result.
> IME the exact path name is unnecessary.
> Rolf, your best shot at contributing is to bring up problems that have
> actually been encountered on Fedora.  Changes need to come as a side
> effect of discussions, not the other way around.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html