On Tue, 20 May 2008, Res wrote:

> You are so correct, bugger, how did I miss that one
> Oh well, lets see if he pastes his new error now he has hopefully learnt
> how to manually load modules

I have known for many years how to load modules, nothing to learn
more than what has changed recently. I recognize my remarks might
have been confusing. I should maybe have written that loading
classical way without *.ko does not load modules. As a result, I
tried adding *.ko to see if this would help. Still no luck. I
am now trying a couple different tricks to better understand the
problem, but I must say, I am concerned about how many changes
are happening in this OS that are baffling even those of us who
have used, contributed and taught Linux extensively since the
beginning.

Dominic

On Tue, 20 May 2008, Dominic-Luc Webb wrote:

>
> On Tue, 20 May 2008, Res wrote:
>
>> You are so correct, bugger, how did I miss that one
>> Oh well, lets see if he pastes his new error now he has hopefully learnt
>> how to manually load modules
>
> I have known for many years how to load modules, nothing to learn
> more than what has changed recently. I recognize my remarks might
> have been confusing. I should maybe have written that loading
> classical way without *.ko does not load modules. As a result, I
> tried adding *.ko to see if this would help. Still no luck. I
> am now trying a couple different tricks to better understand the
> problem, but I must say, I am concerned about how many changes
> are happening in this OS that are baffling even those of us who
> have used, contributed and taught Linux extensively since the
> beginning.

*shrug* I've been using it since almost day dot myself, took a bit of
converting over from unix since i've used that for over 25 years, but
times change, and as such we must change with it, or be left behind,
you wouldnt be using your usb at all if you wanted to stay how we had it
say, 10 years ago.

I have none of the problems you are exhibiting, I use quickcams as remote
security covering my house and have done for a number of years without any
problem, as do many others I know, I do not however use them for
netmeeting style chats as a general rule, but have done so on the odd
occasion.


--
Cheers
Res

I read usenet and lists in pine. But m$ outlook, thunderbird and gmail
often use html span/whatever for quotes, makes it hard to tell who said
what, so I dont try. If I ignore you, thats why! Use a compliant mailer.

On Tue, 20 May 2008, Res wrote:

> I have none of the problems you are exhibiting, I use quickcams as remote
> security covering my house and have done for a number of years without any
> problem, as do many others I know, I do not however use them for
> netmeeting style chats as a general rule, but have done so on the odd
> occasion.


Definitely this prob is new for me. Webcams in general have
worked, sometimes with a little hassle with drivers. I hope
to take you up on a separate discussion soon about VoIP,
since you brought it up. Ekiga now has some problems, seems
to relate to recent changes in ALSA.

Back soon with remarks on insmod problem.

Dominic

On Tue, 20 May 2008, Dominic-Luc Webb wrote:

>
> On Tue, 20 May 2008, Res wrote:
>
>> I have none of the problems you are exhibiting, I use quickcams as remote
>> security covering my house and have done for a number of years without any
>> problem, as do many others I know, I do not however use them for
>> netmeeting style chats as a general rule, but have done so on the odd
>> occasion.
>
>
> Definitely this prob is new for me. Webcams in general have
> worked, sometimes with a little hassle with drivers. I hope
> to take you up on a separate discussion soon about VoIP,
> since you brought it up. Ekiga now has some problems, seems
> to relate to recent changes in ALSA.

I never brought up VoIP, maybe someone else did? I did not see it anyway,
but my news server has a UDP on googlegroups so if someone commented via
them, or had enough content for spamassassin to dump the post, I wouldn't
have seen it


--
Cheers
Res

I read usenet and lists in pine. But m$ outlook, thunderbird and gmail
often use html span/whatever for quotes, makes it hard to tell who said
what, so I dont try. If I ignore you, thats why! Use a compliant mailer.

On Wed, 21 May 2008, Res wrote:

> I never brought up VoIP, maybe someone else did? I did not see it anyway,
> but my news server has a UDP on googlegroups so if someone commented via
> them, or had enough content for spamassassin to dump the post, I wouldn't
> have seen it
> Cheers
> Res

You mentioned "netmeeting" in your last email.

Dominic

On Wed, 21 May 2008, Dominic-Luc Webb wrote:

>
> On Wed, 21 May 2008, Res wrote:
>
>> I never brought up VoIP, maybe someone else did? I did not see it anyway,
>> but my news server has a UDP on googlegroups so if someone commented via
>> them, or had enough content for spamassassin to dump the post, I wouldn't
>> have seen it
>> Cheers
>> Res
>
> You mentioned "netmeeting" in your last email.
>

netmeeting is not voip, its been around years and years and years longer
than voip


--
Cheers
Res

I read usenet and lists in pine. But m$ outlook, thunderbird and gmail
often use html span/whatever for quotes, makes it hard to tell who said
what, so I dont try. If I ignore you, thats why! Use a compliant mailer.

In alt.os.linux.slackware, Res wrote:

> On Wed, 21 May 2008, Dominic-Luc Webb wrote:
>
>>
>> On Wed, 21 May 2008, Res wrote:
>>
>>> I never brought up VoIP, maybe someone else did? I did not see it
>>> anyway, but my news server has a UDP on googlegroups so if someone
>>> commented via them, or had enough content for spamassassin to dump the
>>> post, I wouldn't have seen it
>>> Cheers
>>> Res
>>
>> You mentioned "netmeeting" in your last email.
>>
>
> netmeeting is not voip, its been around years and years and years longer
> than voip

Pardon my intrusion, but you are (sort of) wrong here.

Netmeeting uses the H.323 protocol suite over TCP/IP to transmit video and
voice, so technically it qualifies as an implementation of a
V(oice)o(ver)IP solution.

These days, the H.323 protocol suite has fallen in disfavour with the VoIP
crowd (it is still used by the teleconference people), and has mostly been
replaced by implementations of the SIP family of protocols (defined by the
IETF) and the IAX protocol suite defined by the makers of the popular
Asterisk PBX software. There are, of course, other popular VoIP protocols,
ranging from Cisco's internal TCP/IP protocol to the TCP/IP protocol used
by Skype, but SIP seems to be the emerging standard, at least for voice
session initiation and control.


--
Lew Pitcher

Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------

On Wed, 21 May 2008, Lew Pitcher wrote:

> > netmeeting is not voip, its been around years and years and years longer
> > than voip
>
> Pardon my intrusion, but you are (sort of) wrong here.

Actually, he is completely wrong! Netmeeting is specifically
defined as VOIP software. There are no ambiguities on this
point. I have no idea why he would challenge this.

Dominic

In alt.os.linux.slackware, Dominic-Luc Webb wrote:

> On Wed, 21 May 2008, Lew Pitcher wrote:
>
>> > netmeeting is not voip, its been around years and years and years
>> > longer than voip
>>
>> Pardon my intrusion, but you are (sort of) wrong here.
>
> Actually, he is completely wrong! Netmeeting is specifically
> defined as VOIP software.

Not quite, and thats why I said "(sort of) wrong". Netmeeting is
specifically designed as a teleconferencing system, with video and voice,
using the H.323 conferencing protocols. It carries voice over IP, so that
makes it VOIP, but it /also/ carries video (and, IIRC, whiteboard) data
which is specifically /not/ VOIP.

--
Lew Pitcher

Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------

if you want to get fuckin pendantic about it maybe, but the term netmeeting
was used, again, many years before voip was conceived, i thought the avg
user in this group had enough nouse to know what i was referring to, but
clearly i must spell things out like i'm talking to a 5 yo


On Wed, 21 May 2008, Lew Pitcher wrote:

>
> In alt.os.linux.slackware, Res wrote:
>
>> On Wed, 21 May 2008, Dominic-Luc Webb wrote:
>>
>>>
>>> On Wed, 21 May 2008, Res wrote:
>>>
>>>> I never brought up VoIP, maybe someone else did? I did not see it
>>>> anyway, but my news server has a UDP on googlegroups so if someone
>>>> commented via them, or had enough content for spamassassin to dump the
>>>> post, I wouldn't have seen it
>>>> Cheers
>>>> Res
>>>
>>> You mentioned "netmeeting" in your last email.
>>>
>>
>> netmeeting is not voip, its been around years and years and years longer
>> than voip
>
> Pardon my intrusion, but you are (sort of) wrong here.
>
> Netmeeting uses the H.323 protocol suite over TCP/IP to transmit video and
> voice, so technically it qualifies as an implementation of a
> V(oice)o(ver)IP solution.
>
> These days, the H.323 protocol suite has fallen in disfavour with the VoIP
> crowd (it is still used by the teleconference people), and has mostly been
> replaced by implementations of the SIP family of protocols (defined by the
> IETF) and the IAX protocol suite defined by the makers of the popular
> Asterisk PBX software. There are, of course, other popular VoIP protocols,
> ranging from Cisco's internal TCP/IP protocol to the TCP/IP protocol used
> by Skype, but SIP seems to be the emerging standard, at least for voice
> session initiation and control.
>
>
>

--
Cheers
Res

I read usenet and lists in pine. But m$ outlook, thunderbird and gmail
often use html span/whatever for quotes, makes it hard to tell who said
what, so I dont try. If I ignore you, thats why! Use a compliant mailer.