Re: [xenocara] xenodm.man fix

2023-02-16 Thread Klemens Nanni
16.02.2023 18:29, Mikhail пишет: > /etc/X11/xenodm/Xsession file has a check for x bit > > startup=$HOME/.xsession > [...] > if [ -s "$startup" ]; then > if [ -x "$startup" ]; then > "$startup" > else > /bin/sh "$startup" > fi > [...] This w

[xenocara] xenodm.man fix

2023-02-16 Thread Mikhail
/etc/X11/xenodm/Xsession file has a check for x bit startup=$HOME/.xsession [...] if [ -s "$startup" ]; then if [ -x "$startup" ]; then "$startup" else /bin/sh "$startup" fi [...] diff /var/git/xenocara commit - 1322100d794a22f2ed024540585b4

Re: llvm-strip vs ld.bfd (at least on i386): SIGABRT in sys_execve

2023-02-16 Thread Theo Buehler
On Wed, Feb 15, 2023 at 11:30:34AM -0800, Philip Guenther wrote: > llvm-strip is somehow ignoring the alignment requirements of the segments. > If you look at the "readelf -l" output instead: > > Good: > Program Headers: > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align >

if_detach(): move rtm_ifannounce(IFAN_DEPARTURE) outside netlock

2023-02-16 Thread Vitaliy Makkoveev
This is the mbuf(9) allocation and broadcast transmission for PF_ROUTE sockets, netlock is not required here. Make sense for systems with many short time living pseudo interfaces like tun(4) and pppx(4). The corresponding IFAN_ARRIVAL announce could be also done without netlock held, but I like t

Re: Push solock() down to sosetopt()

2023-02-16 Thread Vitaliy Makkoveev
On Thu, Feb 16, 2023 at 01:19:07PM +0300, Vitaliy Makkoveev wrote: > > Sorry for big non obvious diff. I need this refactoring to keep required > lock order between solock() and the standalone sblock(). > The standalone sblock() could be non obvious for this moment. I want to to this mostly beca

Re: Push solock() down to sosetopt()

2023-02-16 Thread Vitaliy Makkoveev
On Wed, Feb 15, 2023 at 08:08:42PM +0100, Alexander Bluhm wrote: > On Mon, Jan 30, 2023 at 05:03:30PM +0300, Vitaliy Makkoveev wrote: > > It makes sense to push solock() down to sosetopt() too. For a half cases > > (*pr_ctloutput)() is just null op, so there is no reason to call it. > > Also, a lot