Re: Is there a script for updating sources for KSE?

On Sat, Oct 06, 2001 at 12:32:20AM +1000, Andrew Kenneth Milton wrote: > Nevermind d8). I've updated the code for vmware2, and the drm-kmod ports, and > have contacted the maintainers. So hopefully the code will go into the > relevant ports soon. I already posted patches for vmware on Sept 14; be

Re: kldxref broken, maybe?

On Tue, Oct 09, 2001 at 10:49:56AM -0700, Bruce A. Mah wrote: > If memory serves me right, Ruslan Ermilov wrote: > > On Thu, Sep 20, 2001 at 10:19:22PM -0700, Peter Wemm wrote: > > > Warner Losh wrote: > > > > In message Mark Peek writes: > > > > : Install

Re: Why do soft interrupt coelescing?

"Kenneth D. Merry" wrote: > eh? The card won't write past the point that has been acked by the kernel. > If the kernel hasn't acked the packets and one of the receive rings fills > up, the card will hold off on sending packets up to the kernel. Uh, eh? You mean the card will hold off on DMA and

EE locale MFC from current ?

Hi Is there a possibility that Estonian locale be MFC'd from current ? TIA Lauri To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ACPI: Can't power off dual AthlonXP1500 & TigerMP

Hello, world. Recent -current can power off via ACPI, such dual celeron/667 & ECS D6VAA(VIA AppoloPro133A). Both "shutdown -p" and pushing power SW work fine. But my dual AthlonXP1500 & TYAN TigerMP can NOT power off by any way: "shutdown -p" or pushing power SW or keep pushing power SW 10 s

NFS: unable to lock and fopen

Hello world, again. I can NOT "inc" my mail. NFS(v3) & mail server is FreeBSD2.2.8 . NFS client is FreeBSD5-current . MH is ja-mh-6.8.4.j3.03 installed from package. On the 5-current client, I can read my mail by mail(1). But I can NOT "inc". Such as: % inc +inbox ...(many minutes)... inc:

Re: NFS: unable to lock and fopen

Le 2001-10-10, NAKAMURA Kazushi écrivait : > % inc +inbox > ...(many minutes)... > inc: unable to lock and fopen /var/mail/kaz I have been having problems with NFS client locking on -CURRENT for some time, cf. PR bin/27231. Thomas. -- Thomas Quinot ** Département Informatique & Réseaux ** [EM

Re: amd not loading nfsclient.ko in -current of 9/26

Le 2001-09-28, Georg-W. Koltermann écrivait : > after upgrading my current a few days ago I find that amd does not > work any more: > > Sep 28 09:47:19 hunter amd[309]: /net: mount: No such file or directory > Sep 28 09:47:19 hunter amd[309]: extra mkdirs required for /net > Sep 28 0

Undefined symbol "__stderrp" ?

After cvsupping and makeing world and kernel this afternoon, when launching a binary linked against libc.so.4 and libm.so.2, I get /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol "__stderrp". Binaries linked against libc.so.5 and libm.so.2 work just fine (the symbol is defined in li

Re: Undefined symbol "__stderrp" ?

Ooops. This was discussed here recently. That's what I get for not reading -CURRENT when on holidays *and* not grepping enough of the backlog. Sorry. -- Thomas Quinot ** Département Informatique & Réseaux ** [EMAIL PROTECTED] ENST // 46 rue Barrault // 75634 PARIS CEDEX 13

Re: kldxref broken, maybe?

On Wed, Oct 10, 2001 at 11:09:30AM -0700, Mark Peek wrote: > At 9:29 AM -0700 10/10/01, Bruce A. Mah wrote: > >OK, sounds good. Seems to me this is something that might deserve a > >mention in UPDATING. Something like: > > > > During a source upgrade of a 4-STABLE machine to -CURRENT, the >

Re: kldxref broken, maybe?

In message <[EMAIL PROTECTED]> "Crist J. Clark" writes: : I think just running 'installworld' twice will "fix" it. The error is : non-fatal, but not without implications. The only one that I am aware : of is that your system might have some trouble doing kldload(8) unless : it is given the full pa

Re: kldxref broken, maybe?

Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Crist J. Clark" writes: > : I think just running 'installworld' twice will "fix" it. The error is > : non-fatal, but not without implications. The only one that I am aware > : of is that your system might have some trouble doing kldload(8) unles

Re: kldxref broken, maybe?

At 4:04 PM -0700 10/10/01, Peter Wemm wrote: >Warner Losh wrote: >> In message <[EMAIL PROTECTED]> "Crist J. >>Clark" writes: >> : I think just running 'installworld' twice will "fix" it. The error is >> : non-fatal, but not without implications. The only one that I am aware >> : of is that y

Re: kldxref broken, maybe?

On Wed, Oct 10, 2001 at 03:52:43PM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Crist J. Clark" writes: > : I think just running 'installworld' twice will "fix" it. The error is > : non-fatal, but not without implications. The only one that I am aware > : of is that your system migh

Approach to integrate a driver into the kernel [winmodem]

Hi All, I've now been using the FreeBSD winmodem driver (Available at: http://www.geocities.com/wtnbkysh/) under -current for a few weeks now and haven't noticed a single glitch. Whilst I know this is a port of a linux drivers and contains a binary only object from Lucent. Is there any ch

Re: Approach to integrate a driver into the kernel [winmodem]

On Thu, 11 Oct 2001, Benjamin Close wrote: >Hi All, > I've now been using the FreeBSD winmodem driver (Available at: >http://www.geocities.com/wtnbkysh/) under -current for a few weeks now >and haven't noticed a single glitch. Whilst I know this is a port of a >linux drivers and contains a

Re: Why do soft interrupt coelescing?

On Wed, Oct 10, 2001 at 01:59:48 -0700, Terry Lambert wrote: > "Kenneth D. Merry" wrote: > > eh? The card won't write past the point that has been acked by the kernel. > > If the kernel hasn't acked the packets and one of the receive rings fills > > up, the card will hold off on sending packets u

Re: Approach to integrate a driver into the kernel [winmodem]

On 11-Oct-2001 Brandon D. Valentine wrote: > If the license on the kernel module is incompatible with the base > system, you might be able to get the hooks to support it committed to > FreeBSD and get the kernel modules made installable as a port. > /usr/local/modules anyone? =) I would _re

Re: kldxref broken, maybe?

On Wed, Oct 10, 2001 at 06:25:48PM +1000, Bruce Evans wrote: > On Wed, 10 Oct 2001, Ruslan Ermilov wrote: > > > I do make -CURRENT worlds every night on a -STABLE box, and the > > kldxref(8) miss is non-fatal: > > ... > > ===> wi > > install -c -o root -g wheel -m 555 if_wi.ko /CURRENT/boot/ker

Re: kldxref broken, maybe?

If memory serves me right, Ruslan Ermilov wrote: > On Wed, Oct 10, 2001 at 06:25:48PM +1000, Bruce Evans wrote: > > On Wed, 10 Oct 2001, Ruslan Ermilov wrote: > > > > > I do make -CURRENT worlds every night on a -STABLE box, and the > > > kldxref(8) miss is non-fatal: > > > ... > > > ===> wi > >

Re: kldxref broken, maybe?

At 9:29 AM -0700 10/10/01, Bruce A. Mah wrote: >OK, sounds good. Seems to me this is something that might deserve a >mention in UPDATING. Something like: > > During a source upgrade of a 4-STABLE machine to -CURRENT, the > installkernel step will attempt to execute a non-existent kld