On 17-08-31 14:43:10, Rick Stevens wrote:
On 08/31/2017 11:14 AM, Tony Nelson wrote:
> On 17-08-31 12:41:09, Mike Wright wrote:
>
>> How about using "env": env PATH="new_path" chroot /some_dir
>>
>> Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
>> files? If so, chroot coul
On 17-08-31 11:34:21, Kevin Cummings wrote:
On 08/30/17 15:16, Tony Nelson wrote:
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be a link to /usr/bin. is /usr/bin in
the
P
On 08/31/2017 11:14 AM, Tony Nelson wrote:
> On 17-08-31 12:41:09, Mike Wright wrote:
>
>> How about using "env": env PATH="new_path" chroot /some_dir
>>
>> Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
>> files? If so, chroot could be defined as an alias to "env ... chroot
On 17-08-31 12:41:09, Mike Wright wrote:
How about using "env": env PATH="new_path" chroot /some_dir
Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
files? If so, chroot could be defined as an alias to "env ...
chroot" and thereby eliminate the problem.
Seems to work
On 17-08-31 12:18:38, Tom H wrote:
On Wed, Aug 30, 2017 at 3:16 PM, Tony Nelson
wrote:
>
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
> this could happen; I would think that PATH is set inside the chroot
>
On 08/31/2017 09:41 AM, Mike Wright wrote:
> On 08/31/2017 09:26 AM, Rick Stevens wrote:
>> On 08/31/2017 08:34 AM, Kevin Cummings wrote:
>>> On 08/30/17 15:16, Tony Nelson wrote:
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not.
On 08/31/2017 09:26 AM, Rick Stevens wrote:
On 08/31/2017 08:34 AM, Kevin Cummings wrote:
On 08/30/17 15:16, Tony Nelson wrote:
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be
On 08/31/2017 08:34 AM, Kevin Cummings wrote:
> On 08/30/17 15:16, Tony Nelson wrote:
>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>> included /bin, but now on f26 it does not. I don't understand how
>
> For a while now, /bin should be a link to /usr/bin. is /usr/bin in
On Thu, Aug 31, 2017 at 11:34 AM, Kevin Cummings
wrote:
> On 08/30/17 15:16, Tony Nelson wrote:
>>
>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>> included /bin, but now on f26 it does not. I don't understand how
>
> For a while now, /bin should be a link to /usr/bin. is /u
On Wed, Aug 30, 2017 at 3:16 PM, Tony Nelson
wrote:
>
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
> this could happen; I would think that PATH is set inside the chroot
> by the shell. How does PATH get set?
On 08/30/17 15:16, Tony Nelson wrote:
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be a link to /usr/bin. is /usr/bin in the
PATH?
> this could happen; I would think that PAT
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not. I don't understand how
this could happen; I would think that PATH is set inside the chroot
by the shell. How does PATH get set? I see how it is modified and
have fixed my issue, provide
12 matches
Mail list logo
