The Program Committee for the 3rd Workshop on the Theory and Practice of
Provenance (TaPP '11) invites you to submit short papers on
ongoing work.
TaPP '11 will bring together researchers and practitioners doing
innovative work in the area of provenance. With the deluge of digital data
we are curr
On Tue, 1 Mar 2011, Jason Helfman wrote:
On Tue, Mar 01, 2011 at 12:01:48PM -0800, Carl thus spake:
I can explicitly include ucom in a kernel by adding "device ucom" in the
configuration file, in which case it would call DRIVER_MODULE(), right?
That would then make it appear in the "kldstat -v
On Tue, Mar 01, 2011 at 12:01:48PM -0800, Carl thus spake:
On 2011-03-01 3:20 AM, Maxim Khitrov wrote:
kldstat provides information about components that were loaded
dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option
(enabled by default in GENERIC), then you can see the static
On 2011-03-01 3:20 AM, Maxim Khitrov wrote:
kldstat provides information about components that were loaded
dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option
(enabled by default in GENERIC), then you can see the static
components using:
config -x /boot/kernel/kernel
As has b
On Tuesday, March 01, 2011 6:49:17 am Daniel O'Connor wrote:
>
> On 01/03/2011, at 15:10, Carl wrote:
> > Kernel drivers can be (and in at least one case are) compiled into the
> > kernel but are not reported when queried for, at least not in a way that
I am aware of. For example, the ucom drive
On 3/1/11 12:20 PM, Maxim Khitrov wrote:
> On Mon, Feb 28, 2011 at 11:40 PM, Carl wrote:
>> Kernel drivers can be (and in at least one case are) compiled into the
>> kernel but are not reported when queried for, at least not in a way that I
>> am aware of. For example, the ucom driver is present i
On Tue, 1 Mar 2011 06:20:29 -0500
Maxim Khitrov wrote:
> kldstat provides information about components that were loaded
> dynamically. If your kernel was built with INCLUDE_CONFIG_FILE option
> (enabled by default in GENERIC), then you can see the static
> components using:
It seems it can also
On Mon, Feb 28, 2011 at 11:40 PM, Carl wrote:
> Kernel drivers can be (and in at least one case are) compiled into the
> kernel but are not reported when queried for, at least not in a way that I
> am aware of. For example, the ucom driver is present in the GENERIC kernel
> in this way. My expecta
On 3/1/11 5:40 AM, Carl wrote:
> Kernel drivers can be (and in at least one case are) compiled into the
> kernel but are not reported when queried for, at least not in a way that
> I am aware of. For example, the ucom driver is present in the GENERIC
> kernel in this way. My expectation was that "k
On 01/03/2011, at 15:10, Carl wrote:
> Kernel drivers can be (and in at least one case are) compiled into the kernel
> but are not reported when queried for, at least not in a way that I am aware
> of. For example, the ucom driver is present in the GENERIC kernel in this
> way. My expectation w
10 matches
Mail list logo
