On Sun, 2002-12-08 at 20:56, Sean Kelly wrote:
> On Sun, Dec 08, 2002 at 06:01:49PM -0600, Alan L. Cox wrote:
> > Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> > code has never been safe for general use.
>
> Just for the sake of clusure, that did in fact fix it. Thank yo
On Sun, Dec 08, 2002 at 06:01:49PM -0600, Alan L. Cox wrote:
> Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> code has never been safe for general use.
Just for the sake of clusure, that did in fact fix it. Thank you very much.
Now I'm off to figure out why a specific im
On Sun, Dec 08, 2002 at 05:13:26PM -0800, Matthew Dillon wrote:
>
> :Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> :code has never been safe for general use.
> :
> :Unfortunately, when it was documented in NOTES, this was fact was
> :omitted.
> :
> :Alan
>
> After t
:Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
:code has never been safe for general use.
:
:Unfortunately, when it was documented in NOTES, this was fact was
:omitted.
:
:Alan
After the release, I swear I am going shitcan that damn option.
Robert Watson wrote:
>
> On Sun, 8 Dec 2002, Alan L. Cox wrote:
>
> > Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> > code has never been safe for general use.
> >
> > Unfortunately, when it was documented in NOTES, this was fact was
> > omitted.
>
> Is the attached diff
On Sun, 8 Dec 2002, Alan L. Cox wrote:
> Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> code has never been safe for general use.
>
> Unfortunately, when it was documented in NOTES, this was fact was
> omitted.
Is the attached diff appropriate, then?
Robert N M Watson
Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
code has never been safe for general use.
Unfortunately, when it was documented in NOTES, this was fact was
omitted.
Alan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the me
Whenever x11-fm/nautilus2 starts up and goes to display my home directory
in a window, my kernel panics. This is currently 100% repeatable, but I'm
unable to get a full backtrace because the backtrace is never totally
completed.
While the backtrace is being spit out to my scree from the panic, my
