Date: Fri, 09 Jul 2004 14:06:56 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: arch@freebsd.org Subject: Re: [RFC] kldunload -f argument. Message-ID: <21507.1089374816@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 08 Jul 2004 22:12:28 %2B0200." <6595.1089317548@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <6595.1089317548@critter.freebsd.dk>, Poul-Henning Kamp writes: > >In an ideal situation, unmount(8) will fail to unload if the >filesystem is in use but the administrator has the option of applying >the -f(orce) option which tells the kernel: "umount at any cost" [3]. > > >We do not have the same flexibility with kldunload(8), and this is >leading to a minor spot of trouble for modules which autoattach to >things, like for instance GEOM classes where it can be very hard if >not impossible to get the module idle from userland so it can be >unloaded. Here is a patch which does this: http://phk.freebsd.dk/patch/kldunload.patch Tests, comments etc welcome! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21507.1089374816>