On Fri, Feb 10, 2017 at 03:28:53AM -0800, m...@lamarciana.com wrote:
> > The issue you raise there arises because the xterm is not a login shell
> > so will not use .profile.
> > It is interactive so (using bash) will use .bashrc
> >
> > On the immediate question here you can always set the path explicitly:
> > qvm-run -p qube "export PATH=$PATH:<NEWPATH> && foo"
>
> Hey Unman. The issue is that neither `~/.bashrc` nor `/etc/bash.bashrc` from
> my VM are used when I do `qvm-run` from dom0. Your workaround works but I
> think it is quite cumbersome. I wonder if there is any way to change the VM
> PATH seen from dom0 for every command.
>
> Thanks
>
Yes, I know - that's why I said "using bash".
You are using zsh, so you said, so you need to put the path in ~/.zprofile
For example, with simple script 'logit' in home/user/newpath:
qvm-run -a -p qube logit
fails with "logit: not found"
append path=('home/user/newpath' $path) to ~/.zprofile
Then qvm-run succeeds
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20170211004810.GA9930%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.
