Date: Tue, 26 Apr 2011 12:05:00 -0700 From: Doug Barton <dougb@FreeBSD.org> To: "Andrey V. Elsukov" <ae@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, Alexander Motin <mav@FreeBSD.org> Subject: Re: Why not just name the cam-ata devices the same as the old names? Message-ID: <4DB7175C.6060408@FreeBSD.org> In-Reply-To: <4DB71654.5060008@FreeBSD.org> References: <4DB70949.6090104@FreeBSD.org> <4DB70F97.1070809@FreeBSD.org> <4DB71311.7080203@FreeBSD.org> <4DB71654.5060008@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/26/2011 12:00, Andrey V. Elsukov wrote: > On 26.04.2011 22:46, Doug Barton wrote: >> If that plan proves successful what I'm thinking is that I can put some >> code in mergemaster on 9.0-RELEASE that checks for the old device names >> in /etc/fstab and suggests that the user change them to the new names. I >> don't generally like to give mergemaster specific knowledge of certain >> files, but there is precedent for doing so for changes like this, and as >> long as we are not relying on mergemaster to _fix_ the problem, I'm Ok >> with doing it that way. So I will stay tuned to see how this develops. > > mergemaster usually used a bit later than it can help, i mean that we > recommend run it after installing kernel and first reboot. Right, that's one reason I don't want mergemaster to be the solution for fixing this. Another is that not everyone uses it, and almost noone who uses freebsd-update uses it. To be clear about what I meant, assuming that there is some solution which allows users with the old adN entries to boot with the new cam-ata devices, mergemaster can detect this condition, and warn the user that they should update their fstab. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DB7175C.6060408>