Yes. That is exactly what I did. Too bad I deleted it yesterday o.0 I
need the practice anyway.
On Thu, Oct 22, 2015 at 3:53 AM, wrote:
> 22. Oct 2015 02:21 by craigcgar...@gmail.com:
>
> Thank you
>
> On Wed, Oct 21, 2015 at 8:12 PM, William Harrington
> wrote:
>
>> On Wed, 21 Oct 2015 19:
22. Oct 2015 02:21 by craigcgar...@gmail.com:
> Thank you
>
> On Wed, Oct 21, 2015 at 8:12 PM, William Harrington <>
> kb0...@berzerkula.org> > wrote:
>
>> On Wed, 21 Oct 2015 19:29:19 -0400
>> Craig Garner <>> craigcgar...@gmail.com>> > wrote:
>>
>> > I rebooted
>> > back in to my host, did the
Thank you
On Wed, Oct 21, 2015 at 8:12 PM, William Harrington
wrote:
> On Wed, 21 Oct 2015 19:29:19 -0400
> Craig Garner wrote:
>
> > I rebooted
> > back in to my host, did the chroot and tried to execute passwd. It would
> > automatically act like I hit enter until it failed.
>
> Passwd requi
On Wed, 21 Oct 2015 19:29:19 -0400
Craig Garner wrote:
> I rebooted
> back in to my host, did the chroot and tried to execute passwd. It would
> automatically act like I hit enter until it failed.
Passwd requires access to devices for input, otherwise you get the behaviour
described. mount $LF
When I finished building and booted, I could not log in. So, I rebooted
back in to my host, did the chroot and tried to execute passwd. It would
automatically act like I hit enter until it failed. I tried setting root
and another user. Thinking something was wrong with passwd, I went to
build t
