IRC channel logs

<gnu_srs1>youpi: any reason hurd-amd64 is not present? https://buildd.debian.org/stats/graph-ports-week-big.png

<gnu_srs1>too low built percentage to be visible?

<youpi>the scale is set automatically

<youpi>but that can be a reason not to show it yet, to avoid squeezing the others, yes

<slex>hello guys, i'm looking some code in gnumach, i'd learn how to wrote a little block device driver in userspace. can you suggest me what i should look/do/study?

<slex>i want to totally avoid at the linux block driver, i did read in the past days

<slex>v

<slex>sorry i lost the connection, so i have to do again the question. I'm reading the linux_block.c driver but i want to write a simple block driver in user space for gnumach totally avoiding the usage of the linux driver code

<slex>Where should i start to llok?

<slex>look* and stufy?

<slex>study*

<solid_black>slex: hi

<solid_black>usespace drivers are for the Hurd, not for gnumach

<solid_black>gnumach is kernelspace

<solid_black>for general examples of (virtual) block devices, look for translators in trans/ in the Hurd source tree, e.g. trans/null.c

<solid_black>writing the actual driver, i.e. communicating with the hardware device, I cannot help you with, ask someone else

<slex>solid_black: ok, yes is what i want experimenting to. i want to communicate with the hardware from userspace. like a server that can "access" to the hardware from userpace, but i think that at some point the kernel must be called to effectively write to the disk?

<azert>slex: I think we have an userspace driver framework on the Hurd

<azert>uh fine he left

<azert>BTW it wasn’t clear at all what he wanted to achieve

IRC channel logs

2024-11-12.log