From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: 32 or 64
Date: Wed, 21 Dec 2016 19:33:21 +0000 [thread overview]
Message-ID: <20161221193321.GA24231@fujitsu.shahaf.local2> (raw)
In-Reply-To: <ddc5b344-1489-f23b-c46a-5e17949bf54c__41077.1772302271$1482347804$gmane$org@eastlink.ca>
Ray Andrews wrote on Wed, Dec 21, 2016 at 11:15:20 -0800:
> 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)
Don't share the /bin directory between OS installs. Doing so is liable
to leave one of the two OSes unbootable at some point.
That's assuming /bin is on the / partition. if /bin is a symlink to
/usr/bin [as seems to be fashionable nowadays] and /usr is its own
partition, then sharing that partition can be made to work, with some
care. But I don't think that's what you have.
> 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.
For future reference, there's `uname -m`.
But again: I would recommend just giving each OS its own partition.
That's a lot less likely to break.
Cheers,
Daniel
next parent reply other threads:[~2016-12-21 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ddc5b344-1489-f23b-c46a-5e17949bf54c__41077.1772302271$1482347804$gmane$org@eastlink.ca>
2016-12-21 19:33 ` Daniel Shahaf [this message]
2016-12-21 20:24 ` Ray Andrews
2016-12-21 19:15 Ray Andrews
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161221193321.GA24231@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).