Using Linux Mail command to send out "Display Name"

When sending out email through Linux mail command, the program will fetch the user information through options or configuration files. A typical scenario is the user's description in /etc/passwd ( or a central NIS server passwd file), will be include in the email header "From=user@domain.com (user description)". And in a outlook client, the "user description" will be display in "From" colum.

Here is the problem, sometimes, the user description in password file is not for a good summary for the user, it may contain some other inforamtion for the administrators. Then the user need change this field manually when sending out email.

Two options to do that,

mail -r "123@123.com (I am 123)" 456@456.com
or
env from="123@123.com (I am 123)" mail 456@456.com

Then the receiver will see a email from "I am 123" in Outlook.

Boot SUSE Linux on POWER

Booting SUSE Linux On IBM POWER

SUSE has automated necessary configuration step to LILO for PPC. Here is the information how it works.

The firmware of IBM POWER, which is named OPENFIRMWARE, will look for the boot device according to a bootlist. The bootlist could be changed from the Linux. OPENFIRMWARE could be configured either to look for a PREP partition of SCSI disks, or a bootable file on the 1st primary partition which could be formatted as FAT16. SUSE uses the 2nd way to do the booting.

Steps LILO performs,
Create the partition, and formatted to FAT16. The partition should be the 1st partition of the disk.
Create a yaboot.cnf according to /etc/lilo.conf.
Copy "yaboot", "yaboot.cnf", kernel image and initrd to this partion.
Modify bootlist of the FIRMWARE to look for file "yaboot" instead of the whole partition.

+++++++
+ sda1 + <--- The boot partion, FAT16.
+++++++
+ sda2 + <--- Other partition or partitions
+++++++

Below is an example of how the system is configured,

/*+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

# fdisk -l /dev/sda

Disk /dev/sda: 214.7 GB, 214748364800 bytes
255 heads, 63 sectors/track, 26108 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 4 32098+ 6 FAT16
/dev/sda2 5 19264 154705950 fd Linux raid autodetect
/dev/sda3 19265 20439 9438187+ fd Linux raid autodetect
#
# mount /dev/sda1 /mnt/sda1
# ls /mnt/sda1
initrd.001 initrd.002 ppc vmlinux.001 vmlinux.002 yaboot yaboot.cnf
#
# show_of_path.sh /dev/sda
/vdevice/v-scsi@3000001a/disk@8100000000000000
# show_of_path.sh /dev/sdb
/vdevice/v-scsi@3000002e/disk@8100000000000000
#
# bootlist -m normal -r
/vdevice/v-scsi@3000001a/disk@8100000000000000:1,yaboot
/vdevice/v-scsi@3000002e/disk@8100000000000000:1,yaboot
/vdevice/l-lan@3000000b:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
#

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*/

The manpage of "show_of_path.sh" and "bootlist" will tell more information about these two commands.

Because LILO for PPC will handle all these works, all an adminsitrator need do is to modify the /etc/lilo.conf to reflect the right boot partition and kernel name, and run /sbin/lilo to update the change to boot partition. The only exception is when you have multiple booting partition. There is an entry in /etc/lilo.conf, named "boot = xxxx", which will be used by LILO to decide which partition to update. Like the case above, there are two boot partition, sda1 and sdb1, so administrator should run lilo twice with boot=sda1 and boot=sdb1 seperately.


Reference:

1. http://www.ibm.com/developerworks/systems/library/es-conf-swraid/
2. Chapter 9 and 13 of http://www.linux.org/docs/ldp/howto/IBM7248-HOWTO/index.html
3. http://www.ibm.com/developerworks/systems/library/es-SW_RAID_LINUX.html

UUID or label of ext2 file system in LINUX

To view a file system's UUID or Label,

>vol_id /dev/sda1



To change of an ext3 file system's UUID

>uuidgen

>tune2fs /dev/sda1 -U "new-uuid-number"

>vol_id /dev/sda1


To change of a ext3 file system's label

>tune2fs /dev/sda1 -L "new-label"