<damo22>youpi: how do you know where to protect a thread with mutexes when making it multithreaded? <damo22>i mean in the context of a translator like rumpdisk <damo22>also, when you take the mutex, what is supposed to happen when it's already locked? EBUSY? <damo22>demo@zamhurd:~$ sudo grub-install /dev/wd0 <damo22>Installing for i386-pc platform. <damo22>grub-install: error: cannot find a GRUB drive for part:2:device:wd0. Check your device.map. <youpi>damo22: when you take a mutex, as long as it's busy the mutex_lock call blocks <youpi>you have to protect any shared data structure <youpi>between someone that adds something to it and someone that reads it <youpi>I'd need a backtrace etc. for the grub issue, I'm not getting this <damo22>do you use part:2:device:wd0 in your root= or do you use /dev/wd0s2 <youpi>but update-grub doesn't look at that <damo22>thats strange because i do too, but /etc/mtab says /dev/wd0s2 <youpi>it looks at the ext2fsb mount <damo22>it prints that in its error message <damo22>when you say you need a backtrace, it does not crash so where would you like the trace? <youpi>to see where it gets that info from <damo22>or do i go through the debian package <damo22>it tries 3 different ways to get the disk from the device <damo22>grub-install has no debug symbols <damo22>0x08121409 in grub_util_biosdisk_get_grub_dev () <damo22>#0 0x08121409 in grub_util_biosdisk_get_grub_dev () <damo22>#1 0x081210f2 in grub_util_get_grub_dev () <damo22>Thread 4 hit Breakpoint 2, 0x08121cb9 in grub_util_find_hurd_root_device () <damo22>#0 0x08121cb9 in grub_util_find_hurd_root_device () <damo22>#1 0x0812233e in grub_guess_root_devices () <youpi>did you install the -dbgsym packages? <damo22>not via that command but i searched the list and installed htme <youpi>I have found missing parsing for part: before device: <youpi>I have uploaded a fixed package to debian-ports <youpi>you should only need grub-common and grub2-common <damo22>grub-install: error: Storage information for `/dev/wd0s2' does not include type. <youpi>usually you'd install on /dev/wd0 not /dev/wd0s2 <damo22>demo@zamhurd:~$ sudo grub-install /dev/wd0 <damo22>Installing for i386-pc platform. <damo22>grub-install: error: Storage information for `/dev/wd0s2' does not include type. <youpi>I'm not getting this with a freshl yinstalled system <youpi>and grub-common grub2-common version +hurd.6 <youpi>I don't think that'll change anything <youpi>the diff between +hurd.5 and +hurd.6 is in the parsing, not grub.Cfg generation <damo22>i had the wrong settrans on /dev/wd0s2 <damo22>demo@zamhurd:~$ showtrans /dev/wd0s2 <damo22>/hurd/storeio -T typed part:2:device:@/dev/disk:/dev/wd0 <damo22>should have been /hurd/storeio -T typed part:2:device:@/dev/disk:wd0 <damo22>demo@zamhurd:~$ showtrans /dev/wd0s2 <damo22>/hurd/storeio -T typed part:2:device:@/dev/disk:wd0 <damo22>demo@zamhurd:~$ sudo grub-install /dev/wd0 <damo22>Installing for i386-pc platform. <damo22>Installation finished. No error reported. <damo22>how do you ensure that the mutex only applies per thread? do you have to make it a global? <damo22>i think my mutex patch might fix the refcount even though multithreading is not enabled yet <youpi>damo22: a mutex has to be global otherwise it's useless :) <youpi>yes, that'd fix the refcount as well <youpi>if anybody sees curiosa, tell that +hurd.6 should solving the issue <Jari-->hi all + Richard Stallman friends <Jari-->Personally I am building a CP/M Plus revision of 2022. ***Guest8046 is now known as roptat
<spk121>CP/M was my first OS. All I remember is that there was a command called 'pip' and a word processor called WordStar