svn commit: r220982 - in head: . sys/amd64/conf sys/arm/conf sys/conf sys/i386/conf sys/ia64/conf sys/mips/conf sys/mips/malta sys/pc98/conf sys/powerpc/conf sys/sparc64/conf sys/sun4v/conf

[Alexander Motin]

On 26.04.2011 11:02, Pawel Jakub Dawidek wrote:
> Now, what about fstab? There is a problem to figure out which disk we
> booted from once we enter the kernel. I was wondering if we could detect
> that someone is trying to mount root which from 'ad[0-9]+<X>' and
> then we could scan all ada[0-9]+<X>  looking for UFS file system and
> /etc/fstab in there and / entry which matches vfs.root.mountfrom variable.
> This should cover 99% of cases. 1% is for cases where another disk have
> identical partitioning scheme and /etc/fstab file. There also might be
> cases where someone defines vfs.root.mountfrom in /boot/loader.conf and
> doesn't really use /etc/fstab.

I think it will be unpredictable. Many disks may have s1a and especially 
s1d.

What do you think about this:
http://docs.freebsd.org/cgi/mid.cgi?4DB54BA9.5050901
? I've found that zpool utility don't likes symbolic links, but except 
this and together with fixing hardcoding problem IMHO it looks not bad.

-- 
Alexander Motin