Solaris

Definitely go over the new commands introduced in S10.

Other great talking points:

- Leadville HBA drivers , which is why they may see long target names...

4. c6t5006016141E00C85d0 <DGC-RAID5-0326 cyl 40958 alt 2 hd 128 sec 10>
/pci@7,700000/emlx@0/fp@0,0/ssd@w5006016141e00c85,0


- LDOMs/sun4v - LDOMs can only be leveraged on servers using sun4v architectures (Sun T1000/T2000/T5220, etc). I state this to avoid confusion.

- DTrace should only be introduced to advanced users, but sample scripts can be found in /usr/demo/dtrace

i think dtrace is going beyond what they may need to know. advanced debugging should not be a field engineer's task.

dtrace alone could be a week long class.

debugging of what?

any problem or performance issues on a system...

this is what i call "troubleshoting". debugging is something on softwarelevel... (in my opion).

hahah. i see your point. i guess i use the term to loosely.

so lets try it again... advanced troubleshooting

what about user environment?? do they know that? how to change it, set it up to whatever. just trying to think of something more meaningful to their everyday tasks (which i only have a brief idea as to what they actually do from what you said).

i do like your topics on SMF and predictive self healing.

how about setting up services to be managed by SMF? moving away from legacy rc.

i know they do installs and patching but do they know all the different ways of doing this??

maybe i'll to a short introduction of JET... not a bad idea...

p.s. i've edited the first post to reflect the input...