$B$O$8$a$^$7$F!"$j$+$G!<$9!#(B$BFMA3$G$9$,!":G6a!"$I!<$b!VF|>H$j!W$,B3$$$F$k$N$h$M!#(B$B$"!<$C!"$I$C$+$KCK!"$$$J$$$+$J!<$C!"$J!<$s$F(B$B;W$C$?$j$7$A$c$C$F$k:#F|$3$N:"!#(B$B$C$F$f!<%o%1$G!"%"%J%?$K$*$B%V%7%D%1$J%a!<%k$+$b$7$l$J$$$1$I!"5v$7$F$M!#(B$B$$$i$J$$$J$i%4%_H"$K%]%$$7$F2<
On Thursday, 15 July 1999 at 0:08:07 -0400, Luoqi Chen wrote:
>> I've been getting this panic when I've installed new kernels the last
>> couple of times. The panic is occuring when I have freshly booted the
>> system with a new kernel and logged on for the first time. It appears
>> to occur at
On Thu, 15 Jul 1999 21:18:03 +0100, Dominic Mitchell wrote:
> This of course begs the question, under what circumstances *should* one
> use INVARIANTS?
This has been explained to me before as "when you have the time and
inclination to look into any problems that this might cause or
highlight."
On Thu, Jul 15, 1999 at 10:01:18AM -0700, Matthew Dillon wrote:
> :> I realise that will stop the panic from looking at the source code, but
> :> surely it's just covering up the problem and waiting for it to happen
> :> later?
> :>
> :I'm pretty it's caused by the INVARIANTS option, similar incid
On Thu, Jul 15, 1999 at 12:18:42PM -0400, Luoqi Chen wrote:
> > I realise that will stop the panic from looking at the source code, but
> > surely it's just covering up the problem and waiting for it to happen
> > later?
> >
> I'm pretty it's caused by the INVARIANTS option, similar incidents have
On Thu, 15 Jul 1999, Luoqi Chen wrote:
> > I realise that will stop the panic from looking at the source code, but
> > surely it's just covering up the problem and waiting for it to happen
> > later?
> >
> I'm pretty it's caused by the INVARIANTS option, similar incidents have been
> reported man
I'm interested in finding someone to help me get the aio patches I've
written committed into -current. These fixes make the aio routines much
more useful for io on sockets than they are now (each io op on a socket
blocks an aiod). This is a bit of a work in progress, but I've been
running these
On Thu, Jul 15, 1999 at 01:32:50PM -0400, John W. DeBoskey wrote:
>It seems to have dropped the v2 flag...
Mount can only get generic options back again - I went looking for
a way to get the other options back again when I was adding the fstab
and cur options to mount, but couldn't find any.
Hi,
I just noticed the following while tracing my config to make
sure everything was correct:
From /etc/fstab, I am forcing a v2 mount:
netapp01:/vol/sas /sasnfs rw,nfsv20 2
/sbin/mount -p should create an fstab format output:
netapp01:/vol/sas
:> I realise that will stop the panic from looking at the source code, but
:> surely it's just covering up the problem and waiting for it to happen
:> later?
:>
:I'm pretty it's caused by the INVARIANTS option, similar incidents have been
:reported many times before. The problem with INVARIANTS is
> I realise that will stop the panic from looking at the source code, but
> surely it's just covering up the problem and waiting for it to happen
> later?
>
I'm pretty it's caused by the INVARIANTS option, similar incidents have been
reported many times before. The problem with INVARIANTS is that
11 matches
Mail list logo
