jaeger changed the topic of #crux to: CRUX 3.7 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
brian__ is now known as brian|lfs
joe9 has joined #crux
joe9 has quit [Ping timeout: 255 seconds]
groovy3shoes has joined #crux
groovy2shoes has quit [Read error: Connection reset by peer]
<cruxbot> [core.git/3.7]: exim: 4.96.1 -> 4.96.2
<cruxbot> [opt.git/3.7]: python3-pip: 23.2.1 -> 23.3
<cruxbot> [contrib.git/3.7]: pnpm: 8.9.0 -> 8.9.2
groovy2shoes has joined #crux
groovy3shoes has quit [Read error: Connection reset by peer]
lavaball has joined #crux
ppetrov^ has joined #crux
tarxvfz has joined #crux
tarxvfz has quit [Remote host closed the connection]
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
stoffepojken has joined #crux
tarxvfz has joined #crux
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
stoffepojken has joined #crux
tarxvfz has quit [Read error: Connection reset by peer]
tarxvfz has joined #crux
<farkuhar> According to doas(1) the resetting of environment variables is supposed to assign PATH a value "appropriate for the target user." Our /etc/profile defines PATH the same for both root and non-root users, but opendoas must have a different hard-coded default, because it doesn't regard /opt/bin as "appropriate for the target user" root.
<farkuhar> And thus the doas.conf manpage recommends specifying absolute paths when writing the rules, with the warning that when a relative path is specified, "only a restricted PATH will be searched."
<SiFuh> Yes, and it is recommened that you use strict exact paths for everything
<SiFuh> Doing executing /sbin/passwd ./passwd /some/location/passwd and passwd are completely differently according to doas
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
stoffepojken has joined #crux
<farkuhar> Speaking of paths, what is supposed to happen when you invoke a command within a login shell, move the binary to another location (still in $PATH), and then re-run the same command (not as an absolute path)? Under bash it appears that caching of the path results in "command not found" for the second invocation. But is this behaviour required by POSIX?
<SiFuh> Good question. I noticed that back in 2002 and never thought much of it since then.
chrcav has quit [Quit: leaving]
z3bra has quit [Remote host closed the connection]
<cruxbot> [opt.git/3.7]: tevent: update to 0.16.0
<cruxbot> [opt.git/3.7]: qpdf: update to 11.6.3
<cruxbot> [opt.git/3.7]: oniguruma: update to 6.9.9
<cruxbot> [opt.git/3.7]: conky: update to 1.19.6
ppetrov^ has quit [Quit: Leaving]
<cruxbot> [opt.git/3.7]: samba: update to 4.19.2
tarxvfz has quit [Ping timeout: 252 seconds]
tarxvfz has joined #crux
chrcav has joined #crux
tarxvfz has quit [Ping timeout: 252 seconds]
z3bra has joined #crux
<cruxbot> [contrib.git/3.7]: bandwhich: 0.21.0 -> 0.21.1
groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux
<cruxbot> [contrib.git/3.7]: dysk: 2.8.1 -> 2.8.2
brian__ has joined #crux
brian|lfs has quit [Ping timeout: 258 seconds]
<cruxbot> [contrib.git/3.7]: p5-image-exiftool: 12.67 -> 12.68
braewoods_ is now known as braewoods
lavaball has quit [Remote host closed the connection]
tilman has quit [Ping timeout: 255 seconds]
tilman has joined #crux
brian__ is now known as brian|lfs