Ok, I do get stuff in /dev/disk. But I don't get any for the FBA disks (vdisks). Does it ignore those? (dasdl and dasdm below)
sles964:/dev/disk/by-id # lsdasd 0.0.0100(FBA ) at ( 94: 0) is dasda : active at blocksize 512, 250000 blocks, 122 MB 0.0.0201(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, 72000 blocks, 281 MB 0.0.0202(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, 6300 blocks, 24 MB 0.0.0203(ECKD) at ( 94: 12) is dasdd : active at blocksize 4096, 45000 blocks, 175 MB 0.0.0204(ECKD) at ( 94: 16) is dasde : active at blocksize 4096, 36000 blocks, 140 MB 0.0.0205(ECKD) at ( 94: 20) is dasdf : active at blocksize 4096, 63000 blocks, 246 MB 0.0.0206(ECKD) at ( 94: 24) is dasdg : active at blocksize 4096, 563400 blocks, 2200 MB 0.0.0207(ECKD) at ( 94: 28) is dasdh : active at blocksize 4096, 135000 blocks, 527 MB 0.0.0208(ECKD) at ( 94: 32) is dasdi : active at blocksize 4096, 18000 blocks, 70 MB 0.0.0209(ECKD) at ( 94: 36) is dasdj : active at blocksize 4096, 482040 blocks, 1882 MB 0.0.020a(ECKD) at ( 94: 40) is dasdk : active at blocksize 4096, 1260000 blocks, 4921 MB 0.0.ff00(FBA ) at ( 94: 44) is dasdl : active at blocksize 512, 500000 blocks, 244 MB 0.0.ff01(FBA ) at ( 94: 48) is dasdm : active at blocksize 512, 1000000 blocks, 488 MB sles964:/dev/disk/by-id # ls -al total 1 drwxr-xr-x 2 root root 528 May 17 07:57 . drwxr-xr-x 4 root root 96 May 17 07:57 .. lrwxrwxrwx 1 root root 11 May 17 07:57 0X0201 -> ../../dasdb lrwxrwxrwx 1 root root 12 May 17 07:57 0X0201p1 -> ../../dasdb1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0202 -> ../../dasdc lrwxrwxrwx 1 root root 12 May 17 07:57 0X0202p1 -> ../../dasdc1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0203 -> ../../dasdg lrwxrwxrwx 1 root root 12 May 17 07:57 0X0203p1 -> ../../dasdg1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0204 -> ../../dasde lrwxrwxrwx 1 root root 12 May 17 07:57 0X0204p1 -> ../../dasde1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0205 -> ../../dasdf lrwxrwxrwx 1 root root 12 May 17 07:57 0X0205p1 -> ../../dasdf1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0206 -> ../../dasdd lrwxrwxrwx 1 root root 12 May 17 07:57 0X0206p1 -> ../../dasdd1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0207 -> ../../dasdh lrwxrwxrwx 1 root root 12 May 17 07:57 0X0207p1 -> ../../dasdh1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0208 -> ../../dasdi lrwxrwxrwx 1 root root 12 May 17 07:57 0X0208p1 -> ../../dasdi1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X0209 -> ../../dasdj lrwxrwxrwx 1 root root 12 May 17 07:57 0X0209p1 -> ../../dasdj1 lrwxrwxrwx 1 root root 11 May 17 07:57 0X020A -> ../../dasdk lrwxrwxrwx 1 root root 12 May 17 07:57 0X020A1 -> ../../dasdk1 Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Christian Borntraeger Sent: Thursday, May 17, 2007 7:40 AM To: [email protected] Subject: Re: [LINUX-390] Using UDEV on sles9x Am Donnerstag, 17. Mai 2007 15:22 schrieb Marcy Cortes: > I'd like to be able to reference devices like /dev/dasd/8000/part1 > instead of via /dev/dasdc1. (or /dev/dasd/0.0.8000/part1 is close > enough) like Levanta does. > > Reading all the device driver stuff it looks like I need to implement udev. > I can't for the life of me figure out how to turn this on! Has anyone > done this? If you run udevstart, you will get several symbolic links in /dev/disk/. If that works, there is an init script to let udev run on every boot: /etc/init.d/boot.udev # chkconfig boot.udev on will turn udev on. -- IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Herbert Kircher Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
smime.p7s
Description: S/MIME cryptographic signature
