All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 22 Mar 2023 22:59:27 +0100	[thread overview]
Message-ID: <87355wv45c.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CABRndgz8n37jikSwt3uBkGTM-UBObYcny6xEqhnFkDod9dae1Q@mail.gmail.com> (Zvi Vered's message of "Wed, 22 Mar 2023 20:03:35 +0200")

>>>>> "Zvi" == Zvi Vered <veredz72@gmail.com> writes:

 > Hi Peter,
 > The output of: ls -la /dev/null :
 > -rw-rw----    1 root           root       256 Dec 23   13:07 /dev/null

So /dev/null is a regular file, not a character device?

 > In S60rcma (my script, in /etc/init.d)  I added:
 > mdev -s
 > dropbear -R -E

 > After login, ssh client works fine.
 > It seems adding "mdev" solved the problem.
 > I think buildroot rootfs should solve it without adding any script.

It does. Again, please provide more details - E.G. how does your
Buildroot .config look like and how do you get the rootfs onto your
target?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-03-22 21:59 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 ` [Buildroot] 2023.02 : pty_allocate: openpty: No such file or directory Peter Korsgaard
     [not found]   ` <CABRndgyqeJXm6XqwYQ_QUaQAGB9EENSq4dc3qLaq6Y3RUhxFUg@mail.gmail.com>
2023-03-21 18:49     ` 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 [this message]
     [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=87355wv45c.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.