Skip to main content

Old School profile


Now - I believe the preferred methodology is to take advantage of .bashrc and .bash_profile
.bashrc is now intended to have alias(es) and functions
.bash_profile will have environment and startup programs

They appear to be called in this order...
.bash_profile
  ->  .bashrc
    ->  /etc/bashrc
         (source /etc/bashrc)
    (source ~/.bashrc)
(source .bash_profile)

So - customizations you add to your own files actually get sourced last.  Specifically the .bash_profile customizations.  Kind of interesting, if you stop to look at the process.



#
# Copyleft (c) 2003 by Crashwerx Macrosystems, Inc.
# All rights reserved.
#
# ident "@(#).profile      1.10    01/06/23 SMI"
# Optimized for ksh

# TERMINAL SETTINGS
stty istrip
#stty erase ^?
stty -echoctl
ulimit -c 0
umask 022

TERM=vt100
EDITOR=vi
VISUAL=vi
OS=`uname`
hostname=`hostname | cut -f1 -d.`
# Make ssh connections (C)ompressed and enable (X)-forward
alias SSH="ssh -X -C $1"

PATH=$PATH:/usr/bin/:/sbin:/usr/sbin:
case $OS in
 SunOS)
   PS1="`/usr/ucb/whoami`@${hostname} $ "
   echo "\033]0; `uname -n` - `/usr/ucb/whoami` \007"
   PATH=$PATH:/usr/sfw/bin:/opt/sfw/bin:/usr/sfw/sbin:/opt/sfw/sbin:/usr/openwin/bin
   PATH=$PATH:/usr/ucb/:/usr/platform/sun4u/bin:/usr/platform/i86pc:/usr/ccs/bin
   PATH=$PATH:/opt/VRTS/bin:/opt/VRTSvcs/bin:/usr/openv/netbackup/bin
   PATH=$PATH:/usr/openv/volmgr/bin:/opt/SUNWsrspx/bin:/opt/SUNWppro/bin
   LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/sfw/lib:/opt/sfw/lib
 ;;
 AIX)
   PS1="`/usr/bin/whoami`@${hostname} $ "
   echo "\033]0; ${hostname} - `/usr/bin/whoami` \007";
 ;;
 *)
   PS1="`/usr/bin/whoami`@${hostname} $ "
   echo -ne "\033]0; ${hostname} - `/usr/bin/whoami` \007";
 ;;
esac

# OpenSourc'y type crap...
PATH=$PATH:/opt/sfw/bin:/usr/local/bin:/usr/local/sbin:/opt/bin:/opt/Acrobat5/bin:/usr/gnome/bin::/opt/csw/bin
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/lib:/usr/lib:/usr/share/lib:/usr/local/lib:/usr/gnome/lib:/opt/gnome/lib:/opt/csw/lib:/usr/local/ssl/lib:

MANPATH=$MANPATH:/usr/share/man:/opt/VRTS/man

JAVA_HOME="/usr/j2se"
#echo "fix shift key issue: setxkbmap"

export TERM EDITOR VISUAL PS1 PATH LD_LIBRARY_PATH MANPATH JAVA_HOME

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.