zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: 32 or 64
Date: Wed, 21 Dec 2016 12:24:20 -0800	[thread overview]
Message-ID: <eafb9387-82cd-329e-38e8-f1c4afb6de61@eastlink.ca> (raw)
In-Reply-To: <20161221193321.GA24231@fujitsu.shahaf.local2>

On 21/12/16 11:33 AM, Daniel Shahaf wrote:
> Ray Andrews wrote on Wed, Dec 21, 2016 at 11:15:20 -0800:
>
> 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 just for my personal binaries, not the system /bins.  I suppose 
the expected thing would be to have that stuff in /usr/local/bin but I 
like to keep all my personally made stuff in one partition separate from 
stuff made by the OS or by installing things officially, that way I just 
mount my partition on to the FS of any OS and I've got all my stuff 
exactly perfect right away and I basically never touch  anything else 
except sometimes you hafta tinker with a few files in /etc. The only 
hitch has ever been the jump to 64 bit, which gives me a different set 
of my binaries and a different zsh.  Maybe I haven't figured out the 
best protocol for that.
>
> For future reference, there's `uname -m`.

That's best, because it won't change with any 64 bit kernel, I think.
>
> But again: I would recommend just giving each OS its own partition.
> That's a lot less likely to break.

Yup, I'm quite a partitioner, there's just the shared stuff to to with 
zsh and my few personal binaries.  Nice to unpack everything from one 
suitcase and be right at home.


  reply	other threads:[~2016-12-21 20:24 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
2016-12-21 20:24   ` Ray Andrews [this message]
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=eafb9387-82cd-329e-38e8-f1c4afb6de61@eastlink.ca \
    --to=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).