IRC channel logs

<Pellescours>I discovered a bug with the console display, I don’t know how to fix it yet. When you press some special character (non ascii ones) like é or è when you backspace the character don’t disapear from the screen. But the backspace is effective, the char is not here anymore

<Pellescours>it’s still displayed but not in the "command buffer" anymore

<youpi>such kind of issue also depend on the shell, inputrc configuration etc.

<youpi>in .inputrc I have:

<youpi>set convert-meta off

<youpi>set input-meta on

<youpi>set output-meta on

<Pellescours>I reproduce it on the login screen

<youpi>and then I can backspace over non-ascii

<youpi>login screen most probably doesn't have proper inputrc

<youpi>actually my linux box's login screen suffers from the same kind of issue

<youpi>anyway, really use these inputrc lines in a real user shell, it does work for me

<Pellescours>your right, thanks

<solid_black>damo22: ping

<solid_black>ok, I have the v2 of the gnumach kernel write exploit

<solid_black>it does work on i386 this time

<solid_black>but, I have not guessed the correct address to overwrite on darnassus, and seem to have panicked it instead :|

<Denis>hello all. would anybody like to host a Buildbot worker VM on Hurd to add to this infrastructure? https://www.tcpdump.org/ci.html

<Denis>I have tried one hosting company, but they use virtio, which Hurd does not support

<solid_black>ok

<solid_black>bugaevc@darnassus:~$ ./exhax

<solid_black>root@darnassus:~#

<gnu_srs>solid_black: Interesting. I assume you will supply patches to solve that leak?

<azert>Was curious about the device tree that solid_black mentioned a few days ago. It looks to me like a solution and a step in the direction of open firmwares

<azert>It’s an open format to describe an hardware platform such as it could be the ibm-pc

<azert> Found good infos here https://wiki.st.com/stm32mpu/wiki/Device_tree and here https://wiki.st.com/stm32mpu/wiki/Interrupt_overview

IRC channel logs

2024-03-06.log