mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Issue with install_node creating pipes
Date: Wed, 8 Mar 2017 11:07:49 +0100	[thread overview]
Message-ID: <20170308100749.5autsq6djovmy5ni@pengutronix.de> (raw)
In-Reply-To: <94D4A88F8AC34646A5288D11318F5D5B0D9E5F32@GDUKADH841.uk1.r-org.net>

Hi,

On Thu, Mar 02, 2017 at 08:25:48AM +0000, jon.bird@gd-ms.uk wrote:
> There seems to be an issue using install_node to create named pipes, previously (with 2012.12.1 release), this worked:
> 
> @$(call install_node, syslogparser, 121, 121, 0644, p, , ,/var/local/syslogparser0.fifo)
> 
> Now (with 2016.04 release), the creation of the final image fails:
> 
> ...
> Configuring nfsutils.
> mknod: `./var/local/syslogparser0.fifo': File exists
> make: *** [/home/jon/sdr/os_uplift1/platform-i586/state/image_working_dir] Error 1

I think ptxdist-2015.01.0-42-g15c165d69929 broke this. I'm suprised nobody
notices before. Can you try without this change? You can just copy the
script to the same location in your BSP and change it there.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-03-08 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  8:25 jon.bird
2017-03-08 10:07 ` Michael Olbrich [this message]
2017-03-09 14:20   ` jon.bird
     [not found]     ` <8013bd45-7b84-9429-83b6-db1413731d24@rohieb.name>
2017-03-14 14:16       ` jon.bird
2017-03-24 16:37         ` Michael Olbrich

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=20170308100749.5autsq6djovmy5ni@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox