On Mon 2 Apr 2018 at 14:36:00 -0400, Tom H wrote:
> You have "dev/tty". It should be "/dev/tty".
Thank you for catching that typo, I lost the slash somewhere between
the first and second syntax. In my case it was harmless, because I
chrooted into a filesystem root, such that dev/tty ==
On Sun, Apr 1, 2018 at 10:54 PM, wrote:
> On 03/30/2018 11:10 AM, Bas Zoutendijk wrote:
>> On Fri 30 Mar 2018 at 10:33:45 -0600, the...@sys-concept.com wrote:
>>>
>>> I'm using a scrip to log-in/boot strap the system over NFS
>>>
>>> -
>>> #!/bin/sh
>>>
>>>
On 04/02/2018 03:29 AM, Bas Zoutendijk wrote:
> On Mon 2 Apr 2018 at 10:25:45 +0200, David Haller wrote:
>> You owe me a dollar!
>>
>> export PS1="$(chroot '$HOST') $PS1";
>> ^
>
> The text within the parentheses was meant as literal text, the chroot
> command is executed
On Mon 2 Apr 2018 at 10:25:45 +0200, David Haller wrote:
> You owe me a dollar!
>
> export PS1="$(chroot '$HOST') $PS1";
> ^
The text within the parentheses was meant as literal text, the chroot
command is executed rightward of the pipe. I could just as well write
Hello,
On Sun, 01 Apr 2018, the...@sys-concept.com wrote:
>On 03/30/2018 11:10 AM, Bas Zoutendijk wrote:
[..]
>> echo 'export PS1="(chroot '$HOST') $PS1"; exec > $ROOT /bin/bash -i
>The above syntax produced an error:
>
>chroot-eden: line 30: syntax error near unexpected token `('
On Sun 1 Apr 2018 at 20:54:13 -0600, the...@sys-concept.com wrote:
> The above syntax produced an error:
>
> chroot-eden: line 30: syntax error near unexpected token `('
> chroot-eden: line 30: `echo 'export PS1="(chroot '$HOST') $PS1"; exec
>
> I've tried it without brackets "()" no effect.
On 03/30/2018 11:10 AM, Bas Zoutendijk wrote:
> On Fri 30 Mar 2018 at 10:33:45 -0600, the...@sys-concept.com wrote:
>> I'm using a scrip to log-in/boot strap the system over NFS
>>
>> -
>> #!/bin/sh
>>
>> HOST=${0##*/}
>> HOST=${HOST#*-}
>> ROOT=/mnt/${HOST}
>> ...
>> exec chroot '${ROOT}'
On 03/30/2018 11:10 AM, Bas Zoutendijk wrote:
> On Fri 30 Mar 2018 at 10:33:45 -0600, the...@sys-concept.com wrote:
>> I'm using a scrip to log-in/boot strap the system over NFS
>>
>> -
>> #!/bin/sh
>>
>> HOST=${0##*/}
>> HOST=${HOST#*-}
>> ROOT=/mnt/${HOST}
>> ...
>> exec chroot '${ROOT}'
On Fri 30 Mar 2018 at 10:33:45 -0600, the...@sys-concept.com wrote:
> I'm using a scrip to log-in/boot strap the system over NFS
>
> -
> #!/bin/sh
>
> HOST=${0##*/}
> HOST=${HOST#*-}
> ROOT=/mnt/${HOST}
> ...
> exec chroot '${ROOT}' /bin/bash -l
> ---
>
> When I'm presented with bash
I'm using a scrip to log-in/boot strap the system over NFS
-
#!/bin/sh
HOST=${0##*/}
HOST=${HOST#*-}
ROOT=/mnt/${HOST}
...
exec chroot '${ROOT}' /bin/bash -l
---
When I'm presented with bash prompt, it is the same as the one I logged
IN from. So to eliminate the confusion I would like to
10 matches
Mail list logo