mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jakov Simunic <jakov.simunic@ericsson.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Backporting udev-182 to ptxdist 1.99.20
Date: Wed, 13 Jun 2018 14:57:57 +0000	[thread overview]
Message-ID: <HE1PR0702MB3804D47FDBAF7FB8AEEB113C987E0@HE1PR0702MB3804.eurprd07.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1716 bytes --]

Hello,
After I managed to surpass all obstacles on my way to making udev-182 build on the ancient version of ptxdist 1.99.20, there is still some work to be done 😊
ptxdist go – does everything ok, but,
ptxdist images – chmod and chown complain about paths to udev files

chmod: cannot access `./sbin/udevd': No such file or directory
chown: cannot access `./sbin/udevd': No such file or directory
chmod: cannot access `./sbin/udevadm': No such file or directory
chown: cannot access `./sbin/udevadm': No such file or directory
chmod: cannot access `./etc/udev/rules.d/01-basic.rules': No such file or directory
chown: cannot access `./etc/udev/rules.d/01-basic.rules': No such file or directory
chmod: cannot access `./etc/udev/rules.d/10-local.rules': No such file or directory
chown: cannot access `./etc/udev/rules.d/10-local.rules': No such file or directory
chmod: cannot access `./etc/udev/rules.d/50-default.rules': No such file or directory
chown: cannot access `./etc/udev/rules.d/50-default.rules': No such file or directory
chmod: cannot access `./etc/init.d/udev': No such file or directory
chown: cannot access `./etc/init.d/udev': No such file or directory
chmod: cannot access `./etc/udev/udev.conf': No such file or directory
chown: cannot access `./etc/udev/udev.conf': No such file or directory
chmod: cannot access `./lib/libudev.so.0.13.1': No such file or directory
chown: cannot access `./lib/libudev.so.0.13.1': No such file or directory

What i don't understand is:
  How can i change these paths?
  Some paths seem ok, so I don't understand why chmod and chown are complaining, I suppose the path they are
--
Lijep pozdrav / Best regards
Jakov Šimunić


[-- Attachment #1.2: Type: text/html, Size: 4679 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2018-06-13 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 14:57 Jakov Simunic [this message]
2018-06-13 15:06 ` Michael Olbrich
2018-06-14 11:37   ` Jakov Simunic
2018-06-28 12:25     ` Jakov Simunic

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=HE1PR0702MB3804D47FDBAF7FB8AEEB113C987E0@HE1PR0702MB3804.eurprd07.prod.outlook.com \
    --to=jakov.simunic@ericsson.com \
    --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