Hi! On Fri, 2014-10-03 at 04:45:13 +0200, Guillem Jover wrote: > After checking the s-s-d and libkvm code again now, it seems it does > not require any kvm_read(3) at all, so /dev/mem should not be needed > either, could you try the attached patch on a jail? (I need to recover > my damaged GNU/kFreeBSD system, as now I only have access to porter > boxes. :/ )
I just reinstalled my GNU/kFreeBSD system and I tested it outside a jail, and ktrace tells me it does not access /dev/mem anymore. I've also fixed an issue when kvm_getprocs(3) does not find any pid, which might have also been involved in the errors you where seeing. > On Thu, 2014-10-02 at 22:03:37 +0100, Steven Chamberlain wrote: > > No problem. Does that mean you'd happily revert to using linprocfs? > > If there's no better option, yes. Right now I'm thinking to merge > the attached patch for 1.17.14 as a hotfix, and then switch to a pure > sysctl(2) implementation for 1.17.15, so that we can get rid of the > libkvm dependency. Otherwise revert to linprocfs. Does that sound good? Something else I just realized now is that libkvm pulls in libbsd and libfreebsd-glue into the pseudo-essential set on GNU/kFreeBSD, which makes the situation a bit worse. So as stated above I'll be switching to sysctl(2) later on, but I'm open to a revert if this is deemed problematic too. Thanks for input Steven! Regards, Guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141004215925.ga18...@gaara.hadrons.org
