On Wed, 9 Feb 2005 10:51:36 -0500
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
BFF> The LinuxThreads library seems to be the best-supported way. I don't think
BFF> that there should be legal/licensing issues using it.
Unfortunatelly, I can't use the LinuxThreads library, it simpl
Daniel O'Connor wrote:
On Sun, 20 Feb 2005 16:12, Peter Jeremy wrote:
I have a hardware interrupt handler that has to forward a signal to
userland and that I'd like to mark INTR_FAST. AFAIK, the normal way
to forward a signal is:
if ((p = pfind(sc->pid_to_signal)) != NULL) {
Hello,
I was wondering if anyone has figured a way to make vn_fullpath() reliable?
Perhaps there is another approach to attacking this problem. Here is what I need
to accomplish:
I need to be able to determine dynamic linker, shared libraries or executable
name for a specific process.
The alter
Hi Guys,
Here is a section of my code:
*** Wtrend_Drivers.c ***
void Reset_Network (unsigned char Network)
{
Length = 0x00; //Length = 0 as we are not sending any data with
this command
Receiver = 0x00;//Dummy Value for receiver,
Node takes prefferance
Node = 0xF
In message: <[EMAIL PROTECTED]>
Peter Jeremy <[EMAIL PROTECTED]> writes:
: I have a hardware interrupt handler that has to forward a signal to
: userland and that I'd like to mark INTR_FAST. AFAIK, the normal way
: to forward a signal is:
: if ((p = pfind(sc->pid_to_signal)) != N
On Mon, 21 Feb 2005, Kathy Quinlan wrote:
> Hi Guys,
>
> Here is a section of my code:
>
> *** Wtrend_Drivers.c ***
> unsigned char Length , Network , Receiver , Node , Command = 0x00;
> //Some Variables
>
> These are some of the errors I get in pairs for each of the above variables:
>
> Wtrend_
Zera William Holladay wrote:
On Mon, 21 Feb 2005, Kathy Quinlan wrote:
Hi Guys,
Here is a section of my code:
*** Wtrend_Drivers.c ***
unsigned char Length , Network , Receiver , Node , Command = 0x00;
//Some Variables
These are some of the errors I get in pairs for each of the above variables:
Wt
On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
>These are some of the errors I get in pairs for each of the above variables:
>
>Wtrend_Drivers.c:15: conflicting types for `Receiver'
>Wtrend_Drivers.h:9: previous declaration of `Receiver'
Without knowing exactly what is on those lines, it
Joerg Sonnenberger has discovered a problem in the snc(4) driver that might
result in packets showing up on bpf multiple times. See the changelog for
sys/dev/netif/snc/dp83932.c in their source tree[1].
Attached is a fix for HEAD. I am almost sure that it is right, but I'd
welcome a review as
Peter Jeremy wrote:
On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
These are some of the errors I get in pairs for each of the above variables:
Wtrend_Drivers.c:15: conflicting types for `Receiver'
Wtrend_Drivers.h:9: previous declaration of `Receiver'
Without knowing exactly what is on
On Sunday 20 February 2005 11:02 am, Kathy Quinlan wrote:
> Peter Jeremy wrote:
> > On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
> >>These are some of the errors I get in pairs for each of the above
> >> variables:
> >>
> >>Wtrend_Drivers.c:15: conflicting types for `Receiver'
> >>Wtren
On Mon, 21 Feb 2005, Kathy Quinlan wrote:
> Peter Jeremy wrote:
>
> > On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
> >
> >>These are some of the errors I get in pairs for each of the above variables:
> >>
> >>Wtrend_Drivers.c:15: conflicting types for `Receiver'
> >>Wtrend_Drivers.h:9:
Kathy Quinlan wrote:
Peter Jeremy wrote:
On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
These are some of the errors I get in pairs for each of the above
variables:
Wtrend_Drivers.c:15: conflicting types for `Receiver'
Wtrend_Drivers.h:9: previous declaration of `Receiver'
Without know
Michael C. Shultz wrote:
On Sunday 20 February 2005 11:02 am, Kathy Quinlan wrote:
Peter Jeremy wrote:
On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
These are some of the errors I get in pairs for each of the above
variables:
Wtrend_Drivers.c:15: conflicting types for `Receiver'
Wtrend_D
Richard Sharpe wrote:
On Mon, 21 Feb 2005, Kathy Quinlan wrote:
Peter Jeremy wrote:
On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
These are some of the errors I get in pairs for each of the above variables:
Wtrend_Drivers.c:15: conflicting types for `Receiver'
Wtrend_Drivers.h:9: prev
Gary Corcoran wrote:
Kathy Quinlan wrote:
Peter Jeremy wrote:
On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
These are some of the errors I get in pairs for each of the above
variables:
Wtrend_Drivers.c:15: conflicting types for `Receiver'
Wtrend_Drivers.h:9: previous declaration of `Re
On Sunday 20 February 2005 11:48 am, Kathy Quinlan wrote:
> Gary Corcoran wrote:
> > Kathy Quinlan wrote:
> >> Peter Jeremy wrote:
> >>> On Mon, 2005-Feb-21 00:22:56 +0800, Kathy Quinlan wrote:
> These are some of the errors I get in pairs for each of the
> above variables:
>
>
On Sun, 20 Feb 2005, Michael C. Shultz wrote:
> > >> Here is a section of my code:
> > >>
> > >> *** Wtrend_Drivers.c ***
> > >>
> > >> (12)void Reset_Network (unsigned char Network)
> > >> (13) {
> > >> (14)Length = 0x00;
> > >> (15)Receiver = 0x00;
> > >> (16)Node = 0xFF;
> > >> (1
On Feb 20, 2005, at 3:41 PM, Richard Sharpe wrote:
On Sun, 20 Feb 2005, Michael C. Shultz wrote:
Here is a section of my code:
*** Wtrend_Drivers.c ***
(12)void Reset_Network (unsigned char Network)
(13) {
(14)Length = 0x00;
(15)Receiver = 0x00;
(16)Node = 0xFF;
(17)Command = Rese
On Sun, 20 Feb 2005, Max Laier wrote:
> Joerg Sonnenberger has discovered a problem in the snc(4) driver that
> might result in packets showing up on bpf multiple times. See the
> changelog for sys/dev/netif/snc/dp83932.c in their source tree[1].
>
> Attached is a fix for HEAD. I am almost su
On Sun, Feb 20, 2005 at 09:02:25PM +, Robert Watson wrote:
>
> On Sun, 20 Feb 2005, Max Laier wrote:
>
> > Joerg Sonnenberger has discovered a problem in the snc(4) driver that
> > might result in packets showing up on bpf multiple times. See the
> > changelog for sys/dev/netif/snc/dp83932.c
On Sun, Feb 20, 2005, Igor Shmukler wrote:
> Hello,
>
> I was wondering if anyone has figured a way to make vn_fullpath() reliable?
>
> Perhaps there is another approach to attacking this problem. Here is what I
> need
> to accomplish:
>
> I need to be able to determine dynamic linker, shared l
On Sun, Feb 20, 2005, David Schultz wrote:
> On Sun, Feb 20, 2005, Igor Shmukler wrote:
> > Hello,
> >
> > I was wondering if anyone has figured a way to make vn_fullpath() reliable?
> >
> > Perhaps there is another approach to attacking this problem. Here is what I
> > need
> > to accomplish:
>
On Sunday 20 February 2005 12:41 pm, Richard Sharpe wrote:
> On Sun, 20 Feb 2005, Michael C. Shultz wrote:
> > > >> Here is a section of my code:
> > > >>
> > > >> *** Wtrend_Drivers.c ***
> > > >>
> > > >> (12)void Reset_Network (unsigned char Network)
> > > >> (13) {
> > > >> (14)Length = 0
On Sun, 20 Feb 2005, Michael C. Shultz wrote:
> > > > >> *** Wtrend_Drivers.c ***
> > > > >>
> > > > >> (12)void Reset_Network (unsigned char Network)
> > > > >> (13) {
> > > > >> (14)Length = 0x00;
> > > > >> (15)Receiver = 0x00;
> > > > >> (16)Node = 0xFF;
> > > > >> (17)Comman
On Mon, 2005-Feb-21 03:02:29 +0800, Kathy Quinlan wrote:
>Peter Jeremy wrote:
>>2) Pre-process the source and have a close look at the definitions and
>> declarations for Receiver. You may have a stray #define that is
>> confusing the type or a missing semicolon.
...
>(14)Length = 0x00;
>(
26 matches
Mail list logo
