On Apr 2, 10:33am, g...@ir.bbn.com (Greg Troxel) wrote: -- Subject: Re: CVS commit: src/sys/dev/raidframe
| It seems there are 3 behaviors for root | | 1) don't change the root device (old behavior with -A yes) That does autoconfig for raid and does not deal with root at all. | 2) if root is on a component, change root to the raid, otherwise don't | change. This behavior did not exist before my commit. It is now only turned on with -A root. | 3) force the root device to be the raid (old behavior with -A root) This does not exist anymore. You can currently: 1. boot -a 2. make a kernel that has root on raidx Or: 1. add the ability to pass the root name through the bootblocks/userconf 2. add a raidctl -A forceroot and obey that. | It seems to me that the behavior 1 (not in case 2) isn't useful, and | that we could make behavior 2 the default behavior, with 3 with -A yes. Yes, I think you are right. There could be an issue with having wd0a being the real root and then a raid component on wd0e... In that case do we want to make wd0e the root device because it is on the same drive? | Is there any reason why someone would not want to use the raid for root | when a) the system booted from a component and b) it's marked | autoconfigurable? If anything, I think there should be a way to disable | autoconfiguration. See above... There is a way to disable autoconfiguration, but there is currently no easy way to get the old behavior? What do you think we should do? christos