Date: Thu, 11 Jun 1998 22:08:30 +0200 From: Stefan Eggers <seggers@semyam.dinoco.de> To: freebsd-bugs@FreeBSD.ORG Cc: seggers@semyam.dinoco.de Subject: Re: bin/854: swapinfo shows incorrect information for vnconfig'd swap. Message-ID: <199806112008.WAA04698@semyam.dinoco.de> In-Reply-To: My message of "Thu, 11 Jun 1998 21:05:52 %2B0200." <199806111905.VAA02085@semyam.dinoco.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> What I didn't find out, yet is who creates /var/run/dev.db. I did no > extensive research, though. Just a few man's and grep's in places I > thought to be promising. Maybe someone else knows. Now I know its dev_mkdb(8) which creates this database. The man page says it's in since 4.4BSD - at least FreeBSD 2.2-stable from a few days ago (the configuration I used for testing) had it. ;-) The fix for the problem is adding a call to dev_mkdb after new nodes were created by MAKEDEV(8) - that way the device name data- base in /var/run/dev.db is as consistent with the existing devices as it can be with this duplication. Sorry, no diff. I just had the idea and now put it into a reply to the PR. The perfect solution would always keep both in sync. Something like DEVFS with a way to ask it for a name for a given device/unit pair. Maybe /dev/devname.db which gets generated and update by the DEVFS itself. The downside of this is the added complexity due to the database code which has to be in the kernel (or is a userland DEVFS possible?) then. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806112008.WAA04698>