Re: Way forward with BIND 8

On Sat, 7 Jun 2003, Brad Knowles wrote: This is a rather different statement than you previously gave. I've been extremely consistent in saying that I'm talking about the right thing to do _now_. I purposely tried to avoid confusing the issue with detailed plans for the future, however

Re: Can't build -CURRENT on 4.7

On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this is not

Re: Can't build -CURRENT on 4.7

On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support

LOR: dev/sound/isa/mss.c and dev/sound/pcm/channel.c

I was trying to get core or some sort of trace for what I think are kse related, but I get this instead. Randomly after this during various operations, my system totally locks up (I don't know enough, whether it's related or not). lock order reversal 1st 0xc40bb540 pcm0 (sound softc) @

Re: Can't build -CURRENT on 4.7

On Sat, Jun 07, 2003 at 12:08:31AM -0700, Kris Kennaway wrote: On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT

Re: Can't build -CURRENT on 4.7

On Sat, Jun 07, 2003 at 01:07:24AM -0700, David O'Brien wrote: I carefully worded the reply to specifically address build 5-CURRENT on 4.7. Can you try src/share/mk/bsd.sys.mk rev 1.29 to see if it fixes your problem? Have you tested it thoroughly? Didn't you back out -std=c99 in a previous

Virus Removal Notification

On 6/7/2003 the OWLS, Inc. mail server processed a message from your address that contained the W32/Sobig-C virus. The message was sent to [EMAIL PROTECTED] The OWLS, Inc. mail server removed the virus and notified the recipient. The message, without the detected virus attachments, is attached

dhclient script in rc.d doesn't use ${dhcp_program} (conf/53007)

Hi folks- I'm happily using 5.1 and it's terrific. Keep up the great work. I just submitted a PR for a bug I noticed in the dhclient script. Namely, it ignores the setting of dhcp_program from rc.conf. A one-line fix did the trick for me, although there may be ramifications I'm not aware

Re: imgact_gzip.c

In message [EMAIL PROTECTED], David Yeske wr ites: imgact_gzip.c seems to be pretty stale. Has anyone considered fixing this? If this were fixed then kldload() / linker_load_module() could deal with a gzipped .ko file, and gzipped elf executables would work also? At least originally

Re: geom_vol_ffs problems

In message [EMAIL PROTECTED], Per Kristian Hove writes: plan to growfs it later, and your fstab contains /dev/vol entries) the obvious thing would be to check the parent GEOM and check that the partition we're tasting is of type FS_BSDFFS. That would eliminate the c-partition problem. This does

Re: dhclient script in rc.d doesn't use ${dhcp_program}(conf/53007)

On Sat, 7 Jun 2003 03:18:18 -0600 John Nielsen [EMAIL PROTECTED] wrote: I just submitted a PR for a bug I noticed in the dhclient script. Namely, it ignores the setting of dhcp_program from rc.conf. A one-line fix did the trick for me, although there may be ramifications I'm not aware of.

rcNG automonter(amd)

hi, I have a problem with /etc/rc.d/amd, because of the line command_args= ${amd_program} gets run in the background, ldconfig failes to cache libraries in /usr/local/lib (which is automounted :-) Is there realy a need for the ? amd will background itself after it's done with the

Re: [PATCH] Tweak re-routing of PCI interrupts

On 6/6/2003 9:29 PM, Bernd Walter wrote: On Fri, Jun 06, 2003 at 01:17:43PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Bernd Walter [EMAIL PROTECTED] writes: : I already wondered how you could route interrupts without ACPI until I : booted my printserver with a

Re: kern/53010: FreeBSD-CURRENT cannot use 2940 UW on SNI Pro C6(Pentium Pro System)

John's tweak patch for re-routing of PCI interrupts seems to work. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: geom_vol_ffs problems

[Poul-Henning Kamp, 2003-06-07] | This does not work for FFS filesystems stored in apple or sun partitions, | but theese do on the other hand, not have the magic 'c' problem. (I know it wouldn't work for FFS filesystems in non-BSD partitions, which must be supported. It was not my

Re: rcNG automonter(amd)

On Sat, 07 Jun 2003 13:13:15 +0300 Danny Braniss [EMAIL PROTECTED] wrote: hi, I have a problem with /etc/rc.d/amd, because of the line command_args= ${amd_program} gets run in the background, ldconfig failes to cache libraries in /usr/local/lib (which is automounted :-) Is

Re: Can't build -CURRENT on 4.7

On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support

Re: [PATCH] Tweak re-routing of PCI interrupts

In message: [EMAIL PROTECTED] Jens Rehsack [EMAIL PROTECTED] writes: : On 6/6/2003 9:29 PM, Bernd Walter wrote: : On Fri, Jun 06, 2003 at 01:17:43PM -0600, M. Warner Losh wrote: : In message: [EMAIL PROTECTED] : Bernd Walter [EMAIL PROTECTED] writes: : : I already

Re: Can't build -CURRENT on 4.7

In message: [EMAIL PROTECTED] Ruslan Ermilov [EMAIL PROTECTED] writes: : On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: : On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: : The compiler in 4.7 does not like this: : : -std=gnu99 : : As a

Re: rcNG automonter(amd)

This may have been because of a missed merge from rcOG. How does the following work for you? Cheers. it will fix my problem, but in an 'obscure way', just have to remember to set amd_flags my point is that amd should not be backgrounded by default, it does so anyway once it managed to

Re: rcNG automonter(amd)

On Sat, 07 Jun 2003 15:48:47 +0300 Danny Braniss [EMAIL PROTECTED] wrote: context I have a problem with /etc/rc.d/amd, because of the line command_args= [amd] gets run in the background, ldconfig failes to cache libraries in /usr/local/lib (which is automounted :-) /context my

Re: [PATCH] Tweak re-routing of PCI interrupts

On Sat, Jun 07, 2003 at 01:08:12PM +0200, Jens Rehsack wrote: dmesg of machine which now runs with the fix: npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 pcib0: Host to PCI bridge at pcibus 0 on motherboard Same situtation with my Board - no $PIR

How to kill a 5.0R installation with 5.1R

Folks, This is the second time that I have this happen here. I had a 5.0R installed on a box. After upgrading, (make world make kernel) the box crashes instantly in the boot loader and reboots itself. If I try to load the kernel manually, I get: Disk error 0x4, (lba=0xfc2247f) There should

Re: How to kill a 5.0R installation with 5.1R

On Sat, Jun 07, 2003 at 03:45:56PM +0200, Martin Blapp wrote: Folks, This is the second time that I have this happen here. I had a 5.0R installed on a box. After upgrading, (make world make kernel) the box crashes instantly in the boot loader and reboots itself. How does it crash? If

Re: How to kill a 5.0R installation with 5.1R

Hi, This has been one of my laptops. It had three partitions on it, the first one FreeBSD. How does it crash? I have lilo installed. When I choose freebsd, I get the normal freebsd loader: FreeBSD/i386 BOOT After that, I see very fast a message scrolling over the screen, it turns black

Re: How to kill a 5.0R installation with 5.1R

On Sat, Jun 07, 2003 at 03:45:56PM +0200, Martin Blapp wrote: Folks, This is the second time that I have this happen here. I had a 5.0R installed on a box. After upgrading, (make world make kernel) the box crashes instantly in the boot loader and reboots itself. Have you tried

Re: How to kill a 5.0R installation with 5.1R

Hi, Have you tried loader.old? I personally also keep a loader.work copy on my systems - just in case. Whooo. Yes, loader.old did the trick. Wow :-) Thanky you very much ! I'm just curious now why the new loader instantly panics. Martin ___ [EMAIL

Re: How to kill a 5.0R installation with 5.1R

On Sat, Jun 07, 2003 at 04:00:46PM +0200, Martin Blapp wrote: Hi, This has been one of my laptops. It had three partitions on it, the first one FreeBSD. How does it crash? I have lilo installed. When I choose freebsd, I get the normal freebsd loader: FreeBSD/i386 BOOT After

Re: How to kill a 5.0R installation with 5.1R

Hi, over the screen, it turns black again, and voila, the box has rebooted. I've killed the second box the same way. After restoring boot0/boot1 I found that my disklables were nuked. Enjoy. Um, so what do you use? lilo or boot0? :-) Lilo. And the first box I killed with just a

Audigy Support?

Hello all. I've been using the OSS drivers for my Audigy Gamer sound card for quite some time now, and would like to switch away from OSS. I vaguely remember, after searching Google, that someone had gotten this to work after a recent cvsup. Unfortunately, I cannot seem to get this to work

Re: Can't build -CURRENT on 4.7

David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this

Re: Can't build -CURRENT on 4.7

On Sat, Jun 07, 2003 at 06:30:11AM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Ruslan Ermilov [EMAIL PROTECTED] writes: : On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: : On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: : The compiler

Re: Can't build -CURRENT on 4.7

In message: [EMAIL PROTECTED] David O'Brien [EMAIL PROTECTED] writes: : First off, I'd like to say that's my understanding as well. : : That was not my understanding at all. The last time it came it, it was specifically stated that it was until the branch point. But so far the work

Re: rcNG automonter(amd)

On Sat, Jun 07, 2003 at 09:04:46AM -0400, Mike Makonnen wrote: On Sat, 07 Jun 2003 15:48:47 +0300 Danny Braniss [EMAIL PROTECTED] wrote: context I have a problem with /etc/rc.d/amd, because of the line command_args= [amd] gets run in the background, ldconfig failes to cache

FreeBSD 5.1-RELEASE (cvs) problems..

Hello there. Just installed FreeBSD 5.1-BETA from a ISO, then upgrade to 5.1-RELEASE via CVS (RELENG_5_1). Looks like there are alot of problems with ACPI and the floppy disk controller on this mainboard. It's a Abit BP6 Dual-CPU mainboard with two Celeron 400MHz CPU's running on it. I have a

Re: Can't build -CURRENT on 4.7

On Sat, Jun 07, 2003 at 10:38:15AM -0700, Tim Kientzle wrote: Index: usr.bin/xlint/lint1/cgram.y === RCS file: /usr/src/cvs/src/usr.bin/xlint/lint1/cgram.y,v retrieving revision 1.7 diff -u -r1.7 cgram.y ---

Re: Can't build -CURRENT on 4.7

On Sat, Jun 07, 2003 at 10:38:15AM -0700, Tim Kientzle wrote: Index: Makefile.inc1 === RCS file: /usr/src/cvs/src/Makefile.inc1,v retrieving revision 1.363 diff -u -r1.363 Makefile.inc1 --- Makefile.inc1 31 May 2003 21:29:38

[-CURRENT tinderbox] failure on i386/i386

TB --- 2003-06-07 17:28:52 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-06-07 17:28:52 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-06-07 17:31:51 - building world TB --- cd

Re: [-CURRENT tinderbox] failure on i386/i386

In message [EMAIL PROTECTED], Tinderbox wri tes: /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/geom/geom_dev.c /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/sys/geom/geom_dev.c:81: conflicting types for `g_dev_print'

Re: Audigy Support?

There seems to be a patch floating around. I saw it at bsdforums.org - see http://www.bsdforums.org/forums/showthread.php?s=threadid=6961 . It's created by Orlando Bassotto. I don't know if is yet included in the FreeBSD source, or why it is not. Best regards, Arjan On Saturday 07 June 2003

Re: Can't build -CURRENT on 4.7

In message: [EMAIL PROTECTED] David O'Brien [EMAIL PROTECTED] writes: : + WORLDTMP=${WORLDTMP} CSTD= \ : : may. This seems to mostly work... I'm trying to sort out a couple of other issues, but those may be related to other changes that I've made in my test tree. Warner

Regression: Playing QT files from mplayer stopped working in 5.1

Hi, Since a short time (don't know exactly when it happened) it's not possible anymore to play Quicktime files (.mov) with mplayer on 5.1-CURRENT. It has to be a change in -CURRENT, I haven't updated mplayer. When trying to play a QT file, mplayer outputs: win32 libquicktime loader (c) Sascha

Re: Way forward with BIND 8

Fri, Jun 06, 2003 at 03:01:02, DougB wrote about Re: Way forward with BIND 8: FYI, for those wondering why I'm not considering BIND 9 for import, please see http://people.freebsd.org/~dougb/whybind8.html Among other things: standard resolver is waaay(tm) old. Even keeping with BIND8, it

Re: Regression: Playing QT files from mplayer stopped working in 5.1

On Sat, 7 Jun 2003 22:28:29 +0200, Arjan van Leeuwen [EMAIL PROTECTED] wrote: Hi, Since a short time (don't know exactly when it happened) it's not possible anymore to play Quicktime files (.mov) with mplayer on 5.1- CURRENT. It has to be a change in -CURRENT, I haven't updated mplayer. When

Re: Audigy Support?

On Sat, Jun 07, 2003 at 01:19:42PM -0400, John Wilson wrote: I've been using the OSS drivers for my Audigy Gamer sound card for quite some time now, and would like to switch away from OSS. I vaguely remember, after searching Google, that someone had gotten this to work after a recent cvsup.

Old Courier MTA , broken

Hi, courier in ports is 0.39 when current courier is 0.40.2 afaik. Additionaly it wont build without editing the Makefile and taking out the brake. Any idea when current courier will be implemented ? thx alot -- Christophe Zwecker mail: [EMAIL PROTECTED] Hamburg, Germany

[-CURRENT tinderbox] failure on sparc64/sparc64

TB --- 2003-06-07 21:10:21 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-06-07 21:10:21 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-06-07 21:12:45 - building world TB

Re: Can't build -CURRENT on 4.7

David O'Brien wrote: This won't work on non-i386, due to alloca issues. + WORLDTMP=${WORLDTMP} CSTD= \ may. Hmmm... This seems like the Right Thing in any case, since it is one less assumption you're making about the build environment. I'm still getting buildworld failures, though. Long

Re: 5.1-BETA em

There... http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/52835 Pete - Original Message - From: Robert Watson [EMAIL PROTECTED] To: Petri Helenius [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, May 15, 2003 9:54 PM Subject: Re: 5.1-BETA em Could you file a

installworld failure

% make installworld === gnu/usr.bin/binutils === gnu/usr.bin/binutils/libiberty === gnu/usr.bin/binutils/libbfd === gnu/usr.bin/binutils/libopcodes === gnu/usr.bin/binutils/libbinutils === gnu/usr.bin/binutils/addr2line install -s -o root -g wheel -m 555 addr2line /usr/bin install:

4.8 - 5.0-CURRENT build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I'm attempting to do a 'make buildworld' for FreeeBSD 5.0-CURRENT on a FreeBSD 4.8 box # uname -a FreeBSD 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I receive

ULE SMP panics fixed.

I found the culprit. It was an off by one error. rev 1.35 has the fix. Thanks, Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 4.8 - 5.0-CURRENT build error

In message: [EMAIL PROTECTED] Evan S. [EMAIL PROTECTED] writes: : # make : building shared library libkse.so.1 : thr_libc.So: In function `sigaction': : thr_libc.So(.text+0x54): multiple definition of `_sigaction' : thr_sigaction.So(.text+0x0): first defined here : thr_libc.So: In

p5-GD-1.41 wont build

Hi, when trying to build above I get this: AutoSplitting blib/lib/GD.pm (blib/lib/auto/GD) /usr/local/bin/perl5.6.1 -I/usr/local/lib/perl5/5.6.1/mach -I/usr/local/lib/perl5/5.6.1/BSDPAN /usr/local/lib/perl5/5.6.1/ExtUtils/xsubpp -typemap /usr/local/lib/perl5/5.6.1/ExtUtils/typemap -typemap

sendmail starts before rpc.statd and rpc.lockd

Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. NFS access cache time=2 Starting statd. Starting lockd. It looks like sendmail starts before rpc.lockd and rpc.statd? This will cause diskless clients to

Re: sendmail starts before rpc.statd and rpc.lockd

Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. NFS access cache time=2 Starting statd. Starting lockd. I should clarify that /etc/rc.d/virecover is calling sendmail. Does virecover need to be called this