On Tue, 30 May 2000, Garrett Wollman wrote:
> <<[EMAIL PROTECTED]> said:
>
> > i know that :) i guess my questions were
> > 1) why the same piece of code duplicated in all ``mount_xxx'' utilities?
>
> Because the original loadable module system held strongly to the
> religion that the kernel sh
On Tue, 30 May 2000, Zhihui Zhang wrote:
>http://thc.inferno.tusculum.edu/files/thc/bsdkern.html
That stuff is excellent. It belongs in doc/. Any chances of it making
it there?
Brandon D. Valentine
--
"You should believe in death, taxes, Larry Ellison's loathing of Bill
Gates and Intel's ina
< said:
> i know that :) i guess my questions were
> 1) why the same piece of code duplicated in all ``mount_xxx'' utilities?
Because the original loadable module system held strongly to the
religion that the kernel should never load anything of its own
accord. The designers of the current load
i know that :) i guess my questions were
1) why the same piece of code duplicated in all ``mount_xxx'' utilities?
2) if we are loading fs kernel module from ``mount_xxx'' why
we have to do it again in kernel?
if i'm not missing anything, by the time we reach ``mount''
function, fs module will b
I believe that it is used to dynamic load filesystem modules. Please read
the following pages to understand what is a kernel module:
http://thc.inferno.tusculum.edu/files/thc/bsdkern.html
-Zhihui
On Tue, 30 May 2000, Yevmenkin, Maksim N, CSCIO wrote:
> Hello All,
>
> i've been looking at ``m
Hello All,
i've been looking at ``mount_xxx'' code and have noticed "strange" thing.
all ``mount_xxx'' utilities have common part of code, like
error = getvfsbyname("xxx", &vfc);
if (error && vfsisloadable("xxx")) {
if (vfsload("xxx"))
