On Wed, May 4, 2011 at 8:16 AM, krad <kraduk_at_gmail.com> wrote: > On 4 May 2011 04:13, Jason Hellenthal <jhell_at_dataix.net> wrote: >> Edwin, >> >> >>> >> /dev/acd0 /cdrom cd9660 ro,noauto 0 >> 0 >> >>> >> /dev/acd1 /cdrom1 cd9660 ro,noauto 0 >> 0 >> >> As a side note. These are also now useless & can be sent to /dev/null for >> extra padding ;) >> >> Shouldn't cause no harm being there but just for reference. >> > Just a sanity check here people, but if the machine was built with freebsd > 6.x i would guess it machine is a few years old. If so i doubt the hardware > would support ahci, and therefore wouldn't have the ada type devices, it > would have the old ad style ata ones and therefore noe fstab twiddling > should be necessary. > > Forgive me if im missing something here. If you enable "options ATA_CAM" in the kernel, which uses the old ata(4) driver via some cam(4) shims, then you also get the adaX device nodes. There's currently 4 ways to access PATA/SATA disks: - old-style ata(4) using adX device nodes - old-style ata(4) using ataahci(4) for ACHI-like access to PATA/SATA disks, I believe using adX - old-style ata(4) via ATA_CAM using adaX device nodes - new-style ahci(4)/siis(4)/another(4) using adaX device nodes I forget the name of the other AHCI-style driver. The first two options uses atacontrol to manage the disks. The last two options use camcontrol to manage the disks. I believe the plan in 9.0 is to have everything accessed via ATA_CAM/ahci(4) so all PATA/SATA drives show up the same, as adaX, with everything being managed via camcontrol, finally unifying all PATA/SATA/SCSI/SAS disk access via cam(4). -- Freddie Cash fjwcash_at_gmail.comReceived on Wed May 04 2011 - 14:03:06 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:13 UTC