[RFC] kldunload -f argument.

[Pawel Jakub Dawidek]

On Fri, Jul 09, 2004 at 02:06:56PM +0200, Poul-Henning Kamp wrote:
+> In message <6595.1089317548 at 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!

Could we implement those new flags as a flags, i.e:

#define	LINKER_UNLOAD_FORCE	0x01
(only this)

So we don't have to create another syscall when we want to add something
in the future.

-- 
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd at FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20040709/bd4e2d9c/attachment.bin