davdunc

 . /usr/share/Modules/init/bash

 [root@master iozone]# set | grep MODULE
 LOADEDMODULES=
 MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles:
 MODULESHOME=/usr/share/Modules

 #!/bin/bash
 . /usr/share/Modules/init/bash
 module list
 module purge
 module list
 module avail
 module load mpi/openmpi-mellanox-interconnects-gcc
 module list

 sh ~/sandbox/modu.sh
 No Modulefiles Currently Loaded.
 No Modulefiles Currently Loaded.
 
 ----------------------------------------------- /usr/share/Modules/modulefiles -----------------------------------------------
 PMPI/modulefile                           mpi/mvapich1-platform-interconnects-gnu
 dot                                       mpi/mvapich2-platform-interconnects-gnu
 module-cvs                                mpi/openmpi-mellanox-interconnects-gcc
 module-info                               mpi/openmpi-mellanox-interconnects-intel
 modules                                   mpi/openmpi-mellanox-interconnects-pgi
 mpi/mvapich1-mellanox-interconnects-gcc   mpi/openmpi-platform-interconnects-gnu
 mpi/mvapich1-mellanox-interconnects-intel null
 mpi/mvapich1-mellanox-interconnects-pgi   use.own
         This module will prepend the openmpi-mellanox-gnu bin, man and lib directories
         to the PATH, MANPATH and LD_LIBRARY_PATH environment variables,
         respectively.
 
 Currently Loaded Modulefiles:
   1) mpi/openmpi-mellanox-interconnects-gcc
 [root@master iozone]#

The smbios-utils and the corresponding libsmbios are available from the dell-community repo. That repo is maintained by Dell. The bios revisions for the M1530 appear to be considerably out of date. A run of yum install $(bootstrap_firmware) returns no updates. I figure that means that there are no other XPS M1530 squeaky wheels (such as myself) or there are just no better updates than the A08 I am currently running. As I recall my last attempt to update beyond A08 crippled my mousepad.

So the good news is that the Wireless controller is working. The bad news is that BIOS update A12 is out there waiting for me to rip the .hdr out with . . . what? I don't know. extract_hdr is gone and firmware_tool doesn't have the --extract method I was hoping to use to remove it.

Sad thing is that I know whose fault it is that it isn't working. It is mine. I am Fedora.

I am sure that the majority of my Linux friends would not make the same mistake I made on my latest installation of postfix. I am most dependent upon the use of google apps to manage my mail service over the last few . . . years(!) Wow! Has it really been that long? Well . . . anyway I made a simple mistake and only 5 minutes on #postfix on irc.freenode.net (donate!)

So what did I do? I set my hostname to thekaratekidsband.com and then I let postfix use that. What does postfix do with a hostname like "thekaratekidsband.com"? It uses the second section of the hostname to populate the second level of the domain name.  Then it uses the last section of the hostname to populate the third level.  This is the automated method of populating the value $mydestination.  This isn't helpful if your hostname is not very basic.

I was using a hostname of thekaratekidsband.com  and the result was the domain name com.com and that wasn't what I was expecting.  If you are using postfix, then you will get your best default results from a simple 3-level hostname.  If you are not using a simple host configuration or you are using a simple configuration that does not match the basic configuration then you may need to modify your $hostname or $mydestination. 

I was looking for a real method for troubleshooting the construction of this name.  I did not actually find the method for debugging the rewrite.  It didn't seem to happen in a way that was exposed in the expanded vars or in the debug, but I did find two users on #postfix who queued the channel bot to tell me how it worked.  They pointed me to $myorigin to show me the problem.  On my server $myorigin returned the same value as $domain.  I just assumed that the rewrite described for the mydestination was the problem. 

I look forward to reading a better explanation or getting one in the comments. :-)

http://www.postfix.org/BASIC_CONFIGURATION_README.html#myorigin  for informaiton (note that's the first page)