Monday, August 8, 2011
Why such a ridiculous restriction?
Monday, March 14, 2011
With putty, the following batch file will do the trick (pass the destination host as the first argument):
echo ssh %1 > "%DATFILE%"
start putty -load "<putty session name>" <intermediate> -t -m "%DATFILE%"
Sunday, March 6, 2011
Sadly, the Putty folks have failed to incorporate the change into winpgntc.c.
Saturday, February 12, 2011
I tracked the problem down to a Java property that disables use of DirectDraw. A lot of Java apps seem to do this due to a poor implementation in earlier versions of java (*sigh*). Fortunately, there's an easy fix -- the property can be changed by adding this to the command line:
Saturday, February 5, 2011
Thursday, February 3, 2011
- Pageant’s security measures reject the proxy request due to the two processes running with different SIDs.
- The proxy agent isn’t seen by any processes launched from your outside your shell (since the environment variables only get set in ~/.bash_profile)
Here’s my solution for issue #2. Instead of running keychain at the start of every login shell, just run it once at Windows startup, and set the environment variables system-wide using setx. Here’s my shell script that does that:
# Be sure to run this script in a login shell so that cygwin paths are properly
# set, otherwise the Windows version of hostname will run and mess things up
/usr/bin/keychain -q -Q
# The -csh script works perfectly since we can just substitute setx for setenv
Since this is only running once at startup, keychain isn’t really needed. And to simplify a bit more, it can be done in a batch file:
REM The -csh script works perfectly since we can just substitute setenv for setx
charade -c | sed 's/setenv/setx/' | sed 's/;$//' > %FN%
Saturday, January 8, 2011
If you run p4 sync in Linux from outside the AltRoot location, p4 will sync to a new directory with the name of the p4 Root. Say you accidentally run p4 sync from the /etc dir – you’ll end up with a directory like /etc/S:\workspace, and your real workspace directory will now be out of sync. (This isn’t a problem with p4 for cygwin, since cygwin can interpret Windows paths.)
Here’s a workaround:
1) Remove the base directory from the Root and AltRoot paths
2) Add the base directory to all paths in the workspace mapping
3) Add / as a second AltRoot
4) Create a symlink in / with the name of the base directory, pointing to the real location.
By using / as a second AltRoot, every linux directory will match, and the default root will never be used.
Here's a simpler workaround that instead just results in a an error message when running p4 outside of the workspace root.
1) Set P4CLIENT to something invalid like `XXXXX - Running from invalid root`
2) Set P4CONFIG to `.p4config`
3) Create a file called `.p4config` in your workspace root. Inside add the line `P4CLIENT=[Name]` substituting [Name] with your real client name