Subject: Re: ahc or disk problem?
To: Tracy J. Di Marco White <gendalia@iastate.edu>
From: Wojciech Puchar <wojtek@chylonia.3miasto.net>
List: netbsd-users
Date: 09/05/2002 21:44:28
> Sep 4 15:49:58 flow2 /netbsd: sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST336752LC, 2213> SCSI3 0/direct fixed
> Sep 4 15:49:58 flow2 /netbsd: sd0: 34732 MB, 18496 cyl, 8 head, 480 sec, 512 bytes/sect x 71132959 sectors
> Sep 4 15:49:58 flow2 /netbsd: sd0: sync (25.0ns offset 63), 16-bit (80.000MB/s) transfers, tagged queueing
> Sep 4 15:49:58 flow2 /netbsd: sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST336752LC, 2213> SCSI3 0/direct fixed
> Sep 4 15:49:58 flow2 /netbsd: sd1: 34732 MB, 18496 cyl, 8 head, 480 sec, 512 bytes/sect x 71132959 sectors
> Sep 4 15:49:58 flow2 /netbsd: sd1: sync (25.0ns offset 63), 16-bit (80.000MB/s) transfers, tagged queueing
> Sep 4 15:49:58 flow2 /netbsd: ses0 at scsibus0 target 6 lun 0: <PE/PV, 1x3 SCSI BP, 0.26> SCSI2 3/processor fixed
> Sep 4 15:49:58 flow2 /netbsd: ses0: SAF-TE Compliant Device
> Sep 4 15:49:58 flow2 /netbsd: ses0: async, 8-bit transfers
sorry if stupid question - but what's "ses"?
i found only comment it's SCSI enclosure device, but not man (1.5.3)
what is it?