Date: Sat, 27 Jun 2009 14:22:00 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: FreeBSD-Current <freebsd-current@freebsd.org>, scottl@FreeBSD.org Subject: Re: RFC: ATA to CAM integration patch Message-ID: <4A4600D8.5020105@FreeBSD.org> In-Reply-To: <20090627125036.000017f1@unknown> References: <4A4517BE.9040504@FreeBSD.org> <20090627125036.000017f1@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Leidinger wrote: > On Fri, 26 Jun 2009 21:47:26 +0300 Alexander Motin <mav@FreeBSD.org> > wrote: >> - make sure that you will be able to boot if your SATA disk devices >> name change from some ad4 to ada0; > > Will it stay at adaX, or is it planned to move it to daX like other > harddisks attached via SCSI? If it stays like it is now: what's the > rationale to use a different name? It is still point of discussion. I have arguments for 3 different options: da - PRO: habitual CAM/SCSI disk name; CONTRA: ATA disk uses completely separate ATA-native peripheral driver, it is difficult use the same name for two drivers and it IMHO looks ugly: ad - PRO: habitual ATA disk name; CONTRA: heavily conflicts with ATA_STATIC_ID ata(4) option device unit numbering, also the same driver name conflict, but a bit easier due to different parent bus; ada - PRO: perfect from internal infrastructure PoV; CONTRA: just unhabitual. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A4600D8.5020105>