hi,
On 02/21/2012 08:11 AM, YAMAMOTO Takashi wrote:
hi,
On 01/10/2012 03:30 AM, YAMAMOTO Takashi wrote:
hi,
Hi,
I would like to change upreempt_pri to default to 0 as this
makes wakeups where the interrupted cpu schedules a thread on
another cpu behave like as if it where scheduled
It's not just $ORIGIN that can make use of it. Imagine for a moment
getting a backtrace automatically on a segfault. It's a lot easier
and more reliable if you get access to the debug sections. Those are
normally not mapped though, so you need access to the path.
Actually, you don't. You
I have a question regarding the vnode_to_path() function [...]
The problem is that it works if and only if [...].
That's the immediate pragmatic problem.
More serious, I think, is that it exhibits a much more fundamental
confusion: it is confusing objects with names for objects.
The correct
I don't think that's really an accurate way of saying it.
Well I could have said I confused raidctl's display,
but the one thing that really worried me was the ioctl error at the bottom.
In my experience, the only way to get out of a used hot spare state
is to unconfigure and reconfigure.
Yes,
hi,
hi,
On 02/21/2012 08:11 AM, YAMAMOTO Takashi wrote:
hi,
On 01/10/2012 03:30 AM, YAMAMOTO Takashi wrote:
hi,
Hi,
I would like to change upreempt_pri to default to 0 as this
makes wakeups where the interrupted cpu schedules a thread on
another cpu behave like as if it where
