Hello,
I use read only /usr also,
I don't like a script changing mount options without a warning.
If it's read-only reorder_kernel should fail.
I just put a symlink from /usr/share/relink to /var/relink and everything
works fine...
With mount_mfs we could have a temporary directory but where has g
Klemens Nanni wrote:
> Reading /etc/rc I was under the impression that read-only /usr is indeed
> a scenario we support, since reorder_libs() already does what I propose,
> only in a more complicated way:
>
> revision 1.481
> date: 2016/05/26 14:59:48; author: rpe; state: Exp; lin
On Mon, Nov 14, 2022 at 03:15:53PM -0700, Theo de Raadt wrote:
> Readonly /usr is not a supported or recomended configuration.
>
> This is adding a lot of scripting that we don't everyone to run.
>
> I disagree strongly with this direction of OpenBSD having undocumented
> (undocumentable?) little
Readonly /usr is not a supported or recomended configuration.
This is adding a lot of scripting that we don't everyone to run.
I disagree strongly with this direction of OpenBSD having undocumented
(undocumentable?) little behaviours that allow root to configure their
machine in novel non-default
On Tue, Nov 08, 2022 at 11:10:19AM +, Klemens Nanni wrote:
> More read-only filesystems mean less fsck during boot after crashes.
> Especially on crappy machines like the Pinebook Poop, I keep /usr
> read-only and run with this diff so I still get a relinked kernel.
>
> rc's reorder_libs() alr
More read-only filesystems mean less fsck during boot after crashes.
Especially on crappy machines like the Pinebook Poop, I keep /usr
read-only and run with this diff so I still get a relinked kernel.
rc's reorder_libs() already does the same remount dance, but for
multiple directories/filesystem
