From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18747 invoked by alias); 21 Dec 2016 19:15:28 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22243 Received: (qmail 19997 invoked from network); 21 Dec 2016 19:15:28 -0000 X-Qmail-Scanner-Diagnostics: from mta01.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(24.224.136.30):SA:0(-3.8/5.0):. Processed in 0.765713 secs); 21 Dec 2016 19:15:28 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-3.8 required=5.0 tests=RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.eastlink.ca designates 24.224.136.30 as permitted sender) X-Authority-Analysis: v=2.2 cv=HKaBLclv c=1 sm=1 tr=0 a=28Ntk8jg+Dho8ABWn/CRtA==:117 a=28Ntk8jg+Dho8ABWn/CRtA==:17 a=IkcTkHD0fZMA:10 a=4oWaqBRBj-rETPMFnNwA:9 a=QEXdDO2ut3YA:10 X-EL-IP-NOAUTH: 24.207.16.108 To: Zsh Users From: Ray Andrews Subject: 32 or 64 Message-id: Date: Wed, 21 Dec 2016 11:15:20 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 MIME-version: 1.0 Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit Gentlemen: Now that I have both 32 bit and 64 bit versions of various binaries, whereas I used to just store them in a /Bin directory which is on my path, now, if I'm jumping back and forth between 32 bit Debian and 64 bit Debian, whereas previously different installs could share the same /Bin directory (all being 32 bit previously) now I hafta be able to distinguish 32 from 64, so I'm thinking to symlink /Bin to either /Bin32 or /Bin64 and I'm wondering if there might be a simple way for zsh to make that link for me based on knowing if either itself, or the kernel is 32 or 64 bit. I could test the output of 'uname -r' of course, but I'd not be surprised if zsh can do it more elegantly and robustly than checking for substrings in the kernel name.