g...@gson.org (Andreas Gustafsson) writes:
>Could this also be leveraged to fix PR 51503, and/or to eliminate the need
>for the amd64 live-image target to build both NetBSD-N.M-amd64-live-wd0root.img
>and NetBSD-N.M-amd64-live-sd0root.img?
Not fully. It might help for a specific live image, but d
k...@munnari.oz.au (Robert Elz) writes:
>The proposed change looks fine to me - I tried to think of any cases
>where it wouldn't work properly, and could not come up with any (provided
>the sysctl is working of course). My only concern would be the amount
>it adds to libc (in terms of file size)
jmcne...@invisible.ca (Jared McNeill) writes:
>I came up with this simple patch to getfsspecname that allows ROOT=
ROOT= only works for your special case where you know the root
partition. An alias that represents device+partition would be more
versatile.
For that DEV_USES_PARTITIONS (from kern
Jared McNeill wrote:
> The ARM images currently contain an fstab entry that points to ld0. I want
> to make this more generic as we may have different root devices and/or
> root device units may not be consistent across reboots.
>
> I came up with this simple patch to getfsspecname that allows R
Date:Sun, 30 Sep 2018 17:39:47 -0500
From:=?utf-8?B?Q8OhZw==?=
Message-ID: <20180930223947.sfc8-%c...@bitmessage.ch>
| It'd be more consistent with the rest of the file.
More consistent with a file that contains NAME=thing ... ?
The proposed change looks fine to
Jared McNeill wrote:
> I came up with this simple patch to getfsspecname that allows ROOT=
> syntax for fs_spec. It uses the value of the kern.root_device sysctl to
> construct a device path, so my fstab can have entries like this:
>
>ROOT=a / ffs rw,noatime
The ARM images currently contain an fstab entry that points to ld0. I want
to make this more generic as we may have different root devices and/or
root device units may not be consistent across reboots.
I came up with this simple patch to getfsspecname that allows ROOT=
syntax for fs_spec. It u
