> >> This is dangerous for the OSM. When the i2o OSM shuts an IOP
> >> down, it is history. It will stop doing any work at all; network,
> >> disk, console, mouse, whatever. I reserve that for really, really
> >> shutdown/reset.
> >
> > I'm not sure I understand what you mean by "dangerous".
On 10-May-00 Mike Smith wrote:
...
>> This is dangerous for the OSM. When the i2o OSM shuts an IOP
>> down, it is history. It will stop doing any work at all; network,
>> disk, console, mouse, whatever. I reserve that for really, really
>> shutdown/reset.
>
> I'm not sure I understand what
On Tue, 9 May 2000, Mike Smith wrote:
> >
> > On 10-May-00 Mike Smith wrote:
> > >> Sorry to bother y'll, but;
> > >>
> > >> Has anyone ever used that? I see no trace of any kernel
> > >> code calling it, and the at_shutdown code appears to be
> > >> gone.
> > >
> > > It's still used in the s
Simon Shapiro wrote:
>
> On 10-May-00 Mike Smith wrote:
> >> Sorry to bother y'll, but;
> >>
> >> Has anyone ever used that? I see no trace of any kernel
> >> code calling it, and the at_shutdown code appears to be
> >> gone.
> >
> > It's still used in the shutdown code; it was meant to be ava
>
> On 10-May-00 Mike Smith wrote:
> >> Sorry to bother y'll, but;
> >>
> >> Has anyone ever used that? I see no trace of any kernel
> >> code calling it, and the at_shutdown code appears to be
> >> gone.
> >
> > It's still used in the shutdown code; it was meant to be available for
> > gener
On 10-May-00 Mike Smith wrote:
>> Sorry to bother y'll, but;
>>
>> Has anyone ever used that? I see no trace of any kernel
>> code calling it, and the at_shutdown code appears to be
>> gone.
>
> It's still used in the shutdown code; it was meant to be available for
> general use elsewhere, bu
Correction to the below message;
Figured it out all by myself :-)
Thanx!
On 10-May-00 Simon Shapiro wrote:
> Sorry to bother y'll, but;
>
> Has anyone ever used that? I see no trace of any kernel
> code calling it, and the at_shutdown code appears to be
> gone.
>
> BTW, for all it is worth,
> Sorry to bother y'll, but;
>
> Has anyone ever used that? I see no trace of any kernel
> code calling it, and the at_shutdown code appears to be
> gone.
It's still used in the shutdown code; it was meant to be available for
general use elsewhere, but I haven't seen anyone playing with it, so
Sorry to bother y'll, but;
Has anyone ever used that? I see no trace of any kernel
code calling it, and the at_shutdown code appears to be
gone.
BTW, for all it is worth, any caching controller not using
this is guaranteed to lose data.
that can range from 4MB to 256MB, all of which the kernel
