Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20

[Jakov Simunic <jakov.simunic@ericsson.com>]

Hello,
Have tried to do a distclean then a new image build, still got the same errors for chmod and chown on udev files.
What I figured out is that this line gives the errors during the ptxdist images stage:

(awk -F: '{ if ($1 == "f") printf("chmod %s \".%s\"; chown %s.%s \".%s\";\n", $5, $2, $3, $4, $2); if ($1 == "n") printf("mkdir -p \".`dirname \"%s\"`\"; mknod -m %s \".%s\" %s %s %s; chown %s.%s \".%s\";\n", $2, $5, $2, $6, $7, $8, $3, $4, $2);}' /home/ezsimja/ptxdist/platform-xxx/images/permissions &&		\

Contents of /home/ezsimja/ptxdist/platform-xxx/images/permissions reffering to udev:

f:/sbin/udevd:0:0:0755
f:/sbin/udevadm:0:0:0755
f:/etc/udev/rules.d/01-basic.rules:0:0:0644
f:/etc/udev/rules.d/10-local.rules:0:0:0644
f:/etc/udev/rules.d/50-default.rules:0:0:0644
f:/etc/init.d/udev:0:0:0755
f:/etc/udev/udev.conf:0:0:0644
f:/lib/libudev.so.0.13.1:0:0:0644

Check to see if files are really where they should be:

ls ptxdist/platform-xxx/root/sbin/
adjtimex  hwclock   ip        klogd             pam_tally2           start-stop-daemon  udevd
arp       ifconfig  ipaddr    logread           pam_timestamp_check  swapoff            udhcpc
depmod    ifdown    iplink    mkdosfs           pivot_root           swapon             unix_chkpwd
devmem    ifup      ipneigh   mke2fs            poweroff             switch_root        unix_update
dhcpd     init      iproute   mkhomedir_helper  reboot               sysctl
getty     inotifyd  iprule    modprobe          rmmod                syslogd
halt      insmod    iptunnel  pam_tally         route                udevadm

ls ptxdist/platform-xxx/root/etc/udev/rules.d/
01-basic.rules  10-local.rules  50-default.rules

ls platform-esc0201/root/etc/init.d/
crond    lmd        mountconf   ntp      rcK  sysklogd  usbmem
hwclock  logrotate  networking  openssh  rcS  udev

ls platform-esc0201/root/etc/udev/
rules.d  udev.conf

ls platform-esc0201/root/lib/
init                 libm.so.6              libpamc.so             libresolv.so.2
ld-2.25.so           libncurses.so          libpamc.so.0           librt-2.25.so
ld-linux-armhf.so.3  libncurses.so.5        libpamc.so.0.82.1      librt.so.1
libc-2.25.so         libncurses.so.5.6      libpam_misc.so         libthread_db-1.0.so
libcrypt-2.25.so     libnsl-2.25.so         libpam_misc.so.0       libthread_db.so.1
libcrypt.so.1        libnsl.so.1            libpam_misc.so.0.82.1  libudev.so
libc.so.6            libnss_compat-2.25.so  libpam.so              libudev.so.0
libdl-2.25.so        libnss_compat.so.2     libpam.so.0            libudev.so.0.13.1
libdl.so.2           libnss_dns-2.25.so     libpam.so.0.84.2       libutil-2.25.so
libgcc_s.so          libnss_dns.so.2        libpthread-2.25.so     libutil.so.1
libgcc_s.so.1        libnss_files-2.25.so   libpthread.so.0        modules
libm-2.25.so         libnss_files.so.2      libresolv-2.25.so      security

It seems to me that all files are accounted for.
When does /home/ezsimja/ptxdist/platform-xxx/images/permissions get generated and what role does it have?
Thought that install_copy and friends handled ownership and permissions.
Any advice is welcome.

--
Lijep pozdrav / Best regards
Jakov Šimunić

-----Original Message-----
From: ptxdist <ptxdist-bounces@pengutronix.de> On Behalf Of Michael Olbrich
Sent: Wednesday, June 13, 2018 5:07 PM
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20

On Wed, Jun 13, 2018 at 02:57:57PM +0000, Jakov Simunic wrote:
> 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

I'm not sure about ptxdist 1.99.20, but in may version, this can happen after updating packages and is usually fixed by a clean rebuilt of the whole BSP.

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
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de