Thanks to: Bryan Moore, Kevin Graham, Darren Dunham, Glenn Cantello, David Foster, Tim Fritz, Bryan Pepin. Nobody really provided a way to tell writable disk devices from read-only devices, but all the suggestions pointed me to a simple solution that solved my current problem, which was to determine the boot disk at JumpStart time. The answer: let JumpStart determine it itself. The boot disk can then be referred to in the rest of the profile as "rootdisk". This resulted in the following profiles: For initial installation, install_type initial_install system_type server boot_device any update partitioning explicit filesys rootdisk.s0 free / filesys rootdisk.s1 2048 swap filesys rootdisk.s3 128 cluster SUNWCXall For upgrade, install_type upgrade cluster SUNWCXall My original question: >>I am trying to programmatically generate a profile for JumpStart >>installations. The issue, here, is that I cannot predict the disk that >>will be used for O.S. installation. >> >>In 99% of cases, I will be able to use "c0t0d0s0", but there are fringe >>cases where the actual disk where I put my root partition is on a >>different device name (case in point, my SunFire 280R is installed on >>"c1t0d0s0", while the device on controller 0 is the CD-ROM drive). >> >>I know I can determine the list of mountable devices using "iostat -xpn", >>but how can I detect whether the device is a writable disk, suitable for >>Solaris installation, or if it isn't (CD-ROM drive or other read-only >>device)? The "format" command seems to be able to do that. >> >>Thanks in advance. +===========================================================+ | Fabrice "Script It!" Guerini Blue Martini Software, Inc. | | Senior Operations Engineer 2600 Campus Drive | | Tel: (650) 356-7576 San Mateo, CA 94403-2522 | | Fax: (650) 356-4001 www.bluemartini.com | +===========================================================+ _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Fri May 17 15:16:51 2002
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:43 EST