From: Peter Korsgaard <peter@korsgaard.com>
To: Zvi Vered <veredz72@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] 2023.02 : pty_allocate: openpty: No such file or directory
Date: Mon, 20 Mar 2023 09:51:01 +0100 [thread overview]
Message-ID: <875yavx0ui.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABRndgw1EVFyDNDcRJ10gOPFfw-gH+7Gqx7P537EiSVr5Wq6Kw@mail.gmail.com> (Zvi Vered's message of "Fri, 17 Mar 2023 06:57:16 +0200")
>>>>> "Zvi" == Zvi Vered <veredz72@gmail.com> writes:
> Hello,
> I built rootfs for aarch64 (little endian) and used it to boot cortex A-53
> with kernel 4.9.x
> After login (+password) I ran dropbear (included in buildroot) with:
> dropbear -F -R -E
> and got no errors.
> Upon trying to connect via SSH from ssh client I got:
> pty_allocate: openpty: No such file or directory
> No pty was allocated, couldn't execute
> Exit (root) from <10.0.0.1:51333>: Error reading Connection reset by peer
> Can you please advise what can be done?
Can you provide some more details, please? Dropbear installs an
initscript so it should normally start up automatically.
The openpty issue sounds like your kernel perhaps doesn't have pty
support. Did you enable CONFIG_UNIX98_PTYS / CONFIG_LEGACY_PTYS in the
kernel configuration?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next parent reply other threads:[~2023-03-20 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABRndgw1EVFyDNDcRJ10gOPFfw-gH+7Gqx7P537EiSVr5Wq6Kw@mail.gmail.com>
2023-03-20 8:51 ` Peter Korsgaard [this message]
[not found] ` <CABRndgyqeJXm6XqwYQ_QUaQAGB9EENSq4dc3qLaq6Y3RUhxFUg@mail.gmail.com>
2023-03-21 18:49 ` [Buildroot] 2023.02 : pty_allocate: openpty: No such file or directory Peter Korsgaard
[not found] ` <CABRndgwMRVDXzSAoGb5fU9PqM2b6z6we5rH40_NCs7w12LHiDA@mail.gmail.com>
2023-03-21 19:28 ` Peter Korsgaard
[not found] ` <CABRndgz8n37jikSwt3uBkGTM-UBObYcny6xEqhnFkDod9dae1Q@mail.gmail.com>
2023-03-22 21:59 ` Peter Korsgaard
[not found] ` <CABRndgycL0_hvf5dizJDby8VeW_z4xSnTZkXUOsVsXwy==yheA@mail.gmail.com>
2023-03-23 6:56 ` Peter Korsgaard
[not found] ` <CABRndgzV8hKy1pyRCNm+sgi_ePoHgYrS5h_4ca2bZd3E006nPQ@mail.gmail.com>
2023-03-24 6:36 ` Peter Korsgaard
[not found] ` <CABRndgz5EeQhEkqHG0R=T0AvQnzOLHbabO+MjkYH9UHK53pL8g@mail.gmail.com>
[not found] ` <CABRndgwHc_rpSxXqMdMmGb+3yDy5FSAjk=UDqeA0CvRS13=oiQ@mail.gmail.com>
2023-03-25 10:37 ` Peter Korsgaard
[not found] ` <CABRndgyK0f71HMi15+r8k0nu51sHQrRDx=OA7e5BWR6Oudhnbg@mail.gmail.com>
2023-03-27 19:12 ` Peter Korsgaard
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=875yavx0ui.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=veredz72@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.