It is interesting why threre is no answer for this question so long time,
regardless that it was posted 2 times :)
For me it is also interesting to get the answer for this question
since from time to time i also confused by such msgs on
shutdown.
syncing disks... 54 1 1 1 1 1 1 1 1 1 1 1 1 1 1
On Thu, 2005-Feb-24 17:59:19 -0700, Scott Long wrote:
- kernel option support. How do we support vendor modules in a kernel
that might be compiled with PAE (rather common these days), SMP, MAC,
etc. The loader and /boot infrastructure has no concept of this. It's
highly important, though.
hi,
drop me a line if you are willing/interested in trying out the
iSCSI initiator driver. Also if you are willing to just look at it
and provide some feedback.
So far I have tested it against: NetAPP, Intransa and Linux, so if
you have other targets it would help.
BTW, I've been using 5.3
On 2005-02-25 11:34, Kathy Quinlan [EMAIL PROTECTED] wrote:
Daniel O'Connor wrote:
On Thu, 24 Feb 2005 17:57, Kathy Quinlan wrote:
ATM it is written in codevisionAVR which is where the function is
called, so I guess for now I will just break the AVR support;)
Ahh..
So.. are you talking about
Hello hackers,
I wrote to @questions, but as result, I have advised to address the help to you.
Sorry, if I spend your time
I have notebook IP-120MHz without FDD
He is NOT BOOT from CD.
How can i install FreeBSD on it?
Hardvare configuration:
Compaq 5280
Intel Pentium 120MHz
80Mb RAM
4,3 Gb
Although I am not exactly an expert on the field, I'll try to explain.
The disk write procedures should wait for the disk to be ready, and this
involves (soft)interrupts. When rebooting, the system can only wait for
the device drivers to empty the write buffers, since it is not in
interrupt
On Thu, 24 Feb 2005 16:49:59 -0800, Ashwin Chandra [EMAIL PROTECTED] wrote:
Quick question for you hackers!
If i wanted to change the scheduler to have a certain marked bad process have
a higher time quantum than everyone elses (because it is behaving bad, high
mem usage and context
On Thu, Feb 24, 2005 at 03:24:17PM -0600 I heard the voice of
Chris Dillon, and lo! it spake thus:
Your problem with smartmontools doesn't seem to be limited to the
Smart Array 642, I just tried it on a DL380 G3 with the Smart Array
5i+ and got the same error you did. It appears to be a
sleeping(). What you probably want to do is
actually allocate wired kernel pages and export them
to userspace. Take a
look at the GEOM gstat(8) implementation, which does
exactly that.
However, you have to make sure that if you ever
decide to reuse that
kernel memory for something else (i.e.,
9 matches
Mail list logo
