Re: kern/46732: setroot(9) is called twice after "MI root onwedges"changes

[Michael van Elst <mlelstv%serpens.de@localhost>]

The following reply was made to PR kern/46732; it has been noted by GNATS.

From: Michael van Elst <mlelstv%serpens.de@localhost>
To: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, mlelstv%NetBSD.org@localhost
Subject: Re: kern/46732: setroot(9) is called twice after "MI root
 onwedges"changes
Date: Wed, 25 Jul 2012 19:57:08 +0200

 On Wed, Jul 25, 2012 at 08:56:55PM +0900, Izumi Tsutsui wrote:
 > mlelstv@ wrote:
 > 
 > > And as my idea for rootconf() was to also clean up the root-on-raidframe
 > > hack later, things would be even more complicated.
 > 
 > What won't actually work are you claiming?
 > Just root on wedge (or raidframe) case?
 
 Yes.
 
 
 > Not RB_ASKNAME case, but "bootloader is loaded via network,
 > but a kernel needs to be loaded from harddisk (or viceversa)."
 > 
 > In that case, a user has to specify a kernel loadpath (including
 > device name) on the bootloader's prompt at the first boot, but
 > no need to specify it on the bootloader prompt after reboot.
 
 Sounds like a strange edge case. Isn't passing back the loadpath
 much easier?
 
 
 > Indeed, but isn't it better to allow MD post-setroot()-hooks
 > if it's trivial?
 
 I still don't believe that this belongs here.
 
 
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."