Date:Sat, 1 Apr 2023 12:08:47 -0400 (EDT)
From:Mouse
Message-ID: <202304011608.maa07...@stone.rodents-montreal.org>
| I would much prefer to use the existing mechanisms to specify
| filesystem-specific parameters more generally
I agree. The proposal looks like
>> mount /dev/dk0:bart /mnt
> I would much prefer to use the existing mechanisms to specify
> filesystem-specific parameters more generally. [...]
> mount -t foo -o -x=bart /mnt
(a) Oops, that should be
mount -t foo -o -x=bart /dev/dk0 /mnt
(b) This is what I did back in the 1
> mount /dev/dk0:bart /mnt
> mount /dev/dk0%lisa /mnt
> mount /dev/dk0@maggy /mnt
> Our current mount(8) and all other file systems uses pathadj() from
> sbin/mount/pathadj.c that is really a wrapper around realpath(3).
> My proposal is to adjust
> pathadj(const char *inpu
Dear folks,
there are file systems that although living in one partition/device support
multiple heads/labels to mount on that can't be expressed as a disk partition
scheme like disklabel or GPT since they all live in one partion.
A common way to mount such systems is to append the head-name to t