Re: kern/48018 (modunload gets confused with unloading buildin modules)

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

On Aug 29,  6:35am, Reinoud Zandijk wrote:
}
} The following reply was made to PR kern/48018; it has been noted by GNATS.
} 
} From: Reinoud Zandijk <reinoud%NetBSD.org@localhost>
} To: Sergio Lopez <slp%sinrega.org@localhost>
} Cc: gnats-bugs%NetBSD.org@localhost
} Subject: Re: kern/48018 (modunload gets confused with unloading buildin 
modules)
} Date: Thu, 29 Aug 2013 08:31:57 +0200
} 
}  On Wed, Aug 28, 2013 at 09:29:12PM +0000, Sergio Lopez wrote:
}  > That's the expected behavior. Running modunload on a builtin module
}  > just disables it. From modstat(8):
}  > 
}  >  REFS  Number of references held on the module.  Disabled builtin
}  >        modules will show a count of -1 here.
}  
}  Oh i must have missed that! tnx
}  
}  AFAIR having a disabled kernel module won't allow a new version to be loaded
}  from disk or is it? If not, wouldn't this be handy?

     built-in modules are linked at kernel build time.  There's no
way to disentangle them so that they can be truely unloaded.

}-- End of excerpt from Reinoud Zandijk