* "Andreas K. Huettel" <2862978.mvXUDI8C0e @pinacolada> :
Wrote on Sun, 07 Apr 2024 15:27:42 +0200:
>> I see no way of migrating to 23.0 profile because of not-recompilable
>> packages that are installed (over 4 years) which block --emptytree,
>> and do not wish to be forced to migrate to
On Mon, Apr 8, 2024 at 5:51 AM Jaco Kroon wrote:
>
> Hi All,
>
> I was hoping for some advise regarding how I could improve the glusterfs
> package for users (and myself). At least those using openrc, but I
> suspect similar may be applicable to systemd, but I have no idea how
> systemd handles
Hi Joonas,
On 2024/04/11 12:02, Joonas Niilola wrote:
Hey,
On 11.4.2024 9.14, Jaco Kroon wrote:
The latter can certainly be done and makes sense (only required if
you're using the fuse mount, so if USE=fuse at least).
The former doesn't make sense to do blindly in /etc/init.d/netmount
(which
Hey,
On 11.4.2024 9.14, Jaco Kroon wrote:
>
> The latter can certainly be done and makes sense (only required if
> you're using the fuse mount, so if USE=fuse at least).
>
> The former doesn't make sense to do blindly in /etc/init.d/netmount
> (which belongs to sys-apps/openrc, not glusterfs).
Hi Joonas,
Thanks for the below. Further comments there.
On 2024/04/11 07:11, Joonas Niilola wrote:
On 8.4.2024 12.51, Jaco Kroon wrote:
In order for glusterfs to mount successfully the fuse module needs to be
available when mount.glusterfs is invoked. This can be achieved in one
of two