| 1 |
On 30 July 2015 at 01:22, William Hubbs <williamh@g.o> wrote: |
| 2 |
> On Thu, Jul 30, 2015 at 01:11:30AM +0300, Alon Bar-Lev wrote: |
| 3 |
>> On 29 July 2015 at 23:20, William Hubbs <williamh@g.o> wrote: |
| 4 |
>> > |
| 5 |
>> > All, |
| 6 |
>> > |
| 7 |
>> > so that there is a better idea out there of what I'm talking about, the |
| 8 |
>> > OpenRC github repository now has a mount-service branch. |
| 9 |
>> |
| 10 |
>> Nice! |
| 11 |
>> |
| 12 |
>> But I still trying to figure out why do we need to keep fstab around. |
| 13 |
>> It is pure legacy. |
| 14 |
> |
| 15 |
> Is it? I have heard different people say it is, and it isn't, so I have |
| 16 |
> no idea. |
| 17 |
> |
| 18 |
> If fstab is truly legasy, I'll look into that. |
| 19 |
|
| 20 |
for what it worth, a fstab.d would have been something usable... :) |
| 21 |
|
| 22 |
but if you are providing netifrc like configuration, there is no need |
| 23 |
to split configuration between the layout and the fstab, everything |
| 24 |
should be at one place if possible. |
| 25 |
|
| 26 |
maybe we can have some intermediate options... to bridge the gap, but |
| 27 |
all are in the scope of conf.d, examples: |
| 28 |
|
| 29 |
eval $(openrc-mount-helper-fstab ${NAME} /mnt/auto) |
| 30 |
|
| 31 |
or... builtin |
| 32 |
|
| 33 |
mount_driver_\${NAME}=fstab # will call eval |
| 34 |
$(openrc-mount-helper-${openrc-mount-driver-\${NAME}} ${NAME} "$@") |
| 35 |
mount_mountpoint=/mnt/auto |
| 36 |
|
| 37 |
but this fstab usage is optional. |
Archives