> I'd like to suggest a name: lsdisk and lspart to list the disks and also > the disks/partitions that are available. (Or maybe lsdisk should just > list the disks and partitions in an indented list? Listing the > partitions is important. Listing the controllers might not hurt > anything, either.)
Hmmm... the current scheme seems to be "subject verb <object>". E.g. disk list or disk info c1t9d0 disk info -p c1* With partitions, I assume you mean slices. Partitions are outside of Solaris and managed by fdisk. > Linux has lspci[0], lsscsi, lsusb, lsof, and a number of other > ls-tab-tab utilities out-of-the-box[1]. These utilities would be quite > intuitive for folks who've learned Linux first, and would help people > transition to Solaris quickly. Do we really need to bend and warp everything to suit Linux switchers? (only half :-). > When I first learned Solaris (some years ago now), it took me a > surprisingly long time to get the device naming scheme and the partition > numbering. The naming/numbering is quite intuitive (except for that > part about c0t0d0s2 being the entire device[1]), but I would have felt > that I understood it quicker if I'd seen a nice listing that matches the > concept, and also had quick way to find out the name of that disk that I > just plugged in. My friends who are new to Solaris seem to have the > same problem out of the gate. I did not have this experience. I came from BSD where there were things like /dev/sd0d (which also exist on Solaris), but the Sun way was not too strange... > [0] Including lspci and lsusb with Solaris would be a great idea -- Well, there is scanpci. > [1] Since Solaris 10 still uses /bin/sh as the root shell, I feel that I > must explain that this is tab completion. In bash/zsh/tcsh, hitting tab > twice searches the $PATH for ls* and displays the results.... I know > that most-everyone on the list already knows this, but I can't help my > self! [ducks!] At the risk of outing myself as a hardcore nit picker, in tcsh it is Control-D, and only once, not twice. :-) > > [2] If I'm giving someone a tour of Solaris administration, /dev/sda > isn't particularly different from /dev/dsk/c0t0d0. But if I open > /dev/dsk/c0t0d0s2 with a partitioning tool, repartition, then > build/mount a filesystem without Something Bad happening, then my > spectators heads usually explode. After that, they don't believe me > when I tell them that they mostly understand what's going on. Yes, ZFS > and the EFI disklabels fix this when you have a system with a ZFS root > and no UFS disks -- but UFS is still necessary in a lot of > configuration, so this kind of system-quirk should be made obvious to > Unix-literate people coming from non-Solaris backgrounds. Maybe it's because I have a Solaris background, but I fail to see any quirk here... Best regards -- Volker -- ------------------------------------------------------------------------ Volker A. Brandt Consulting and Support for Sun Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim Email: [EMAIL PROTECTED] Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 45 Geschäftsführer: Rainer J. H. Brandt und Volker A. Brandt _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
