**** BEGIN LOGGING AT Tue Aug 23 02:59:56 2022 Aug 23 08:57:57 good morning all. Aug 23 08:59:20 Yesterday got some funny situation with Popen. Aug 23 08:59:20 > import subprocess; subprocess.call(('echo', 'foo'), cwd="./mypath", stdout=subprocess.STDOUT, stderr=subprocess.STDOUT) Aug 23 08:59:20 Leads to OSError: [Errno 9] Bad file descriptor: './mypath' Aug 23 08:59:54 sharing with you as it was not obvious for me at all Aug 23 11:53:20 ptsneves, but is it obvious now? Aug 23 12:01:29 Well this is something you cannot do. The point is you cannot have stdout=STDOUT Aug 23 12:01:43 instead if you want stdout enabled you need to set it to None. Otherwise you get that message Aug 23 12:02:44 i wondered if this was straightforward for you, because guys at #python told me it kind of is. Aug 23 12:02:50 and that it is in the docs Aug 23 12:07:52 ahh, so the errno is not about ./mypath at all Aug 23 12:07:56 strace showed me dup2() failing, which makes sense Aug 23 13:00:42 yes! Aug 23 13:00:51 the mypath is an artifact Aug 23 13:01:21 and if cwd is None you will just get Bad file descriptor. Which seems to me very obscure just the same Aug 23 16:00:00 Hi Aug 23 16:00:00 is there any way to execute command using '${@' expression Aug 23 16:00:01 ${@os.system(command)} doesn't seem to work Aug 23 16:35:36 DvorkinDmitry: Well, if you are building an image that only you will use, then there are no problems with creating an SSH key at build time. However, if you are building an image that will be deployed to many different products, then you do not want them all to use the same SSH key. Aug 23 16:37:15 Saur[m], but it requires the password to authenticate anyway.... Aug 23 16:42:45 JaMa: Hey, quick question for whenever you're around, we're wondering if there's a better way to switch to an eglfs-based environment, removing all weston/x11 stuff in one go. DISTRO_FEATURES+PACKAGECONFIG? It'd be nice for a user to have an easy way to switch Aug 23 16:44:15 DvorkinDmitry: I thought you were referring to the server key, but now it sounds more like you are talking about the public key used when accessing the product. You can of course install your public key to `${ROOT_HOME}/.ssh/authorized_keys` and as long as you have registered your key with ssh-add, you can then access the product without having to login (just like any other server where you have authorized your public key). Aug 23 16:53:41 Saur[m], I am talking about the generation of the /etc/ssh/ssh_host* files that is automatically running on very first ssh login Aug 23 17:06:31 DvorkinDmitry: Here is the code we use in our extension to rootfs-postprocess.bbclass to add an SSH server key for developers: https://pastebin.com/awqcGYYB Aug 23 17:07:22 In our environment, OE_USER_DIR is set to `~/.openembedded`, but you can of course use whatever path you want. Aug 23 17:15:54 Saur[m], thank you! is it safe enougth to use pre-generated files and force password auth? Aug 23 17:45:39 DvorkinDmitry: Well, we only use this for developers that build their own images and there it should be fine. It is definitely not suitable for production. Aug 23 21:40:50 Saur[m], yea. thank you **** BEGIN LOGGING AT Wed Aug 24 01:00:24 2022 **** ENDING LOGGING AT Wed Aug 24 02:59:57 2022