-CURRENT `make world` fails.. (ucontext.h?)
Hi, On a fresh cvsup of the -CURRENT sources, I've been trying to do a `make world`. I've gotten all the way through (past signal 12 errors, which were fixed by reading the -CURRENT archives and recompiling an up-to-date kernel) to the boot loader. Since the errors are on another box (which is in singleuser mode), I can't produce the exact log, however, I'll do my best copying it off its screen 10 feet from here..: == sys/boot/i386/libi386 cc -O -pipe -I/usr/src/sys/boot/i386/libi386 [...] In file from ... from ... from/usr/src/sys/boot/i386/libi386/aout_freebsd.c:29: /usr/src/sys/boot/i386/libi386/../../../sys/ucontext.h:34: machine/ucontext.h: No such file or directory. [...] *** Error code 1 --- I've looked around the src for a machine/ucontext.h. The particular including file, /usr/src/sys/sys/ucontext.h includes machine/ucontext.h, so if it's looking at /usr/include/machine/ucontext.h, that's not there.. is this the correct file to be #include'ing? Is there any additional information I can provide (I noticed a related thread, but DCS's reply didn't seem to help..)? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcic.ko recent changes to sys/pccard/*
Hi, I'm running FreeBSD 4.0-CURRENT on my laptop, a Dell Inspiron 7000. I successfully got my 3Com Megahertz 3C574B Ethernet PC-Card to work under 4.0-CURRENT (sources as of September 29, 1999 @ 10AM EDT, before marcel's infamous signal.h commits). CVSup'ing recently and finally successfully remaking world, I find that the sys/pccard/* has changed somewhat. Looking through the cvsweb changes, I see Warner's message about changing the PCMCIA support lines in the kernel configfile, so I did that. (see cvs log messages for src/sys/pccard/pccard.c,v 1.89) But it doesn't work. I'm assuming that my kernel config file's settings do not affect make world in any way, and thus it seems that pcic.ko is not being built by make world anymore... Thus, /dev/card0 is reported as "Device not configured" upon boot (because kldload can't find pcic.ko in /modules or elsewhere). What's going on here? Is the Makefile in src/sys/modules/pcic borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem likely, as the last time it was changed was for the $Id$ - $FreeBSD$ change, which of course was mostly propagated by Peter Wemm. And it wasn't relevant to pcic anyway. So where is it breaking? It's either breaking in a Makefile I missed somewhere, or the pcic code is broken, or I'm broken (being egotistical, I doubt it ;). --Will Andrews [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcic.ko recent changes to sys/pccard/*
On 18-Oct-99 Warner Losh wrote: In message [EMAIL PROTECTED] Will Andrews writes: : But it doesn't work. I'm assuming that my kernel : config file's settings do not affect make world in any way, : and thus it seems that pcic.ko is not being built by make world : anymore... What doesn't work? Can you give some error messages as well as a complete dmesg? I could give you a complete dmesg and error messages.. but I'll have to read them off argon (the laptop sitting next to me), since argon's only Internet connection _was_ through that PC-Card Ethernet card. :-) Let me try...: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Oct 18 03:13:00 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ARGON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT, PSE36,MMX,FXSR real memory = 134217728 (131072K bytes) avail memory = 127410176 (124424K bytes) Preloaded elf kernel "kernel" at 0xc028b000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028b09c. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus) on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: ATI model 4c42 graphics accelerator irq 11 at device 0.0 on pci1 pcic0: TI PCI-1220 PCI-CardBus Bridge at device 4.0 on pci0 pcic1: TI PCI-1220 PCI-CardBus Bridge at device 4.1 on pci0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 devclass_alloc_unit: pcic0 already exists, using next available unit number devclass_alloc_unit: pcic1 already exists, using next available unit number isa0: ISA bus on isab0 ide_pci0: Intel PIIX4 Bus-master IDE controller at device 7.1 on pci0 chip1: UHCI USB controller irq 11 at device 7.2 on pci0 chip2: Intel 82371AB Power management controller at device 7.3 on pci0 pci0: unknown card (vendor=0x125d, dev=0x1968) at 8.0 irq 5 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): IBM-DADA-26480 wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) on COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: PLIP network interface on ppbus 0 pccard: initializing drivers: ep changing root device to wd0s2a --- Here's /usr/src/sys/i386/conf/ARGON: # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.192 1999/09/22 05:07:49 wpaul Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident ARGON maxusers100 makeoptions DEBUG=-g options INET options FFS options FFS_ROOT options MSDOSFS options CD9660 options CD9660_ROOT options PROCFS options COMPAT_43 options SCSI_DELAY=15000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options SOFTUPDATES options NO_F00F_HACK options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options IDE_DELAY=8000 device pcm0 controller isa0 controller pnp0 controller pci0 controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 controller wdc0at isa? port IO_WD1 irq 14 diskwd0 at wdc0 drive 0 diskwd1 at wdc0 drive 1 device wcd0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts device sc0 at isa? options XSERVER device npx0at nexus? port IO_NPX irq 13 device apm0at nexus? disable flags 0x31 controller pcic0 at isa? controller pcic1 at isa? controller card0 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device ppc0at isa? port? flags 0x40 irq 7 controller ppbu
Re: -CURRENT `make world` fails.. (ucontext.h?)
On 18-Oct-99 Daniel C. Sobral wrote: I'm tracking this now. Well, I'll start tracking as soon as I finish my mail. I suggested first upgrading to 3.3 (or even 3.2), and only then to current. That _will_ work, as it will upgrade the loader. Alas, you need not even go to such pains. Just cvsup to -stable, cd /sys/boot; make depend make all install, and then cvsup to -current, make the kernel, etc, etc. Yes, that's how I did it. Actually, I had 3.3-RELEASE.. I downloaded the entire -CURRENT CVS repository so I could get sources for September 29, before marcel's changes. Then I burned those sources to a CD-R, and loaded it on my laptop. Made world, rebooted, and I'm in 4.0-CURRENT. Then after several unsuccessful attempts to do a newer world, I finally got it. argon.blackdawn.com (my laptop) is _NOW_ running 4.0-CURRENT as of October 17, 1999 @ 9PM EDT. Only one problem is left - my pccard isn't working. I'm working with Warner Losh on that... (hopefully something good will come out of that.) The person who first reported the problem said he succesfully used the loader from a recent snap. That will work. Go to a near FreeBSD ftp site, get the "loader" binary from a snapshot, copy it to /boot, and that will be able to load a -current kernel. Interesting. All I did was rebuild the kernel again and tried another make world. For some reason, the system wanted me to build the same kernel twice. Or maybe I cvsup'd more than once, and didn't build a new kernel the second or third time. I don't know. :) I didn't try a bootloader off the ftp sites.. that wouldn't have worked for me anyway, since pccard support broke around the time I got to the bootloader in `make world`. I mean, it broke 'cause I lost my old Sept. 29 kernel. I forgot to keep a backup copy of it.. :\ As for the problem it goes like this: FreeBSD 3.1's loader was not capable of loading a kernel at a different base address than the one FreeBSD used up to that point. Unfortunately, this resulted in an annoying bug that affected machines with lots of RAM and big maxusers (like, for instance, 256). This was corrected by moving the base address of kernel, which required modifications to loader. Thus, FreeBSD's 3.1 loader is not capable of booting a current kernel. Perhaps people need to install a new boot loader first (one that is of 4.0-CURRENT lineage), as you suggested. Then perhaps building a -CURRENT kernel, and rebooting. Of course, I dunno if that'd work, given the differing kernel and world.. Now, aout_freebsd.c (and possibly other files) in sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes sys/signal.h. The later requires machine/ucontext.h, which is not present. Why the newer signal.h is found but not ucontext.h, I'll find out shortly (I hope :). For now, I'm working with the hypothesis of a "file.h" instead of file.h #include. Yes, I thought the machine/ucontext.h was the problem. Is "machine/ucontext.h" under /usr/src somewhere? I thought I saw one, but couldn't seem to finger its precise path. All things considered, this isn't much of a problem in itself. There is a huge problem here,though. Generally speaking, loader is immune to world troubles, since it uses libstand. But, are we not risking chicken-and-egg problems such as this by including standard sys/*.h? Situations where newer loaders are needed to boot a new kernel (as much as we would like loader to be able to handle all future kernels), but not being able to build them until a newer kernel is booted? Like I said above, a -CURRENT kernel may have problems with a -STABLE world. I'm honestly not fully aware of the dependencies regarding the signal changes (i.e., ucontext.h), so my thoughts may be completely wrong. :-) Comments? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcic.ko recent changes to sys/pccard/*
On 18-Oct-99 David O'Brien wrote: On Mon, Oct 18, 1999 at 12:25:48PM -0400, Will Andrews wrote: If you don't believe me when I say that pcic _was_ working for the Sept. 29 sources: The pcic modules is *KNOWN* to have and cause problems. Warner told you this and you still insist on pushing the issue. Why? NO FreeBSD developer uses the pcic *module*, thus it is quite unwise for you to be using it as we no longer test it or keep it in sync with the rest of the kernel. No, no... see below. : What's going on here? Is the Makefile in src/sys/modules/pcic : borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem : likely, as the last time it was changed was for the $Id$ - The building of modules/pcic was removed from /sys/modules/Makefile. Check the history on that file. The pcic module is borked and hasn't worked for a long time. Actually, it worked for me in my last world - September 29, 1999 @ 10AM EDT. STOP USING IT!!! I disabled it in -STABLE and -CURRENT quite some time ago. How is it you are even compiling and installing it? Please statically compile it into your kernel so developer's time isn't wasted on this. We have known problems for PCIMCA modems and that is where the pccard developer's time needs to be spent. I apologize for causing undue freaking-out... I am confused. :) First things first. After this message, I'm going to read the -current archives regarding pccard. Second, it should be noted that I don't see how I could ever have used the pcic module.. if you disabled it before September 29, then it must have been kernel support. My old logs show no indication that any module was loaded before, so if the 9/29 kernel worked, why doesn't the current kernel work with my pccard? I made the appropriate changes that Warner mentioned in the cvs logs for src/sys/pccard/pccard.c, v1.89, as I said before. Third, part of my confusion is due to /etc/rc.pccard, which seems to attempt to load the module. Since I received no errors before (in the 9/29 world/kernel) about kldload failing, it seems like there WAS indeed a pcic.ko module (because now, since there is no module, kldload gives an error on booting up: "can't find module pcic".) I would never use any deprecated software. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: sio working
On 23-Oct-99 Warner Losh wrote: OK. I managed to get sio and ep working on the plane back from FreeBSDCon'99. There are some problems with card eject at the moment, but will be committing things to the tree shortly. I will be your guinea pig, if you like. :-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio working
On 23-Oct-99 Warner Losh wrote: In message [EMAIL PROTECTED] Will Andrews writes: : I will be your guinea pig, if you like. :-) Grab the current patches from http://www.freebsd.org/~imp/pccard-snap.patch but read my other posting about the warnings and such. As of yet, I haven't tested your code. I will be, in a few. I took the opportunity to go over the patch first. I noticed a little discrepancy in ep_pccard_identify, where the switch() does not offer a default: case. You should put something like that in there and call the card "Unknown 3Com card" or somesuch. Same for ep_pccard_card_attach(). That's all I can manage from a quick skim of your code. Well, I'm gonna test out this kernel patch. (after safely backing up sys/). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/etc pccard.conf.sample
At 09:53 PM 10/25/99 -0700, you wrote: kuriyama1999/10/25 21:53:29 PDT Modified files:(Branch: RELENG_3) etc pccard.conf.sample Log: MFC: Add Allied Telesis CentreCOM LA-PCM_V2 entry. Here's another (works only under 4.0-CURRENT, as this particular PC-Card is a CardBus): # 3Com Megahertz 3C574B (3CCFE574BT) card "3Com" "Megahertz 574B" config 0x1 "ep0" 10 0x1 insert /etc/pccard_ether ep0 insert 3Com Megahertz 574B card inserted remove /sbin/ifconfig delete ep0 remove 3Com Megahertz 574B card removed I originally was unable to get this card working - it required IRQ 10, so I had to change the "?" to "10" (my entry was copied from another 3Com card, don't remember which). Note: This hasn't been tested with Warner's new pcic code. I'll be doing that this weekend. :-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/etc pccard.conf.sample
At 01:46 AM 10/27/99 -0700, you wrote: Are you *SURE* this is CardBus? AFAIK, we don't yet (at least pre-Warner's new pcic code) support CardBus. Hrmm.. I could have sworn it was a CardBus card: http://www.3com.com/client/mcd/products/3ccfe574btsp.html Perhaps I was just seeing things, sorry. I have friends who happen to have Xircom multifunc cards (which _are_ CardBus) - would you guys like me to try and test them? I can get them long enough to test them out with the newconfig functionality. In retrospect.. I probably confused their cards with mine. :-) # 3Com Megahertz 3C574B (3CCFE574BT) Isn't this just a rebadged (and slightly tweaked) 3Com 3c574tx? Most likely. Their pccard.conf configurations are very similar. Jun, `pccardc dumpcis` output for you at: http://stimpy.multiweb.net/~dragon/3CCFE574BT.txt I have sup'd my sources and will be remaking world kernel tonight, I will let you know what happens... -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current build fails
On 30-Oct-99 Vincent Poy wrote: Hmmm, I can understand the build/install portion but will it boot since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE. I highly advise that you read the last month's archive of the -current mailing list archives: http://docs.FreeBSD.ORG/mail/archive/1999/freebsd-current/. Read ALL the messages. Oh, and update your -CURRENT. A -CURRENT machine with sources from March 1999 indicates you're not running a machine in sync with the purpose of -CURRENT. Use -STABLE instead. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: laptop problems
At 04:25 PM 11/1/99 -0700, you wrote: What's your eeporm problem? I have fixed and committed patches to the ep driver where the card wasn't being identified. I thought I sent you something about this before.. My card IS getting recognized, and seems to be on the appropriate port, BUT, I think memory pointers are getting mixed up, because it's returning the _WRONG_ MAC address. Plus, 'pccard0' is being used even though it's not in the kernel currently loaded. Here's the kernel output (that I found erroneous): pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 Here's the pccardd output: ep0: 3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX at port 0x240-0x25f irq 10 slot 0 on pccard0 ep0: Ethernet address 4b:57:4b:57:4b:57 ep0: strange connector type in EEPROM, assuming AUI Yes, I have a 3Com 3CCFE574BT that has worked with -CURRENT before. And yes, the kernel sources (at least relevant to pccard) is up to date, including your EEPROM an pcic_p.c (or whatever) fixes. The devclass_alloc_unit() problem was fixed by the pcic_p.c fix, but EEPROM problems lurk. :\ Me too. I'll know when I get home tonight. Well? *cross fingers* :) --- It's been a few days since I wrote this reply. I've been hacking /sys/dev/ep/if_ep.c, trying to figure out what's wrong. I originally thought the ep_get_macaddr() function's for() loop was erroneous in that it uses an integer `i' in the for loop instead of a u_int_16. That theory didn't go (still got the wrong MAC addresses.. something's not right.), however, I did find out that the polling thing was caused by pcic's IRQ not being assigned properly. I hardwared the pcic_irq = 11; in my /sys/pccard/pcic.c, and that removed the error. So, somebody borked pcic.c in this respect somewhere (haven't looked further yet), although this hardwire didn't fix the MAC address problem. Then I had a look at the odd EEPROM problem, which seems to have been caused by erroneous values in IFM_ETHER_10T, etc. I put in a debugging device_printf(), and found my ifm.ifmedia (whatever's in the switch() with a default: that outputs the error message above (it's in /sys/dev/ep/if_ep.c)) to equal 0. What the hell's wrong with this thing? IFM_ETHER_10T should be 0, judging by the array definition given. Perhaps you meant to use an enum? Anyway, I plugged in a case 0: to see if that fixed the problem, and it did. So, something's borked with that too. /me will check CVS logs tomorrow to see if in one place or another ep_get_macaddr(), etc. got borked somehow. Thoughts / Comments? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot problems with todays kernel
At 04:42 PM 11/4/99 -0800, you wrote: Seems to me like a simple problem: devclass_alloc_unit: npx0 already exists, using next available unit number device npx0at isa? port IO_NPX irq 13 Shouldn't this be "at nexus?" ? Like apm0 is. I'm not quite sure it was the problem that Mike Smith just fixed (vfs_conf.c, that is). Or was npx0's assignment changed in a recent commit? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot problems with todays kernel
[ CC:'d to mdodd, imp as it relates to their current work ] At 10:44 PM 11/4/99 -0800, you wrote: I'm now running into issues with pccard and the ep driver, where ep0 (3c574B) is seen at boot time, at a familiar port/irq, but with a bogus mac address.. (4b:57:4b:57:4b:57). ifconfig -a will immediately lock up the system, with a reboot following a minute or two later.. this only happens when there is a card inserted.. I have EXACTLY the same problems! Exactly the same PC-Card, exactly the same MAC address problem.. I even get that exact same MAC address - 4b:57:4b:57:4b:57! I've been looking over Matt Dodd's commit (-r1.91) to if_ep.c, and I think I may have figured out this problem. I'll need to do some testing first to see. I'll send a patch on Saturday if/when my fixes get the MAC address right. I suspect that if the fix gets the MAC address right, connectivity / kernel stability with if_ep will return. roadwarrior /kernel: pcic0: VLSI 82C146 at irq 10 on isa0 roadwarrior /kernel: pccard0: PC Card bus -- kludge version on pcic0 roadwarrior /kernel: pccard1: PC Card bus -- kludge version on pcic0 I believe I have the same PCIC controller. roadwarrior /kernel: pccard: card inserted, slot 0 roadwarrior pccardd[62]: Using I/O addr 0x240, size 32 roadwarrior pccardd[62]: Setting config reg at offs 0x1 to 0x41, Reset time = 50 ms roadwarrior lpd[144]: restarted roadwarrior pccardd[62]: Assigning I/O window 0, start 0x240, size 0x20 flags 0x7 roadwarrior pccardd[62]: Assign ep0, io 0x240-0x25f, mem 0x0, 0 bytes, irq 3, flags 0 roadwarrior /kernel: ep0: 3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX at port 0x240-0x25f irq 3 slot 0 on pccard0 roadwarrior /kernel: ep0: Ethernet address 4b:57:4b:57:4b:57 Hmm.. ep0 on IRQ 3? It should be on IRQ 10. At least, that's what has always worked for me on previous -CURRENT code. Otherwise I get the same last 2 messages. I note though that your PCIC is using IRQ 10. Normally, mine would use IRQ 11, and ep0 would use IRQ 10. roadwarrior /kernel: Fatal trap 12: page fault while in kernel mode roadwarrior /kernel: fault virtual address= 0x0 roadwarrior /kernel: fault code = supervisor read, page not present roadwarrior /kernel: instruction pointer = 0x8:0x0 roadwarrior /kernel: stack pointer= 0x10:0xc7523de4 roadwarrior /kernel: frame pointer= 0x10:0xc7523e08 roadwarrior /kernel: code segment = base 0x0, limit 0xf, type 0x1b roadwarrior /kernel: = DPL 0, pres 1, def32 1, gran 1 roadwarrior /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 roadwarrior /kernel: current process = 310 (ifconfig) roadwarrior /kernel: interrupt mask = net tty roadwarrior /kernel: trap number = 12 roadwarrior /kernel: panic: page fault roadwarrior /kernel: roadwarrior /kernel: syncing disks... 24 24 20 12 done roadwarrior /kernel: Automatic reboot in 15 seconds - press a key on the console to abort Yep - this happens to me when i do a `ifconfig ep0`. Ka-boom. roadwarrior /kernel: Mounting root from ufs:/dev/wd0s1a roadwarrior /kernel: pccard: card inserted, slot 0 roadwarrior pccardd[60]: Using I/O addr 0x240, size 32 roadwarrior pccardd[60]: Setting config reg at offs 0x1 to 0x41, Reset time = 50 ms roadwarrior lpd[144]: restarted roadwarrior pccardd[60]: Assigning I/O window 0, start 0x240, size 0x20 flags 0x7 roadwarrior pccardd[60]: Assign ep0, io 0x240-0x25f, mem 0x0, 0 bytes, irq 3, flags 0 Again, I don't like that IRQ. I'll get back to y'all on the MAC address issue. Good night. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: where to get -current pkgs?
On Thu, Oct 17, 2002 at 01:01:59PM -0500, David W. Chapman Jr. wrote: bento should have them but I dont' know how up to date it is. Bento is returning to 5-CURRENT builds in lieu of DP2 and hopefully 5.0-RELEASE, now that 4.7-RELEASE is out. I believe we will do 4-STABLE builds less frequently than 5-CURRENT for some time. In any case, the latest packages available publically are posted on the FTP mirrors, but also on bento (check the webpages). regards -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __sF
On Sat, Nov 02, 2002 at 10:10:31AM -0800, Steve Kargl wrote: This will break some commercially available software that can't easily replaced. kargl[248] f95 -V a.f90 NAGWare Fortran 95 compiler Release 4.2(468) Copyright 1990-2002 The Numerical Algorithms Group Ltd., Oxford, U.K. f95comp version is 4.2(468) /usr/local/lib/NAGWare/libf96.so: undefined reference to `__sF' collect2: ld returned 1 exit status I seriously doubt that NAG will support both a 4.x and 5.x version of their compiler. That's why we have compat libs. compat4x should handle this unless I'm mistaken. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openssh question
On Mon, Mar 06, 2000 at 11:23:45AM -0800, William Woods wrote: Now that openssh is in the base system, I assume it will no longer be in the ports. How do we update it, ie, when a updated version comes out. I would rather not make world just to update that. # cvsup standard-supfile (until 4.0 becomes -stable) # cd /usr/src/secure/usr.bin/ssh make clean depend all install Someone correct me if I'm wrong. :-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
On Wed, Mar 15, 2000 at 11:59:29AM -0600, Jeffrey J. Mountin wrote: However, if you consider the size of the file and the possibility of corruption, then it should be archived with gzip and forget the compression (gzip -1). Now it can be checked for errors. MD5 checksums are more compact and much cooler. Another issue is the size. Many factors determine how quickly one can obtain the ISO. It would be nice if it were broken into smaller volumes. About 10-20 MB each would be good. That way should something fail, there less time and bandwidth wasted should one need to start over. Ever heard of 'reget'? Call me a disinterested 3rd party. Never pull the ISO, only the parts needed. ;) I tend to agree with this. 650MB is way too much - perhaps the images could be broken up according to the portion of the system (i.e., bin, sbin, usr.bin, usr.sbin, etc, et cetera). -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
On Fri, Mar 17, 2000 at 10:00:44AM -0500, Kelly Yancey wrote: This is all beginning to smell a lot like a FTP install. Exactly. Only thing is, an FTP install requires a usable internet connection on intended box, which is not always available. ;-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslogd_flags in /etc/defaults/rc.conf
On Mon, Mar 20, 2000 at 09:45:49AM -0800, Nick Johnson wrote: I'm curious to see if anyone is like-minded with me that syslogd_flags in /etc/defaults/rc.conf should be "-ss" instead of "". I reasoned that it should be, considering: 1. Most people don't direct syslogs at other machines in my experience. 2. Someone could conceivably DOS a machine by directing tons of crap at port 121, which is also noted in the BUGS section of the syslogd manpage. 3. Syslogd runs as root, and while it is a mature piece of code, I think it preferable to minimize the number of root applications listening on sockets. This seems like a reasonable change. Thanks for pointing this out! :) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make world' fails
On Sun, Apr 02, 2000 at 01:39:15AM +0200, Patrick Mau wrote: Hi all, the subject says it all. It fails with the follwing messages: === libssh cd /usr/src/gnu/lib/libgcc; make depend; make all; make install echo '#include i386/xm-i386.h' config.h echo '#include "gansidecl.h"'tconfig.h echo '#include xm-freebsd.h' config.h echo '#include "i386/xm-i386.h"' tconfig.h echo '#include "i386/i386.h"'tm.h echo '#include "i386/att.h"' tm.h echo '#include freebsd.h' tm.h echo '#include "i386/freebsd.h"' tm.h echo '#include "i386/perform.h"' tm.h rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC -I/usr/obj/usr/src/i386/usr/include /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c mkdep -f .depend -a -nostdinc++ -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/inc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo2.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/new.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:33: gansidecl.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:34: eh-common.h: No such file or directory [root@oscar /usr/src] locate gansidecl.h /usr/src/contrib/gcc/gansidecl.h [root@oscar /usr/src] locate eh-common.h /usr/src/contrib/gcc/eh-common.h I had a similar problem that plagued me for 2 months before I finally figured it out 2 days ago. You need to remove your CXXFLAGS definition in /etc/make.conf, it is conflicting with CXXFLAGS in /usr/share/mk/sys.mk. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Stale modules (Re: panic in the morning)
On Thu, Apr 20, 2000 at 11:56:08AM +0100, Paul Richards wrote: that rapid developer folks can disable it. ITYM "rabid". And I kinda resent that.. ;-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld breakage (netstat/route.c rev 1.43)
Buildworld on 5.0-CURRENT is breaking here: === usr.bin/netstat cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/if.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/inet.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/inet6.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/main.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/mbuf.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/mroute.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/ipx.c cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/route.c /usr/src/usr.bin/netstat/route.c: In function `p_tree': /usr/src/usr.bin/netstat/route.c:284: structure has no member named `rn_b' /usr/src/usr.bin/netstat/route.c:308: structure has no member named `rn_r' /usr/src/usr.bin/netstat/route.c:309: structure has no member named `rn_l' /usr/src/usr.bin/netstat/route.c: In function `p_rtnode': /usr/src/usr.bin/netstat/route.c:321: structure has no member named `rn_b' /usr/src/usr.bin/netstat/route.c:329: structure has no member named `rn_b' /usr/src/usr.bin/netstat/route.c:330: structure has no member named `rn_l' /usr/src/usr.bin/netstat/route.c:330: structure has no member named `rn_r' /usr/src/usr.bin/netstat/route.c:336: structure has no member named `rm_b' [1] + exit 1 make buildworld 2 1 | done tee build.log *** Error code 1 Stop in /usr/src/usr.bin/netstat. *** Error code 1 If Mark or Garrett could fix this ASAP that would be nice. :) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP changes and breaking kld object module compatibility
On Mon, Apr 24, 2000 at 12:36:45AM -0400, Alok K. Dhir wrote: Totally off topic question that I've wondered for some time now - what does MFC stand for? Merge From CURRENT. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Tue, Apr 25, 2000 at 03:30:27PM -0500, Richard Wackerbarth wrote: Yes, the developers do a good job of repressing opinions that differ from their own. It should be noted that the person who brought this up was a developer. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Wed, Apr 26, 2000 at 12:27:22PM +0200, Brad Knowles wrote: Why would "The Project" have to do anything? We've already established this is of minority appeal, Have we? Really? We have established that this is of minority It seems to me that the typical assumption is that if someone doesn't speak up, they abstain their vote, for whatever value it might have. Thus, given the number of people who have said they don't think it worth it, and given the number who said they would like this feature, I think we've established that this is a minority issue, quite clearly. Since this is a volunteer project, people are NOT going to be polled on their opinion about X, Y, or Z. They'll either speak up if they care enough or they'll be quiet about the whole proceeding. It does seem that this mailing list is entirely inappropriate for this particular topic; perhaps this thread should be moved to freebsd-arch. Or, as Chuck said about 10 messages ago, it should just die. Either way, I don't honestly care. I'm just not going to be convinced to do any of the coding necessary to prune our repository. I have better things to do with my time than something like that. :-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Wed, Apr 26, 2000 at 08:53:52AM -0700, Frank Mayhar wrote: "Frankly, my dear, I don't give a damn." Richard, for the record, I'd like to point out that the person who said this is not a developer and therefore the backlashing you're getting is not solely from developers. Other people are sick of your crap, too. :) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: Removal of unneeded sys/kernel.h
On Wed, Apr 26, 2000 at 11:50:11AM +0200, Poul-Henning Kamp wrote: New patch at: http://phk.freebsd.dk/misc/sys_kernel_h.patch This patch removes 67 unneeded instances of #include sys/kernel.h Comments, tests and reviews please. Just write a script to check all #include's against their prototypes and have it autogen diffs. I'm sure perl mavens will say that'll only take about 100 lines of perl. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: Removal of unneeded sys/kernel.h
On Fri, Apr 28, 2000 at 07:45:36AM +0200, Poul-Henning Kamp wrote: I agree too, but nobody has written *that* code yet. Instead of trying to find these yourself, why not invest this time in writing said script? :) (I'm not volunteering for this.. ;-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rc.d startup scripts
Hello, I've noticed an inconsistency among our ports. It seems that not every port that installs rc.d startup scripts includes methods to not only startup, but also shutdown and/or restart, where appropriate. (Sent to -ports for ports hackers' opinions.) Shouldn't this sort of thing be standardized? And maybe a similar method be integrated into /etc/rc for restarting base system daemons? (Sent to -current for src hackers' opinions.) Please continue specific discussion on either of these in their own list, or if reply is general Cc both. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rc.d startup scripts
On Sat, May 06, 2000 at 04:15:33PM -0400, Brandon D. Valentine wrote:
You have answered your own question. What exists in ${PREFIX}/etc/rc.d
are startup scripts, *not* shutdown or restart scripts.
Okay, then you think that all the ports rc.d *.sh scripts should be changed
only to allow startup, right?
You mean our init system should look like RedHat's? The OS is named
Free_BSD_ because we use not only the source code from the BSD team at
UCB, but because we practice their OS philosophy as closely as is still
relevant to the industry. We use BSD init, not SVR4, and I don't see
any reason for that to be altered.
Fine, you can quote historical context to argue against doing something
similar to SVR4 init. I, however, see nothing wrong with making it easier
to manage the daemons. Of course, that does not necessarily need to go in
the rc.d scripts.
--
Will Andrews [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+
G+ e- h! r--+++ y?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: rc.d startup scripts
On Mon, May 08, 2000 at 11:53:16PM -0700, Doug Barton wrote: Point well taken. If anyone has references to this work, or an easy introduction to netbsd's version I'd love to look at them. I've been hoping to carve out some time to work on this, but every time I talk about vacation, my boss just laughs That's to be expected of a company like Yahoo! -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles
On Sun, May 14, 2000 at 01:25:16PM -0600, Lyndon Nerenberg wrote: I like the idea, but the -l flag conflicts with a different usage for SVR4 derived makes (on at least AIX, Irix, and Solaris): -l load Specifies that no new jobs (commands) should be started if there are others jobs running and the load average is at least load (a floating-point number). With no argument, removes a previous load limit. Maybe this should instead be a -d sub-option? And I like the idea of adding the -l functionality described above. Ok, what do other people think? I mean, it'd be easy to change the flag to use this feature. -dl seems fine for this particular feature. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking build world costs $5? (was: Can we please have a current that compiles?)
On Sun, May 14, 2000 at 10:19:21AM +0930, Greg Lehey wrote: I'd go along with that. What do the other committers think? Can I drink pop instead? I'm underage, and I don't like alcohol anyway. :) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make(1) patches to bypass quietness prescribed by @-prefixed commands in Makefiles
Hi all,
Some time ago I was complaining about how there is no way to force make(1)
to display the commands executed by @-prefixed commands in Makefiles. So I
went around and talked to a few people and one guy clued me in on how I
would add something like this (sorry, I don't remember the name right now
as this was a few weeks ago..).
This option is useful for people with complex Makefile hierarchies who
cannot simply insert a `@${ECHO} "SOMEVAR = ${SOMEVAR}"` as needed in their
Makefiles or remove all the @'s in their Makefiles. In particular, I would
use this feature to debug ports.
Attached is the patch. If I can get permission, I'd like to commit this to
code on -current, with a possible MFC in a few weeks (?). I'd like to hear
any complaints about this code, including any style(9) mistakes, whether
this option would be considered bloat, and whether the variable name
``beLoud'' is appropriate in this context. ;-)
Thanks,
--
Will Andrews [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+
G+ e- h! r--+++ y?
Index: compat.c
===
RCS file: /extra/cvsroot/src/usr.bin/make/compat.c,v
retrieving revision 1.17
diff -u -r1.17 compat.c
--- compat.c2000/04/14 06:39:10 1.17
+++ compat.c2000/05/13 17:38:22
@@ -241,6 +241,8 @@
while ((*cmd == '@') || (*cmd == '-')) {
if (*cmd == '@') {
silent = TRUE;
+ if (beLoud)
+ silent = FALSE;
} else {
errCheck = FALSE;
}
Index: job.c
===
RCS file: /extra/cvsroot/src/usr.bin/make/job.c,v
retrieving revision 1.17
diff -u -r1.17 job.c
--- job.c 2000/01/17 06:43:40 1.17
+++ job.c 2000/05/13 17:38:12
@@ -556,6 +556,8 @@
while (*cmd == '@' || *cmd == '-') {
if (*cmd == '@') {
shutUp = TRUE;
+ if (beLoud)
+ shutUp = FALSE;
} else {
errOff = TRUE;
}
Index: main.c
===
RCS file: /extra/cvsroot/src/usr.bin/make/main.c,v
retrieving revision 1.35
diff -u -r1.35 main.c
--- main.c 1999/11/23 10:35:24 1.35
+++ main.c 2000/05/13 17:47:35
@@ -138,6 +138,7 @@
BooleanbeVerbose; /* -v flag */
BooleanoldVars;/* variable substitution style */
BooleancheckEnvFirst; /* -e flag */
+BooleanbeLoud; /* -l flag */
LstenvFirstVars; /* (-E) vars to override from env */
static Boolean jobsRunning;/* TRUE if the jobs might be running */
@@ -175,9 +176,9 @@
optind = 1; /* since we're called more than once */
#ifdef REMOTE
-# define OPTFLAGS "BD:E:I:L:PSV:d:ef:ij:km:nqrstv"
+# define OPTFLAGS "BD:E:I:L:PSV:d:ef:ij:klm:nqrstv"
#else
-# define OPTFLAGS "BD:E:I:PSV:d:ef:ij:km:nqrstv"
+# define OPTFLAGS "BD:E:I:PSV:d:ef:ij:klm:nqrstv"
#endif
rearg: while((c = getopt(argc, argv, OPTFLAGS)) != -1) {
switch(c) {
@@ -322,6 +323,10 @@
case 'k':
keepgoing = TRUE;
Var_Append(MAKEFLAGS, "-k", VAR_GLOBAL);
+ break;
+ case 'l':
+ beLoud = TRUE;
+ Var_Append(MAKEFLAGS, "-l", VAR_GLOBAL);
break;
case 'm':
Dir_AddDir(sysIncPath, optarg);
Index: make.h
===
RCS file: /extra/cvsroot/src/usr.bin/make/make.h,v
retrieving revision 1.12
diff -u -r1.12 make.h
--- make.h 1999/09/11 13:17:35 1.12
+++ make.h 2000/05/13 17:41:09
@@ -322,6 +322,8 @@
extern Boolean checkEnvFirst; /* TRUE if environment should be searched for
* all variables before the global context */
+extern Boolean beLoud; /* Force all commands to be outputted; ignores
+* @-prefixes, etc. */
extern Lst envFirstVars; /* List of specific variables for which the
* environment should be searched before the
* global context */
ftp(1) breakage w/ passive mode?
[ i'm not on -stable, but am on -current ] Hi all, I'm having trouble with ftp(1) in passive mode on 4-STABLE and 5-CURRENT: FreeBSD 4.0-STABLE #0: Sat May 27 10:26:43 EDT 2000 FreeBSD 5.0-CURRENT #1: Fri May 26 04:52:03 EDT 2000 2 5002-0 (18:46:17) [will@radon ~]% ftp ftp://ftp.FreeBSD.org/pub/ Connected to ftp.freesoftware.com. [..] 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. 200 Type set to I. 250 CWD command successful. 250 CWD command successful. ftp ls 500 'EPSV': command not understood. 500 'LPSV': command not understood. Passive mode refused. ftp However, it works on some servers: 2 5007-0 (18:49:16) [will@radon /usr/src/usr.bin/ftp]% ftp ftp://ftp.cs.ubc.ca/ Connected to ftp.cs.ubc.ca. [..] 200 Type set to I. 250 CWD command successful. ftp ls 227 Entering Passive Mode (142,103,6,49,233,148) 150 Opening ASCII mode data connection for /bin/ls. total 28 drwxrwxr-x 10 root other512 Jan 17 1996 . drwxrwxr-x 10 root other512 Jan 17 1996 .. lrwxrwxrwx 1 root other 7 Dec 27 1995 bin - usr/bin lrwxrwxrwx 1 root other 1 Dec 27 1995 cs - . [..] ftp quit So it seems there's something quite broken in the code. My suspect is rev 1.25 of ftp.c and associated commits. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp(1) breakage w/ passive mode?
On Sun, May 28, 2000 at 05:53:38PM -0700, Cy Schubert - ITSD Open Systems Group wrote: According to the ftp(1) man page: Please note that if you are connecting to IPv6 ftp server, the program will use EPSV/EPRT pair and LPSV/LPRT pair, in- stead of PASV and PORT. The meaning is the same.) Ok.. I have no IPv6 network except for my localnet. The outside network is completely IPv4. What would make ftp(1) think it has an IPv6 connection? I have no idea.. If you have no requirement for IPv6 you may wish to create a custom kernel w/o IPv6 options. Well, it has purely experimental purposes.. I'd rather leave it in and get ftp(1) properly fixed, since everything else works just fine. :-) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Starange behaviour ...
On Sun, Jun 04, 2000 at 12:58:28PM -0400, bush doctor wrote: the same port reports none of the warnings :(. Any clues? Different libc linking in one of the libs. -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Check for ports updates
On Tue, Jun 06, 2000 at 09:27:16PM +0200, Thomas Schuerger wrote: Is there already a tool that checks the installed ports for available updates in /usr/ports? I've written such a tool, which seems to work fine already. Anyone interested? pkg_version(1) -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: setsockopt(IP_FW_ADD)
On Sun, Jun 11, 2000 at 01:19:44PM -0700, Edwin Culp wrote: 00050 divert 8668 ip from any to any via dc0 ipfw: setsockopt(IP_FW_ADD): Invalid argument I'm getting this error with ipfw running current as of this morning. Has something changed? Other than that you forgot options IPDIVERT in your kernel? -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make.conf fix
Hi -current and -ports,
I've noticed something that seems to have been broken for a long time.
In etc/defaults/make.conf we have several MASTER_SITE_* variables which
reference "%SUBDIR%". However, these variables do not work as expected.
So we must fix this discrepancy with the following patch.
Comments?
--
Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+
G+ e- h! r--+++ y?
Index: make.conf
===
RCS file: /extra/cvsroot/src/etc/defaults/make.conf,v
retrieving revision 1.110
diff -u -r1.110 make.conf
--- make.conf 2000/06/17 10:51:47 1.110
+++ make.conf 2000/06/20 21:20:45
@@ -184,22 +184,22 @@
# Some ports use a special variable to point to a collection of
# mirrors of well-known software archives. If you have a mirror close
# to you, uncomment any of the following lines and change it to that
-# address. (Don't remove the "/%SUBDIR%/" part.)
+# address. (Don't remove the "/${MASTER_SITE_SUBDIR}/" part.)
#
# Note: the right hand sides of the following lines are only for your
# information. For a full list of default sites, take a look at
# bsd.port.mk.
#
-#MASTER_SITE_XCONTRIB= ftp://ftp.x.org/contrib/%SUBDIR%/
-#MASTER_SITE_GNU= ftp://prep.ai.mit.edu/pub/gnu/%SUBDIR%/
-#MASTER_SITE_PERL_CPAN=
ftp://ftp.digital.com/pub/plan/perl/CPAN/modules/by-module/%SUBDIR%/
-#MASTER_SITE_TEX_CTAN= ftp://ftp.tex.ac.uk/tex-archive/%SUBDIR%/
-#MASTER_SITE_SUNSITE= ftp://metalab.unc.edu/pub/Linux/%SUBDIR%/
-#MASTER_SITE_KDE= ftp://ftp.kde.org/pub/kde/%SUBDIR%/
-#MASTER_SITE_COMP_SOURCES=
ftp://gatekeeper.dec.com/pub/usenet/comp.sources.%SUBDIR%/
-#MASTER_SITE_GNOME=ftp://ftp.gnome.org/pub/GNOME/sources/%SUBDIR%/
-#MASTER_SITE_AFTERSTEP=ftp://ftp.afterstep.org/%SUBDIR%/
-#MASTER_SITE_WINDOWMAKER= ftp://ftp.windowmaker.org/pub/%SUBDIR%/
+#MASTER_SITE_XCONTRIB= ftp://ftp.x.org/contrib/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_GNU= ftp://prep.ai.mit.edu/pub/gnu/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_PERL_CPAN=
+ftp://ftp.digital.com/pub/plan/perl/CPAN/modules/by-module/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_TEX_CTAN= ftp://ftp.tex.ac.uk/tex-archive/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_SUNSITE= ftp://metalab.unc.edu/pub/Linux/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_KDE= ftp://ftp.kde.org/pub/kde/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_COMP_SOURCES=
+ftp://gatekeeper.dec.com/pub/usenet/comp.sources.${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_GNOME=ftp://ftp.gnome.org/pub/GNOME/sources/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_AFTERSTEP=ftp://ftp.afterstep.org/${MASTER_SITE_SUBDIR}/
+#MASTER_SITE_WINDOWMAKER= ftp://ftp.windowmaker.org/pub/${MASTER_SITE_SUBDIR}/
#
#
# Kerberos IV
Re: make.conf fix
On Wed, Jun 21, 2000 at 12:09:02AM -0700, Satoshi - Ports Wraith - Asami wrote:
Waitaminit. These are correct, please look at bsd.sites.mk. What
makes you think they are not working?
Hmm... weird. I tried using the overrides in make.conf some time ago
and they didn't work and I had to use ${MASTER_SITE_SUBDIR} instead of
%SUBDIR%. Anyway, I withdraw this patch.
--
Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+
G+ e- h! r--+++ y?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: new ftpd feature...
On Wed, Jun 28, 2000 at 12:23:53PM -0500, Visigoth wrote: I understand how IP_PORTRANGE_HIGH and all work, but there are other programs which use these as well, and in at least my application, having support in ftpd is nice... I'd have to agree with Visigoth here; system controls should be for EVERYTHING, not just controlling one server. Visigoth could use it for a short-term solution, but in the long term, I think his solution is better (in principle, I didn't look at the code). -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
On Sat, Jul 01, 2000 at 07:14:35PM +0400, Ilmar S. Habibulin wrote: Some order, i suppose. There is plenty of order in the current system. Garrett Wollman suggested that you answer this question carefully, and you have not done that, but provide a vague summary of your beliefs. Moreover, many people are used to the current system; changing it is a fundamental, non-trivial job. This requires good reasoning. -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Sun, Jul 02, 2000 at 07:58:17AM +0200, [EMAIL PROTECTED] wrote: Synopsis: add -c for grand total to df(1), like du(1) does Description: sample of output : # df -c Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/da0s1a 1904559 1249983 50221271%/ /dev/da1s1c 2031922 1336326 53304371%/disk2 /dev/da2s1a 1904559 1484367 26782885%/disk1 /dev/da3s1a 1904559 1414623 33757281%/disk4 procfs 440 100%/proc total 7745603 5485303 164065577% Does anyone else here think this is a good idea? If so, I'd like to merge this in -CURRENT and MFC before 4.1-RELEASE. It seems like a fairly nice addition to df(1), and can be useful for system accounting. -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Tue, Jul 04, 2000 at 03:32:11PM +1000, Andy Farkas wrote: My only suggestion is to put a dashed line above the totals in order to clearly say they are totals (like I did below). That might be nice, but I object on the grounds that it isn't consistent with du -c. -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Tue, Jul 04, 2000 at 04:06:46PM +0200, Sheldon Hearn wrote: My only objection is that it seems to produce useless values. Can you think of a use for these grand totals? They are helpful for monitoring total space; I would use them in administrative scripts to watch my space. Granted, this job could be done by shell scripts.. but I think it would be useful in df(1). -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Tue, Jul 04, 2000 at 10:34:41PM +0200, Sheldon Hearn wrote: Okay, then. Let me be more specific. How is the notion of "total space" useful? :-) Tells you when it's time to get new hard drives? I guess the originator of the PR should provide a reason. =\ -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Thu, Jul 06, 2000 at 06:09:54PM +0200, Paul Herman wrote: Naturally, "no reason not to put it in" is most certainly *not* a reason to put it in. I would like to hear some to sway me one way or the other. How about precedent: du -c. "Hey, we could have used an awk script with du(1) too!!" -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup sites are all at capacity?
On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote: I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and each site returns this message: Rejected by server: Access limit exceeded; try again later I've gotten that before but never with all of the hosts out there. Is everyone and their brother doing a make world today, are the sites down for maintenance, or is something sinister going on? Mine (cvsup12) is still below capacity (28 max clients): http://paloalto.csociety.org/mrtg-sanmateo/ (mrtg) It never got above 10 clients before today. How about a few people switch to my server for regular updates? Thanks. :) Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
09/18 -CURRENT does not boot off SATA
Hi,
My -CURRENT workstation won't boot off the WD Raptor 36GB disk,
which is on a SiI 3112A SATA-150 controller. This was working
with a kernel in early July. {build,install}{world,kernel}
completed. Fortunately, it seems I can still boot with the
older kernel. I guess ATAng problems still haven't been fleshed
out or I'm missing something?
Anyway, the disk is probed but is not correctly identified. It
says something like:
ad4: 32MB * * * * * * * * * * * * * * * * * * * * [65537/1/1] at ata2-master WDMA0
where * appears to be a smiley face. Strange.
Anyone seen anything like this? Thanks in advance.
Regards,
--
wca
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 09/18 -CURRENT does not boot off SATA
On Thu, Sep 18, 2003 at 08:48:57PM -0700, Will Andrews wrote:
My -CURRENT workstation won't boot off the WD Raptor 36GB disk,
which is on a SiI 3112A SATA-150 controller. This was working
with a kernel in early July. {build,install}{world,kernel}
completed. Fortunately, it seems I can still boot with the
older kernel. I guess ATAng problems still haven't been fleshed
out or I'm missing something?
Anyway, the disk is probed but is not correctly identified. It
says something like:
ad4: 32MB * * * * * * * * * * * * * * * * * * * * [65537/1/1] at ata2-master WDMA0
where * appears to be a smiley face. Strange.
Anyone seen anything like this? Thanks in advance.
So, having received no response to this, I decided to bootstrap
the machine using a PATA disk. Funny that, the machine won't
boot off the PATA disk directly. Hilarity ensues. For details,
see: http://csociety.org/~will/dmesg.badATAng
which is the output of dmesg -a where I booted -v.
Regards,
--
wca
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote: OK, here's what we can do to fix this: 1) Put back -pthread in -current so all the ports don't fail 2) I will build a full set of -current packages with the -pthread error still in place, to determine the list of packages that need to be fixed (in fact I already have this, see http://dosirak.kr.freebsd.org/errorlogs). 3) You, John Birrell, and whoever else is interested in fixing these ports can work on them at your own pace without disrupting life for the rest of the users. Once they're all fixed, we can turn the error back on or make it a NOP or do whatever else is decided to be appropriate. 4) It is likely that steps 2 and 3 will need to be iterated several times, because there are dozens of ports that need to be fixed, and many of them are hiding other ports that depend on them and also need to be fixed. I don't know if there is much point to #1 at this point since it's been gone for about 2 weeks now. #2/3/4 sounds fine to me. In the meantime KF is working on a patch to properly support PTHREAD_LIBS in KDE's configure scripts. We plan to commit it when the freeze lifts, pending PR #55325. I suggest that people not build ports on -CURRENT for a few weeks until things get sorted out, unless they're going to fix the problems with specific ports. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Sun, Sep 21, 2003 at 02:12:55AM -0400, Daniel Eischen wrote: Because when things break, people fix them. There is no motivation (as seen in the last 2+ years) to fix something that isn't broken. Please also see: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=321307+0+archive/2003/freebsd-ports/20030601.freebsd-ports my posting to ports@ in May of this year. I wish you'd pushed the issue a bit more aggressively. Sometimes people don't pay close enough attention, and I am definitely one of those people. My apologies for missing that message. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Sun, Sep 21, 2003 at 03:17:28AM -0400, Daniel Eischen wrote: From what I've recently read, the freeze should be lifting this week. Can we hold off till then? Is a few more days going to matter? If the freeze continues longer than expected, I'll back the change out until it's over. I think we are going to extend it to allow more fixes for 4.9 since it's going to be delayed. But I'm not positive. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Mon, Sep 22, 2003 at 10:35:10PM -0600, Scott Long wrote: [...] Scott said it all for me. Seriously. The whole idea of breaking backwards de-facto compatibility is bad, bad, bad. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Initial list of ports that fail due to -pthread
On Wed, Sep 24, 2003 at 01:34:13AM -0400, Michael Edenfield wrote: One very important group of ports that should get looked at when this gets worked out is KDE. Apparently, Qt uses a different means of determining wether to use threading, than the ports that depend on it. The qt-using ports appear to check for -lpthread, then c++ -pthread, and if neither of those checks pass, disable threading: I have been working with KDE-FreeBSD to make a patch to fix this problem since last week. I am nearly done testing it, so please bear with me and I will get it committed soon. We expect to remove it with the release of KDE 3.2 in a few months as it will be committed to HEAD in KDE. Also, I believe I fixed qt32 on 18 September 2003. It certainly built and works fine on my 5.1-CURRENT 2003/09/19 box. It's just KDE that needs fixing at the moment. I'm typing this in KDE 3.1.4 on said machine. Thanks. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE 3.1.4 on 5.1-CURRENT fixes for PTHREAD_LIBS
Hello, With the help of Adriaan de Groot, Andy Fawcett, and Lauri Watts, I've successfully built KDE on 5.1-CURRENT as of 2003/09/19. The following patch can be applied: http://www.fruitsalad.org/patches/kde314-fixpth.diff using: cd /usr/ports patch kde314-fixpth.diff Please test this. Followups to [EMAIL PROTECTED], flames to /dev/null. Thanks for your time. Note1: At the moment KDE hasn't been built on axp* for 4.9R, so this patch won't be committed in the meantime. Note2: Yes, we know -pthread was temporarily put back. It will be removed again soon. Note3: There are several ports that use KDE's configure scripts but are not maintained by us. These ports are most likely still broken. Some of them use our Makefile.kde code, and for those, I've added a line to ignore our pthfix since they will need their own. Note4: Patch has been applied to KDE HEAD to resolve the same issues. Therefore, this patch will be removed when 3.2 is released. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
On Mon, Sep 29, 2003 at 09:13:48PM +0200, Soren Schmidt wrote: First off, there is ONLY support for Promise and HPT soft RAID in the ATA driver, other vendors products are *not* supported (yet). Second, there seem to be a problem with some sil3112 setups where timeouts and what not ruins the lunch, but so far I've not been able to reproduce.. I am still unable to use my SATA drive, it's probed incorrectly as I posted earlier. Reverting to the August 10th 00:00 UTC kernel fixes this problem, so I concluded that ATAng broke this. If it makes any difference, my model is a SiI3112 RAID controller, but I only have one drive and it probes as ad4... the situation doesn't improve any if I add ataraid. But maybe ATAng doesn't take into account the difference between a normal and a RAID SiI 3112, if any? Here are my dmesg's again (Sep 18th, Aug 10th kernels): http://csociety.org/~will/dmesg.badATAng http://csociety.org/~will/dmesg.Aug10.preATAng The problem shown in the first dmesg still showed itself when I tried a new kernel on Sep 25th. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
On Mon, Sep 29, 2003 at 04:05:11PM -0500, David Leimbach wrote: I'd have to reboot and see how recent my FreeBSD stuff is... I have been rather distracted by the job which pays me salary :). If you can do that, I'll check out a copy of the kernel from that day and try to narrow down when the SiI3112A/WD Raptor probe broke. Hopefully that will be of more use to Soren. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
On Mon, Sep 29, 2003 at 05:42:24PM -0500, David Leimbach wrote: Ok... I built mine on Thu Sep 18 22:42:16 CDT 2003. I think that's post ATAng commit. WTF?!?! My problem is for Sep 18 kernel and later. I'll have to try Sep 15 or something just to see... Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
SiI 3112A doesn't probe, take two: found the commit that broke it
Hi, http://lists.freebsd.org/pipermail/cvs-src/2003-September/009918.html src/sys/dev/ata/ata-all.c, rev 1.188 src/sys/dev/ata/ata-lowlevel.c, rev 1.8 After an exhaustive binary search, I've found this is the commit that broke probing for my SATA disk. Merely reverting the change on the latest kernel doesn't compile, however. :-\ Hope this is more helpful, Soren... I'll just stick with the Sep 1 00:00 UTC kernel for now. If you have any patches you think will fix this problem feel free to ask me to test. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI3112 SATA controller problems - status
On Tue, Sep 30, 2003 at 10:06:40PM +0200, Soren Schmidt wrote: I have now found a way to reproduce the DMA problems some setups seems to be having with the SiI3112A SATA chip. Now, if I use real SATA drives, (and I mean real SATA drives, the WD Raptor fx is not a real SATA device but just a PATA device with a build in PATA-SATA converter chip) it works just fine no matter what I try. Interesting. SATA is also a power spec, right? I use a normal SATA cable but also an ATX power connector. I'm guessing that's what you mean by the Raptor not being a real SATA drive. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI3112 SATA controller problems - status
On Tue, Sep 30, 2003 at 10:22:33PM +0200, Soren Schmidt wrote: No what I mean is that the Raptor is a PATA device fitted with a marvell PATA-SATA converter on board, its not a pure SATA design, but just the old stuff they used to make with the marvell chip kludged on the back :) The power connector is uninteresting in this context. Interesting, since no one's made any PATA drives that spin at 10,000 RPM as far as I know. For some reason I thought the interface change allowed for this (but couldn't come up with a good reason why it would make a difference). :) Thanks for your work, btw. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI3112 SATA controller problems - status
On Tue, Sep 30, 2003 at 06:15:58PM -0500, David Leimbach wrote: Yeah... I feel somewhat betrayed. Time to switch to a different drive brand :) I should have bought a Maxtor 10K III U160 SCSI drive instead. :) Getting an appropriate controller would have been more expensive, but the drive's about the same... ;-\ Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
On Fri, Oct 03, 2003 at 09:45:27PM -0400, Barney Wolff wrote: I'm finally motivated to ask, why don't security advisories contain the equivalent revs for -head? Surely I can't be the only person following -current who doesn't build every day. Simply because the SO does not support -CURRENT. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
On Fri, Oct 03, 2003 at 10:10:41PM -0400, Barney Wolff wrote: Does this mean that the situation can ever arise where a security bug is corrected in the advisory's announced releases but not in -current? Or, can we assume that as of the time of the security announcement the vulnerability has *always* been corrected in -current? No. Yes. The rule is that changes are always committed to -CURRENT first, unless they do not apply. This rule is rarely broken in FreeBSD, and certainly never broken for security issues. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc related -current upgrade problems
On Fri, Jul 25, 2003 at 05:45:10PM -0700, Scott M. Likens wrote: These issues have been addressed in KDE 3.1.3 if you're patient enough for Will to work out the kinks the ports will be updated in a week or less. Much more likely someone else on kde-freebsd is going to solve those problems, if they aren't already. regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: D-Link DGE-500T support
On Tue, Aug 05, 2003 at 08:49:50AM -0500, Nick H. - Network Operations wrote: I attempted to use a D-Link DGE-500T card this weekend on 5.1-RELEASE (and -CURRENT) with no success. It is unable to probe the device and find a proper driver for it. My question is: are there any plans currently to provide support for this card? If there is already support for it (which may be the case) then which driver is it using? I tried a GENERIC kernel with all the default drivers, but it diddnt work with them. I can eventually get dmesg output again, but I'd need to bring the server down to put the card back in. Any help is more than welcome. Thank you! This card's chipset is the NatSemi gigE chipset, which is supported by the nge(4) driver. However, as nge(4) cards are relatively uncommon, support is not enabled by default in the GENERIC kernel. You can load the if_nge module, however. kldload if_nge In fact, the only gigE chipset common enough to make it into GENERIC is the Broadcom, supported by bge(4). Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/kdebase3 build?
On Thu, Jan 16, 2003 at 03:14:25PM -0600, Sean Kelly wrote: I'm not entirely sure this belongs on -CURRENT, but I couldn't find any KDE specific list similar to -gnome and I seem to recall that the building of KDE3 was a desired goal for FreeBSD 5.0. That said, I apologize in advance if this is the wrong place to take this. There is. See http://lists.csociety.org/listinfo/kde-freebsd/ which is where [EMAIL PROTECTED] sends mail to. Is it just me, or does x11/kdebase3 (3.0.5) not build on 5.0-STABLE? 5.0-STABLE? What's that? :) Seriously, KDE built fine for me on -CURRENT but I haven't tested a recent one. Perhaps this problem might be because of a recent change to -CURRENT. I notice that VM_METER is not defined in my latest upgrade. So I looked on a 4-STABLE box and found it in vm/vm_param.h. Then I found it in src/sys/vm/vm_param.h. According to the cvs log, Matt Dillon changed the name of the variable. Sigh. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VM_METER no longer defined?
On Fri, Jan 17, 2003 at 01:02:07PM -0500, Joe Marcus Clarke wrote: It looks like Matt did this to fix vm.vmtotal. From sys/vm/vm_param.h: Make 'sysctl vm.vmtotal' work properly using updated patch from Hiten. (the patch in the PR was stale). It looks to have been replaced by VM_TOTAL. I fixed libgtop[2] by checking for VM_TOTAL, and using that instead of VM_METER. This seems to work. Of course, these things can be fixed. But I consider this change gratuitous and it breaks standard compatability rules: deprecate for one major version and remove in the second. I haven't seen any reason why this couldn't be added to vm/vm_param.h: #define VM_METER VM_TOTAL for compatability purposes. This change is way too sudden in an external API (if it's supposed to be internal, then protect it with an #ifdef _KERNEL already!). Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VM_METER no longer defined?
On Sat, Jan 18, 2003 at 04:02:00PM -0500, Joe Marcus Clarke wrote: Ok, I agree that the naming could cause confusion since there is a vmmeter struct and a vmtotal struct. However, the Release Engineering policy that was set out at the start of RELENG_5_0 is that public API changes need review. I'm not saying that those reviews won't be approved, but we want to keep the pain involved in 5.0-5.1 as low as possible. This is causing pain with several high-profile ports. In my opinion, the inconsistency in VM_METER was annoying, but not enough to justify breaking an interface that has been existence since _1994_. Dude, that is _9_ years. If you'd like the name to change, lets hold of for RELENG_5 to happen. Please back out the name change. Scott, the API change does not exist in RELENG_5_0. This change only went into HEAD. ...which will later become 5.1 and RELENG_5, yes? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: wifi drivers error - 5.0-CURRENT
On Sat, Jan 18, 2003 at 10:14:47PM -0600, Nick H. -- Technical Support Engineer wrote: Got this today after cvsup'ing earlier this morning: Read src/UPDATING. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Amanda backups, or dump(8) broken?
Hi, Is anyone else here backing up -CURRENT machines using AMANDA? I've been noticing that the backups for these machines have what appear to be bad backups. That is to say, amverify gives things like this: [...] firepipe-3 (ganymede._.20030304.1): amrestore: 0: skipping start of tape: date 20030304 label firepipe-3 amrestore: 1: restoring ganymede._.20030304.1 gzip: stdin: decompression OK, trailing garbage ignored amrestore: 2: reached end of information cannot open /dev/tty: Device not configured Tape is not a dump tape 64+0 in 64+0 out firepipe-3 (oberon._usr.20030304.2): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring oberon._usr.20030304.2 gzip: stdin: decompression OK, trailing garbage ignored amrestore: 1: reached end of information cannot open /dev/tty: Device not configured Tape is not a dump tape 64+0 in 64+0 out [...] ganymede: FreeBSD ganymede.firepipe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sun Mar 2 22:01:40 EST 2003 [EMAIL PROTECTED]:/net/ganymede/src/sys/i386/compile/GANYMEDE i386 oberon: FreeBSD oberon.firepipe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Jan 14 01:19:15 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/sparc64/compile/OBERON sparc64 Ganymede runs Amanda 2.4.3 while oberon is running Amanda 2.4.4b1 due to 64-bit safeness fixes in that version. Note that I also back up three other machines (two 4.x/i386 and one Linux/mipsel) without a peep from amverify. Anyone know if maybe the dump format has been changed to the extent that it breaks Amanda or something? In fact, based on the 64+0 it appears that the header or something similar may have been broken. Or maybe Amanda is broken. I'm just looking for someone else who has already seen this behavior. Preferably someone else that knows what the issue is and how it might be fixed... Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Amanda backups, or dump(8) broken?
On Tue, Mar 04, 2003 at 11:57:34AM -0800, Brooks Davis wrote: I've seen reports that dump compatability was broken. I'm dumping two 5.0 boxes and one 4-STABLE box to one of the 5.0 boxes and the amverify I'm current running doesn't seem to have any problem. Thus, I'd tend to suspect we need to fix restore in 4.x. What about non FreeBSD Amanda servers? Are they going to be able to verify a FreeBSD-CURRENT dump? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GBDE automation scripts?
On Wed, Mar 12, 2003 at 05:39:01PM -0800, Lucky Green wrote: I am writing a section for the Handbook on how to use gbde. Currently, using gbde is a rather manual process. Each time a host reboots, the admin needs to attach the gbde device(s), enter any required passphrases, manually fsck the partition, and mount it. I suspect some subscribers to this mailing list have scripts in place to at least partially automate the process. If you have such a script, could you please get in touch with me for inclusion of the script in the Handbook? I suggest getting it added to the ports tree, or perhaps the base system itself. PHK might have a preference along these lines. Putting it in the Handbook isn't my idea of being a good place to maintain actual programs. Just a thought. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Fix for pam_nologin.so runtime error
On Thu, Oct 18, 2001 at 03:02:49PM -0701, Jos Backus wrote: Forgot to mention, I had to make kcheckpass setuid root to make kcheckpass itself work (just verified this on -stable). Uh.. that's documented. See ports/x11/kdebase2/Makefile rev 1.77. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Fix for pam_nologin.so runtime error
On Thu, Oct 18, 2001 at 03:15:58PM -0701, Jos Backus wrote: Really? I just checked 1.77 and I don't see it. Can you tell me what to look for? Oops.. rev 1.78 in conjunction with pkg-message :) http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/kdebase2/Makefile.diff?r1=1.77r2=1.78 http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/kdebase2/pkg-message?rev=1.1content-type=text/x-cvsweb-markup :) -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: chinput can't work on KDE2.2.2
On Tue, Jan 22, 2002 at 08:56:13AM +, Liu Siwei wrote: This question is not appropriate for the -current list. I'm expanding this to include the maintainers of the KDE ports to see if anyone else has an idea what's going on. I have a question about FreeBSD's locale. I use the zh_CN.EUC locale to let my FreeBSD support Simplied Chinese. It's all right in gnome 1.4. But in recent version of KDE(aka. KDE-2.2.2), I can't set zh_CN.EUC locale for it. For I have select the country is Asia-China, language is Simplied Chinese, code is gb2312.1980. I need not set any locale in my environment to display Simplied Chinese at all. But for I have not set locale, I can't use chinput in KDE. So I set my locale to zh_CN.EUC in my $HOME/.xinitrc. But when I restart my KDE, it can't display Chinese word proper! in kedit, kwrite, etc, I can use chinput through I can't input any Chinese word proper. If I set my locale to zh_CN.GB2312, zh_CN.GBK or nothing, the KDE can display Chinese word proper, but I can't use chinput. So, how to set ocale to let chinput work under KDE2.2.2? A very inportant QUESTION is: why FreeBSD want zh_CN.EUC while KDE is not? My machine is AMD-K7 700, FreeBSD-current,all software are installed from ports(sources). I'm sorry but I can't help with this specific problem since I do not use any locale other than the default. :( -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org down?
On Thu, Feb 07, 2002 at 04:44:36PM +0100, Miguel Mendez wrote: I know this is probably offtopic but is there any problem with current.freebsd.org at the moment? I've been unable to log in for almost an hour, the ftp daemon is up, it just doesn't allow me in and I was about to load -CURRENT on my laptop. Jordan announced recently that Qwest is upgrading the hardware and that there would be intermittent problems with the server for a certain period (a few days as I recall). Regards -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MODULES_WITH_WORLD=true means no modules?
On Thu, Feb 07, 2002 at 09:57:47PM +0100, BOUWSMA Beery wrote: Maybe... I've changed my /etc/make.conf from the default, to be MODULES_WITH_WORLD=true # do not build modules when building kernel ^^^ ...you need to read the option you enabled? since I find myself often building new kernels (plus identical modules) without updating the rest of the source, taking extra time. Regards. -- wca 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: current.freebsd.org down?
On Thu, Feb 07, 2002 at 04:44:36PM +0100, Miguel Mendez wrote: I know this is probably offtopic but is there any problem with current.freebsd.org at the moment? I've been unable to log in for almost an hour, the ftp daemon is up, it just doesn't allow me in and I was about to load -CURRENT on my laptop. Jordan announced recently that Qwest is upgrading the hardware and that there would be intermittent problems with the server for a certain period (a few days as I recall). Regards -- wca 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: FreeBSD unfinished NIS+ implementation in Linux ?
On Sun, Feb 17, 2002 at 03:57:59PM +0100, Martin Blapp wrote: Bill, did you ever allowed them to make it GPL only ? Looking at the code it should be possible to import some things and make a NIS+ client available. But only if it's not GPL'd. Interesting. I looked as nisgrep/nisgrep.c and noticed that the code structure was basically the same, but the variables were just slightly different... -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI timecounter help needed!
On Mon, Feb 25, 2002 at 10:59:16AM +0100, Poul-Henning Kamp wrote: Machines with ACPI timecounters will now print 10 lines at boot when the timer is tested. You should mention that this requires bootverbose. If you are lucky you will see ten times something like: ACPI timer looks GOOD min = 3, max = 3, width = 1 That means that you have well implemented ACPI timer. If you are unlucky, one, several or all 10 lines will be marked as BAD. Please send me an email with these 10 lines and the output of pciconf -l -v for your machine. I'm am interested in reports both from good and bad machines. I will send you mine as soon as I can figure out how to extract the information usefully as the machine behaves VERY badly with the ACPI timecounter -- the only way I can see output on the syscons console is if I break into DDB repeatedly. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: missing idea.h ... ?
On Fri, Jul 21, 2000 at 09:14:57PM -0300, The Hermit Hacker wrote: Just tried to compile kde2 after upgrading to the latest 5.0-CURRENT and its reporting: In file included from /usr/include/openssl/pem.h:66, from /usr/include/openssl/ssl.h:147, from https.cc:42: /usr/include/openssl/evp.h:99: openssl/idea.h: No such file or directory its being included by a system file, so I can't blame the kde2 source for it ... I just set 'MAKE_IDEA' in my make.conf and am doing a new 'make world', but should not having that cause a problem? I don't encounter such problems in my KDE 2721 builds. I build on 4.1-RC with full OpenSSL sources. BTW: I should have a webpage/ftpsite etc. ready for port test builds tomorrow.. bug me if it's not announced soon. 8) -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Request for review/comments - new option for uname(1)
On Wed, Aug 09, 2000 at 12:59:29AM +0100, Mark Ovens wrote: Is there any reason why this is unacceptable and could not be committed? Because it can be done with an awk/sed script? -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:+ a--- C++ UB$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e h! r- y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: our CVSweb has been updated
On Mon, Aug 14, 2000 at 07:19:29PM +0900, Akinori -Aki- MUSHA wrote: I imported cvsweb.conf and cvsweb.conf-* files in the same directory as cvsweb.cgi is so we could maintain them as well as cvsweb.cgi. They are read only when there are no /usr/local/etc/cvsweb.conf, so please copy them to your local directory /usr/local/etc/ and configure them as they suit your local environment. (e.g. changing locations of repositories) Thank you *VERY*MUCH*. -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:+ a--- C++ UB$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e h! r- y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
On Wed, Aug 23, 2000 at 10:28:00AM -0400, Siobhan Patricia Lynch wrote: ^ this is cute: notice the dates, they predate the epoch. They don't predate the epoch. The epoch starts at 00:00 UTC on January 1, 1970. Hence, the dates are exactly the epoch (20:00 -0400 UTC on December 31, 1969). But you *DO* have a real bug there.. ;- -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:+ a--- C++ UB$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e h! r- y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP changes committed ... ?
On Thu, Sep 07, 2000 at 03:11:27AM -0300, The Hermit Hacker wrote: I thought one of the SMP developers announced that it was now committed, yet I haven't seen any commit messages for it ... I'm running the newest patch, so am waiting for the commit messages before I actually do my next upgrade ... They were committed about 4 hours ago. -- Will Andrews [EMAIL PROTECTED] [EMAIL PROTECTED] GCS/E/S @d- s+:+ a--- C++ UB$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e h! r- y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: POSTFIX-- Wietse: tweak and go! --pkg port: both duds
On Sun, Oct 08, 2000 at 01:14:14PM +0200, Brad Knowles wrote: 2. You mention the use of snapshots, but this is not recommended practice for sites new to postfix. Instead, start with the most recent "release" version, e.g., postfix-19991231-pl09. According to Wietse, the "snapshot" versions are: Work-in-progress code, subject to change, needs testing before it can become an official release. However, these versions are what he runs on his own systems, so it's probably better than the official "production" release version of code from most anyone else. Heh.. Wietse uses so-called ``experimental'' Postfix on his systems. And there are *LOTS* of people who think that whatever Wietse runs is good enough for them.. so this statement had better be hased on personal experience about the actual stability of ``experimental''. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench The Universal Answer to All Problems - "It has something to do with physics." -- Comic on door of Room 240, Physics Building, Purdue University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a.out binaries die in -current recently
On Sun, Oct 08, 2000 at 03:41:07PM -0500, Mark Hittinger wrote: For the past couple of days the old style binaries don't work under -current, they simply core. Well, my attitude would be "so what?". But others may find a valid need for a.out binaries *shrug*. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench The Universal Answer to All Problems - "It has something to do with physics." -- Comic on door of Room 240, Physics Building, Purdue University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a.out binaries die in -current recently
On Mon, Oct 09, 2000 at 11:40:09PM -0600, Warner Losh wrote: netscape. Nope. BSDI Netscape bins don't require a.out libs. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench The Universal Answer to All Problems - "It has something to do with physics." -- Comic on door of Room 240, Physics Building, Purdue University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SANDISK SmartMedia still does not work with -current ATA-driver
On Tue, Oct 17, 2000 at 08:29:04PM +0200, Michael Reifenberger wrote: it seems to be a ata issue because it worked before some ata-updates (after SMPng). Is anyone using SANDISK SmartMedia successfully with -cuurent? Strange, I get exactly the same output from September 29 -current. :( I'm going to bug Warner/Soren at BSDCon ... -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 09:51:32PM +0900, Makoto MATSUSHITA wrote: It is mandatory for FreeBSD installation via IPv6 network (via network devices; using gif(4) pseudo interface is a rare case, so it should be removed). Please keep INET6 option as it is. I agree with this sentiment.. please leave INET6 support in the GENERIC kernel. I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 10:27:50PM +0900, Makoto MATSUSHITA wrote: MFS is required; don't forget we have mfsroot.flp :-) Oh yeah... time to drink some more caffeinated pop and wake up.. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: licq after crt* change
On Wed, Nov 08, 2000 at 12:46:43PM +0300, Dmitry Valdov wrote: licq doesn't work since crt* change.. (coredumps) Any workaround? (recompile if licq qt doesn't help). /usr/ports/net/licq IIRC, the discussion about that found that it wasn't crt*'s fault but rather a bug in the dynamic linker. John Polstra fixed it and MFC'd yesterday. Please upgrade and try again. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Confusing error messages from shell image activation
On Sat, Dec 09, 2000 at 08:21:28PM +0100, [EMAIL PROTECTED] wrote: Agreed. It would be nice if FreeBSD could use the same system as NetBSD, storing the packages/ports under /usr/pkg. That's why PREFIX exists. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/local abuse
On Sun, Dec 10, 2000 at 11:14:32AM -0800, Joe Kelsey wrote: You are simply wrong in your characterization of /usr/local. As far back as I can remember, /usr/local has been used for locally installed [...] Pfft. Everyone has their own way of organizing files. There is no right or wrong. However, the fact that /usr/local is still hardcoded into packages IS a bug. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/usr.bin/make arch.c
On Fri, Dec 15, 2000 at 06:14:38PM -0800, Dag-Erling Smorgrav wrote: Log: Fix a bug introduced in rev. 1.17: initialize variables before use, not after. Rev. 1.17 was "Obtained from NetBSD", but is significantly different from the equivalent NetBSD revision (rev. 1.30), which does not have this bug. My apologies to those of you who had problems as a result of this commit. Thanks to DES who explained the problem to me and showed me how to avoid problems like this in the future. Boy, I'm glad I let this settle in current. :) -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: usr.sbin/ntp/ntpd make: Cannot allocate memory
On Sat, Dec 16, 2000 at 03:32:48AM +0100, Dag-Erling Smorgrav wrote: This was caused by a heisenbug in make(1) which I fixed a few minutes ago. Yes, this is my fault. Sorry to everyone who has/had problems. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld broken
On Fri, Dec 29, 2000 at 02:42:18PM +0100, German Tischler wrote: cc -fpic -DPIC -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D_ _DBINTERFACE_PRIVATE -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/ src/lib/libc/../libc/locale -DBROKEN_DES -DYP -DHESIOD -I/usr/obj/usr/src/i386/u sr/include -c /usr/src/lib/libc/../libc/db/btree/bt_close.c -o bt_close.So In file included from /usr/src/lib/libc/../libc/db/btree/btree.h:44, from /usr/src/lib/libc/../libc/db/btree/bt_close.c:52: /usr/obj/usr/src/i386/usr/include/mpool.h:54: syntax error before `CIRCLEQ_ENTRY ' /usr/obj/usr/src/i386/usr/include/mpool.h:65: syntax error before `CIRCLEQ_HEAD' Yes, it's true. Someone axed CIRCLEQ earlier, but apparently didn't test buildworld first. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
