* [ptxdist] Backporting udev-182 to ptxdist 1.99.20 @ 2018-06-13 14:57 Jakov Simunic 2018-06-13 15:06 ` Michael Olbrich 0 siblings, 1 reply; 4+ messages in thread From: Jakov Simunic @ 2018-06-13 14:57 UTC (permalink / raw) To: ptxdist [-- 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20 2018-06-13 14:57 [ptxdist] Backporting udev-182 to ptxdist 1.99.20 Jakov Simunic @ 2018-06-13 15:06 ` Michael Olbrich 2018-06-14 11:37 ` Jakov Simunic 0 siblings, 1 reply; 4+ messages in thread From: Michael Olbrich @ 2018-06-13 15:06 UTC (permalink / raw) To: ptxdist 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20 2018-06-13 15:06 ` Michael Olbrich @ 2018-06-14 11:37 ` Jakov Simunic 2018-06-28 12:25 ` Jakov Simunic 0 siblings, 1 reply; 4+ messages in thread From: Jakov Simunic @ 2018-06-14 11:37 UTC (permalink / raw) To: ptxdist 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20 2018-06-14 11:37 ` Jakov Simunic @ 2018-06-28 12:25 ` Jakov Simunic 0 siblings, 0 replies; 4+ messages in thread From: Jakov Simunic @ 2018-06-28 12:25 UTC (permalink / raw) To: ptxdist Hello, I have managed to resolve these errors when I removed the redirection in rules/post/images.make when at line 102 where the following is done: @DESTDIR=$(WORKDIR) $(FAKEROOT) -- $(PTXCONF_SYSROOT_HOST)/bin/ipkg-cl -f $(IMAGEDIR)/ipkg.conf -o $(WORKDIR) install $(IPKG_FILES) 2>&1 >/dev/null And it showed me that my util-linux wasn't being installed properly, and I fixed that. After that it built fine, but the image failed to boot on the device saying that: starting udevd... error binding udev control socket [FAILED] After a lot of searching I found that the runtime data of udev moved from /dev/.udev/ to /run/udev/ which I didn't have in my rootfs. Figured how to make that directory with the right type of the filesystem, edited the fstab also, now udev starts without errors on the target, but it still won't boot. Now it says the following: U-Boot 2015.10 (Apr 12 2017 - 14:48:14 +0200) CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz) CPU: Industrial temperature grade (-40C to 105C) at 42C Reset cause: POR Board: i.MX6UL Teton/P7618 I2C: ready DRAM: 512 MiB NAND: 128 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 In: serial Out: serial Err: serial Net: No ethernet found. UBI: attaching mtd1 to ubi0 UBI: scanning is finished UBI: attached mtd1 (name "mtd=2", size 123 MiB) to ubi0 UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 UBI: good PEBs: 988, bad PEBs: 0, corrupted PEBs: 0 UBI: user volume: 13, internal volumes: 1, max. volumes count: 128 UBI: max/mean erase counter: 194/122, WL threshold: 4096, image sequence number: 1101414808 UBI: available PEBs: 0, total reserved PEBs: 988, PEBs reserved for bad PEB handling: 20 flags1: tbr 0, tbp 0, act 0, seq 176 flags2: tbr 0, tbp 1, act 1, seq 179 Found a test boot image at flags2 bootargs: console=ttymxc0,115200 ubi.mtd=ESC ubi.block=0,root2 root=/dev/ubiblock0_11 rootfstype=squashfs ro quiet Starting kernel ... mounting filesystems... [DONE] mounting conf filesystem... [DONE] validating configuration data... validating configuration data... [DONE] starting udevd... [DONE] waiting for devices... [DONE] starting syslogd... [DONE] starting klogd... [DONE] starting crond... [DONE] hwclock: can't open '/dev/misc/rtc': No such file or directory starting sshd... [FAILED] run-parts: /etc/rc.d/S16openssh: exit status 1 And the old image with older udev-175 says this (it boots normally): U-Boot 2015.10 (Apr 12 2017 - 14:48:14 +0200) CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz) CPU: Industrial temperature grade (-40C to 105C) at 41C Reset cause: POR Board: i.MX6UL Teton/P7618 I2C: ready DRAM: 512 MiB NAND: 128 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 In: serial Out: serial Err: serial Net: No ethernet found. UBI: attaching mtd1 to ubi0 UBI: scanning is finished UBI: attached mtd1 (name "mtd=2", size 123 MiB) to ubi0 UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 UBI: good PEBs: 988, bad PEBs: 0, corrupted PEBs: 0 UBI: user volume: 13, internal volumes: 1, max. volumes count: 128 UBI: max/mean erase counter: 194/122, WL threshold: 4096, image sequence number: 1101414808 UBI: available PEBs: 0, total reserved PEBs: 988, PEBs reserved for bad PEB handling: 20 flags1: tbr 0, tbp 0, act 0, seq 176 flags2: tbr 0, tbp 0, act 1, seq 178 Found an active image at flags1 bootargs: console=ttymxc0,115200 ubi.mtd=ESC ubi.block=0,root1 root=/dev/ubiblock0_7 rootfstype=squashfs ro quiet Starting kernel ... mounting filesystems... [DONE] starting udevd... [DONE] waiting for devices... [DONE] mounting conf filesystem... [DONE] validating configuration data... validating configuration data... [DONE] starting syslogd... [DONE] starting klogd... [DONE] starting crond... [DONE] starting sshd... [DONE] TARGET_DEVICE login: Any suggestions/advice on what could be broken and how to proceed with fixing? Should I try stracing sshd? Is the bootloader output fishy? -- Lijep pozdrav / Best regards Jakov Šimunić -----Original Message----- From: ptxdist <ptxdist-bounces@pengutronix.de> On Behalf Of Jakov Simunic Sent: Thursday, June 14, 2018 1:37 PM To: ptxdist@pengutronix.de Subject: Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20 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 _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-06-28 12:25 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-06-13 14:57 [ptxdist] Backporting udev-182 to ptxdist 1.99.20 Jakov Simunic 2018-06-13 15:06 ` Michael Olbrich 2018-06-14 11:37 ` Jakov Simunic 2018-06-28 12:25 ` Jakov Simunic
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox