IMAGINE THAT
This email is of an ADULT NATURE, if you are not over 18 years old, you must delete this message as you are not the intended recipient. http://213.180.33.225/site2/ - FREE UNLIMITED ACCESS- The horniest TEEN XXX online 50,000 Ultimate Fucking Channels 120,000 Hardcore Premium Images Teen fucking, licking and sucking videos. - FREE UNLIMITED ACCESS- http://213.180.33.225/site2/ These Babes are built like godessses!!! Where the fuck were they when I was growing up? http://213.180.33.225/site2/ They were a little scared at first but now they love the taste of cock! - FREE UNLIMITED ACCESS - To remove yourself from our free newsletter service, email [EMAIL PROTECTED] with the word 'remove' in the subject field To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
smbfs support
Hi. I'm trying to compile smbfs. I've added SMBFS and NETSMB options to my kernel config, but I'm not sure is it enough. The output of make buildkernel is as follows: -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/fs/smbfs/smbfs_io.c /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_readvdir': /usr/src/sys/fs/smbfs/smbfs_io.c:97: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_readvnode': /usr/src/sys/fs/smbfs/smbfs_io.c:201: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c:205: warning: passing arg 3 of `vn_lock' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:208: warning: passing arg 3 of `vn_lock' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:215: warning: passing arg 4 of `VOP_GETATTR' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:220: warning: passing arg 4 of `VOP_GETATTR' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:186: warning: `p' might be used uninitialized in this function /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_writevnode': /usr/src/sys/fs/smbfs/smbfs_io.c:253: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c:241: warning: `p' might be used uninitialized in this function /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_doio': /usr/src/sys/fs/smbfs/smbfs_io.c:310: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_getpages': /usr/src/sys/fs/smbfs/smbfs_io.c:461: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_putpages': /usr/src/sys/fs/smbfs/smbfs_io.c:599: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_vinvalbuf': /usr/src/sys/fs/smbfs/smbfs_io.c:657: warning: passing arg 4 of `vinvalbuf' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:667: warning: passing arg 4 of `vinvalbuf' from incompatible pointer type Is there any workaround for this? greets przem To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: smbfs support
On Wed, 28 Nov 2001 13:06:00 +0100, Przemyslaw Kowalczyk wrote: | I'm trying to compile smbfs. I've added SMBFS and NETSMB options to my kernel | config, but I'm not sure is it enough. The output of make buildkernel is as | follows: I don't think anyone's updated smbfs for the post-KSE world order. The smbfs maintainer seems snowed under, and Julian wants someone who understands it better to take a look. That was the case a couple of weeks ago, at any rate. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: smbfs support
hi, there! On Wed, Nov 28, 2001 at 02:30:54PM +0200, Sheldon Hearn wrote: | I'm trying to compile smbfs. I've added SMBFS and NETSMB options to my kernel | config, but I'm not sure is it enough. The output of make buildkernel is as | follows: I don't think anyone's updated smbfs for the post-KSE world order. The smbfs maintainer seems snowed under, and Julian wants someone who understands it better to take a look. That was the case a couple of weeks ago, at any rate. I have some untested patches in my tree and I will contact bp this week about them (I wanted to import smbfs userland to the tree and already got ok from bp but could not test it because kernel-side smbfs is not compilable yet). /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: smbfs support
hi, there! On Wed, Nov 28, 2001 at 02:55:24PM +0200, Sheldon Hearn wrote: | I have some untested patches in my tree and I will contact bp this | week about them (I wanted to import smbfs userland to the tree and | already got ok from bp but could not test it because kernel-side smbfs | is not compilable yet). Excellent news! Presumably, if bp doesn't respond by the end of the year, you'll go ahead regardless? :-) :) bp is quite responsive. I even had a talk with him on #bsdcode /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: smbfs support
On Wed, 28 Nov 2001 18:58:10 +0600, Max Khon wrote: | :) | bp is quite responsive. I even had a talk with him on #bsdcode Even more good news. I look forward to forgetting about the smbfs port! :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/conf files src/sys/dev/ciss ciss.c cissio.h cissreg.h cissvar.h src/sys/modules Makefile src/sys/modules/ciss Makefile src/sys/i386/conf NOTES
On Wed, 28 Nov 2001 12:57:04 +0600 (NOVT), [EMAIL PROTECTED] (Nickolay Dudorov) said: And I can buildkernel only after the next patch: I don't reach that: /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:3214: conflicting types for `cis s_open' /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:210: previous declaration of `ci ss_open' /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:3232: conflicting types for `cis s_close' /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:211: previous declaration of `ci ss_close' /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:3251: conflicting types for `cis s_ioctl' /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:212: previous declaration of `ci ss_ioctl' /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:1640: warning: `ciss_abort_reque st' defined but not used -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law Minneapolis, Minnesota He who will not reason is a bigot; he who cannot is a fool; and he who dares not, is a slave. -- William Drummond To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cdrecord produces broken CDs on -CURRENT: The Answer !
The Problem was the use of vfs.ioopt=2 ! As long as vfs.ioopt is 1 or 2 the CDs are broken and with vfs.ioopt=0 the CDs are o.k. I didn't see any other problems with the use of vfs.ioopt=2, especially no Filesystem corruption :-). Are there other known problems withs vfs.ioopt != 0 ? Ciao Christoph :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
posible libc_r pthread bug?
I posted this on -hackers, it was suggested I post it to -current as well
I've encountered a problem using pthread_cancel, pthread_join and
pthread_setcanceltype, I'm hoping someone can shed some light.
(in a nutshell : pthread_setcanceltype doesn't seem to work)
(if there's a more appropriate mailing list for this, please let me know)
I recently encountered a situation where, after calling pthread_cancel to
cancel a thread, the call to pthread_join hangs indefinitely. I quickly figured
out that it was because the thread being cancelled was never reaching a
cancellation point (in fact it was an infinite loop with no function calls at all).
Sure enough, adding a pthread_testcancel() in the loop allowed
pthread_join to return. However this solution isn't acceptable for my requirements.
I discovered the pthread_setcanceltype function and its
PTHREAD_CANCEL_ASYNCHRONOUS parameter, which looked like
they would give me exactly what I needed : allow threads to be cancelled
regardless of what they are doing (basically a pthread equivalent to
TerminateThread).
Unfortunately, my tests have been less than conclusive : pthread_setcanceltype
doesn't seem to do anything at all. It tells me it succeeds, subsequent calls
properly report the previous cancellation type as ASYNCHRONOUS.
But pthread_join still hangs, and adding pthread_testcancel calls still
makes it work...
I'm working on a FreeBSD 4.4-release machine; I ran the same test under
FreeBSD 4.3-release and got the same results. However, running it on a
Linux box (Mandrake release, 2.4.x kernel), I get exactly the results I
was expecting (that is, setting the cancellation type to asynchronous allows
the thread to be cancelled at any time)
see the end of this message for my test program
So the questions are
-am I doing something wrong or misinterpreting the man pages?
-if not, is this a known bug?
-if so, is there a workaround (or is it already fixed)?
-if not, can someone investigate? (I once had a look at the libc_r code
and ran away screaming)
If this turns out to be a bug in libc_r, a suggestion for a work-around
(even a hack) would be much appreciated, even if a proper fix is found and
committed to CVS (requiring an upgrade from 4.4-release installations is
something we'd rather avoid).
now for some disclaimers :
I'm aware that asynchronous cancellations (TerminateThread-style) are an
Evil Thing To Do. Unfortunately I have no choice in the matter.
I'm aware that there are some strict limitations on what a thread is allowed
to do while its cancellation type is asynchronous. specifically, it should only
call cancel-safe functions. Note that in my test program, the thread being
cancelled doesn't call any functions at all after setting its cancellation type, so
this shouldn't be an issue.
now for the code :
#include stdio.h
#include pthread.h
/* thread entry point */
void * thread_entry (void *arg)
{
int i;
if(0!=pthread_setcanceltype(PTHREAD_CANCEL_ASYNCHRONOUS,NULL))
{
fprintf(stderr,setcanceltype failed!\n);
}
fprintf(stderr,thread_entry entering loop\n);
while(1)
{
i++;
/* uncomment this to insert a cancellation point */
/* pthread_testcancel();*/
}
/* if we see this, it would mean the loop has been optimized out... */
fprintf(stderr, after loop\n);
}
int main(void)
{
pthread_t thread;
pthread_attr_t attr;
void *pthread_param;
pthread_attr_init(attr);
fprintf(stderr,creating thread\n);
pthread_create(thread,attr,thread_entry,NULL);
fprintf(stderr,thread created; hit enter to cancel it...\n);
getchar();
fprintf(stderr,cancelling...\n);
if(0!=pthread_cancel(thread))
{
fprintf(stderr,cancel failed!\n);
}
fprintf(stderr,after cancel, before join...\n);
if(0!=pthread_join(thread,pthread_param))
{
fprintf(stderr,join failed!\n);
}
fprintf(stderr,after join\n);
}
please ask if more details are needed
Thanks in advance,
Louis-Philippe Gagnon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/conf files src/sys/dev/ciss ciss.c cissio.h cissreg.h cissvar.h src/sys/modules Makefile src/sys/modules/ciss Makefile src/sys/i386/conf NOTES
From: Michael Harnois [EMAIL PROTECTED] Date: Wed, 28 Nov 2001 08:25:00 -0600 On Wed, 28 Nov 2001 12:57:04 +0600 (NOVT), [EMAIL PROTECTED] (Nickolay Dudorov) said: And I can buildkernel only after the next patch: I don't reach that: /usr/src/sys/modules/ciss/../../dev/ciss/ciss.c:3214: conflicting types for `cis ... I got to the same failure point that Michael did, (hand-)applied Nickolay's patch, and was able to build the kernel OK. Now installing world, as I type. Most of Nickolay's patch appears to update ciss.c for the KSE support, it seems to me. Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdrecord produces broken CDs on -CURRENT: The Answer !
On 28 Nov, Christoph Herrmann wrote: The Problem was the use of vfs.ioopt=2 ! As long as vfs.ioopt is 1 or 2 the CDs are broken and with vfs.ioopt=0 the CDs are o.k. I didn't see any other problems with the use of vfs.ioopt=2, especially no Filesystem corruption :-). Are there other known problems withs vfs.ioopt != 0 ? At the time I tested this, native netscape died with a bus error (or segfault?, don't remember). Bye, Alexander. -- There's no place like ~ http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libfetch kqueue patch
Garrett Wollman wrote: On Mon, 26 Nov 2001 15:27:45 -0500 (EST), Andrew R. Reiter [EMAIL PROTECTED] said: As from OpenBSD (in shorter form): fd_set *fds = calloc(howmany(fd+1, NFDBITS), sizeof(fd_mask)); But this is not portable. The application is not allowed to assume anything about the structure of an fd_set, or the existence of a type `fd_mask', or the existence of a macro `howmany' (which is actually prohibited). The only portable (in the sense of officially standardized) interface that doesn't suffer from this problem is poll(). This answers your original concern - convert it to use poll(2) instead of select(2) and you will be safe from the out of default fd_set without loosing portability. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can somebody add new usb scanner?
Ilmar S. Habibulin wrote: It works with latest sane. Done. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: smbfs support
SMBFS is broken, it will be fixed but I'm not sure when. the other broken one in NWFS On Wed, 28 Nov 2001, Przemyslaw Kowalczyk wrote: Hi. I'm trying to compile smbfs. I've added SMBFS and NETSMB options to my kernel config, but I'm not sure is it enough. The output of make buildkernel is as follows: -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/fs/smbfs/smbfs_io.c /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_readvdir': /usr/src/sys/fs/smbfs/smbfs_io.c:97: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_readvnode': /usr/src/sys/fs/smbfs/smbfs_io.c:201: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c:205: warning: passing arg 3 of `vn_lock' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:208: warning: passing arg 3 of `vn_lock' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:215: warning: passing arg 4 of `VOP_GETATTR' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:220: warning: passing arg 4 of `VOP_GETATTR' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:186: warning: `p' might be used uninitialized in this function /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_writevnode': /usr/src/sys/fs/smbfs/smbfs_io.c:253: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c:241: warning: `p' might be used uninitialized in this function /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_doio': /usr/src/sys/fs/smbfs/smbfs_io.c:310: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_getpages': /usr/src/sys/fs/smbfs/smbfs_io.c:461: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_putpages': /usr/src/sys/fs/smbfs/smbfs_io.c:599: structure has no member named `uio_procp' /usr/src/sys/fs/smbfs/smbfs_io.c: In function `smbfs_vinvalbuf': /usr/src/sys/fs/smbfs/smbfs_io.c:657: warning: passing arg 4 of `vinvalbuf' from incompatible pointer type /usr/src/sys/fs/smbfs/smbfs_io.c:667: warning: passing arg 4 of `vinvalbuf' from incompatible pointer type Is there any workaround for this? greets przem To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re:
TechMail found a potentially dangerous file attachment
The TechMail Anti-Virus Scanner found a potentially dangerous file (New_Napster_Site.MP3.pif) sent from Jim Gansle ([EMAIL PROTECTED]). The file was discovered attached to an email message addressed to you with a subject of Re:. The attachment has been replaced with a safe text file and the remainder of the message has been placed in your Inbox. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cardbus help
Warner Losh wrote: In message [EMAIL PROTECTED] John McCullough writes: : pcib2: routed slot 15 INTA to irq 255 : pccbb: Unable to map IRQ... : panic: resouce_list_release:can't find resource : Debugger(panic) This is a bug in pcibus issue. IRQ 255 should be treated as unallocated, so please route. As I'm still learning, I hope my questions aren't too annoying, to do this would I have the kernel route to a different IRQ (say 10) instead of 255 by default? thanks, Johnm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/conf files src/sys/dev/ciss ciss.c cissio.h cissreg.h cissvar.h src/sys/modules Makefile src/sys/modules/ciss Makefile src/sys/i386/conf NOTES
In message [EMAIL PROTECTED] Nickolay Dudorov writ es: : And I can buildkernel only after the next patch: I just removed this from build until Mike can fix the ciss driver itself. Sorry about this; I got distracted last night, and my last -current test build was too long ago. 8( I'll try to fix it tonight; in the meantime, where's that hat? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/conf files src/sys/dev/ciss ciss.c cissi
On 28-Nov-01 Mike Smith wrote:
In message [EMAIL PROTECTED] Nickolay Dudorov
writ
es:
:And I can buildkernel only after the next patch:
I just removed this from build until Mike can fix the ciss driver
itself.
Sorry about this; I got distracted last night, and my last -current
test build was too long ago. 8( I'll try to fix it tonight; in the
meantime, where's that hat?
I've got a patch that I think will work for both 4.x and 5.0. It compiles on
-current at least. It is at www.freebsd.org/~jhb/patches/ciss.patch and below
(note, my mailer destroys patches, so the version below is just for viewing):
Index: ciss.c
===
RCS file: /usr/cvs/src/sys/dev/ciss/ciss.c,v
retrieving revision 1.1
diff -u -r1.1 ciss.c
--- ciss.c 27 Nov 2001 23:08:36 - 1.1
+++ ciss.c 28 Nov 2001 23:23:45 -
@@ -216,7 +216,7 @@
static struct cdevsw ciss_cdevsw = {
ciss_open, ciss_close, noread, nowrite, ciss_ioctl,
nopoll, nommap, nostrategy, ciss, CISS_CDEV_MAJOR,
-nodump, nopsize, 0, -1
+nodump, nopsize, 0, nokqfilter
};
/
@@ -3210,7 +3210,7 @@
* Handle an open on the control device.
*/
static int
-ciss_open(dev_t dev, int flags, int fmt, struct proc *p)
+ciss_open(dev_t dev, int flags, int fmt, d_thread_t *p)
{
struct ciss_softc *sc;
@@ -3228,7 +3228,7 @@
* Handle the last close on the control device.
*/
static int
-ciss_close(dev_t dev, int flags, int fmt, struct proc *p)
+ciss_close(dev_t dev, int flags, int fmt, d_thread_t *p)
{
struct ciss_softc *sc;
@@ -3247,7 +3247,7 @@
* simplify the porting of Compaq's userland tools.
*/
static int
-ciss_ioctl(dev_t dev, u_long cmd, caddr_t addr, int32_t flag, struct proc *p)
+ciss_ioctl(dev_t dev, u_long cmd, caddr_t addr, int32_t flag, d_thread_t *p)
{
struct ciss_softc *sc;
interror;
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: where is the idle_loop in current ?
On 28-Nov-01 Bruce Evans wrote: On Mon, 26 Nov 2001, John Baldwin wrote: We don't do preemption in the kernel yet, so they need to yield the CPU when another thread is available. The page zeroing thread does this wrong as it should check procrunnable() instead of switching after doing N pages. The idle Except it would always find at least itself runnable :-). No b/c it isn't on the runqueue when it does the check. :) Nor is the default idle loop ever on the runqueues. Bruce -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
more on the linuxulator
I'm not sure if I'm sending this to the correct place, but since it is a
problem that will/could be fixed in -CURRENT, I'm assuming this is the right
place.
I tried to get the winex linux binary to run using the linux_base-6.1
libraries and I still got some errors, although not as many:
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
I was just wondering if anyone was planning to implement this. If not, I'll
probably do my best to try to get it working.
Ken
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: more on the linuxulator
On Wed, Nov 28, 2001 at 11:55:58PM -0500, Kenneth Culver wrote:
I'm not sure if I'm sending this to the correct place, but since it is a
problem that will/could be fixed in -CURRENT, I'm assuming this is the right
place.
I tried to get the winex linux binary to run using the linux_base-6.1
libraries and I still got some errors, although not as many:
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
I was just wondering if anyone was planning to implement this. If not, I'll
probably do my best to try to get it working.
Ken
The errors that you posted don't really mean much without more information.
It would be very useful to know what fd=6 refers to, and you can use truss
to find that out. Let me know if you need help.
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: world broken in share/colldef ?
On Wed, Nov 28, 2001 at 11:00:10 +0100, Poul-Henning Kamp wrote: Any clues ? Rebuild colldef from very latest sources. BTW, colldef is already in bootstrap-tools -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
