09:46 <Guest9551> hello

09:47 <Guest9551> sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

09:48 <Guest9551> help me to solve this problem

09:55 <Guest9935> sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

09:55 <Guest9935> help me to solve this problem

09:55 <Guest9935> sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

09:55 <Guest9935> help me to solve this problem

09:56 <Guest9935> hello

09:56 <Guest9935> anyone is here?

10:01 <jduchniewicz> Try reflashing the image (if you havent done it already)

10:02 <Guest9935> yes tried

10:02 <Guest9935> yes i tried

10:04 <Guest9935> same problem is coming when i reflashing image

10:09 <jduchniewicz> Another image?

10:09 <jduchniewicz> Or broken flash if it is not the image

10:10 <Guest9935> could you send me link of old and best image

10:10 <Guest9935> i am using latest image

10:14 <zmatt> Guest9935: let me get this straight, you are claiming that immediately after flashing the latest image, without doing anything else on it, sudo is broken on your system? even though this only affects you and sudo works fine for everyone else

10:14 <zmatt> what does ls -l /usr/bin/sudo show?

10:14 <Guest9935> yes

10:14 <Guest9935> okk

10:15 <Guest9935> -rwxr-xr-x 1 root root 110700 Aug 13 2021 /usr/bin/sudo

10:17 <zmatt> it's showing a modification date of today

10:17 <zmatt> implying you've done something that modified it

10:18 <Guest9935> so what i have to do for working fine sudo in BBB

10:18 <zmatt> (on a newly flashed system it would have a modification date of february 2nd 2020

10:18 <Guest9935> ok

10:19 <zmatt> you've clearly done something to the system *after* flashing that broke it

10:19 <zmatt> wait, how exactly did you reflash the beaglebone? can you describe the steps you performed?

10:20 <Guest9935> ok

10:20 <Guest9935> 1st i created two partiions of my sd card

10:20 <Guest9935> one is BOOT and another is ROOTFS

10:20 <zmatt> stop. why are you doing this?

10:21 <Guest9935> i want start booting process from sd card not form emmc'

10:21 <Guest9935> so thats why i have done this things

10:22 <zmatt> this is also not an appropriate step for creating a bootable sd card, and you said many times you were reflashing the beaglebone while now you're saying you're booting from sd card

10:22 <Guest9935> in BOOT partition i pasted uImage uBoot.img MLO .dtb and uENV.txt

10:22 <zmatt> you also claimed you were using the latest image

10:22 <Guest9935> yes

10:22 <zmatt> which is ready to go and does not involve any of these steps

10:22 <zmatt> you just flash the image to sd card, done

10:22 <Guest9935> ok i mounted .img file

10:23 <zmatt> and then proceeded to create a broken system

10:23 <Guest9935> so what i have to do?

10:23 <zmatt> none of this is needed. just flash the image file directly to sd card

10:23 <Guest9935> how? through beleana etcher?

10:23 <zmatt> that is recommended yes

10:24 <Guest9935> then how i can start booting process for SD card

10:24 <zmatt> also, reflashing the beaglebone and booting from eMMC is recommended over booting from SD card (eMMC is faster), but if for whatever reason you really insist of booting from sd card instead of using eMMC then it is highly recommended to wipe eMMC (using "sudo blkdiscard /dev/mmcblk1") after booting from SD card

10:25 <zmatt> normally you just insert the SD card and power the beaglebone, it will boot from SD card automatically

10:25 <Guest9935> okk

10:25 <Guest9935> what if want change device tree and i have to change .dtb file then how i uplode this file boot partition of eMMC

10:26 <Guest9935> i want to

10:26 <zmatt> why are you talking about eMMC again? you just said you wanted to boot from sd card

10:26 <zmatt> also, boot partitions haven't been used for many many years, the dtb is loaded directly from the rootfs

10:26 <Guest9935> ok

10:27 <zmatt> (using a custom dtb is generally not recommended unless you really know what you're doing, which you clearly don't)

10:27 <Guest9935> okk thamk you so much

10:27 <zmatt> using either runtime pin configuration (with config-pin) or a device tree overlay is perfectly adequate for most users

10:27 <Guest9935> yess

10:28 <Guest9935> thank you so much

10:28 <zmatt> and for future reference: simplying copying the files of a linux rootfs will break the system unless you take special case to preserve all metadata, including permissions, ACLs, and extended attributes

10:28 <zmatt> *special care

10:29 <Guest9935> okk

10:29 <Guest9935> thanks for helping me

10:29 <Guest9935> i will try

18:52 <zmatt> just when you'd think the whole freenode thing can't get weirder or sadder.... https://freenode.org/news/on-power-to-the-people

18:52 <zmatt> "Officially become digital territory of the Joseon Empire"

18:54 <zmatt> chat.freenode.net is now an alias for irc.joseon.kr

19:09 <mru> wtf

19:35 <buzzmarshall> oh boy... more ra ra were the greatest nation crap... another irc network bytes the dust