tired to export display settings maually before using X exports?
try adding this to your “~/.bashrc”
if [ -z "$DISPLAY" ]; then
if [ `ps -awwwux|grep X11.app |grep -vc grep` -gt 0 ]; then
export DISPLAY=":0.0"
fi
fi
Excerpt from Viscosity Support Forums:
Problem is, I want the standard 192.168.x.x and the 10.x.x.x networks to be routed locally, not through the VPN.
Try the following:
1. Go to the Viscosity menu, select Preferences, and Edit your connection
2. Click on the networking tab
3. Click the small “+” button in the Routing section to add a new route
4. Enter a Route/IP of “192.168.0.0″ (no quotes). Enter a submask of “255.255.0.0″. Enter a gateway of “net_gateway”. Click the Add button.
5. Repeat steps 3 and 4, expect with a Route/IP of “10.0.0.0″, and a submask of “255.0.0.0″
6. Click the Save button and try connecting.
The “net_gateway” command instructs the traffic to be routed through your normal local gateway rather than through the VPN connection.
Wanted: files with 0660, directories with 770
Config:
Problem: OS X clients creates
Solution:
unix extensions = no
in smb.conf on server
Since I’m using Mac OS X for admin tasks at work I was annoyed about the keymappings and presets in Terminal.app. As bash is the standard shell in Leopard, I missed the settings that I’m accustomed to as a long term Linux user and admin.
If every solution could be so easy. Just create the neccessary config files:
touch ~/.bash_profile
paste the following code in ~/.bash_profile:
if [ -f ~/.bashrc ]; then source ~/.bashrc fi
touch ~/.bashrc
As usual, you can tweak almost all bash settings in your “~/.bashrc”.
Here are some examples:
# Define how Bash prompt looks like: # # User @ Host - working dir export PS1='\u@\h\w: ' # Cli Colors export CLICOLOR=1 # use bold blue for dir’s export LSCOLORS=Exfxcxdxbxegedabagacad # history handling # # Erase duplicates export HISTCONTROL=erasedups # resize history size export HISTSIZE=5000 # append to bash_history if Terminal.app quits shopt -s histappend alias l='ls -al'
Adapt the keyboard mappings to your needs:
touch ~/.inputrc
The following code shows some example setting for your ~/.inputrc:
# do not bell on tab-completion set bell-style none # set bell-style visible set convert-meta off set input-meta on set output-meta on set show-all-if-ambiguous on set visible-stats on set completion-ignore-case On "\e[1~": beginning-of-line "\e[4~": end-of-line "\e[5~": history-search-backward "\e[6~": history-search-forward "\e[3~": delete-char "\e[2~": quoted-insert "\e[5C": forward-word "\e[5D": backward-word "\e\e[C": forward-word "\e\e[D": backward-word
warum dieses Blog auf einmal so anders aussieht.
Richtig: bin auf den Mac gekommen 
Zugegeben, ich bin ein wenig spät dran (übler Mitläufer). Nach den blumigen Lobpreisungen eines durchaus begabten Coders der mit Vista auf die Klappe fiel (siehe Blogroll), wollte ich’s wissen. In der Firma lag gerade noch ein herrenloses Powerbook G4 17″ und wartete auf sinnvolle Verwendung – ein Wink mit dem Zaunpfahl.
Kurzfassung: innerhalb von 48 Stunden alle produktiven Anwendungen auf OS X migriert. Alles mit Bordmitteln oder Freeware/OpenSource. Seit gut 8 Wochen keine Abstürze, keine Bluescreens. Funktionierendes ACPI, reboot nur in Ausnahmefällen z.B. Programminstallation oder Updates. Wechseln der Monitor-Konfiguration ohne Probleme. WLAN, Bluetooth, Drucken – alles klappt reibungslos.
Die heimische Windows-Workstation wurde mittlerweile durch einen iMac ausgewechselt.
Bye bye WinXP – nicht alles war schlecht, aber die Summe der Probleme nicht akzeptabel.
