Since mdconfig can autoallocate the device, why is this needed ?
In message <[EMAIL PROTECTED]>, Makoto MATSUSHITA writes:
>
>src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable
>(formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to
>configure md -- trivial, a
> Also, I think that this isn't the right fix to a bigger problem.
> Instead, it shouldn't be hard to get a list of configured devices
> out of mdconfig via an ioctl on /dev/mdctl. This would be the right
> fix, as it would fix the general case problem you describe, not just
> one instance of it.
Oops, sorry that From: address was different from the first email...
jhb> Instead, it shouldn't be hard to get a list of configured devices
jhb> out of mdconfig via an ioctl on /dev/mdctl. This would be the
jhb> right fix, as it would fix the general case problem you describe,
jhb> not just one
On 04-Feb-01 Makoto MATSUSHITA wrote:
>
> jhb> The current method always finds an unused device to use, so the
> jhb> old VNDEVICE-style hack is no longer needed. There's no point to
> jhb> setting an explicit device to use.
>
> But I want to ensure that all used md(4) devices is unconfigured
jhb> The current method always finds an unused device to use, so the
jhb> old VNDEVICE-style hack is no longer needed. There's no point to
jhb> setting an explicit device to use.
But I want to ensure that all used md(4) devices is unconfigured after
it is used.
Imagine you run 'make release' f
On 03-Feb-01 Makoto MATSUSHITA wrote:
>
> src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable
> (formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to
> configure md -- trivial, add '-u' option if MDDEVICE is already defined.
But you shouldn't need this. The
