Duncan Sands wrote:
(in fact, fork() is exactly how libpthread is implemented on Linux)
clone()
Fair enough. My point was that Linux implements threads using processes,
differing from the KSE system of FreeBSD.
The fault is with FreeBSD, really, as every POSIX-compliant system is
expected to
jeremy wrote:
Btw, I'm still using pppoa2, 'cos I can't manage to make pppoa3 work :P
(see below)
PPPoA3 won't work under FreeBSD 4.x due to a poor implementation of
pthreads (I couldn't find a nice workaround either). I did get it
working in FreeBSD 5.x linking against the new libthr
Ok Overbeek (mz) wrote:
If good old fork() would have been used (in stead of threads),
then there would be no problem whatsoever?
Yes, but since PPPoA3 relies on inter-thread communication this would
have been a rather untidy solution with fork().
(in fact, fork() is exactly how libpthread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 20 Jul 2003 22:38 pm, you wrote:
I've had some fails in connecting to irc.openprojects.net
for irc chatting on this matter. Is this the right server?
Try irc.freenode.net, the network was renamed some time ago.
Thanks and greetings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 19 Jul 2003 20:58 pm, you wrote:
Sorry for bothering you guys but I've just installed for the first time
BSD yesterday, so indulge me please..
I've correctly done all, I've pppoa2 and BSD 5.0
I've not heard of BSD 5.0, so I'm
On Tue, 15 Jul 2003, Nuno Ricardo Gomes Antunes wrote:
I having just a little problem: my FreeBSD 5.1 RELEASE crashes when I
try to reboot/shutdown or kill pppoa3 program after a connection.
Yes. It happens to me too. The kernel panics when trying to kill pppoa3.
Don't know if it's a kse
On Mon, 7 Jul 2003, Nuno Ricardo Gomes Antunes wrote:
I've read in the news section of the Speedtouch usb driver homepage that
pppoa3 works on FreeBSD 5.1-CURRENT. However I was unable to find any recent
post on the subject in the lists archive. Has anyone had success? If so,
with what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 26 May 2003 13:58 pm, Iwrote:
Hmm. I've had a thorough look into /sys/dev/usb/ugen.c, and I can't see how
this panic could be occurring since the patch.
This issue has now been fixed. It turned out that the patch was misapplied
when it
