From owner-freebsd-current Sun Jan 16 0:18:21 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C959614D78; Sun, 16 Jan 2000 00:18:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BE8A61CD5D7 for ; Sun, 16 Jan 2000 00:18:20 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 16 Jan 2000 00:18:20 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Nuking /usr/src/contrib/patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce tells me there were good reasons why patch won't be upgraded ("downgraded") from 2.1 to 2.5 - it was already tried once and reverted. Should we blow away /usr/src/contrib/patch if it's never going to be used? Kris ---- "How many roads must a man walk down?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 0:23:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 43C5114D78 for ; Sun, 16 Jan 2000 00:23:17 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 129kxF-0005Xq-00; Sun, 16 Jan 2000 10:22:33 +0200 From: Sheldon Hearn To: Marcel Moolenaar Cc: "Pierre Y. Dampure" , current@FreeBSD.ORG Subject: Re: make world breaks in /usr/src/usr.bin/xlint In-reply-to: Your message of "Sat, 15 Jan 2000 12:02:09 +0100." <388053B1.F80D3E01@scc.nl> Date: Sun, 16 Jan 2000 10:22:33 +0200 Message-ID: <21317.948010953@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000 12:02:09 +0100, Marcel Moolenaar wrote: > No. build-tools are those tiny little utilities that are part of the > sources and are only used to build the sources. Okay, so how do we boot-strap lint? Ultimately, the build of the lint libraries requires a working lint, which most people don't have at this stage. However, the lint binary itself doesn't require boot-strapping. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 1:39:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from gemini.bnc.net (gemini.bnc.net [195.247.233.33]) by hub.freebsd.org (Postfix) with ESMTP id 8096F152B7 for ; Sun, 16 Jan 2000 01:39:55 -0800 (PST) (envelope-from ap@bnc.net) Received: (from ap@localhost) by gemini.bnc.net (8.9.3/8.9.3) id KAA10702 for current@freebsd.org; Sun, 16 Jan 2000 10:39:35 +0100 (CET) (envelope-from ap) Date: Sun, 16 Jan 2000 10:39:35 +0100 From: Achim Patzner To: current@freebsd.org Subject: Current, XEON and MP performance Message-ID: <20000116103935.A9402@bnc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know where to ask first (or what to look at) so I'd like some creative guessing by some people closer to the sources... Running the same programs on nearly identically configured -CURRENT kernels on a HP NetServer LH4 (four 550 MHz PIII Xeon with 512MB Cache, supposed to be an INTEL 450NX-based chipset) with one GB RAM and a home-grown ASUS P2-BDS based system (two 450 MHz PIII) with 512 MB RAM I find that the programs (running on the same input data) on the "smaller" machine tend to take only a third of the CPU time they need on the LH4. [Worse: The LH4 behaves like a spoilt brat when it comes to hardware, disliking the Intel EtherExpress that came with it (generating bus mastering problems after bringing it up), having interrupt routing problems with two DEC TULIP based ethernet cards sharing the same IRQ and being picky just which 3C906B-TX it gets plugged in. It's a bitch and I'd like shooting it. Oh yes - HP has been very helpful, telling me that I was at least 10 years behind wanting to run a BSD and that only WinNT, HP-Sux and Linux were supported on this hardware.] Back to the topic: Are there any reasons for these observations? If someone liked taking a closer look at it I could provide them with access to the machine (and its console). I ran out of clues... Achim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 2: 3:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 980FA14D03 for ; Sun, 16 Jan 2000 02:02:48 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 39368 invoked by uid 1001); 16 Jan 2000 10:02:01 +0000 (GMT) To: Alexander@Leidinger.net Cc: current@freebsd.org Subject: Re: crash with ffs_softdep.c 1.52 From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 15 Jan 2000 14:45:29 +0100 (CET)" References: <200001151345.OAA00557@Magelan.Leidinger.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 16 Jan 2000 11:02:01 +0100 Message-ID: <39366.948016921@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > unfortunally no core dump, but I'm able to reproduce it (I just have to > enable softupdates). > > ---snip--- > panic: softdep_disk_write_complete: lock is held > Debugger("panic") > Stopped at Debugger+0x36: mocb $0,in_Debugger.354 > db> trace > Debugger(x027c6a3) at Debugger+0x36 > panic(c028a900, c33618c0, c0a54000, c3361a10, c02a4a34) at panic+0x70 > softdep_disk_write_complete(c3361a10) at softdep_disk_write_complete+0x1f > vfs_backgroundwritedone(c3361a10, c3361a10, c0a54000, c0aa3400, c0aa3400) at vfs_backgroundwritedone+0x45 > biodone(c3361a10, c0a54014, c3361a10) at biodone+0x5a > dadone(c0aa0780, c0aa3400, c073ba20, 40000200, ffffffff) at dadone+0x202 > camisr(c02d93b4, c02a4cec, c0241b30, 4000200, c0256486) at camisr+0x1ed > swi_cambio(40000200, c0256486, c0255f21, 40000200, c0a32800) at swi_cambio+0xd > splz_swi(c073bb20, 0, 10, c0240010, 10) at splz_swi+0x14 > Xresume9() at Xresume9+0x2b > --- interrupt, eip: 0xc024c6ce, esp = 0xc02a4d34, ebp = 0 --- > default_halt() at default_halt+0x2 > ---snip-- I have a core dump here. -current from 15. January, ffs_softdep.c 1.52. Got one crash during buildworld (but didn't have core dump enabled), so last night I started a "make buildworld; rm -rf /usr/obj/whatever" loop. Sure enough, it crashed again the third time through the loop: (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc014ec9d in panic (fmt=0xc02740f4 "from debugger") at ../../kern/kern_shutdown.c:554 #2 0xc013122d in db_panic (addr=-1071349235, have_addr=0, count=-1, modif=0xcbb2acf4 "") at ../../ddb/db_command.c:433 #3 0xc01311cd in db_command (last_cmdp=0xc02a3e1c, cmd_table=0xc02a3c7c, aux_cmd_tablep=0xc02f087c) at ../../ddb/db_command.c:333 #4 0xc0131292 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc013331b in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc0247f54 in kdb_trap (type=3, code=0, regs=0xcbb2adfc) at ../../i386/i386/db_interface.c:158 #7 0xc025a878 in trap (frame={tf_fs = 24, tf_es = -1047396336, tf_ds = 16, tf_edi = -972208896, tf_esi = 256, tf_ebp = -877482428, tf_isp = -877482456, tf_ebx = -1071090464, tf_edx = -1070539680, tf_ecx = 1, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1071349235, tf_cs = 8, tf_eflags = 582, tf_esp = -1071031421, tf_ss = -1071154158}) at ../../i386/i386/trap.c:531 #8 0xc024820d in Debugger (msg=0xc0277c12 "panic") at machine/cpufunc.h:64 #9 0xc014ec94 in panic (fmt=0xc02874e0 "initiate_write_inodeblock: already started") at ../../kern/kern_shutdown.c:552 #10 0xc01fa297 in initiate_write_inodeblock (inodedep=0xc183b200, bp=0xc60d4500) at ../../ufs/ffs/ffs_softdep.c:2856 #11 0xc01fa0df in softdep_disk_io_initiation (bp=0xc60d4500) at ../../ufs/ffs/ffs_softdep.c:2743 #12 0xc018514b in spec_strategy (ap=0xcbb2aecc) at ../../miscfs/specfs/spec_vnops.c:412 #13 0xc01701a3 in bwrite (bp=0xc60d4500) at vnode_if.h:923 #14 0xc0175622 in vop_stdbwrite (ap=0xcbb2af24) at ../../kern/vfs_default.c:319 #15 0xc0175459 in vop_defaultop (ap=0xcbb2af24) at ../../kern/vfs_default.c:138 #16 0xc0171120 in vfs_bio_awrite (bp=0xc60d4500) at vnode_if.h:1172 #17 0xc0184fc2 in spec_fsync (ap=0xcbb2af7c) at ../../miscfs/specfs/spec_vnops.c:357 #18 0xc0177c93 in sched_sync () at vnode_if.h:537 #19 0xc0248974 in fork_trampoline () Cannot access memory at address 0xffe. (kgdb) up 10 #10 0xc01fa297 in initiate_write_inodeblock (inodedep=0xc183b200, bp=0xc60d4500) at ../../ufs/ffs/ffs_softdep.c:2856 2856 panic("initiate_write_inodeblock: already started"); (kgdb) l 2851 struct fs *fs; 2852 ufs_lbn_t prevlbn = 0; 2853 int i, deplist; 2854 2855 if (inodedep->id_state & IOSTARTED) 2856 panic("initiate_write_inodeblock: already started"); 2857 inodedep->id_state |= IOSTARTED; 2858 fs = inodedep->id_fs; 2859 dp = (struct dinode *)bp->b_data + 2860 ino_to_fsbo(fs, inodedep->id_ino); I had written down the routine names from the first crash - this is exactly the same crash as first time (but different from the one that Alexander Leidinger is seeing). Other details: - Abit BP6 motherboard, 2 x Celeron 366, no overclocking. IBM DPTA-372730 disk on UDMA-66 controller. Softupdates enabled on all file systems. - Kernel config file and boot messages included below. The core dump is right now being copied over a 64 kbps line, to a more accessible location, should be available in a couple of hours. If anybody would like a copy, please send me email. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- machine i386 cpu I686_CPU ident BP6_MP_ATA maxusers 32 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES options MSGBUF_SIZE=32768 options INCLUDE_CONFIG_FILE # Include this file in kernel options DDB options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa0 device pci0 device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device sym0 # NCR/Symbios Logic (do not mix with ncr, it conflicts) device scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x31 # Advanced Power Management device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? port? flags 0x40 irq 7 device ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device device pcm0 device smbus0 device iicbus0 device iicbb0 device intpm0 device smb0 at smbus? device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device ti0 # Alteon Tigon based cards (Netgear GA620 etc) pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf #Berkeley packet filter device uhci0 # UHCI PCI->USB interface device ohci0 # OHCI PCI->USB interface device usb0 # USB Bus (required) device ugen0 # Generic ---------------------------------------------------------------------- Copyright (c) 1992-2000 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: Sat Jan 15 20:26:38 CET 2000 sthaug@bp6.nethelp.no:/local/freebsd-current/src/sys/compile/BP6_MP_ATA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (367.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 256917504 (250896K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 12 IOAPIC #0 intpin 17 -> irq 5 IOAPIC #0 intpin 18 -> irq 11 IOAPIC #0 intpin 19 -> irq 10 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0363000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: port 0x9000-0x90ff mem 0xe6000000-0xe6000fff,0xe4000000-0xe4ffffff irq 12 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: port 0xa000-0xa01f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Timecounter "PIIX" frequency 3579545 Hz intpm0: port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 pcm0: port 0xa400-0xa43f irq 10 at device 9.0 on pci0 ti0: mem 0xec200000-0xec203fff irq 11 at device 11.0 on pci0 ti0: Ethernet address: 00:a0:cc:73:32:dd sym0: <875> port 0xa800-0xa8ff mem 0xec206000-0xec206fff,0xec207000-0xec2070ff irq 5 at device 13.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking fxp0: port 0xac00-0xac1f mem 0xec000000-0xec0fffff,0xec205000-0xec205fff irq 12 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:1b:45:e6 fxp1: port 0xb000-0xb01f mem 0xec100000-0xec1fffff,0xec204000-0xec204fff irq 10 at device 17.0 on pci0 fxp1: Ethernet address 00:a0:c9:b6:df:4b ata-pci1: port 0xbc00-0xbcff,0xb800-0xb803,0xb400-0xb407 irq 11 at device 19.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xb400 irq 11 on ata-pci1 ata-pci2: port 0xc800-0xc8ff,0xc400-0xc403,0xc000-0xc007 irq 11 at device 19.1 on pci0 ata-pci2: Busmastering DMA supported fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: ATA-4 disk at ata2 as master ad1: 26105MB (53464320 sectors), 53040 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA66 Waiting 3 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1d WARNING: / was not properly dismounted cd0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [337438 x 2048 byte records] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 3:32:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.iserlohn.netsurf.de (mail.iserlohn.netsurf.de [194.195.194.253]) by hub.freebsd.org (Postfix) with ESMTP id 67C9C14F47 for ; Sun, 16 Jan 2000 03:32:39 -0800 (PST) (envelope-from sascha@schumann.cx) Received: from schumann.cx (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by mail.iserlohn.netsurf.de (8.9.1/8.9.1) with SMTP id MAA32603 for ; Sun, 16 Jan 2000 12:32:56 +0100 Received: (qmail 1978 invoked from network); 16 Jan 2000 11:32:34 -0000 Received: from flaubert.foo.bar (192.168.0.99) by guerilla.foo.bar with SMTP; 16 Jan 2000 11:32:34 -0000 Received: (qmail 2941 invoked by uid 500); 16 Jan 2000 11:32:34 -0000 Date: Sun, 16 Jan 2000 12:32:34 +0100 From: Sascha Schumann To: Matthew Dillon Cc: The Hermit Hacker , Rod Taylor , freebsd-current@FreeBSD.ORG Subject: Re: Thoughts... Message-ID: <20000116123233.A2861@schumann.cx> References: <200001160526.VAA02919@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001160526.VAA02919@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Jan 15, 2000 at 09:26:08PM -0800 X-Notice: Copyright (c) 2000 Sascha Schumann. All rights reserved. X-Operating-System: Linux 2.2.14 #3 Tue Jan 11 22:09:10 CET 2000 alpha Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 15, 2000 at 09:26:08PM -0800, Matthew Dillon wrote: > > :> > :> There are lots of ways of syncing up that do not require sending the > :> entire image over the network every time. Syncing is something you could > :> do with an NFS mount quite easily, combined with something like cpdup > :> (see /usr/ports/sysutils/cpdup). > : > :we use rdist on our network to keep our production servers in sync...we > :tend to avoid 'nfs traffic' as much as possible... > : > :Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > > I've never trusted rdist for exact mirroring. I remember trying to use > it at BEST and it not getting everything right, though I can't remember > exactly what it didn't get right... probably things like devices and > hardlinks. I wound up taking the 'stat' hit and having the clients > scan the disk hierarchy for changes, and making sure the NFS server > could handle it. But you do not have to do things that way -- for example, > the server could keep track of the changes itself and send a list to > the client which the client then copies via NFS. There is also rsync which can push/pull data, handles devices and hard links correctly and which also works through ssh. Especially the latter is a nice feature, because I had to do some live mirroring once over untrusted networks. Getting secure file transfering to work was quite easy using ssh/rsync. Hardcore rdist users will miss the flexibility of their rdist.conf, but most applications can be implemented through some clever shell scripting. -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 4:22:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id DFF5714DB0 for ; Sun, 16 Jan 2000 04:22:10 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id NAA06062 for current@FreeBSD.org; Sun, 16 Jan 2000 13:22:09 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F04458863; Sun, 16 Jan 2000 12:58:15 +0100 (CET) Date: Sun, 16 Jan 2000 12:58:15 +0100 From: Ollivier Robert To: current@FreeBSD.org Subject: Re: PNPBIOS + Dell PowerEdge = panic() Message-ID: <20000116125815.A88640@keltia.freenix.fr> Reply-To: smp@FreeBSD.org Mail-Followup-To: current@FreeBSD.org References: <20000116002113.B75768@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000116002113.B75768@jade.chc-chimes.com>; from billf@chc-chimes.com on Sun, Jan 16, 2000 at 12:21:13AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bill Fumerola: > As the subject indicated PNPBIOS and Dell PowerEdge servers seem > to be a recipe for disaster. This doesn't bother me too terribly Speaking of PowerEdge, do we support them in SMP under -STABLE ? A friend of mine has tried to run 3.4-R in SMP mode on one of them and it doesn't like it apparently. Sorry if I don't have more info as he's now on vacation... It doesn't like the 2nd APIC in the system AFAIK. Any more idea ? I redirected this to "freebsd-smp" anyway. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 4:23:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from hermes.mixx.net (concorde.mixx.net [212.84.196.2]) by hub.freebsd.org (Postfix) with ESMTP id 9870F14ED2 for ; Sun, 16 Jan 2000 04:23:39 -0800 (PST) (envelope-from news-list.freebsd.current@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (Postfix) with ESMTP id F1A0E16D898 for ; Sun, 16 Jan 2000 13:23:37 +0100 (CET) Received: by mate.bln.innominate.de (Postfix, from userid 9) id 9077F2CA6D; Sun, 16 Jan 2000 13:03:55 +0100 (CET) From: news-list.freebsd.current@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.current Subject: neomagic question Date: 16 Jan 2000 12:03:51 GMT Organization: innominate AG, Berlin, Germany Lines: 25 Message-ID: Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 948024231 2339 10.0.0.13 (16 Jan 2000 12:03:51 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/4.0-CURRENT (i386)) To: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG somehow the neomagic audio driver seems to not work for the chips in the sony n505x notebook which also has this chip - first the pci id's are different chip 8039104d class 0c0010 card 8060104d chip 00101073 class 040100 card 805e104d (at least that are the two unresolved pci chips on that machine - i'm not shure which one is the audio chip) - i changed the pci id in the neomagic driver (both the av and the zx one to both of the above id's) and get a crash for the av entry and a "cannot map rsources" for the zx driver - thus my question: has anyone any other idea i may try to get this working - i'am willing to do debugging and testing if there's an idea ... also i can give any more detailed info required (btw. all this is for -current) a lot of thanks in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 4:39:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from hermes.mixx.net (concorde.mixx.net [212.84.196.2]) by hub.freebsd.org (Postfix) with ESMTP id 6564714DB5 for ; Sun, 16 Jan 2000 04:39:08 -0800 (PST) (envelope-from news-list.freebsd.current@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (Postfix) with ESMTP id 04B2316D898 for ; Sun, 16 Jan 2000 13:39:07 +0100 (CET) Received: by mate.bln.innominate.de (Postfix, from userid 9) id 2752E2CA6C; Sun, 16 Jan 2000 13:23:39 +0100 (CET) From: news-list.freebsd.current@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.current Subject: resource_list_alloc Date: 16 Jan 2000 12:23:38 GMT Organization: innominate AG, Berlin, Germany Lines: 32 Message-ID: Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 948025418 4852 10.0.0.13 (16 Jan 2000 12:23:38 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/pre-1.4-19990805 ("Preacher Man") (UNIX) (FreeBSD/4.0-CURRENT (i386)) To: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm currently trying to get the initio driver from initio ready for -current and have it working fine with an u2w controller on one machine (smp btw.) after finding out the COMPAT_PCI_DRIVER thing :-) but still have problems with an 9100 utra controller on another machine where i get: resoource_list_alloc: resource entry is busy and a panic after the probe - maybe its due to the machine (it's an pci i486 where for instance also the ide controller could not be probed via the pci device ...) - but i think it should be possible (it's not on a share irq or something - i also tried different irq's) to get this solved - so my questions are: has anyone an idea what the problem here is ? - does anyone have any good pointer to docs describing all the pci probing/ataching and resource management in the current FreeBSD ? i have put the current version of the code at ftp://ftp.innominate.org/tgr/projects/FreeBSD/iha/current/ if anyone wants to see the source the problem comes from a lot of thanks in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 6:20:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 4552414CFA for ; Sun, 16 Jan 2000 06:20:41 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (Shiva-HGW-166.fernuni-hagen.de [132.176.120.166]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id PAA19112; Sun, 16 Jan 2000 15:20:14 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <3881D3DC.DA529726@fernuni-hagen.de> Date: Sun, 16 Jan 2000 15:21:16 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: no more parallel port zip drive Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My parallel port zip-drive stopped working this weekend with the new ppc code. There is no printer attached: Here are the relevant parts of dmesg and the kernel config file. (First what CPU etc.) CPU: AMD-K6(tm) 3D processor (262.36-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 33554432 (32768K bytes) avail memory = 29876224 (29176K bytes) Preloaded elf kernel "kernel" at 0xc02bf000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ata-pci0: port 0x4000-0x400f,0x2000-0x2003,0x80400000-0x80400007,0xcc880a4-0xcc880a7,0x2143200-0x2143207 irq 0 at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode pps0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 vpo0: on ppbus0 vpo0: EPP 1.9 mode vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (5) Here are parts of the config file: # Parallel port options PPC_PROBE_CHIPSET device ppc0 at isa? port? irq 7 device ppbus0 # Parallel port bus (required) device pps0 at ppbus? device lpt0 at ppbus? # Printer device plip0 # TCP/IP over parallel device ppi0 at ppbus? # Parallel port interface device device vpo0 at ppbus? # Requires scbus and da0 -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 7: 1: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from frida.mra.si (frida.mra.si [193.2.116.133]) by hub.freebsd.org (Postfix) with ESMTP id 7D7C414A1B for ; Sun, 16 Jan 2000 07:01:03 -0800 (PST) (envelope-from vladimir.rudl@mra.si) Received: from vlado.mra ([193.2.116.2]) by frida.mra.si (8.9.3/8.9.3) with SMTP id QAA23528 for ; Sun, 16 Jan 2000 16:02:08 +0100 (CET) Received: by localhost with Microsoft MAPI; Sun, 16 Jan 2000 15:59:03 +0100 Message-ID: <01BF603A.9C6508E0.vladimir.rudl@mra.si> From: Vladimir Rudl To: "'freebsd-current@freebsd.org'" Subject: Date: Sun, 16 Jan 2000 15:59:02 +0100 Organization: MRA X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe brane@frida.mra.si To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 7:20: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 0A23414DED for ; Sun, 16 Jan 2000 07:20:03 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 129rT9-000Blq-0A; Sun, 16 Jan 2000 15:19:55 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA33613; Sun, 16 Jan 2000 15:19:59 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 16 Jan 2000 15:18:56 +0000 (GMT) From: Doug Rabson To: Thomas Graichen , graichen@innominate.de Cc: current@freebsd.org Subject: Re: resource_list_alloc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Jan 2000, Thomas Graichen wrote: > i'm currently trying to get the initio driver from initio ready for > -current and have it working fine with an u2w controller on one > machine (smp btw.) after finding out the COMPAT_PCI_DRIVER thing :-) > but still have problems with an 9100 utra controller on another > machine where i get: > > resoource_list_alloc: resource entry is busy > > and a panic after the probe - maybe its due to the machine (it's > an pci i486 where for instance also the ide controller could not > be probed via the pci device ...) - but i think it should be > possible (it's not on a share irq or something - i also tried > different irq's) to get this solved - so my questions are: has > anyone an idea what the problem here is ? - does anyone have any > good pointer to docs describing all the pci probing/ataching and > resource management in the current FreeBSD ? You are probably trying to change a resource (e.g. with bus_set_resource()) after you have previously allocated it with bus_alloc_resource(). Once a resource is allocated, it can't be changed until it is released. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 7:46: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (ns.ruhr.de [141.39.224.34]) by hub.freebsd.org (Postfix) with SMTP id C741314CE4 for ; Sun, 16 Jan 2000 07:46:02 -0800 (PST) (envelope-from robsch@robkaos.ruhr.de) Received: (qmail 57547 invoked by alias); 16 Jan 2000 15:46:01 -0000 Received: by robkaos.ruhr.de (Smail-3.2.0.107 1999-Sep-8 #1) id ; Sun, 16 Jan 2000 16:42:27 +0100 (CET) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: 3.4 -> current upgrade/bootstrap problem To: freebsd-current@freebsd.org Date: Sun, 16 Jan 2000 16:42:27 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wanted to upgrade my 3.4 system to current. I cvsuped the current sources and did a 'make buildworld'. This went fine. Now I tried 'make installworld' . This crashed with a signal 12 error in /bin/sh. I already have used current for years. For some reason I had to install 3.4 on the machine and now I wanted to go back to current. The procedure I always used was: make buildworld make installworld reboot compiling new kernel reboot Now I have a bootstrapping problem with /bin/sh (bad system call). How can I solve this problem? TIA Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 7:51:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [62.104.201.3]) by hub.freebsd.org (Postfix) with ESMTP id 6FA9214CE4 for ; Sun, 16 Jan 2000 07:51:35 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout1.freenet.de with esmtp (Exim 3.12 #2) id 129rxl-0001ED-00 for current@freebsd.org; Sun, 16 Jan 2000 16:51:33 +0100 Received: from [212.81.240.78] (helo=Magelan.Leidinger.net) by mx1.01019freenet.de with esmtp (Exim 3.12 #2) id 129rxl-00024J-00 for current@freebsd.org; Sun, 16 Jan 2000 16:51:33 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id PAA02049 for ; Sun, 16 Jan 2000 15:39:30 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001161439.PAA02049@Magelan.Leidinger.net> Date: Sun, 16 Jan 2000 15:39:29 +0100 (CET) From: Alexander Leidinger Subject: fix for apm.4 To: current@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-948033572=:2046" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-948033572=:2046 Content-Type: TEXT/plain; charset=us-ascii Hi, the patch makes apm.4 consistent with LINT ("isa?"->"nexus?"). Bye, Alexander. -- Withdrawal is for quitters. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E --0-1804289383-948033572=:2046 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment; filename="apm.diff" 21c21 < .Cd device apm0 at isa? --- > .Cd device apm0 at nexus? --0-1804289383-948033572=:2046-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 7:52: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [62.104.201.3]) by hub.freebsd.org (Postfix) with ESMTP id 718D514EBE for ; Sun, 16 Jan 2000 07:51:46 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout1.freenet.de with esmtp (Exim 3.12 #2) id 129rxr-0001EZ-00; Sun, 16 Jan 2000 16:51:39 +0100 Received: from [212.81.240.78] (helo=Magelan.Leidinger.net) by mx1.01019freenet.de with esmtp (Exim 3.12 #2) id 129rxo-00024J-00; Sun, 16 Jan 2000 16:51:37 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id QAA00543; Sun, 16 Jan 2000 16:47:37 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001161547.QAA00543@Magelan.Leidinger.net> Date: Sun, 16 Jan 2000 16:47:35 +0100 (CET) From: Alexander Leidinger Subject: Re: crash with ffs_softdep.c 1.52 To: bright@wintelcom.net Cc: peter@netplex.com.au, current@FreeBSD.ORG In-Reply-To: <20000115152625.T508@fw.wintelcom.net> MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-948037658=:540" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-948037658=:540 Content-Type: TEXT/plain; charset=us-ascii On 15 Jan, Alfred Perlstein wrote: >> >> > unfortunally no core dump, but I'm able to reproduce it (I just have to >> >> > enable softupdates). >> >> >> >> how? It looks like splbio is not up but the softdep lock is held. >> >> ^^^^ >> I just have to enable softupdates on /home, /var, /usr, /usr/obj to >> get a panic at "Additional daemons: syslogd" while booting. >> If I disable softupdates at /var I'm able to log in (X11) and dial out >> -> panic (because of fetchnews/fetchmail/whatever are accessing >> something). With only softupdates for /var I'm also able to reproduce the panic at reboot. >> > The best thing is to look at this global variable for lkt_held: >> > static struct lockit { >> > int lkt_spl; >> > pid_t lkt_held; >> > } lk; >> > >> > and see which process held the lock. Do a traceback on that process as well.. [HowTo DDB?] > http://www.freebsd.org/handbook/kerneldebug.html ---snip--- db> x/ld,2 lk lk: 0 161 db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 161 d7cebg00 d86bd000 0 160 161 000004 3 getbuf c3361ccb syslogd 160 d7cec500 d86a5000 0 6 6 004086 3 wait d7cec500 syslogd [...] 6 wait sh [...] ---snip--- How do I do a traceback on PID 161? "trace/u" outputs the same as "trace" and I haven't found anything related except "trace/u" in ddb(4). I'm still not able to get a core dump of this, perhaps a misconfiguration? fstab: ---snip--- /dev/da0s1b none swap sw 0 0 ---snip--- rc.conf: ---snip--- dumpdev="/dev/da0s1b" ---snip--- (104) netchild@ttyp2 > ll /dev/da0s1b crw-r----- 1 root operator 13, 0x00020001 1 Dez 12:41 /dev/da0s1b Kernel config and output of dmesg attached. Bye, Alexander. -- Where do you think you're going today? http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E --0-1804289383-948037658=:540 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment; filename=WORK machine i386 ident WORK maxusers 40 makeoptions DEBUG=-g makeoptions CONF_CFLAGS=-fno-builtin # # Allow user-mode programs to manipulate their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of). # #options USER_LDT #allow user-level control of i386 ldt # Options for the VM subsystem #options PQ_NOOPT # No coloring options PQ_LARGECACHE # color for 512k/16k cache #options PQ_HUGECACHE # color for 1024k/16k cache cpu I686_CPU # aka Pentium Pro(tm) options CPU_FASTER_5X86_FPU options CPU_SUSP_HLT options "NO_F00F_HACK" options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options MD5 options DDB options GDB_REMOTE_CHAT options KTRACE #kernel tracing #options PERFMON options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device bpf #Berkeley packet filter #pseudo-device disc #Discard device pseudo-device streams options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity #options IPDIVERT #divert sockets #options IPSTEALTH #support for stealth forwarding options TCP_RESTRICT_RST #restrict emission of TCP RST options ICMP_BANDLIM options FFS #Fast filesystem options CD9660 #ISO 9660 filesystem options KERNFS #Kernel filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options MFS #Memory File System #options NFS #Network File System #options NFS_NOSERVER #Disable the NFS-server code. options FFS_ROOT #FFS usable as root device options SOFTUPDATES options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L device scbus0 #base SCSI code #device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) #device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device pt0 at scbus? # SCSI processor type options CAM_MAX_HIGHPOWER=4 options SCSI_DELAY=5000# Be pessimistic about Joe SCSI device pseudo-device pty #Pseudo ttys pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) #pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. options MSGBUF_SIZE=40960 device isa0 # Enable support for the kernel PLL to use an external PPS signal, # under supervision of [x]ntpd(8) # More info in ntpd documentation: http://www.eecis.udel.edu/~ntp #options PPS_SYNC options PNPBIOS device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP="german.iso" #options KBD_DISABLE_KEYMAP_LOAD # refuse to load a keymap options KBD_INSTALL_CDEV # install a CDEV entry in /dev device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts options VESA pseudo-device splash device sc0 at isa? flags 0x06 options MAXCONS=16 # number of virtual consoles options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT="iso" options SC_HISTORY_SIZE=800 # number of history buffer lines #options SC_DISABLE_REBOOT # disable reboot key sequence device npx0 at nexus? port IO_NPX flags 0x0 irq 13 device ata0 device atadisk0 # ATA disk drives #device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives #device wdc0 at isa? port IO_WD1 irq 14 #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 #options IDE_DELAY=2000 # Be optimistic about Joe IDE device #device wfd0 device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device sio0 at isa? port IO_COM1 flags 0x20010 irq 4 device sio1 at isa? port 0x2e8 irq 10 flags 0x20000 device ed0 device pcm0 device sbc0 device joy0 device pca0 at isa? port IO_TIMER1 device apm0 at nexus? #ACPI Experimental Driver #device acpi0 device pci0 device ahc0 options AHC_ALLOW_MEMIO device smbus0 device intpm0 device smb0 at smbus? device iicbus0 device iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? options AVM_A1 device isic0 at isa? port 0x300 irq 3 flags 4 pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 2 pseudo-device "i4bctl" pseudo-device "i4brbch" 2 pseudo-device "i4btel" 1 pseudo-device "i4bipr" 2 options IPR_VJ pseudo-device "i4bisppp" 2 options PERIPH_1284 # Makes your computer act as a IEEE1284 # compliant peripheral device ppbus0 device lpt0 at ppbus? #device plip0 at ppbus? device ppi0 at ppbus? #device pps0 at ppbus? device lpbb0 at ppbus? device ppc0 at isa? port? irq 7 #options CLK_CALIBRATION_LOOP options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION device uhci0 device ohci0 device usb0 device ums0 device ukbd0 device ulpt0 device uhid0 device ugen0 --0-1804289383-948037658=:540 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment; filename="dmesg.txt" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #33: Thu Jan 13 16:29:27 CET 2000 root@Magelan.Leidinger.net:/usr/src/sys/compile/WORK Timecounter "i8254" frequency 1193273 Hz CPU: Pentium II/Celeron (400.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 134205440 (131060K bytes) avail memory = 126513152 (123548K bytes) Preloaded elf kernel "kernel" at 0xc035d000. VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc02fc9f7 (1000117) VESA: 3dfx Interactive, Inc. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: <3Dfx Voodoo 3 graphics accelerator> port 0xd800-0xd8ff mem 0xde000000-0xdfffffff,0xda000000-0xdbffffff irq 11 at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: port 0xb800-0xb80f at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: port 0xe800-0xe80f irq 9 at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ed0: port 0xa800-0xa81f irq 15 at device 10.0 on pci0 ed0: address 00:80:ad:40:bd:e7, type NE2000 (16 bit) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x6 on isa0 sc0: VGA <16 virtual consoles, flags=0x206> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x20010 on isa0 sio0: type ST16650A sio1 at port 0x2e8-0x2ef irq 10 flags 0x20000 on isa0 sio1: type ST16650A pca0 at port 0x40 on isa0 pca0: PC speaker audio driver isic0 at port 0x1b00-0x1b1f,0x16e0-0x16ff,0x6e0-0x6ff,0xee0-0xeff,0x1300-0x131f,0x300-0x31f,0xb00-0xb1f irq 3 flags 0x4 on isa0 isic0: AVM A1 or Fritz!Card Classic ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown0: at iomem 0-0x9ffff,0x100000-0x7ffffff,0xe8000-0xeffff,0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xcd000-0xcffff,0xfffe0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0x41-0x44 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown3: at port 0xf0 irq 13 on isa0 unknown4: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown: can't assign resources unknown5: at port 0xcf8-0xcff on isa0 unknown: can't assign resources sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 joy0: at port 0x200-0x207 on isa0 IP packet filtering initialized, divert disabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default i4b: ISDN call control device attached i4bisppp: 2 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 2 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 1 ISDN telephony interface device(s) attached i4brbch: 2 raw B channel access device(s) attached i4btrc: 2 ISDN trace device(s) attached ad0: ATA-0 disk at ata0 as master ad0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO3 afd0: rewriteable drive at ata0 as slave afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: 4096KB/s, transfer limit 64 blks, PIO0 afd0: Medium: Unknown media (0x0) Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4100MB (8398656 512 byte sectors: 255H 63S/T 522C) cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted ed0: device timeout --0-1804289383-948037658=:540-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 10: 1:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id B6DDD14EA1 for ; Sun, 16 Jan 2000 10:01:40 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (mailhost.houabg.com [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id MAA10591 for ; Sun, 16 Jan 2000 12:41:56 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from 216-118-21-147.pdq.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id ZXZ46QMK; Sun, 16 Jan 2000 12:05:52 -0600 Message-ID: <03db01bf604c$dae9ce40$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Robert Schien" , References: Subject: Re: 3.4 -> current upgrade/bootstrap problem Date: Sun, 16 Jan 2000 12:09:38 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The procedure for going form 3.4 to -current is make your -current kernel reboot do make world make -current kernel again ----- Original Message ----- From: "Robert Schien" To: Sent: Sunday, January 16, 2000 9:42 AM Subject: 3.4 -> current upgrade/bootstrap problem > I wanted to upgrade my 3.4 system to current. I cvsuped the current sources > and did a 'make buildworld'. This went fine. > Now I tried 'make installworld' . This crashed with a signal 12 error > in /bin/sh. > I already have used current for years. For some reason I had to install > 3.4 on the machine and now I wanted to go back to current. > > The procedure I always used was: > make buildworld > make installworld > reboot > compiling new kernel > reboot > > Now I have a bootstrapping problem with /bin/sh (bad system call). > > How can I solve this problem? > > TIA > Robert > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 10:15:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 613C914CB5 for ; Sun, 16 Jan 2000 10:15:57 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA05686; Sun, 16 Jan 2000 10:14:48 -0800 (PST) Message-Id: <200001161814.KAA05686@implode.root.com> To: Achim Patzner Cc: current@FreeBSD.ORG Subject: Re: Current, XEON and MP performance In-reply-to: Your message of "Sun, 16 Jan 2000 10:39:35 +0100." <20000116103935.A9402@bnc.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Jan 2000 10:14:48 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I don't know where to ask first (or what to look at) so I'd like some >creative guessing by some people closer to the sources... > >Running the same programs on nearly identically configured -CURRENT kernels >on a HP NetServer LH4 (four 550 MHz PIII Xeon with 512MB Cache, supposed to >be an INTEL 450NX-based chipset) with one GB RAM and a home-grown ASUS >P2-BDS based system (two 450 MHz PIII) with 512 MB RAM I find that the >programs (running on the same input data) on the "smaller" machine tend to >take only a third of the CPU time they need on the LH4. [Worse: The LH4 >behaves like a spoilt brat when it comes to hardware, disliking the Intel >EtherExpress that came with it (generating bus mastering problems after >bringing it up), having interrupt routing problems with two DEC TULIP based >ethernet cards sharing the same IRQ and being picky just which 3C906B-TX it >gets plugged in. It's a bitch and I'd like shooting it. Oh yes - HP has been >very helpful, telling me that I was at least 10 years behind wanting to run >a BSD and that only WinNT, HP-Sux and Linux were supported on this hardware.] > >Back to the topic: Are there any reasons for these observations? If someone >liked taking a closer look at it I could provide them with access to the >machine (and its console). I ran out of clues... What about wall-clock time? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 10:44:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 643F814EC4 for ; Sun, 16 Jan 2000 10:44:16 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA55572; Sun, 16 Jan 2000 10:43:58 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 16 Jan 2000 10:43:58 -0800 (PST) From: Doug White To: "Vladimir B. Grebeschikov" Cc: current@FreeBSD.ORG Subject: Re: syslogd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jan 2000, Vladimir B. Grebeschikov wrote: > On Sat, 15 Jan 2000, Doug White wrote: > > > > # log firewall messages ONLY in this file (noy in messages below) > > > !!ipfw > > > *.* /var/log/ipfw > > > > This is a bad example. ipfw messages come from the kernel so you can't > > filter those. > > it really works, try it Oh. Heh. I stand corrected. My sincere apologies. Now that's cleared up, I'd agree that your suggestion would be a useful feature. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 11:21:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1CC4F14C91 for ; Sun, 16 Jan 2000 11:21:27 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40327>; Mon, 17 Jan 2000 06:13:34 +1100 Content-return: prohibited From: Peter Jeremy Subject: ATA errors To: freebsd-current@FreeBSD.ORG Message-Id: <00Jan17.061334est.40327@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 06:13:33 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whilst my -current system has stopped crashing every night, I got some odd log messages last night. At the time the system should have been doing a cvs update (or possibly a make world). There was nothing in the CD-ROM (ata0-slave) at the time. I'm running the latest version of ata (about 7 days old). Jan 17 00:48:45 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Jan 17 00:48:45 gsmx07 /kernel: ata1: resetting devices .. done Jan 17 00:48:45 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:48:45 gsmx07 /kernel: ata0: resetting devices .. done Jan 17 00:49:56 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Jan 17 00:49:56 gsmx07 /kernel: ata1: resetting devices .. done Jan 17 00:49:56 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:49:56 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:56 gsmx07 /kernel: ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:56 gsmx07 /kernel: done Jan 17 00:49:56 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:49:56 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:56 gsmx07 /kernel: ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:56 gsmx07 /kernel: done Jan 17 00:49:56 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Jan 17 00:49:56 gsmx07 /kernel: ata1: resetting devices .. done Jan 17 00:49:56 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:49:56 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:56 gsmx07 /kernel: ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: done Jan 17 00:49:57 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:49:57 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: done Jan 17 00:49:57 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting Jan 17 00:49:57 gsmx07 /kernel: ad2: ad_timeout: trying fallback to PIO mode Jan 17 00:49:57 gsmx07 /kernel: ata1: resetting devices .. done Jan 17 00:49:57 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:49:57 gsmx07 /kernel: ad0: ad_timeout: trying fallback to PIO mode Jan 17 00:49:57 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: done Jan 17 00:49:57 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting Jan 17 00:49:57 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: ata0-slave: timeout waiting for command=ef s=00 e=64 Jan 17 00:49:57 gsmx07 /kernel: done The relevant probe messages are: Jan 14 07:37:02 gsmx07 /kernel: The Regents of the University of California. All rights reserved. Jan 14 07:37:02 gsmx07 /kernel: FreeBSD 4.0-CURRENT #25: Fri Jan 14 07:35:47 EST 2000 Jan 14 07:37:02 gsmx07 /kernel: root@:/3.0/cvs/src/sys/compile/gsmx Jan 14 07:37:02 gsmx07 /kernel: CPU: Pentium II (267.31-MHz 686-class CPU) Jan 14 07:37:02 gsmx07 /kernel: Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Jan 14 07:37:02 gsmx07 /kernel: pcib0: on motherboard Jan 14 07:37:02 gsmx07 /kernel: pci0: on pcib0 Jan 14 07:37:02 gsmx07 /kernel: pcib1: at device 1.0 on pci0 Jan 14 07:37:02 gsmx07 /kernel: pci1: on pcib1 Jan 14 07:37:02 gsmx07 /kernel: isab0: at device 7.0 on pci0 Jan 14 07:37:02 gsmx07 /kernel: isa0: on isab0 Jan 14 07:37:02 gsmx07 /kernel: ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 Jan 14 07:37:02 gsmx07 /kernel: ata-pci0: Busmastering DMA supported Jan 14 07:37:02 gsmx07 /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Jan 14 07:37:02 gsmx07 /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Jan 14 07:37:02 gsmx07 /kernel: ata-isa0: already registered as ata0 Jan 14 07:37:02 gsmx07 /kernel: ata-isa1: already registered as ata1 Jan 14 07:37:02 gsmx07 /kernel: ad0: ATA-3 disk at ata0 as master Jan 14 07:37:02 gsmx07 /kernel: ad0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S Jan 14 07:37:02 gsmx07 /kernel: ad0: 16 secs/int, 1 depth queue, UDMA33 Jan 14 07:37:02 gsmx07 /kernel: ad2: ATA-0 disk at ata1 as master Jan 14 07:37:02 gsmx07 /kernel: ad2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S Jan 14 07:37:02 gsmx07 /kernel: ad2: 16 secs/int, 1 depth queue, WDMA2 Jan 14 07:37:02 gsmx07 /kernel: acd0: CDROM drive at ata0 as slave Jan 14 07:37:02 gsmx07 /kernel: acd0: read 1723KB/s (1723KB/s), 256KB buffer, PIO4 Jan 14 07:37:02 gsmx07 /kernel: acd0: Reads: CD-R, CD-RW, CD-DA stream Jan 14 07:37:02 gsmx07 /kernel: acd0: Audio: play, 16 volume levels Jan 14 07:37:02 gsmx07 /kernel: acd0: Mechanism: ejectable tray Jan 14 07:37:02 gsmx07 /kernel: acd0: Medium: no/blank disc inside, unlocked The config file is: # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata2 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering Does anyone have any suggestions? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 11:57: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 7B10C151EC for ; Sun, 16 Jan 2000 11:56:55 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 64BD33E39; Sun, 16 Jan 2000 20:56:50 +0100 (CET) Date: Sun, 16 Jan 2000 20:56:50 +0100 From: Jesper Skriver To: current@FreeBSD.org Subject: apm suspend ?? Message-ID: <20000116205650.A64495@skriver.dk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="envbJBWh7q8WU6mo" X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Hi, Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now suspend doesn't work as expected. When I run 'apm -z' the laptop suspends as normal, but right after this the harddisk led turns on, and it powers up again. Any ideas ? dmesg attached /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #6: Sun Jan 16 19:50:21 CET 2000 root@tam:/usr/src/sys/compile/TAM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (363.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 66912256 (65344K bytes) config> q avail memory = 61820928 (60372K bytes) Preloaded elf kernel "kernel" at 0xc02f6000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f609c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: mem 0x70400000-0x704fffff,0x70000000-0x703fffff,0xe0000000-0xe0ffffff irq 11 at device 0.0 on pci1 pcic-pci0: mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 pcic-pci1: mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 csa0: mem 0x50000000-0x500fffff,0x50100000-0x50100fff irq 11 at device 6.0 on pci0 pcm0: on csa0 ac97: dac not ready isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: port 0x8400-0x841f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0xefa0-0xefaf at device 7.3 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic: polling mode pcic: polling mode pcic0: on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 ad0: ATA-4 disk at ata0 as master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s2a pccard: card inserted, slot 0 pccard: card inserted, slot 1 ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 10 slot 0 on pccard0 ep0: Ethernet address 00:60:97:88:a0:cf ep0: unload stray irq 10 pccard: card disabled, slot 0 pccard: card disabled, slot 1 pccard: card inserted, slot 0 pccard: card inserted, slot 1 resumed from suspended mode (slept 00:00:11) ata0: resetting devices .. done ata1: resetting devices .. done ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 10 slot 0 on pccard0 ep0: Ethernet address 00:60:97:88:a0:cf --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 12:12:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id A356B14DCB for ; Sun, 16 Jan 2000 12:12:48 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (Shiva-HGW-091.fernuni-hagen.de [132.176.120.91]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id VAA20082; Sun, 16 Jan 2000 21:12:24 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <38822668.5D9FFC8B@fernuni-hagen.de> Date: Sun, 16 Jan 2000 21:13:28 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: when the modem rings twice .... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my freebsd box goes down, something strange happens, when a ring signal is detected. I have apm disabled in the bios and no apm device in the config file. It is "alsmost a reset", like a short power failure. The screen is disturbed for a moment. The same happens when the alt+bs key is pressed with XFree btw. The modem sent a ring signal during a build world. I had to reformat the root partition afterwards. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 12:23: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 321DA15359 for ; Sun, 16 Jan 2000 12:22:41 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id PAA03056; Sun, 16 Jan 2000 15:25:17 -0500 From: Bill Paul Message-Id: <200001162025.PAA03056@skynet.ctr.columbia.edu> Subject: Re: Current, XEON and MP performance To: ap@bnc.net (Achim Patzner) Date: Sun, 16 Jan 2000 15:25:15 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <20000116103935.A9402@bnc.net> from "Achim Patzner" at Jan 16, 2000 10:39:35 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4264 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Achim Patzner had to walk into mine and say: > I don't know where to ask first (or what to look at) so I'd like some > creative guessing by some people closer to the sources... > > Running the same programs on nearly identically configured -CURRENT kernels > on a > HP NetServer LH4 > (four 550 MHz PIII Xeon with 512MB Cache, 512MB cache? I think you mean KB. > supposed to be an INTEL 450NX-based chipset) > with one GB RAM > and a home-grown ASUS P2-BDS based system > (two 450 MHz PIII) > with 512 MB RAM > I find that the > programs (running on the same input data) on the "smaller" machine tend to > take only a third of the CPU time they need on the LH4. Can you show us the actual results from your testing (an hopefully your testing methods as well) that led you to this conclusion? Details matter. Are these programs I/O bound, CPU bound, or a little of both? FreeBSD's SMP support still depends largely on the big giant lock approach which means that while you can indeed get processes running on multiple CPUs at the same time, you end up using only one CPU once you enter the kernel. And you have to enter the kernel in order to perform any disk, network or even console I/O. If your programs suck large datasets into memory, do lots of number crunching on them, then spit the results back out to a disk file, then they should benefit from more CPUs. However if they read and write data a lot while running, you're going to be limited by the big giant lock. There may also be scalability issues (i.e. does FreeBSD perform better as you add more CPUs or does it spend so much time trying to stay out of its own way that it actually performs worse) however I don't know enough to say if you could be running into such problems as the only SMP machines I have access to have only 2 CPUs. > [Worse: The LH4 > behaves like a spoilt brat when it comes to hardware, disliking the Intel > EtherExpress that came with it (generating bus mastering problems after > bringing it up), Which model Intel EtherExpress? What chipset? What bus mastering problems exactly? > having interrupt routing problems with two DEC TULIP based > ethernet cards sharing the same IRQ Which tulip cards? What driver? What kind of problems? I find it unusual that two PCI devices would wind up with the same IRQ with the APIC enabled since it's supposed to give you a lot more IRQs than in UP mode. > and being picky just which 3C906B-TX it > gets plugged in. There is no such card as a 3c906B. There's a 3c905B, and there's a 3c905C. Unfortunately, 3Com did go through several different ASIC revisions with the 3c905B series, some of which work better than others, but again, I see no details here. > It's a bitch and I'd like shooting it. Oh yes - HP has been > very helpful, telling me that I was at least 10 years behind wanting to run > a BSD and that only WinNT, HP-Sux and Linux were supported on this hardware.] If somebody at HP actually told you that HP-UX runs on anything besides the PA-RISC architecture (and, in the distant past, the m68k architecture), they were either a) jerking your chain, b) working at HP in an parallel dimension, c) misinformed, or d) not terribly bright. (I'm sure HP wouldn't mind having HP-UX/x86, but they certainly don't offer it as a product now.) > Back to the topic: Are there any reasons for these observations? If someone > liked taking a closer look at it I could provide them with access to the > machine (and its console). I ran out of clues... Hard to tell really without more info. We don't know what your test programs do, so it's impossible to predict what their behavior should or shouldn't be. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 12:33:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust74.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C37FE14BE6; Sun, 16 Jan 2000 12:33:23 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sun, 16 Jan 2000 15:33:21 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Bryan Liesner Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA CD-R problems, still... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you try this patch to src/usr.sbin/burncd, and see if things work after that? Thanks! (BTW, there's also an extra feature in there, hope you don't mind :) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' Index: burncd.c =================================================================== RCS file: /usr2/ncvs/src/usr.sbin/burncd/burncd.c,v retrieving revision 1.4 diff -u -r1.4 burncd.c --- burncd.c 2000/01/15 15:51:47 1.4 +++ burncd.c 2000/01/16 03:56:18 @@ -38,8 +38,9 @@ #include #include #include +#include -#define BLOCKS 32 +#define BLOCKS 16 static int fd, saved_block_size; void cleanup(int); @@ -142,8 +143,13 @@ err(EX_IOERR, "ioctl(CDRIOCNEXTWRITEABLEADDR)"); if (!quiet) { + struct stat sb; + + if (fstat(file, &sb) < 0) + err(EX_IOERR, "fstat(%s)", argv[arg]); fprintf(stderr, "next writeable LBA %d\n", addr); - fprintf(stderr, "writing from file %s\n", argv[arg]); + fprintf(stderr, "writing from file %s - %d KB\n", + argv[arg], sb.st_size / (1 << 10)); } lseek(fd, 0, SEEK_SET); size = 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 13: 2:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 86D981539C for ; Sun, 16 Jan 2000 13:02:06 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA05815; Sun, 16 Jan 2000 22:01:45 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Peter Wemm Cc: "Cameron Grant" , freebsd-current@FreeBSD.ORG Subject: Re: newpcm References: <20000111151945.9C6DD1CD1@overcee.netplex.com.au> From: Dag-Erling Smorgrav Date: 16 Jan 2000 22:01:45 +0100 In-Reply-To: Peter Wemm's message of "Tue, 11 Jan 2000 23:19:45 +0800" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: > Dag-Erling Smorgrav wrote: > > My SB128 still doesn't attach: > Does the following hack work? Beautifully! DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 13:23:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E3D915373 for ; Sun, 16 Jan 2000 13:23:23 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA24048 for ; Sun, 16 Jan 2000 12:33:48 -0800 Date: Sun, 16 Jan 2000 12:33:47 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: does this look broken to you? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) Alpha's don't have a trap.h... 2) Why are derived files ending up in the source tree? Yes, this is after a make obj. -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/alpha DESTDIR=/usr/obj/usr/src/alpha INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=alpha TOOLS_PREFIX=/usr/obj/usr/src/alpha PATH=/usr/obj/usr/src/alpha/usr/sbin:/usr/obj/usr/src/alpha/usr/bin:/usr/obj/usr/src/alpha/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools cd /usr/src/games/fortune/strfile; make obj; make depend; make all; make install /usr/obj/usr/src/alpha/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/alpha/usr/include /usr/src/games/fortune/strfile/strfile.c cd /usr/src/games/fortune/strfile; make _EXTRADEPEND echo strfile: /usr/obj/usr/src/alpha/usr/lib/libc.a >> .depend make: don't know how to make /usr/include/machine/trap.h. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 14:40:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from gate.lustig.com (h08002be407ad.ne.mediaone.net [24.128.156.91]) by hub.freebsd.org (Postfix) with SMTP id E21BE150E9 for ; Sun, 16 Jan 2000 14:40:24 -0800 (PST) (envelope-from barry@lustig.com) Received: (qmail 65274 invoked from network); 16 Jan 2000 22:40:19 -0000 Received: from devious.lustig.com (205.246.2.244) by gate.lustig.com with SMTP; 16 Jan 2000 22:40:19 -0000 Received: (qmail 20161 invoked by uid 1001); 16 Jan 2000 22:40:19 -0000 Message-ID: <20000116224019.20160.qmail@devious.lustig.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach_patches v148.2) In-Reply-To: <20000114203240.C1626@hal.mpn.cp.philips.com> X-Nextstep-Mailer: Mail 4.2mach_patches [i386] (Enhance 2.2p2) Received: by NeXT.Mailer (1.148.2.RR) From: Barry Lustig Date: Sun, 16 Jan 2000 17:40:18 -0500 To: Jos Backus Subject: Re: Possible IPv6-related problem Cc: current@freebsd.org Reply-To: barry@Lustig.COM References: <20000114203240.C1626@hal.mpn.cp.philips.com> X-Organizations: Barry Lustig & Associates, Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you try the following patch to qmail: --- ipme.c.~1~ Mon Jun 15 06:53:16 1998 +++ ipme.c Sat Nov 20 18:21:26 1999 @@ -48,7 +48,7 @@ if ((s = socket(AF_INET,SOCK_STREAM,0)) == -1) return -1; - len = 256; + len = 1024; for (;;) { if (!stralloc_ready(&buf,len)) { close(s); return 0; } buf.len = 0; Qmail wasn't iterating through the available interfaces properly and would overwrite its stack. This patch took care of the problem for me. barry On Fri, 14 Jan 2000, Jos Backus wrote: > Fyi: this afternoon, after a make world, kernel build and a reboot I was > seeing the following in my mail log: > > 2000-01-14 17:09:09.846441500 new msg 15377 > 2000-01-14 17:09:09.846838500 info msg 15377: bytes 277 from > t.com> qp 545 uid 666 > 2000-01-14 17:09:09.858416500 starting delivery 27: msg 15377 to remote > jbackus@ plex > .nl > 2000-01-14 17:09:09.858685500 status: local 0/10 remote 1/20 > 2000-01-14 17:09:09.868815500 delivery 27: failure: > Sorry,_I_couldn't_find_any_h ost_ > named_??????????O?????????gif2?._(#5.1.2)/ > 2000-01-14 17:09:09.870004500 status: local 0/10 remote 0/20 > 2000-01-14 17:09:09.977818500 bounce msg 15377 qp 547 > 2000-01-14 17:09:09.978254500 end msg 15377 > 2000-01-14 17:09:10.093495500 new msg 15657 > 2000-01-14 17:09:10.093829500 info msg 15657: bytes 871 from <> qp 547 uid > 106 2000-01-14 17:09:10.104767500 starting delivery 28: msg 15657 to > remote Jos.Back us@n > l.origin-it.com > 2000-01-14 17:09:10.105033500 status: local 0/10 remote 1/20 > 2000-01-14 17:09:10.114447500 delivery 28: failure: > Sorry,_I_couldn't_find_any_h ost_ > named_??????O?????????gif1?0??,._(#5.1.2)/ > 2000-01-14 17:09:10.115695500 status: local 0/10 remote 0/20 > 2000-01-14 17:09:10.132110500 bounce msg 15657 qp 549 > 2000-01-14 17:09:10.132548500 end msg 15657 > > The strange hostname should have been the name of our local smarthost. > After taking > > options INET6 #IPv6 communications protocols > options IPSEC #IP security > options IPSEC_ESP #IP security (crypto; define w/ IPSEC) > options IPSEC_IPV6FWD #IP security tunnel for IPv6 > options IPSEC_DEBUG #debug for IP security > > out of the kernel, the problem went away. > > I'm assuming this is related to the IPv6 changes because I have these > additional interfaces: > > gif0: flags=8010 mtu 1280 > gif1: flags=8010 mtu 1280 > > and those interface names show up in the garbage. The library call > involved seems to be res_query(). > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 14:51: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from queeg.ludd.luth.se (queeg.ludd.luth.se [130.240.16.109]) by hub.freebsd.org (Postfix) with ESMTP id A24D014E18 for ; Sun, 16 Jan 2000 14:50:58 -0800 (PST) (envelope-from dateck@ludd.luth.se) Received: from sister.ludd.luth.se (dateck@sister.ludd.luth.se [130.240.16.77]) by queeg.ludd.luth.se (8.9.3/8.9.3) with ESMTP id XAA02661 for ; Sun, 16 Jan 2000 23:50:53 +0100 (CET) From: Tomas Klockar Received: (dateck@localhost) by sister.ludd.luth.se (8.6.11/8.6.11) id XAA24355 for freebsd-current@freebsd.org; Sun, 16 Jan 2000 23:50:52 +0100 Message-Id: <200001162250.XAA24355@sister.ludd.luth.se> Subject: Current freezes up on my machine To: freebsd-current@freebsd.org Date: Sun, 16 Jan 100 23:50:52 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have discovered that whenever i use the ntp daemon my computer freezes up. It does not freeze immeditly. A random time after boot it freezes, without the ntp it works completely without any problem. I compiled and installed, both world and kernal the 10 of january. To me it feels like a deadlock caused by ntpd. The only way out of this problem is pushing the reset button or the power switch. btw the manpages for ntpd is still called xntpd, although that might have been fixed today. If there is anything else needed from me to help solve this problem please tell me what to do. Best regards, Tomas Klockar The output from dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Mon Jan 10 23:57:19 CET 2000 dateck@cyberspace.campus.luth.se:/usr/src/sys/compile/CYBERSPACE Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (332.90-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 167772160 (163840K bytes) avail memory = 159391744 (155656K bytes) Preloaded elf kernel "kernel" at 0xc02fb000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 chip1: port 0x5f00-0x5f0f at device 7.3 on pci0 vr0: port 0x6800-0x687f mem 0xe3120000-0xe312007f irq 9 at device 9.0 on pci0 vr0: Ethernet address: 00:80:c8:eb:a1:65 miibus0: on vr0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vga-pci0: mem 0xe2000000-0xe27fffff,0xe2800000-0xe2ffffff,0xe3100000-0xe311ffff irq 9 at device 10.0 on pci0 pci0: unknown card (vendor=0x1105, dev=0x8300) at 11.0 irq 9 ncr0: port 0x6c00-0x6cff mem 0xe3121000-0xe31210ff irq 10 at device 12.0 on pci0 isa0: unexpected tag 14 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ep0: not probed (disabled) joy0 at port 0x201 on isa0 gusc0: at port 0x220-0x22f,0x320-0x327,0x32c-0x32f irq 11 drq 5,7 on isa0 pcm0: on gusc0 unknown0: on isa0 joy1: at port 0x200 on isa0 unknown1: at port 0x388-0x389 irq 5 drq 1 on isa0 unknown2: at port 0x330-0x331 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: ATA-2 disk at ata0 as slave ad1: 2446MB (5009760 sectors), 4970 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, WDMA2 acd0: DVD-ROM drive at ata1 as master acd0: read 2062KB/s (4125KB/s), 256KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA, DVD-ROM, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/wd1s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-CCS device da0: 3.300MB/s transfers da0: 312MB (640299 512 byte sectors: 64H 32S/T 312C) da2 at ncr0 bus 0 target 5 lun 0 da2: Removable Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: 96MB (196608 512 byte sectors: 64H 32S/T 96C) da1 at ncr0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) -- Tomas Klockar can be found at the following adresses: Kårhusvägen 4:23 | Furuvägen 102 | dateck@ludd.luth.se 977 54 Luleå | 871 52 Härnösand | dateck@solace.mh.se Tel: +46-920-231335 | Tel: +46-611-13393 | d94-tkl@sm.luth.se Mob: +46-70-664 33 26 | Mob: +46-70-374 0 347 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 17: 9:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id A71081508B; Sun, 16 Jan 2000 17:09:22 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-2.blackbox-2.netaxs.com (dyn-2.blackbox-2.netaxs.com [207.106.60.2]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id UAA08270; Sun, 16 Jan 2000 20:09:15 -0500 (EST) Date: Sun, 16 Jan 2000 20:09:14 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: green@FreeBSD.org Cc: sos@FreeBSD.org, current@FreeBSD.org Subject: Re: ATA CD-R problems, still... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jan 2000, Brian Fundakowski Feldman wrote: >Can you try this patch to src/usr.sbin/burncd, and see if things work >after that? Thanks! (BTW, there's also an extra feature in there, hope >you don't mind :) > Yes, I burned a full 650MB onto a CD-R disk. No problems at all. And I see just changing the definition of BLOCKS from 32 to 16 did the trick. I thought there was going to be a lot of digging into the ATAPI driver to get this fixed. Thanks! Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 17:39:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 3EDF914C2D for ; Sun, 16 Jan 2000 17:39:44 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id MAA50562; Mon, 17 Jan 2000 12:39:33 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma050555; Mon, 17 Jan 00 12:39:08 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.2) with ESMTP id MAA04644; Mon, 17 Jan 2000 12:39:12 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Mon, 17 Jan 2000 12:39:12 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: "David W. Chapman Jr." Cc: Robert Schien , freebsd-current@FreeBSD.ORG Subject: Re: 3.4 -> current upgrade/bootstrap problem In-Reply-To: <03db01bf604c$dae9ce40$931576d8@inethouston.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Jan 2000, David W. Chapman Jr. wrote: > The procedure for going form 3.4 to -current is > > make your -current kernel > reboot > do make world > make -current kernel again I have just successfully done this. I had problems trying to compile with gcc 2.7.2 so I installed the gcc 2.95 package and did all my compiles using it. Here is what I did... 1. install gcc 2.95 port. 2. cd /usr/bin and rename cc and gcc to *.old and symlink cc and gcc to /usr/local/bin/gcc295 (Remember to delete the .old entries once you're finished) I did the cc/gcc rename as the buildworld kept complaining that it couldn't find gcc295. :( Then I built the 4.0-CURRENT config so I could build a kernel. 2. update to current sources (cd /usr ; cvs co src) 3. cd /usr/src/usr.sbin/config 4. "make ; make install" Created and built the new kernel. 5. cd /usr/src/sys/i386/conf 6. create new kernel config file 7. config -r KERNEL 8. cd /usr/src/sys/compile/KERNEL 9. "make depend ; make ; make install" Then booted into the kernel to do the rest of the install. 10. reboot into single user mode (boot -s) 11. mount / /usr /var /tmp (readwrite) 12. cd /usr/src 13. "make buildworld" (I think at this point I had problems using the "-j14" parm) 14. "make installworld" 15. cd /etc 16. run "mergemaster" and update your configuration 17. reboot into 4.0-CURRENT Then I rebuilt the kernel with a complete 4.0-CURRENT toolset. 18. cd /usr/src/sys/i386/conf 19. "config -r KERNEL" 20. cd /usr/src/sys/compile/KERNEL 21. "make depend ; make ; make install" 22. reboot This was done on a Dell PowerEdge 2300 with Dual PIII 450s, 512Mb RAM and 54Gb disk (3 x 9Gb in a Vinum stripe). Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 17:45:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7857614BF3; Sun, 16 Jan 2000 17:45:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id CAA97240; Mon, 17 Jan 2000 02:45:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001170145.CAA97240@freebsd.dk> Subject: Re: ATA CD-R problems, still... In-Reply-To: from Bryan Liesner at "Jan 16, 2000 08:09:14 pm" To: bleez@netaxs.com (Bryan Liesner) Date: Mon, 17 Jan 2000 02:45:18 +0100 (CET) Cc: green@FreeBSD.ORG, sos@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > On Sun, 16 Jan 2000, Brian Fundakowski Feldman wrote: > > >Can you try this patch to src/usr.sbin/burncd, and see if things work > >after that? Thanks! (BTW, there's also an extra feature in there, hope > >you don't mind :) > > > > Yes, I burned a full 650MB onto a CD-R disk. No problems at all. And > I see just changing the definition of BLOCKS from 32 to 16 did the > trick. I thought there was going to be a lot of digging into the > ATAPI driver to get this fixed. There really wasn't any functional changes to the driver, but there was to the util :) It is sad though that there still are so many crappy drives be made :( However I've committed the fix... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 18:26:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id DA0541504F; Sun, 16 Jan 2000 18:26:08 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-2.blackbox-2.netaxs.com (dyn-2.blackbox-2.netaxs.com [207.106.60.2]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id VAA16235; Sun, 16 Jan 2000 21:25:56 -0500 (EST) Date: Sun, 16 Jan 2000 21:25:55 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Soren Schmidt Cc: Bryan Liesner , green@FreeBSD.ORG, sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA CD-R problems, still... In-Reply-To: <200001170145.CAA97240@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Soren Schmidt wrote: >There really wasn't any functional changes to the driver, but there was >to the util :) >It is sad though that there still are so many crappy drives be made :( > >However I've committed the fix... > > >-S=F8ren > Now if we can only get my crappy tape drive to probe... :) Are future commits going to address that? =20 Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 20: 5:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-55.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.183]) by hub.freebsd.org (Postfix) with ESMTP id 56D1814E10; Sun, 16 Jan 2000 20:05:14 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id EAA00508; Mon, 17 Jan 2000 04:01:44 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA00850; Mon, 17 Jan 2000 02:38:25 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001170238.CAA00850@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@FreeBSD.org Cc: Peter Wemm Subject: PnP probing in -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 02:38:24 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Since the PnP probing code was made unconditional in the bootup routines on December 6, I've been having problems with my Adaptec 1542CP. I've got my BIOS set to ``non pnp OS'' and my 1542 set to 0x330. I've never had ``options pnp0'' in my config, and on December 6 (when isa/pnp.c and isa/pnpprobe.c started being included with isa devices rather than with ``options pnp*'', the card stopped being probed. If I skip the code in pnp_identify() in isa/pnp.c, everything works fine. Are there any plans to re-optionify this code ? I can provide more details once I rebuild my machine.... See my other post about some ata problems, coming to a -current list near you ! Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 21: 3:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3423C14CC4 for ; Sun, 16 Jan 2000 21:03:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA09817; Sun, 16 Jan 2000 21:02:57 -0800 (PST) (envelope-from dillon) Date: Sun, 16 Jan 2000 21:02:57 -0800 (PST) From: Matthew Dillon Message-Id: <200001170502.VAA09817@apollo.backplane.com> To: sthaug@nethelp.no Cc: Alexander@Leidinger.net, current@FreeBSD.ORG Subject: Re: crash with ffs_softdep.c 1.52 References: <200001151345.OAA00557@Magelan.Leidinger.net> <39366.948016921@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The core dump is right now being copied over a 64 kbps line, to a more :accessible location, should be available in a couple of hours. If anybody :would like a copy, please send me email. : :Steinar Haug, Nethelp consulting, sthaug@nethelp.no Steinar, if you can give me a private ftp or http address to obtain the core and the associated debug kernel image, Kirk (the author of softupdates) and I will be able to research the panic. I recommend gzip -9'ing the core and the debug kernel. Note that kernel core dumps may contain pieces of password files and other sensitive data and distribution of them should be strictly limited to people you trust. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 21:18:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from 24.67.43.232.sk.wave.home.com (24.67.43.232.sk.wave.home.com [24.67.43.232]) by hub.freebsd.org (Postfix) with ESMTP id 5AE3B14C1A for ; Sun, 16 Jan 2000 21:18:45 -0800 (PST) (envelope-from aam396@mail.usask.ca) Received: from localhost (aam396@localhost) by 24.67.43.232.sk.wave.home.com (8.9.3/8.9.3) with ESMTP id XAA34540 for ; Sun, 16 Jan 2000 23:19:59 -0600 (CST) (envelope-from aam396@mail.usask.ca) X-Authentication-Warning: 24.67.43.232.sk.wave.home.com: aam396 owned process doing -bs Date: Sun, 16 Jan 2000 23:19:57 -0600 (CST) From: Andrey X-Sender: aam396@hairy.animal.usask.ca To: freebsd-current@freebsd.org Subject: newbye question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I couldn't find detailed info about upgrading in the tutorials/handbook on FreeBSD.org, so I'd like to ask my question here -- Is it safe to 'make world' on a recently cvsup-ed current version while the system installed (i.e. being upgraded) is 3.4? Would there be any changes in /dev entries, network configuration (i.e. drivers changed) kernel configuration, etc, that need to be made? My question does not concern stability and possibility of crashes, but rather overall system configuration and possible conflicts with -stable... Thanx! Andrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 22:23:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id B808914F7B for ; Sun, 16 Jan 2000 22:23:48 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id BAA35911 for current@freebsd.org; Mon, 17 Jan 2000 01:52:08 -0500 (EST) (envelope-from dervish) Date: Mon, 17 Jan 2000 01:52:08 -0500 From: bush doctor To: current@freebsd.org Subject: Buildworld failing in "===> secure/usr.bin/openssl" Message-ID: <20000117015208.A35884@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From sources cvsup around 14:00 EST ... cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DNO_RSA -DNO_SSL2 -I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomUpdate' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_GetRandomBytesNeeded' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPrivateDecrypt' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPublicEncrypt' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomFinal' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPrivateEncrypt' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomInit' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPublicDecrypt' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 Stop in /usr/src/secure. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. #:^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 22:26:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2CB9914F56 for ; Sun, 16 Jan 2000 22:26:17 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA25547; Sun, 16 Jan 2000 22:26:12 -0800 Date: Sun, 16 Jan 2000 22:26:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: bush doctor Cc: current@FreeBSD.ORG Subject: Re: Buildworld failing in "===> secure/usr.bin/openssl" In-Reply-To: <20000117015208.A35884@ikhala.tcimet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has been fixed, approx 1700 EST. On Mon, 17 Jan 2000, bush doctor wrote: > >From sources cvsup around 14:00 EST ... > > cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DNO_RSA -DNO_SSL2 -I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomUpdate' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_GetRandomBytesNeeded' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPrivateDecrypt' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPublicEncrypt' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomFinal' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPrivateEncrypt' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomInit' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPublicDecrypt' > *** Error code 1 > > Stop in /usr/src/secure/usr.bin/openssl. > *** Error code 1 > > Stop in /usr/src/secure/usr.bin. > *** Error code 1 > > Stop in /usr/src/secure. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > #:^) > -- > So ya want ta hear da roots? > bush doctor > Of course I run FreeBSD!! > http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 22:30:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id D0DA91504C for ; Sun, 16 Jan 2000 22:30:09 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id BAA35987; Mon, 17 Jan 2000 01:58:27 -0500 (EST) (envelope-from dervish) Date: Mon, 17 Jan 2000 01:58:27 -0500 From: bush doctor To: Matthew Jacob Cc: current@freebsd.org Subject: Re: Buildworld failing in "===> secure/usr.bin/openssl" Message-ID: <20000117015827.A35938@ikhala.tcimet.net> References: <20000117015208.A35884@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Sun, Jan 16, 2000 at 10:26:12PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Matthew Jacob aka (mjacob@feral.com) said: > Has been fixed, approx 1700 EST. Thanxs. I knew I should have re-supped before sending to list. > > > On Mon, 17 Jan 2000, bush doctor wrote: > > > >From sources cvsup around 14:00 EST ... > > > > cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DNO_RSA -DNO_SSL2 -I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomUpdate' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_GetRandomBytesNeeded' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPrivateDecrypt' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPublicEncrypt' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomFinal' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPrivateEncrypt' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `R_RandomInit' > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSAPublicDecrypt' > > *** Error code 1 > > > > Stop in /usr/src/secure/usr.bin/openssl. > > *** Error code 1 > > > > Stop in /usr/src/secure/usr.bin. > > *** Error code 1 > > > > Stop in /usr/src/secure. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > #:^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 22:40:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 3714F15177 for ; Sun, 16 Jan 2000 22:40:27 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12A6Nf-0002ZN-00 for current@freebsd.org; Mon, 17 Jan 2000 02:15:15 -0500 Message-ID: <388361A5.B57C0EB2@netquick.net> Date: Mon, 17 Jan 2000 13:38:29 -0500 From: TrouBle Reply-To: trouble@netquick.net Organization: Hacked Furbies X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-20000114-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Buildworld failing in References: <20000117015208.A35884@ikhala.tcimet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG from 4.0-20000114-CURRENT cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -o strfile strfile.o sh /usr/src/tools/install.sh -c -s -o root -g games -m 555 strfile /usr/obj/usr/src/i386/usr/games /usr/src/tools/install.sh: Can't open /usr/src/tools/install.sh: No such file or directory *** Error code 2 Stop in /usr/src/games/fortune/strfile. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. and also check this out cpp -v Using builtin specs. gcc version 2.95.2 19991024 (release) /usr/libexec/cpp -lang-c -v -Di386 -Dunix -D__FreeBSD__=4 -D__FreeBSD_cc_version=400003 -D__i386__ -D__unix__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=400003 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__ELF__ - GNU CPP version 2.95.2 19991024 (release) (i386 FreeBSD/ELF) #include "..." search starts here: #include <...> search starts here: /usr/include /usr/include End of search list. The following default directories have been omitted from the search path: /usr/include/g++ End of omitted list. -------snip------- it just hangs here, i have to CTRL-C it -- ...and that is how we know the Earth to be banana-shaped. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 23:14:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust124.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D44C614F7C; Sun, 16 Jan 2000 23:13:57 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 17 Jan 2000 02:13:31 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Bruce Evans Cc: Stephen McKay , freebsd-current@FreeBSD.org, dt@FreeBSD.org Subject: Re: Crash from ^T during heavy paging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Jan 2000, Bruce Evans wrote: > > Please do the work, but send it to me for review. > > I didn't have a fix for this particular problem until after seeing > your first mail about it. It didn't make sense for P_INMEM to be so > apparently broken without it causing problems until recently. Using the magic of :%s:p_stats->p_\([usi]\)\(u[^a-zA-Z_0-9]\):p_\1\2:g, and just using vi to edit the headers too :), I submit the following to you for review. I'll be testing it in its entirety tomorrow, but I'm already reasonably confident this is correct. What do you think? > > Bruce -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' Index: kern_resource.c =================================================================== RCS file: /usr2/ncvs/src/sys/kern/kern_resource.c,v retrieving revision 1.53 diff -u -r1.53 kern_resource.c --- kern_resource.c 1999/11/29 11:29:03 1.53 +++ kern_resource.c 2000/01/17 07:08:31 @@ -528,7 +528,7 @@ tu += (tv.tv_usec - switchtime.tv_usec) + (tv.tv_sec - switchtime.tv_sec) * (int64_t)1000000; } - ptu = p->p_stats->p_uu + p->p_stats->p_su + p->p_stats->p_iu; + ptu = p->p_uu + p->p_su + p->p_iu; if (tu < ptu || (int64_t)tu < 0) { /* XXX no %qd in kernel. Truncate. */ printf("calcru: negative time of %ld usec for pid %d (%s)\n", @@ -542,30 +542,30 @@ iu = tu - uu - su; /* Enforce monotonicity. */ - if (uu < p->p_stats->p_uu || su < p->p_stats->p_su || - iu < p->p_stats->p_iu) { - if (uu < p->p_stats->p_uu) - uu = p->p_stats->p_uu; - else if (uu + p->p_stats->p_su + p->p_stats->p_iu > tu) - uu = tu - p->p_stats->p_su - p->p_stats->p_iu; + if (uu < p->p_uu || su < p->p_su || + iu < p->p_iu) { + if (uu < p->p_uu) + uu = p->p_uu; + else if (uu + p->p_su + p->p_iu > tu) + uu = tu - p->p_su - p->p_iu; if (st == 0) - su = p->p_stats->p_su; + su = p->p_su; else { su = ((tu - uu) * st) / (st + it); - if (su < p->p_stats->p_su) - su = p->p_stats->p_su; - else if (uu + su + p->p_stats->p_iu > tu) - su = tu - uu - p->p_stats->p_iu; + if (su < p->p_su) + su = p->p_su; + else if (uu + su + p->p_iu > tu) + su = tu - uu - p->p_iu; } - KASSERT(uu + su + p->p_stats->p_iu <= tu, + KASSERT(uu + su + p->p_iu <= tu, ("calcru: monotonisation botch 1")); iu = tu - uu - su; - KASSERT(iu >= p->p_stats->p_iu, + KASSERT(iu >= p->p_iu, ("calcru: monotonisation botch 2")); } - p->p_stats->p_uu = uu; - p->p_stats->p_su = su; - p->p_stats->p_iu = iu; + p->p_uu = uu; + p->p_su = su; + p->p_iu = iu; up->tv_sec = uu / 1000000; up->tv_usec = uu % 1000000; Index: proc.h =================================================================== RCS file: /usr2/ncvs/src/sys/sys/proc.h,v retrieving revision 1.98 diff -u -r1.98 proc.h --- proc.h 1999/12/29 04:24:45 1.98 +++ proc.h 2000/01/17 06:57:17 @@ -239,6 +239,9 @@ struct proc *p_leader; struct pasleep p_asleep; /* Used by asleep()/await(). */ void *p_emuldata; /* process-specific emulator state data */ + u_int64_t p_uu; /* previous user time (us) */ + u_int64_t p_su; /* previous system time (us) */ + u_int64_t p_iu; /* previous interrupt time (us) */ }; #define p_session p_pgrp->pg_session Index: resourcevar.h =================================================================== RCS file: /usr2/ncvs/src/sys/sys/resourcevar.h,v retrieving revision 1.15 diff -u -r1.15 resourcevar.h --- resourcevar.h 1999/12/29 04:24:46 1.15 +++ resourcevar.h 2000/01/17 06:56:17 @@ -47,9 +47,6 @@ #define pstat_startzero p_ru struct rusage p_ru; /* stats for this proc */ struct rusage p_cru; /* sum of stats for reaped children */ - u_int64_t p_uu; /* previous user time (us) */ - u_int64_t p_su; /* previous system time (us) */ - u_int64_t p_iu; /* previous interrupt time (us) */ #define pstat_endzero pstat_startcopy #define pstat_startcopy p_timer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 23:43:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5033E15108 for ; Sun, 16 Jan 2000 23:43:37 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12A6oB-0007Rh-00; Mon, 17 Jan 2000 09:42:39 +0200 From: Sheldon Hearn To: NAKAJI Hiroyuki Cc: current@FreeBSD.ORG Subject: Re: lint not working on -current? In-reply-to: Your message of "15 Jan 2000 21:59:14 +0900." <86zou77aot.fsf@xa12.heimat.gr.jp> Date: Mon, 17 Jan 2000 09:42:39 +0200 Message-ID: <28624.948094959@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Jan 2000 21:59:14 +0900, NAKAJI Hiroyuki wrote: > SH> I mailed publically a patch to fix this last week. Not a single > SH> follow-up since then, so I'll commit it now. :-) > > Related to this? Today's buildworld fails. Indeed. When I tested the change I made, I already had a working lint binary installed in /usr/bin, so I didn't notice this one. I backed out the offending change over the week-end. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 16 23:59:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 3F2F714FAF for ; Sun, 16 Jan 2000 23:59:27 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A40241CD4; Mon, 17 Jan 2000 15:59:19 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Somers Cc: freebsd-current@FreeBSD.org Subject: Re: PnP probing in -current In-Reply-To: Message from Brian Somers of "Mon, 17 Jan 2000 02:38:24 GMT." <200001170238.CAA00850@hak.lan.Awfulhak.org> Date: Mon, 17 Jan 2000 15:59:19 +0800 From: Peter Wemm Message-Id: <20000117075919.A40241CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > Hi, > > Since the PnP probing code was made unconditional in the bootup > routines on December 6, I've been having problems with my > Adaptec 1542CP. What PnP device ID does it have? static struct isa_pnp_id aha_ids[] = { {AHA1542_PNP, NULL}, /* ADP1542 */ {AHA1542_PNPCOMPAT, NULL}, /* PNP00A0 */ {0} }; ahareg.h:#define AHA1542_PNP 0x42159004 /* ADP1542 */ ahareg.h:#define AHA1542_PNPCOMPAT 0xA000D040 /* PNP00A0 */ What do you get on dmesg? Any "unknown" devices? Have you tried "options PNPBIOS" and "device aha0" (no "at isa? ..."). Can you include some lines from boot -v showing the parsing of the pnp id? Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 0:49:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4C59E14D8A; Mon, 17 Jan 2000 00:49:25 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id TAA21262; Mon, 17 Jan 2000 19:49:21 +1100 Date: Mon, 17 Jan 2000 19:49:17 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Brian Fundakowski Feldman Cc: Stephen McKay , freebsd-current@FreeBSD.org, dt@FreeBSD.org Subject: Re: Crash from ^T during heavy paging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Using the magic of :%s:p_stats->p_\([usi]\)\(u[^a-zA-Z_0-9]\):p_\1\2:g, > and just using vi to edit the headers too :), I submit the following to > you for review. I'll be testing it in its entirety tomorrow, but I'm > already reasonably confident this is correct. What do you think? The substitution has a good chance of being correct if it sort of works at all :-), except global substitions give style bugs when long lines become shorter, etc. About 2 lines are affected. > Index: proc.h > =================================================================== > RCS file: /usr2/ncvs/src/sys/sys/proc.h,v > retrieving revision 1.98 > diff -u -r1.98 proc.h > --- proc.h 1999/12/29 04:24:45 1.98 > +++ proc.h 2000/01/17 06:57:17 > @@ -239,6 +239,9 @@ > struct proc *p_leader; > struct pasleep p_asleep; /* Used by asleep()/await(). */ > void *p_emuldata; /* process-specific emulator state data */ > + u_int64_t p_uu; /* previous user time (us) */ > + u_int64_t p_su; /* previous system time (us) */ > + u_int64_t p_iu; /* previous interrupt time (us) */ > }; > > #define p_session p_pgrp->pg_session Bug: I think p_uu etc. are no longer initialized on fork. They should be in the zeroed section. They should be next to p_runtime and p_uticks, etc. for stylistic reasons. Moving code gives style bugs when the styles in different files are different. proc.h actually follows the rule about comments being filled like English sentences, as in the p_asleep line, except in sloppy FreeBSD additions like the p_emuldata line. Don't fix this. I already have. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 1: 6:26 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 57F0A14DD8; Mon, 17 Jan 2000 01:06:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4577B1CD43A for ; Mon, 17 Jan 2000 01:06:24 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 01:06:24 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Mandating USA_RESIDENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In order to know whether or not to build the patent-restricted RSA code, the openssl build needs to look at the value of USA_RESIDENT, which isn't set by default. If this value is unset, or anything other than 'NO'[*], it assumes the user is in the USA and doesn't build the RSA code (or uses RSAref if present). The problem is that a lot of ports depend on RSA being there, so we need to be able to provide it if at all possible. To that end, I'd like to add a check to 'make world' for an appropriate value of USA_RESIDENT so it definitively knows which version to build. crypto code obtained from freefall is no problem, but a lot of US people probably get theirs from internat, so that version has to be able to decide how to build. We should also ask users to pick a value in sysinstall to cover the binary installation path (and document it in the upgrade notes in case they don't use either). In the long run I'd like to see sysinstall fetching an international-version package of the openssl libraries if they choose 'no', but given the timeframe, we'll probably have to settle for documentation explaining what to do manually (i.e. pkg_add the openssl-int package, or the rsaref and openssl-usa-rsaref packages if they want RSA support). Unless Jordan's obtained advice to the contrary yet someone else will have to build the international version externally. I'll build the USA package. I'm not entirely sure this is the best way to go about things (it's a messy area) - any suggestions are welcome. Kris [*] I should make the matching more flexible. ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 1:34:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.hk.linkage.net (smtp01.hk.linkage.net [210.184.16.66]) by hub.freebsd.org (Postfix) with ESMTP id 53C8514D92 for ; Mon, 17 Jan 2000 01:34:48 -0800 (PST) (envelope-from satyajit@spnetctg.com) Received: from mail.spnetctg.com (qmailr@mail.spnetctg.com [210.184.28.8]) by smtp01.hk.linkage.net (8.8.8/8.8.8) with SMTP id RAA12801 for ; Mon, 17 Jan 2000 17:28:45 +0800 (HKT) Received: (qmail 17103 invoked from network); 17 Jan 2000 10:02:14 -0000 Received: from unknown (HELO spnetctg.com) (210.184.28.220) by mail.spnetctg.com with SMTP; 17 Jan 2000 10:02:14 -0000 Message-ID: <3882DBCD.9AE54F6A@spnetctg.com> Date: Mon, 17 Jan 2000 09:07:25 +0000 From: Satyajit Das X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: time and Date problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello I'm from bangladesh. I install FBSD 3.3 . FBSD shows 12 hours advanced from current time and also date. when i install i select Bangladesh . please inform how can i fix my current time and date. satyajit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 1:40:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 79FCC15011 for ; Mon, 17 Jan 2000 01:40:48 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id JAA05433; Mon, 17 Jan 2000 09:40:42 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3882DBCD.9AE54F6A@spnetctg.com> Date: Mon, 17 Jan 2000 09:40:42 -0000 (GMT) From: "Steve O'Hara-Smith" To: Satyajit Das Subject: RE: time and Date problem Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-00 Satyajit Das wrote: > hello > > I'm from bangladesh. > I install FBSD 3.3 . > FBSD shows 12 hours advanced from current time and also date. > when i install i select Bangladesh . > please inform how can i fix my current time and date. Set your machine CMOS clock to GMT using the bios setup controls, or use adjkerntz (see man page) to maintain your CMOS clock at wall time. PS: This would be better on -questions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 1:56:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 276A914C2D for ; Mon, 17 Jan 2000 01:56:29 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id CAA00375 for current@freebsd.org; Mon, 17 Jan 2000 02:19:24 -0800 (PST) Date: Mon, 17 Jan 2000 02:19:24 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: world broken using /usr/local/lib? Message-ID: <20000117021924.Q508@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG broken here for the last 12 hours or so: cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/speed.c cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/verify.c cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/version.c cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/x509.c cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x66a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ? do i need to rebuild a port, and why? thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 4:23:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 03DC614C1B; Mon, 17 Jan 2000 04:21:26 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id OAA76527; Mon, 17 Jan 2000 14:22:40 +0200 (EET) (envelope-from ru) Date: Mon, 17 Jan 2000 14:22:39 +0200 From: Ruslan Ermilov To: committers@FreeBSD.org, current@FreeBSD.org Cc: Peter Wemm Subject: HEADS UP: GNU texinfo has been upgraded to 4.0 Message-ID: <20000117142239.B70086@relay.ucb.crimea.ua> Mail-Followup-To: committers@FreeBSD.org, current@FreeBSD.org, Peter Wemm Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [CC'ed explicitly to Peter Wemm, because he was the person] [who requested --forceentry for install-info(1), see below] Hi! I've just upgraded our GNU texinfo to the latest available version 4.0. Please see src/contrib/texinfo/NEWS for what has been changed since 3.12. It should be built with `make world', not by simple `cvs update' and `make'. If you wonder why, please see the log message for src/gnu/usr.bin/texinfo/doc/Makefile,v 1.10. But if you need to, it is possible to build it without `world' by: make MAKEINFO=../makeinfo/makeinfo The install-info(1)'s --forceentry option has been removed, since it is (and always was) the same as stock --entry option (i.e., it overrides any INFO-DIR-ENTRY from the INFO-FILE). Happy hacking, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 4:41:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 10B4814CFF; Mon, 17 Jan 2000 04:41:21 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12ABTB-0008pg-00; Mon, 17 Jan 2000 14:41:17 +0200 From: Sheldon Hearn To: Ruslan Ermilov Cc: committers@FreeBSD.org, current@FreeBSD.org, Peter Wemm Subject: Re: HEADS UP: GNU texinfo has been upgraded to 4.0 In-reply-to: Your message of "Mon, 17 Jan 2000 14:22:39 +0200." <20000117142239.B70086@relay.ucb.crimea.ua> Date: Mon, 17 Jan 2000 14:41:17 +0200 Message-ID: <33955.948112877@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000 14:22:39 +0200, Ruslan Ermilov wrote: > I've just upgraded our GNU texinfo to the latest available version 4.0. > Please see src/contrib/texinfo/NEWS for what has been changed since 3.12. Excellent! src/contrib/texinfo/NEWS: . New markup commands: @env (for environment variables), @command (for command names), @option (for command-line options). This should allow us to back out rev 1.22. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 4:52: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [62.104.201.5]) by hub.freebsd.org (Postfix) with ESMTP id B870614BC9 for ; Mon, 17 Jan 2000 04:51:57 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout0.freenet.de with esmtp (Exim 3.12 #2) id 12ABdU-0002iX-00; Mon, 17 Jan 2000 13:51:56 +0100 Received: from [213.6.46.225] (helo=Magelan.Leidinger.net) by mx1.01019freenet.de with esmtp (Exim 3.12 #2) id 12ABdS-0002Y2-00; Mon, 17 Jan 2000 13:51:54 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id NAA08566; Mon, 17 Jan 2000 13:51:20 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001171251.NAA08566@Magelan.Leidinger.net> Date: Mon, 17 Jan 2000 13:51:19 +0100 (CET) From: Alexander Leidinger Subject: Solved(?): crash with ffs_softdep.c 1.52 To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG In-Reply-To: <200001170502.VAA09817@apollo.backplane.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've successfully booted with ffs_softdep.c 1.54, I'm doing now a full buildworld to stress the system. If you didn't hear from me it works (or my system had a crash and I'm not able to recover ;) ). Bye, Alexander. -- Too many freaks, not enough circuses. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 4:56:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mlss15.cl.msu.edu (mlss15.cl.msu.edu [35.9.4.115]) by hub.freebsd.org (Postfix) with ESMTP id AF7CC14CE1 for ; Mon, 17 Jan 2000 04:56:31 -0800 (PST) (envelope-from buchanon@mlss15.cl.msu.edu) Received: from localhost (buchanon@localhost) by mlss15.cl.msu.edu (8.9.3/8.9.3) with ESMTP id HAA93029 for ; Mon, 17 Jan 2000 07:59:35 -0500 (EST) (envelope-from buchanon@mlss15.cl.msu.edu) Date: Mon, 17 Jan 2000 07:59:34 -0500 (EST) From: Mike Buchanon To: freebsd-current@freebsd.org Subject: Problems making a kernel... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I just did a cvsup and was trying to build a kernel. The make depend failed as follows: c ../../i386/i386/vm86.c ../../i386/i386/vm_machdep.c ../../i386/isa/clock.c . ./../isa/fd.c ../../i386/isa/intr_machdep.c ../../i386/isa/ipl_funcs.c ../../i3 86/isa/isa.c ../../i386/isa/isa_compat.c ../../i386/isa/isa_dma.c ../../i386/is a/npx.c ../../i386/isa/pcaudio.c ../../i386/isa/pcibus.c ../../i386/isa/ppc.c ../../i386/isa/random_machdep.c ../../i386/isa/spkr.c ../../i386/isa/vesa.c ../ ../isa/atkbd_isa.c ../../isa/atkbdc_isa.c ../../isa/psm.c ../../isa/sio.c ../.. /isa/syscons_isa.c ../../isa/vga_isa.c ../../kern/subr_diskmbr.c ../../libkern/ divdi3.c ../../libkern/moddi3.c ../../libkern/qdivrem.c ../../libkern/udivdi3.c ../../libkern/umoddi3.c ioconf.c param.c vnode_if.c config.c ../../i386/i386/ge nassym.c ../../pci/if_xl.c:133: miibus_if.h: No such file or directory mkdep: compile failed *** Error code 1 I looked and sure enough if_xl.c isn't there. Did I miss something? Or is this just a 'in flux' thing :) TTFN, /mtb -- ,,, (. .) +--oOO--(_)--OOo---------------------------------------------+ Michael Thomas Buchanon --------- Information Technologist Home Page URL: http://manetheren.cl.msu.edu/~buchanon/ Brighter the honour hence +============================================================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 5:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-77.max2-du-ws.dialnetwork.pavilion.co.uk [212.74.8.205]) by hub.freebsd.org (Postfix) with ESMTP id C1BDB14C09; Mon, 17 Jan 2000 05:28:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA01116; Mon, 17 Jan 2000 13:11:41 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA22353; Mon, 17 Jan 2000 13:16:07 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001171316.NAA22353@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Somers Cc: freebsd-current@FreeBSD.org, Peter Wemm , Soren Schmidt Subject: Re: PnP probing in -current In-Reply-To: Message from Brian Somers of "Mon, 17 Jan 2000 02:38:24 GMT." <200001170238.CAA00850@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 13:16:06 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Hi, > > Since the PnP probing code was made unconditional in the bootup > routines on December 6, I've been having problems with my > Adaptec 1542CP. > > I've got my BIOS set to ``non pnp OS'' and my 1542 set to 0x330. > I've never had ``options pnp0'' in my config, and on December 6 (when > isa/pnp.c and isa/pnpprobe.c started being included with isa devices > rather than with ``options pnp*'', the card stopped being probed. > > If I skip the code in pnp_identify() in isa/pnp.c, everything works > fine. > > Are there any plans to re-optionify this code ? > > I can provide more details once I rebuild my machine.... See my > other post about some ata problems, coming to a -current list near > you ! Forget that. I trashed my /usr (over 20000 files were put in lost+found and I got all sorts of funny (?) things going on with fsck), but it looks like it was a hardware problem. Still, a bit nasty considering I hadn't got softupdates or an async filesystem :-( I'll try enabling ata after I've rebuilt the machine. > Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 5:30: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 7E48514C10 for ; Mon, 17 Jan 2000 05:29:57 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.151]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA23D3; Mon, 17 Jan 2000 14:29:54 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id OAA10383; Mon, 17 Jan 2000 14:29:44 +0100 (CET) (envelope-from asmodai) Date: Mon, 17 Jan 2000 14:29:44 +0100 From: Jeroen Ruigrok/Asmodai To: Andrey Cc: freebsd-current@freebsd.org Subject: Re: newbye question Message-ID: <20000117142944.B9255@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from aam396@mail.usask.ca on Sun, Jan 16, 2000 at 11:19:57PM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000117 08:00], Andrey (aam396@mail.usask.ca) wrote: >Is it safe to 'make world' on a recently cvsup-ed current version while >the system installed (i.e. being upgraded) is 3.4? I heard from some people, Will Andrews and George Cox, that it isn't easy. >Would there be any changes in /dev entries, network configuration >(i.e. drivers changed) kernel configuration, etc, that need to be made? Read /usr/src/UPDATING >My question does not concern stability and possibility of crashes, but >rather overall system configuration and possible conflicts with -stable... Your probably better off installing/upgrading by means of a snap. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project We must all hang together, else we shall all hang separately... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 6:16:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id D474314BC9 for ; Mon, 17 Jan 2000 06:16:18 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb29.imasy.or.jp [202.227.24.157]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id XAA02717; Mon, 17 Jan 2000 23:16:09 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200001171416.XAA02717@tasogare.imasy.or.jp> To: Alexander@Leidinger.net Cc: current@freebsd.org Subject: Re: fix for apm.4 In-Reply-To: Your message of "Sun, 16 Jan 2000 15:39:29 +0100 (CET)" <200001161439.PAA02049@Magelan.Leidinger.net> References: <200001161439.PAA02049@Magelan.Leidinger.net> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 17 Jan 2000 23:16:06 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the patch makes apm.4 consistent with LINT ("isa?"->"nexus?"). Committed. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 6:35:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 787E014C10 for ; Mon, 17 Jan 2000 06:35:14 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id KAA86652; Mon, 17 Jan 2000 10:03:24 -0500 (EST) (envelope-from dervish) Date: Mon, 17 Jan 2000 10:03:24 -0500 From: bush doctor To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: world broken using /usr/local/lib? Message-ID: <20000117100324.A65480@ikhala.tcimet.net> References: <20000117021924.Q508@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000117021924.Q508@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Jan 17, 2000 at 02:19:24AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Alfred Perlstein aka (bright@wintelcom.net) said: > broken here for the last 12 hours or so: > > cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/speed.c > cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/verify.c > cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/version.c > cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/x509.c > cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref > speed.o: In function `speed_main': > speed.o(.text+0x66a): undefined reference to `RSA_PKCS1_RSAref' > /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > ? > > do i need to rebuild a port, and why? Did a quick look and found the following: ikhala.tcimet.net:dervish> nm /usr/local/lib/libRSAglue.a | grep ERR_load_RSAREF_strings 00000000 T ERR_load_RSAREF_strings ikhala.tcimet.net:dervish> Do we also need a -lRSAglue? > > thanks, > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 6:37:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.2hip.net (gizmo.2hip.net [208.241.12.2]) by hub.freebsd.org (Postfix) with ESMTP id B8C5C14E0D for ; Mon, 17 Jan 2000 06:37:31 -0800 (PST) (envelope-from rnoland@gizmo.2hip.net) Received: (from rnoland@localhost) by gizmo.2hip.net (8.9.3/8.9.3) id JAA10546; Mon, 17 Jan 2000 09:37:19 -0500 (EST) (envelope-from rnoland) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14467.10527.127430.757657@gizmo.2hip.net> Date: Mon, 17 Jan 2000 09:37:19 -0500 (EST) From: "Robert C. Noland III" To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: world broken using /usr/local/lib? In-Reply-To: <20000117021924.Q508@fw.wintelcom.net> References: <20000117021924.Q508@fw.wintelcom.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You have a libcrypto in /usr/local/lib which was not compiled with rsaref. When it reaches out to get rsaref, it also picks up the libcrypto and libssl from /usr/local/lib rather than the build tree. Move them out of the way... robert. Alfred Perlstein writes: >broken here for the last 12 hours or so: > >cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/speed.c >cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/verify.c >cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/version.c >cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -c /home/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/x509.c >cc -pipe -O2 -DMONOLITH -DNO_IDEA -I/home/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/home/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref >speed.o: In function `speed_main': >speed.o(.text+0x66a): undefined reference to `RSA_PKCS1_RSAref' >/usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' >*** Error code 1 >1 error >*** Error code 2 >1 error >*** Error code 2 >1 error >*** Error code 2 >1 error >*** Error code 2 >1 error >*** Error code 2 >1 error > >? > >do i need to rebuild a port, and why? > >thanks, >-- >-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 6:54:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id E58B314D97 for ; Mon, 17 Jan 2000 06:54:11 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id GAA46564 for ; Mon, 17 Jan 2000 06:54:11 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id GAA69760 for current@freebsd.org; Mon, 17 Jan 2000 06:54:11 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001171454.GAA69760@realtime.exit.com> Subject: 3C589 problems? To: current@freebsd.org Date: Mon, 17 Jan 2000 06:54:10 -0800 (PST) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just want to know if anyone else is still having problems with their 3C589 or 574 after Matt Dodd's latest series of checkins. For my Dell Inspiron, his checkins solved the MAC address problem, but I'm still having serious problems with both cards (I have both a 589D and a 574BT). My problem shows itself in _very_ slow (on the order of 8 kB/s) and bursty traffic, like it's still not getting interrupts and is using the watchdog timer to clock packets in and out. I uncommented the printf in the ep_if_watchdog() and, sure enough, the watchdog timer is going off a _lot_. Something is seriously wrong and I'm not sure where to look next. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7: 8:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id BF57014A0B; Mon, 17 Jan 2000 07:08:36 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id HAA36080; Mon, 17 Jan 2000 07:08:11 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id HAA11385; Mon, 17 Jan 2000 07:07:21 -0800 (PST) To: Kris Kennaway Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile References: From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 17 Jan 2000 07:06:55 -0800 In-Reply-To: Kris Kennaway's message of "Sat, 15 Jan 2000 21:33:05 -0800 (PST)" Message-ID: Lines: 16 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Kris Kennaway * Openssl should now be fully functional for both US and international users * - please report any problems you have in using it to me. You should be * able to compile all openssl-using code (some of them require rsaref and * therefore cannot be used in a commercial setting, others do not), although * the ports may need tweaking to deal with the changed base location (/usr * instead of /usr/local). Should I add some stuff to handle the differences in bsd.port.mk (like we did with perl5)? For one thing, openssl is in -current only so we need a way to have ports easily depend on the openssl port in -stable. -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7:13: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 700E514C1A for ; Mon, 17 Jan 2000 07:12:59 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id B4E631F45; Mon, 17 Jan 2000 16:12:57 +0100 (CET) Date: Mon, 17 Jan 2000 16:12:57 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: TexInfo breaks buildworld Message-ID: <20000117161257.A38296@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The recent import of GNU TexInfo 4.0 seems to break buildworld. ../../../contrib/texinfo/doc/info.texi -o info.info /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/info.texi:69: N o matching `@end ifnottex'. /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/info.texi:77: U nmatched `@end'. makeinfo: Removing output file `info.info' due to errors; use --force to preserv e. *** Error code 2 -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7:13:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.hk.linkage.net (smtp01.hk.linkage.net [210.184.16.66]) by hub.freebsd.org (Postfix) with ESMTP id 14DBD14EB7 for ; Mon, 17 Jan 2000 07:13:47 -0800 (PST) (envelope-from satyajit@spnetctg.com) Received: from mail.spnetctg.com (qmailr@mail.spnetctg.com [210.184.28.8]) by smtp01.hk.linkage.net (8.8.8/8.8.8) with SMTP id XAA10456 for ; Mon, 17 Jan 2000 23:07:43 +0800 (HKT) Received: (qmail 7872 invoked from network); 17 Jan 2000 15:39:13 -0000 Received: from unknown (HELO spnetctg.com) (210.184.28.231) by mail.spnetctg.com with SMTP; 17 Jan 2000 15:39:13 -0000 Message-ID: <38832C56.6E02A394@spnetctg.com> Date: Mon, 17 Jan 2000 14:51:02 +0000 From: Satyajit Das X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: shell problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I like to use BASH shell in my user account. how can i do this ? please inform. when i install Freebsd that time I saw [D] in bash so why i'm in /bin/sh shell . satyajit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7:22: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 910B714A04 for ; Mon, 17 Jan 2000 07:22:04 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id PAA54426; Mon, 17 Jan 2000 15:21:40 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <38832C56.6E02A394@spnetctg.com> Date: Mon, 17 Jan 2000 15:21:40 -0000 (GMT) From: "Steve O'Hara-Smith" To: Satyajit Das Subject: RE: shell problem Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Jan-00 Satyajit Das wrote: > I like to use BASH shell in my user account. how can i do this ? please > inform. Install bash (either from ports or a package). Use chsh to change the entry for Shell to /usr/local/bin/bash. PS: This sort of question is better on -questions than -current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7:34:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 7324714D97 for ; Mon, 17 Jan 2000 07:34:33 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 6A51737A2 for ; Mon, 17 Jan 2000 09:34:32 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id JAA00563 for ; Mon, 17 Jan 2000 09:34:32 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Mon, 17 Jan 2000 09:34:32 -0600 (CST) From: Thomas Veldhouse To: freebsd-current@freebsd.org Subject: Current Locks up Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a problem with Current (cvsup afternoon of 01-16-2000) locking up solid. My machine did not respond to a ping from my STABLE box. I finally pushed the reset button (ATX case) and it unfreezed the box. I had a similar lockup about 1/2 hour later. Again, pressing the reset button unfroze the box. The box continued on normally. There were no errors in the logs. I was running Netscape Communicator 4.7(US) under XFree86-3.3.6 and Windowmaker. I have apm turned off. My hardware is a compaq MB (essentially the same as the FIC SD11) with an Athlon 600MHz CPU. I am using a Linksys 10/100 PCI card (version 2) using the dc0 driver. ATA seems to work wonderfully (w/o SOFTUPDATES) using async. Is this an ACPI issue? Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7:45:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 96D2A14E91 for ; Mon, 17 Jan 2000 07:45:44 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id AAA00448 for ; Tue, 18 Jan 2000 00:45:41 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp389.kt.rim.or.jp [202.247.140.89]) by mail1.rim.or.jp (3.7W/) id AAA23641 for ; Tue, 18 Jan 2000 00:45:42 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id AAA54093; Tue, 18 Jan 2000 00:45:41 +0900 (JST) Date: Tue, 18 Jan 2000 00:45:40 +0900 Message-ID: <14467.14628.579240.98517T@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Subject: 0xdeadc0de ??? User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) Cc: Jun Kuriyama MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found message below at inserting aue0 (after pccard ed0 insert/remove). ----- aue0: LUA-TX MELCO LUA-TX, rev 1.10/1.01, addr 2 aue0: Ethernet address: 00:40:26:61:10:c7 miibus0: on aue0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Data modified on freelist: word 7 of object 0xc0828400 size 364 previous type USBdev (0x0 != 0xdeadc0de) aue0: starting DAD for fe80:0003::0240:26ff:fe61:10c7 aue0: DAD complete for fe80:0003::0240:26ff:fe61:10c7 - no duplicates found ----- Should I track this behaviour (if I can revisit this message), or I can simply ignore this message? Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 7:51:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 140AC14E4D for ; Mon, 17 Jan 2000 07:51:43 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.151]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3B75; Mon, 17 Jan 2000 16:51:34 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id QAA11574; Mon, 17 Jan 2000 16:50:57 +0100 (CET) (envelope-from asmodai) Date: Mon, 17 Jan 2000 16:50:56 +0100 From: Jeroen Ruigrok/Asmodai To: Mike Buchanon Cc: freebsd-current@freebsd.org Subject: Re: Problems making a kernel... Message-ID: <20000117165056.D9255@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from buchanon@mlss15.cl.msu.edu on Mon, Jan 17, 2000 at 07:59:34AM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000117 16:01], Mike Buchanon (buchanon@mlss15.cl.msu.edu) wrote: >../../pci/if_xl.c:133: miibus_if.h: No such file or directory >mkdep: compile failed >*** Error code 1 You do have device miibus0 in your config file? -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project We must all hang together, else we shall all hang separately... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 8: 2:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust252.tnt3.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CE15214DF6; Mon, 17 Jan 2000 08:02:01 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 17 Jan 2000 11:01:53 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Bruce Evans Cc: Stephen McKay , freebsd-current@FreeBSD.org, dt@FreeBSD.org Subject: Re: Crash from ^T during heavy paging In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Bruce Evans wrote: > > Using the magic of :%s:p_stats->p_\([usi]\)\(u[^a-zA-Z_0-9]\):p_\1\2:g, > > and just using vi to edit the headers too :), I submit the following to > > you for review. I'll be testing it in its entirety tomorrow, but I'm > > already reasonably confident this is correct. What do you think? > > The substitution has a good chance of being correct if it sort of works > at all :-), except global substitions give style bugs when long lines > become shorter, etc. About 2 lines are affected. Nuts! :) > > @@ -239,6 +239,9 @@ > > struct proc *p_leader; > > struct pasleep p_asleep; /* Used by asleep()/await(). */ > > void *p_emuldata; /* process-specific emulator state data */ > > + u_int64_t p_uu; /* previous user time (us) */ > > + u_int64_t p_su; /* previous system time (us) */ > > + u_int64_t p_iu; /* previous interrupt time (us) */ > > }; > > > > #define p_session p_pgrp->pg_session > > Bug: I think p_uu etc. are no longer initialized on fork. They should be > in the zeroed section. They should be next to p_runtime and p_uticks, > etc. for stylistic reasons. Hm. I would think that the intuitive thing is them being initialized to reasonable values on a fork. I must not be very intuitive *g* > > Moving code gives style bugs when the styles in different files are > different. proc.h actually follows the rule about comments being filled > like English sentences, as in the p_asleep line, except in sloppy FreeBSD > additions like the p_emuldata line. Don't fix this. I already have. I wasn't even aware of differences in language like that between files. Maybe I'm too used to there being no sentence structure :) Thank you, though! I now understand the idea of header theory a bit better. > > Bruce > > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 8: 9:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-41.max2-du-ws.dialnetwork.pavilion.co.uk [212.74.8.169]) by hub.freebsd.org (Postfix) with ESMTP id 2E8F114E37 for ; Mon, 17 Jan 2000 08:09:11 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA00396; Mon, 17 Jan 2000 16:08:48 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA25647; Mon, 17 Jan 2000 16:13:14 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001171613.QAA25647@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Peter Wemm Cc: Brian Somers , freebsd-current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: PnP probing in -current In-Reply-To: Message from Peter Wemm of "Mon, 17 Jan 2000 15:59:19 +0800." <20000117075919.A40241CD4@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 16:13:14 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers wrote: > > Hi, > > > > Since the PnP probing code was made unconditional in the bootup > > routines on December 6, I've been having problems with my > > Adaptec 1542CP. > > What PnP device ID does it have? > > static struct isa_pnp_id aha_ids[] = { > {AHA1542_PNP, NULL}, /* ADP1542 */ > {AHA1542_PNPCOMPAT, NULL}, /* PNP00A0 */ > {0} > }; > > ahareg.h:#define AHA1542_PNP 0x42159004 /* ADP1542 */ > ahareg.h:#define AHA1542_PNPCOMPAT 0xA000D040 /* PNP00A0 */ It seems to have ADP1542. > What do you get on dmesg? Any "unknown" devices? Lots of unknown devices, wrt ADP1542: ADP1542: adding irq mask 0xdc00 ADP1542: adding dma mask 0xe0 ADP1542: start dependant ADP1542: adding io range 0x330-0x333, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x334-0x337, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x234-0x237, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x230-0x233, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x134-0x137, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x130-0x133, size=0x4, align=0x4 ADP1542: end dependant ADP1542: adding memory range 0xc8000-0xdc03f, size=0x40, align=0x4000 and a little later: > Have you tried "options PNPBIOS" and "device aha0" (no "at isa? ..."). Without saying it's ``at isa?'' I get only one aha failed line (I'm sure I used to get nothing) at boot time. I still see the ADP lines though (of course). > Can you include some lines from boot -v showing the parsing of the pnp id? Sure, well, what gets recorded by dmesg anyway - if you need anything from before the attached, I'll have to transcribe it manually or muck about with a serial console: range 0xf8000-0xfbfff, size=0x4000 PNP0c02: adding memory range 0xfc000-0xfffff, size=0x4000 PNP0c02: start dependant pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: adding io range 0x480-0x48f, size=0x10, align=0 PNP0a03: start dependant pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x40b-0x40b, size=0x1, align=0 PNP0c02: adding io range 0x4d6-0x4d6, size=0x1, align=0 PNP0c02: adding io range 0x5000-0x501f, size=0x20, align=0 PNP0c02: adding io range 0x4000-0x403f, size=0x40, align=0 PNP0c02: start dependant pnpbios: handle 10 device ID PNP0c02 (020cd041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 11 device ID PNP0501 (0105d041) PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: adding irq mask 0x40 PNP0700: start dependant pnpbios: handle 12 device ID PNP0700 (0007d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: start dependant pnpbios: handle 13 device ID PNP0400 (0004d041) PNP0501: adding irq mask 00x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 14 device ID PNP0501 (0105d041) PNP0c02: adding io range 0x208-0x20f, size=0x8, align=0 PNP0c02: start dependant pnpbios: handle 15 device ID PNP0c02 (020cd041) Trying Read_Port at 203 ADP1542: adding irq mask 0xdc00 ADP1542: adding dma mask 0xe0 ADP1542: start dependant ADP1542: adding io range 0x330-0x333, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x334-0x337, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x234-0x237, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x230-0x233, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x134-0x137, size=0x4, align=0x4 ADP1542: start dependant ADP1542: adding io range 0x130-0x133, size=0x4, align=0x4 ADP1542: end dependant ADP1542: adding memory range 0xc8000-0xdc03f, size=0x40, align=0x4000 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,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): wd0: 1221MB (2501856 sectors), 2482 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc0: unit 1 (wd1): wd1: 1623MB (3324384 sectors), 3298 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (wd2): wd2: 7339MB (15032115 sectors), 15907 cyls, 15 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1: unit 1 (atapi): , removable, accel, dma, iordis wcd0: drive speed 1378KB/sec, 256KB cache wcd0: supported read types: CD-DA wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sio0: irq maps: 0x441 0x451 0x441 0x441 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1: irq maps: 0x441 0x449 0x441 0x441 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 sio2: irq maps: 0x441 0x441 0x441 0x441 sio2: probe failed test(s): 0 1 2 4 6 7 9 sio3: configured irq 9 not in bitmap of probed irqs 0 sio3: irq maps: 0x441 0x441 0x441 0x441 sio3: probe failed test(s): 0 1 2 4 6 7 9 ppc0: parallel port found at 0x378 ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/PS2/NIBBLE_ID/PS2_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: NPAP,PJL,PCL lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 plip0: on ppbus0 bpf: lp0 attached isic0 at port 0xe80,0xa60-0xa9f,0x260-0x29f,0x660-0x69f irq 5 flags 0x3 on isa0 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) isic0: HSCX 82525 or 21525 Version 2.1 isa_probe_children: probing PnP devices unknown: can't assign resources unknown0: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown3: at port 0xf0-0xff irq 13 on isa0 unknown4: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0x100000-0x7ffffff on isa0 unknown5: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff on isa0 unknown6: at port 0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f on isa0 unknown7: at port 0x40b,0x4d6,0x5000-0x501f,0x4000-0x403f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown8: at port 0x208-0x20f on isa0 aha0: status reg test failed ff unknown9: at port 0x330-0x333 irq 11 drq 5 on isa0 de0: enabling 10baseT port BIOS Geometries: 0:026b3f3f 0..619=620 cylinders, 0..63=64 heads, 1..63=63 sectors 1:03373f3f 0..823=824 cylinders, 0..63=64 heads, 1..63=63 sectors 2:01df1f3f 0..479=480 cylinders, 0..31=32 heads, 1..63=63 sectors 3:03fe1520 0..1022=1023 cylinders, 0..21=22 heads, 1..32=32 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, unlimited logging bpf: sl0 attached bpf: sl1 attached bpf: ppp0 attached bpf: ppp1 attached new masks: bio 4008c040, tty 4003009a, net 400704ba bpf: lo0 attached i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached bpf: isp0 attached bpf: isp1 attached bpf: isp2 attached bpf: isp3 attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) bpf: ipr0 attached bpf: ipr1 attached bpf: ipr2 attached bpf: ipr3 attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached Mounting root from ufs:/dev/wd0s1a wd0s1: type 0xa5, start 63, end = 2501855, size 2501793 : OK start_init: trying /sbin/init > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 Thanks. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 8: 9:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 65CF914C88 for ; Mon, 17 Jan 2000 08:09:34 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA04447; Mon, 17 Jan 2000 11:12:09 -0500 From: Bill Paul Message-Id: <200001171612.LAA04447@skynet.ctr.columbia.edu> Subject: Re: Current, XEON and MP performance To: ap@bnc.net (Achim Patzner) Date: Mon, 17 Jan 2000 11:12:08 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <20000117122223.C9402@bnc.net> from "Achim Patzner" at Jan 17, 2000 12:22:23 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 8080 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Achim Patzner had to walk into mine and say: > > Can you show us the actual results from your testing (an hopefully your > > testing methods as well) that led you to this conclusion? Details matter. > > First test was running an apache and fcgi noticing that it took considerably > longer to respond than the old server. Next test was a number of homegrown > programs under time(1). > > > Are these programs I/O bound, CPU bound, or a little of both? > > All of it; one is page-view accounting for the current web server, others > are meteorological simulations. > > > FreeBSD's SMP support still depends largely on the big giant lock approach > > which means that while you can indeed get processes running on multiple > > CPUs at the same time, you end up using only one CPU once you enter the > > kernel. > > Which would account for needing more wall-clock-time. But heaps of CPU time? > > > And you have to enter the kernel in order to perform any disk, network > > or even console I/O. If your programs suck large datasets into memory, > > do lots of number crunching on them, then spit the results back out to > > a disk file, then they should benefit from more CPUs. However if they > > read and write data a lot while running, you're going to be limited by > > the big giant lock. > > Hm. Both are MP systems. Both were - at the time of test - virtually idle > besides running the tests. I could even retry in single user mode. I'm taking about your test programs themselves, not the rest of the system. It doesn't matter if the system is otherwise idle: if *your* programs perform a lot of I/O, then the big giant lock will hurt you. > > There may also be scalability issues (i.e. does FreeBSD perform better > > as you add more CPUs or does it spend so much time trying to stay out > > of its own way that it actually performs worse) however I don't know > > enough to say if you could be running into such problems as the only > > SMP machines I have access to have only 2 CPUs. > > As far as I understood HP Germany, they'd be glad to lend you one of them > for a few months. You'd just have to ask. I'm not an SMP expert, though perhaps those who are SMP experts might want to take advantage of this. > > > [Worse: The LH4 > > > behaves like a spoilt brat when it comes to hardware, disliking the Int= > el > > > EtherExpress that came with it (generating bus mastering problems after > > > bringing it up), > >=20 > > Which model Intel EtherExpress? What chipset? > > I'll have to put it into another machine - it's sitting on a shelf right > now. But it was working reliably AND fast on another ASUS P2B-DS machine. > > > What bus mastering problems exactly? > > Time outs, followed by a panic. This is still a bit vague. It would be nice to know exactly what the timeout error messages said, as well as what the panic message said. > > > having interrupt routing problems with two DEC TULIP based ethernet > > > cards sharing the same IRQ > >=20 > > Which tulip cards? > > CNet CN100 with an 21443 21143, not 21443. > > What driver? > > if_de Try if_dc instead. > > What kind of problems? > > Constant time outs under higher load than a few packets a second; no more > than 18 KB/second on a switch, no matter whether full duplex or not. This is probably due to a bug in the if_de driver. I finally got a proper handle on it the other day. The 21143 is different from the 21140 in a couple of ways, the most important being that it has built-in NWAY autonegotiation support. If you want to make a 10/100 autonegotiating NIC with a 21140 chip, you need to use an external MII-compliant tranceiver chip with NWAY support. You can design board with the 21143 like this as well, however you can *also* do it using the 21143's own built-in NWAY support. The DEC DE500-BA card works like this. The problem is that in adding the built-in autoneg support, DEC/Intel did a really dumb thing. In the CSR6 register, there's a bit that controls full duplex/half duplex operation: turn it on, the chip runs in full duplex mode, turn it off and it runs in half duplex. On the 21140, this is the *only* function that this bit has. But in the 21143, this bit has two functions: if the internal autoneg is shut off, then it behaves like it does on the 21140, but if autoneg is turned *on*, then it controls whether or not the chip advertises 10Mbps half duplex when performing autonegotiation. Why is this dumb? For the following reasons: - There are plenty of unused bits in other registers that DEC/Intel could have used instead of overloading the meaning of the full duplex enable bit in CSR6. - The chip defaults to autoneg turned on after a reset. It also defaults to half duplex. So if you want to manually enable full duplex, you *must* first turn off the autoneg (by clearing CSR14). The de driver doesn't know about this, and the result is that full duplex mode just won't work. If your board uses an external transceiver, the internal NWAY support should be turned off, but it isn't. So selecting full duplex mode manually or autonegotiating full duplex with a link partner doesn't work, and you stay in half duplex mode no matter what you do. The if_dc driver handles this correctly. You could tweak the de driver to handle it too, however looking at the code, I don't think it handles non-MII cards properly. The dc driver should handle those correctly (at the very least, you can always manually override the mode with ifconfig even if the autoneg gets it wrong). > > I find it unusual > > that two PCI devices would wind up with the same IRQ with the APIC enabled > > since it's supposed to give you a lot more IRQs than in UP mode. > > *ROTFL* (sorry). HP's algorithm for allocating IRQs is giving "same devices" > the same IRQs if they are running out of IRQS. > > Just take a look at this: Uhm... [...] > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin= > 2 > APIC_IO: routing 8254 via 8259 on pin 0 > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! I'm a little worried about this. You might want to forward all this information to the freebsd-smp list: I'm a little out of my depth. > >=20 > > > and being picky just which 3C906B-TX it > > > gets plugged in. > >=20 > > There is no such card as a 3c905B. There's a 3c905B, and there's a > > 3c905C. Unfortunately, 3Com did go through several different ASIC > > revisions with the 3c905B series, some of which work better than others, > > but again, I see no details here. > > 2nd time. Sorry. I should really be more carefull: > > xl0@pci1:3:0: class=3D0x020000 card=3D0x905510b7 chip=3D0x905510b7 rev=3D= > 0x64 hdr=3D0x00 > xl1@pci2:2:0: class=3D0x020000 card=3D0x905510b7 chip=3D0x905510b7 rev=3D= > 0x24 hdr=3D0x00 > > The one not working stated rev=3D0x00. And it is working perfectly well in > another machine. Again, there is a distinct lack of details. You can't just say it doesn't work. You have to describe the failure. > > Ok. Tell me what info to gather. Any preferred benchmarks? Again, you didn't show us the actual results from your original tests. You just said "it's not as fast." We don't want your interpretation of the data: we want the data itself. Again, I would ask the freebsd-smp list about this. Also, I would try installing a more current version of -current just to be sure you're on the same page as they are. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 8:24:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 6E93914F75 for ; Mon, 17 Jan 2000 08:24:33 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id IAA47366; Mon, 17 Jan 2000 08:24:25 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id IAA71114; Mon, 17 Jan 2000 08:24:20 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001171624.IAA71114@realtime.exit.com> Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) In-Reply-To: from Jonathan Chen at "Jan 10, 2000 01:02:40 am" To: jon@spock.org (Jonathan Chen) Date: Mon, 17 Jan 2000 08:24:20 -0800 (PST) Cc: imp@village.org (Warner Losh), grog@lemis.com (Greg Lehey), current@FreeBSD.ORG Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the delay on this reply; I was going over some old email and came across this only a week late. Jonathan Chen wrote: > With what little pccard/ethernet programming experiences I've had, this > problem seems to be caused by the interrupt for the card getting lost > somewhere before getting processed by the handler. The reason you still > get traffic is because of the watchdog. (Try uncommenting the commented > out lines in sys/dev/ep/if_ep.c in the function ep_if_watchdog(), you > should start seeing lots of kernel messages saying "ep: watchdog".) After > looking briefly at the ep files, I saw something that doesn't seem right. > In sys/dev/ep/if_ep_pccard.c around line 176, there's a comment that says > "Fake IRQ must be 3". Now maybe the card requires it, or maybe the > original author just didn't have anything on IRQ 3, I don't know. So, I'd > suggest turning off com2 or whatever you have on irq3, -or- change the > "fake irq" to something else you do have free on the next line (ie, > 0x3000-> 0xa000 if you have IRQ10 free). If this works, great... if not, I > hope Warner gets some more free time. ;) According to the docs, this "Fake IRQ must be 3" is legitimate. The IRQ programmed into the resource config register in window 0 _must_ be 3: "any other value will disable the IRQ line drivers." (Quoted from the doc. > As for the other problem with collisions, I did a search on the word > collision on sys/dev/ep/if_ep.c, and found only one mention at around line > 620. The comment says "TXS_MAX_COLLISION - we shouldn't get here". I > suspect it does get there, so I suggest putting a printf there to find out. > I also suspect that the card may require a reset or some other stuff if and > when it "gets there". If that's the case, someone else with the specs on > the 589 cards can look that up and do it. I can state pretty categorically that, at least in my case, we're _not_ getting here. As I said in an earlier email, I'm still having interrupt problems with the 589 (I have a 3C589D) and the 574BT. I haven't tracked it down yet, but I'm hunting. I do know, at least, that I'm not receiving _any_ interrupts from either card. So far I don't know why. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 9: 5:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from scds.com (d122-h010.rh.rit.edu [129.21.122.138]) by hub.freebsd.org (Postfix) with ESMTP id 99F3D14C89; Mon, 17 Jan 2000 09:05:34 -0800 (PST) (envelope-from jseger@jseger.scds.com) Received: from localhost (jseger@localhost) by scds.com (8.9.3/8.9.3) with ESMTP id MAA14083; Mon, 17 Jan 2000 12:04:31 -0500 (EST) (envelope-from jseger@jseger.scds.com) Date: Mon, 17 Jan 2000 12:04:31 -0500 (EST) From: "Justin M. Seger" To: current@freebsd.org, dan@freebsd.org, fullermd@futuresouth.com Subject: Latest pkg_delete core dumps Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a current built yesterday, pkg_name core dumps on: %pkg_delete m4-1.4/ Segmentation fault(core dumped) or any pkg_name with a '/' on the end. In the past this worked fine. I'm guessing that this was broken with the following commit: revision 1.15 date: 2000/01/15 01:15:34; author: dan; state: Exp; lines: +24 -3 Teach pkg_delete and pkg_info how to deal with full pathnames (/var/db/pkg/foo-1.0, instead of just foo-1.0). Submitted by: Matthew D. Fuller If no one else fixes it, I'll try to look at it later today. Thanks, Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 9:14:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 7087F14C12; Mon, 17 Jan 2000 09:14:10 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 5BBC516C5; Mon, 17 Jan 2000 09:13:04 -0800 (PST) Date: Mon, 17 Jan 2000 09:13:04 -0800 From: Chris Piazza To: Satoshi - Ports Wraith - Asami Cc: Kris Kennaway , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile Message-ID: <20000117091304.A1328@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from asami@FreeBSD.ORG on Mon, Jan 17, 2000 at 07:06:55AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 07:06:55AM -0800, Satoshi - Ports Wraith - Asami wrote: > * From: Kris Kennaway > > * Openssl should now be fully functional for both US and international users > * - please report any problems you have in using it to me. You should be > * able to compile all openssl-using code (some of them require rsaref and > * therefore cannot be used in a commercial setting, others do not), although > * the ports may need tweaking to deal with the changed base location (/usr > * instead of /usr/local). > > Should I add some stuff to handle the differences in bsd.port.mk (like > we did with perl5)? > > For one thing, openssl is in -current only so we need a way to have > ports easily depend on the openssl port in -stable. Actually any port that depends on openssl depends on crypto.1, which will be found in /usr/lib anyway :). I haven't had any problems building ports that require openssl, although I'm using the international version etc. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 9:19:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 39E1214C12 for ; Mon, 17 Jan 2000 09:19:25 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.5.62]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 6D19E5975 for ; Mon, 17 Jan 2000 18:19:24 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 5EF7E4E48; Mon, 17 Jan 2000 18:19:23 +0100 (CET) Date: Mon, 17 Jan 2000 18:19:23 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: XFree86 3.9.17 Message-ID: <20000117181923.A60855@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything special except removing doc from the list of subdirs... -=-=- ./to_wfont -o Roman.phont Roman.src ./to_wfont -o Roman_M.phont Roman_M.src [1] + done make World > makeworld 2>& 1 Mon Jan 17 18:02:33 CET 2000 Full build of Release 6.4 of the X Window System complete. -=-=- -=-=- 430 [18:02] roberto@caerdonn:/build/xc> ll programs/Xserver/XFree86 -rwxr-xr-x 1 roberto staff 1596449 Jan 17 18:00 programs/Xserver/XFree86* 431 [18:02] roberto@caerdonn:/build/xc> ldd !$ ldd programs/Xserver/XFree86 programs/Xserver/XFree86: libxpg4.so.2 => /usr/lib/libxpg4.so.2 (0x2818d000) libz.so.2 => /usr/lib/libz.so.2 (0x28191000) libm.so.2 => /usr/lib/libm.so.2 (0x2819e000) libc.so.4 => /usr/lib/libc.so.4 (0x281b9000) 432 [18:02] roberto@caerdonn:/build/xc> gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) -=-=- It seems to be complete with all .a and .so. The build used the following CFLAGS -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_NULL -DHAS_SNPRINTF -DLIBX11 -DERRORDB=\"/usr/X11R6/lib/X11/XErrorDB\" Haven't tried it yet :) -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 9:29: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A9B3214BFF for ; Mon, 17 Jan 2000 09:28:52 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA11925; Mon, 17 Jan 2000 18:28:34 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: CGiordano@ids.net Cc: Reinier Bezuidenhout , freebsd-current@FreeBSD.ORG Subject: Re: newpcm References: <200001110908.LAA06044@oskar.dev.nanoteq.co.za> <387C3130.4930E69B@ids.net> From: Dag-Erling Smorgrav Date: 17 Jan 2000 18:28:33 +0100 In-Reply-To: Chris Giordano's message of "Wed, 12 Jan 2000 02:45:52 -0500" Message-ID: Lines: 29 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Giordano writes: > Luigi Rizzo explained this behavior in the old pcm driver > about a year or so ago. I believe it was due to some applications > setting a fixed buffering size with the SETFRAGMENT(?) ioctl, which > was not implemented in old pcm and then mistakenly writing smaller > than intended sound samples because they assumed a different buffer > size. I don't know if this applies to newpcm, but it sounds like > the same symptoms. > > Check the -current mailing list archives for pcm0 and xgalaga. -multimedia, actually: I (and many others, I'm sure) would be very grateful if somebody would implement Luigi's first suggestion, to wit: > 1) complete the SETFRAGMENT (or whatever it is called) implementation > (not hard, you just need to reduce the blocksize in the dma buffer > descriptor and reset the dma channel; The ioctl in question is SNDCTL_DSP_SETFRAGMENT. Its semantics are described in the "Making audio complicated" section of the OSS Programmer's Guide: . DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 9:32:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust252.tnt3.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F03B14CF1; Mon, 17 Jan 2000 09:32:12 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Mon, 17 Jan 2000 12:32:09 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Jun Kuriyama Cc: current@FreeBSD.org Subject: Re: 0xdeadc0de ??? In-Reply-To: <14467.14628.579240.98517T@localhost.sky.rim.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Jun Kuriyama wrote: > > I found message below at inserting aue0 (after pccard ed0 > insert/remove). > > ----- > aue0: LUA-TX MELCO LUA-TX, rev 1.10/1.01, addr 2 > aue0: Ethernet address: 00:40:26:61:10:c7 > miibus0: on aue0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > Data modified on freelist: word 7 of object 0xc0828400 size 364 previous type USBdev (0x0 != 0xdeadc0de) > aue0: starting DAD for fe80:0003::0240:26ff:fe61:10c7 > aue0: DAD complete for fe80:0003::0240:26ff:fe61:10c7 - no duplicates found > ----- > > Should I track this behaviour (if I can revisit this message), or I > can simply ignore this message? > Basically, this means that you correctly enabled INVARIANT* to catch bugs, and you found one. Here, it seems that a USBdev is being used after being free()d. I'd suggest reporting it directly to Bill Paul and Nick Hibma, since they'll be familiar with their code :) > > Jun Kuriyama // kuriyama@sky.rim.or.jp > // kuriyama@FreeBSD.org > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:12:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id A06D414DAB; Mon, 17 Jan 2000 10:12:13 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id MAA19179; Mon, 17 Jan 2000 12:12:05 -0600 (CST) Date: Mon, 17 Jan 2000 12:12:05 -0600 From: "Matthew D. Fuller" To: "Justin M. Seger" Cc: current@freebsd.org, dan@freebsd.org Subject: Re: Latest pkg_delete core dumps Message-ID: <20000117121205.A18789@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 12:04:31PM -0500, a little birdie told me that Justin M. Seger remarked > In a current built yesterday, pkg_name core dumps on: > %pkg_delete m4-1.4/ > Segmentation fault(core dumped) > > or any pkg_name with a '/' on the end. In the past this worked fine. > > I'm guessing that this was broken with the following commit: I believe so. I'm presently out of town so I don't have access to the patches I made, but I know why it is. I added code to deal with trailing /'s because they often appear with path-name completion (which is the whole point of the commit). But it'll freak out if there's only a trailing / with none in a full path before it. The first rindex() call will catch that and use the null afterward as the package name, or something like that. Should be fairly easy to fix up nicely, just add another check in there. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:18: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B248414EEE for ; Mon, 17 Jan 2000 10:18:00 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA63657; Mon, 17 Jan 2000 11:17:50 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA10403; Mon, 17 Jan 2000 11:18:03 -0700 (MST) Message-Id: <200001171818.LAA10403@harmony.village.org> To: Jesper Skriver Subject: Re: apm suspend ?? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 Jan 2000 20:56:50 +0100." <20000116205650.A64495@skriver.dk> References: <20000116205650.A64495@skriver.dk> Date: Mon, 17 Jan 2000 11:18:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now : suspend doesn't work as expected. : : When I run 'apm -z' the laptop suspends as normal, but right after this : the harddisk led turns on, and it powers up again. That's very odd. apm hasn't changed since Dec 2 and even that was just deleting code that had been obsolete for a while now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:22:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A281E14F3C for ; Mon, 17 Jan 2000 10:22:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA63680; Mon, 17 Jan 2000 11:22:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA10447; Mon, 17 Jan 2000 11:22:43 -0700 (MST) Message-Id: <200001171822.LAA10447@harmony.village.org> To: Brian Somers Subject: Re: PnP probing in -current Cc: Peter Wemm , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org In-reply-to: Your message of "Mon, 17 Jan 2000 16:13:14 GMT." <200001171613.QAA25647@hak.lan.Awfulhak.org> References: <200001171613.QAA25647@hak.lan.Awfulhak.org> Date: Mon, 17 Jan 2000 11:22:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001171613.QAA25647@hak.lan.Awfulhak.org> Brian Somers writes: : Without saying it's ``at isa?'' I get only one aha failed line (I'm : sure I used to get nothing) at boot time. I still see the ADP lines : though (of course). odd. It has been a while since I tried the aha 1542CP card. I'll have to give it a shot with a releatively current current machine. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:24: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 1100514F63 for ; Mon, 17 Jan 2000 10:23:57 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-13.iptelecom.net.ua [212.9.226.141]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA24126 for ; Mon, 17 Jan 2000 20:28:39 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id UAA06982 for ; Mon, 17 Jan 2000 20:23:21 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38835E15.F94FD00D@altavista.net> Date: Mon, 17 Jan 2000 20:23:17 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Problems with rc.network Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After today's cvsup'ing and mergemaster'ing I discovered that something weird happened with the rc.network script. In the past I newer had any problems with my notebook boot-up, but today it stops for several minutes on "Starting final network daemons:" and writing something like: "Cannot send MNT PRC: RPC: Port mapper failure - RPC timed out..." It looks like it trying to contact my another computer I have at home over plip line because after several minutes it sudenly prints "lp0: Too many errors, Going off-line" and continues boot-up sequence. I do not know wny it is doing so, because I have noauto option for all my NFS volumes and disabled all network daemons except inetd in my rc.conf. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:24:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4FEE015042; Mon, 17 Jan 2000 10:24:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA63706; Mon, 17 Jan 2000 11:24:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA10496; Mon, 17 Jan 2000 11:24:25 -0700 (MST) Message-Id: <200001171824.LAA10496@harmony.village.org> To: Brian Somers Subject: Re: PnP probing in -current Cc: freebsd-current@FreeBSD.ORG, Peter Wemm In-reply-to: Your message of "Mon, 17 Jan 2000 02:38:24 GMT." <200001170238.CAA00850@hak.lan.Awfulhak.org> References: <200001170238.CAA00850@hak.lan.Awfulhak.org> Date: Mon, 17 Jan 2000 11:24:25 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001170238.CAA00850@hak.lan.Awfulhak.org> Brian Somers writes: : Since the PnP probing code was made unconditional in the bootup : routines on December 6, I've been having problems with my : Adaptec 1542CP. : : I've got my BIOS set to ``non pnp OS'' and my 1542 set to 0x330. : I've never had ``options pnp0'' in my config, and on December 6 (when : isa/pnp.c and isa/pnpprobe.c started being included with isa devices : rather than with ``options pnp*'', the card stopped being probed. : : If I skip the code in pnp_identify() in isa/pnp.c, everything works : fine. : : Are there any plans to re-optionify this code ? : : I can provide more details once I rebuild my machine.... See my : other post about some ata problems, coming to a -current list near : you ! So you have your 1542CP hardware set to be hardwired at 0x330 and not in PnP mode? Is that correct? If so, then why is it responding to the PnP probes. It shouldn't be. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:27:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B8FAB14F3D for ; Mon, 17 Jan 2000 10:27:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA63726; Mon, 17 Jan 2000 11:27:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA10533; Mon, 17 Jan 2000 11:27:29 -0700 (MST) Message-Id: <200001171827.LAA10533@harmony.village.org> To: frank@exit.com Subject: Re: 3C589 problems? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Jan 2000 06:54:10 PST." <200001171454.GAA69760@realtime.exit.com> References: <200001171454.GAA69760@realtime.exit.com> Date: Mon, 17 Jan 2000 11:27:29 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001171454.GAA69760@realtime.exit.com> Frank Mayhar writes: : I just want to know if anyone else is still having problems with their : 3C589 or 574 after Matt Dodd's latest series of checkins. Yea. I'm only getting 950KiB/s with ftp. I'm bummed. Matt was geting 1.1MiB/s :-(. : Something is seriously wrong and I'm not sure where to look next. Sounds a lot like a bad irq assignment from pccardd. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 10:29:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 938CA14EEC; Mon, 17 Jan 2000 10:29:02 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-13.iptelecom.net.ua [212.9.226.141]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA24663; Mon, 17 Jan 2000 20:33:45 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id UAA07008; Mon, 17 Jan 2000 20:28:28 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38835F47.FE17BF29@altavista.net> Date: Mon, 17 Jan 2000 20:28:23 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Alexander N. Kabaev" Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alexander N. Kabaev" wrote: > As promised, I tried to look into the problem little futher. The following > patch fixes all crashes for me and I was unable to reproduce the bug anymore. I > would really like to hear if it works for you too. I am especially interested > to know if it works on Alpha, because I cannot test it myself. > > PS. The code in question is in mashine independent, so I have reason to believe > that this patch may fix the problem for other platforms too... > > Index: contrib/gcc/except.c > =================================================================== > RCS file: /home/ncvs/src/contrib/gcc/except.c,v > [Nice patch stripped] Yeah, it works! (at least at a first glance). David, what do you think about it? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11: 8:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 517AB14D5A for ; Mon, 17 Jan 2000 11:08:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA57775; Mon, 17 Jan 2000 11:08:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA37493; Mon, 17 Jan 2000 11:08:14 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2000 11:08:14 -0800 From: "David O'Brien" To: Maxim Sobolev Cc: "Alexander N. Kabaev" , current@FreeBSD.ORG Subject: Re: C++ exceptions doesn't work in shared libraries Message-ID: <20000117110814.J7184@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <38835F47.FE17BF29@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38835F47.FE17BF29@altavista.net>; from sobomax@altavista.net on Mon, Jan 17, 2000 at 08:28:23PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 08:28:23PM +0200, Maxim Sobolev wrote: > > Index: contrib/gcc/except.c > > =================================================================== > > RCS file: /home/ncvs/src/contrib/gcc/except.c,v > > [Nice patch stripped] > > Yeah, it works! (at least at a first glance). David, what do you think > about it? Not really wanting to take a file off the vendor branch to fix something that seems to be broken elsewhere. I have to wonder why all the other platforms in the world doesn't need this change. I spent a few hours on this yesterday, but am not closer to fixing it. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11:31:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 9BF2414F5C; Mon, 17 Jan 2000 11:31:19 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id OAA01462; Mon, 17 Jan 2000 14:37:31 -0500 (EST) Date: Mon, 17 Jan 2000 14:37:31 -0500 From: Dan Moschuk To: "Justin M. Seger" Cc: current@freebsd.org, dan@freebsd.org, fullermd@futuresouth.com Subject: Re: Latest pkg_delete core dumps Message-ID: <20000117143731.C1156@spirit.jaded.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jseger@scds.com on Mon, Jan 17, 2000 at 12:04:31PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris reported this to me last night, and I was going to do the patch tonight. If someone wants to send me a diff before tonight, I'll just commit that. | In a current built yesterday, pkg_name core dumps on: | %pkg_delete m4-1.4/ | Segmentation fault(core dumped) | | or any pkg_name with a '/' on the end. In the past this worked fine. | | I'm guessing that this was broken with the following commit: | | revision 1.15 | date: 2000/01/15 01:15:34; author: dan; state: Exp; lines: +24 -3 | Teach pkg_delete and pkg_info how to deal with full pathnames | (/var/db/pkg/foo-1.0, instead of just foo-1.0). | | Submitted by: Matthew D. Fuller | | | If no one else fixes it, I'll try to look at it later today. | | Thanks, | Justin | -- Dan Moschuk (TFreak!dan@freebsd.org) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11:33:47 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1FD5014F4A; Mon, 17 Jan 2000 11:33:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D33731CD438; Mon, 17 Jan 2000 11:33:43 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 11:33:43 -0800 (PST) From: Kris Kennaway To: Satoshi - Ports Wraith - Asami Cc: ports@freebsd.org, current@FreeBSD.org Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > Should I add some stuff to handle the differences in bsd.port.mk (like > we did with perl5)? It may be useful - although there are a lot of inconsistencies in how the openssl ports look for it. Dirk Froemberg was going to help with this - I'm not sure exactly what the best way to do it is. For example, ports like w3m-ssl pass the location of the openssl include directory, which needs to be either /usr/include or ${LOCALBASE}/include. Perhaps the best thing would be to bump OSVERSION (belatedly). Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11:45:42 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 449E614CC7; Mon, 17 Jan 2000 11:45:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C0A911CD468; Mon, 17 Jan 2000 11:45:40 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 11:45:40 -0800 (PST) From: Kris Kennaway To: "Robert C. Noland III" Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: world broken using /usr/local/lib? In-Reply-To: <14467.10527.127430.757657@gizmo.2hip.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Robert C. Noland III wrote: > You have a libcrypto in /usr/local/lib which was not compiled with > rsaref. When it reaches out to get rsaref, it also picks up the > libcrypto and libssl from /usr/local/lib rather than the build tree. > Move them out of the way... I figured this out late last night (I couldn't reproduce it for a long time because my test boxes didn't have the openssl port installed) - I'm looking at how to fix it. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11:50:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id CA01E14E7A for ; Mon, 17 Jan 2000 11:50:19 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id LAA49158; Mon, 17 Jan 2000 11:50:18 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id LAA74051; Mon, 17 Jan 2000 11:50:17 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001171950.LAA74051@realtime.exit.com> Subject: Re: 3C589 problems? In-Reply-To: <200001171827.LAA10533@harmony.village.org> from Warner Losh at "Jan 17, 2000 11:27:29 am" To: imp@village.org (Warner Losh) Date: Mon, 17 Jan 2000 11:50:17 -0800 (PST) Cc: frank@exit.com, current@FreeBSD.ORG Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <200001171454.GAA69760@realtime.exit.com> Frank Mayhar writes: > : I just want to know if anyone else is still having problems with their > : 3C589 or 574 after Matt Dodd's latest series of checkins. > Yea. I'm only getting 950KiB/s with ftp. I'm bummed. Matt was > geting 1.1MiB/s :-(. Yeah, well, you're doing better than I am. :-) > : Something is seriously wrong and I'm not sure where to look next. > Sounds a lot like a bad irq assignment from pccardd. Well, after I wrote this, I updated the sources again, which got some pccardc changes. Now I get "driver allocation failed" from pccardd, with an error I can't remember offhand (something like "invalid operation for device", but I know that's not it). The odd thing is that going back to the old kernel fixes it. I'll do some more digging tonight. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11:51:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 0970714BC6 for ; Mon, 17 Jan 2000 11:51:36 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id OAA29506; Mon, 17 Jan 2000 14:51:00 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000117110814.J7184@dragon.nuxi.com> Date: Mon, 17 Jan 2000 14:51:00 -0500 (EST) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: "David O'Brien" Subject: Re: C++ exceptions doesn't work in shared libraries Cc: current@FreeBSD.ORG, Maxim Sobolev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I already pointed out in private message, this bug is in fact i386 specific and it was wrong to fix it in gcc/except.c file. The real problem is that default builtin_setjmp implementation does not restore any registers except for stack pointers when doing nonlocal jump. This means, that every platform, that needs to store/restore some other state between jumps, has to provide appropriate definitions for builtin_setjmp_setup and builtin_setjmp_receiver RTL expansions. Every plaftorm which needs to do some additional processing at setjmp receive point, such as restoring additional information previously saved by builtin_setjmp_setup, can provide definition for builtin_setjmp_receiver RTL expansion. That is exactly what I do in a second (improved, I hope) patch I have sent to David yesterday. The i386 code compiled with -fpic flag requires the value of PIC register (EBX) to be restored in order to function properly. I do not provide expansion for builtin_setjmp_setup because GCC documentation explicitly states that values should be recalculated if possibe, rather than stored in setjmp buffer and proper value for EBX can easlity be determined from the current EIP contents. Since the patch is extremely small and simple, I am attaching it below for those who want to test it. Of course, I would greatly appreciate if you will let me know the results. I am aware that my English is far from perfect and asking for your patience. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 17-Jan-00 Time: 14:11:19 ---------------------------------- Index: config/i386/i386.md =================================================================== RCS file: /home/ncvs/src/contrib/gcc/config/i386/i386.md,v retrieving revision 1.5 diff -u -r1.5 i386.md --- config/i386/i386.md 1999/11/15 04:28:55 1.5 +++ config/i386/i386.md 2000/01/16 04:21:02 @@ -8195,3 +8195,13 @@ load_pic_register (1); DONE; }") + +(define_expand "builtin_setjmp_receiver" + [(label_ref (match_operand 0 "" ""))] + "flag_pic" + " +{ + load_pic_register (1); + DONE; +}") + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 11:56:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EACA314D1B for ; Mon, 17 Jan 2000 11:56:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id LAA57999; Mon, 17 Jan 2000 11:56:48 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2000 11:56:48 -0800 From: "David O'Brien" To: "Alexander N. Kabaev" Cc: "David O'Brien" , current@FreeBSD.ORG, Maxim Sobolev Subject: Re: C++ exceptions doesn't work in shared libraries Message-ID: <20000117115648.C53965@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <20000117110814.J7184@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 02:51:00PM -0500, Alexander N. Kabaev wrote: > As I already pointed out in private message, this bug is in fact i386 > specific and it was wrong to fix it in gcc/except.c file. The real > problem is that default builtin_setjmp implementation does not restore > any registers except for stack pointers when doing nonlocal jump. This > means, that every platform, that needs to store/restore some other > state between jumps, has to provide appropriate definitions for > builtin_setjmp_setup and builtin_setjmp_receiver RTL expansions. Why doesn't OpenBSD, Linux, or Solaris x86 need this patch? > That is exactly what I do in a second (improved, I hope) patch I have > sent to David yesterday. I may go with this patch, but I need to understand more why it is needed before I take a file off the vendor branch. Any help would be appreciated. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12: 3: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id CEC6514FAD for ; Mon, 17 Jan 2000 12:02:55 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 68F762CE5D; Mon, 17 Jan 2000 22:02:48 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id ED0A46A; Mon, 17 Jan 2000 22:02:53 +0200 (EET) Date: Mon, 17 Jan 2000 22:02:53 +0200 From: Vallo Kallaste To: Ollivier Robert Cc: FreeBSD Current Users' list Subject: Re: XFree86 3.9.17 Message-ID: <20000117220253.A20605@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000117181923.A60855@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000117181923.A60855@caerdonn.eurocontrol.fr>; from Ollivier Robert on Mon, Jan 17, 2000 at 06:19:23PM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 06:19:23PM +0100, Ollivier Robert wrote: > I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything > special except removing doc from the list of subdirs... > > -=-=- > ./to_wfont -o Roman.phont Roman.src > ./to_wfont -o Roman_M.phont Roman_M.src > [1] + done make World > makeworld 2>& 1 > > Mon Jan 17 18:02:33 CET 2000 > > Full build of Release 6.4 of the X Window System complete. > > -=-=- > 430 [18:02] roberto@caerdonn:/build/xc> ll programs/Xserver/XFree86 > -rwxr-xr-x 1 roberto staff 1596449 Jan 17 18:00 programs/Xserver/XFree86* > 431 [18:02] roberto@caerdonn:/build/xc> ldd !$ > ldd programs/Xserver/XFree86 > programs/Xserver/XFree86: > libxpg4.so.2 => /usr/lib/libxpg4.so.2 (0x2818d000) > libz.so.2 => /usr/lib/libz.so.2 (0x28191000) > libm.so.2 => /usr/lib/libm.so.2 (0x2819e000) > libc.so.4 => /usr/lib/libc.so.4 (0x281b9000) > 432 [18:02] roberto@caerdonn:/build/xc> gcc -v > Using builtin specs. > gcc version 2.95.2 19991024 (release) > > Haven't tried it yet :) Have you tried to install it? It does builds but barfs at some point for install process. Not that I care so much about it, 3.3.6 works for my G400 now, thanks god. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12: 4:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (Postfix) with ESMTP id 054FB14D28 for ; Mon, 17 Jan 2000 12:04:28 -0800 (PST) (envelope-from ejh@ejhslu.eas.slu.edu) Received: from ejhslu.eas.slu.edu (ejhslu.eas.slu.edu [165.134.8.243]) by mnw.eas.slu.edu (8.9.3/8.9.3) with ESMTP id OAA03685 for ; Mon, 17 Jan 2000 14:04:26 -0600 (CST) Received: (from ejh@localhost) by ejhslu.eas.slu.edu (8.9.3/8.9.3) id OAA01550 for current@freebsd.org; Mon, 17 Jan 2000 14:04:25 -0600 (CST) Date: Mon, 17 Jan 2000 14:04:25 -0600 (CST) From: "Eric J. Haug" Message-Id: <200001172004.OAA01550@ejhslu.eas.slu.edu> To: current@freebsd.org Subject: USB D-Link DSB-650 kue0: failed to load code Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have a Toshiba 2100CDS laptop with an OHCI USB controller that gives a kue0: failed to load code segment error message Rather than clutter the list, the conf file and the dmesg boot file is available at ftp.eas.slu.edu:/pub/incoming/[usbdmesg, usbbootmsg, usbltaconf] The usbbootmsg is from yesterdays kernel sources with some of the debug variables set to 15. The changes from today did not seem to make any difference. the stripped mesg output from a boot follows: ohci0: mem 0xf7fff000-0xf7ffffff irq 11 at device 11.0 on pci0 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered kue0: D-Link Corp 10Mbps ethernet adapter, rev 1.00/0.02, addr 2 kue0: failed to load code segment: IOERROR device_probe_and_attach: kue0 attach returned 6 eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:20:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id C414C14E99 for ; Mon, 17 Jan 2000 12:20:44 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id DC80E3E39; Mon, 17 Jan 2000 21:20:38 +0100 (CET) Date: Mon, 17 Jan 2000 21:20:38 +0100 From: Jesper Skriver To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: apm suspend ?? Message-ID: <20000117212038.A69519@skriver.dk> References: <20000116205650.A64495@skriver.dk> <200001171818.LAA10403@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001171818.LAA10403@harmony.village.org>; from imp@village.org on Mon, Jan 17, 2000 at 11:18:02AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: > In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: > : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now > : suspend doesn't work as expected. > : > : When I run 'apm -z' the laptop suspends as normal, but right after this > : the harddisk led turns on, and it powers up again. > > That's very odd. apm hasn't changed since Dec 2 and even that was > just deleting code that had been obsolete for a while now. I don't get it either - will try to revert to -CURRENT as of jan 5th, and see if it works again ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:27:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 5DE6314FBF for ; Mon, 17 Jan 2000 12:27:21 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id PAA16594; Mon, 17 Jan 2000 15:25:56 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA29133; Mon, 17 Jan 2000 15:25:58 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA29129; Mon, 17 Jan 2000 15:25:58 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Mon, 17 Jan 2000 15:25:58 -0500 (EST) From: Kenneth Wayne Culver To: Vallo Kallaste Cc: Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: XFree86 3.9.17 In-Reply-To: <20000117220253.A20605@myhakas.matti.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had to get rid of some things from Xext to make it install properly myself. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Mon, 17 Jan 2000, Vallo Kallaste wrote: > On Mon, Jan 17, 2000 at 06:19:23PM +0100, Ollivier Robert wrote: > > > I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything > > special except removing doc from the list of subdirs... > > > > -=-=- > > ./to_wfont -o Roman.phont Roman.src > > ./to_wfont -o Roman_M.phont Roman_M.src > > [1] + done make World > makeworld 2>& 1 > > > > Mon Jan 17 18:02:33 CET 2000 > > > > Full build of Release 6.4 of the X Window System complete. > > > > -=-=- > > 430 [18:02] roberto@caerdonn:/build/xc> ll programs/Xserver/XFree86 > > -rwxr-xr-x 1 roberto staff 1596449 Jan 17 18:00 programs/Xserver/XFree86* > > 431 [18:02] roberto@caerdonn:/build/xc> ldd !$ > > ldd programs/Xserver/XFree86 > > programs/Xserver/XFree86: > > libxpg4.so.2 => /usr/lib/libxpg4.so.2 (0x2818d000) > > libz.so.2 => /usr/lib/libz.so.2 (0x28191000) > > libm.so.2 => /usr/lib/libm.so.2 (0x2819e000) > > libc.so.4 => /usr/lib/libc.so.4 (0x281b9000) > > 432 [18:02] roberto@caerdonn:/build/xc> gcc -v > > Using builtin specs. > > gcc version 2.95.2 19991024 (release) > > > > Haven't tried it yet :) > > Have you tried to install it? It does builds but barfs at some point for > install process. Not that I care so much about it, 3.3.6 works for my > G400 now, thanks god. > -- > > Vallo Kallaste > vallo@matti.ee > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:32:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id A4C2F14EE3 for ; Mon, 17 Jan 2000 12:32:37 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.117.168]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOH001PSXGU9C@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Mon, 17 Jan 2000 12:12:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 347B0918C2; Mon, 17 Jan 2000 12:12:29 -0800 (PST) Date: Mon, 17 Jan 2000 12:12:29 -0800 (PST) From: Alex Zepeda Subject: Re: Solved(?): crash with ffs_softdep.c 1.52 In-reply-to: <200001171251.NAA08566@Magelan.Leidinger.net> To: Alexander Leidinger Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Alexander Leidinger wrote: > I've successfully booted with ffs_softdep.c 1.54, I'm doing now a full > buildworld to stress the system. Hmm. I still got repeatable crashes with 1.54, and finally got to the point where lost+found got populated. I also just got my finger smashed in a door, making writing a tad bit impossible. When the swelling/pain goes down, I'll have a back trace :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:39:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id 32D5114BFF; Mon, 17 Jan 2000 12:39:42 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id PAA43537; Mon, 17 Jan 2000 15:39:34 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38837E05.72203F31@acm.org> Date: Mon, 17 Jan 2000 15:39:33 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add lynx-ssl to the list of ports which are broken on current. This was as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make world. Jim Bloom bloom@acm.org Kris Kennaway wrote: > > On 17 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > > > Should I add some stuff to handle the differences in bsd.port.mk (like > > we did with perl5)? > > It may be useful - although there are a lot of inconsistencies in how the > openssl ports look for it. Dirk Froemberg was going to help with this - > I'm not sure exactly what the best way to do it is. For example, ports > like w3m-ssl pass the location of the openssl include directory, which > needs to be either /usr/include or ${LOCALBASE}/include. Perhaps the best > thing would be to bump OSVERSION (belatedly). > > Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:41: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id BDABC14ECC for ; Mon, 17 Jan 2000 12:40:57 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 404 invoked by uid 1010); 17 Jan 2000 19:30:02 -0000 Date: Mon, 17 Jan 2000 19:30:02 +0000 From: George Cox To: current@freebsd.org Subject: /dev/sndstat Message-ID: <20000117193002.A259@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupped yesterday. extremis /dev # ./MAKEDEV sndstat0 expr: non-numeric argument bad node: mknod mixerstat0 Something's wrong :-) best; gjvc -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:45:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 5E39F1500D for ; Mon, 17 Jan 2000 12:45:12 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id PAA04866; Mon, 17 Jan 2000 15:48:43 -0500 From: Bill Paul Message-Id: <200001172048.PAA04866@skynet.ctr.columbia.edu> Subject: Re: USB D-Link DSB-650 kue0: failed to load code To: ejh@eas.slu.edu (Eric J. Haug) Date: Mon, 17 Jan 2000 15:48:42 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <200001172004.OAA01550@ejhslu.eas.slu.edu> from "Eric J. Haug" at Jan 17, 2000 02:04:25 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2891 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Eric J. Haug had to walk into mine and say: > Hi all, > > I have a Toshiba 2100CDS laptop with an OHCI USB controller > that gives a kue0: failed to load code segment error message > Rather than clutter the list, the conf file and the dmesg boot > file is available at > ftp.eas.slu.edu:/pub/incoming/[usbdmesg, usbbootmsg, usbltaconf] > The usbbootmsg is from yesterdays kernel sources with some of the debug > variables set to 15. > The changes from today did not seem to make any difference. > > the stripped mesg output from a boot follows: > > ohci0: mem 0xf7fff000-0xf7ffffff irq 11 at device 11.0 on pci0 > usb0: OHCI version 1.0 > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > kue0: D-Link Corp 10Mbps ethernet adapter, rev 1.00/0.02, addr 2 > kue0: failed to load code segment: IOERROR > device_probe_and_attach: kue0 attach returned 6 An important point which you neglect to mention is: how long did it take before the IOERROR message appeared? (That is, how much time passed between the first kue0 probe message and the next?) Getting the Kawasaki chip to work requires downloading firmware into it, and the code segment of the firmware is about 3800 bytes, which makes for a fairly large control transfer. I had to set things up with a longer than normal timeout to make this work on my laptop. If the IOERROR message appears after only a second or two (or maybe three), then the timeout may not be long enough for your machine. If it sits there for a long time (ten seconds or longer) then it's probably something else. To see if this in fact the problem, do the following: - Bring up /sys/dev/usb/if_kue.c in your favorite editor. - Find the kue_do_request() function. - Change the timeout from 500000 to 1000000, i.e. change this: usbd_setup_default_xfer(xfer, dev, 0, 500000, req, data, UGETW(req->wLength), USBD_SHORT_XFER_OK, 0); to this: usbd_setup_default_xfer(xfer, dev, 0, 1000000, req, data, UGETW(req->wLength), USBD_SHORT_XFER_OK, 0); Then recompile your kernel/module/whatever and try again. (And let me know what happens, of course.) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:50:45 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 9E27D1539E; Mon, 17 Jan 2000 12:50:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E9031CD40E; Mon, 17 Jan 2000 12:50:42 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 12:50:42 -0800 (PST) From: Kris Kennaway To: Jim Bloom Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile In-Reply-To: <38837E05.72203F31@acm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Jim Bloom wrote: > Add lynx-ssl to the list of ports which are broken on current. This was > as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make > world. Well, that makes a list of one. Can you provide more information (e.g. a transcript?) Are you using openssl-rsaref, or openssl with no RSA (the latter will break many ports, the former has a restrictive license). Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:51:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id CFEB914EDB for ; Mon, 17 Jan 2000 12:51:31 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id PAA29739; Mon, 17 Jan 2000 15:49:43 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000117115648.C53965@relay.nuxi.com> Date: Mon, 17 Jan 2000 15:49:43 -0500 (EST) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: "David O'Brien" Subject: Re: C++ exceptions doesn't work in shared libraries Cc: Maxim Sobolev , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I cannot comment on OpenBSD or Solaris, since I do not have access to them right now. My guess is that OpenBSD and Solaris x86 either 1. do not use sjlj exception propagation, or 2. do not use _builtin_setjmp Linux does not use sjlj exceptions for sure and as a result it is not affected by this bug. In case when they do not use sjlj exceptions, appropriate EBX restoration code is provided by the exception_receiver RTL. Unfortunately, G++ only emits exception_receiver when using non-sjlj exceptions. In my first patch I tried to force exception_receiver to be emitted in for sjlj exceptions too, but only when GCC uses builtin{setjmp|longjmp} implementations. Standard C library setjmp/longjmp should have EBX preserved correctly already and thus do not need any special code. I have looked at Aplha backend and found out, that Alpha does the right thing and tries to restore its equivalent of PIC register on setjmp receive point, so apparently, GCC expects _builtin_setjmp and builtin_longjmp to do all necessary register preservations. i386 backend clearly fails to do that. On 17-Jan-00 David O'Brien wrote: > On Mon, Jan 17, 2000 at 02:51:00PM -0500, Alexander N. Kabaev wrote: >> As I already pointed out in private message, this bug is in fact i386 >> specific and it was wrong to fix it in gcc/except.c file. The real >> problem is that default builtin_setjmp implementation does not restore >> any registers except for stack pointers when doing nonlocal jump. This >> means, that every platform, that needs to store/restore some other >> state between jumps, has to provide appropriate definitions for >> builtin_setjmp_setup and builtin_setjmp_receiver RTL expansions. > > Why doesn't OpenBSD, Linux, or Solaris x86 need this patch? > >> That is exactly what I do in a second (improved, I hope) patch I have >> sent to David yesterday. > > I may go with this patch, but I need to understand more why it is needed > before I take a file off the vendor branch. Any help would be > appreciated. > > -- > -- David (obrien@NUXI.com) ---------------------------------- E-Mail: Alexander N. Kabaev Date: 17-Jan-00 Time: 14:57:58 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:52:32 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E29C914FDF; Mon, 17 Jan 2000 12:52:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D718F1CD40E; Mon, 17 Jan 2000 12:52:29 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 12:52:29 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Cc: ports@freebsd.org Subject: Rolling OSVERSION Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless anyone objects I'm going to bump OSVERSION tonight to provide a cutoff for whether or not openssl is available in the base system. Ports need to behave differently in either case.. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 12:54:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 22B67152F8 for ; Mon, 17 Jan 2000 12:54:32 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id PAA04909; Mon, 17 Jan 2000 15:58:29 -0500 From: Bill Paul Message-Id: <200001172058.PAA04909@skynet.ctr.columbia.edu> Subject: Re: /dev/sndstat To: gjvc@extremis.demon.co.uk (George Cox) Date: Mon, 17 Jan 2000 15:58:27 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <20000117193002.A259@extremis.demon.co.uk> from "George Cox" at Jan 17, 2000 07:30:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1065 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, George Cox had to walk into mine and say: > I cvsupped yesterday. I install a complete snapshot today. > extremis /dev # ./MAKEDEV sndstat0 > expr: non-numeric argument > bad node: mknod mixerstat0 > > Something's wrong :-) No, nothing is wrong: x-ctr# cd /dev x-ctr# ./MAKEDEV snd0 x-ctr# ls -l /dev/sndstat crw-rw-rw- 1 root wheel 30, 6 Jan 17 10:51 /dev/sndstat /dev/sndstat is created as a consequence of creating doing MAKEDEV snd0. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 13: 7:11 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 42C3D14F1A; Mon, 17 Jan 2000 13:07:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 329AD1CD468; Mon, 17 Jan 2000 13:07:07 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 13:07:07 -0800 (PST) From: Kris Kennaway To: ports@freebsd.org Cc: current@freebsd.org Subject: USE_OPENSSL Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Cross-posting to -current because I would like some feedback about the last paragraph - namely how to test for RSA capability] How about the following: 1) I bump OSVERSION due to the (potential) presence of openssl in the base system. 2) We add a USE_OPENSSL knob to bsd.port.mk which tests for this and the openssl libraries in /usr/lib, and sets LIB_DEPENDS appropriately. 3) Setting USE_OPENSSL=RSA requires a RSA-capable version of openssl (i.e. they've either built with USA_RESIDENT=NO, or have installed rsaref and rebuilt) and emits an explanatory warning if it's not available. The only problem I can see so far is how to tell whether RSA support is available. We can do a dynamic check to see if openssl(1) can actually do RSA, but that's not as good as an existence check of something. Currently we don't build libRSARefglue.a because I couldn't see what it was useful for (it's rolled into libcrypto for us), but this still wouldn't differentiate between an (international) full openssl a (USA) neutered one without rsaref. Hmm, it may cause problems for ports which expect it, though :-( Stuffing a file in /etc is an obvious solution, but there may be a better one. Anyone? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 13:40:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 6509514FD8; Mon, 17 Jan 2000 13:40:20 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id NAA94764; Mon, 17 Jan 2000 13:40:18 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000117131750.00a9d8f0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 17 Jan 2000 13:40:18 -0800 To: Kris Kennaway , Jim Bloom From: Manfred Antar Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: References: <38837E05.72203F31@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:50 PM 1/17/00 -0800, Kris Kennaway wrote: >On Mon, 17 Jan 2000, Jim Bloom wrote: > > > Add lynx-ssl to the list of ports which are broken on current. This was > > as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make > > world. > >Well, that makes a list of one. Can you provide more information (e.g. a >transcript?) Are you using openssl-rsaref, or openssl with no RSA (the >latter will break many ports, the former has a restrictive license). > >Kris Here is another one apache13-php3 when compiled with modssl . I'm using RSA. It builds and installs fine but when starting the server with ssl : #apachectl startssl the following error occurs : Syntax error on line 240 of /usr/local/etc/apache/apache.conf: Cannot load /usr/local/libexec/apache/libssl.so into server: /usr/lib/libcrypto.so.1: Undefined symbol "R_RandomUpdate" /usr/local/sbin/apachectl startssl: httpd could not be started It can be fixed by adding -L/usr/local/lib -lrsaref to the SSL_LIBS= line in /usr/ports/www/apache13-php3/work/apache_1.3.9/src/modules/ssl/Makefile Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 13:41:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id 93D5014EEA; Mon, 17 Jan 2000 13:41:11 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id QAA64138; Mon, 17 Jan 2000 16:40:43 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38838C5B.EC50719A@acm.org> Date: Mon, 17 Jan 2000 16:40:43 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the sequence I used for installing thing yesterday when I had the problem. First, I cvsup'ed and did a make world. Next, I installed the rsaref-2.0 port. Finally, I tried to make the lynx-ssl port. The basic problem is that some of the include files are not being found (ssl.h and crypto.h). I haven't read everything closely, but I believe that the source uses #include #include and puts -I${PREFIX}/include/openssl (in the Makefile) in CFLAGS. This might be fixed by changing the source to #include #include and having -I${PREFIX}/include in CFLAGS. Here is the build log minus the configuration output: ===> Extracting for lynx-ssl-2.8.2.1 >> Checksum OK for lynx2.8.2rel.1.tar.gz. >> Checksum OK for lynx-282-ssl.patch.gz. ===> lynx-ssl-2.8.2.1 depends on executable: openssl - found ===> lynx-ssl-2.8.2.1 depends on shared library: crypto.1 - found ===> lynx-ssl-2.8.2.1 depends on shared library: ssl.1 - found ===> Patching for lynx-ssl-2.8.2.1 ===> Applying distribution patches for lynx-ssl-2.8.2.1 ===> Applying FreeBSD patches for lynx-ssl-2.8.2.1 ===> Configuring for lynx-ssl-2.8.2.1 ... (Config deleted) ... ===> Building for lynx-ssl-2.8.2.1 PATH=.:$PATH; export PATH; /bin/sh -c './cfg_defs.sh' Constructing sed-script sed -e '/^#/d' -e '/^$/d' -e 's%\(.*\)=\(.*\@.*\)$%s=@\1@=\2=g%' -e 's%\(. *\)=\(http:.*\)$%s=@\1@=\2=g%' -e 's%\(.*\)=\(ftp:.*\)$%s=@\1@=\2=g%' -e 's%\( .*\)=\(.*\.html\)$%s=@\1@=\2=g%' ./lynx_help/help_files.txt | tr '=' '%' > hel p_files.sed Creating LYHelp.h ********************************************** Help files will NOT be gzipped. ********************************************** cd WWW/Library/Implementation && make CC="cc" LY_CFLAGS="-O -pipe -I/usr/local/ include/openssl" CPPFLAGS="" LYFLAGS="-I/usr/local/include -DUSE_SSL" cc -DHAVE_CONFIG_H -I/usr/local/include -DUSE_SSL -I../../.. -I../../../src -I../../.. -I../../../src -I../../../WWW/Library/Implementation -O -pipe -I/u sr/local/include/openssl -I/usr/local/include -DUSE_SSL -I../../../WWW/Library/ Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH -c ../../../WWW/Library/Implementat ion/HTParse.c cc -DHAVE_CONFIG_H -I/usr/local/include -DUSE_SSL -I../../.. -I../../../src -I../../.. -I../../../src -I../../../WWW/Library/Implementation -O -pipe -I/u sr/local/include/openssl -I/usr/local/include -DUSE_SSL -I../../../WWW/Library/ Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH -c ../../../WWW/Library/Implementat ion/HTAccess.c cc -DHAVE_CONFIG_H -I/usr/local/include -DUSE_SSL -I../../.. -I../../../src -I../../.. -I../../../src -I../../../WWW/Library/Implementation -O -pipe -I/u sr/local/include/openssl -I/usr/local/include -DUSE_SSL -I../../../WWW/Library/ Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH -c ../../../WWW/Library/Implementat ion/HTTP.c ../../../WWW/Library/Implementation/HTTP.c:15: ssl.h: No such file or directory ../../../WWW/Library/Implementation/HTTP.c:16: crypto.h: No such file or directo ry ../../../WWW/Library/Implementation/HTTP.c:75: syntax error before `*' ../../../WWW/Library/Implementation/HTTP.c:75: warning: data definition has no t ype or storage class ../../../WWW/Library/Implementation/HTTP.c:83: syntax error before `*' ../../../WWW/Library/Implementation/HTTP.c: In function `HTGetSSLHandle': ../../../WWW/Library/Implementation/HTTP.c:90: warning: assignment makes pointer from integer without a cast ../../../WWW/Library/Implementation/HTTP.c:91: request for member `cert' in some thing not a structure or union ../../../WWW/Library/Implementation/HTTP.c:100: warning: return makes pointer fr om integer without a cast ../../../WWW/Library/Implementation/HTTP.c: In function `HTLoadHTTP': ../../../WWW/Library/Implementation/HTTP.c:178: `SSL' undeclared (first use in t his function) ../../../WWW/Library/Implementation/HTTP.c:178: (Each undeclared identifier is r eported only once ../../../WWW/Library/Implementation/HTTP.c:178: for each function it appears in. ) ../../../WWW/Library/Implementation/HTTP.c:178: `handle' undeclared (first use i n this function) ../../../WWW/Library/Implementation/HTTP.c:323: warning: passing arg 1 of `HTPro gress' makes pointer from integer without a cast *** Error code 1 Jim Bloom bloom@acm.org Kris Kennaway wrote: > > On Mon, 17 Jan 2000, Jim Bloom wrote: > > > Add lynx-ssl to the list of ports which are broken on current. This was > > as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make > > world. > > Well, that makes a list of one. Can you provide more information (e.g. a > transcript?) Are you using openssl-rsaref, or openssl with no RSA (the > latter will break many ports, the former has a restrictive license). > > Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 13:56:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5123D14A31; Mon, 17 Jan 2000 13:56:40 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA58642; Mon, 17 Jan 2000 13:56:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA38148; Mon, 17 Jan 2000 13:56:40 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2000 13:56:40 -0800 From: "David O'Brien" To: Kris Kennaway Cc: current@freebsd.org Subject: Re: Mandating USA_RESIDENT Message-ID: <20000117135639.A38119@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Mon, Jan 17, 2000 at 01:06:24AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 01:06:24AM -0800, Kris Kennaway wrote: > In order to know whether or not to build the patent-restricted RSA code, > the openssl build needs to look at the value of USA_RESIDENT, which isn't > set by default. If this value is unset, or anything other than 'NO'[*], it > assumes the user is in the USA and doesn't build the RSA code Due to the concequence involved, you really do need to check for 'NO', 'YES', and "other". Rather than combining 'YES' and "other". -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14: 0:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 6145914FA6 for ; Mon, 17 Jan 2000 14:00:28 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA23322; Mon, 17 Jan 2000 17:00:14 -0500 (EST) Message-ID: <20000117170014.A22939@netmonger.net> Date: Mon, 17 Jan 2000 17:00:14 -0500 From: Christopher Masto To: Jesper Skriver , Warner Losh Cc: current@FreeBSD.ORG Subject: Re: apm suspend ?? References: <20000116205650.A64495@skriver.dk> <200001171818.LAA10403@harmony.village.org> <20000117212038.A69519@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <20000117212038.A69519@skriver.dk>; from Jesper Skriver on Mon, Jan 17, 2000 at 09:20:38PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote: > On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: > > In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: > > : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now > > : suspend doesn't work as expected. > > : > > : When I run 'apm -z' the laptop suspends as normal, but right after this > > : the harddisk led turns on, and it powers up again. > > > > That's very odd. apm hasn't changed since Dec 2 and even that was > > just deleting code that had been obsolete for a while now. > > I don't get it either - will try to revert to -CURRENT as of jan 5th, > and see if it works again ... Sometimes the "enter" at the end of the command is sufficient to wake the machine back up. Have you tried "sleep 2; apm -z"? Just a stupid guess. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14: 4:24 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2B4C414F26; Mon, 17 Jan 2000 14:04:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1481C1CD643; Mon, 17 Jan 2000 14:04:23 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 14:04:23 -0800 (PST) From: Kris Kennaway To: David O'Brien Cc: current@freebsd.org Subject: Re: Mandating USA_RESIDENT In-Reply-To: <20000117135639.A38119@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, David O'Brien wrote: > Due to the concequence involved, you really do need to check for 'NO', > 'YES', and "other". Rather than combining 'YES' and "other". You're suggesting not building openssl at all if they don't have a boolean value? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14: 4:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2DF1715043 for ; Mon, 17 Jan 2000 14:04:42 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA58659; Mon, 17 Jan 2000 14:04:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA38178; Mon, 17 Jan 2000 14:04:40 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2000 14:04:40 -0800 From: "David O'Brien" To: Carl Makin Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.4 -> current upgrade/bootstrap problem Message-ID: <20000117140440.B38119@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <03db01bf604c$dae9ce40$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from carl@xena.aipo.gov.au on Mon, Jan 17, 2000 at 12:39:12PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 12:39:12PM +1100, Carl Makin wrote: > Here is what I did... > > 1. install gcc 2.95 port. > 2. cd /usr/bin and rename cc and gcc to *.old and symlink cc and gcc to > /usr/local/bin/gcc295 (Remember to delete the .old entries once you're > finished) This is definately the wrong thing to be doing. I don't guarentee that the GCC 2.95 port can properly build world or kernels on 3.4. Anyway, the upgrade should be self-hosting, and this approach isn't. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14: 6:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (Postfix) with ESMTP id 3428314FA6 for ; Mon, 17 Jan 2000 14:06:56 -0800 (PST) (envelope-from ejh@ejhslu.eas.slu.edu) Received: from ejhslu.eas.slu.edu (ejhslu.eas.slu.edu [165.134.8.243]) by mnw.eas.slu.edu (8.9.3/8.9.3) with ESMTP id QAA04408; Mon, 17 Jan 2000 16:06:14 -0600 (CST) Received: (from ejh@localhost) by ejhslu.eas.slu.edu (8.9.3/8.9.3) id QAA01820; Mon, 17 Jan 2000 16:06:13 -0600 (CST) Date: Mon, 17 Jan 2000 16:06:13 -0600 (CST) From: "Eric J. Haug" Message-Id: <200001172206.QAA01820@ejhslu.eas.slu.edu> To: wpaul@skynet.ctr.columbia.edu Subject: Re: USB D-Link DSB-650 kue0: failed to load code Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Subject: Re: USB D-Link DSB-650 kue0: failed to load code > To: ejh@eas.slu.edu (Eric J. Haug) > Date: Mon, 17 Jan 2000 15:48:42 -0500 (EST) > X-Loop: FreeBSD.ORG > > > > > I have a Toshiba 2100CDS laptop with an OHCI USB controller > > that gives a kue0: failed to load code segment error message > > kue0: D-Link Corp 10Mbps ethernet adapter, rev 1.00/0.02, addr 2 > > kue0: failed to load code segment: IOERROR > > device_probe_and_attach: kue0 attach returned 6 > > An important point which you neglect to mention is: how long did it > take before the IOERROR message appeared? (That is, how much time > passed between the first kue0 probe message and the next?) Getting the > > If the IOERROR message appears after only a second or two (or maybe > three), then the timeout may not be long enough for your machine. If > it sits there for a long time (ten seconds or longer) then it's probably > something else. It goes by very fast. The only time that the USB device can be recognized is at boot time. Running usbd and plugging in the device results in usb0: unrecoverable error, controller halted. usbd_new_device: addr=2, getting first desc failed uhub_explore: usb_new_device failed, error=TIMEOUT uhub0: device problem, disabling port 1 > - Find the kue_do_request() function. > - Change the timeout from 500000 to 1000000, i.e. change this: > > usbd_setup_default_xfer(xfer, dev, 0, 1000000, req, > data, UGETW(req->wLength), USBD_SHORT_XFER_OK, 0); After this change Again, the boot message rushes by. But later, say about 8 seconds or so about the time the system is printing out ppc0 messages i get panic: removing other than first element. This panic seems to be in usb_transfer_complete when the SIMPLEQ_REMOVE_HEAD macro is executed. ddb trace reveals: shutdown_panic panic usb_transfer_complete ... at 0xd4 ohci_process_done ... at 0x121 ohci_intr1 ... 0x137 ohci_intr ... at 0x36 Xresume11 ... at 0x2b --- interrupt vec1 ... at 0x2 mi_startup ... at 0x70 begin eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:19:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 06DAF14D0C for ; Mon, 17 Jan 2000 14:19:42 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id RAA68144 for current@freebsd.org; Mon, 17 Jan 2000 17:25:37 -0500 (EST) (envelope-from dervish) Date: Mon, 17 Jan 2000 17:25:37 -0500 From: Bush Doctor To: current@freebsd.org Subject: buildworld failure in "===> makeinfo" Message-ID: <20000117172537.F21380@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "make buildworld" fails with sources cvsup'd around 17:00 est ... whereintheworld.pl (thanxs Bill Fenner) shows ... -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- A tail -35 gives ... building standard txi library ranlib libtxi.a ===> makeinfo cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/cmds.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/defun.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/files.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/footnote.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/html.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/index.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/insertion.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/lang.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/macro.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/makeinfo.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/multi.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/node.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/sectioning.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf o/../../../../contrib/texinfo/makeinfo/toc.c cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -o makeinfo cmds.o defun.o files.o foo tnote.o html.o index.o insertion.o lang.o macro.o makeinfo.o multi.o node.o sectioning.o toc.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/te xinfo/makeinfo/../libtxi/libtxi.a /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot open crt1.o: No such file or directory *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo. *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 #:^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:26:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 71EB914FE5; Mon, 17 Jan 2000 14:26:08 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA02541; Mon, 17 Jan 2000 14:26:00 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA01426; Mon, 17 Jan 2000 14:26:00 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 17 Jan 2000 14:26:00 -0800 (PST) Message-Id: <200001172226.OAA01426@vashon.polstra.com> To: kris@hub.freebsd.org Subject: Re: Rolling OSVERSION In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Kris Kennaway wrote: > Unless anyone objects I'm going to bump OSVERSION tonight to provide a > cutoff for whether or not openssl is available in the base system. Ports > need to behave differently in either case.. You mean "__FreeBSD_version" (in src/sys/sys/param.h), right? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:34:11 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id DF2AB14E52; Mon, 17 Jan 2000 14:34:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D00511CD643; Mon, 17 Jan 2000 14:34:09 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 14:34:09 -0800 (PST) From: Kris Kennaway To: John Polstra Cc: current@freebsd.org Subject: Re: Rolling OSVERSION In-Reply-To: <200001172226.OAA01426@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, John Polstra wrote: > You mean "__FreeBSD_version" (in src/sys/sys/param.h), right? Right, sorry. OSVERSION is what bsd.port.mk calls it. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:40:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 718DB14E52; Mon, 17 Jan 2000 14:40:14 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-245.ix.netcom.com [209.109.235.245]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id OAA59795; Mon, 17 Jan 2000 14:39:48 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id OAA03096; Mon, 17 Jan 2000 14:38:57 -0800 (PST) To: Kris Kennaway Cc: ports@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile References: From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 17 Jan 2000 14:38:53 -0800 In-Reply-To: Kris Kennaway's message of "Mon, 17 Jan 2000 11:33:43 -0800 (PST)" Message-ID: Lines: 15 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Kris Kennaway * It may be useful - although there are a lot of inconsistencies in how the * openssl ports look for it. Dirk Froemberg was going to help with this - * I'm not sure exactly what the best way to do it is. For example, ports * like w3m-ssl pass the location of the openssl include directory, which * needs to be either /usr/include or ${LOCALBASE}/include. Perhaps the best * thing would be to bump OSVERSION (belatedly). Well, the whole point is to standardize it, ala Motif and perl. Maybe we can pass OPENSSLINCLUDES and OPENSSLLIBS in CONFIGURE_ENV? Can you come up with a list of pathnames that are used in openssl-requiring ports? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:40:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id C1F9D1500D; Mon, 17 Jan 2000 14:40:51 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-245.ix.netcom.com [209.109.235.245]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id OAA59827; Mon, 17 Jan 2000 14:40:28 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id OAA03100; Mon, 17 Jan 2000 14:39:34 -0800 (PST) To: Kris Kennaway Cc: current@freebsd.org, ports@freebsd.org Subject: Re: Rolling OSVERSION References: From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 17 Jan 2000 14:39:30 -0800 In-Reply-To: Kris Kennaway's message of "Mon, 17 Jan 2000 12:52:29 -0800 (PST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Kris Kennaway * Unless anyone objects I'm going to bump OSVERSION tonight to provide a * cutoff for whether or not openssl is available in the base system. Ports * need to behave differently in either case.. Sounds fine, but the people in -current land probably know that variable as __FreeBSD_version.... :) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:46:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 39C5614E53 for ; Mon, 17 Jan 2000 14:46:25 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id DE9FA3E3D; Mon, 17 Jan 2000 23:46:23 +0100 (CET) Date: Mon, 17 Jan 2000 23:46:23 +0100 From: Jesper Skriver To: Christopher Masto Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: apm suspend ?? Message-ID: <20000117234623.A70090@skriver.dk> References: <20000116205650.A64495@skriver.dk> <200001171818.LAA10403@harmony.village.org> <20000117212038.A69519@skriver.dk> <20000117170014.A22939@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000117170014.A22939@netmonger.net>; from chris@netmonger.net on Mon, Jan 17, 2000 at 05:00:14PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 05:00:14PM -0500, Christopher Masto wrote: > On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote: > > On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: > > > In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: > > > : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now > > > : suspend doesn't work as expected. > > > : > > > : When I run 'apm -z' the laptop suspends as normal, but right after this > > > : the harddisk led turns on, and it powers up again. > > > > > > That's very odd. apm hasn't changed since Dec 2 and even that was > > > just deleting code that had been obsolete for a while now. > > > > I don't get it either - will try to revert to -CURRENT as of jan 5th, > > and see if it works again ... > > Sometimes the "enter" at the end of the command is sufficient to wake the > machine back up. Have you tried "sleep 2; apm -z"? Yep, that's not it. I've just verified, by reverting to -CURRENT as of *default date=2000.01.05.12.00.00 Suspend works as expected, tomorrow I'll try at 2 days intervals, to try to narrow down the commit making the difference ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:47: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-51.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.179]) by hub.freebsd.org (Postfix) with ESMTP id EED4F15068 for ; Mon, 17 Jan 2000 14:46:55 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA00657; Mon, 17 Jan 2000 22:46:47 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA31762; Mon, 17 Jan 2000 22:51:11 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001172251.WAA31762@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Warner Losh Cc: Brian Somers , Peter Wemm , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: PnP probing in -current In-Reply-To: Message from Warner Losh of "Mon, 17 Jan 2000 11:22:43 MST." <200001171822.LAA10447@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 22:51:11 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200001171613.QAA25647@hak.lan.Awfulhak.org> Brian Somers writes: > : Without saying it's ``at isa?'' I get only one aha failed line (I'm > : sure I used to get nothing) at boot time. I still see the ADP lines > : though (of course). > > odd. It has been a while since I tried the aha 1542CP card. I'll > have to give it a shot with a releatively current current machine. I take that back. The card isn't seen now unless I say ``at isa?''. > Warner -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 14:49: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-51.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.179]) by hub.freebsd.org (Postfix) with ESMTP id D225914FEA; Mon, 17 Jan 2000 14:49:00 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA00965; Mon, 17 Jan 2000 22:48:58 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA32179; Mon, 17 Jan 2000 22:53:22 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001172253.WAA32179@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Warner Losh Cc: Brian Somers , freebsd-current@FreeBSD.ORG, Peter Wemm , brian@hak.lan.Awfulhak.org Subject: Re: PnP probing in -current In-Reply-To: Message from Warner Losh of "Mon, 17 Jan 2000 11:24:25 MST." <200001171824.LAA10496@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 22:53:22 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200001170238.CAA00850@hak.lan.Awfulhak.org> Brian Somers writes: > : Since the PnP probing code was made unconditional in the bootup > : routines on December 6, I've been having problems with my > : Adaptec 1542CP. > : > : I've got my BIOS set to ``non pnp OS'' and my 1542 set to 0x330. > : I've never had ``options pnp0'' in my config, and on December 6 (when > : isa/pnp.c and isa/pnpprobe.c started being included with isa devices > : rather than with ``options pnp*'', the card stopped being probed. > : > : If I skip the code in pnp_identify() in isa/pnp.c, everything works > : fine. > : > : Are there any plans to re-optionify this code ? > : > : I can provide more details once I rebuild my machine.... See my > : other post about some ata problems, coming to a -current list near > : you ! > > So you have your 1542CP hardware set to be hardwired at 0x330 and not > in PnP mode? Is that correct? If so, then why is it responding to > the PnP probes. It shouldn't be. I've no idea, but this is what's happening. Just before the boot: prompt, the BIOS confirms that the card is taking on 0x330/irq11/drq7. > Warner -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15: 6:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 8560D14E39 for ; Mon, 17 Jan 2000 15:06:46 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 10271 invoked from network); 17 Jan 2000 23:06:40 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 17 Jan 2000 23:06:40 -0000 Message-ID: <3883A052.9107353A@cvzoom.net> Date: Mon, 17 Jan 2000 18:05:54 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: vallo@matti.ee Cc: Ollivier Robert , FreeBSD Current Users' list Subject: Re: XFree86 3.9.17 References: <20000117181923.A60855@caerdonn.eurocontrol.fr> <20000117220253.A20605@myhakas.matti.ee> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vallo Kallaste wrote: > Have you tried to install it? It does builds but barfs at some point for > install process. Not that I care so much about it, 3.3.6 works for my > G400 now, thanks god. What I did was: build it using the stock gcc-2.95.2 compiler, for make World. During make install, I switched compilers by setting PATH=/usr/local/bin:$PATH. The compiler I used was the development version of gcc, gcc-2.96-current. After switching compilers, the install went OK. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15:16:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 2A5D914F7E; Mon, 17 Jan 2000 15:15:40 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id BAA24425; Tue, 18 Jan 2000 01:16:49 +0200 (EET) (envelope-from ru) Date: Tue, 18 Jan 2000 01:16:48 +0200 From: Ruslan Ermilov To: green@FreeBSD.org, Bush Doctor Cc: current@FreeBSD.org Subject: Re: buildworld failure in "===> makeinfo" Message-ID: <20000118011648.A22643@relay.ucb.crimea.ua> Mail-Followup-To: green@FreeBSD.org, Bush Doctor , current@FreeBSD.ORG References: <20000117172537.F21380@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="J2SCkAp4GZ/dPZZf" X-Mailer: Mutt 0.95.3i In-Reply-To: <20000117172537.F21380@goku.cl.msu.edu>; from Bush Doctor on Mon, Jan 17, 2000 at 05:25:37PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii On Mon, Jan 17, 2000 at 05:25:37PM -0500, Bush Doctor wrote: > "make buildworld" fails with sources cvsup'd around 17:00 est ... > > whereintheworld.pl (thanxs Bill Fenner) shows ... > > -------------------------------------------------------------- > >>> Rebuilding the temporary build tree > -------------------------------------------------------------- > >>> stage 1: bootstrap tools > -------------------------------------------------------------- > >>> stage 2: cleaning up the object tree > -------------------------------------------------------------- > >>> stage 2: rebuilding the object tree > -------------------------------------------------------------- > >>> stage 2: build tools > -------------------------------------------------------------- > >>> stage 3: cross tools > -------------------------------------------------------------- > > A tail -35 gives ... > > building standard txi library > ranlib libtxi.a > ===> makeinfo > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/cmds.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/defun.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/files.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/footnote.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/html.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/index.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/insertion.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/lang.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/macro.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/makeinfo.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/multi.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/node.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/sectioning.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinf > o/../../../../contrib/texinfo/makeinfo/toc.c > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/sr > c/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -o makeinfo cmds.o defun.o files.o foo > tnote.o html.o index.o insertion.o lang.o macro.o makeinfo.o multi.o node.o sectioning.o toc.o /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/te > xinfo/makeinfo/../libtxi/libtxi.a > /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot open crt1.o: No such file or directory > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/texinfo. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > Could you please try the following patch? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: Makefile.inc1 =================================================================== @@ -168,7 +168,7 @@ TMAKE= ${TMAKEENV} ${MAKE} -f Makefile. XMAKEENV= ${BOOTSTRAPENV} \ TARGET_ARCH=${MACHINE_ARCH} XMAKE= ${XMAKEENV} ${MAKE} -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML \ - -DNO_FORTRAN -DNO_GDB + -DNO_FORTRAN -DNO_GDB -DNOSHARED # world stage WMAKEENV= ${CROSSENV} \ --J2SCkAp4GZ/dPZZf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15:27:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 5CDF015043 for ; Mon, 17 Jan 2000 15:27:06 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA05198; Mon, 17 Jan 2000 18:31:03 -0500 From: Bill Paul Message-Id: <200001172331.SAA05198@skynet.ctr.columbia.edu> Subject: Re: USB D-Link DSB-650 kue0: failed to load code To: ejh@eas.slu.edu (Eric J. Haug) Date: Mon, 17 Jan 2000 18:31:02 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <200001172206.QAA01820@ejhslu.eas.slu.edu> from "Eric J. Haug" at Jan 17, 2000 04:06:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2078 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Eric J. Haug had to walk into mine and say: > > > - Find the kue_do_request() function. > > - Change the timeout from 500000 to 1000000, i.e. change this: > > > > usbd_setup_default_xfer(xfer, dev, 0, 1000000, req, > > data, UGETW(req->wLength), USBD_SHORT_XFER_OK, 0); > > After this change > Again, the boot message rushes by. > But later, say about 8 seconds or so > about the time the system is printing out ppc0 messages > i get > panic: removing other than first element. *sigh* Whatever. Fortunately, it turns out I had an OHCI controller here and I was able to duplicate this problem. (It doesn't happen with my laptop and UHCI controller, otherwise I could have spotted it before.) I just updated the driver in -current to fix this. The driver tries to check if the firmware is already running by reading the MAC address. It turns out that doing this when the firmware is not running generates a 0 length transfer. This doesn't seem to do any harm with a UHCI controller, but it makes the OHCI controller (or its driver) mad. I changed the code to test for the presence of already running firmware in a different way, and now it seems to work with my test system. Make sure to get src/sys/dev/usb/if_kue.c revision 1.16. This version should fix the problem. I also noticed that performance with the OHCI controller is significantly better than with the UHCI controller. Just my rotten luck I'm stuck with a UHCI one in my laptop. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15:33: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 923C415054 for ; Mon, 17 Jan 2000 15:32:59 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA57398; Mon, 17 Jan 2000 18:32:47 -0500 (EST) Date: Mon, 17 Jan 2000 18:32:47 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: frank@exit.com, current@FreeBSD.ORG Subject: Re: 3C589 problems? In-Reply-To: <200001171827.LAA10533@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Warner Losh wrote: > In message <200001171454.GAA69760@realtime.exit.com> Frank Mayhar writes: > : I just want to know if anyone else is still having problems with their > : 3C589 or 574 after Matt Dodd's latest series of checkins. > > Yea. I'm only getting 950KiB/s with ftp. I'm bummed. Matt was > geting 1.1MiB/s :-(. Actually, David O'Brien was getting near that; I've got a Vadem 365 (ISA) PCIC board and while my performance isn't wonderful it is usable. I get pretty good speeds on the ISA/EISA/MCA boards though. Like you, I suspect that Frank has an IRQ problem of some sort. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15:42:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id C154914DF5; Mon, 17 Jan 2000 15:42:34 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id QAA16040; Mon, 17 Jan 2000 16:42:12 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Mon, 17 Jan 2000 16:42:11 -0700 (MST) From: Doug Russell To: Ruslan Ermilov Cc: green@FreeBSD.ORG, Bush Doctor , current@FreeBSD.ORG Subject: Re: buildworld failure in "===> makeinfo" In-Reply-To: <20000118011648.A22643@relay.ucb.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Ruslan Ermilov wrote: > On Mon, Jan 17, 2000 at 05:25:37PM -0500, Bush Doctor wrote: > > "make buildworld" fails with sources cvsup'd around 17:00 est ... > > > > /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot open crt1.o: No such file or directory > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo. > > *** Error code 1 > > > Could you please try the following patch? I'm having the same problem with sources about 17:07 EST. (I'm MST.) ROOT crystal:/usr/sup 251 > dir src-all total 3656 -rw-rw-r-- 1 root wheel 3730624 Jan 17 15:07 checkouts.cvs:. The patch did not help. I'm re-cvsupping and trying again with and without the -DNOSHARED now. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15:52: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id B0F1A1503C for ; Mon, 17 Jan 2000 15:51:58 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id AAA59497 for ; Tue, 18 Jan 2000 00:51:45 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <01dd01bf6145$e13d6c80$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: Why not a default number of pings? Date: Tue, 18 Jan 2000 00:51:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been hit by a "forgotten ping" again. I still do not see a reason for not having a default number of pings, = instead of infinite. The only reason I've seen is "It's always been so". Even if a default of 4 pings is not acceptable, because windows does it = that way, why not a large default then? If somebody _really_ want to ping forever, let them use -t0, and defend = the rest of us from our blunders of forgetting a ping, keeping the line = open infinitely. How about a MAX_PING=3D3600 in make.conf or so? I've supplied patches earlier, but they've been rejected. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 15:52:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id AA4011508C for ; Mon, 17 Jan 2000 15:52:16 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id AAA59494 for ; Tue, 18 Jan 2000 00:51:45 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <01da01bf6145$e0fa4900$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: ppp, incoming mail keeping the line up. Date: Tue, 18 Jan 2000 00:44:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I run user-ppp, and I have a mx-record for my system, so incoming mail = goes directly to my system. Now I'm afraid if I'm on a a mailing list with a frequency of mail = faster than my timeout period, I could be online a very long time. If I filter incoming smtp wuth the alive-filter, I guess I'd be shutting = the line down in the middle of recieving mail. Or is it possible to specify a shorter alive-time for mail only?=20 Sort of "any traffic will keep the line up for 10 seconds, traffic = allowed by afilter will keep the line for 2 minutes". Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16: 2:20 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 89AE414F3A; Mon, 17 Jan 2000 16:02:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 738AB1CD644; Mon, 17 Jan 2000 16:02:18 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 17 Jan 2000 16:02:18 -0800 (PST) From: Kris Kennaway To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Why not a default number of pings? In-Reply-To: <01dd01bf6145$e13d6c80$0e00a8c0@neland.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Leif Neland wrote: > If somebody _really_ want to ping forever, let them use -t0, and > defend the rest of us from our blunders of forgetting a ping, keeping > the line open infinitely. I use ping for precisely this purpose. Yes, I could change my setup, but so could you :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16: 3:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3AAD714F9B for ; Mon, 17 Jan 2000 16:03:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id QAA21239; Mon, 17 Jan 2000 16:25:08 -0800 (PST) Date: Mon, 17 Jan 2000 16:25:08 -0800 From: Alfred Perlstein To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Why not a default number of pings? Message-ID: <20000117162508.D16038@fw.wintelcom.net> References: <01dd01bf6145$e13d6c80$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <01dd01bf6145$e13d6c80$0e00a8c0@neland.dk>; from leifn@neland.dk on Tue, Jan 18, 2000 at 12:51:26AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Leif Neland [000117 16:16] wrote: > I've been hit by a "forgotten ping" again. > > I still do not see a reason for not having a default number of pings, instead of infinite. > The only reason I've seen is "It's always been so". > > Even if a default of 4 pings is not acceptable, because windows does it that way, why not a large default then? > > If somebody _really_ want to ping forever, let them use -t0, and defend the rest of us from our blunders of forgetting a ping, keeping the line open infinitely. > > How about a MAX_PING=3600 in make.conf or so? > > I've supplied patches earlier, but they've been rejected. Please provide a reference to the PR you submitted and I'll have a look. I don't think this modification will go in unless it's based on the 'MAX_PING=3600' idea with a default for infinity. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16:13:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (Postfix) with ESMTP id A6D1014EC5 for ; Mon, 17 Jan 2000 16:13:37 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg130-101.ricochet.net [204.179.130.101]) by geocities.com (8.9.3/8.9.3) with ESMTP id QAA14799; Mon, 17 Jan 2000 16:13:16 -0800 (PST) Message-ID: <3883B0F4.60A1623F@geocities.com> Date: Mon, 17 Jan 2000 16:16:52 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: current@FreeBSD.ORG, Gerald Abshez Subject: Re: NFS and Samba (file transfer crashes system) References: <387FDF2D.575DC537@geocities.com> <200001150528.VAA95955@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > If the machine still crashes then we need to know what the panic message > is. It may be useful to configure a kernel with DDB enabled to cause it > to drop into DDB on a crash (this assuming you aren't running X on the > machine, since DDB only runs on the console). In that case you should be > able to obtain the panic message and do a 'trace' to get more detailed > information on where the box is crashing. > > -Matt > Matthew Dillon > With my first posting i was following current as of 20000110. The system simply freezes and i have to reset when i transfer files from win9x (workstation--by drag and drop), linux and freebsd 3.2 (individual workstations--nfs clients by issuing cp command) to the system (nfs and samba server)... as well as transfering files from the system to win9x (explorer--by drag and drop). I had since upgraded to current-20000114 evening and compiled a kernel and the same happens. I also have to run fsck manually about 90 percent of the time i reboot with lots of "counts in the super-block wrong" and "incorrect link counts" on the slice i transfer files to/from, plus a couple of files corrupted. But after reading and following matt's instructions i have had four crash panics with these results: ----------------- kernel.0 vmcore.0 panic: ffs_blkfree: bad size syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 26m34s dumping to dev #ad/0x20021, offset 864256 dump ata2: resetting devices .. done (kgdb) where #0 0xc01372b0 in boot ( ) #1 0xc0137634 in poweroff_wait ( ) #2 0xc01ceee3 in ffs_blkfree ( ) #3 0xc01d1335 in ffs_indirtrunc ( ) #4 0xc01d0e8d in ffs_truncate ( ) #5 0xc01d896e in ufs_setattr ( ) #6 0xc01dac45 in ufs_vnoperate ( ) #7 0xc0195f5c in nfsrv_setattr ( ) #8 0xc01b0bd1 in nfssvc_nfsd ( ) #9 0xc01b04eb in nfssvc ( ) #10 0xc020ee26 in syscall ( ) #11 0xc0201b06 n Xint0x80_syscall ( ) #12 0x80480f9 in ?? ( ) ---------------- kernel.1 vmcore.1 IdlePTD 2994176 initial pcb at 2699e0 panicstr: from debugger panic messages: --- Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc018c039 stack pointer = 0x10:0xc433bcb0 frame pointer = 0x10:0xc433bd04 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 91 (nfsd) interrupt mask panic: from debugger Uptime: 2h51m38s dumping to dev #ad/0x20021, offset 864256 dump ata2: resetting devices .. done (kgdb) where #0 0xc013afb4 in boot ( ) #1 0xc013b351 in panic ( ) #2 0xc011bcf9 in db_panic ( ) #3 0xc011bc99 in db_command ( ) #4 0xc011bd5e in db_command_loop ( ) #5 0xc011dde7 in db_trap ( ) #6 0xc0206d05 in kdb_trap ( ) #7 0xc02150d8 in trap_fatal ( ) #8 0xc0214ae3 in trap ( ) #9 0xc018c039 in ip_output ( ) #10 0xc0193060 in udp_output ( ) #11 0xc0193298 in upd_send ( ) #12 0xc0156183 in sosend ( ) #13 0xc01ad56a in nfs_send ( ) #14 0xc01b4d81 in nfssvc_nfsd ( ) #15 0xc01b4477 in nfssvc ( ) #16 0xc0215336 in syscall ( ) #17 0xc0207606 in Xint0x80_syscall ( ) #18 0x80480f0 in ?? ( ) The last two panics have the same infos as "kernel.1 vmcore.1." So, I will be "cvsup" this afternoon, hoping things work, and yes I will add DEBUG-g option next time I compile the kernel :-). Also, please let me know if I am writing any redundant infos or if I should include any other infos from kgdb when posting a panic message. Sorry for the ignorance but I am still familiarizing with how things work in -current. arnee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16:13:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id 5923C150D6 for ; Mon, 17 Jan 2000 16:13:50 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.117.184]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOI005JH880GG@mta3.snfc21.pbi.net> for current@FreeBSD.ORG; Mon, 17 Jan 2000 16:05:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id F194F918D2; Mon, 17 Jan 2000 16:04:47 -0800 (PST) Date: Mon, 17 Jan 2000 16:04:47 -0800 (PST) From: Alex Zepeda Subject: Re: USB D-Link DSB-650 kue0: failed to load code In-reply-to: <200001172331.SAA05198@skynet.ctr.columbia.edu> To: Bill Paul Cc: current Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Bill Paul wrote: > I also noticed that performance with the OHCI controller is significantly > better than with the UHCI controller. Just my rotten luck I'm stuck > with a UHCI one in my laptop. Ok, with all this flurry of USB development, I keep seeing UHCI and OHCI. What's the difference? - alex who thought USB ethernet was bad until he had to buy an AAUI transciever .. builtin ethernet my ass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16:17: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id B815014F9B for ; Mon, 17 Jan 2000 16:16:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02174; Mon, 17 Jan 2000 16:24:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001180024.QAA02174@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: New softupdates panic In-reply-to: Your message of "Fri, 14 Jan 2000 21:33:31 PST." <200001150533.VAA95996@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 16:24:16 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :Uniprocessor kernel, checking out /sys from an NFS-mounted repository, > :kernel built from sources current as of this afternoon. > :(apologies for any typos, no serial console) > : > :panic: initate_write_inodeblock: already started > > Checking out from an NFS mounted repository into a local > filesystem w/ softupdates enabled? That's correct. > ... > :panic() > :initiate_write_inodeblock() > :softdep_disk_io_initiation() > :spec_stratety() > :bwrite() > :vop_stdbwrite() > :vop_defaultop() > :vfs_bio_awrite() > :spec_fsync() > :sched_sync() > :fork_trampoline() > > This is definitely new, I've never seen this one before. I'll try > to reproduce it on monday when I get back to Berkeley. In the mean > time, please see if you can reproduce the panic. If we can get the > panic reproducable then I can reproduce it on my test box and handle > all the crash dump nicities to hand over to Kirk. I've just built a kernel current as of a few minutes ago, and it's entirely reproducible. What can I do for you now? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16:17:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id B0C7015054 for ; Mon, 17 Jan 2000 16:17:07 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 36653 invoked by uid 1000); 18 Jan 2000 00:17:53 -0000 Date: Tue, 18 Jan 2000 01:17:53 +0100 From: Andreas Braukmann To: Donn Miller Cc: vallo@matti.ee, Ollivier Robert , FreeBSD Current Users' list Subject: Re: XFree86 3.9.17 Message-ID: <20000118011753.A36169@cage.tse-online.de> References: <20000117181923.A60855@caerdonn.eurocontrol.fr> <20000117220253.A20605@myhakas.matti.ee> <3883A052.9107353A@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3883A052.9107353A@cvzoom.net>; from dmmiller@cvzoom.net on Mon, Jan 17, 2000 at 06:05:54PM -0500 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, Jan 17, 2000 at 06:05:54PM -0500, Donn Miller wrote: > > Have you tried to install it? It does builds but barfs at some point for > > install process. Not that I care so much about it, 3.3.6 works for my > > G400 now, thanks god. ... what was the problem with the G400 in earlier revisions? 3.3.5 (built from the port) lives quite happily on my G400? I'm very eager to get my hands on a XFree86 with dual-head support and truetype-rendering, therefor my interest in the XFree86 prereleases. > During make install, I switched compilers by setting > PATH=/usr/local/bin:$PATH. ahhh. > The compiler I used was the development version of gcc, > gcc-2.96-current. Is the gcc-2.96-current in the ports collection? Browsing through /usr/ports/lang I've detected only the older egcs-port? -Andreas -- Andreas Braukmann - irgendwer@internet-adresse.de The computer revolution is over. The computers won. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16:20:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id B0DEC15018 for ; Mon, 17 Jan 2000 16:20:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id QAA15673; Mon, 17 Jan 2000 16:17:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001180017.QAA15673@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Donn Miller Cc: vallo@matti.ee, Ollivier Robert , "FreeBSD Current Users' list" Subject: Re: XFree86 3.9.17 In-reply-to: Your message of "Mon, 17 Jan 2000 18:05:54 EST." <3883A052.9107353A@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 16:17:06 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those using XFree86 3.9.17 or higher and have a Matrox g400 or g200 feel free to use mpegplay or mpeg2play from my ftp site . Both programs have been modified to use the new XFree86 Xv PutImage extension which can do yuv->rgb + scaling hardware assisted -- for instance mpeg play can scale an image to 1600x1200 . You will need this simple patch for Xv if you are running XFree86 3.9.17 : xc/programs/Xserver/Xext diff -c xvdisp.c~ xvdisp.c *** xvdisp.c~ Thu Dec 16 18:18:46 1999 --- xvdisp.c Thu Jan 6 20:54:25 2000 *************** *** 1131,1137 **** --- 1131,1140 ---- ev.shmseg = stuff->shmseg; ev.offset = stuff->offset; WriteEventsToClient(client, 1, (xEvent *) &ev); + + } + return (client->noClientException); } static int --------------------------- ftp://rah.star-gate.com/pub/mpeg2play.tar.gz ftp://rah.star-gate.com/pub/mpeg_play.tar.gz -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 16:48:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 76D3615018 for ; Mon, 17 Jan 2000 16:48:31 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 40806 invoked by uid 1010); 17 Jan 2000 22:00:27 -0000 Date: Mon, 17 Jan 2000 22:00:27 +0000 From: George Cox To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: /dev/sndstat Message-ID: <20000117220027.A32849@extremis.demon.co.uk> References: <20000117193002.A259@extremis.demon.co.uk> <200001172058.PAA04909@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <200001172058.PAA04909@skynet.ctr.columbia.edu>; from wpaul@skynet.ctr.columbia.edu on Mon, Jan 17, 2000 at 03:58:27PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17/01 15:58, Bill Paul wrote: > No, nothing is wrong: > /dev/sndstat is created as a consequence of creating doing MAKEDEV snd0. No, you're right. I'm sorry. Pass the dunce's hat. gjvc --mode sheepish -- [gjvc] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 17: 4:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 4E45014FDB; Mon, 17 Jan 2000 17:04:31 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id MAA81476; Tue, 18 Jan 2000 12:04:29 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma081456; Tue, 18 Jan 00 12:04:10 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.2) with ESMTP id MAA16595; Tue, 18 Jan 2000 12:04:14 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Tue, 18 Jan 2000 12:04:14 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.4 -> current upgrade/bootstrap problem In-Reply-To: <20000117140440.B38119@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David, On Mon, 17 Jan 2000, David O'Brien wrote: > On Mon, Jan 17, 2000 at 12:39:12PM +1100, Carl Makin wrote: > > Here is what I did... > > 1. install gcc 2.95 port. > > 2. cd /usr/bin and rename cc and gcc to *.old and symlink cc and gcc to > > /usr/local/bin/gcc295 (Remember to delete the .old entries once you're > > finished) > This is definately the wrong thing to be doing. I don't guarentee that > the GCC 2.95 port can properly build world or kernels on 3.4. Anyway, > the upgrade should be self-hosting, and this approach isn't. Yes, I thought it wasn't ideal either but gcc 2.7.2.1 that comes with 3.4-RELEASE doesn't seem to be able to build the world OR the kernel at the moment. At least with the above steps I got the system up enough to be able to rebuild world and the kernel with the 4.0 toolset. I also had problems with "genassym". I had to build and install it before I could compile the kernel. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 17: 4:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7832D14F81 for ; Mon, 17 Jan 2000 17:04:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02848; Mon, 17 Jan 2000 17:12:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001180112.RAA02848@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Fumerola Cc: current@FreeBSD.org Subject: Re: PNPBIOS + Dell PowerEdge = panic() In-reply-to: Your message of "Sun, 16 Jan 2000 00:21:13 EST." <20000116002113.B75768@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 17:12:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem here is that the i386 nexus_alloc_resource() unconditionally calls pmap_mapdev() to map any memory-type resource into the kernel. This is definitely a bad idea; IMHO we should only do this when the resource is actually activated (and obviously free it when deactivated). Commentary? Should I just commit the change and see what happens? 8) > Hola, > > As the subject indicated PNPBIOS and Dell PowerEdge servers seem > to be a recipe for disaster. This doesn't bother me too terribly > much as I don't need PNPBIOS for anything on this machine, but I > figured the new-bus folks didn't have enough to do, so I'd help. > > This machine is a dual pIII/450 w/512MB. This is not SMP specific, BTW. > > This post exposes my DDB and newbus stupidity. If this was gdb, > I'd at least try and pull out some sort of relevent data. I have > a guess that the sheer amount/range of the ports and iomem has > something to do with it. That or the fact one starts with 0. > > Thanks and e-mail me privatly or catch me on IRC (bfumerola) if > you want me to try things with this server. > > -- > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - > > The relative part: > > unknown0: at port 0x800-0x83f,0x850-0x85f,0xe0-0xef,0x22,0x2e-0x2f,0x80,0xaa00-0xaa7f iomem 0-0x9ffff,0x100000-0x1fffdfff,0xfff80000-0xffffffff,0xf0000-0xfffff,0xec000-0xeffff irq 15 on isa0 > panic: pmap_mapdev: Couldn't alloc kernel virtual memory > mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.555 > > The full boot -v: > > -- Forwarded message from Bill Fumerola -- > > SMAP type=01 base=00000000 00000000 len=00000000 000a0000 > SMAP type=02 base=00000000 000f0000 len=00000000 00010000 > SMAP type=01 base=00000000 00100000 len=00000000 1fefe000 > SMAP type=02 base=00000000 1fffe000 len=00000000 00002000 > SMAP type=02 base=00000000 fff80000 len=00000000 00080000 > SMAP type=02 base=00000000 fec00000 len=00000000 00010000 > SMAP type=02 base=00000000 fee00000 len=00000000 00010000 > Copyright (c) 1992-2000 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: Fri Jan 14 20:51:21 GMT 2000 > jkhblows@crazyhorse.internal.chc-chimes.com:/usr/src/sys/compile/GLUEPNP > Calibrating clock(s) ... TSC clock: 447668222 Hz, i8254 clock: 1193124 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CLK_USE_TSC_CALIBRATION not specified - using old calibration method > CPU: Pentium III/Xeon (447.69-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > Features=0x383fbff > real memory = 536862720 (524280K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009efff, 647168 bytes (158 pages) > 0x00300000 - 0x1fffbfff, 533708800 bytes (130300 pages) > avail memory = 518021120 (505880K bytes) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > SMP: CPU0 apic_initialize(): > lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > bios32: Found BIOS32 Service Directory header at 0xc00ffe80 > bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0xcc0e > pnpbios: Found PnP BIOS data at 0xc00fe2d0 > pnpbios: Entry = f0000:e2f4 Rev = 1.0 > Other BIOS signatures found: > ACPI: 000fdef0 > Preloaded elf kernel "pnpbios" at 0xc02e4000. > Pentium Pro MTRR support enabled > md0: Malloc disk > Creating DISK md0 > Math emulator present > SMP: CPU0 bsp_apic_configure(): > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff > pci_open(1): mode 1 addr port (0x0cf8) is 0x80000090 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) > devclass_alloc_unit: pcib0 already exists, using next available unit number > npx0: on motherboard > npx0: INT 16 interface > pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) > pcib0: on motherboard > found-> vendor=0x8086, dev=0x71a0, revid=0x00 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base f0000000, size 26 > found-> vendor=0x8086, dev=0x71a1, revid=0x00 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=1 secondarybus=1 > found-> vendor=0x1011, dev=0x0024, revid=0x03 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=3 secondarybus=2 > found-> vendor=0x8086, dev=0x7110, revid=0x02 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > found-> vendor=0x8086, dev=0x7111, revid=0x01 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > found-> vendor=0x8086, dev=0x7112, revid=0x01 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=0 > found-> vendor=0x8086, dev=0x7113, revid=0x02 > class=06-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[90]: type 1, range 32, base 00000850, size 4 > Freeing (NOT implemented) redirected PCI irq 14. > found-> vendor=0x10b8, dev=0x0005, revid=0x08 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=20 > map[10]: type 1, range 32, base 0000dc00, size 8 > map[14]: type 1, range 32, base fe000000, size 12 > pci0: on pcib0 > pcib2: at device 1.0 on pci0 > found-> vendor=0x1002, dev=0x4744, revid=0x5c > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base fc000000, size 24 > map[14]: type 1, range 32, base 0000fc00, size 8 > map[18]: type 1, range 32, base fbfff000, size 12 > pci1: on pcib2 > vga-pci0: port 0xfc00-0xfcff mem 0xfbfff000-0xfbffffff,0xfc000000-0xfcffffff at device 0.0 on pci1 > pcib3: at device 2.0 on pci0 > Freeing (NOT implemented) redirected PCI irq 11. > found-> vendor=0x9005, dev=0x001f, revid=0x00 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=16 > map[10]: type 1, range 32, base 0000ec00, size 8 > map[14]: type 1, range 64, base f9fff000, size 12 > found-> vendor=0x8086, dev=0x0960, revid=0x03 > class=06-04-00, hdrtype=0x01, mfdev=1 > subordinatebus=3 secondarybus=3 > Freeing (NOT implemented) redirected PCI irq 10. > found-> vendor=0x8086, dev=0x1960, revid=0x03 > class=0e-00-01, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > intpin=a, irq=18 > map[10]: type 1, range 32, base f6c00000, size 22 > pci2: on pcib3 > ahc0: port 0xec00-0xecff mem 0xf9fff000-0xf9ffffff irq 16 at device 4.0 on pci2 > ahc0: Reading SEEPROM...done. > ahc0: Manual LVD Termination > ahc0: BIOS eeprom is present > ahc0: Secondary High byte termination Enabled > ahc0: Secondary Low byte termination Enabled > ahc0: Primary Low Byte termination Enabled > ahc0: Primary High Byte termination Enabled > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc0: Downloading Sequencer Program... 399 instructions downloaded > pcib4: at device 10.0 on pci2 > pci3: on pcib4 > amr0: mem 0xf6c00000-0xf6ffffff irq 18 at device 10.1 on pci2 > amr0: firmware 3.00 bios 1.36 16MB memory > amrd0: on amr0 > amrd0: 17136MB (35094528 sectors) RAID 5 (optimal) > Creating DISK amrd0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > pci0: Intel PIIX4 ATA controller (vendor=0x8086, dev=0x7111) at 7.1 > pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 0 > Timecounter "PIIX" frequency 3579545 Hz > chip1: port 0x850-0x85f at device 7.3 on pci0 > tx0: port 0xdc00-0xdcff mem 0xfe000000-0xfe000fff irq 20 at device 8.0 on pci0 > tx0: address 00:e0:29:36:21:2d, type SMC9432TX, Auto-Neg 100Mbps bpf: tx0 attached > > pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) > devclass_alloc_unit: pci1 already exists, using next available unit number > pcib1: on motherboard > pci4: on pcib1 > pnpbios: 16 devices, largest 179 bytes > PNP0c02: adding memory range 0-0x9ffff, size=0xa0000 > PNP0c02: adding memory range 0x100000-0x1fffdfff, size=0x1fefe000 > PNP0c02: adding memory range 0xfff80000-0xffffffff, size=0x80000 > PNP0c02: adding memory range 0xf0000-0xfffff, size=0x10000 > PNP0c02: adding memory range 0xec000-0xeffff, size=0x4000 > PNP0c02: adding io range 0x800-0x83f, size=0x40, align=0x1 > PNP0c02: adding io range 0x850-0x85f, size=0x10, align=0x1 > PNP0c02: adding io range 0xe0-0xef, size=0x10, align=0x1 > PNP0c02: adding io range 0x22-0x22, size=0x1, align=0x1 > PNP0c02: adding io range 0x2e-0x2f, size=0x2, align=0x1 > PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 > PNP0c02: adding io range 0xaa00-0xaa7f, size=0x80, align=0x1 > PNP0c02: adding irq mask 0x8000 > PNP0c02: start dependant > pnpbios: handle 0 device ID PNP0c02 (020cd041) > PNP0501: adding irq mask 0x10 > PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 > PNP0501: start dependant > pnpbios: handle 2 device ID PNP0501 (0105d041) > PNP0501: adding irq mask 00x8 > PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 > PNP0501: start dependant > pnpbios: handle 3 device ID PNP0501 (0105d041) > PNP0401: adding dma mask 0x2 > PNP0401: adding irq mask 0x80 > PNP0401: adding io range 0x378-0x37f, size=0x8, align=0x8 > PNP0401: adding io range 0x778-0x77b, size=0x4, align=0x8 > PNP0401: start dependant > pnpbios: handle 4 device ID PNP0401 (0104d041) > PNP0700: adding irq mask 0x40 > PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 > PNP0700: adding dma mask 0x4 > PNP0700: start dependant > pnpbios: handle 5 device ID PNP0700 (0007d041) > PNP0f13: adding irq mask 0x1000 > PNP0f13: start dependant > pnpbios: handle 6 device ID PNP0f13 (130fd041) > PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 > PNP0a03: start dependant > pnpbios: handle 7 device ID PNP0a03 (030ad041) > PNP0c02: adding irq mask 0x200 > PNP0c02: start dependant > pnpbios: handle 8 device ID PNP0c02 (020cd041) > PNP0000: adding irq mask 00x4 > PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 > PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 > PNP0000: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 > PNP0000: start dependant > pnpbios: handle 9 device ID PNP0000 (0000d041) > PNP0003: adding memory range 0xfee00000-0xfee0ffff, size=0x10000 > PNP0003: adding memory range 0xfec00000-0xfec0ffff, size=0x10000 > PNP0003: start dependant > pnpbios: handle 10 device ID PNP0003 (0300d041) > PNP0100: adding irq mask 00x1 > PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 > PNP0100: start dependant > pnpbios: handle 11 device ID PNP0100 (0001d041) > PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 > PNP0200: adding io range 0-0xf, size=0x10, align=0x1 > PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 > PNP0200: adding dma mask 0x10 > PNP0200: start dependant > pnpbios: handle 12 device ID PNP0200 (0002d041) > PNP0303: adding irq mask 00x2 > PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 > PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 > PNP0303: start dependant > pnpbios: handle 13 device ID PNP0303 (0303d041) > PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 > PNP0800: start dependant > pnpbios: handle 14 device ID PNP0800 (0008d041) > PNP0b00: adding irq mask 0x100 > PNP0b00: adding io range 0x70-0x73, size=0x4, align=0x1 > PNP0b00: start dependant > pnpbios: handle 15 device ID PNP0b00 (000bd041) > PNP0c04: adding irq mask 0x2000 > PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 > PNP0c04: start dependant > pnpbios: handle 16 device ID PNP0c04 (040cd041) > Trying Read_Port at 203 > Trying Read_Port at 243 > Trying Read_Port at 283 > Trying Read_Port at 2c3 > Trying Read_Port at 303 > Trying Read_Port at 343 > Trying Read_Port at 383 > Trying Read_Port at 3c3 > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0065 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 > psm0: current command byte:0065 > kbdc: TEST_AUX_PORT status:0000 > kbdc: RESET_AUX return code:00fe > kbdc: RESET_AUX return code:00fe > kbdc: RESET_AUX return code:00fe > kbdc: DIAGNOSE status:0055 > kbdc: TEST_KBD_PORT status:0000 > psm0: failed to reset the aux device. > vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 > fb0: vga0, vga, type:VGA (5), flags:0x7007f > fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 > fb0: init mode:24, bios mode:3, current mode:24 > fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k > VGA parameters upon power-up > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > VGA parameters in BIOS for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x0> > sc0: fb0 kbd0 > sio0: irq maps: 0x41 0x51 0x41 0x41 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A, console > sio1: irq maps: 0x41 0x49 0x41 0x41 > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: parallel port found at 0x378 > ppc0: ECP SPP ECP+EPP SPP > ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > isa_probe_children: probing PnP devices > unknown0: at port 0x800-0x83f,0x850-0x85f,0xe0-0xef,0x22,0x2e-0x2f,0x80,0xaa00-0xaa7f iomem 0-0x9ffff,0x100000-0x1fffdfff,0xfff80000-0xffffffff,0xf0000-0xfffff,0xec000-0xeffff irq 15 on isa0 > panic: pmap_mapdev: Couldn't alloc kernel virtual memory > mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.555 > db> trace > Debugger(c0242cd2) at Debugger+0x35 > panic(c0258d00,0,c148d540,3,c0296360) at panic+0xa4 > pmap_mapdev(100000,1fefdfff,2,1fefe000,1fffdfff) at pmap_mapdev+0x46 > nexus_alloc_resource(c147b200,c1483b80,3,c02f8cdc,100000) at nexus_alloc_resource+0xa8 > BUS_ALLOC_RESOURCE(c147b200,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 > bus_generic_alloc_resource(c147b180,c1483b80,3,c02f8cdc,100000) at bus_generic_alloc_resource+0x2d > BUS_ALLOC_RESOURCE(c147b180,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 > resource_list_alloc(c147c5c4,c147b000,c1483b80,3,c02f8cdc) at resource_list_alloc+0x69 > pci_alloc_resource(c147b000,c1483b80,3,c02f8cdc,100000) at pci_alloc_resource+0x38 > BUS_ALLOC_RESOURCE(c147b000,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 > bus_generic_alloc_resource(c147dc00,c1483b80,3,c02f8cdc,100000) at bus_generic_alloc_resource+0x2d > BUS_ALLOC_RESOURCE(c147dc00,c1483b80,3,c02f8cdc,100000) at BUS_ALLOC_RESOURCE+0x43 > resource_list_alloc(c147c5c0,c1483f80,c1483b80,3,c02f8cdc,100000,ffffffff,1,2) at resource_list_alloc+0xf1 > isa_probe_children(c1483f80) at isa_probe_children+0x186 > configure(0,2f6c00,300000,0,c011c4d6) at configure+0x41 > mi_startup(c02f8fb4,0,0,a04,0) at mi_startup+0x70 > begin() at begin+0x4b > db> panic > panic: from debugger > mp_lock = 00000003; cpuid = 0; lapic.id = 01000000 > Uptime: 0s > amr0: flushing cache... > > ----- End forwarded message ----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 17: 5:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 2DED114F92; Mon, 17 Jan 2000 17:05:57 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A999D1C41; Mon, 17 Jan 2000 20:05:56 -0500 (EST) Date: Mon, 17 Jan 2000 20:05:56 -0500 From: Bill Fumerola To: Mike Smith Cc: current@FreeBSD.org Subject: Re: PNPBIOS + Dell PowerEdge = panic() Message-ID: <20000117200556.L8895@jade.chc-chimes.com> References: <20000116002113.B75768@jade.chc-chimes.com> <200001180112.RAA02848@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001180112.RAA02848@mass.cdrom.com>; from msmith@freebsd.org on Mon, Jan 17, 2000 at 05:12:14PM -0800 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 05:12:14PM -0800, Mike Smith wrote: > The problem here is that the i386 nexus_alloc_resource() unconditionally > calls pmap_mapdev() to map any memory-type resource into the kernel. > This is definitely a bad idea; IMHO we should only do this when the > resource is actually activated (and obviously free it when deactivated). > > Commentary? Should I just commit the change and see what happens? 8) Naturally, I know nothing of the implications, but I'd certainly test patches since I can reproduce this with the greatest of ease. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 17:35:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BDB9F15072 for ; Mon, 17 Jan 2000 17:35:44 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id RAA23533 for current@freebsd.org; Mon, 17 Jan 2000 17:58:47 -0800 (PST) Date: Mon, 17 Jan 2000 17:58:47 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: er... missing the point? Message-ID: <20000117175847.G16038@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think a code/feature freeze is supposed to be implemented by breaking world so others can't test things. cc -pipe -O2 -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/home/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/home/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/home/src/i386/usr/include -c /home/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo/toc.c cc -pipe -O2 -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/home/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/home/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/home/src/i386/usr/include -o makeinfo cmds.o defun.o files.o footnote.o html.o index.o insertion.o lang.o macro.o makeinfo.o multi.o node.o sectioning.o toc.o /usr/obj/home/src/i386/home/src/gnu/usr.bin/texinfo/makeinfo/../libtxi/libtxi.a /usr/obj/home/src/i386/usr/libexec/elf/ld: cannot open crt1.o: No such file or directory *** Error code 1 1 error :P thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 17:58:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (liv3-3.hamilton.idirect.com [209.161.208.3]) by hub.freebsd.org (Postfix) with ESMTP id 9A1051524C; Mon, 17 Jan 2000 17:58:18 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id VAA01013; Mon, 17 Jan 2000 21:04:27 -0500 (EST) Date: Mon, 17 Jan 2000 21:04:27 -0500 From: Dan Moschuk To: Mike Smith Cc: Bill Fumerola , current@FreeBSD.ORG Subject: Re: PNPBIOS + Dell PowerEdge = panic() Message-ID: <20000117210427.A546@spirit.jaded.net> References: <20000116002113.B75768@jade.chc-chimes.com> <200001180112.RAA02848@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001180112.RAA02848@mass.cdrom.com>; from msmith@FreeBSD.ORG on Mon, Jan 17, 2000 at 05:12:14PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | The problem here is that the i386 nexus_alloc_resource() unconditionally | calls pmap_mapdev() to map any memory-type resource into the kernel. | This is definitely a bad idea; IMHO we should only do this when the | resource is actually activated (and obviously free it when deactivated). | | Commentary? Should I just commit the change and see what happens? 8) Commit and see what happens. I'll keep the pointy had warm for you. 8) -- Dan Moschuk (TFreak!dan@freebsd.org) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 18: 6:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 6C545150BF for ; Mon, 17 Jan 2000 18:06:25 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 8507 invoked by uid 1010); 18 Jan 2000 02:06:34 -0000 Date: Tue, 18 Jan 2000 02:06:34 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: Compiling XFree86 3.9.17 Message-ID: <20000118020634.A8092@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="BOKacYhQ+x31HxR3" User-Agent: Mutt/1.1.1i X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii I've been reworking the FreeBSD configuration file for XFree86 3.9.17. At the moment, I've only done Intel. (Don't despair Alpha folks -- I'll get myself a Compaq testdrive account :-)) This file is a drop-in replacement for 'xc/config/cf/FreeBSD.cf' You don't need any 'xc/config/cf/host.def' file. Just cp and make World [1] It works on both 4.0-CURRENT and 3.4-STABLE. [2] If you could give it a go, and correct me on any incorrect definitions/switches/whatever I'd be very grateful. Sadly, there's a couple of gotchas. First, it won't actually compile _everything_ using the base compiler (gcc 2.95.2). This is due to a bug in this version of gcc. To fix this, remove the -O2 option in the Makefile of the affected module. Secondly, XF86Setup is broken in this version of XFree86. No XF86Setup will be built by this config file. More news on that as it happens. best; gjvc -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth [1] The XFree86 world, that is, obviously. [2] If anyone has a 2.2.8 machine, and can do a test build, please do! :-) --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="FreeBSD-gjvc.cf" XCOMM platform: $TOG: FreeBSD.cf /main/21 1997/10/05 20:42:34 kaleb $ XCOMM platform: $XFree86: xc/config/cf/FreeBSD.cf,v 3.85 1999/05/22 08:39:55 dawes Exp $ XCOMM gjvc: $Id: FreeBSD-gjvc.cf,v 1.8 2000/01/18 01:37:35 gjvc Exp $ /* ---- [ WHAT THIS IS ] -------------------------------------------------- This file is intended to replace the xc/config/cf/FreeBSD.cf file in the XFree86 3.9.17 distribution. You don't need a host.def file or need to make any changes to the stock XFree86 3.9.17 tarballs [but see below] This will let you build XFree86 on 3.4-STABLE and 4.0-CURRENT. I don't know if it works on earlier FreeBSD 3.x versions. To use this file, copy it right over the current 'config/cf/FreeBSD.cf' file and type 'make World' in the 'xc' directory. cp xc/config/cf/FreeBSD.cf xc/config/cf/FreeBSD.cf.original cp FreeBSD-gjvc.cf xc/config/cf/FreeBSD.cf cd xc && make World I've also futzed around with #defines, C library features and goodness knows what else, so if you have any opinions on what follows I'd be grateful. ---- [ KNOWN PROBLEMS ] ----------------------------------------------- 3.4-STABLE : No reported problems yet -- be first! :-) 4.0-CURRENT : Using the system compiler (2.95.2), compilation of the files xc/programs/Xserver/Xext/xf86vmode.c xc/programs/Xserver/Xext/extmod/xf86vmode.c will fail with a 'Unable to generate reloads' error. This is a bug in gcc, and has been fixed in the latest gcc snapshot. Either disable all optimisation for the compilation of just that file, or use a later version of the compiler. (Hint: do a make World, and then a make all -- the compilation will stop here and you can remove the '-O2' flag in the Makefile.) XFree86 3.9.17 : the directory xc/doc/ is strangely missing an Imakefile, and consquently the build fails on it. I got my documents by using the documents directory of XFree86 3.9.16. XF86Setup is currently broken in 3.9.17 so no attemp is made to build it. Anyway, please give it a go, and let me know how you get on. All feedback is appreciated. :-) ---- [ GIVING FEEDBACK ] --------------------------------------------- Please include the output of 'uname -a', and 'gcc --version' when reporting problems. best; George Cox */ /* OPERATING SYSTEM IDENTIFICATION */ #ifndef OSName #define OSName DefaultOSName #endif #ifndef OSMajorVersion #define OSMajorVersion DefaultOSMajorVersion #endif #ifndef OSMinorVersion #define OSMinorVersion DefaultOSMinorVersion #endif #ifndef OSTeenyVersion #define OSTeenyVersion DefaultOSTeenyVersion #endif #ifndef OSVendor #define OSVendor The FreeBSD Project #endif /* BINARY FORMAT */ #define UseElfFormat YES #define OSBinaryFormat ELF #define BuildAoutLibraries YES /* COMPILER */ #define GccUsesGas YES #define GnuCpp YES #define HasBsdMake YES #define HasCplusplus YES #define HasGcc YES #define HasGcc2 YES #define HasGcc2ForCplusplus YES #define HasGnuMake NO #define UseGas YES /* COMPILER COMMANDS */ #define CcCmd gcc #define CppCmd /usr/bin/cpp #define DefaultCCOptions -O2 -pipe -ansi -pedantic -Dasm=__asm GccWarningOptions #define InstallCmd /usr/bin/install #define MkdirHierCmd mkdir -p #define PreProcessCmd /usr/bin/cpp #define RawCppCmd /usr/bin/cpp #define StandardCppDefines /**/ #define StandardCppOptions /**/ /* DEFINES -- ASSEMBLER */ #define AsmElfDefines -D__ELF__ #define AsmDefines -DUSE_GAS AsmElfDefines #define GccGasOption -DGCCUSESGAS #define DefaultGcc2i386Opt /**/ #define OptimizedCDebugFlags DefaultGcc2i386Opt /* C LANGUAGE CONVENTIONS */ #define NeedConstPrototypes YES #define NeedFunctionPrototypes YES #define NeedNestedPrototypes YES #define NeedVarargsPrototypes YES #define NeedWidePrototypes NO /* C LIBRARY FEATURES */ #define HasBSD44Sockets YES #define HasBsearch YES #define HasDlopen YES #define HasMTRRSupport YES #define HasMkstemp YES #define HasNdbm YES #define HasPoll NO /* _poll is not in the a.out libc -- how silly! */ #define HasPutenv YES #define HasSetUserContext YES #define HasShm YES #define HasSnprintf YES #define HasSockets YES #define HasStrcasecmp YES #define HasStreams NO #define HasUsableFileMmap YES #define HasVFork YES #define HasVoidSignalReturn YES #define Malloc0ReturnsNull NO #define SetTtyGroup YES #define HasWChar32 YES /* SYSTEM LIBRARIES */ #define ExtraLibraries -lxpg4 #define GnuMallocLibrary -lgnumalloc #define HasSharedLibraries YES #define HasLibCrypt YES #define HasZlib YES #define HasNCurses YES #define DlLibrary -rdynamic /* no -ldl */ #define NCursesLibName -lcurses #define UseGnuMalloc NO #define StaticLibrary(libpath,libname) -Wl,-Bstatic Concat(-L,libpath) Concat(-l,libname) -Wl,-Bdynamic /* MISCELLANEOUS DEFINES */ #define ExtraFilesToClean *.core #define UseRgbTxt YES #define DoLoadableServer YES #define AvoidNullMakeCommand YES #define CompressAllFonts YES #define ForceNormalLib YES #define StripInstalledPrograms YES /* DEFINES -- X */ #define StandardDefines -DCSRG_BASED -D_BSD_SOURCE -D_XOPEN_SOURCE #define ServerOSDefines XFree86ServerOSDefines -DDDXTIME #define ServerExtraDefines GccGasOption XFree86ServerDefines #define XawI18nDefines -DUSE_XWCHAR_STRING -DUSE_XMBTOWC /* PATHS */ #define DefaultUserPath /bin:/usr/bin:/sbin:/usr/sbin:$(BINDIR) #define DefaultSystemPath /bin:/usr/bin:/sbin:/usr/sbin:$(BINDIR) #define SystemManDirectory /usr/share/man #define PreIncDir DefaultGccIncludeDir /* DOCUMENT TYPESETTING TOOLS */ #define EqnCmd eqn -Tps #define NeqnCmd neqn -Tlatin1 #define NroffCmd groff -Tlatin1 #define TroffCmd groff -Tps /* XFREE86 BUILD SYSTEM INCLUDE FILES */ #include #include /* Good luck, Commander */ /* ...TRANSMISSION ENDS... */ --BOKacYhQ+x31HxR3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 18: 7:38 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id E1AD4150AD; Mon, 17 Jan 2000 18:07:36 -0800 (PST) From: "Jonathan M. Bresler" To: leif@neland.dk Cc: freebsd-current@FreeBSD.ORG In-reply-to: <01da01bf6145$e0fa4900$0e00a8c0@neland.dk> (leifn@neland.dk) Subject: Re: ppp, incoming mail keeping the line up. Message-Id: <20000118020736.E1AD4150AD@hub.freebsd.org> Date: Mon, 17 Jan 2000 18:07:36 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I run user-ppp, and I have a mx-record for my system, so incoming mail = > goes directly to my system. this is asking for trouble. you should get yourself an MX that is online all the time and will store your mail for you. you can then pick it up whenever you want using APOP or POP thru SSH....i peronsally use APOP thru SSH via fetchmail ;) jmb > > Now I'm afraid if I'm on a a mailing list with a frequency of mail = > faster than my timeout period, I could be online a very long time. > > If I filter incoming smtp wuth the alive-filter, I guess I'd be shutting = > the line down in the middle of recieving mail. > > Or is it possible to specify a shorter alive-time for mail only?=20 > > Sort of "any traffic will keep the line up for 10 seconds, traffic = > allowed by afilter will keep the line for 2 minutes". > > Leif > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 18: 7:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.37]) by hub.freebsd.org (Postfix) with ESMTP id D0B381513D for ; Mon, 17 Jan 2000 18:07:40 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by mx3.mail.ru with esmtp (Exim 3.02 #114) id 12AO2z-000MuJ-00; Tue, 18 Jan 2000 05:07:06 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id VAA00845; Mon, 17 Jan 2000 21:07:28 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000117115648.C53965@relay.nuxi.com> Date: Mon, 17 Jan 2000 21:07:28 -0500 (EST) From: "Alexander N. Kabaev" To: "David O'Brien" Subject: Re: C++ exceptions doesn't work in shared libraries Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why doesn't OpenBSD, Linux, or Solaris x86 need this patch? I tried to compile and run attached program on dual-processor Compaq Proliant server running RedHat Linux 6.1 at Compaq testdrive site (thanks, Compaq!) and guess what? Compiled with -fsjlj-exceptions Linux bails out with "Not enough memory" error message. Compiled without -fsjlj-exceptions, it dumps core. It _could_ use some patches after all :) I would really appreciate if people having access to the OpenBSD/i386 Solaris/x86 boxes will try the following program on these boxes and share results with us. I will be greatly surprised if OpenBSD will survive the test since their egcs looks like stock egcs 1.1.2 version which has not been heavily patched from original Cygnus version. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 17-Jan-00 Time: 20:30:14 ---------------------------------- # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # Makefile # foo.cc # main.cc # echo x - Makefile sed 's/^X//' >Makefile << 'END-of-Makefile' XCXX=g++ XLD=ld XCXXFLAGS=-g -fpic -fexceptions X Xall: arf X Xarf: main.o foo.so X ${CXX} -o arf main.o foo.so X X Xfoo.so: foo.o X ${LD} -Bshareable -o foo.so foo.o X Xclean: X rm -f arf *.o *.so END-of-Makefile echo x - foo.cc sed 's/^X//' >foo.cc << 'END-of-foo.cc' X#include X Xint Foo (); X Xint Baz () X{ X char *msg = "Bax thowing..."; X printf ("in baz\n"); X throw msg; X printf ("baz should not be here.\n"); X} X X Xint Foo () X{ X try { X Baz (); X } catch (char *msg) { X printf ("foo caught %s\n", msg); X } X} END-of-foo.cc echo x - main.cc sed 's/^X//' >main.cc << 'END-of-main.cc' X#include X Xint Foo (); X Xint Xmain () X{ X try { X printf ("calling foo\n"); X Foo (); X printf ("returned from foo\n"); X } catch (char *msg) { X printf ("exception from foo: %s\n", msg); X } catch (...) { X printf ("unknown exception\n"); X } X} END-of-main.cc exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 17 18:11:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from BSDpc.geek4food.org (adsl-216-103-105-71.dsl.snfc21.pacbell.net [216.103.105.71]) by hub.freebsd.org (Postfix) with ESMTP id 9691415043; Mon, 17 Jan 2000 18:11:10 -0800 (PST) (envelope-from andy@geek4food.org) Received: from mega.geek4food.org (mega.geek4food.org [192.168.1.57]) by BSDpc.geek4food.org (Postfix) with ESMTP id AA2DF11B85; Mon, 17 Jan 2000 18:11:09 -0800 (PST) Received: from mega.geek4food.org (localhost.geek4food.org [127.0.0.1]) by mega.geek4food.org (8.9.3/8.9.3) with ESMTP id SAA13312; Mon, 17 Jan 2000 18:11:09 -0800 (PST) (envelope-from andy@geek4food.org) Message-Id: <200001180211.SAA13312@mega.geek4food.org> To: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Integrated Vibra16 in -current Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 17 Jan 2000 18:11:09 -0800 From: Andy Sparrow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I recently cvsup'd -CURRENT both so that I could run StarOffice 5.1 (it's an SMP box), and to check it out (as it will soon be a Release, and I see a lot of good stuff going on there, like the SMP locking, NFS fixes etc.). I've got a Micron W6-Li Lightning board with integrated Creative Vibra16X and Adaptec 7880, and I run a WinTV card as well. I also have the ISA Waveblaster daughter card that makes the sound setup effectively an AWE32. After upgrading, I discovered that I couldn't get the sound chip on the motherboard to get probed correctly. Given the Plug'n'Pray changes in -current, I pretty much expected to lose AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to probe the "magic" ports for the AWE32). However, I wasn't expecting to lose the ability to use VoxWare altogether. Without PNPBIOS, I got these messages (config file was the same one as used under -STABLE, just converted by the simple expedient of fixing the complaints from 'config', mostly changing 'controller' to 'device' etc.): sb_reset_dsp failed sb_reset_dsp failed awe0 at port 0x620 on isa0 AWE32: not detected unknown0: at port 0x621-0x624 on isa0 unknown1:
 
------=_NextPart_000_0042_01BF61D6.2800CD20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 6:21:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id A99D514E0B; Tue, 18 Jan 2000 06:21:33 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id BAA06329; Wed, 19 Jan 2000 01:20:42 +1100 Date: Wed, 19 Jan 2000 01:20:38 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Ruslan Ermilov Cc: Sheldon Hearn , marcel@FreeBSD.ORG, Munehiro Matsuda , freebsd-current@FreeBSD.ORG Subject: Re: Is texinfo needed for buildworld with -DNOINFO ? In-Reply-To: <20000118152012.A15591@relay.ucb.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Ruslan Ermilov wrote: > On Tue, Jan 18, 2000 at 11:47:27PM +1100, Bruce Evans wrote: > > On Tue, 18 Jan 2000, Ruslan Ermilov wrote: > > > How's that not a problem? The current Makefile.inc1 is written so, > that bootstrap-tools are built with: > > BMAKE=${BMAKEENV} ${MAKE} -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML > ^^^^^^^^ > So, how inside the Makefile.inc1's bootstrap-tools: target I could know > whether the user requested NOINFO, or Makefile.inc1 itself? Oops. Makefile.inc1 always recurses to builds tools targets with -DNOINFO, and the tools targets are (should be) internal, so the patch is just an obfuscated way of removing texinfo from the list. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 6:23:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id BACBC14D33 for ; Tue, 18 Jan 2000 06:23:39 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 12656 invoked by uid 1010); 18 Jan 2000 12:12:10 -0000 Date: Tue, 18 Jan 2000 12:12:10 +0000 From: George Cox To: Pascal Hofstee Cc: Nick Hibma , FreeBSD CURRENT Mailing List Subject: Re: mergemaster and new files Message-ID: <20000118121210.B50992@extremis.demon.co.uk> References: <20000118120528.B82699@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000118120528.B82699@shadowmere.student.utwente.nl>; from daeron@shadowmere.student.utwente.nl on Tue, Jan 18, 2000 at 12:05:28PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18/01 12:05, Pascal Hofstee wrote: > Yes .. i have noticed several occasions of mergemaster pointing out to me > that a file from /usr/src/etc didn't exist in my own /etc tree yet. And if you do a mergemaster -v it will tell you what exists in /etc, but not in /usr/src/etc. Very handy. :-) best; gjvc -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 7:21: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 289D914ED9 for ; Tue, 18 Jan 2000 07:20:58 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id KAA66939; Tue, 18 Jan 2000 10:20:43 -0500 (EST) Date: Tue, 18 Jan 2000 10:20:43 -0500 (EST) From: "Matthew N. Dodd" To: Frank Mayhar Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) In-Reply-To: <200001181048.CAA07011@realtime.exit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Frank Mayhar wrote: > Interestingly, I rebuilt world with the latest pccardd changes and, > suddenly, the 589D started working perfectly. Unfortunately, the > 574BT doesn't work at all now. It appears to configure properly, but > it doesn't transmit or receive. Ok, I need the output of 'dmesg', 'ifconfig -a', your kernel config, and 'ident /sys/dev/ep/*'. I suspect you'll find that the 574BT may be in the 'OACTIVE' state as indicated in the flags section of ifconfig. Please try tcpdumping on ep0 and on another box (using the MAC address of the 574) and seeing if any traffic is visable. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 7:33:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2B52214F6F for ; Tue, 18 Jan 2000 07:33:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA67552; Tue, 18 Jan 2000 07:33:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA31947; Tue, 18 Jan 2000 07:33:49 -0800 (PST) (envelope-from obrien) Date: Tue, 18 Jan 2000 07:33:49 -0800 From: "David O'Brien" To: Munehiro Matsuda Cc: freebsd-current@freebsd.org Subject: Re: Is texinfo needed for buildworld with -DNOINFO ? Message-ID: <20000118073349.A31929@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000118191419G.haro@tk.kubota.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000118191419G.haro@tk.kubota.co.jp>; from haro@tk.kubota.co.jp on Tue, Jan 18, 2000 at 07:14:19PM +0900 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that texinfo is compiled as cross-tools for buildworld. > But, is it really needed when -DNOINFO has been specified? You stole my plan! :-) Once the dust settles and the current crop of `make world' problems are fixed, I want to commit a simular patch as I don't care for info files and don't want to waste time building them. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 8: 4:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 0FB2A14CA4 for ; Tue, 18 Jan 2000 08:03:53 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id SAA61307; Tue, 18 Jan 2000 18:04:44 +0200 (EET) (envelope-from ru) Date: Tue, 18 Jan 2000 18:04:44 +0200 From: Ruslan Ermilov To: Ben Rosengart Cc: current@FreeBSD.org Subject: Re: HEADS UP: grep 2.4a is now in the tree Message-ID: <20000118180444.A58470@relay.ucb.crimea.ua> Mail-Followup-To: Ben Rosengart , current@FreeBSD.org References: <20000118120001.A60039@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Ben Rosengart on Tue, Jan 18, 2000 at 11:00:43AM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 18, 2000 at 11:00:43AM -0500, Ben Rosengart wrote: > On Tue, 18 Jan 2000, Ruslan Ermilov wrote: > > > --binary-files='text' treats binary files as text > > (equivalent to -a or --text). > > So "-a" now does the opposite of what it used to do? > Not exactly. A stock grep 2.0 did not distinguish between binary and text files. So we (FreeBSD) added -a option, which caused grep to skip binary files. A stock grep 2.3 intoduced a stock -a option. By default, grep 2.3 prints a one-line message "Binary file FOO matches" (if it really matches). Grep 2.4 introduces a --binary-files option, which could be used to either 1) print a one-line message, if files matches; 2) treat the binary files as text files; 3) skip binary files. The equivalent to the old -a option is --binary-files=without-match. If you want this by default, you can hardcode it in GREP_OPTIONS environment variable. For a full story, see src/gnu/usr.bin/grep/NEWS. Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 8:20:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id DB30A14D1B; Tue, 18 Jan 2000 08:20:20 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA25082; Tue, 18 Jan 2000 11:20:19 -0500 (EST) (envelope-from wollman) Date: Tue, 18 Jan 2000 11:20:19 -0500 (EST) From: Garrett Wollman Message-Id: <200001181620.LAA25082@khavrinen.lcs.mit.edu> To: Mike Smith Cc: Bill Fumerola , current@FreeBSD.ORG Subject: Re: PNPBIOS + Dell PowerEdge = panic() In-Reply-To: <200001180112.RAA02848@mass.cdrom.com> References: <20000116002113.B75768@jade.chc-chimes.com> <200001180112.RAA02848@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > This is definitely a bad idea; IMHO we should only do this when the > resource is actually activated (and obviously free it when deactivated). Absolutely! As I keep trying to explain to people, that's why there *is* a separate activate function (or one of the reasons, anyway). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9: 0: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id B4DC014BEF for ; Tue, 18 Jan 2000 09:00:00 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 78189 invoked from network); 18 Jan 2000 16:59:54 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 18 Jan 2000 16:59:54 -0000 Message-ID: <01fa01bf61d5$7162c550$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Sheldon Hearn" , References: <11376.948200498@axl.noc.iafrica.com> Subject: Re: Mandating USA_RESIDENT Date: Tue, 18 Jan 2000 10:26:12 -0500 Organization: MindStep Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, If we are changing the meaning of "USA_RESIDENT", could we replace it by something else completely. I know that the USA are the center of the universe ;-), but... It seems to me that a things progress, the crypto regulation gets more complicated everyday. Why not have a "CRYPTO_COUNTRY" variable that could be set to "USA" "FRANCE" "CANADA" or "other" based where you live and weither special consideration must be taken relative to the crypto code ? Then as part of the build process, automatically create specific variables for RSA or other stuff as they show up: CRYPTO_RSA="RSAref" or CRYPTO_RSA="rsa" or CRYPTO_RSA="none". This can be done by a little bit of shell script easily. The other thing that could be set based on the CRYPTO_COUNTRY code is where to get the FreeBSD crypto related source from. Finally, the current "USA_RESIDENT" variable can then be generated automatically and with good confidence that it is set to a correct value (for the ports or source that still relies on that). OK, it may be overkill for what we need now. So if it looks too much like a bad idea, kill it now. Patrick. ----- Original Message ----- From: Sheldon Hearn Newsgroups: list.freebsd.current Sent: Tuesday, January 18, 2000 8:02 AM Subject: Re: Mandating USA_RESIDENT > > > On 18 Jan 2000 03:03:09 PST, Satoshi - Ports Wraith - Asami wrote: > > > Maybe it's better to make it an error to not specify it (yes, killing > > "make world" and stuff, that's what UPDATING is for). > > There's no better time for doing so than prior to 4.0-RELEASE. :-) > > Does sysinstall set this one? If not, it should. Then we can stop > worrying about it. :-) > > Ciao, > Sheldon. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9: 9:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 278D014BEF for ; Tue, 18 Jan 2000 09:09:40 -0800 (PST) (envelope-from jrs@enteract.com) Received: from shell-2.enteract.com (jrs@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id LAA40945 for ; Tue, 18 Jan 2000 11:09:36 -0600 (CST) (envelope-from jrs@enteract.com) Date: Tue, 18 Jan 2000 11:09:36 -0600 (CST) From: John Sconiers To: freebsd-current@freebsd.org Subject: make world fail Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi is any oone else having trouble doing a make world? Completed reomved /usr/obj and usr/src/ cvs'd twice and got the following error: (trimmed) /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:96: print "FIX(numcodes)" > "codeftr" awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:96: ^ unexpected newline awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:97: print "FIX(strcodes)" > "codeftr" awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:97: ^ unexpected newline awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:98: print "#endif /* BROKEN_LINKER */" > "codeftr" awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:98: ^ unexpected newline *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. JRS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9:22:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3E43914DAA; Tue, 18 Jan 2000 09:22:48 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA25221; Tue, 18 Jan 2000 12:22:46 -0500 (EST) (envelope-from wollman) Date: Tue, 18 Jan 2000 12:22:46 -0500 (EST) From: Garrett Wollman Message-Id: <200001181722.MAA25221@khavrinen.lcs.mit.edu> To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: Kris Kennaway , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < Won't people get into legal trouble (technically) if they build the > wrong version? Depends on who they work for. Some people may work for organizations which have licensing agreements in place to permit them to use RSA. (This includes about 10,000 people who happen to work for the patent assignee.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9:27: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 0EB4C14E4C for ; Tue, 18 Jan 2000 09:27:03 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id LAA03496 for freebsd-current@freebsd.org; Tue, 18 Jan 2000 11:27:00 -0600 (CST) From: Mohit Aron Message-Id: <200001181727.LAA03496@cs.rice.edu> Subject: RELNOTES.TXT To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2000 11:27:00 -0600 (CST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I checked the file RELNOTES.TXT for the latest snapshot (4.0-20000118-CURRENT). The following network cards from Intel are listed: Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel PRO/100+ Management Adapter FreeBSD also supports the "Intel InBusiness 10/100 PCI Network Adaptor", which has a different PCI device ID than the above listed cards. Can someone also add this to RELNOTES.TXT. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9:29:42 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6697C14D67; Tue, 18 Jan 2000 09:29:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 53B101CD631; Tue, 18 Jan 2000 09:29:41 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 09:29:41 -0800 (PST) From: Kris Kennaway To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: Feature test for OpenSSL + RSA In-Reply-To: <8543.948189126@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Sheldon Hearn wrote: > On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote: > > > +.if defined(WITH_RSA) && ${WITH_RSA} == YES > > + /usr/bin/touch /etc/ssl/openssl_hasrsa > > Um, are you sure you want that hard path, /etc/ssl ? Shouldn't there be > a ${DESTDIR} in there? What do you need this for? Yep, I realised this when I was falling asleep last night. Thanks :) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9:46:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 0C2A61504E; Tue, 18 Jan 2000 09:46:23 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id RAA99429; Tue, 18 Jan 2000 17:46:24 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 18 Jan 2000 17:46:23 -0000 (GMT) From: "Steve O'Hara-Smith" To: (Satoshi - Ports Wraith - Asami) Subject: Re: Mandating USA_RESIDENT Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-00 Satoshi - Ports Wraith - Asami wrote: > Won't people get into legal trouble (technically) if they build the > wrong version? As far as I understand things specifying USA_RESIDENT=yes when it is not true is liable (technically) to get some US based ftp server operator in trouble (most likely Walnut Creek) by downloading export controlled material from a US ftp site (this seems insane to me but that is my understanding). It may also get the user into trouble depending on the legal status of crypto in their country. Setting USA_RESIDENT=no when it is not true is liable to get the user into trouble for patent violations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 9:48:35 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6EEA8153D0; Tue, 18 Jan 2000 09:48:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F82F1CD62F; Tue, 18 Jan 2000 09:48:15 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 09:48:15 -0800 (PST) From: Kris Kennaway To: Sheldon Hearn Cc: David O'Brien , current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: <11376.948200498@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Sheldon Hearn wrote: > Does sysinstall set this one? If not, it should. Then we can stop > worrying about it. :-) Not yet, but it should. If someone can help me out here it would be greatly appreciated. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 10: 5: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 65CB114FFB; Tue, 18 Jan 2000 10:04:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 558091CD466; Tue, 18 Jan 2000 10:04:29 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 10:04:29 -0800 (PST) From: Kris Kennaway To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: Feature test for OpenSSL + RSA In-Reply-To: <20000118104019.DCD111CD9@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Peter Wemm wrote: > Yes, This should most definately have ${DESTDIR} for this sort of thing, but > even then I'm not sure this is a good change.. We have got to find a better > way than this. I've said this a couple of times in private, but will repeat it again for the list: we could do something like `nm /usr/lib/libcrypto.so | grep RSA_free`, but this seemed ugly and non-obvious to me (e.g. if someone who is not bsd.port.mk wanted to check whether their openssl port was RSA-enabled). It also seems to get invoked about 20 times during the course of making an openssl-using port (at least, that's how many times my debugging echos get run :) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 10: 9:56 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id DA17C14EFC; Tue, 18 Jan 2000 09:58:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CC26C1CD405; Tue, 18 Jan 2000 09:58:21 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 09:58:21 -0800 (PST) From: Kris Kennaway To: Patrick Bihan-Faou Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: <01fa01bf61d5$7162c550$040aa8c0@local.mindstep.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Patrick Bihan-Faou wrote: > If we are changing the meaning of "USA_RESIDENT", could we replace it by We're not. It's just that until now it hasn't really mattered if it wasn't set (the cases where it did matter, like whether or not to fetch a crypto port from a US site, it was required it to be set there). Now it needs to be set to do a buildword. > It seems to me that a things progress, the crypto regulation gets more > complicated everyday. Why not have a "CRYPTO_COUNTRY" variable that could be > set to "USA" "FRANCE" "CANADA" or "other" based where you live and weither > special consideration must be taken relative to the crypto code ? I don't know much about the restrictions of other countries. If the current crypto policies were a legal problem for someone else we can surely change them to suit, but I'd rather not complicate things even more than they are already without a reason.. > The other thing that could be set based on the CRYPTO_COUNTRY code is where > to get the FreeBSD crypto related source from. Well, right now there is only one non-US crypto repository (AFAIK), so "closest" is a degenerate case :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 10:40:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 9C43D14C21 for ; Tue, 18 Jan 2000 10:38:27 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id LAA22704 for ; Tue, 18 Jan 2000 11:38:00 -0700 (MST) Received: from ip-26-004.prc.gblx.net(206.165.26.4), claiming to be "pinyon.org" via SMTP by smtp03.primenet.com, id smtpdAAA8ZaynS; Tue Jan 18 11:37:49 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id C526C6C for ; Tue, 18 Jan 2000 11:37:55 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: current@FreeBSD.ORG Subject: FIC SD-11 not happy with ata Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jan 2000 11:37:55 -0700 From: "Russell L. Carter" Message-Id: <20000118183755.C526C6C@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I swapped out my motherboard and am seeing this now: ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode That doesn't sound good... This drive ran just fine with an ASUS P2B and seems to run fine on the FIC too. This is on a farm fresh -current. I've appended the dmesg. Cheers, Russell Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #14: Tue Jan 18 10:44:46 MST 2000 rcarter@chomsky.pinyon.org:/usr/src/sys/compile/CURRENT Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 499034055 Hz CPU: AMD-K7(tm) Processor (499.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc0400000 real memory = 268369920 (262080K bytes) avail memory = 257212416 (251184K bytes) Preloaded elf kernel "kernel" at 0xc02f3000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: port 0xd800-0xd8ff mem 0xeefff000-0xeeffffff,0xef000000-0xefffffff at device 3.0 on pci0 pci0: unknown card (vendor=0x12eb, dev=0x0001) at 6.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: at device 7.4 on pci0 de0: port 0xc800-0xc87f mem 0xeeffef80-0xeeffefff irq 11 at device 9.0 on pci0 de0: 21143 [10-100Mb/s] pass 3.0 de0: address 00:80:c8:63:47:84 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 5 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PCL,PostScript lpt0: on ppbus0 lpt0: Interrupt-driven port ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: ATA-4 disk at ata1 as master ad1: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA66 Mounting root from ufs:/dev/ad0s1a de0: enabling 100baseTX port ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 2:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D003014ECF; Tue, 18 Jan 2000 11:02:11 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA69384; Tue, 18 Jan 2000 12:02:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18545; Tue, 18 Jan 2000 12:02:28 -0700 (MST) Message-Id: <200001181902.MAA18545@harmony.village.org> To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Subject: Re: Mandating USA_RESIDENT Cc: Kris Kennaway , "David O'Brien" , current@FreeBSD.ORG In-reply-to: Your message of "18 Jan 2000 03:03:09 PST." References: Date: Tue, 18 Jan 2000 12:02:28 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Satoshi - Ports Wraith - Asami writes: : Won't people get into legal trouble (technically) if they build the : wrong version? RESIDENT= CITIZEN= Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 3:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7FCE014DFB for ; Tue, 18 Jan 2000 11:03:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA69388; Tue, 18 Jan 2000 12:03:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18558; Tue, 18 Jan 2000 12:03:41 -0700 (MST) Message-Id: <200001181903.MAA18558@harmony.village.org> To: Brian Somers Subject: Re: PnP probing in -current Cc: Peter Wemm , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org In-reply-to: Your message of "Tue, 18 Jan 2000 12:33:30 GMT." <200001181233.MAA52927@hak.lan.Awfulhak.org> References: <200001181233.MAA52927@hak.lan.Awfulhak.org> Date: Tue, 18 Jan 2000 12:03:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001181233.MAA52927@hak.lan.Awfulhak.org> Brian Somers writes: : UP, UP, UP, UP, DOWN, UP, DOWN, DOWN : : Needless to say (you wanna see the state of this place), I can't seem : to find the manual at the moment :-/ OK. I'll take a look at it and see what's up. I even found my 1542CP in the large mass of cards in my basement... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 4:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5F80B14CA6; Tue, 18 Jan 2000 11:04:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA98816; Tue, 18 Jan 2000 11:04:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Sheldon Hearn , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-reply-to: Your message of "Tue, 18 Jan 2000 09:48:15 PST." Date: Tue, 18 Jan 2000 11:04:29 -0800 Message-ID: <98813.948222269@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not yet, but it should. If someone can help me out here it would be > greatly appreciated. "Setting it in sysinstall" is easy. Deciding where and how to set it in response to questions at certain stages of the installations(s) is more the sticking point. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 4:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 6652F15132; Tue, 18 Jan 2000 11:04:41 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id UAA14857; Tue, 18 Jan 2000 20:04:16 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Tue, 18 Jan 2000 20:03:14 +0100 To: Kris Kennaway , Patrick Bihan-Faou From: Brad Knowles Subject: Re: Mandating USA_RESIDENT Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:58 AM -0800 2000/1/18, Kris Kennaway wrote: > I don't know much about the restrictions of other countries. If the > current crypto policies were a legal problem for someone else we can > surely change them to suit, but I'd rather not complicate things even more > than they are already without a reason.. Russia and France both are highly crypto-unfriendly, in that you are not allowed to use any crypto whatsoever unless it has been explicitly approved by the government. Since their lists of what's been "approved" (read: cracked) by the government may differ, we're starting to get into some issues here where I think a "CRYPTO_COUNTRY" variable would make a lot of sense, and then we could derive appropriate "RSA" and "USA_RESIDENT" variables from them. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 5:33 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 25245150B9; Tue, 18 Jan 2000 11:04:32 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 15B9C1CD635; Tue, 18 Jan 2000 11:04:32 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 11:04:32 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: Satoshi - Ports Wraith - Asami , David O'Brien , current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: <200001181902.MAA18545@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Warner Losh wrote: > In message Satoshi - Ports Wraith - Asami writes: > : Won't people get into legal trouble (technically) if they build the > : wrong version? > > RESIDENT= > CITIZEN= What about us dual citizens? :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 5:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7167614E4C for ; Tue, 18 Jan 2000 11:05:53 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA73452; Tue, 18 Jan 2000 20:05:37 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001181905.UAA73452@freebsd.dk> Subject: Re: FIC SD-11 not happy with ata In-Reply-To: <20000118183755.C526C6C@pinyon.org> from "Russell L. Carter" at "Jan 18, 2000 11:37:55 am" To: rcarter@pinyon.org (Russell L. Carter) Date: Tue, 18 Jan 2000 20:05:37 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Russell L. Carter wrote: > > I swapped out my motherboard and am seeing this now: > > ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying > ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying > ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying > ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA > falling back to PIO mode This for the most part means cable and/or power problems, does this appear immediately or under moderate/high load ?? Remember the K7 is a power hog, how big is you PSU, especially how much power (amps) can it deliver on the 3.3V 5V and 12V rails ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11: 6:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-7.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.135]) by hub.freebsd.org (Postfix) with ESMTP id C0E1714ECF; Tue, 18 Jan 2000 11:06:24 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA00737; Tue, 18 Jan 2000 19:03:11 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA57355; Tue, 18 Jan 2000 19:03:02 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001181903.TAA57355@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: sos@FreeBSD.org Cc: current@FreeBSD.org Subject: ata observation (bug?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jan 2000 19:03:02 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I don't know if you'd class this as a bug report or more as an observation. I have a machine with the following: ata-pci0: port 0xf000-0xf00f at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 [.....] ad0: ATA-0 disk at ata0 as master ad0: 1623MB (3324384 sectors), 3298 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad1: ATA-4 disk at ata1 as master ad1: 7339MB (15032115 sectors), 15907 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-4 disk at ata1 as slave ad2: 26063MB (53377152 sectors), 52953 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 Note that ad0 is on a controller of its own, and ad[12] are on the second controller. If I put the second (7Gb) disk on the first controller as slave, I can't get the machine to boot. The wd driver works ok, but ad, although coming up in the ``?'' list in vfs_mountroot_ask(), won't boot... I get error 6 when I try ufs:/dev/rad0s1a at the prompt. This has stopped me going to the ata driver on this machine for a long time :-/ Moving the two UDMA disks to a controller of their own has solved the problem.... Comments ? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11:12:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3F8031501B; Tue, 18 Jan 2000 11:10:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA69462; Tue, 18 Jan 2000 12:10:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18696; Tue, 18 Jan 2000 12:11:07 -0700 (MST) Message-Id: <200001181911.MAA18696@harmony.village.org> To: Kris Kennaway Subject: Re: Mandating USA_RESIDENT Cc: Satoshi - Ports Wraith - Asami , "David O'Brien" , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 18 Jan 2000 11:04:32 PST." References: Date: Tue, 18 Jan 2000 12:11:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : > In message Satoshi - Ports Wraith - Asami writes: : > : Won't people get into legal trouble (technically) if they build the : > : wrong version? : > : > RESIDENT= : > CITIZEN= : : What about us dual citizens? :-) OK, forget CITIZEN then. I forget that gets complicated in a hurry. I've forgotten than many middle eastern countries offer this (Isreal and Turkey come to mind) and it isn't as relevant as RESIDENT. The idea for RESIDENT would be that it must be in {us,ca} to build RSA patented stuff via RSAREF. If other patented or semi-patented stuff came along, then we could test to see if it was jp, and not build the YoShiHaNya ONeCo data compression modules for that country, but allow building them elsewhere. It would be much more flexible than the rigid and US Centric USA_RESIDENT. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11:12:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable126.102-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 8919114C21 for ; Tue, 18 Jan 2000 11:11:07 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 78883 invoked from network); 18 Jan 2000 19:11:05 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 18 Jan 2000 19:11:05 -0000 Message-ID: <027601bf61e7$c4e5fe10$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: Subject: Make world break on openssl... Date: Tue, 18 Jan 2000 14:11:05 -0500 Organization: MindStep Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, this is probably not news, but here is what I get. I tried with both USA_RESIDENT=YES and no USA_RESIDENT defined... The code has been CVSuped on tuesday Jan 18 2000 around 2am EST. cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src-freebsd-4.x/secure/usr.bin/opens sl -DRSAref -I/usr/obj/usr/src-freebsd-4.x/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src-freebsd-4.x/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src-freebsd-4.x/secure/usr.bin. *** Error code 1 Stop in /usr/src-freebsd-4.x/secure. *** Error code 1 Stop in /usr/src-freebsd-4.x. *** Error code 1 Stop in /usr/src-freebsd-4.x. *** Error code 1 Stop in /usr/src-freebsd-4.x. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11:13:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 71EC0150CC; Tue, 18 Jan 2000 11:13:08 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA69466; Tue, 18 Jan 2000 12:13:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18715; Tue, 18 Jan 2000 12:13:29 -0700 (MST) Message-Id: <200001181913.MAA18715@harmony.village.org> To: Garrett Wollman Subject: Re: PNPBIOS + Dell PowerEdge = panic() Cc: Mike Smith , Bill Fumerola , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 18 Jan 2000 11:20:19 EST." <200001181620.LAA25082@khavrinen.lcs.mit.edu> References: <200001181620.LAA25082@khavrinen.lcs.mit.edu> <20000116002113.B75768@jade.chc-chimes.com> <200001180112.RAA02848@mass.cdrom.com> Date: Tue, 18 Jan 2000 12:13:28 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001181620.LAA25082@khavrinen.lcs.mit.edu> Garrett Wollman writes: : < said: : : > This is definitely a bad idea; IMHO we should only do this when the : > resource is actually activated (and obviously free it when deactivated). : : Absolutely! As I keep trying to explain to people, that's why there : *is* a separate activate function (or one of the reasons, anyway). Yes. There's lots of cool things that one can do with this. I know that the pccard code, both old and new, deferrs the actual programming of the bridge until a resource is activated (except for IRQ, which it further deferrs until the interrupt handler is setup). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11:29:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 69C1215116 for ; Tue, 18 Jan 2000 11:28:43 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id B7A0919CB; Tue, 18 Jan 2000 14:28:37 -0500 (EST) Date: Tue, 18 Jan 2000 14:28:37 -0500 From: Will Andrews To: Bush Doctor Cc: FreeBSD Current Subject: Re: buildworld failure in "===> makeinfo" Message-ID: <20000118142837.A6739@argon.blackdawn.com> References: <20000117172537.F21380@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000117172537.F21380@goku.cl.msu.edu>; from dervish@goku.cl.msu.edu on Mon, Jan 17, 2000 at 05:25:37PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 05:25:37PM -0500, Bush Doctor wrote: > "make buildworld" fails with sources cvsup'd around 17:00 est ... > > whereintheworld.pl (thanxs Bill Fenner) shows ... What does this Perl script do? :-) --Will To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11:31: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 236B315158 for ; Tue, 18 Jan 2000 11:29:57 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-5.local.net [192.168.1.5]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id LAA08659 for ; Tue, 18 Jan 2000 11:29:56 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <3884BF85.50170456@MexComUSA.net> Date: Tue, 18 Jan 2000 11:31:17 -0800 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Problems with PCMCIA Cards Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running current as of yesterday. I have neglegently not been rebooting after make world and making a new kernel. Yesterday I did reboot and found that something has changed and my D-Link 660 and my Viking Modem PCMCIA cards are no longer working. :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for D-Link(DE-66 0): Inappropriate ioctl for device Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for Viking(V.90 K 56flex): Inappropriate ioctl for device My kernel configuration is: device card0 device pcic0 at isa? device pcic1 at isa? device ed0 My pccard.conf is: card "D-Link" "DE-660" config 0x20 "ed0" 11 0x10 insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete I could find no changes in LINT or in /etc . I even ran mergemaster, just incase. I am trying to build a new world but have been stopped at crypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 Any help will be appreciated. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 11:58:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8DD1214BF2; Tue, 18 Jan 2000 11:58:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA73631; Tue, 18 Jan 2000 20:58:11 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001181958.UAA73631@freebsd.dk> Subject: Re: ata observation (bug?) In-Reply-To: <200001181903.TAA57355@hak.lan.Awfulhak.org> from Brian Somers at "Jan 18, 2000 07:03:02 pm" To: brian@Awfulhak.org (Brian Somers) Date: Tue, 18 Jan 2000 20:58:11 +0100 (CET) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Somers wrote: > Hi, > > I don't know if you'd class this as a bug report or more as an > observation. I have a machine with the following: bug :) > ata-pci0: port 0xf000-0xf00f at device 15.0 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > [.....] > ad0: ATA-0 disk at ata0 as master > ad0: 1623MB (3324384 sectors), 3298 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, WDMA2 > ad1: ATA-4 disk at ata1 as master > ad1: 7339MB (15032115 sectors), 15907 cyls, 15 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > ad2: ATA-4 disk at ata1 as slave > ad2: 26063MB (53377152 sectors), 52953 cyls, 16 heads, 63 S/T, 512 B/S > ad2: 16 secs/int, 1 depth queue, UDMA33 > > Note that ad0 is on a controller of its own, and ad[12] are on the > second controller. If I put the second (7Gb) disk on the first > controller as slave, I can't get the machine to boot. The wd driver > works ok, but ad, although coming up in the ``?'' list in > vfs_mountroot_ask(), won't boot... I get error 6 when I try > ufs:/dev/rad0s1a at the prompt. > > This has stopped me going to the ata driver on this machine for a > long time :-/ > > Moving the two UDMA disks to a controller of their own has solved the > problem.... Hmm, I'll investigate this, it sure adds more data to the equation.. Thanks for the report! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 12:22:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from sapphire.looksharp.net (mcdouga9.user.msu.edu [35.10.148.141]) by hub.freebsd.org (Postfix) with ESMTP id ECBD814BE5 for ; Tue, 18 Jan 2000 12:22:26 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by sapphire.looksharp.net (8.9.3/8.9.3) with ESMTP id PAA18200; Tue, 18 Jan 2000 15:21:36 -0500 (EST) (envelope-from bsdx@looksharp.net) X-Authentication-Warning: sapphire.looksharp.net: bsdx owned process doing -bs Date: Tue, 18 Jan 2000 15:21:36 -0500 (EST) From: Adam To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Why not a default number of pings? In-Reply-To: <01dd01bf6145$e13d6c80$0e00a8c0@neland.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the -a parameter to ping would be useful to you. It makes the pc speaker emit a beep for every reply. If you have the speaker working and are not hearing impaired, you will NOT forget! :) On Tue, 18 Jan 2000, Leif Neland wrote: > I've been hit by a "forgotten ping" again. > > I still do not see a reason for not having a default number of pings, instead of infinite. > The only reason I've seen is "It's always been so". > > Even if a default of 4 pings is not acceptable, because windows does it that way, why not a large default then? > > If somebody _really_ want to ping forever, let them use -t0, and defend the rest of us from our blunders of forgetting a ping, keeping the line open infinitely. > > How about a MAX_PING=3600 in make.conf or so? > > I've supplied patches earlier, but they've been rejected. > > Leif > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 12:24:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id DF0A415239 for ; Tue, 18 Jan 2000 12:24:33 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 81492 invoked by uid 1001); 18 Jan 2000 20:24:27 +0000 (GMT) To: kris@hub.freebsd.org Cc: leif@neland.dk, freebsd-current@FreeBSD.ORG Subject: Re: Why not a default number of pings? From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 17 Jan 2000 16:02:18 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 18 Jan 2000 21:24:27 +0100 Message-ID: <81490.948227067@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If somebody _really_ want to ping forever, let them use -t0, and > > defend the rest of us from our blunders of forgetting a ping, keeping > > the line open infinitely. > > I use ping for precisely this purpose. Yes, I could change my setup, > but so could you :-) I used SunOS (and later Solaris) for many years - with ping having a default count of 1. I hated it - I almost always used the -s option to get *my* desired ping behavior (standard BSD). And it wasn't a case of being used to something else - SunOS *was* my first contact with Unix. So please don't change the default behavior of ping. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 13:23:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 9F88B14ECD for ; Tue, 18 Jan 2000 13:23:33 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id PAA00450; Tue, 18 Jan 2000 15:23:04 -0600 (CST) (envelope-from obonilla) Date: Tue, 18 Jan 2000 15:23:04 -0600 From: Oscar Bonilla To: Edwin Culp Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards Message-ID: <20000118152304.A436@fisicc-ufm.edu> References: <3884BF85.50170456@MexComUSA.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <3884BF85.50170456@MexComUSA.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: > I am running current as of yesterday. I have neglegently not been > rebooting after make world and making a new kernel. Yesterday I did > reboot and found that something has changed and my D-Link 660 and my > Viking Modem PCMCIA cards are no longer working. > > :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for > D-Link(DE-66 > 0): Inappropriate ioctl for device > > Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for > Viking(V.90 K > 56flex): Inappropriate ioctl for device > > My kernel configuration is: > > device card0 > device pcic0 at isa? > device pcic1 at isa? > > device ed0 > > My pccard.conf is: > > card "D-Link" "DE-660" > config 0x20 "ed0" 11 0x10 > insert /etc/pccard_ether ed0 > remove /sbin/ifconfig ed0 delete > > I could find no changes in LINT or in /etc . I even ran mergemaster, > just incase. > > I am trying to build a new world but have been stopped at > > crypto -L/usr/local/lib -lrsaref > speed.o: In function `speed_main': > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > /usr/local/lib/libcrypto.so: undefined reference to > `ERR_load_RSAREF_strings' > *** Error code 1 > Stop in /usr/src/secure/usr.bin/openssl. > *** Error code 1 > Stop in /usr/src/secure/usr.bin. > *** Error code 1 > I was having exactly the same problem with a current cvsuped today. I could fix it by changing the line device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 to device pcic0 at isa? in the kernel config file... regards, -oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 50 D4 B6 9B DB 7D D8 47 DF 3C ED 39 18 78 DA 8C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 13:29:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DC49214F86 for ; Tue, 18 Jan 2000 13:29:12 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id QAA51654 for ; Tue, 18 Jan 2000 16:29:00 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 18 Jan 2000 16:28:59 -0500 (EST) From: Chuck Robey To: FreeBSD current Subject: breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sure would be nice if some folks would start testing before committing. I'm starting to wonder how long it'll be before it builds again. I understand screwups (god know I better!) but if you don't test before commit, that's taking things a step too far. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 13:39:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E82C15108; Tue, 18 Jan 2000 13:39:04 -0800 (PST) (envelope-from taavi@uninet.ee) Received: by ns.uninet.ee (Postfix, from userid 1001) id 2B8B225898; Tue, 18 Jan 2000 23:39:00 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by ns.uninet.ee (Postfix) with SMTP id 26A7E14A12; Tue, 18 Jan 2000 23:39:00 +0200 (EET) Date: Tue, 18 Jan 2000 23:39:00 +0200 (EET) From: Taavi Talvik To: "Jordan K. Hubbard" Cc: Kris Kennaway , Sheldon Hearn , David O'Brien , current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: <98813.948222269@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Jordan K. Hubbard wrote: > > Not yet, but it should. If someone can help me out here it would be > > greatly appreciated. > > "Setting it in sysinstall" is easy. Deciding where and how to set it > in response to questions at certain stages of the installations(s) > is more the sticking point. Maybe we should extend meaning of USA_RESIDENT or introduce new variable indicating contry. After doing netfork install, subsecuent fetces for ports/packages/distfiles from nearest ftp.xx.freebsd.org/cvsup.xx.freebsd.org is really handy. Specially for newcomers, who do not yet have idea of editing /etc/make.conf best regards, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee Unineti Andmeside AS | phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 13:45:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 1AC531523F for ; Tue, 18 Jan 2000 13:45:35 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 94687104C13; Tue, 18 Jan 2000 15:45:34 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext04.compaq.com (Postfix) with ESMTP id 8F2DBFB101 for ; Tue, 18 Jan 2000 15:45:34 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id F0D1EBC4CD; Tue, 18 Jan 2000 15:45:26 -0600 (CST) Received: from fedex-s1.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id D35CFB2A42 for ; Tue, 18 Jan 2000 15:45:26 -0600 (CST) From: Bruce Burden Posted-Date: Tue, 18 Jan 2000 15:46:06 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id PAA20109 for freebsd-current@freebsd.org; Tue, 18 Jan 2000 15:41:19 -0600 (CST) Message-Id: <200001182141.PAA20109@panther.txn.cpqcorp.net> Subject: Re: breakage To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2000 15:41:18 -0600 (CST) Reply-To: bruce.burden@compaq.com In-Reply-To: from "Chuck Robey" at Jan 18, 2000 04:28:59 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sure would be nice if some folks would start testing before > committing. I'm starting to wonder how long it'll be before it builds > again. > I had two problems building a kernel from 1/16/2000: I had to create the directories: /usr/share/examples/ses /usr/share/doc/bind before the "make installworld" would work. The "make buildworld" worked fine. The was on top of code downloaded and build 1/1/2000. So, if it is breakage, it happened in the last two days. Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 13:45:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from smartypants.caffeine.com (adsl-209-233-24-51.dsl.snfc21.pacbell.net [209.233.24.51]) by hub.freebsd.org (Postfix) with ESMTP id 1DB271527E for ; Tue, 18 Jan 2000 13:45:39 -0800 (PST) (envelope-from wellsian@caffeine.com) Received: from localhost (wellsian@localhost) by smartypants.caffeine.com (8.9.3/8.9.2) with ESMTP id NAA23147; Tue, 18 Jan 2000 13:35:22 -0800 (PST) (envelope-from wellsian@caffeine.com) Date: Tue, 18 Jan 2000 13:35:22 -0800 (PST) From: dwells To: fritz.heinrichmeyer@fernuni-hagen.de Cc: current@freebsd.org Subject: Re: when the modem rings twice .... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 16 Jan 2000 21:13:28 +0100 >From: "F. Heinrichmeyer" > >my freebsd box goes down, something strange happens, when a ring signal >is detected. I >have apm disabled in the bios and no apm device in the config file. > >It is "alsmost a reset", like a short power failure. The screen is >disturbed for a moment. The same happens when the alt+bs key is pressed >with XFree btw. > >The modem sent a ring signal during a build world. I had to reformat the >root partition afterwards. Other than power (mis)management the only thing I can think of would be the modem cable. External modem? Have you tested where RI goes? If it's an internal then please disregard this reach. :) Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 14:10:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 480DC151E2; Tue, 18 Jan 2000 14:10:06 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.197]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA7419; Tue, 18 Jan 2000 23:09:58 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id XAA23380; Tue, 18 Jan 2000 23:09:46 +0100 (CET) (envelope-from asmodai) Date: Tue, 18 Jan 2000 23:09:46 +0100 From: Jeroen Ruigrok/Asmodai To: Andy Sparrow Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Integrated Vibra16 in -current Message-ID: <20000118230946.L12908@daemon.ninth-circle.org> References: <200001180211.SAA13312@mega.geek4food.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001180211.SAA13312@mega.geek4food.org>; from andy@geek4food.org on Mon, Jan 17, 2000 at 06:11:09PM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000118 04:02], Andy Sparrow (andy@geek4food.org) wrote: >Given the Plug'n'Pray changes in -current, I pretty much expected to lose >AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to >probe the "magic" ports for the AWE32). AWE32 here, PnPBIOS to off, and added device pcm0 and device sbc0 to my kernel config file. Works perfectly for me. Thanks Cameron! -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project I was searching through the Heavens and somehow I slipped... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 14:11:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D0E9F151E8 for ; Tue, 18 Jan 2000 14:11:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA70297; Tue, 18 Jan 2000 15:11:31 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA20351; Tue, 18 Jan 2000 15:11:43 -0700 (MST) Message-Id: <200001182211.PAA20351@harmony.village.org> To: Brian Somers Subject: Re: PnP probing in -current Cc: Peter Wemm , freebsd-current@FreeBSD.org, brian@hak.lan.Awfulhak.org In-reply-to: Your message of "Tue, 18 Jan 2000 12:33:30 GMT." <200001181233.MAA52927@hak.lan.Awfulhak.org> References: <200001181233.MAA52927@hak.lan.Awfulhak.org> Date: Tue, 18 Jan 2000 15:11:42 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001181233.MAA52927@hak.lan.Awfulhak.org> Brian Somers writes: : Where UP == OFF, from 1-8 I've got : : UP, UP, UP, UP, DOWN, UP, DOWN, DOWN OK. I've found out what the problem is, at least with the bog standard GENERIC. I'll see about finding some time to fix aha. Short answer is that aha is caching softc pointers, which it shouldn't really be doing in the new world order. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 14:24:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 50C2D14C39 for ; Tue, 18 Jan 2000 14:24:14 -0800 (PST) (envelope-from trouble@netquick.net) Received: from bastille.netquick.net ([216.48.32.159] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12Aham-000CWS-00; Tue, 18 Jan 2000 17:59:16 -0500 Message-ID: <3885904F.17F8E607@netquick.net> Date: Wed, 19 Jan 2000 05:22:07 -0500 From: TrouBle Reply-To: trouble@netquick.net Organization: Hacked Furbies X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-20000114-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey Cc: FreeBSD current Subject: Re: breakage References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as of a cvsup from today, i just finished a buildworls and an installworld, so it seems the errors on my system have gone away Chuck Robey wrote: > > Sure would be nice if some folks would start testing before > committing. I'm starting to wonder how long it'll be before it builds > again. I understand screwups (god know I better!) but if you don't test > before commit, that's taking things a step too far. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 15:14:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id EB90C14A26 for ; Tue, 18 Jan 2000 15:14:05 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 359803E3F; Wed, 19 Jan 2000 00:13:06 +0100 (CET) Date: Wed, 19 Jan 2000 00:13:06 +0100 From: Jesper Skriver To: Christopher Masto Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: apm suspend ?? Message-ID: <20000119001306.A74876@skriver.dk> References: <20000116205650.A64495@skriver.dk> <200001171818.LAA10403@harmony.village.org> <20000117212038.A69519@skriver.dk> <20000117170014.A22939@netmonger.net> <20000117234623.A70090@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000117234623.A70090@skriver.dk>; from jesper@skriver.dk on Mon, Jan 17, 2000 at 11:46:23PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 17, 2000 at 11:46:23PM +0100, Jesper Skriver wrote: > On Mon, Jan 17, 2000 at 05:00:14PM -0500, Christopher Masto wrote: > > On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote: > > > On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: > > > > In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: > > > > : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now > > > > : suspend doesn't work as expected. > > > > : > > > > : When I run 'apm -z' the laptop suspends as normal, but right after this > > > > : the harddisk led turns on, and it powers up again. > > > > > > > > That's very odd. apm hasn't changed since Dec 2 and even that was > > > > just deleting code that had been obsolete for a while now. > > > > > > I don't get it either - will try to revert to -CURRENT as of jan 5th, > > > and see if it works again ... > > > > Sometimes the "enter" at the end of the command is sufficient to wake the > > machine back up. Have you tried "sleep 2; apm -z"? > > Yep, that's not it. > > I've just verified, by reverting to -CURRENT as of > *default date=2000.01.05.12.00.00 > > Suspend works as expected, tomorrow I'll try at 2 days intervals, to try > to narrow down the commit making the difference ... And it also works as of *default date=2000.01.13.23.00.00 But didn't on the cvsup on the 16th ... will try to narrow it down even further ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 15:31:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0E21214C85 for ; Tue, 18 Jan 2000 15:31:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id AAA31735 for ; Wed, 19 Jan 2000 00:28:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: boot messages for pci devices... From: Poul-Henning Kamp Date: Wed, 19 Jan 2000 00:28:09 +0100 Message-ID: <31733.948238089@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 Is this level of verbosity really helping anybody ? I thought we printed out the port/mem stuff for ISA because it is usually jumpered by the admin, but for dynamic allocation busses/devices I think this should be "bootverbose" material. Or maybe we should always make the resource allocations bootverbose stuff now ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 15:36:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E0A5414DB1; Tue, 18 Jan 2000 15:36:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA73441; Tue, 18 Jan 2000 18:35:27 -0500 (EST) Date: Tue, 18 Jan 2000 18:35:26 -0500 (EST) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: <31733.948238089@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Poul-Henning Kamp wrote: > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > Is this level of verbosity really helping anybody ? Its consistant, but I need to unify all the resource printing stuff since theres about 5 different ways that are being used to print the stuff right now. I'll do this after 4.0R. > I thought we printed out the port/mem stuff for ISA because it is > usually jumpered by the admin, but for dynamic allocation > busses/devices I think this should be "bootverbose" material. Humm... Thats possible. There was talk a while ago about making multiple levels of verbosity in the bootup messages. I'll explore this when I fix the line wrapping issues. It would really be nice if we could have busfs; this would make it much easier to allow access to this sort of information. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 15:46:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 1616F14F30; Tue, 18 Jan 2000 15:46:51 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id EF4C416BE; Tue, 18 Jan 2000 15:45:42 -0800 (PST) Date: Tue, 18 Jan 2000 15:45:42 -0800 From: Chris Piazza To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... Message-ID: <20000118154542.B282@norn.ca.eu.org> References: <31733.948238089@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <31733.948238089@critter.freebsd.dk>; from phk@FreeBSD.ORG on Wed, Jan 19, 2000 at 12:28:09AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: > > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > Is this level of verbosity really helping anybody ? I *thought* I noticed it was different. I actually find this pretty annoying because it wraps almost all of the lines and makes it difficult to read dmesg. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16: 6:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 9FE12150E3 for ; Tue, 18 Jan 2000 16:06:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id QAA27689 for ; Tue, 18 Jan 2000 16:02:36 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001190002.QAA27689@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-reply-to: Your message of "Wed, 19 Jan 2000 00:28:09 +0100." <31733.948238089@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jan 2000 16:02:36 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > Is this level of verbosity really helping anybody ? > > I thought we printed out the port/mem stuff for ISA because it is > usually jumpered by the admin, but for dynamic allocation busses/devices > I think this should be "bootverbose" material. > > Or maybe we should always make the resource allocations bootverbose stuff > now ? > I think that the pci info should be displayed onlly in verbose mode . Some of the pci devices specially the newer graphic cards have tons of memory map registers and it is of virtually no use to users. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16:18:48 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 70A6114C31; Tue, 18 Jan 2000 16:18:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 573E71CD645; Tue, 18 Jan 2000 16:18:46 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 16:18:46 -0800 (PST) From: Kris Kennaway To: Taavi Talvik Cc: "Jordan K. Hubbard" , Sheldon Hearn , David O'Brien , current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Taavi Talvik wrote: > Maybe we should extend meaning of USA_RESIDENT or introduce new variable > indicating contry. After doing netfork install, subsecuent fetces for > ports/packages/distfiles from nearest > ftp.xx.freebsd.org/cvsup.xx.freebsd.org is really handy. Specially for > newcomers, who do not yet have idea of editing /etc/make.conf There seems to be broad support for this idea, but I'd prefer to leave it as is for now and get it working properly, then we can revisit it after 4.0-REL. Fetching packages due to network topology is another idea I've wanted to implement for a while, although I was thinking of doing it dynamically by testing the available bandwidth to each of the hosts (and storing it in a database) and using them in order of increasing bandwidth. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16:21: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id A5BB41508B; Tue, 18 Jan 2000 16:20:59 -0800 (PST) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id BAA19160; Wed, 19 Jan 2000 01:18:04 +0100 (CET) (envelope-from leif@neland.dk) Message-ID: <006e01bf6212$ba40b740$0e00a8c0@neland.dk> From: "Leif Neland" To: "Jonathan M. Bresler" Cc: References: <20000118020736.E1AD4150AD@hub.freebsd.org> Subject: Re: ppp, incoming mail keeping the line up. Date: Wed, 19 Jan 2000 01:16:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jonathan M. Bresler" To: Cc: Sent: Tuesday, January 18, 2000 3:07 AM Subject: Re: ppp, incoming mail keeping the line up. > >=20 > > I run user-ppp, and I have a mx-record for my system, so incoming = mail =3D > > goes directly to my system. >=20 > this is asking for trouble. you should get yourself an MX > that is online all the time and will store your mail for you. you can > then pick it up whenever you want using APOP or POP thru SSH....i > peronsally use APOP thru SSH via fetchmail ;) >=20 I have a higher numbered MX online all the time, and used to pick up by = ETRN. Now I pick up by uucp (just for the heck of it), but still have myself = as lowest MX, to get mail fast while online. I don't like fetchmail to handle all my adresses and aliases. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16:32:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id C043F14E6D for ; Tue, 18 Jan 2000 16:32:15 -0800 (PST) (envelope-from usebsd@free.fr) Received: from safi (paris11-nas5-22-191.dial.proxad.net [213.228.22.191]) by postfix1.free.fr (Postfix) with SMTP id E7A0628DAD; Wed, 19 Jan 2000 01:20:05 +0100 (MET) From: "mouss" To: "Steve O'Hara-Smith" , "Satyajit Das" Cc: Subject: RE: shell problem Date: Wed, 19 Jan 2000 01:35:06 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I like to use BASH shell in my user account. how can i do this ? please > > inform. > > Install bash (either from ports or a package). > > Use chsh to change the entry for Shell to /usr/local/bin/bash. and before you ask why you cannot ftp to your machine, do not forget to add the path above to /etc/shells. > PS: This sort of question is better on -questions than -current. and one should take a look at the mailing list manifest! regards, mouss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16:36:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id DFBBE14FB2; Tue, 18 Jan 2000 16:36:30 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id LAA12787; Wed, 19 Jan 2000 11:33:06 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma012763; Wed, 19 Jan 00 11:32:55 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.2) with ESMTP id LAA29452; Wed, 19 Jan 2000 11:33:05 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Wed, 19 Jan 2000 11:33:04 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Kris Kennaway wrote: > Fetching packages due to network topology is another idea I've wanted to > implement for a while, although I was thinking of doing it dynamically by > testing the available bandwidth to each of the hosts (and storing it in a > database) and using them in order of increasing bandwidth. You also need to cater for those of us behind restrictive firewalls that keep our own copies of the packages distribution. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16:47: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7385414FB2; Tue, 18 Jan 2000 16:47:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 630991CD647; Tue, 18 Jan 2000 16:47:07 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 16:47:07 -0800 (PST) From: Kris Kennaway To: Patrick Bihan-Faou Cc: freebsd-current@FreeBSD.ORG Subject: Re: Make world break on openssl... In-Reply-To: <027601bf61e7$c4e5fe10$040aa8c0@local.mindstep.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Patrick Bihan-Faou wrote: > cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src-freebsd-4.x/secure/usr.bin/opens > sl -DRSAref -I/usr/obj/usr/src-freebsd-4.x/i386/usr/include -o openssl > apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o > enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o > pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o > sess_id.o speed.o verify.o version.o > x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref > speed.o: In function `speed_main': > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > /usr/local/lib/libcrypto.so: undefined reference to > `ERR_load_RSAREF_strings' it's a known problem which I hope to fix tonight - pkg_delete or move aside your openssl installation (e.g. /usr/local/lib/lib{crypto,ssl}.*). Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 16:58:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (deep-thought.demos.su [195.133.1.74]) by hub.freebsd.org (Postfix) with ESMTP id 0633214DBE; Tue, 18 Jan 2000 16:58:49 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id DAA65801; Wed, 19 Jan 2000 03:53:30 +0300 (MSK) (envelope-from ache) Date: Wed, 19 Jan 2000 03:53:29 +0300 From: "Andrey A. Chernov" To: Peter Wemm Cc: current@freebsd.org, bde@freebsd.org, sheldonh@freebsd.org Subject: Re: Security hole with new setresuid call Message-ID: <20000119035329.A65749@nagual.pp.ru> References: <20000118061202.50F8D1CD4@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000118061202.50F8D1CD4@overcee.netplex.com.au> Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 18, 2000 at 02:12:02PM +0800, Peter Wemm wrote: > .. and why is this a security hole? setresuid(geteuid(), geteuid(), geteuid()) > is equivalent to setuid(geteuid()).. Umm, maybe not the hole exactly, but difference between same area syscalls implementation. We define POSIX_APPENDIX_B_4_2_2 by default for setuid(geteuid()), but I mean case when it is _not_ defined (BTW, why to have define which is always on?) And in case POSIX_APPENDIX_B_4_2_2 is not defined, ruid = euid; assignment was not allowed before you add new syscall. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 17: 0:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 398C315153 for ; Tue, 18 Jan 2000 17:00:09 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 1552 invoked by uid 1010); 19 Jan 2000 00:50:24 -0000 Date: Wed, 19 Jan 2000 00:50:24 +0000 From: George Cox To: Jeroen Ruigrok/Asmodai Cc: Andy Sparrow , freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Integrated Vibra16 in -current Message-ID: <20000119005024.B1487@extremis.demon.co.uk> References: <200001180211.SAA13312@mega.geek4food.org> <20000118230946.L12908@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000118230946.L12908@daemon.ninth-circle.org>; from asmodai@wxs.nl on Tue, Jan 18, 2000 at 11:09:46PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18/01 23:09, Jeroen Ruigrok/Asmodai wrote: > >Given the Plug'n'Pray changes in -current, I pretty much expected to lose > >AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to > >probe the "magic" ports for the AWE32). > > AWE32 here, PnPBIOS to off, and added device pcm0 and device sbc0 to my > kernel config file. > > Works perfectly for me. Yeap, I've got a Creative AWE64 Gold ISA card working perfectly using the exact same settings. $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 18 2000 20:59:19 Installed devices: pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) > Thanks Cameron! Yes absolutely. Well done, Sir! To think I was on the point of selling my AWE64 about 5 months ago because it didn't work under FreeBSD! gjvc -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 17:19:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 69C7814D1D for ; Tue, 18 Jan 2000 17:19:48 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 2385 invoked by uid 1010); 19 Jan 2000 01:03:01 -0000 Date: Wed, 19 Jan 2000 01:03:01 +0000 From: George Cox To: Brad Knowles Cc: Kris Kennaway , Patrick Bihan-Faou , Sheldon Hearn , freebsd-current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT Message-ID: <20000119010301.A2299@extremis.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: ; from blk@skynet.be on Tue, Jan 18, 2000 at 08:03:14PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18/01 20:03, Brad Knowles wrote: > Russia and France both are highly crypto-unfriendly, in that you are > not allowed to use any crypto whatsoever unless it has been explicitly > approved by the government. France changed their policy from zero-crypto to allowing 128-bits almost exactly a year ago today. http://slashdot.org/articles/99/01/19/1255234.shtml -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18: 7:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 400FD14E0C for ; Tue, 18 Jan 2000 18:07:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA70813 for ; Tue, 18 Jan 2000 18:03:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA34925 for current@freebsd.org; Tue, 18 Jan 2000 18:03:01 -0800 (PST) (envelope-from obrien) Date: Tue, 18 Jan 2000 18:03:01 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: boot messages for pci devices... Message-ID: <20000118180301.A34556@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <31733.948238089@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <31733.948238089@critter.freebsd.dk>; from phk@freebsd.org on Wed, Jan 19, 2000 at 12:28:09AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 Agreed. For a PCI card all I want to know is what it is, and what IRQ it was assigned. A single line should be suffient. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18: 8:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-95.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.223]) by hub.freebsd.org (Postfix) with ESMTP id 5967A14BFE for ; Tue, 18 Jan 2000 18:08:27 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA01972; Wed, 19 Jan 2000 00:41:17 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA01391; Wed, 19 Jan 2000 00:41:16 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001190041.AAA01391@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Warner Losh Cc: Brian Somers , Peter Wemm , freebsd-current@FreeBSD.org, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: PnP probing in -current In-Reply-To: Message from Warner Losh of "Tue, 18 Jan 2000 15:11:42 MST." <200001182211.PAA20351@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jan 2000 00:41:16 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200001181233.MAA52927@hak.lan.Awfulhak.org> Brian Somers writes: > : Where UP == OFF, from 1-8 I've got > : > : UP, UP, UP, UP, DOWN, UP, DOWN, DOWN > > OK. I've found out what the problem is, at least with the bog > standard GENERIC. I'll see about finding some time to fix aha. Short > answer is that aha is caching softc pointers, which it shouldn't > really be doing in the new world order. Thanks for spending the time - I'll look out for the fix and un-hak pnp.c :*O > Warner > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18: 9:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7C33F14F49; Tue, 18 Jan 2000 18:09:52 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA70822; Tue, 18 Jan 2000 18:06:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA34956; Tue, 18 Jan 2000 18:06:16 -0800 (PST) (envelope-from obrien) Date: Tue, 18 Jan 2000 18:06:16 -0800 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Cc: kris@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT Message-ID: <20000118180616.B34556@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <11376.948200498@axl.noc.iafrica.com> <01fa01bf61d5$7162c550$040aa8c0@local.mindstep.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <01fa01bf61d5$7162c550$040aa8c0@local.mindstep.com>; from patrick@mindstep.com on Tue, Jan 18, 2000 at 10:26:12AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 18, 2000 at 10:26:12AM -0500, Patrick Bihan-Faou wrote: > Then as part of the build process, automatically create specific variables > for RSA or other stuff as they show up: > > CRYPTO_RSA="RSAref" or CRYPTO_RSA="rsa" or CRYPTO_RSA="none". This can be > done by a little bit of shell script easily. I think this is the only way to properly handle it. As Garrett pointed out, some people in the USA actually do have a licence to use the "good" version of RSA. We could default if we wanted to: USA_RESIDENT=YES ==> CRYPTO_RSA=RSAref USA_RESIDENT=NO ==> CRYPTO_RSA=RSAintl if CRYPTO_RSA was unset. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:13:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7ADDE14E6D; Tue, 18 Jan 2000 18:13:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA01105; Tue, 18 Jan 2000 18:10:01 -0800 Date: Tue, 18 Jan 2000 18:10:00 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: <20000118180301.A34556@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: > > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it > was assigned. A single line should be suffient. Do you even need to know what IRQ it was assigned? It seems to me that IRQ, like IO-PORT, is only needed if you're either interested in such stuff or to catch conflicts (both are under bootverbose) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:15:38 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2D06714D62; Tue, 18 Jan 2000 18:15:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0CA201CD405; Tue, 18 Jan 2000 18:15:35 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 18:15:35 -0800 (PST) From: Kris Kennaway To: David O'Brien Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: <20000118180616.B34556@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, David O'Brien wrote: > I think this is the only way to properly handle it. As Garrett pointed > out, some people in the USA actually do have a licence to use the "good" > version of RSA. Is this the same Garrett who persuaded me not to include the RSA code at all in the freefall repository so that people wouldn't get in trouble for simply posessing it? :) > We could default if we wanted to: > > USA_RESIDENT=YES ==> CRYPTO_RSA=RSAref > USA_RESIDENT=NO ==> CRYPTO_RSA=RSAintl > > if CRYPTO_RSA was unset. I have no problem with this, but it means either we have to have people who have an RSA license get their crypto from internat, or freefall has to have the RSA code (possbibly in another cvsup collection). Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:27:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from web2102.mail.yahoo.com (web2102.mail.yahoo.com [128.11.68.246]) by hub.freebsd.org (Postfix) with SMTP id CCC1E14DB1 for ; Tue, 18 Jan 2000 18:27:45 -0800 (PST) (envelope-from valsho@yahoo.com) Received: (qmail 25114 invoked by uid 60001); 19 Jan 2000 02:14:07 -0000 Message-ID: <20000119021407.25113.qmail@web2102.mail.yahoo.com> Received: from [147.226.112.101] by web2102.mail.yahoo.com; Tue, 18 Jan 2000 18:14:07 PST Date: Tue, 18 Jan 2000 18:14:07 -0800 (PST) From: "Valentin S. Chopov" Subject: ata-all.c : undefined atapi_attach() in ata_attach() To: Soren Schmidt Cc: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that we need #if...#endif here, maybe something like that: ... #if NATAPICD > 0 || NATAPIFD > 0 || NATAPIST > 0 /* then the atapi devices */ for (ctlr=0; ctlrdevices & ATA_ATAPI_MASTER) atapi_attach(atadevices[ctlr], ATA_MASTER); if (atadevices[ctlr]->devices & ATA_ATAPI_SLAVE) atapi_attach(atadevices[ctlr], ATA_SLAVE); } #endif ... Val __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:39: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6F07A14E08; Tue, 18 Jan 2000 18:39:05 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA26359; Wed, 19 Jan 2000 12:46:41 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 19 Jan 2000 12:46:41 +1030 (CST) From: "Daniel O'Connor" To: Matthew Jacob Subject: Re: boot messages for pci devices... Cc: current@FreeBSD.ORG, "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-00 Matthew Jacob wrote: > Do you even need to know what IRQ it was assigned? It seems to me > that IRQ, > like IO-PORT, is only needed if you're either interested in such > stuff or to > catch conflicts (both are under bootverbose) What would be nice would be to have the normal version displayed and the verbose stuff go to a seperate buffer and logged seperatly.. ie so you don't clutter your boot screen with junk, but if you have a problem you can get at the verbose info :) .. and no I don't have any patches :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:51:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 7A5CA152A6 for ; Tue, 18 Jan 2000 18:51:38 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-5.local.net [192.168.1.5]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id QAA68778; Tue, 18 Jan 2000 16:44:01 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <38850925.9C27674C@MexComUSA.net> Date: Tue, 18 Jan 2000 16:45:25 -0800 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Oscar Bonilla Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards References: <3884BF85.50170456@MexComUSA.net> <20000118152304.A436@fisicc-ufm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar, Thanks a lot, but my kernel.conf has device pcic0 isa? Already. Thanks, ed Oscar Bonilla wrote: > On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: > > I am running current as of yesterday. I have neglegently not been > > rebooting after make world and making a new kernel. Yesterday I did > > reboot and found that something has changed and my D-Link 660 and my > > Viking Modem PCMCIA cards are no longer working. > > > > :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for > > D-Link(DE-66 > > 0): Inappropriate ioctl for device > > > > Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for > > Viking(V.90 K > > 56flex): Inappropriate ioctl for device > > > > My kernel configuration is: > > > > device card0 > > device pcic0 at isa? > > device pcic1 at isa? > > > > device ed0 > > > > My pccard.conf is: > > > > card "D-Link" "DE-660" > > config 0x20 "ed0" 11 0x10 > > insert /etc/pccard_ether ed0 > > remove /sbin/ifconfig ed0 delete > > > > I could find no changes in LINT or in /etc . I even ran mergemaster, > > just incase. > > > > I am trying to build a new world but have been stopped at > > > > crypto -L/usr/local/lib -lrsaref > > speed.o: In function `speed_main': > > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > > /usr/local/lib/libcrypto.so: undefined reference to > > `ERR_load_RSAREF_strings' > > *** Error code 1 > > Stop in /usr/src/secure/usr.bin/openssl. > > *** Error code 1 > > Stop in /usr/src/secure/usr.bin. > > *** Error code 1 > > > > I was having exactly the same problem with a current cvsuped today. > I could fix it by changing the line > > device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 > > to > > device pcic0 at isa? > > in the kernel config file... > > regards, > > -oscar > > -- > pgp public key: finger obonilla@fisicc-ufm.edu > pgp fingerprint: 50 D4 B6 9B DB 7D D8 47 DF 3C ED 39 18 78 DA 8C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:52:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 2FF1C14E14; Tue, 18 Jan 2000 18:52:11 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA27401; Tue, 18 Jan 2000 21:52:10 -0500 (EST) (envelope-from wollman) Date: Tue, 18 Jan 2000 21:52:10 -0500 (EST) From: Garrett Wollman Message-Id: <200001190252.VAA27401@khavrinen.lcs.mit.edu> To: Kris Kennaway Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: References: <20000118180616.B34556@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Is this the same Garrett who persuaded me not to include the RSA code at > all in the freefall repository so that people wouldn't get in trouble for > simply posessing it? :) No, this is the same Garrett who persuaded you not to include the RSA code at all in the freefall repository so that I could continue to maintain a mirror without getting into trouble with the Technology Licensing Office. I can (at work) *use* RSA all I want, but can't distribute it without approval from TLO, who must be persuaded that the Institute would benefit. I think it took them something like six months to come to agreement (with the then RSADSI) over the distribution of free PGP. This gets even more complicated when I start to involve my own private activities -- such as participating in the FreeBSD Project as a developer -- which is (part of) why I don't use software containing RSA in the course of personal-time activities. (And hence why I can't log in to freefall, at least until markm and I get Kerberos inter-realm set up.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 18:54:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B89AD14FF2 for ; Tue, 18 Jan 2000 18:54:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA71022; Tue, 18 Jan 2000 18:54:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA35258; Tue, 18 Jan 2000 18:54:40 -0800 (PST) (envelope-from obrien) Date: Tue, 18 Jan 2000 18:54:40 -0800 From: "David O'Brien" To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... Message-ID: <20000118185440.E32841@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000118180301.A34556@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Tue, Jan 18, 2000 at 06:10:00PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote: > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it > > was assigned. A single line should be suffient. > > Do you even need to know what IRQ it was assigned? It seems to me that IRQ, With wacky PC hardware being what it is, I would say yes. Especially on laptops. Having to tell everyone to boot verbose besides posting /var/run/dmesg.boot would be yet one more thing to get over when pulling teeth [read details] from people. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 19: 1:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 88D4114E14; Tue, 18 Jan 2000 19:01:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA01273; Tue, 18 Jan 2000 19:00:57 -0800 Date: Tue, 18 Jan 2000 19:00:57 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Daniel O'Connor" Cc: current@FreeBSD.ORG, "David O'Brien" Subject: Re: boot messages for pci devices... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What would be nice would be to have the normal version displayed and > the verbose stuff go to a seperate buffer and logged seperatly.. > > ie so you don't clutter your boot screen with junk, but if you have a > problem you can get at the verbose info :) > > .. and no I don't have any patches :) From tne cmn_err(9f) man page for solaris: The first character in format affects where the message will be written: ! the message goes only to the system buffer. ^ the message goes only to the console. ? If level is also CE_CONT, the message is always sent to the system buffer, but is only written to the console when the system has been booted in verbose mode. See kernel(1M). If neither condition is met, the '?' character has no effect and is simply ignored. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 19: 1:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 82EA714D5F; Tue, 18 Jan 2000 19:01:51 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id TAA01306; Tue, 18 Jan 2000 19:01:51 -0800 Date: Tue, 18 Jan 2000 19:01:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: <20000118185440.E32841@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, David O'Brien wrote: > On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote: > > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it > > > was assigned. A single line should be suffient. > > > > Do you even need to know what IRQ it was assigned? It seems to me that IRQ, > > > With wacky PC hardware being what it is, I would say yes. Especially on > laptops. Having to tell everyone to boot verbose besides posting > /var/run/dmesg.boot would be yet one more thing to get over when pulling > teeth [read details] from people. Hmm? Haven't we argued over this before [ default grep output ]]? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 19: 6:31 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8F60114EFA; Tue, 18 Jan 2000 19:06:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EBB41CD64B; Tue, 18 Jan 2000 19:06:28 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 19:06:28 -0800 (PST) From: Kris Kennaway To: Garrett Wollman Cc: David O'Brien , freebsd-current@FreeBSD.ORG Subject: Re: Mandating USA_RESIDENT In-Reply-To: <200001190252.VAA27401@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Garrett Wollman wrote: > No, this is the same Garrett who persuaded you not to include the RSA > code at all in the freefall repository so that I could continue to > maintain a mirror without getting into trouble with the Technology The upshot of all of which is that people who want RSA and have a license would have to get their crypto from internat, or from freefall with a special cvsup collection :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 19: 7:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from rumba.clave.gr.jp (rumba.clave.gr.jp [202.248.115.186]) by hub.freebsd.org (Postfix) with ESMTP id C704E15111 for ; Tue, 18 Jan 2000 19:07:54 -0800 (PST) (envelope-from mac@clave.gr.jp) Received: from localhost (rumba.clave.gr.jp [202.248.115.186]) by rumba.clave.gr.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA11166; Wed, 19 Jan 2000 12:05:52 +0900 (JST) To: eculp@MexComUSA.net Cc: obonilla@fisicc-ufm.edu, current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-Reply-To: <38850925.9C27674C@MexComUSA.net> References: <3884BF85.50170456@MexComUSA.net> <20000118152304.A436@fisicc-ufm.edu> <38850925.9C27674C@MexComUSA.net> X-Mailer: Mew version 1.94.2pre8 on Emacs 20.5 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000119120544K.mac@clave.gr.jp> Date: Wed, 19 Jan 2000 12:05:44 +0900 From: Masahide -mac- NODA X-Dispatcher: imput version 20000113(IM136) Lines: 29 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Edwin Culp Subject: Re: Problems with PCMCIA Cards Date: Tue, 18 Jan 2000 16:45:25 -0800 Message-ID: <38850925.9C27674C@MexComUSA.net> eculp> > On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: eculp> > > I am running current as of yesterday. I have neglegently not been eculp> > > rebooting after make world and making a new kernel. Yesterday I did eculp> > > reboot and found that something has changed and my D-Link 660 and my eculp> > > Viking Modem PCMCIA cards are no longer working. eculp> > > :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for eculp> > > D-Link(DE-66 eculp> > > 0): Inappropriate ioctl for device eculp> > > Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for eculp> > > Viking(V.90 K eculp> > > 56flex): Inappropriate ioctl for device I got this case, and fix it. :-) Probably, your kernel and pccardd is mismatch. To fix, cooy src/sys/pccard/cardinfo.h to /usr/incude/pccard/cardinfo.h, and make install pccard[cd] in src/usr.sbin/pccard. -- mac@clave.gr.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 19:12:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by hub.freebsd.org (Postfix) with ESMTP id 618FF14FCA for ; Tue, 18 Jan 2000 19:12:30 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA17425; Wed, 19 Jan 2000 12:12:27 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id MAA26121; Wed, 19 Jan 2000 12:12:27 +0900 (JST) Date: Wed, 19 Jan 2000 12:12:27 +0900 (JST) Message-Id: <200001190312.MAA26121@lavender.yy.cs.keio.ac.jp> To: eculp@MexComUSA.net Cc: current@FreeBSD.ORG, sanpei@sanpei.org Subject: Re: Problems with PCMCIA Cards In-Reply-To: Your message of "Wed, 19 Jan 2000 04:31:17 JST". <3884BF85.50170456@MexComUSA.net> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG eculp@MexComUSA.net wrote: >> I am running current as of yesterday. I have neglegently not been >> rebooting after make world and making a new kernel. Yesterday I did >> reboot and found that something has changed and my D-Link 660 and my >> Viking Modem PCMCIA cards are no longer working. >> >> :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for >> D-Link(DE-660): Inappropriate ioctl for device ~~~~~ I also had same problem. I think you need to update /usr/sbin/pccardd. This problem is related to below commit. ---- Date: Sat, 15 Jan 2000 22:44:48 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org hosokawa 2000/01/15 22:44:48 PST Modified files: sys/pccard cardinfo.h pccard.c usr.sbin/pccard/pccardd cardd.c Log: This fixes a bug that /etc/pccard_ether did not work without DHCP. For example, when /etc/pccard.conf had ed0 in config line, but kernel refused this name and said ----- related file: /usr/sbin/pccardd /usr/include/pccard/cardinfo.h your kernel # Do we have to add this changes to UPDATING file? MIHIRA Yoshiro Yokohama, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 19:30:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id C51D91528D for ; Tue, 18 Jan 2000 19:30:48 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas6-24-91.dial.proxad.net [213.228.24.91]) by postfix2.free.fr (Postfix) with ESMTP id 48630768C1; Wed, 19 Jan 2000 00:18:31 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id BAA01475; Wed, 19 Jan 2000 01:26:35 +0100 (CET) (envelope-from nsouch) Message-ID: <20000119012635.08678@breizh.free.fr> Date: Wed, 19 Jan 2000 01:26:35 +0100 From: Nicolas Souchu To: "F. Heinrichmeyer" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: no more parallel port zip drive References: <3881D3DC.DA529726@fernuni-hagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3881D3DC.DA529726@fernuni-hagen.de>; from F. Heinrichmeyer on Sun, Jan 16, 2000 at 03:21:16PM +0100 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 16, 2000 at 03:21:16PM +0100, F. Heinrichmeyer wrote: > >My parallel port zip-drive stopped working this weekend with the new ppc >code. There is no printer attached: Hmm, any chance to change parallel port bios setting on your MB? > > >-- >Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de >FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) >tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 20: 2:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id EE7CE14DD3; Tue, 18 Jan 2000 20:02:22 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id KAA76866; Wed, 19 Jan 2000 10:02:14 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 19 Jan 2000 10:02:14 +0600 (NS) From: Max Khon To: Ruslan Ermilov Cc: Ben Rosengart , current@FreeBSD.ORG Subject: Re: HEADS UP: grep 2.4a is now in the tree In-Reply-To: <20000118180444.A58470@relay.ucb.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 18 Jan 2000, Ruslan Ermilov wrote: > The equivalent to the old -a option is --binary-files=without-match. > If you want this by default, you can hardcode it in GREP_OPTIONS > environment variable. I think there should be one-letter shorthand for this. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 20:32:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id CF0FC14DD3 for ; Tue, 18 Jan 2000 20:32:48 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-5.local.net [192.168.1.5]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id UAA69504; Tue, 18 Jan 2000 20:32:33 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <38853EB6.1A4536C1@MexComUSA.net> Date: Tue, 18 Jan 2000 20:33:59 -0800 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Masahide -mac- NODA Cc: obonilla@fisicc-ufm.edu, current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards References: <3884BF85.50170456@MexComUSA.net> <20000118152304.A436@fisicc-ufm.edu> <38850925.9C27674C@MexComUSA.net> <20000119120544K.mac@clave.gr.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I copied the src/sys/pccard/cardinfo.h which was different from the one in include. I remade pccardc and pccardd. I haven't tested it yet because I am waiting for my "desperation" make world to finish in about 15 minutes, but I'm confident that is the problem. Thanks, I would not have found it for a while. I checked UPDATING and saw nothing, although my problem may have been because I haven't been able to finish a world since the commit. ed Masahide -mac- NODA wrote: > From: Edwin Culp > Subject: Re: Problems with PCMCIA Cards > Date: Tue, 18 Jan 2000 16:45:25 -0800 > Message-ID: <38850925.9C27674C@MexComUSA.net> > > eculp> > On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: > eculp> > > I am running current as of yesterday. I have neglegently not been > eculp> > > rebooting after make world and making a new kernel. Yesterday I did > eculp> > > reboot and found that something has changed and my D-Link 660 and my > eculp> > > Viking Modem PCMCIA cards are no longer working. > > eculp> > > :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for > eculp> > > D-Link(DE-66 > eculp> > > 0): Inappropriate ioctl for device > > eculp> > > Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for > eculp> > > Viking(V.90 K > eculp> > > 56flex): Inappropriate ioctl for device > > I got this case, and fix it. :-) > > Probably, your kernel and pccardd is mismatch. > > To fix, cooy src/sys/pccard/cardinfo.h to /usr/incude/pccard/cardinfo.h, > and make install pccard[cd] in src/usr.sbin/pccard. > > -- > mac@clave.gr.jp > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 20:34:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 3E64D14BCE for ; Tue, 18 Jan 2000 20:34:13 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-5.local.net [192.168.1.5]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id UAA69510; Tue, 18 Jan 2000 20:33:58 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <38853F0B.1810D625@MexComUSA.net> Date: Tue, 18 Jan 2000 20:35:24 -0800 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: MIHIRA Yoshiro Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards References: <200001190312.MAA26121@lavender.yy.cs.keio.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you very much. The include file was different and I copied it and rebuilt pccardc and pccardd and think that will solve the problem. Thanks, ed MIHIRA Yoshiro wrote: > eculp@MexComUSA.net wrote: > > >> I am running current as of yesterday. I have neglegently not been > >> rebooting after make world and making a new kernel. Yesterday I did > >> reboot and found that something has changed and my D-Link 660 and my > >> Viking Modem PCMCIA cards are no longer working. > >> > >> :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for > >> D-Link(DE-660): Inappropriate ioctl for device > ~~~~~ > I also had same problem. I think you need to update /usr/sbin/pccardd. > This problem is related to below commit. > > ---- > Date: Sat, 15 Jan 2000 22:44:48 -0800 (PST) > To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org > > hosokawa 2000/01/15 22:44:48 PST > > Modified files: > sys/pccard cardinfo.h pccard.c > usr.sbin/pccard/pccardd cardd.c > Log: > This fixes a bug that /etc/pccard_ether did not work without DHCP. > For example, when /etc/pccard.conf had ed0 in config line, but kernel > refused this name and said > ----- > > related file: > /usr/sbin/pccardd > /usr/include/pccard/cardinfo.h > your kernel > > # Do we have to add this changes to UPDATING file? > > MIHIRA Yoshiro > Yokohama, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21: 4:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id DF2E01525E for ; Tue, 18 Jan 2000 21:04:22 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id WAA09721; Tue, 18 Jan 2000 22:04:05 -0700 (MST) Received: from ip-83-145.prc.primenet.com(207.218.83.145), claiming to be "pinyon.org" via SMTP by smtp01.primenet.com, id smtpdAAARTaGZs; Tue Jan 18 22:03:53 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id 3C3086F; Tue, 18 Jan 2000 22:03:22 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: Soren Schmidt Cc: current@freebsd.org Subject: Re: FIC SD-11 not happy with ata In-Reply-To: Message from Soren Schmidt of "Tue, 18 Jan 2000 21:50:25 +0100." <200001182050.VAA73799@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 18 Jan 2000 22:03:21 -0700 From: "Russell L. Carter" Message-Id: <20000119050322.3C3086F@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %It seems Russell L. Carter wrote: %> %It seems Russell L. Carter wrote: %> %> = %> %> I swapped out my motherboard and am seeing this now: %> %> = %> %> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying %> %> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying %> %> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying %> %> ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=3D= ATA_ACTIVE_ATA %> %> falling back to PIO mode %> % %> %This for the most part means cable and/or power problems, does this %> %appear immediately or under moderate/high load ?? %> %Remember the K7 is a power hog, how big is you PSU, especially how %> %much power (amps) can it deliver on the 3.3V 5V and 12V rails ?? %> = %> All good points. Swapping the cable for an 80 pin ATA/66 %> cable had no effect. The PSU claims it can deliver %> 14A @ 3.3V, 25A @ 5V, and 10A @ 12V for this 250W unit. % %That should be enough... Hi Soren, I am beginning to believe that the FIC mb is the problem. My IBM-DPTA-372050 is only half as fast (500MB bonnie) as on the P2B (~10MB/s vs. ~19MB/s). A Jan 11 kernel = doesn't downgrade to PIO on the IBM-DTTA-371440 as fast as this evenings -current with your latest bits does, but eventually it gets there. )(*&$#%$# stupid magazine benchmarkers never actually test = things like IO... grrrrr.... Regards, Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:14:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id DBE0214F49 for ; Tue, 18 Jan 2000 21:14:39 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id VAA34307 for freebsd-current@freebsd.org; Tue, 18 Jan 2000 21:14:38 -0800 (PST) (envelope-from freebsd) Posted-Date: Tue, 18 Jan 2000 21:14:38 -0800 (PST) Message-Id: <200001190514.VAA34307@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Tue, 18 Jan 2000 21:14:37 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: YAWF: World failure- undefined reference to `RSA_PKCS1_RSAref' Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:24: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5AB4E152DD for ; Tue, 18 Jan 2000 21:23:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA70985; Tue, 18 Jan 2000 22:23:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA21575; Tue, 18 Jan 2000 21:38:47 -0700 (MST) Message-Id: <200001190438.VAA21575@harmony.village.org> To: Edwin Culp Subject: Re: Problems with PCMCIA Cards Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 18 Jan 2000 11:31:17 PST." <3884BF85.50170456@MexComUSA.net> References: <3884BF85.50170456@MexComUSA.net> Date: Tue, 18 Jan 2000 21:38:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3884BF85.50170456@MexComUSA.net> Edwin Culp writes: : :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for : D-Link(DE-66 : 0): Inappropriate ioctl for device Make sure that your kernel and pccardd match. The binary api changes from time to time in -curent. This is a sure symptom. Also, you will likely need to add an IRQ to the pcic line in your kernel config. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:24: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D028E14EFA; Tue, 18 Jan 2000 21:23:55 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA70993; Tue, 18 Jan 2000 22:23:53 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA21604; Tue, 18 Jan 2000 21:44:13 -0700 (MST) Message-Id: <200001190444.VAA21604@harmony.village.org> To: Chris Piazza Subject: Re: boot messages for pci devices... Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 18 Jan 2000 15:45:42 PST." <20000118154542.B282@norn.ca.eu.org> References: <20000118154542.B282@norn.ca.eu.org> <31733.948238089@critter.freebsd.dk> Date: Tue, 18 Jan 2000 21:44:13 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000118154542.B282@norn.ca.eu.org> Chris Piazza writes: : I *thought* I noticed it was different. I actually find this pretty : annoying because it wraps almost all of the lines and makes it difficult : to read dmesg. I don't mind them, but wouldn't object to a generic wrapping mechanism. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:24: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EA0D2152D4 for ; Tue, 18 Jan 2000 21:23:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA70990 for ; Tue, 18 Jan 2000 22:23:53 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA21591; Tue, 18 Jan 2000 21:40:47 -0700 (MST) Message-Id: <200001190440.VAA21591@harmony.village.org> To: Chuck Robey Subject: Re: breakage Cc: FreeBSD current In-reply-to: Your message of "Tue, 18 Jan 2000 16:28:59 EST." References: Date: Tue, 18 Jan 2000 21:40:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : Sure would be nice if some folks would start testing before : committing. I'm starting to wonder how long it'll be before it builds : again. I understand screwups (god know I better!) but if you don't test : before commit, that's taking things a step too far. I did a make world Sunday and it worked. I did a makeworld today and it was busted. Turned out to be a cvsup problem that I owe jdp a message about. It was at least into what looked like the usr.sbin's when I left it to come home. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:38:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 2076F14ECE for ; Tue, 18 Jan 2000 21:38:11 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA50862; Tue, 18 Jan 2000 21:37:44 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001190537.VAA50862@gndrsh.dnsmgr.net> Subject: Re: FIC SD-11 not happy with ata In-Reply-To: <20000119050322.3C3086F@pinyon.org> from "Russell L. Carter" at "Jan 18, 2000 10:03:21 pm" To: rcarter@pinyon.org (Russell L. Carter) Date: Tue, 18 Jan 2000 21:37:43 -0800 (PST) Cc: sos@freebsd.dk (Soren Schmidt), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > %It seems Russell L. Carter wrote: > %> %It seems Russell L. Carter wrote: > %> %> > %> %> I swapped out my motherboard and am seeing this now: ... > > )(*&$#%$# stupid magazine benchmarkers never actually test > things like IO... grrrrr.... We in the computer hardware business have a better name for ``FIC'', Fix It Continuously. They are not known for their quality, or should I say they are known for their lack of quality :-). -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:48:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1F68314F49 for ; Tue, 18 Jan 2000 21:48:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA09991; Tue, 18 Jan 2000 21:48:38 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA07834; Tue, 18 Jan 2000 21:48:37 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 18 Jan 2000 21:48:37 -0800 (PST) Message-Id: <200001190548.VAA07834@vashon.polstra.com> To: imp@village.org Subject: Re: breakage In-Reply-To: <200001190440.VAA21591@harmony.village.org> References: <200001190440.VAA21591@harmony.village.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001190440.VAA21591@harmony.village.org>, Warner Losh wrote: > > I did a make world Sunday and it worked. I did a makeworld today and > it was busted. Turned out to be a cvsup problem that I owe jdp a > message about. Details, please. If I had a nickel for every "CVSup problem" that turned out to be something else, I'd be a rich man today. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 21:54:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9AE2A14E5B for ; Tue, 18 Jan 2000 21:54:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA71846; Tue, 18 Jan 2000 22:54:39 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA23001; Tue, 18 Jan 2000 22:55:10 -0700 (MST) Message-Id: <200001190555.WAA23001@harmony.village.org> To: John Polstra Subject: Re: breakage Cc: current@freebsd.org In-reply-to: Your message of "Tue, 18 Jan 2000 21:48:37 PST." <200001190548.VAA07834@vashon.polstra.com> References: <200001190548.VAA07834@vashon.polstra.com> <200001190440.VAA21591@harmony.village.org> Date: Tue, 18 Jan 2000 22:55:10 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001190548.VAA07834@vashon.polstra.com> John Polstra writes: : Details, please. If I had a nickel for every "CVSup problem" that : turned out to be something else, I'd be a rich man today. I was working on that.... It was either one of two things. My cvsup file at work didn't have a delete line like I had at home: *default delete I also had the following line in my file at work: *default umask 2 (notice missing = sign). What happened was that no revisions of the gcc (and others) tree were deleted with the latest checkins there. Also the default branch was still 1 rather than 1.1.1.x, it didn't switch. Once I added the delete line and umask=2 (added the =), everything updated. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22: 1:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id BF9E814EBB; Tue, 18 Jan 2000 22:01:27 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA27188; Tue, 18 Jan 2000 22:01:22 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA17122; Tue, 18 Jan 2000 22:01:22 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id WAA24045; Tue, 18 Jan 2000 22:00:02 -0800 (PST) Message-ID: <3885542A.3BF1C292@softweyr.com> Date: Tue, 18 Jan 2000 23:05:30 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Satoshi - Ports Wraith - Asami , Kris Kennaway , "David O'Brien" , current@freebsd.org Subject: Re: Mandating USA_RESIDENT References: <200001181902.MAA18545@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message Satoshi - Ports Wraith - Asami writes: > : Won't people get into legal trouble (technically) if they build the > : wrong version? > > RESIDENT= > CITIZEN= Is there an ISO code for Mars yet? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22: 3:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 653BE1524C; Tue, 18 Jan 2000 22:03:08 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA27214; Tue, 18 Jan 2000 22:03:06 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA17165; Tue, 18 Jan 2000 22:03:05 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id WAA24120; Tue, 18 Jan 2000 22:01:45 -0800 (PST) Message-ID: <38855492.1821CC1E@softweyr.com> Date: Tue, 18 Jan 2000 23:07:14 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Warner Losh , Satoshi - Ports Wraith - Asami , "David O'Brien" , current@freebsd.org Subject: Re: Mandating USA_RESIDENT References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Tue, 18 Jan 2000, Warner Losh wrote: > > > In message Satoshi - Ports Wraith - Asami writes: > > : Won't people get into legal trouble (technically) if they build the > > : wrong version? > > > > RESIDENT= > > CITIZEN= > > What about us dual citizens? :-) CITIZEN=HL # gone to HelL in the handbasket of my choice... -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:40:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 99F1814FCA for ; Tue, 18 Jan 2000 22:40:24 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA78401; Wed, 19 Jan 2000 01:40:15 -0500 (EST) Date: Wed, 19 Jan 2000 01:40:15 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: Edwin Culp , current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-Reply-To: <200001190438.VAA21575@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Warner Losh wrote: > Also, you will likely need to add an IRQ to the pcic line in your > kernel config. The pcic driver should be smart enough to find a free IRQ; in addition pccardd shouldn't have to specify a list of IRQs to use; thats info the kernel knows about. I'm kind of curious to know if the newbus 'rewrite' leans this way. I'm a little skeptical of 'usbd', and 'pccardd' at this point; the need for userland event delivery is one thing but at this point it looks like both of them do nearly the same thing. Matching drivers to hardware is something a newbus driver should do itself; relying on an external hint mechanism strikes me as a solution prone to user aggravation. (speaking as an aggravated user of course.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:44:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8FA99150CC; Tue, 18 Jan 2000 22:44:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA33350; Wed, 19 Jan 2000 07:43:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-reply-to: Your message of "Tue, 18 Jan 2000 18:10:00 PST." Date: Wed, 19 Jan 2000 07:43:58 +0100 Message-ID: <33348.948264238@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > > >> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: >> > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 >> >> Agreed. For a PCI card all I want to know is what it is, and what IRQ it >> was assigned. A single line should be suffient. > >Do you even need to know what IRQ it was assigned? It seems to me that IRQ, >like IO-PORT, is only needed if you're either interested in such stuff or to >catch conflicts (both are under bootverbose) The IRQ is useful to me at least, since the ISA/PCI irq distribution is rather hackish and non-trivial to get right at times. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:44:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 937E91512C for ; Tue, 18 Jan 2000 22:44:52 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA72061; Tue, 18 Jan 2000 23:44:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA23508; Tue, 18 Jan 2000 23:45:21 -0700 (MST) Message-Id: <200001190645.XAA23508@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Problems with PCMCIA Cards Cc: Edwin Culp , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 01:40:15 EST." References: Date: Tue, 18 Jan 2000 23:45:21 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : The pcic driver should be smart enough to find a free IRQ; in addition : pccardd shouldn't have to specify a list of IRQs to use; thats info the : kernel knows about. Should be smart enough? How? There are a limited number of IRQs available on most laptops. There are typically no tables to look these things up in, no plug and play things to ask in modern pcs because we're using compatibility mode from the pci bridge chip. About the best one can do is allocate the irq last and hope that the first free one that is available is actually wired to the bridge chip and can be used. We can augment that with hints that have proven to be good on most laptops, but it is still a crap shoot. At least for cardbus bridges we'll be able to ask the pci bios what is available and use that. : I'm kind of curious to know if the newbus 'rewrite' leans this way. I'm a : little skeptical of 'usbd', and 'pccardd' at this point; the need for : userland event delivery is one thing but at this point it looks like both : of them do nearly the same thing. Matching drivers to hardware is : something a newbus driver should do itself; relying on an external hint : mechanism strikes me as a solution prone to user aggravation. (speaking : as an aggravated user of course.) We agree on this point completely. The only reason to have pccardd in the new world order is to provide a mechanism to run ifconfig when the card is inserted. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:51:59 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id AC8A714A2B; Tue, 18 Jan 2000 22:51:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9CB411CD634; Tue, 18 Jan 2000 22:51:58 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 18 Jan 2000 22:51:58 -0800 (PST) From: Kris Kennaway To: FreeBSD mailing list Cc: freebsd-current@freebsd.org Subject: Re: YAWF: World failure- undefined reference to `RSA_PKCS1_RSAref' In-Reply-To: <200001190514.VAA34307@mrynet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, FreeBSD mailing list wrote: > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' Please pay attention to the mailing list. I'm testing the fix for this now with a make world of both possible cases, but ppkg_delete or move aside the openssl libraries in /usr/local/lib for now. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:52:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 15E2E14F41; Tue, 18 Jan 2000 22:52:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA02062; Tue, 18 Jan 2000 22:52:44 -0800 Date: Tue, 18 Jan 2000 22:52:43 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: <33348.948264238@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The IRQ is useful to me at least, since the ISA/PCI irq distribution is > rather hackish and non-trivial to get right at times. Note that I'm not saying that IRQ is not useful - I'm just asking whether it's important to see when bootverbose == 0. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:53:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 20C4F14FF2 for ; Tue, 18 Jan 2000 22:53:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA72097; Tue, 18 Jan 2000 23:53:26 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA23572; Tue, 18 Jan 2000 23:53:58 -0700 (MST) Message-Id: <200001190653.XAA23572@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Problems with PCMCIA Cards Cc: Edwin Culp , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 01:40:15 EST." References: Date: Tue, 18 Jan 2000 23:53:58 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : pccardd shouldn't have to specify a list of IRQs to use; thats info the : kernel knows about. Oops. Missed this part. The problem again is that the kernel doesn't know about this. At least it knows it only to a point. It knows which IRQs are in use, but it doesn't know if the pcic (or cardbus bridge in compat mode) can route to a given free irq. For cardbus bridges, we can at least ask the PCI BIOS, so much relief will come there. For old pcic devices that aren't plug and play, we have almost no hope... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 22:59:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 2B7BF15166 for ; Tue, 18 Jan 2000 22:59:08 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA78701; Wed, 19 Jan 2000 01:59:04 -0500 (EST) Date: Wed, 19 Jan 2000 01:59:04 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-Reply-To: <200001190653.XAA23572@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Warner Losh wrote: > Oops. Missed this part. The problem again is that the kernel doesn't > know about this. At least it knows it only to a point. It knows > which IRQs are in use, but it doesn't know if the pcic (or cardbus > bridge in compat mode) can route to a given free irq. Ok, I'm obviously missing something here... You mean the IRQs specified in /etc/pccard.conf are a complete crapshoot? We're pulling rabbits out of a hat? Jesus. How does Windows deal with this? Can the PCIC hardware be told to generate an interrupt? Can we use this during the device probe/attach to generate a list of IRQs that the PCIC can route to? Granted this is rather ugly but we can do this last and only test free IRQs and complain when we lack free ones but we should be able to at least get the kernel to bitch and moan when it can't figure things out rather than confusing people when their ethernet cards fail to function and stuff like that. > For cardbus bridges, we can at least ask the PCI BIOS, so much relief > will come there. For old pcic devices that aren't plug and play, we > have almost no hope... -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:15:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 98BD514E36 for ; Tue, 18 Jan 2000 23:15:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA72191; Wed, 19 Jan 2000 00:15:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA23745; Wed, 19 Jan 2000 00:16:09 -0700 (MST) Message-Id: <200001190716.AAA23745@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Problems with PCMCIA Cards Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 01:59:04 EST." References: Date: Wed, 19 Jan 2000 00:16:09 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Ok, I'm obviously missing something here... You mean the IRQs specified : in /etc/pccard.conf are a complete crapshoot? Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC part. If they are, then it works great. If they aren't, then we lose bigtime. : We're pulling rabbits out : of a hat? Jesus. How does Windows deal with this? Poorly. Actually, with the new cardbus hardware, more information can be known. Enough to do our jobs. Enough for windows to not suck. Back in the bad old days before plug and pray, pcic was a black art on many machines. About the only saving grace was that pcic parts were more fully wired then. Maybe we can at least do a first order approximation by only trying IRQs that are marked as being for plug and play/PCI use. That wouldn't be that hard to implement, if the PCI BIOS interface is any good in modern -current kernels. : Can the PCIC : hardware be told to generate an interrupt? Can we use this during the : device probe/attach to generate a list of IRQs that the PCIC can route : to? No. Not really. If there is a card in the slot when we boot, we can check to see if it is cool or not. We can even defer this until after the spl is lowered (did peter ever make that change?). We can then try all the free IRQs that we can grab and see if an interrupt happens. If so, then we go ahead and add it to our list of possibilities. If not, then we don't. We should then be able to map which IRQs are available for the pcic to use. Later, we grab from this list. However, all bets are off if the card isn't inserted at boot. Hmmm, now that I'm thinking about this (and annoyed about it all at the same time), we could register a timeout by default. This timeout would poll the card until a card is there. Jump to the middle of the last paragraph and life is good, or at least less evil. This is mildly evil, but at the same time it seems clever and the right thing to do, given all the constraints. Can any of the newbus gurus comment on this plan? Oh, there are some cardbus bridges that need to have the PCI BIOS to configure them properly, or that won't even interrupt at all for the card events, so those bridges might still need to propigate hints down to the pcic/pccard layer in the kernel. Actually, for those cards, we can do a further evil hack for cards that know there should have been an interrupt but wasn't (I'm talking interrupts for the card's hardware, not interrupts for the card comings and goings). We can have an interface called something like PCCARD_IRQ_A_BAD_CALL_TRY_AGAIN, which would rebind a new IRQ to the cards interrupt routine in mid air. A corrective "I shot myself in the foot, please sir may I have another" sort of thing when it notices that timeouts happen rather than interrupts. Big nasty warnings could happen then and we'd try another IRQ until the gun goes "click click click" at which point we ignore further calls and let performance suck. : Granted this is rather ugly but we can do this last and only test : free IRQs and complain when we lack free ones but we should be able to at : least get the kernel to bitch and moan when it can't figure things out : rather than confusing people when their ethernet cards fail to function : and stuff like that. AMEN TO THAT BROTHER! I'll have to see if there is time to prototype this and the other stuff that needs to go into the pccard code before the release. I like the idea of experimenting with the oldcard for this and then using that technology on newcard. The problem is that pccardd needs to know too much about the interrupts to use. :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:15:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 310731526E for ; Tue, 18 Jan 2000 23:15:43 -0800 (PST) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 75569 invoked by uid 268); 19 Jan 2000 07:15:40 -0000 Message-ID: <20000119071540.75568.qmail@rucus.ru.ac.za> Subject: Re: Mandating USA_RESIDENT In-Reply-To: <01fa01bf61d5$7162c550$040aa8c0@local.mindstep.com> from Patrick Bihan-Faou at "Jan 18, 2000 10:26:12 am" To: Patrick Bihan-Faou Date: Wed, 19 Jan 2000 09:15:40 +0200 (SAST) Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Bihan-Faou writes : [Charset iso-8859-1 unsupported, filtering to ASCII...] > Hi, > > If we are changing the meaning of "USA_RESIDENT", could we replace it by > something else completely. I know that the USA are the center of the > universe ;-), but... > > It seems to me that a things progress, the crypto regulation gets more > complicated everyday. Why not have a "CRYPTO_COUNTRY" variable that could be > set to "USA" "FRANCE" "CANADA" or "other" based where you live and weither > special consideration must be taken relative to the crypto code ? Hmm, i would also look at something similar - rather generalise towards countries that are crypto-unfriendly (like the USA, France, etc.) g. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:20: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 72E9915270 for ; Tue, 18 Jan 2000 23:20:05 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id IAA38862; Wed, 19 Jan 2000 08:19:22 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <3885659F.29A31260@fernuni-hagen.de> Date: Wed, 19 Jan 2000 08:19:59 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: Nicolas Souchu Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: no more parallel port zip drive, atapi cdrom, soundcard on mb751 References: <3881D3DC.DA529726@fernuni-hagen.de> <20000119012635.08678@breizh.free.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hard times for the box at home and freebsd-current. there are of course some options to choose in the bios (which one would be adequate?), but before it worked without the need to tweak the bios. Btw. since this night i see the message from ata-all.c (it was too late yesterday night to do more ...) concerning my older cdrom drive: ... drive wont come ready after identify\n", ... The on board sound cards needs constantly a patch to work. I have a pcchips m751 socket 7 MB with SiS chipset (http://www.pcchips.com/m571.html) which is used a lot by friends and two times at home ... On the other side, freebsd-current shows a very good overall performance these days with the new softupdates and the fast ata-disk drivers! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:29:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 58DC314F15 for ; Tue, 18 Jan 2000 23:29:23 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA79128; Wed, 19 Jan 2000 02:29:19 -0500 (EST) Date: Wed, 19 Jan 2000 02:29:19 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-Reply-To: <200001190716.AAA23745@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Warner Losh wrote: > Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC > part. If they are, then it works great. If they aren't, then we lose > bigtime. It seems to me that any IRQ that the PCIC can see will be usable for assignment to a card no? Is there no way to hit the PCIC and tell it to issue an interrupt? Keep in mind I'm coming from a network device background here where a number of chips can be told to do this. Otherwise your timeout solution seems good. Are the valid IRQs dependent on the board integrator or on the chip used? Since we can identify the chips (well, it looks like we can) couldn't we maintain a 'quirk' table? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BF622150F3 for ; Tue, 18 Jan 2000 23:32:16 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA76172; Wed, 19 Jan 2000 08:32:12 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001190732.IAA76172@freebsd.dk> Subject: Re: ata-all.c : undefined atapi_attach() in ata_attach() In-Reply-To: <20000119021407.25113.qmail@web2102.mail.yahoo.com> from "Valentin S. Chopov" at "Jan 18, 2000 06:14:07 pm" To: valsho@yahoo.com (Valentin S. Chopov) Date: Wed, 19 Jan 2000 08:32:12 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Valentin S. Chopov wrote: > > It seems that we need #if...#endif here, maybe > something like that: > > ... > #if NATAPICD > 0 || NATAPIFD > 0 || NATAPIST > 0 > /* then the atapi devices */ > for (ctlr=0; ctlr if (!atadevices[ctlr]) continue; > if (atadevices[ctlr]->devices & > ATA_ATAPI_MASTER) > atapi_attach(atadevices[ctlr], > ATA_MASTER); > if (atadevices[ctlr]->devices & > ATA_ATAPI_SLAVE) > atapi_attach(atadevices[ctlr], ATA_SLAVE); > } > #endif fixed! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:40:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BD03A15272 for ; Tue, 18 Jan 2000 23:40:22 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA72279; Wed, 19 Jan 2000 00:40:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA23887; Wed, 19 Jan 2000 00:40:52 -0700 (MST) Message-Id: <200001190740.AAA23887@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Problems with PCMCIA Cards Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 02:29:19 EST." References: Date: Wed, 19 Jan 2000 00:40:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Otherwise your timeout solution seems good. Are the valid IRQs dependent : on the board integrator or on the chip used? Since we can identify the : chips (well, it looks like we can) couldn't we maintain a 'quirk' table? That I'm not sure of. Given the high cost of notebook machines, I have to rely on information given to be second and third hand. It has taken me a long time to understand it all, and I'm sure that there are still areas that just don't sound right are are slightly wrong. I'm not sure that a quirk table would be needed if we can find an ultra reliable way to assign the IRQs (or reassign them). And there is no way to force an interrupt, that I've found, on the i82365 chip. However, I have as a task to read the datasheets and see if I can find a better way than my timeout method. The datasheets are either long and hard to penetrate, or short in that they say they are compatible with the parts described in the long datasheets :-). The closest I've found is to apply power to the socket. I'll have to read more closely and do some experiments. I'd love to find a good solution to this problem. I'm glad your flame caught me at a time when my brain was up for trying to solve this silly problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:44:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E63B814D43 for ; Tue, 18 Jan 2000 23:44:10 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA79300; Wed, 19 Jan 2000 02:44:07 -0500 (EST) Date: Wed, 19 Jan 2000 02:44:07 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-Reply-To: <200001190740.AAA23887@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Warner Losh wrote: > I'd love to find a good solution to this problem. I'm glad your flame > caught me at a time when my brain was up for trying to solve this > silly problem. Well, I wasn't really trying to flame you, or anyone. It is frusterating to see how much time gets tied up in tracking down dodgy PCIC configs though. Solving that would probably free you up of several emails a week. If I start maintaing any more PCMCIA ethernet drivers I'm going to want the same thing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:45:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 93E9514D48 for ; Tue, 18 Jan 2000 23:45:45 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA72299; Wed, 19 Jan 2000 00:45:39 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA23948; Wed, 19 Jan 2000 00:46:11 -0700 (MST) Message-Id: <200001190746.AAA23948@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Problems with PCMCIA Cards Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 02:44:07 EST." References: Date: Wed, 19 Jan 2000 00:46:11 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Well, I wasn't really trying to flame you, or anyone. It is frusterating : to see how much time gets tied up in tracking down dodgy PCIC configs : though. Solving that would probably free you up of several emails a : week. If I start maintaing any more PCMCIA ethernet drivers I'm going to : want the same thing. I know. You were flaming the state of the universe, and it got me thinking about how to improve same. I didn't take it personally. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:51:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7E23A14A25 for ; Tue, 18 Jan 2000 23:51:36 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA76247; Wed, 19 Jan 2000 08:51:32 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001190751.IAA76247@freebsd.dk> Subject: Re: FIC SD-11 not happy with ata In-Reply-To: <20000119050322.3C3086F@pinyon.org> from "Russell L. Carter" at "Jan 18, 2000 10:03:21 pm" To: rcarter@pinyon.org (Russell L. Carter) Date: Wed, 19 Jan 2000 08:51:32 +0100 (CET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Russell L. Carter wrote: > > Hi Soren, > > I am beginning to believe that the FIC mb is the problem. My > IBM-DPTA-372050 is only half as fast (500MB bonnie) > as on the P2B (~10MB/s vs. ~19MB/s). A Jan 11 kernel > doesn't downgrade to PIO on the > IBM-DTTA-371440 as fast as this evenings -current with your > latest bits does, but eventually it gets there. Hmm, that endeed sound strange, the ICRC errors do point at HW trouble, you dont have the cables running near anything that generates a magnetic field or anything (like near the coils to the voltage regs etc), that is known to make trouble... > )(*&$#%$# stupid magazine benchmarkers never actually test > things like IO... grrrrr.... I wouldn't belive those mags, most of what they write are just rubbish, and often tainted by who bought most advertizing space that month :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 18 23:57:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C8A3B150F0 for ; Tue, 18 Jan 2000 23:57:56 -0800 (PST) (envelope-from bitsurfr@enteract.com) Received: from wildrock (207-229-172-77.d.enteract.com [207.229.172.77]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id BAA22871 for ; Wed, 19 Jan 2000 01:57:53 -0600 (CST) (envelope-from bitsurfr@enteract.com) From: "Chris Silva" To: Subject: Wish list for PCCARD Date: Wed, 19 Jan 2000 01:57:50 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would be nice if the pccard.conf.example had the D-Link DFE-650 in it! For the hell of it, I tried the DE-660, no dice :( Best regards, Chris _____________________________________________________________________ DH/DSS Fingerprint = 8265 0BB8 2C7D A376 3CCD 6858 8630 0E47 194A 0318 RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B PGP Mail encouraged / preferred - keys available on common key servers _____________________________________________________________________ Proud supporter of FreeBSD, NetBSD, and OpenBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 0:34: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 996F7150CC; Wed, 19 Jan 2000 00:33:45 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id JAA04120; Wed, 19 Jan 2000 09:33:49 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001190833.JAA04120@info.iet.unipi.it> Subject: Re: Integrated Vibra16 in -current In-Reply-To: <20000119005024.B1487@extremis.demon.co.uk> from George Cox at "Jan 19, 2000 00:50:24 am" To: George Cox Date: Wed, 19 Jan 2000 09:33:48 +0100 (CET) Cc: Jeroen Ruigrok/Asmodai , Andy Sparrow , freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes absolutely. Well done, Sir! To think I was on the point of selling my > AWE64 about 5 months ago because it didn't work under FreeBSD! pardon me but i thought at least the DSP part of the AWE64 was already supported by the 'oldpcm' driver in 3.x cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 0:50:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id A27B21515A for ; Wed, 19 Jan 2000 00:50:19 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA58573; Wed, 19 Jan 2000 10:29:20 +0200 (EET) (envelope-from ru) Date: Wed, 19 Jan 2000 10:29:20 +0200 From: Ruslan Ermilov To: Max Khon Cc: Ben Rosengart , current@FreeBSD.ORG Subject: Re: HEADS UP: grep 2.4a is now in the tree Message-ID: <20000119102920.B49712@relay.ucb.crimea.ua> Mail-Followup-To: Max Khon , Ben Rosengart , current@FreeBSD.ORG References: <20000118180444.A58470@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Max Khon on Wed, Jan 19, 2000 at 10:02:14AM +0600 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 10:02:14AM +0600, Max Khon wrote: > hi, there! > > On Tue, 18 Jan 2000, Ruslan Ermilov wrote: > > > The equivalent to the old -a option is --binary-files=without-match. > > If you want this by default, you can hardcode it in GREP_OPTIONS > > environment variable. > > I think there should be one-letter shorthand for this. > I asked GNU folks for this, but unfortunately, they don't think so. If you feel strongly, please argue on . -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 1:36:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 50D0015122 for ; Wed, 19 Jan 2000 01:36:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA75926; Wed, 19 Jan 2000 01:36:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA36853; Wed, 19 Jan 2000 01:36:43 -0800 (PST) (envelope-from obrien) Date: Wed, 19 Jan 2000 01:36:43 -0800 From: "David O'Brien" To: jasone@canonware.com Cc: current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. Message-ID: <20000119013643.A36827@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000112211625.A21988@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from eischen@vigrid.com on Thu, Jan 13, 2000 at 06:53:25AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 13, 2000 at 06:53:25AM -0500, Daniel Eischen wrote: > On Wed, 12 Jan 2000, David O'Brien wrote: > > I don't see why a plain function like mkstemp() should be written so > > specially. Couldn't all the hiding/changing done for threads be done > > w/in open() itself? Neither HP-UX 10.30 (which has kernel threads), nor > > Solaris 7 needs such open() hackery in mkstemp(). > > Given where we want to go with pthreads, and the proposed architecture, > I'm not sure why we need to have open -> _libc_open -> __open (or > whatever it is). Why isn't using _open internally in libc sufficient? > open is a weak symbol for _open, and libpthread can override the open > (weak symbol). Is this email being ignored? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 2:59:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id F105C151CC for ; Wed, 19 Jan 2000 02:59:49 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 5330 invoked by uid 1010); 19 Jan 2000 11:00:02 -0000 Date: Wed, 19 Jan 2000 11:00:02 +0000 From: George Cox To: Luigi Rizzo Cc: Jeroen Ruigrok/Asmodai , Andy Sparrow , freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Integrated Vibra16 in -current Message-ID: <20000119110002.A4862@extremis.demon.co.uk> References: <20000119005024.B1487@extremis.demon.co.uk> <200001190833.JAA04120@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <200001190833.JAA04120@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Wed, Jan 19, 2000 at 09:33:48AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19/01 09:33, Luigi Rizzo wrote: > > Yes absolutely. Well done, Sir! To think I was on the point of > > selling my AWE64 about 5 months ago because it didn't work under > > FreeBSD! > > pardon me but i thought at least the DSP part of the AWE64 was already > supported by the 'oldpcm' driver in 3.x Luigi, All I can do is apologise for my incompentence at being able to get it working. :-/ best; gjvc -- [gjvc] \\ "Expectations should not be lowered simply because \\ a product is free." -- Russ Cooper, NTBugTraq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 3:24:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 8F45115264 for ; Wed, 19 Jan 2000 03:24:24 -0800 (PST) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.3) with ESMTP id OAA24089; Wed, 19 Jan 2000 14:23:17 +0300 (MSK) (envelope-from camel@avias.com) Date: Wed, 19 Jan 2000 14:23:16 +0300 (MSK) From: Ilya Naumov To: elt@chaintech.nl Cc: europe@chaintech.com.tw, fae@chaintech.com.tw, current@freebsd.org Subject: ps/2 mouse and new 6btm bios - bug report Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dear sirs, i have uploaded a new bios (6btm0c23.bin, 1999/12/23) into Chaintech 6BTM motherboard and faced with a problem. my Genius NewScroll PS/2 mouse is not functioning under FreeBSD 4.0 OS anymore. the kernel just ignores a mouse or detects it as Generic PS/2 mouse (instead of NetMouse) accompanying this by the messages: psm0: cannot get data psm0: cannot get status anyway, the mouse does not work. the "mouse" string in kernel config is: device psm0 at atkbdc? irq 12 everything is ok with older bios (1999/05/13), but new bios is necessary for me due to coppermine support. both bios versions are suitable for Windows 2000 and NT4. sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 3:30:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 34BBF15280 for ; Wed, 19 Jan 2000 03:30:31 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup6-12.iptelecom.net.ua [212.9.227.76]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA02998; Wed, 19 Jan 2000 13:35:18 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA05741; Wed, 19 Jan 2000 13:29:47 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <3885A029.6837681B@altavista.net> Date: Wed, 19 Jan 2000 13:29:45 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Chris Silva Cc: freebsd-current@FreeBSD.ORG Subject: Re: Wish list for PCCARD References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Silva wrote: > Would be nice if the pccard.conf.example had the D-Link DFE-650 in it! > For the hell of it, I tried the DE-660, no dice :( As always with FreeBSD, all is in your hands. Carefully read pccard.conf and pccardc man pages, add your description into /etc/pccard.conf, verify it works and finally use send-pr to submit diffs between stock and your version of pccard.conf. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 5:49:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 4421B14EF5; Wed, 19 Jan 2000 05:49:15 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 8C0D42DC0A; Wed, 19 Jan 2000 14:49:05 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id C6FD67811; Wed, 19 Jan 2000 14:48:39 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id BAB4410E10; Wed, 19 Jan 2000 14:48:39 +0100 (CET) Date: Wed, 19 Jan 2000 14:48:39 +0100 (CET) From: Andrzej Bialecki To: "Matthew N. Dodd" Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Jan 2000, Matthew N. Dodd wrote: > On Wed, 19 Jan 2000, Poul-Henning Kamp wrote: > > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > > > Is this level of verbosity really helping anybody ? > > Its consistant, but I need to unify all the resource printing stuff since > theres about 5 different ways that are being used to print the stuff right > now. I'll do this after 4.0R. > > > I thought we printed out the port/mem stuff for ISA because it is > > usually jumpered by the admin, but for dynamic allocation > > busses/devices I think this should be "bootverbose" material. > > Humm... Thats possible. There was talk a while ago about making multiple > levels of verbosity in the bootup messages. I'll explore this when I fix > the line wrapping issues. > > It would really be nice if we could have busfs; this would make it much > easier to allow access to this sort of information. I did some hacks a while ago on a tool which could be called "devinfo". It simply traversed the dev/bus tree and displayed tons of info about each node. Perhaps something like that could be useful instead of full-blown FS? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 6:59:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 2F65B1528C; Wed, 19 Jan 2000 06:59:17 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id IAA58836; Wed, 19 Jan 2000 08:59:05 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 19 Jan 2000 08:59:04 -0600 (CST) From: David Scheidt To: Andrzej Bialecki Cc: "Matthew N. Dodd" , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Andrzej Bialecki wrote: > > I did some hacks a while ago on a tool which could be called "devinfo". It > simply traversed the dev/bus tree and displayed tons of info about each > node. > > Perhaps something like that could be useful instead of full-blown FS? This is something like HP-UX's ioscan(1M)? This would be very handy, even it only gave info on the hardware the kernel knows about, as opposed to actually rescanning the busses. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 7: 3:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 8E0FE14EBA for ; Wed, 19 Jan 2000 07:03:14 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-245.ix.netcom.com [209.109.235.245]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id HAA89078 for ; Wed, 19 Jan 2000 07:03:08 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id HAA04869; Wed, 19 Jan 2000 07:03:04 -0800 (PST) Date: Wed, 19 Jan 2000 07:03:04 -0800 (PST) Message-Id: <200001191503.HAA04869@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: current@freebsd.org Subject: sigisempty? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How do I test if sigset_t is empty in -current? The xview sources have this macro: #define sigisempty(s) (!(*(s))) which is ok for the old sigset_t (unsigned int) but obviously won't work for the new one since it's a struct. typedef struct __sigset { unsigned int __bits[_SIG_WORDS]; } sigset_t; Am I supposed to use a loop to iterate through the __bits and test if all of them are zero or something? Thanks, Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 7:32:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 9181614A13 for ; Wed, 19 Jan 2000 07:32:05 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id HAA02005; Wed, 19 Jan 2000 07:30:54 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id HAA12916; Wed, 19 Jan 2000 07:30:54 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id HAA17737; Wed, 19 Jan 2000 07:29:33 -0800 (PST) Message-ID: <3885D9A4.8092A0F9@softweyr.com> Date: Wed, 19 Jan 2000 08:35:00 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Warner Losh , Edwin Culp , current@freebsd.org Subject: Re: Problems with PCMCIA Cards References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > Matching drivers to hardware is > something a newbus driver should do itself; relying on an external hint > mechanism strikes me as a solution prone to user aggravation. (speaking > as an aggravated user of course.) Do you really want to cram a list of all known PCcard and USB devices into your kernel? Ugh. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 7:38:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.spacestar.net (mail2.spacestar.net [206.191.192.10]) by hub.freebsd.org (Postfix) with ESMTP id C1422152FE for ; Wed, 19 Jan 2000 07:38:42 -0800 (PST) (envelope-from d-man@telemere.net) Received: from larry.spacestar.net (larry [206.191.192.6]) by mail2.spacestar.net (Postfix) with ESMTP id 241CD8A0A for ; Wed, 19 Jan 2000 09:38:41 -0600 (CST) Received: from localhost (d-man@localhost) by larry.spacestar.net (8.9.3/8.9.3) with SMTP id JAA24056 for ; Wed, 19 Jan 2000 09:48:34 -0600 X-Authentication-Warning: larry.spacestar.net: d-man owned process doing -bs Date: Wed, 19 Jan 2000 09:48:33 -0600 (CST) From: damieon X-Sender: d-man@larry.spacestar.net To: freebsd-current@freebsd.org Subject: Neat little DPT utils... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I administer several machines running freebsd. Most of them are running FreeBSD-CURRENT, and all of them have DPT SmartRAID IV raid controlers. I was looking though LINT and found that it made reference to a set of tools for working with said cards and happily looked to install it. The tools are in /usr/src/usr.sbin/dpt. To my shock and disapointment ( ;( ) They don't compile. When I issue tha make command this is what I get: visigoth(/usr/src/usr.sbin/dpt) # make ===> dpt_ctlinfo Warning: Object directory not changed from original /usr/src/usr.sbin/dpt/dpt_ctlinfo cc -O -pipe -Wall -I/usr/src/usr.sbin/dpt/dpt_ctlinfo/../../../sys -c dpt_ctlinfo.c dpt_ctlinfo.c:43: scsi/scsi_all.h: No such file or directory dpt_ctlinfo.c:44: scsi/scsi_message.h: No such file or directory dpt_ctlinfo.c:45: scsi/scsiconf.h: No such file or directory dpt_ctlinfo.c:49: sys/dpt.h: No such file or directory dpt_ctlinfo.c: In function `main': dpt_ctlinfo.c:55: syntax error before `pass_thru' dpt_ctlinfo.c:68: `pass_thru' undeclared (first use in this function) dpt_ctlinfo.c:68: (Each undeclared identifier is reported only once dpt_ctlinfo.c:68: for each function it appears in.) dpt_ctlinfo.c:72: `DPT_CTRLINFO' undeclared (first use in this function) dpt_ctlinfo.c:73: `compat_softc' undeclared (first use in this function) dpt_ctlinfo.c:75: `DPT_IOCTL_SEND' undeclared (first use in this function) dpt_ctlinfo.c:85: `MAX_CHANNELS' undeclared (first use in this function) dpt_ctlinfo.c:95: `DPT_NO_CACHE' undeclared (first use in this function) dpt_ctlinfo.c:98: `DPT_CACHE_WRITETHROUGH' undeclared (first use in this function) dpt_ctlinfo.c:101: `DPT_CACHE_WRITEBACK' undeclared (first use in this function) dpt_ctlinfo.c:96: warning: unreachable code at beginning of switch statement *** Error code 1 Stop in /usr/src/usr.sbin/dpt/dpt_ctlinfo. *** Error code 1 Stop in /usr/src/usr.sbin/dpt. I was taking a look through the list archives, and it seems that this issue has come up before, I found that someone had decided that it was looking for depends that are in FreeBSD 2 or something. Are there plans to update these tools for -CURRENT? If not, does anyone have a way of making them work? It is really great to have RAID 5 on all your machines, but if you can't administer the card from the OS then all of my "Hot swapable" SKA stuff is in vain ;) and a large waste of money. Thanks in advance Damieon Stark Unix Systems Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 7:43:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from web1.allunix.com (17.93.ng.netgatepool.quiknet.com [207.231.93.17]) by hub.freebsd.org (Postfix) with ESMTP id 958EB15286 for ; Wed, 19 Jan 2000 07:43:33 -0800 (PST) (envelope-from davey@allunix.com) Received: from windoze (windoze.allunix.com [192.168.3.3]) by web1.allunix.com (8.9.3/8.9.3) with SMTP id IAA01277 for ; Wed, 19 Jan 2000 08:50:38 -0800 (PST) (envelope-from davey@allunix.com) Message-Id: <200001191650.IAA01277@web1.allunix.com> From: davey@allunix.com To: current@freebsd.org Date: Wed, 19 Jan 2000 07:44:19 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: X-mailer: Pegasus Mail for Win32 (v3.11) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 7:52: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from bartman.ic.sunysb.edu (bartman.ic.sunysb.edu [129.49.1.4]) by hub.freebsd.org (Postfix) with ESMTP id A35B314D42 for ; Wed, 19 Jan 2000 07:51:55 -0800 (PST) (envelope-from thsiang@ic.sunysb.edu) Received: from sparky.ic.sunysb.edu (thsiang@sparky.ic.sunysb.edu [129.49.1.3]) by bartman.ic.sunysb.edu (8.9.3/8.9.3) with ESMTP id KAA29608 for ; Wed, 19 Jan 2000 10:51:51 -0500 (EST) Received: from localhost (thsiang@localhost) by sparky.ic.sunysb.edu (8.9.3/8.9.1) with SMTP id KAA04231 for ; Wed, 19 Jan 2000 10:51:50 -0500 (EST) X-Authentication-Warning: sparky.ic.sunysb.edu: thsiang owned process doing -bs Date: Wed, 19 Jan 2000 10:51:50 -0500 (EST) From: "T. Hsiang" X-Sender: thsiang@sparky To: current@freebsd.org Subject: installworld fialed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have the same problem? ---------------------------------------------- ===> gnu/usr.bin/texinfo ===> gnu/usr.bin/texinfo/libtxi ===> gnu/usr.bin/texinfo/makeinfo install -c -s -o root -g wheel -m 555 makeinfo /usr/bin install -c -o root -g wheel -m 444 makeinfo.1.gz /usr/share/man/man1 ===> gnu/usr.bin/texinfo/info install -c -s -o root -g wheel -m 555 info /usr/bin install -c -o root -g wheel -m 444 info.1.gz /usr/share/man/man1 install -c -o root -g wheel -m 444 info.5.gz texinfo.5.gz /usr/share/man/man5 ===> gnu/usr.bin/texinfo/install-info install -c -s -o root -g wheel -m 555 install-info /usr/bin install -c -o root -g wheel -m 444 install-info.1.gz /usr/share/man/man1 ===> gnu/usr.bin/texinfo/texindex install -c -s -o root -g wheel -m 555 texindex /usr/bin install -c -o root -g wheel -m 444 texindex.1.gz /usr/share/man/man1 ===> gnu/usr.bin/texinfo/doc sflag=`grep -q ^INFO-DIR-SECTION info.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY info.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} info.info /usr/share/info/dir sflag=`grep -q ^INFO-DIR-SECTION info-stnd.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY info-stnd.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} info-stnd.info /usr/share/info/dir sflag=`grep -q ^INFO-DIR-SECTION texinfo.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY texinfo.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} texinfo.info /usr/share/info/dir install-info: menu item `makeinfo' already exists, for file `makeinfo' *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo/doc. *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8: 3:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id F1E3614FF2 for ; Wed, 19 Jan 2000 08:03:16 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id LAA02022; Wed, 19 Jan 2000 11:02:44 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3885E024.84663BDA@acm.org> Date: Wed, 19 Jan 2000 11:02:44 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "T. Hsiang" Cc: current@FreeBSD.ORG Subject: Re: installworld fialed References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I had the same problem. I simply removed /usr/share/info and ran installworld again. I don't know what you might lose if you try this, but I don't use info much so I didn't really care. Jim Bloom bloom@acm.org "T. Hsiang" wrote: > > Does anyone have the same problem? > > ---------------------------------------------- > ===> gnu/usr.bin/texinfo > ===> gnu/usr.bin/texinfo/libtxi > ===> gnu/usr.bin/texinfo/makeinfo > install -c -s -o root -g wheel -m 555 makeinfo /usr/bin > install -c -o root -g wheel -m 444 makeinfo.1.gz /usr/share/man/man1 > ===> gnu/usr.bin/texinfo/info > install -c -s -o root -g wheel -m 555 info /usr/bin > install -c -o root -g wheel -m 444 info.1.gz /usr/share/man/man1 > install -c -o root -g wheel -m 444 info.5.gz texinfo.5.gz /usr/share/man/man5 > ===> gnu/usr.bin/texinfo/install-info > install -c -s -o root -g wheel -m 555 install-info /usr/bin > install -c -o root -g wheel -m 444 install-info.1.gz /usr/share/man/man1 > ===> gnu/usr.bin/texinfo/texindex > install -c -s -o root -g wheel -m 555 texindex /usr/bin > install -c -o root -g wheel -m 444 texindex.1.gz /usr/share/man/man1 > ===> gnu/usr.bin/texinfo/doc > sflag=`grep -q ^INFO-DIR-SECTION info.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY info.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} info.info /usr/share/info/dir > sflag=`grep -q ^INFO-DIR-SECTION info-stnd.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY info-stnd.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} info-stnd.info /usr/share/info/dir > sflag=`grep -q ^INFO-DIR-SECTION texinfo.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY texinfo.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} texinfo.info /usr/share/info/dir > install-info: menu item `makeinfo' already exists, for file `makeinfo' > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/texinfo/doc. > *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:15:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 0E0CD152D0 for ; Wed, 19 Jan 2000 08:15:57 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 38559 invoked by uid 1001); 19 Jan 2000 16:14:40 -0000 Date: Wed, 19 Jan 2000 08:14:39 -0800 From: Jason Evans To: David O'Brien Cc: current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. Message-ID: <20000119081439.K27689@sturm.canonware.com> References: <20000112211625.A21988@dragon.nuxi.com> <20000119013643.A36827@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000119013643.A36827@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Jan 19, 2000 at 01:36:43AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 01:36:43AM -0800, David O'Brien wrote: > On Thu, Jan 13, 2000 at 06:53:25AM -0500, Daniel Eischen wrote: > > On Wed, 12 Jan 2000, David O'Brien wrote: > > > I don't see why a plain function like mkstemp() should be written so > > > specially. Couldn't all the hiding/changing done for threads be done > > > w/in open() itself? Neither HP-UX 10.30 (which has kernel threads), nor > > > Solaris 7 needs such open() hackery in mkstemp(). > > > > Given where we want to go with pthreads, and the proposed architecture, > > I'm not sure why we need to have open -> _libc_open -> __open (or > > whatever it is). Why isn't using _open internally in libc sufficient? > > open is a weak symbol for _open, and libpthread can override the open > > (weak symbol). > > Is this email being ignored? No, I was just busy doing other things. There is potentially one good reason to leave these changes in place for now: they allow proper thread cancellation in libc_r as it stands right now. This seems to me like a good enough reason to leave the changes as is until our grand new threads library is realized. However, I agree that in the end we will want to simplify the libc symbol naming. I'm planning on checking in libc_r cancellation changes today that use the current libc symbol naming setup. As soon as we're not using libc_r anymore I'll be glad to simplify the symbol naming. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:18:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id B5900152B8; Wed, 19 Jan 2000 08:18:34 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:RAcuuhKoSZq9IL9wY+MuOSAZZUH87okD@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id BAA00329; Thu, 20 Jan 2000 01:18:24 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id BAA01247; Thu, 20 Jan 2000 01:23:55 +0900 (JST) Message-Id: <200001191623.BAA01247@zodiac.mech.utsunomiya-u.ac.jp> To: "Jeffrey J. Libman" Cc: stable@freebsd.org, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: rpc.statd won't fire on friday's build In-reply-to: Your message of "Sun, 16 Jan 2000 07:49:58 CST." References: Date: Thu, 20 Jan 2000 01:23:54 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am experiencing the same problem on the 4.0-CURRENT system built from the source around Saturday. Another -CURRENT box, for which 'make world' was done from the source about a week ago, appears to have no problem. I suspect `portmap' is somewhat broken. In addition to `rpc.statd', `nfsd' and `mountd' are also unable to register ports. nfsd:[88]: can't register with udp portmap mountd[86]: can't register mount Kazu >no idea what i've done here. > >friday's cvsup and build...new kernel...installed on 2 systems. on one of >the systems, rpc.statd will not run, gets: > >rpc.statd: unable to register (SM_PROG, SM_VERS, udp) > >this particular system has about 50 ip's assigned to lo0...and that has >worked fine as is for months, inspite of all the verbage here about >netmasks and such. loopback IS configured. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:26:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DDAB815295 for ; Wed, 19 Jan 2000 08:26:20 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA73806; Wed, 19 Jan 2000 09:26:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA26180; Wed, 19 Jan 2000 09:26:52 -0700 (MST) Message-Id: <200001191626.JAA26180@harmony.village.org> To: Wes Peters Subject: Re: Problems with PCMCIA Cards Cc: "Matthew N. Dodd" , Edwin Culp , current@freebsd.org In-reply-to: Your message of "Wed, 19 Jan 2000 08:35:00 MST." <3885D9A4.8092A0F9@softweyr.com> References: <3885D9A4.8092A0F9@softweyr.com> Date: Wed, 19 Jan 2000 09:26:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3885D9A4.8092A0F9@softweyr.com> Wes Peters writes: : Do you really want to cram a list of all known PCcard and USB devices : into your kernel? Ugh. Do you really want to cram a list of all known pci cards into the kernel? Same thing really. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:32:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id AB897152B8 for ; Wed, 19 Jan 2000 08:32:47 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12Ay24-00020A-00; Wed, 19 Jan 2000 18:32:32 +0200 From: Sheldon Hearn To: "T. Hsiang" Cc: current@FreeBSD.ORG Subject: Re: installworld fialed In-reply-to: Your message of "Wed, 19 Jan 2000 10:51:50 EST." Date: Wed, 19 Jan 2000 18:32:32 +0200 Message-ID: <7697.948299552@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000 10:51:50 EST, "T. Hsiang" wrote: > Does anyone have the same problem? [...] > install-info: menu item `makeinfo' already exists, for file `makeinfo' > *** Error code 1 Are you getting this with rev 1.131 of src/Makefile.inc1? | revision 1.131 | date: 2000/01/18 11:00:24; author: ru; state: Exp; lines: +4 -4 | Finally resolve the texinfo issue by moving it | from the cross-tools to the bootstrap-tools. | | Requested by: bde, marcel I make and installed world successfully with this version about 15 hours ago. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:44:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24]) by hub.freebsd.org (Postfix) with ESMTP id 607C615052 for ; Wed, 19 Jan 2000 08:44:13 -0800 (PST) (envelope-from stephanb@luna.nl) Received: (from stephanb@localhost) by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id RAA08228 for current@freebsd.org; Wed, 19 Jan 2000 17:44:11 +0100 (CET) Date: Wed, 19 Jan 2000 17:44:11 +0100 From: Stephan van Beerschoten To: current@freebsd.org Subject: make world break Message-ID: <20000119174411.B8084@supra.rotterdam.luna.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -DMONOLITH -DNO_IDEA -I/mnt/archive/CVS/4.0-CURRENT/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/mnt/archive/CVS/4.0-CURRENT/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' This is going on since openssl changed its place in the sourcetree. Am I forgetting something ? (updated -CURRENT as of an hour ago). -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:44:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 6310915297; Wed, 19 Jan 2000 08:44:16 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 226B12DC0A; Wed, 19 Jan 2000 17:44:06 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 453FF7811; Wed, 19 Jan 2000 17:40:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 84BC710E10; Wed, 19 Jan 2000 17:40:35 +0100 (CET) Date: Wed, 19 Jan 2000 17:40:35 +0100 (CET) From: Andrzej Bialecki To: David Scheidt Cc: "Matthew N. Dodd" , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, David Scheidt wrote: > On Wed, 19 Jan 2000, Andrzej Bialecki wrote: > > > > > I did some hacks a while ago on a tool which could be called "devinfo". It > > simply traversed the dev/bus tree and displayed tons of info about each > > node. > > > > Perhaps something like that could be useful instead of full-blown FS? > > > This is something like HP-UX's ioscan(1M)? This would be very handy, even > it only gave info on the hardware the kernel knows about, as opposed to > actually rescanning the busses. No, the code that I wrote doesn't do re-scan. It simply displays the bus info in formatted way. I would have to dust it off and rewrite it in order for it to be usable... Or I can send you the code "as is" and you can finish it. :-) Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:55:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6BC4B1534A for ; Wed, 19 Jan 2000 08:55:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA73967; Wed, 19 Jan 2000 09:54:51 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA26506; Wed, 19 Jan 2000 09:55:28 -0700 (MST) Message-Id: <200001191655.JAA26506@harmony.village.org> To: Edwin Culp Subject: Re: Problems with PCMCIA Cards Cc: Masahide -mac- NODA , obonilla@fisicc-ufm.edu, current@FreeBSD.org In-reply-to: Your message of "Tue, 18 Jan 2000 20:33:59 PST." <38853EB6.1A4536C1@MexComUSA.net> References: <38853EB6.1A4536C1@MexComUSA.net> <3884BF85.50170456@MexComUSA.net> <20000118152304.A436@fisicc-ufm.edu> <38850925.9C27674C@MexComUSA.net> <20000119120544K.mac@clave.gr.jp> Date: Wed, 19 Jan 2000 09:55:27 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38853EB6.1A4536C1@MexComUSA.net> Edwin Culp writes: : Thanks, I would not have found it for a while. I checked UPDATING and saw nothing, : although my problem may have been because I haven't been able to finish a world : since the commit. That's an oversight on my part. Which I'm correcting right now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 8:57:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 88FC915185 for ; Wed, 19 Jan 2000 08:57:47 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA29895; Wed, 19 Jan 2000 11:57:45 -0500 (EST) (envelope-from wollman) Date: Wed, 19 Jan 2000 11:57:45 -0500 (EST) From: Garrett Wollman Message-Id: <200001191657.LAA29895@khavrinen.lcs.mit.edu> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: current@FreeBSD.ORG Subject: sigisempty? In-Reply-To: <200001191503.HAA04869@silvia.hip.berkeley.edu> References: <200001191503.HAA04869@silvia.hip.berkeley.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < How do I test if sigset_t is empty in -current? The xview sources > have this macro: > #define sigisempty(s) (!(*(s))) > which is ok for the old sigset_t (unsigned int) but obviously won't > work for the new one since it's a struct. int sigisempty(sigset_t *my_sigset) { static sigset_t empty_ss; static int emptied; if (!emptied) { sigemptyset(&empty_ss); emptied++; } return (memcmp(my_sigset, &empty_ss, sizeof empty_ss) == 0); } -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 9: 2:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CABAF152B8 for ; Wed, 19 Jan 2000 09:02:12 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA74017; Wed, 19 Jan 2000 10:02:09 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA26574; Wed, 19 Jan 2000 10:02:46 -0700 (MST) Message-Id: <200001191702.KAA26574@harmony.village.org> To: "Chris Silva" Subject: Re: Wish list for PCCARD Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 01:57:50 CST." References: Date: Wed, 19 Jan 2000 10:02:45 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Chris Silva" writes: : Would be nice if the pccard.conf.example had the D-Link DFE-650 in it! : For the hell of it, I tried the DE-660, no dice :( If you send me one, I'll add it to the list Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 9:21:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 0F311152CE; Wed, 19 Jan 2000 09:21:57 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id MAA28462; Wed, 19 Jan 2000 12:21:50 -0500 (EST) Date: Wed, 19 Jan 2000 12:21:50 -0500 (EST) From: Daniel Eischen Message-Id: <200001191721.MAA28462@pcnet1.pcnet.com> To: jasone@canonware.com, obrien@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, I was just busy doing other things. > > There is potentially one good reason to leave these changes in place for > now: they allow proper thread cancellation in libc_r as it stands right > now. This seems to me like a good enough reason to leave the changes as is > until our grand new threads library is realized. However, I agree that in > the end we will want to simplify the libc symbol naming. > > I'm planning on checking in libc_r cancellation changes today that use the > current libc symbol naming setup. As soon as we're not using libc_r > anymore I'll be glad to simplify the symbol naming. I guess I'm confused as to why you can't do what you need with _XXX (internally used, non-cancellable function) and XXX (weak reference to _XXX) within libc. libc_r would provide XXX that did something along the lines of: int XXX(void) { enter_cancellation_point(); _XXX(); leave_cancellation_point(); return(0); } Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 9:29:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id C3D2C152DD for ; Wed, 19 Jan 2000 09:29:29 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA26380; Wed, 19 Jan 2000 12:29:27 -0500 (EST) Message-ID: <20000119122927.A25745@netmonger.net> Date: Wed, 19 Jan 2000 12:29:27 -0500 From: Christopher Masto To: damieon , freebsd-current@FreeBSD.ORG Subject: Re: Neat little DPT utils... Mail-Followup-To: damieon , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from damieon on Wed, Jan 19, 2000 at 09:48:33AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 09:48:33AM -0600, damieon wrote: > I was taking a look through the list archives, and it seems that > this issue has come up before, I found that someone had decided that it > was looking for depends that are in FreeBSD 2 or something. Are there Unfortunately, we currently have a regression problem in FreeBSD. Newer releases tend to drop support for things that have no active maintainer (or a maintainer who is too worn out by continually rewriting his or her software to cope with changed interfaces). Another unfortunate side effect of this is that some developers base their work on older releases rather than chase the moving target of -current. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 9:35:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id CCEC915319 for ; Wed, 19 Jan 2000 09:34:59 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 39016 invoked by uid 1001); 19 Jan 2000 17:33:41 -0000 Date: Wed, 19 Jan 2000 09:33:41 -0800 From: Jason Evans To: Daniel Eischen Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. Message-ID: <20000119093341.M27689@sturm.canonware.com> References: <200001191721.MAA28462@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001191721.MAA28462@pcnet1.pcnet.com>; from eischen@vigrid.com on Wed, Jan 19, 2000 at 12:21:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 12:21:50PM -0500, Daniel Eischen wrote: > > No, I was just busy doing other things. > > > > There is potentially one good reason to leave these changes in place for > > now: they allow proper thread cancellation in libc_r as it stands right > > now. This seems to me like a good enough reason to leave the changes as is > > until our grand new threads library is realized. However, I agree that in > > the end we will want to simplify the libc symbol naming. > > > > I'm planning on checking in libc_r cancellation changes today that use the > > current libc symbol naming setup. As soon as we're not using libc_r > > anymore I'll be glad to simplify the symbol naming. > > I guess I'm confused as to why you can't do what you need with > _XXX (internally used, non-cancellable function) and XXX (weak > reference to _XXX) within libc. libc_r would provide XXX that > did something along the lines of: > > int > XXX(void) > { > enter_cancellation_point(); > _XXX(); > leave_cancellation_point(); > return(0); > } Doen't that method still have the problem of propagating cancellation points within the libc code? In another email I argued for the need for three names, and your response was that three names aren't needed in the context of the next-generation threads library, but it seems to me that in the case of libc_r, three names really are needed in order to do cancellation correctly. Following is a revised version of my previous email (changed to reflect libc_r rather than libpthread): It isn't adequate to only have two names with libc_r. There have to be: 1) _open() -- A name to access the actual system call. 2) _libc_open() -- A name that libc uses internally which by default is the same as _open(), but can be overridden. 3) open() -- The name that an application uses (and cancellation point). If we were to remove _libc_open() and use open() instead inside of libc, we would incorrectly propagate cancellation points (as is the case right now, since _libc_open() and open() are the same in libc_r). If we were to remove _libc_open() and use _open() instead inside of libc, then we would have the problem of some libc functions using system calls directly, where libc_r needs to do call conversion and/or extra bookkeeping work. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 9:43:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id CBBD415308 for ; Wed, 19 Jan 2000 09:43:40 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Wed, 19 Jan 2000 12:43:38 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id MAA99879 for freebsd-current@FreeBSD.ORG; Wed, 19 Jan 2000 12:43:37 -0500 (EST) (envelope-from caa) Date: Wed, 19 Jan 2000 12:43:37 -0500 From: "Charles Anderson" To: FreeBSD Current Subject: Re: make world break Message-ID: <20000119124337.D38392@midgard.dhs.org> References: <20000119174411.B8084@supra.rotterdam.luna.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000119174411.B8084@supra.rotterdam.luna.net>; from stephanb@luna.nl on Wed, Jan 19, 2000 at 05:44:11PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm blowing up in the same place, only mine is more spectacular. I get: cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DRSAref -I /usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o c rl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrs a.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_se rver.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -l crypto -L/usr/local/lib -lrsaref asn1pars.o: In function `asn1parse_main': asn1pars.o(.text+0x91): undefined reference to `BIO_s_file' asn1pars.o(.text+0x97): undefined reference to `BIO_new' asn1pars.o(.text+0xb2): undefined reference to `BIO_ctrl' asn1pars.o(.text+0xca): undefined reference to `sk_new' asn1pars.o(.text+0xeb): undefined reference to `BIO_printf' asn1pars.o(.text+0x108): undefined reference to `BIO_printf' asn1pars.o(.text+0x29f): undefined reference to `sk_push' asn1pars.o(.text+0x2d3): undefined reference to `BIO_printf' plus another 2300+ lines of undefined references. My question is why is this linking in /usr/local/lib/librsaref? That file is from 1998, and I'm sure a bit old for the new openssl stuff. -Charlie On Wed, Jan 19, 2000 at 05:44:11PM +0100, Stephan van Beerschoten wrote: > cc -O -pipe -DMONOLITH -DNO_IDEA -I/mnt/archive/CVS/4.0-CURRENT/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/mnt/archive/CVS/4.0-CURRENT/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref > speed.o: In function `speed_main': > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > > This is going on since openssl changed its place in the sourcetree. > Am I forgetting something ? (updated -CURRENT as of an hour ago). > > -Steve > > -- > Stephan van Beerschoten Email: stephanb@luna.nl > Network Engineer Luna Internet Services > PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 9:53: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 919261530C; Wed, 19 Jan 2000 09:53:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F5EA1CD61D; Wed, 19 Jan 2000 09:53:08 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 19 Jan 2000 09:53:08 -0800 (PST) From: Kris Kennaway To: Stephan van Beerschoten Cc: current@freebsd.org Subject: Re: make world break In-Reply-To: <20000119174411.B8084@supra.rotterdam.luna.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Stephan van Beerschoten wrote: > cc -O -pipe -DMONOLITH -DNO_IDEA -I/mnt/archive/CVS/4.0-CURRENT/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/mnt/archive/CVS/4.0-CURRENT/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref > speed.o: In function `speed_main': > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > > This is going on since openssl changed its place in the sourcetree. > Am I forgetting something ? (updated -CURRENT as of an hour ago). Move aside or pkg_delete your openssl port, and read the mailing lists so I don't have to explain this n times. A fix is coming, but I have to test it on 4 different cases, and the buildworlds take time. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 10: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id C3AC41530D for ; Wed, 19 Jan 2000 10:00:55 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Wed, 19 Jan 2000 13:00:52 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id NAA28538; Wed, 19 Jan 2000 13:00:51 -0500 (EST) (envelope-from caa) Date: Wed, 19 Jan 2000 13:00:51 -0500 From: "Charles Anderson" To: Charles Anderson Cc: FreeBSD Current Subject: Re: make world break Message-ID: <20000119130051.E38392@midgard.dhs.org> References: <20000119174411.B8084@supra.rotterdam.luna.net> <20000119124337.D38392@midgard.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000119124337.D38392@midgard.dhs.org>; from caa@columbus.rr.com on Wed, Jan 19, 2000 at 12:43:37PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And of course right after I post this I go back a page in my current mail folder and spot the message from Kris saying to move the old openssl out of /usr/local/lib. So I'm rebuilding again, with high hopes that it will be successful. But my last question still remains, why is it looking at anything outside of the /usr/src, /usr/obj world? -Charlie On Wed, Jan 19, 2000 at 12:43:37PM -0500, Charles Anderson wrote: > I'm blowing up in the same place, only mine is more spectacular. > > I get: > cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DRSAref -I > /usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o c > rl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrs > a.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_se > rver.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -l > crypto -L/usr/local/lib -lrsaref > asn1pars.o: In function `asn1parse_main': > asn1pars.o(.text+0x91): undefined reference to `BIO_s_file' > asn1pars.o(.text+0x97): undefined reference to `BIO_new' > asn1pars.o(.text+0xb2): undefined reference to `BIO_ctrl' > asn1pars.o(.text+0xca): undefined reference to `sk_new' > asn1pars.o(.text+0xeb): undefined reference to `BIO_printf' > asn1pars.o(.text+0x108): undefined reference to `BIO_printf' > asn1pars.o(.text+0x29f): undefined reference to `sk_push' > asn1pars.o(.text+0x2d3): undefined reference to `BIO_printf' > > plus another 2300+ lines of undefined references. > > My question is why is this linking in /usr/local/lib/librsaref? That > file is from 1998, and I'm sure a bit old for the new openssl stuff. > > -Charlie > > On Wed, Jan 19, 2000 at 05:44:11PM +0100, Stephan van Beerschoten wrote: > > cc -O -pipe -DMONOLITH -DNO_IDEA -I/mnt/archive/CVS/4.0-CURRENT/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/mnt/archive/CVS/4.0-CURRENT/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref > > speed.o: In function `speed_main': > > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > > > > This is going on since openssl changed its place in the sourcetree. > > Am I forgetting something ? (updated -CURRENT as of an hour ago). > > > > -Steve > > > > -- > > Stephan van Beerschoten Email: stephanb@luna.nl > > Network Engineer Luna Internet Services > > PGP fingerprint 4557 9761 B212 FB4C 778D 3529 C42A 2D27 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Charles Anderson caa@columbus.rr.com > > No quote, no nothin' > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 10: 3:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 1D81A15312 for ; Wed, 19 Jan 2000 10:03:24 -0800 (PST) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id MAA14449; Wed, 19 Jan 2000 12:03:19 -0600 (CST) Message-Id: <200001191803.MAA14449@chiba.3jane.net> To: Stephan van Beerschoten Cc: current@FreeBSD.ORG Subject: Re: make world break In-reply-to: <20000119174411.B8084@supra.rotterdam.luna.net> References: <20000119174411.B8084@supra.rotterdam.luna.net> Comments: In-reply-to Stephan van Beerschoten message dated "Wed, 19 Jan 2000 17:44:11 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14446.948304999.1@chiba.3jane.net> Date: Wed, 19 Jan 2000 12:03:19 -0600 From: "Damon M. Conway" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephan van Beerschoten wrote: >cc -O -pipe -DMONOLITH -DNO_IDEA -I/mnt/archive/CVS/4.0-CURRENT/src/secure/usr.bin/opens sl -DRSAref -I/usr/obj/mnt/archive/CVS/4.0-CURRENT/src/i386/usr/include -o openssl app s.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_ client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lss l -lcrypto -L/usr/local/lib -lrsaref >speed.o: In function `speed_main': >speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' > >This is going on since openssl changed its place in the sourcetree. >Am I forgetting something ? (updated -CURRENT as of an hour ago). > i'll answer for kris...it's a known issue and kris is working on fixing it. "it's a known problem which I hope to fix tonight - pkg_delete or move aside your openssl installation (e.g. /usr/local/lib/lib{crypto,ssl}.*). Kris" damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 10:10: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 473D914FE6; Wed, 19 Jan 2000 10:10:00 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA05871; Wed, 19 Jan 2000 13:09:52 -0500 (EST) Date: Wed, 19 Jan 2000 13:09:52 -0500 (EST) From: Daniel Eischen To: Jason Evans Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: <20000119093341.M27689@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Jason Evans wrote: > On Wed, Jan 19, 2000 at 12:21:50PM -0500, Daniel Eischen wrote: > > I guess I'm confused as to why you can't do what you need with > > _XXX (internally used, non-cancellable function) and XXX (weak > > reference to _XXX) within libc. libc_r would provide XXX that > > did something along the lines of: > > > > int > > XXX(void) > > { > > enter_cancellation_point(); > > _XXX(); > > leave_cancellation_point(); > > return(0); > > } > > Doen't that method still have the problem of propagating cancellation > points within the libc code? In another email I argued for the need for > three names, and your response was that three names aren't needed in the > context of the next-generation threads library, but it seems to me that in > the case of libc_r, three names really are needed in order to do > cancellation correctly. Following is a revised version of my previous > email (changed to reflect libc_r rather than libpthread): > > It isn't adequate to only have two names with libc_r. There have to be: > > 1) _open() -- A name to access the actual system call. > > 2) _libc_open() -- A name that libc uses internally which by default is the > same as _open(), but can be overridden. > > 3) open() -- The name that an application uses (and cancellation point). > > If we were to remove _libc_open() and use open() instead inside of libc, we > would incorrectly propagate cancellation points (as is the case right now, > since _libc_open() and open() are the same in libc_r). > > If we were to remove _libc_open() and use _open() instead inside of libc, > then we would have the problem of some libc functions using system calls > directly, where libc_r needs to do call conversion and/or extra bookkeeping > work. Well, before all blocking system calls were renamed to _thread_sys_XXX(), so that the threads library could perform the call conversion. You'd have to revert back to this method, and have libc_r provide routines XXX (which are cancellable, and call _XXX), and _XXX (which does any necessary call conversion/bookkeeping, perhaps calling _thread_sys_XXX). Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 11:12:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 751851539A for ; Wed, 19 Jan 2000 11:12:28 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id LAA00792; Wed, 19 Jan 2000 11:11:30 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <38860C5F.B90A44DD@MexComUSA.net> Date: Wed, 19 Jan 2000 11:11:28 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Masahide -mac- NODA , obonilla@fisicc-ufm.edu, current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards References: <38853EB6.1A4536C1@MexComUSA.net> <3884BF85.50170456@MexComUSA.net> <20000118152304.A436@fisicc-ufm.edu> <38850925.9C27674C@MexComUSA.net> <20000119120544K.mac@clave.gr.jp> <200001191655.JAA26506@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <38853EB6.1A4536C1@MexComUSA.net> Edwin Culp writes: > : Thanks, I would not have found it for a while. I checked UPDATING and saw nothing, > : although my problem may have been because I haven't been able to finish a world > : since the commit. > > That's an oversight on my part. Which I'm correcting right now. > > Warner Thanks. It just caught me off guard:-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 11:39:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 41DF31537C for ; Wed, 19 Jan 2000 11:39:06 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id VAA08022; Wed, 19 Jan 2000 21:38:04 +0200 (EET) (envelope-from ru) Date: Wed, 19 Jan 2000 21:38:04 +0200 From: Ruslan Ermilov To: "T. Hsiang" , Jim Bloom , Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: installworld fialed Message-ID: <20000119213804.B4702@relay.ucb.crimea.ua> Mail-Followup-To: "T. Hsiang" , Jim Bloom , Sheldon Hearn , current@FreeBSD.ORG References: <7697.948299552@axl.noc.iafrica.com> <3885E024.84663BDA@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from T. Hsiang on Wed, Jan 19, 2000 at 10:51:50AM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 10:51:50AM -0500, T. Hsiang wrote: > Does anyone have the same problem? > > ---------------------------------------------- > ===> gnu/usr.bin/texinfo/doc > sflag=`grep -q ^INFO-DIR-SECTION info.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY info.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} info.info /usr/share/info/dir > sflag=`grep -q ^INFO-DIR-SECTION info-stnd.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY info-stnd.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} info-stnd.info /usr/share/info/dir > sflag=`grep -q ^INFO-DIR-SECTION texinfo.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY texinfo.info || echo 1`; install-info ${sflag:+--section=Miscellaneous} ${eflag:+--entry=} texinfo.info /usr/share/info/dir > install-info: menu item `makeinfo' already exists, for file `makeinfo' > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/texinfo/doc. > *** Error code 1 On Wed, Jan 19, 2000 at 11:02:44AM -0500, Jim Bloom wrote: > Yes, I had the same problem. I simply removed /usr/share/info and ran > installworld again. I don't know what you might lose if you try this, > but I don't use info much so I didn't really care. > On Wed, Jan 19, 2000 at 06:32:32PM +0200, Sheldon Hearn wrote: > > Are you getting this with rev 1.131 of src/Makefile.inc1? > > I make and installed world successfully with this version about 15 hours > ago. > The problem is that new install-info(1) will (correctly) refuse to install file FOO with BAR entry if BAR entry already exists for another file FOO2 in /usr/share/info/dir file. In this particular case, the problem is observed because till 1999/01/15 we had src/contrib/texinfo/makeinfo/makeinfo.texi (with entry=makeinfo, file=makeinfo), and starting from that date we have src/contrib/texinfo/doc/texinfo.txi with entry=makeinfo, file=texinfo. The correct fix will be to re-initialize ${DESTDIR}/usr/share/info/dir at the early stage of installworld. I've just committed the fix (src/share/Makefile, src/share/info/Makefile). -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 11:40: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 84768153F1 for ; Wed, 19 Jan 2000 11:39:38 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id UAA24656; Wed, 19 Jan 2000 20:39:37 +0100 (CET) (envelope-from olli) Date: Wed, 19 Jan 2000 20:39:37 +0100 (CET) Message-Id: <200001191939.UAA24656@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-questions@FreeBSD.ORG Subject: Re: shell problem X-Newsgroups: list.freebsd-current In-Reply-To: <8630o4$20re$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mouss wrote in list.freebsd-current: >> Install bash (either from ports or a package). > > and before you ask why you cannot ftp to your machine, do not forget to add > the path above to /etc/shells. The FreeBSD port/package will do that automagically. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 12:24:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 2E29214F49; Wed, 19 Jan 2000 12:24:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA05862; Tue, 18 Jan 2000 18:27:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001190227.SAA05862@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: boot messages for pci devices... In-reply-to: Your message of "Tue, 18 Jan 2000 18:03:01 PST." <20000118180301.A34556@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jan 2000 18:27:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: > > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it > was assigned. A single line should be suffient. The IRQ number is actually pretty redundant as well. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 12:52:38 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1BDF514ED0; Wed, 19 Jan 2000 12:52:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C96D1CD41C; Wed, 19 Jan 2000 12:52:21 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 19 Jan 2000 12:52:21 -0800 (PST) From: Kris Kennaway To: Charles Anderson Cc: FreeBSD Current Subject: Re: make world break In-Reply-To: <20000119130051.E38392@midgard.dhs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Charles Anderson wrote: > be successful. But my last question still remains, why is it looking at > anything outside of the /usr/src, /usr/obj world? It was supposed to just pick up the rsaref library so you can use RSA crypto in openssl, but was also picking up the stale libcrypto.so in /usr/local/lib due to the -L path. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 13:26:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from Voyager.ghb.fh-furtwangen.de (Voyager.GHB.FH-Furtwangen.DE [141.28.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 331D515314 for ; Wed, 19 Jan 2000 13:26:08 -0800 (PST) (envelope-from morrow@DreamWorld.ghb.fh-furtwangen.de) Received: from DreamWorld.ghb.fh-furtwangen.de (root@DreamWorld.ghb.fh-furtwangen.de [141.28.228.98]) by Voyager.ghb.fh-furtwangen.de (8.9.3/8.9.3/ghb) with ESMTP id WAA21879 for ; Wed, 19 Jan 2000 22:37:09 +0100 Received: (from morrow@localhost) by DreamWorld.ghb.fh-furtwangen.de (8.9.3/8.9.3) id WAA13515; Wed, 19 Jan 2000 22:26:05 +0100 (CET) (envelope-from morrow) Date: Wed, 19 Jan 2000 22:26:05 +0100 (CET) From: Adrian Woizik To: current@FreeBSD.ORG Subject: Problems compiling current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Sorry this is the wrong ml for this question but i didn't find anything better for it. I Downloaded the current src tree today but the buildworld hangs on the KerborosIV lib In file included from /usr/src2/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:74, from /usr/src2/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src2/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro name In file included from /usr/src2/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:77, from /usr/src2/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30: /usr/obj/usr/src2/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: `ERROR_TABLE_BASE_' redefined /usr/obj/usr/src2/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this is the location of the previous definition System is FreeBSD 3.4-STABLE on i386 hope that theres anybody who can help mit with that. Thx Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 13:27:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id EAD9E152D3 for ; Wed, 19 Jan 2000 13:27:24 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 1672 invoked from network); 19 Jan 2000 21:27:20 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 19 Jan 2000 21:27:20 -0000 Date: Thu, 20 Jan 2000 08:27:18 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Garrett Wollman Cc: Satoshi Asami , current@FreeBSD.ORG Subject: Re: sigisempty? In-Reply-To: <200001191657.LAA29895@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Garrett Wollman wrote: > < > > How do I test if sigset_t is empty in -current? The xview sources > > have this macro: > > int > sigisempty(sigset_t *my_sigset) > { > static sigset_t empty_ss; > static int emptied; > > if (!emptied) { > sigemptyset(&empty_ss); > emptied++; > } > > return (memcmp(my_sigset, &empty_ss, sizeof empty_ss) == 0); > } You should know better than to compare structs for equality. Even the implementation can't do this in a machine-independent way. The current implementation can do it machine-independently by comparing each element of the __bits[] struct member with 0. The correct answer seems to be "you can't do that" :-). Even checking all signals from 1 to the maximum signal number is difficult because the maximum signal number is difficult to determine and it may be INT_MAX. rcs has fought with variations of this problem. It now uses the following method: keep track of the largest signal number of interest for the current operation, and check all signals from that signal number down to 1. See rcs/lib/rcsutil.c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 13:36:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from Voyager.ghb.fh-furtwangen.de (Voyager.GHB.FH-Furtwangen.DE [141.28.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 9768914DFA for ; Wed, 19 Jan 2000 13:36:23 -0800 (PST) (envelope-from morrow@DreamWorld.ghb.fh-furtwangen.de) Received: from DreamWorld.ghb.fh-furtwangen.de (root@DreamWorld.ghb.fh-furtwangen.de [141.28.228.98]) by Voyager.ghb.fh-furtwangen.de (8.9.3/8.9.3/ghb) with ESMTP id WAA22110 for ; Wed, 19 Jan 2000 22:47:22 +0100 Received: (from morrow@localhost) by DreamWorld.ghb.fh-furtwangen.de (8.9.3/8.9.3) id WAA13569; Wed, 19 Jan 2000 22:36:19 +0100 (CET) (envelope-from morrow) Date: Wed, 19 Jan 2000 22:36:18 +0100 (CET) From: Adrian Woizik To: current@FreeBSD.ORG Subject: Solved was: Problems compiling current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry... problem solved Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 14:24: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id 32D2F14E34 for ; Wed, 19 Jan 2000 14:23:56 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Wed, 19 Jan 2000 17:23:46 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id RAA25440; Wed, 19 Jan 2000 17:23:41 -0500 (EST) (envelope-from caa) Date: Wed, 19 Jan 2000 17:23:41 -0500 From: "Charles Anderson" To: Kris Kennaway Cc: Charles Anderson , FreeBSD Current Subject: Re: make world break Message-ID: <20000119172341.A70456@midgard.dhs.org> References: <20000119130051.E38392@midgard.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Wed, Jan 19, 2000 at 12:52:21PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 12:52:21PM -0800, Kris Kennaway wrote: > On Wed, 19 Jan 2000, Charles Anderson wrote: > > > be successful. But my last question still remains, why is it looking at > > anything outside of the /usr/src, /usr/obj world? > > It was supposed to just pick up the rsaref library so you can use RSA > crypto in openssl, but was also picking up the stale libcrypto.so in > /usr/local/lib due to the -L path. Ahhh, I see to get around that can't include RSA code in the source tree bit. Makes perfect sense now, thank you. -Charlie -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 14:38:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from newmail.netbistro.com (newmail.netbistro.com [204.239.167.35]) by hub.freebsd.org (Postfix) with SMTP id 41F7414C4B for ; Wed, 19 Jan 2000 14:38:42 -0800 (PST) (envelope-from jon@netbistro.com) Received: (qmail 18463 invoked by uid 1020); 19 Jan 2000 22:38:26 -0000 Date: Wed, 19 Jan 2000 14:38:21 -0800 (PST) From: Jon Simola X-Sender: jon@newmail.netbistro.com To: damieon Cc: freebsd-current@freebsd.org Subject: Re: Neat little DPT utils... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, damieon wrote: > I administer several machines running freebsd. Most of > them are running FreeBSD-CURRENT, and all of them have DPT SmartRAID IV > raid controlers. I've got a backup server here with a DPT SmartRAID IV (PM3334UW) running 3.3-STABLE from Nov 17. About 15 minutes of playing and I've got the programs compiling cleanly, however: root@tyberius:/usr/src/usr.sbin/dpt/dpt_ctlinfo$ ./dpt_ctlinfo ./dpt_ctlinfo ERROR: Failed to open "(null)" - Bad address Looking at the code some more, I see: if ( (fd = open(argv[1], O_RDWR, S_IRUSR | S_IWUSR)) == -1 ) { (void)fprintf(stderr, "%s ERROR: Failed to open \"%s\" - %s\n", argv[0], argv[1], strerror(errno)); exit(1); } So, I'm stuck with a compiling program and I don't know what it wants as an argument. Anything I try give me an: root@tyberius:/usr/src/usr.sbin/dpt/dpt_ctlinfo$ ./dpt_ctlinfo /dev/da0 ./dpt_ctlinfo ERROR: Failed to send IOCTL c0444403 - Inappropriate ioctl for device I'll be looking into this some more over the next couple days, but any hints or suggestions are more than welcome. If I can get it running in this 3.3-STABLE server, then I'll steal the controller for a weekend and bang out some -CURRENT code, although I think the necessary changes (STABLE -> CURRENT) should be fairly minor. --- Jon Simola | "In the near future - corporate networks Systems Administrator | reach out to the stars, electrons and light ABC Communications | flow throughout the universe." -- GITS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 14:48: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 0AE18151C2 for ; Wed, 19 Jan 2000 14:47:52 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA12047; Wed, 19 Jan 2000 14:46:36 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA18762; Wed, 19 Jan 2000 14:46:27 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA11586; Wed, 19 Jan 2000 14:45:16 -0800 (PST) Message-ID: <38863FC9.7B66BD3C@softweyr.com> Date: Wed, 19 Jan 2000 15:50:49 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: "Matthew N. Dodd" , Edwin Culp , current@freebsd.org Subject: Re: Problems with PCMCIA Cards References: <3885D9A4.8092A0F9@softweyr.com> <200001191626.JAA26180@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3885D9A4.8092A0F9@softweyr.com> Wes Peters writes: > : Do you really want to cram a list of all known PCcard and USB devices > : into your kernel? Ugh. > > Do you really want to cram a list of all known pci cards into the > kernel? Same thing really. Mmm... Good point. This means updating code and compiling a new kernel every time Joe's hardware company sticks their own name on a generic OEM PCI or PCCard, doesn't it? I love this industry. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 14:52:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 20F35151C2 for ; Wed, 19 Jan 2000 14:52:25 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA89362; Wed, 19 Jan 2000 17:51:32 -0500 (EST) Date: Wed, 19 Jan 2000 17:51:32 -0500 (EST) From: "Matthew N. Dodd" To: Wes Peters Cc: Warner Losh , Edwin Culp , current@freebsd.org Subject: Re: Problems with PCMCIA Cards In-Reply-To: <38863FC9.7B66BD3C@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Wes Peters wrote: > Mmm... Good point. This means updating code and compiling a new > kernel every time Joe's hardware company sticks their own name on a > generic OEM PCI or PCCard, doesn't it? I love this industry. Too many drivers require knowledge of specific cards in order to properly handle 'quirks'. This isn't going to change. While a recompile is annoying we can be assured that a driver maintainer will only add IDs to a driver after they have been confirmed to work. With PCCARD, one has to contend with a certain amount of user fiddling in order to make things work; this appears to be a source of support load. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 15:13:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 100DE14F02 for ; Wed, 19 Jan 2000 15:13:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA75574; Wed, 19 Jan 2000 16:13:06 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA29780; Wed, 19 Jan 2000 16:13:46 -0700 (MST) Message-Id: <200001192313.QAA29780@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Problems with PCMCIA Cards Cc: Wes Peters , Edwin Culp , current@freebsd.org In-reply-to: Your message of "Wed, 19 Jan 2000 17:51:32 EST." References: Date: Wed, 19 Jan 2000 16:13:46 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Too many drivers require knowledge of specific cards in order to properly : handle 'quirks'. This isn't going to change. While a recompile is : annoying we can be assured that a driver maintainer will only add IDs to a : driver after they have been confirmed to work. With PCCARD, one has to : contend with a certain amount of user fiddling in order to make things : work; this appears to be a source of support load. Well, it isn't as bad as it could be. pccard sometimes include a Function ID which can be used to generically attach to a card. This will work well for modems, but unlikely well for something else. Also, the OEM stuff sometimes are sloppy in that they don't always change the IDs, but do change the CIS string... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 15:41:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from flashmail.com (flashmail.com [207.173.216.240]) by hub.freebsd.org (Postfix) with SMTP id DD9481520C for ; Wed, 19 Jan 2000 15:41:08 -0800 (PST) (envelope-from kingdavid@jab.nu) Received: from haas ([152.207.73.177]) by flashmail.com ; Wed, 19 Jan 2000 15:43:43 -0800 Message-ID: <000801bf62d6$5d081f40$09454545@haas> From: "King David" To: Subject: Date: Wed, 19 Jan 2000 18:38:57 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BF62AC.71C69580" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF62AC.71C69580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0005_01BF62AC.71C69580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0005_01BF62AC.71C69580-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 15:42: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from flashmail.com (flashmail.com [207.173.216.240]) by hub.freebsd.org (Postfix) with SMTP id D175E14D90 for ; Wed, 19 Jan 2000 15:42:00 -0800 (PST) (envelope-from kingdavid@jab.nu) Received: from haas ([152.207.73.177]) by flashmail.com ; Wed, 19 Jan 2000 15:44:38 -0800 Message-ID: <001001bf62d6$7d611120$09454545@haas> From: "King David" To: Subject: subscribe freebsd-current Date: Wed, 19 Jan 2000 18:39:52 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01BF62AC.928BDDC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01BF62AC.928BDDC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe freebsd-current ------=_NextPart_000_000D_01BF62AC.928BDDC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe=20 freebsd-current
------=_NextPart_000_000D_01BF62AC.928BDDC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 15:46:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 1312115341 for ; Wed, 19 Jan 2000 15:46:07 -0800 (PST) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id AAA14011; Thu, 20 Jan 2000 00:45:51 +0100 (CET) (envelope-from tobez) Date: Thu, 20 Jan 2000 00:45:51 +0100 From: Anton Berezin To: Satoshi Asami Cc: current@FreeBSD.ORG Subject: Re: sigisempty? Message-ID: <20000120004551.A13892@plab.ku.dk> References: <200001191503.HAA04869@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001191503.HAA04869@silvia.hip.berkeley.edu>; from asami@cs.berkeley.edu on Wed, Jan 19, 2000 at 07:03:04AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 07:03:04AM -0800, Satoshi Asami wrote: > How do I test if sigset_t is empty in -current? The xview sources > have this macro: > > #define sigisempty(s) (!(*(s))) > > which is ok for the old sigset_t (unsigned int) but obviously won't > work for the new one since it's a struct. The very same file nfty.h already has a hack for SVR4: #ifdef SVR4 #define sigisempty(s) (!(((s)->__sigbits[0]) | ((s)->__sigbits[1]) \ | ((s)->__sigbits[2]) | ((s)->__sigbits[3]))) When I compiled xview on a -current machine I just did it the very same hacky way: #define sigisempty(s) (!(((s)->__bits[0]) | ((s)->__bits[1]) \ | ((s)->__bits[2]) | ((s)->__bits[3]))) Of course, the #if for FreeBSD and its version is necessary. Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 16:13:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 64AA514D42 for ; Wed, 19 Jan 2000 16:13:20 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 1980 invoked by uid 1000); 20 Jan 2000 00:13:37 -0000 Date: Thu, 20 Jan 2000 01:13:36 +0100 From: Andreas Braukmann To: freebsd-current@freebsd.org Subject: Filesystem crash / no softupdates / jail running ... Message-ID: <20000120011336.C1478@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, ... I had a major filesystem crash just a few minutes ago. The crash was so heavy, that I first had to think about a hardware-failure. But I didn't found anything in the logfiles. The story: Yesterday I began to play around with an experimentail jail-based virtual server setup. The 'jail world' was located under /scratch/jails/zappa/. 'inetd', 'telnetd', a 'sh' were running jailed. It sees to run rather well. Today I changed my working directory (running a regular, non-jailed shell) to /scratch and found the directory empty. 'What the hell is going on here?' I thought ran a 'ps' just to find the jailed processes running happily. I did a telnet to the virtual server, was able to login successfully and found a apparently intact filesystem. ... and then.. ... and then ... the screen froze and a few seconds later the machines rebooted silently. No tracks in the logs. Sorry, I was running X and currently have no serial console available. Therefor I just can't tell, if it was really a silent reboot or a 'not-seen' panic. The filesystem was totally hosed. 'fsck' spat out masses of 'unknown file type', 'partially allocated inode', 'incorrect block count' (with rather large discrepancies) and 'excessive bad blks' messages. Partially transcripts of 'fsck -y '-logs are available on request. System: K7/700, 256MB, sym0, fxp0 Disk: > The disk contained a ca. 9GB filesystem (default newfs) mounted without any special options (on /scratch). FreeBSD xxx.xxx.xxxx.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Jan 5 14:30:28 CET 2000 I have soft-updates compiled in but deactivated on all filesystems. Regards, Andreas ... sorry, ... my written English is rather ugly ... -- Andreas Braukmann - irgendwer@internet-adresse.de - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 16:28: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9A4F315345 for ; Wed, 19 Jan 2000 16:27:44 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA13551; Thu, 20 Jan 2000 10:56:03 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001191626.JAA26180@harmony.village.org> Date: Thu, 20 Jan 2000 10:56:02 +1030 (CST) From: "Daniel O'Connor" To: Warner Losh Subject: Re: Problems with PCMCIA Cards Cc: current@freebsd.org, Edwin Culp , "Matthew N. Dodd" , Wes Peters Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Jan-00 Warner Losh wrote: > In message <3885D9A4.8092A0F9@softweyr.com> Wes Peters writes: > : Do you really want to cram a list of all known PCcard and USB > : devices > : into your kernel? Ugh. > Do you really want to cram a list of all known pci cards into the > kernel? Same thing really. So a daemon is needed to load the right device driver when the kernel detects a new card being inserted... --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 16:28:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id A7CAB15141 for ; Wed, 19 Jan 2000 16:28:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA04198; Wed, 19 Jan 2000 16:35:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001200035.QAA04198@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: "Matthew N. Dodd" , Edwin Culp , current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-reply-to: Your message of "Tue, 18 Jan 2000 23:53:58 MST." <200001190653.XAA23572@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jan 2000 16:35:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message "Matthew N. Dodd" writes: > : pccardd shouldn't have to specify a list of IRQs to use; thats info the > : kernel knows about. > > Oops. Missed this part. The problem again is that the kernel doesn't > know about this. At least it knows it only to a point. It knows > which IRQs are in use, but it doesn't know if the pcic (or cardbus > bridge in compat mode) can route to a given free irq. It can make a pretty good guess though; certainly good enough in most cases. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 16:39:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 91F0014D90; Wed, 19 Jan 2000 16:39:34 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA76024; Wed, 19 Jan 2000 17:39:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA30588; Wed, 19 Jan 2000 17:40:12 -0700 (MST) Message-Id: <200001200040.RAA30588@harmony.village.org> To: Mike Smith Subject: Re: Problems with PCMCIA Cards Cc: "Matthew N. Dodd" , Edwin Culp , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 16:35:26 PST." <200001200035.QAA04198@mass.cdrom.com> References: <200001200035.QAA04198@mass.cdrom.com> Date: Wed, 19 Jan 2000 17:40:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001200035.QAA04198@mass.cdrom.com> Mike Smith writes: : It can make a pretty good guess though; certainly good enough in most : cases. The problem with guesses is that they are guesses and often wrong. Consider a simple case. If I don't have a sound driver configured on my laptop, IRQ 5 could appear to be free. However, IRQ 5 rarely works for pccard card interrupts in modern laptops. PNPBIOS would help that, but w/o PNPBIOS the kernel could easily be fooled. This is a common case if my helping people with their pccard.conf is any example. If was easy, we'd be doing it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 17:10:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id E313815254 for ; Wed, 19 Jan 2000 17:10:14 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id F15A01C4A; Wed, 19 Jan 2000 20:10:08 -0500 (EST) Date: Wed, 19 Jan 2000 20:10:08 -0500 From: Bill Fumerola To: Wes Peters Cc: Warner Losh , "Matthew N. Dodd" , Edwin Culp , current@freebsd.org Subject: Re: Problems with PCMCIA Cards Message-ID: <20000119201008.D33989@jade.chc-chimes.com> References: <3885D9A4.8092A0F9@softweyr.com> <200001191626.JAA26180@harmony.village.org> <38863FC9.7B66BD3C@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38863FC9.7B66BD3C@softweyr.com>; from wes@softweyr.com on Wed, Jan 19, 2000 at 03:50:49PM -0700 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 03:50:49PM -0700, Wes Peters wrote: > Mmm... Good point. This means updating code and compiling a new kernel > every time Joe's hardware company sticks their own name on a generic OEM > PCI or PCCard, doesn't it? I love this industry. Do the above and try and figure out and track down if the marketing information matches what actually shows up on the product, now find out if it works exactly the same or if there is some stupid quirk that Joe's Hardware added to the chip.... Welcome to Bill Paul's hell. :-> -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 17:51:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id BBC42150D5 for ; Wed, 19 Jan 2000 17:51:06 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 100ADA5; Wed, 19 Jan 2000 20:51:05 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: Christopher Masto , current@freebsd.org Subject: Re: Neat little DPT utils... Date: Wed, 19 Jan 2000 20:48:38 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20000119122927.A25745@netmonger.net> In-Reply-To: <20000119122927.A25745@netmonger.net> MIME-Version: 1.0 Message-Id: <00011920510403.00537@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, you wrote: > Unfortunately, we currently have a regression problem in FreeBSD. > Newer releases tend to drop support for things that have no active > maintainer (or a maintainer who is too worn out by continually > rewriting his or her software to cope with changed interfaces). > Another unfortunate side effect of this is that some developers base > their work on older releases rather than chase the moving target of > -current. If thats the case, then FreeBSD should stop changing :). Rather, with the capabilities of NewBus and the module system could it not be organized in such a way that the interface the driver requires is loaded along with the driver itself? Perhaps older interfaces just call the functions of the new interfaces. Give them a 1 or 2 year grace period to convert over before dropping them cold. (Thats 1 year in -stable, and 1 year of -current). -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 17:56:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id C3B4B14D4C for ; Wed, 19 Jan 2000 17:56:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id RAA02097; Wed, 19 Jan 2000 17:56:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001200156.RAA02097@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: rod@zort.on.ca Cc: Christopher Masto , current@FreeBSD.ORG Subject: Re: Neat little DPT utils... In-reply-to: Your message of "Wed, 19 Jan 2000 20:48:38 EST." <00011920510403.00537@rbtBSD.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jan 2000 17:56:11 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 19 Jan 2000, you wrote: > > Unfortunately, we currently have a regression problem in FreeBSD. > > Newer releases tend to drop support for things that have no active > > maintainer (or a maintainer who is too worn out by continually > > rewriting his or her software to cope with changed interfaces). > > Another unfortunate side effect of this is that some developers base > > their work on older releases rather than chase the moving target of > > -current. > > If thats the case, then FreeBSD should stop changing :). > > Rather, with the capabilities of NewBus and the module system could it not be > organized in such a way that the interface the driver requires is loaded along > with the driver itself? Perhaps older interfaces just call the functions of > the new interfaces. Give them a 1 or 2 year grace period to convert over > before dropping them cold. (Thats 1 year in -stable, and 1 year of -current). > My strategy in the past has been to develop kernel stuff for -current . The interfaces to device drivers or modules is usually a very tiny part of the driver or module. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 18:21: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 9393714F9C for ; Wed, 19 Jan 2000 18:21:05 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:XFrsiIJXDUWkax5C9VoKNZO/2XrsYOvu@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id LAA01674; Thu, 20 Jan 2000 11:20:39 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA10863; Thu, 20 Jan 2000 11:26:10 +0900 (JST) Message-Id: <200001200226.LAA10863@zodiac.mech.utsunomiya-u.ac.jp> To: Ilya Naumov Cc: elt@chaintech.nl, europe@chaintech.com.tw, fae@chaintech.com.tw, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: ps/2 mouse and new 6btm bios - bug report In-reply-to: Your message of "Wed, 19 Jan 2000 14:23:16 +0300." References: Date: Thu, 20 Jan 2000 11:26:09 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >i have uploaded a new bios (6btm0c23.bin, 1999/12/23) into Chaintech 6BTM >motherboard and faced with a problem. my Genius NewScroll PS/2 mouse is ~~~~~~~~~ NetScroll? >not functioning under FreeBSD 4.0 OS anymore. the kernel just ignores a >mouse or detects it as Generic PS/2 mouse (instead of >NetMouse) accompanying this by the messages: > >psm0: cannot get data >psm0: cannot get status > >anyway, the mouse does not work. > >the "mouse" string in kernel config is: > >device psm0 at atkbdc? irq 12 Would you give "boot -v" to the boot loader when starting the system, and send me the entire `dmesg' output? Does the BIOS setup menu have anything related to the PS/2 mouse port? What is your CPU? You said you wanted to use the latest BIOS because it supports Coppermine. Did you use Coppermine with the older BIOS and find the PS/2 mouse working? Or was it another CPU? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 20:27:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 95F8A14E68 for ; Wed, 19 Jan 2000 20:27:02 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id NAA04608; Thu, 20 Jan 2000 13:25:21 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp393.kt.rim.or.jp [202.247.140.93]) by mail1.rim.or.jp (3.7W/) id NAA00809; Thu, 20 Jan 2000 13:25:20 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id NAA20888; Thu, 20 Jan 2000 13:25:19 +0900 (JST) Date: Thu, 20 Jan 2000 13:25:18 +0900 Message-ID: <14470.36398.333535.99329N@localhost.sky.rim.or.jp> From: Jun Kuriyama To: n_hibma@webweaving.org Cc: FreeBSD CURRENT Mailing List Subject: Re: NEC ohci In-Reply-To: In your message of "Tue, 18 Jan 2000 10:43:49 +0000 (GMT)" References: <200001150022.QAA02899@mass.cdrom.com> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Nick Hibma > Try running usbd -e and see if that makes your mouse show up. usbd -e > does the explore once. I've tested on another machine with same NEC OHCI (Toshiba Libretto SS 1000). ----- dmesg ohci0: mem 0xffaff000-0xffafffff irq 11 at device 11.0 on pci0 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ----- When I plugged USB ethernet device (aue0), there is no message. And I've got message if I use "usbd -e". ----- usb0: unrecoverable error, controller halted usbd_new_device: addr=2, getting first desc failed uhub_explore: usb_new_device failed, error=TIMEOUT uhub0: device problem, disabling port 1 ----- PCI IRQ 11 of this machine is shared with other devices. Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 20:36:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7BB1014F1C for ; Wed, 19 Jan 2000 20:36:12 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id XAA93265; Wed, 19 Jan 2000 23:36:08 -0500 (EST) Date: Wed, 19 Jan 2000 23:36:08 -0500 (EST) From: "Matthew N. Dodd" To: Jon Simola Cc: damieon , freebsd-current@FreeBSD.ORG Subject: Re: Neat little DPT utils... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The old pre-CAM DPT driver provided an IOCTL interface that was implemented in sys/dev/dpt/dpt_control.c, which is commented out in sys/conf/files presently. The control devices are named 'dptN' where N is the DPT controller number. sys/conf/majors:88 dpt DPT RAID Controller You're going to need to work on dpt_control.c and make it not stomp on the rest of the driver when it tries to frob the device. Good luck. On Wed, 19 Jan 2000, Jon Simola wrote: > On Wed, 19 Jan 2000, damieon wrote: > > > I administer several machines running freebsd. Most of > > them are running FreeBSD-CURRENT, and all of them have DPT SmartRAID IV > > raid controlers. > > I've got a backup server here with a DPT SmartRAID IV (PM3334UW) running > 3.3-STABLE from Nov 17. About 15 minutes of playing and I've got the programs > compiling cleanly, however: > > root@tyberius:/usr/src/usr.sbin/dpt/dpt_ctlinfo$ ./dpt_ctlinfo > ./dpt_ctlinfo ERROR: Failed to open "(null)" - Bad address > > Looking at the code some more, I see: > > if ( (fd = open(argv[1], O_RDWR, S_IRUSR | S_IWUSR)) == -1 ) { > (void)fprintf(stderr, "%s ERROR: Failed to open \"%s\" - > %s\n", > argv[0], argv[1], strerror(errno)); > exit(1); > } > > So, I'm stuck with a compiling program and I don't know what it wants as an > argument. Anything I try give me an: > > root@tyberius:/usr/src/usr.sbin/dpt/dpt_ctlinfo$ ./dpt_ctlinfo /dev/da0 > ./dpt_ctlinfo ERROR: Failed to send IOCTL c0444403 - Inappropriate ioctl for > device > > I'll be looking into this some more over the next couple days, but any hints > or suggestions are more than welcome. If I can get it running in this > 3.3-STABLE server, then I'll steal the controller for a weekend and bang out > some -CURRENT code, although I think the necessary changes (STABLE -> CURRENT) > should be fairly minor. > > --- > Jon Simola | "In the near future - corporate networks > Systems Administrator | reach out to the stars, electrons and light > ABC Communications | flow throughout the universe." -- GITS > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 20:54:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5E6861504B; Wed, 19 Jan 2000 20:54:27 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA05264; Wed, 19 Jan 2000 23:54:21 -0500 (EST) Date: Wed, 19 Jan 2000 23:54:21 -0500 (EST) From: Daniel Eischen Message-Id: <200001200454.XAA05264@pcnet1.pcnet.com> To: eischen@vigrid.com, jasone@canonware.com Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > Doen't that method still have the problem of propagating cancellation > points within the libc code? In another email I argued for the need for > three names, and your response was that three names aren't needed in the > context of the next-generation threads library, but it seems to me that in > the case of libc_r, three names really are needed in order to do > cancellation correctly. Following is a revised version of my previous > email (changed to reflect libc_r rather than libpthread): > > It isn't adequate to only have two names with libc_r. There have to be: > > 1) _open() -- A name to access the actual system call. Or _thread_sys_open in the case of blocking system calls that the threads library wants to wrap. This is the method that libc_r used to use. In this case _open is a weak symbol to _thread_sys_open, and libc_r provides _open to do the call conversion so that threads don't block. > 2) _libc_open() -- A name that libc uses internally which by default is the > same as _open(), but can be overridden. 1a) _open -- A weak symbol to _thread_sys_open in the case when building for libc_r. > > 3) open() -- The name that an application uses (and cancellation point). > > If we were to remove _libc_open() and use open() instead inside of libc, we > would incorrectly propagate cancellation points (as is the case right now, > since _libc_open() and open() are the same in libc_r). Again, I've never suggested this. I agree that libc needs to use some other name than open. > > If we were to remove _libc_open() and use _open() instead inside of libc, > then we would have the problem of some libc functions using system calls > directly, where libc_r needs to do call conversion and/or extra bookkeeping > work. This is what I have suggested before. What we had before, was that _only_ those system calls that were wrapped by libc_r (to prevent blocking) were changed to _thread_sys_XXX. In this case, you make _XXX a weak symbol to _thread_sys_XXX. This is similar to having _libc_XXX as the weak symbol and _XXX as the system call. I am just suggesting that we revert back to the previous method of renaming only those system calls that libc_r needs to wrap to prevent blocking. So, in the case of open: libc: ----- open (weak symbol to _open) _open (system call) libc_r: ------- open (cancellable routine, calls _open) _open (wrapped to prevent blocking) _thread_sys_open (actual system call) And in the case of lockf: libc: ----- lockf (weak symbol to _lockf) _lockf (actual implementation) libc_r: ------- lockf (cancellable routine, calls _lockf) _lockf (actual implemenation) What we had before the _libc_XXX name additions would have worked as long as all internal uses of XXX inside libc were changed to _XXX, and, when building for libc_r, all renamed (hidden) system calls need _XXX defined as weak symbols to _thread_sys_XXX. My argument is that we don't need to provide weak symbols for all the system calls, only the hidden system calls that libc_r wraps. And, when we implement SA (or whatever we choose to call it), we won't need any hidden system calls. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 21: 2:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 4FCCE1520C; Wed, 19 Jan 2000 21:02:41 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA06534; Thu, 20 Jan 2000 00:02:34 -0500 (EST) Date: Thu, 20 Jan 2000 00:02:34 -0500 (EST) From: Daniel Eischen To: jasone@canonware.com, current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: RFC: buildworld breakage due to cross-tools/libc/mktemp. In-Reply-To: <200001200454.XAA05264@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What we had before the _libc_XXX name additions would have worked > as long as all internal uses of XXX inside libc were changed to > _XXX, and, when building for libc_r, all renamed (hidden) system > calls need _XXX defined as weak symbols to _thread_sys_XXX. Actually, you don't even need to define _XXX as a weak symbol for _thread_sys_XXX when building libc_r. libc_r will provide the routine _XXX to perform the call conversion, so defining _XXX as a weak symbol is not needed. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 21:20:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 04D8614D6C for ; Wed, 19 Jan 2000 21:20:38 -0800 (PST) (envelope-from bitsurfr@enteract.com) Received: from wildrock (207-229-142-152.d.enteract.com [207.229.142.152]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id XAA51614 for ; Wed, 19 Jan 2000 23:20:36 -0600 (CST) (envelope-from bitsurfr@enteract.com) From: "Chris Silva" To: "Current FreeBSD" Subject: Wanting to go to -CURRENT Date: Wed, 19 Jan 2000 23:20:57 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.4-STABLE on a few boxes at home. I want to go to -CURRENT. I'm assuming a cvsup using the standard supfile will do this - however, I have tried cvsuping to current, but it blows up towards the end (I am sorry, I didn't think to save any error messages) and on reboot, I'm forced to single mode, and I can't use the default SH - it's pretty well hung up and I'm forced to do a re-install. Is this something that happens often? Or is there now a trick to use current? TIA Best regards, Chris _____________________________________________________________________ DH/DSS Fingerprint = 8265 0BB8 2C7D A376 3CCD 6858 8630 0E47 194A 0318 RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B PGP Mail encouraged / preferred - keys available on common key servers _____________________________________________________________________ Proud supporter of FreeBSD, NetBSD, and OpenBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 21:27:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 4F441152CE; Wed, 19 Jan 2000 21:27:13 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:6+KtLN6WXcLBePX2JltYUcdJFhjJmmes@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA02213; Thu, 20 Jan 2000 14:27:07 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id OAA16660; Thu, 20 Jan 2000 14:32:38 +0900 (JST) Message-Id: <200001200532.OAA16660@zodiac.mech.utsunomiya-u.ac.jp> To: "Jeffrey J. Libman" , stable@freebsd.org, current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: rpc.statd won't fire on friday's build Date: Thu, 20 Jan 2000 14:32:36 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, my loopback (lo0) was down. It's a pilot error. Sorry for the false alarm. `portmap' is OK in -CURRENT. Jeffrey, your problem may be the same as mine. You had better check `network_interfaces' in /etc/rc.conf. It should have `lo0' together with all other network interfaces. Or, it should have just one word, "auto". Kazu >I am experiencing the same problem on the 4.0-CURRENT system >built from the source around Saturday. Another -CURRENT box, >for which 'make world' was done from the source about a week ago, >appears to have no problem. > >I suspect `portmap' is somewhat broken. In addition to `rpc.statd', >`nfsd' and `mountd' are also unable to register ports. > >nfsd:[88]: can't register with udp portmap >mountd[86]: can't register mount > >Kazu > >>no idea what i've done here. >> >>friday's cvsup and build...new kernel...installed on 2 systems. on one of >>the systems, rpc.statd will not run, gets: >> >>rpc.statd: unable to register (SM_PROG, SM_VERS, udp) >> >>this particular system has about 50 ip's assigned to lo0...and that has >>worked fine as is for months, inspite of all the verbage here about >>netmasks and such. loopback IS configured. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 21:36:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69]) by hub.freebsd.org (Postfix) with ESMTP id 657B2152CE for ; Wed, 19 Jan 2000 21:36:40 -0800 (PST) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.9.3/ignatz) with ESMTP id VAA83283; Wed, 19 Jan 2000 21:36:19 -0800 (PST) Date: Wed, 19 Jan 2000 21:36:18 -0800 (PST) From: "f.johan.beisser" To: Chris Silva Cc: Current FreeBSD Subject: Re: Wanting to go to -CURRENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off, why would you want to go to -current? for the most part, features in -current, might be pulled back in to -stable at some point. when -current is actually released, it'll run quite nicely, but in the meanwhile, it's slightly pointless for most folks to be running it on anything close to resembling a production box. now, after that little rant.. to answer your question.. On Wed, 19 Jan 2000, Chris Silva wrote: > I'm running 3.4-STABLE on a few boxes at home. I want to go to -CURRENT. > I'm assuming a cvsup using the standard supfile will do this - however, > I have tried cvsuping to current, but it blows up towards the end (I > am sorry, I didn't think to save any error messages) and on reboot, I'm > forced to single mode, and I can't use the default SH - it's pretty well > hung up and I'm forced to do a re-install. this is caused by incompatable libraries being installed. your old 3.4-stable box doesn't much like the new 4.0 libraries, and the new 4.0 binaries don't really like the 3.4 kernel.. your solution is pretty much it, you have to reinstall. to the best of my knowledge, "make upgrade" is still broken. you might try to do a buildworld of the -current sources, but most likely they'll fail aswell. > Is this something that happens often? Or is there now a trick to use > current? TIA my trick was getting a SNAP release, and making a bootable CDROM from it. of course, as most "real hackers" would have told you, this is "cheating" and just not the "right way" to do it. but hey, it worked. as for what you might do, or try, well, i suggest first remembering that 4.0 will be out as -stable (heh) "real soon now". > Best regards, > Chris -- jan +-----// f. johan beisser //------------------------------+ email: jan[at]caustic.org web: http://www.caustic.org/~jan "knowledge is power. power corrupts. study hard, be evil." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 21:41: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mumble.frotz.net (mumble.frotz.net [216.15.97.250]) by hub.freebsd.org (Postfix) with SMTP id 6996F152CE for ; Wed, 19 Jan 2000 21:41:06 -0800 (PST) (envelope-from swetland@frotz.net) Received: (qmail 30065 invoked by uid 1000); 20 Jan 2000 05:42:58 -0000 Date: Wed, 19 Jan 2000 21:42:58 -0800 From: "Brian J. Swetland" To: current@freebsd.org Subject: devfs? Message-ID: <20000119214258.A29986@frotz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6us Organization: Frotz Communications, Ltd. X-Mailer-Holy-War: Get Mutt, it bites! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm interested in mucking about with the devfs stuff a bit -- is there currently any active developer/maintainer/docs? I grabbed the 4.0 snapshot from the 17th, installed it, grabbed the kernel sources from CVS, got stuff building and figured out how to enable DDB (not that much different from the kdebug environment I'm used to from BeOS). I figured I'd see if there was any more information than the sources. 4.0-CURRENT seems to work well (though the first time through it had problems booting after install due to some confusion between wd0s4a and ad0s4a -- I nuked the wd* devnodes after the install and it was happy enough). Are there any known SMP issues? (I'm not experiencing any problems with an SMP kernel on a dual PII machine so far) Thanks, Brian -- Brian Swetland - swetland@frotz.net | "If I have hacked deeper than them, it http://www.frotz.net/swetland/ | is because I stand in their trenches." | -- Graham Nelson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 22: 6:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (Postfix) with ESMTP id EA7F6152D3 for ; Wed, 19 Jan 2000 22:06:09 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg136-175.ricochet.net [204.179.136.175]) by geocities.com (8.9.3/8.9.3) with ESMTP id WAA06596; Wed, 19 Jan 2000 22:05:57 -0800 (PST) Message-ID: <3886A6A9.12DA7F32@geocities.com> Date: Wed, 19 Jan 2000 22:09:45 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: current@FreeBSD.ORG, Gerald Abshez Subject: Re: NFS and Samba (file transfer crashes system) References: <387FDF2D.575DC537@geocities.com> <200001150528.VAA95955@apollo.backplane.com> <3883B0F4.60A1623F@geocities.com> <200001180226.SAA18343@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > * Are you running softupdates on the UFS filesystem on the NFS server? no softupdates. > I would also look at your 'dmesg' output to see if you are getting any > IDE errors. no IDE errors > And there is yet another possibility: The new ATA driver has lots of > problems and as far as I can tell none of the reported problems have yet > been fixed. I would recommend going back to the 'wd' driver and seeing > if that helps. some what in a catch 22 here... mb bios handles only 8.4gig and I have a 17gig harddrive > -Matt > Matthew Dillon > I am still having the problem as of version current-20000118 morning. And I have come up with these results with a few scenarios. SCENARIO 1: - from win9x (transferring files from server to win9x) by drag and drop - nfsd off results: - server freezes, reset, no manual fsck, no core dump SCENARIO 2: - from win9x (transferring files FROM win9x to server) by drag and drop - nfsd off results: - clean transfer SCENARIO 3: - from win9x (transferring files FROM win9x to server--another try :-)) by drag and drop - nfsd off results: - drop into ddb with this outcome: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8bc93139 fault code = supervisor read, page not present instruction pointer = 0x8:0xc018aa5f stack pointer = 0x10:0xc437be0c frame pointer = 0x10:0xc437be28 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 163 (smbd) interrupt mask = kernel: type 12 trap, code=0 Stopped at ip_input+0xc7: lock adcb $0x75,%al db> trace ip_input(c03ca500) at ip_input+0xc7 ipintr(c0209880,0,c021e3c2,c0156ac3,0) at ipintr+0x4b swi_net_next(c3fe1b40,c437bed0,c435bedc,0,0) at swi_net_next recvit(c410a400,7,c437bf20,0,c410a400) at recvit+0x101 recvfrom((c410a400,c437bf80,281b0ec8,6bbb,ffff) at recvfrom+0x6c syscall(bfbf002f,c437002f,bfbf002f,ffff,6bbb) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 By this time I am suspecting that it might be samba. So, I tried another scenario. SCENARIO 4: - from freebsd 3.2 box (..#cp -r localdir mntpoint) - samba off results: - server freezes, reset button, run fsck manually, no core dump Not sure of what is going on... but I now suspect, like what matt has mentioned, that neither samba nor nfs are at fault. I simply have to do more experimenting and running the system without the ultra66 controller. arnee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 22:34:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from koala.pulsat.com.au (koala.pulsat.com.au [202.81.128.10]) by hub.freebsd.org (Postfix) with ESMTP id D4F3F151D6; Wed, 19 Jan 2000 22:34:05 -0800 (PST) (envelope-from paul@pulsat.com.au) Received: from localhost (paul@localhost) by koala.pulsat.com.au (8.9.3/8.9.3) with ESMTP id OAA02185; Thu, 20 Jan 2000 14:33:52 +0800 (WST) (envelope-from paul@pulsat.com.au) Date: Thu, 20 Jan 2000 14:33:52 +0800 (WST) From: Paul Reece To: freebsd-questions@freebsd.org Cc: freebsd-current@freebsd.org Subject: Problems with an0 and ISA Aironet Card.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Having a few problems trying to get an ISA Aironet 4800 card working under FreeBSD 4.0-CURRENT. I did try with 3.4-RELEASE first with the appropriate drivers, but had even less luck. What I'm seeing at boot: first suspect lines: isa0: unexpected tag 14 isa0: unexpected tag 14 then: an0: reset failed unknown0: at port 0x100-0x13f irq 5 on isa0 an0: reset failed unknown1: at port 0x140-0x17f irq 10 on isa0 (machine has 2 cards in it). When trying with NON PNP mode, the cards also have the same problem. PCI cards work fine, just not the ISA equivalents.. Anyone have any clues/hints/tips etc? Cheers. Regards, Paul. (replies to me direct please - not on list) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 22:34:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 2BD891537E for ; Wed, 19 Jan 2000 22:34:19 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 26464 invoked from network); 20 Jan 2000 06:34:15 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 20 Jan 2000 06:34:15 -0000 Date: Thu, 20 Jan 2000 17:34:13 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Andrey A. Chernov" Cc: Peter Wemm , current@freebsd.org, bde@freebsd.org, sheldonh@freebsd.org Subject: Re: Security hole with new setresuid call In-Reply-To: <20000119035329.A65749@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Andrey A. Chernov wrote: > On Tue, Jan 18, 2000 at 02:12:02PM +0800, Peter Wemm wrote: > > .. and why is this a security hole? setresuid(geteuid(), geteuid(), geteuid()) > > is equivalent to setuid(geteuid()).. > > Umm, maybe not the hole exactly, but difference between same area syscalls > implementation. Before setresuid() existed, the euid was known to be either the ruid or the svuid, so not checking in setreuid() for the new ruid being either the ruid or the svuid was just an optimization. setreuid() has the interesting implementation detail of setting the svuid to the euid. I think we did this mainly to avoid surprises in old programs that don't know about the svuid, but it has some side effects: (1) it allows unprivileged callers to change the svuid. (2) it maintains the "known" property. setresuid() now allows even unprivileged callers to break the "known" property: starting from a normal setuid setup with svuid == euid, setresuid(euid, ruid, euid) swaps the ruid with the euid like setreuid(euid, ruid), but it doesn't adjust the svuid. Possible fixes 1) change setreuid() to allow new_ruid == euid, etc. 2) do nothing. Programs shouldn't set the svuid to a non-working value if it hurts when they do that. setresuild() now allows privileged callers to set the ids to 3 different values. This may confuse later operation of the process. Fix: don't do that. > We define POSIX_APPENDIX_B_4_2_2 by default for setuid(geteuid()), but I > mean case when it is _not_ defined (BTW, why to have define which is > always on?) It's like the _POSIX_SAVED_IDS define which is always off. It was written before we learned to bury mistakes in the repository :-). > And in case POSIX_APPENDIX_B_4_2_2 is not defined, > ruid = euid; > assignment was not allowed before you add new syscall. It could be done using: seteuid(ruid); setuid(ruid); /* To set svuid too. */ but allowed it dierectly in setuid() to support programs that don't understand BSD4.4 seteuid(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 22:34:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BDE4153C8 for ; Wed, 19 Jan 2000 22:34:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA42986; Wed, 19 Jan 2000 22:34:35 -0800 (PST) (envelope-from dillon) Date: Wed, 19 Jan 2000 22:34:35 -0800 (PST) From: Matthew Dillon Message-Id: <200001200634.WAA42986@apollo.backplane.com> To: arnee Cc: current@FreeBSD.ORG, Gerald Abshez Subject: Re: NFS and Samba (file transfer crashes system) References: <387FDF2D.575DC537@geocities.com> <200001150528.VAA95955@apollo.backplane.com> <3883B0F4.60A1623F@geocities.com> <200001180226.SAA18343@apollo.backplane.com> <3886A6A9.12DA7F32@geocities.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : - nfsd off :results: : - drop into ddb with this outcome: : :Fatal trap 12: page fault while in kernel mode :fault virtual address = 0x8bc93139 :fault code = supervisor read, page not present :instruction pointer = 0x8:0xc018aa5f :stack pointer = 0x10:0xc437be0c :frame pointer = 0x10:0xc437be28 :code segment = base 0x0, limit 0xfffff, type 0x1b : = DPL 0, pres 1, def32 1, gran 1 :processor eflags = interrupt enabled, resume, IOPL = 0 :current process = 163 (smbd) :interrupt mask = :kernel: type 12 trap, code=0 :Stopped at ip_input+0xc7: lock adcb $0x75,%al :db> trace :ip_input(c03ca500) at ip_input+0xc7 :ipintr(c0209880,0,c021e3c2,c0156ac3,0) at ipintr+0x4b :swi_net_next(c3fe1b40,c437bed0,c435bedc,0,0) at swi_net_next :recvit(c410a400,7,c437bf20,0,c410a400) at recvit+0x101 :recvfrom((c410a400,c437bf80,281b0ec8,6bbb,ffff) at recvfrom+0x6c :syscall(bfbf002f,c437002f,bfbf002f,ffff,6bbb) at syscall+0x176 :Xint0x80_syscall() at Xint0x80_syscall+0x26 : :By this time I am suspecting that it might be samba. So, I tried another scenario. This looks to me like a bug in either the ethernet driver or the IP stack. Could you supply the output from 'dmesg'? With NFS and softupdates not being the cause this isn't really in my court any more but maybe someone else in -current has some ideas. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 22:40:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id 56BD015355 for ; Wed, 19 Jan 2000 22:40:10 -0800 (PST) (envelope-from vinson@ucsu.Colorado.EDU) Received: from localhost (vinson@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) with SMTP id XAA02484 for ; Wed, 19 Jan 2000 23:40:05 -0700 (MST) Date: Wed, 19 Jan 2000 23:40:05 -0700 (MST) From: VINSON WAYNE HOWARD To: current@freebsd.org Subject: PAO Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been folowing 4.0, and I have a laptop I'd like to try it on... but I can't figure out how to get support for a 3com 574-tx... normaly Pao would handel that, but I didn't see a pao 4.0 cvs branch. Am I just SOL, or is there a workaround??? Please CC me, I'm not on the list To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 22:56:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 88F3A15369 for ; Wed, 19 Jan 2000 22:56:29 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA77131; Wed, 19 Jan 2000 23:56:28 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA00564; Wed, 19 Jan 2000 23:56:14 -0700 (MST) Message-Id: <200001200656.XAA00564@harmony.village.org> To: VINSON WAYNE HOWARD Subject: Re: PAO Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 19 Jan 2000 23:40:05 MST." References: Date: Wed, 19 Jan 2000 23:56:14 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message VINSON WAYNE HOWARD writes: : I've been folowing 4.0, and I have a laptop I'd like to try it on... but I : can't figure out how to get support for a 3com 574-tx... normaly Pao would : handel that, but I didn't see a pao 4.0 cvs branch. Am I just SOL, or is : there a workaround??? Support for the 574 is in -current. There likely won't be a pao branch for 4.0. It is generally unneeded, modulo a few drivers which will likely be committed to -current shortly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 19 23:38:12 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A591A152A9; Wed, 19 Jan 2000 23:38:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 978A21CD64A; Wed, 19 Jan 2000 23:38:08 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 19 Jan 2000 23:38:08 -0800 (PST) From: Kris Kennaway To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@freebsd.org Subject: Re: cvs commit: src/secure/usr.bin/openssl Makefile In-Reply-To: <200001200729.XAA88272@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Kris Kennaway wrote: > Modified files: > secure/usr.bin/openssl Makefile > Log: > Don't search for libraries in ${LOCALBASE}. This should fix the problems > people were seeing with conflicts with the openssl port. I tried to test all of the possible cases here, so I hope this hasn't broken anyone :-) Internat will follow tomorrow, all being well. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 0:28:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 6A667153B9; Thu, 20 Jan 2000 00:28:33 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id DAA10306; Thu, 20 Jan 2000 03:32:17 -0500 From: Bill Paul Message-Id: <200001200832.DAA10306@skynet.ctr.columbia.edu> Subject: Re: Problems with an0 and ISA Aironet Card.. To: paul@pulsat.com.au (Paul Reece) Date: Thu, 20 Jan 2000 03:32:15 -0500 (EST) Cc: current@freebsd.org, questions@freebsd.org In-Reply-To: from "Paul Reece" at Jan 20, 2000 02:33:52 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3841 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Paul Reece had to walk into mine and say: > Having a few problems trying to get an ISA Aironet 4800 card working under > FreeBSD 4.0-CURRENT. I did try with 3.4-RELEASE first with the > appropriate drivers, but had even less luck. > What I'm seeing at boot: Back up. You're leaving out some info. - When did you buy these cards? (The firmware rev may be an issue. knowing when you bought the card helps me figure out if your firmware is newer than mine.) - What sort of machine are you using? (Show us the *whole* dmesg output. Timing may also be an issue, in which case I need to know the CPU speed.) > first suspect lines: > > isa0: unexpected tag 14 > isa0: unexpected tag 14 I'm not sure if this is related. > then: > > an0: reset failed > unknown0: at port 0x100-0x13f irq 5 on isa0 > an0: reset failed > unknown1: at port 0x140-0x17f irq 10 on isa0 > > > (machine has 2 cards in it). When trying with NON PNP mode, the cards > also have the same problem. Tell us what kernel config line you use when using the card in non-PnP mode. Note that the switches on the card must all be in the correct position in order to enable PnP mode: consult your user's manual for the proper settings. I believe they all need to be in the off position, however I don't have the manual here at home with me so I could be mistaken. (I do remember they all have to be set the same way.) > PCI cards work fine, just not the ISA > equivalents.. > > Anyone have any clues/hints/tips etc? Not really. My one and only ISA card works fine, or at least it did when I did my tests right before I imported the driver. It would help if you could actually look at the card when the kernel boots to see if the LEDs flash at all. If the reset is screwing up, then you should see the LEDs flicker when it tries to access the board. If it's failing to access the board at all, the LEDs won't change at all. Try commenting out the code in an_reset() (i.e. make it an empty function that does nothing) and see if it works then. If it *still* doesn't work, then there's something else wrong. Try to run the following program as root: #include #include #include #include #define IOADDR 0x100 /* change to 0x140 for other card */ main() { int f; f = open("/dev/io", O_RDWR); printf("COMMAND: %x\n", inw(IOADDR)); printf("PARAM0: %x\n", inw(IOADDR + 0x2)); outw(IOADDR + 0x2, 0x1234); printf("PARAM0: 0x\n", inw(IOADDR + 0x2)); exit(0); } This will print out the command and status registers for the card at iobase 0x100. If the card has been properly activated, you should see 0000 for the COMMAND and PARAM0 registers initially, then the program will try to write 0x1234 to the PARAM0 register and read it back. If it reads back 0x1234, then the card is configured right and the reset is screwing up. If on the other hand the program prints ffff for all of the register contents, then the card is not really configured properly for address 0x100. > > Cheers. > > > Regards, > Paul. > > (replies to me direct please - not on list) I'm doing both. Deal with it. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 1:35:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from koala.pulsat.com.au (koala.pulsat.com.au [202.81.128.10]) by hub.freebsd.org (Postfix) with ESMTP id B49D9153CA for ; Thu, 20 Jan 2000 01:35:41 -0800 (PST) (envelope-from paul@pulsat.com.au) Received: from localhost (paul@localhost) by koala.pulsat.com.au (8.9.3/8.9.3) with ESMTP id RAA02989; Thu, 20 Jan 2000 17:35:16 +0800 (WST) (envelope-from paul@pulsat.com.au) Date: Thu, 20 Jan 2000 17:35:16 +0800 (WST) From: Paul Reece To: Bill Paul Cc: current@freebsd.org Subject: Re: Problems with an0 and ISA Aironet Card.. In-Reply-To: <200001200832.DAA10306@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jan 2000, Bill Paul wrote: > Back up. You're leaving out some info. > > - When did you buy these cards? (The firmware rev may be an issue. > knowing when you bought the card helps me figure out if your firmware > is newer than mine.) Cards were purchased in the past 6 months. Revision of the card I'm using at the moment is 3.13 - I upgraded the firmware to the latest. (Win DGS under 'status' reports 3.13). > - What sort of machine are you using? (Show us the *whole* dmesg output. > Timing may also be an issue, in which case I need to know the CPU speed.) CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 201261056 (196544K bytes) avail memory = 192323584 (187816K bytes) Preloaded elf kernel "kernel" at 0xc02b4000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: mem 0xe6000000-0xe6ffffff,0xe4000000-0xe4ffffff irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10 pci0: unknown card (vendor=0x1319, dev=0x0801) at 8.0 irq 11 pci0: unknown card (vendor=0x1319, dev=0x0802) at 8.1 rl0: port 0xec00-0xecff mem 0xe7000000-0xe70000ff irq 9 at device 9.0 on pci0 rl0: Ethernet address: 00:c0:df:25:f1:5c miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isa0: unexpected tag 14 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic1: not probed (disabled) sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 an0: reset failed unknown0: at port 0x100-0x13f irq 5 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata0 as slave acd0: 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked I've only got one card in the machine now. Only one 'unexpected tag' line now.. > Tell us what kernel config line you use when using the card in non-PnP > mode. Note that the switches on the card must all be in the correct > position in order to enable PnP mode: consult your user's manual for > the proper settings. I believe they all need to be in the off position, > however I don't have the manual here at home with me so I could be > mistaken. (I do remember they all have to be set the same way.) for non-PnP mode, they are set as per the manual. Config line for the above was: device an0 at isa? port 0x100 irq 5 same result whether I'm using PnP or not. (above output is from PnP). > Not really. My one and only ISA card works fine, or at least it did when > I did my tests right before I imported the driver. It would help if you > could actually look at the card when the kernel boots to see if the LEDs > flash at all. If the reset is screwing up, then you should see the LEDs > flicker when it tries to access the board. If it's failing to access the > board at all, the LEDs won't change at all. The RED LED statys on during boot, until the kernel tries to init the card - then the RED LED goes out, and thats it. > Try commenting out the code in an_reset() (i.e. make it an empty > function that does nothing) and see if it works then. If it *still* > doesn't work, then there's something else wrong. Tried this - doesn't even list the card in the output except for then unknown line. > Try to run the > following program as root: > This will print out the command and status registers for the card > at iobase 0x100. If the card has been properly activated, you should > see 0000 for the COMMAND and PARAM0 registers initially, then the > program will try to write 0x1234 to the PARAM0 register and read it > back. If it reads back 0x1234, then the card is configured right > and the reset is screwing up. If on the other hand the program prints > ffff for all of the register contents, then the card is not really > configured properly for address 0x100. pcpaul# ./testa COMMAND: 0 PARAM0: ff11 PARAM0: 0x (still no lights on card) if I run it again: pcpaul# ./testa COMMAND: 0 PARAM0: 1234 PARAM0: 0x (and still no lights). This info help at all? Cheers, Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 1:48:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from golf.dax.net (golf.dax.net [193.216.69.103]) by hub.freebsd.org (Postfix) with ESMTP id A05B514F9F for ; Thu, 20 Jan 2000 01:48:15 -0800 (PST) (envelope-from telde@online.no) Received: from delta.shacknet.nu ([193.216.101.70]) by golf.dax.net (8.9.3/8.9.3) with ESMTP id KAA09448 for ; Thu, 20 Jan 2000 10:49:33 +0100 (MET) Received: by delta.shacknet.nu (Postfix, from userid 1001) id 672FD7C48; Wed, 19 Jan 2000 21:35:13 +0100 (CET) Date: Wed, 19 Jan 2000 21:35:12 +0100 From: Terje Elde To: current@FreeBSD.ORG Subject: NO_IDEA Message-ID: <20000119213512.A40812@best.xti.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Mailer: Mutt http://www.mutt.org/ X-Editor: Vim http://www.vim.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Because of copyright issues OpenSSL is being built with -DNO_IDEA. IMHO it's bad to do this for all systems, as it's only limited in some countries. What I'm wondering if we could do is to add a COUNTRY=whatever, which could be used to look up a value in a file which could provide information about patent issues for algorithms like IDEA, as well as be a nice index to which ftp server to use by default. Another thing to consider is adding a COMMERCIAL=[yes|no], which could also help sorting out patent issues. Just some thoughts... Terje Elde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 3: 0:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id D0F00153DC; Thu, 20 Jan 2000 02:59:56 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.8]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FOMRVU01.HAL; Thu, 20 Jan 2000 11:59:54 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id LAA00643; Thu, 20 Jan 2000 11:34:31 +0100 (CET) (envelope-from asmodai) Date: Thu, 20 Jan 2000 11:34:30 +0100 From: Jeroen Ruigrok/Asmodai To: Warner Losh Cc: Chris Piazza , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: boot messages for pci devices... Message-ID: <20000120113430.B283@daemon.ninth-circle.org> References: <20000118154542.B282@norn.ca.eu.org> <31733.948238089@critter.freebsd.dk> <20000118154542.B282@norn.ca.eu.org> <200001190444.VAA21604@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001190444.VAA21604@harmony.village.org>; from imp@village.org on Tue, Jan 18, 2000 at 09:44:13PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000119 08:00], Warner Losh (imp@village.org) wrote: >In message <20000118154542.B282@norn.ca.eu.org> Chris Piazza writes: >: I *thought* I noticed it was different. I actually find this pretty >: annoying because it wraps almost all of the lines and makes it difficult >: to read dmesg. > >I don't mind them, but wouldn't object to a generic wrapping >mechanism. Ditto, I like the current verbosity, and the really bootverbose stuff is WAY much more verbose than this. For me, at least, this allows easy debugging without going full verbose. That wrapping issue seems very useful indeed. At least it would structure the information a bit more orderly. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Peace with honour... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 3:26:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 086EE14D73 for ; Thu, 20 Jan 2000 03:26:10 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id MAA45165; Thu, 20 Jan 2000 12:25:19 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <3886F0D0.A523E8EB@fernuni-hagen.de> Date: Thu, 20 Jan 2000 12:26:08 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Parallel Port Zip Drive works when EPP-Mode is choosen in Bios Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject says all! This evening i will try a patch for the ata driver so maybe all my hardware at home will work again with current when certain patches are applied. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 5: 4: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from hack.babel.dk (hack.babel.dk [194.255.106.77]) by hub.freebsd.org (Postfix) with ESMTP id 7755814D0D for ; Thu, 20 Jan 2000 05:04:01 -0800 (PST) (envelope-from shredder@hack.babel.dk) Received: from localhost (shredder@localhost) by hack.babel.dk (8.9.3/8.9.1) with SMTP id OAA17060 for ; Thu, 20 Jan 2000 14:03:58 +0100 (CET) Date: Thu, 20 Jan 2000 14:03:58 +0100 (CET) From: chrw To: freebsd-current@freebsd.org Subject: swap_pager_getswapspace: failed (4.0-CURRENT) (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------- Forwarded message ---------- Date: Wed, 19 Jan 2000 15:35:23 +0100 (CET) From: chrw To: freebsd-isp@freebsd.org Subject: swap_pager_getswapspace: failed (4.0-CURRENT) Helllo, I am experiencing problems regarding the swap handler. I am running 4.0-CURRENT FreeBSD 4.0-CURRENT #10 The box is running apache-1.3.9, cucipop v1.32, and sendmail 8.9.3, and also runs as an NFS client. Kernel is configured with 512 MAXUSERS, swap device is 400MB with real memory = 134201344 (131056K bytes) avail memory = 126275584 (123316K bytes) Apache is is configured to run with MinSpareServers 50 MaxSpareServers 100 The box runs without any problems, and not using very much swap space for about 24 hours, then suddenly it generates the error message: Jan 19 13:03:03 hostname /kernel: swap_pager_getswapspace: failed and about 1 min later, it stops responding to any service requests. I would be gratefull for any hints or suggestions concerning what might cause this fatal problem and possible solutions. CW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 6:59:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from gandalf.hk.linkage.net (gandalf.hk.linkage.net [202.76.4.1]) by hub.freebsd.org (Postfix) with ESMTP id 74D0F14ECB for ; Thu, 20 Jan 2000 06:59:52 -0800 (PST) (envelope-from satyajit@spnetctg.com) Received: from mail.spnetctg.com (qmailr@mail.spnetctg.com [210.184.28.8]) by gandalf.hk.linkage.net (8.9.1/8.8.8) with SMTP id WAA05209 for ; Thu, 20 Jan 2000 22:59:46 +0800 (HKT) Received: (qmail 30953 invoked from network); 20 Jan 2000 15:26:04 -0000 Received: from unknown (HELO spnetctg.com) (210.184.28.230) by mail.spnetctg.com with SMTP; 20 Jan 2000 15:26:04 -0000 Message-ID: <388720BE.607081AC@spnetctg.com> Date: Thu, 20 Jan 2000 14:50:38 +0000 From: Satyajit Das X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Re: Majordomo results References: <20000120135039.B7842153FC@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG do anyone help me subscribe freebsd-question. I have so many question which i like to share with freebsd-question. please help anyone , how can i subscribe in freebsd-question mailing list. please note, i wrote email address: majordomo@freebsd.org and in body : subscribe freebsd-question may i do wrong ? Majordomo@FreeBSD.ORG wrote: > -- > > >>>> subscribe freebsd-question > **** subscribe: unknown list 'freebsd-question'. > >>>> > >>>> > >>>> > **** Help for Majordomo@FreeBSD.ORG: > > This help message is being sent to you from the Majordomo mailing list > management system at Majordomo@FreeBSD.ORG. > > This is version 1.94.4 of Majordomo. > > If you're familiar with mail servers, an advanced user's summary of > Majordomo's commands appears at the end of this message. > > Majordomo is an automated system which allows users to subscribe > and unsubscribe to mailing lists, and to retrieve files from list > archives. > > You can interact with the Majordomo software by sending it commands > in the body of mail messages addressed to "Majordomo@FreeBSD.ORG". > Please do not put your commands on the subject line; Majordomo does > not process commands in the subject line. > > You may put multiple Majordomo commands in the same mail message. > Put each command on a line by itself. > > If you use a "signature block" at the end of your mail, Majordomo may > mistakenly believe each line of your message is a command; you will > then receive spurious error messages. To keep this from happening, > either put a line starting with a hyphen ("-") before your signature, > or put a line with just the word > > end > > on it in the same place. This will stop the Majordomo software from > processing your signature as bad commands. > > Here are some of the things you can do using Majordomo: > > I. FINDING OUT WHICH LISTS ARE ON THIS SYSTEM > > To get a list of publicly-available mailing lists on this system, put the > following line in the body of your mail message to Majordomo@FreeBSD.ORG: > > lists > > Each line will contain the name of a mailing list and a brief description > of the list. > > To get more information about a particular list, use the "info" command, > supplying the name of the list. For example, if the name of the list > about which you wish information is "demo-list", you would put the line > > info demo-list > > in the body of the mail message. > > II. SUBSCRIBING TO A LIST > > Once you've determined that you wish to subscribe to one or more lists on > this system, you can send commands to Majordomo to have it add you to the > list, so you can begin receiving mailings. > > To receive list mail at the address from which you're sending your mail, > simply say "subscribe" followed by the list's name: > > subscribe demo-list > > If for some reason you wish to have the mailings go to a different address > (a friend's address, a specific other system on which you have an account, > or an address which is more correct than the one that automatically appears > in the "From:" header on the mail you send), you would add that address to > the command. For instance, if you're sending a request from your work > account, but wish to receive "demo-list" mail at your personal account > (for which we will use "jqpublic@my-isp.com" as an example), you'd put > the line > > subscribe demo-list jqpublic@my-isp.com > > in the mail message body. > > Based on configuration decisions made by the list owners, you may be added > to the mailing list automatically. You may also receive notification > that an authorization key is required for subscription. Another message > will be sent to the address to be subscribed (which may or may not be the > same as yours) containing the key, and directing the user to send a > command found in that message back to Majordomo@FreeBSD.ORG. (This can be > a bit of extra hassle, but it helps keep you from being swamped in extra > email by someone who forged requests from your address.) You may also > get a message that your subscription is being forwarded to the list owner > for approval; some lists have waiting lists, or policies about who may > subscribe. If your request is forwarded for approval, the list owner > should contact you soon after your request. > > Upon subscribing, you should receive an introductory message, containing > list policies and features. Save this message for future reference; it > will also contain exact directions for unsubscribing. If you lose the > intro mail and would like another copy of the policies, send this message > to Majordomo@FreeBSD.ORG: > > intro demo-list > > (substituting, of course, the real name of your list for "demo-list"). > > III. UNSUBSCRIBING FROM MAILING LISTS > > Your original intro message contains the exact command which should be > used to remove your address from the list. However, in most cases, you > may simply send the command "unsubscribe" followed by the list name: > > unsubscribe demo-list > > (This command may fail if your provider has changed the way your > address is shown in your mail.) > > To remove an address other than the one from which you're sending > the request, give that address in the command: > > unsubscribe demo-list jqpublic@my-isp.com > > In either of these cases, you can tell Majordomo@FreeBSD.ORG to remove > the address in question from all lists on this server by using "*" > in place of the list name: > > unsubscribe * > unsubscribe * jqpublic@my-isp.com > > IV. FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED > > To find the lists to which your address is subscribed, send this command > in the body of a mail message to Majordomo@FreeBSD.ORG: > > which > > You can look for other addresses, or parts of an address, by specifying > the text for which Majordomo should search. For instance, to find which > users at my-isp.com are subscribed to which lists, you might send the > command > > which my-isp.com > > Note that many list owners completely or fully disable the "which" > command, considering it a privacy violation. > > V. FINDING OUT WHO'S SUBSCRIBED TO A LIST > > To get a list of the addresses on a particular list, you may use the > "who" command, followed by the name of the list: > > who demo-list > > Note that many list owners allow only a list's subscribers to use the > "who" command, or disable it completely, believing it to be a privacy > violation. > > VI. RETRIEVING FILES FROM A LIST'S ARCHIVES > > Many list owners keep archives of files associated with a list. These > may include: > - back issues of the list > - help files, user profiles, and other documents associated with the list > - daily, monthly, or yearly archives for the list > > To find out if a list has any files associated with it, use the "index" > command: > > index demo-list > > If you see files in which you're interested, you may retrieve them by > using the "get" command and specifying the list name and archive filename. > For instance, to retrieve the files called "profile.form" (presumably a > form to fill out with your profile) and "demo-list.9611" (presumably the > messages posted to the list in November 1996), you would put the lines > > get demo-list profile.form > get demo-list demo-list.9611 > > in your mail to Majordomo@FreeBSD.ORG. > > VII. GETTING MORE HELP > > To contact a human site manager, send mail to postmaster@FreeBSD.ORG. > > To get another copy of this help message, send mail to Majordomo@FreeBSD.ORG > with a line saying > > help > > in the message body. > > VIII. COMMAND SUMMARY FOR ADVANCED USERS > > In the description below items contained in []'s are optional. When > providing the item, do not include the []'s around it. Items in angle > brackets, such as
, are meta-symbols that should be replaced > by appropriate text without the angle brackets. > > It understands the following commands: > > subscribe [
] > Subscribe yourself (or
if specified) to the named . > > unsubscribe [
] > Unsubscribe yourself (or
if specified) from the named . > "unsubscribe *" will remove you (or
) from all lists. This > _may not_ work if you have subscribed using multiple addresses. > > get > Get a file related to . > > index > Return an index of files you can "get" for . > > which [
] > Find out which lists you (or
if specified) are on. > > who > Find out who is on the named . > > info > Retrieve the general introductory information for the named . > > intro > Retrieve the introductory message sent to new users. Non-subscribers > may not be able to retrieve this. > > lists > Show the lists served by this Majordomo server. > > help > Retrieve this message. > > end > Stop processing commands (useful if your mailer adds a signature). > > Commands should be sent in the body of an email message to > "Majordomo@FreeBSD.ORG". Multiple commands can be processed provided > each occurs on a separate line. > > Commands in the "Subject:" line are NOT processed. > > If you have any questions or problems, please contact > "Majordomo-Owner@FreeBSD.ORG". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 7: 4:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from 2888.com (hs1-48.irv.zyan.com [216.184.159.48]) by hub.freebsd.org (Postfix) with ESMTP id 5B2FC1507E for ; Thu, 20 Jan 2000 07:04:46 -0800 (PST) (envelope-from cheng@nanhai.gd.cn) Received: from glod003 [210.75.41.89] by 2888.com with ESMTP (SMTPD32-5.05) id A16EFB49013E; Thu, 20 Jan 2000 06:55:42 +0000 From: "thomas xiao" Reply-To: cheng@nanhai.gd.cn Message-ID: {7EF0F9D4-CF88-11D3-8B1F-5254AB1353CD}@glod003 Subject: sell ceramic title products To: trade@FreeBSD.ORG, all@FreeBSD.ORG X-Mailer: DiffondiCool V3.0 (W95/NT) Delfino Solutions (Build: Jun 14 1998) Mime-Version: 1.0 Date: Thu, 20 Jan 2000 22:51:06 +0800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-IMSTrailer: __IMail_5__ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear sir: We are one of the largest Ceramic tiles and Sanitary ware manufacturer in the China.specializing in producing wall and floor tiles with large production scale, complete product varieties and sizes and excellent prestige. our Group has introduced world advanced technologies and equipment from Germany and Italy in succession, and owned over 10 wall and floor tiles production lines and five polishing production lines, of which, the 4200T press and super large polishing line introduced from Italy are both the international top equipment. our Group which leads the trend in space, beautifies the living space and pursues the more modernized people and enterprise has integrated the Chinese essence and spirit, and constantly created the perfect products. our Group has made the products of numerous varieties, which can satisfy the different requirements of vast clients. The company has obtained the recognition of ISO9002 international quality assurance system, and produced the matched, serial, high-quality,practical and artistic products. Depending on its solid strength, we have already become the well-known brand highly praised by people in the construction and decoration industry. our Products Merit: 1.Anti-pollution By improving the formula for raw materials of the product,we have reduced the pores and the caliber of the pore on its ceramic tiles, and painted a layer of special coating on the tile surface, preventing the dirty liquid permeating into its products. This has solved the problem on "dirt absorbing" of polished ceramic tiles existing in China for a long time, and filled up the gap of domestic anti-pollution polished ceramic tile products. Passing the inspection of the Building Material Test Center of the state, the anti-pollution performance of the polished tile has reached the international standard: SO/DIS 10545/14-1994 2.Electronstatics resistant our ceramic tiles can be directly installed on the floor of the program controller room, computer room and microelectronic production and installation workshop to prevent the electrostatic function, or made into the electrostatics resistant moving floor by compounding the wooden shaving board and cement shaving board or other materials, or used as the floor or wall decoration in all places with electrostatic requirements such as the intelligent office, bank, post office and power control room. This product is dust-proof, with stable system resistance, complete pattern and convenient installation, and without the problem on aging and cracks in winter. 3.Radiation-free Inspected by the Building Material Test Center of the state, our ceramic tiles contain no radiative element. Being safe and reliable, they are the guarantee for health, and are the ideal selection for high-quality decoration. Dongpeng ceramic tiles are the ideal substitute products of natural stone materials. Contact us Now: -Tel. +86-757-6239656,6336141 mov:+86013923115367 =46ax. +86-757-6336141 -------------------------------------------------------------------- »¶Ó­µ½http://2888.com ÉêÇëÃâ·Ñ¡¢¶à¹¦ÄÜ¡¢´óÈÝÁ¿¡¢ÖÐÓ¢Îĵĵç×ÓÐÅÏä¡£ »¹ÓÐÈ«¸öÐÔ»¯±¨Ö½¼°Ã¿ÈÕÓʵݡ¢¾«ÃÀºØ¿¨¡¢×Ô¶¯ÃØÊé¡¢ËæÉíÐÅÏä¡¢ËæÉí±Ê¼Ç¡¢ Ãâ·ÑÍøÖ·¡¢¹©Çó¡¢ÕÐƸÇóÖ°¡¢ÍøÉÏÇéÔµÐÅÏ¢µÈµÈºÜʵÓõÄÃâ·Ñ·þÎñ¡£ ÊÀ½çÂÛ̳Íø(http://wforum.com )·Ç³£Óп´Í·£¬ºÜÖµµÃ²Î¼Ó¡£ Get your free, feature-rich, huge e-mailbox at http://2888.com --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 7: 6:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id AA0E514D42 for ; Thu, 20 Jan 2000 07:06:15 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id PAA02139; Thu, 20 Jan 2000 15:06:02 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <388720BE.607081AC@spnetctg.com> Date: Thu, 20 Jan 2000 15:06:01 -0000 (GMT) From: "Steve O'Hara-Smith" To: Satyajit Das Subject: Re: Majordomo results Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Jan-00 Satyajit Das wrote: > please note, i wrote email address: majordomo@freebsd.org > and in body : subscribe freebsd-question The list is called freebsd-questions not freebsd-question. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 9: 4:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DF1F915328 for ; Thu, 20 Jan 2000 09:04:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA51979; Thu, 20 Jan 2000 09:04:08 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Jan 2000 09:04:08 -0800 (PST) From: Matthew Dillon Message-Id: <200001201704.JAA51979@apollo.backplane.com> To: chrw Cc: freebsd-current@FreeBSD.ORG Subject: Re: swap_pager_getswapspace: failed (4.0-CURRENT) (fwd) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Helllo, : :I am experiencing problems regarding the swap handler. : :I am running 4.0-CURRENT FreeBSD 4.0-CURRENT #10 : :The box is running apache-1.3.9, cucipop v1.32, and sendmail 8.9.3, and :also runs as an NFS client. : :Kernel is configured with 512 MAXUSERS, swap device is 400MB with :real memory = 134201344 (131056K bytes) :avail memory = 126275584 (123316K bytes) : :Apache is is configured to run with :MinSpareServers 50 MaxSpareServers 100 : :The box runs without any problems, and not using very much swap space for :about 24 hours, then suddenly it generates the error message: : :Jan 19 13:03:03 hostname /kernel: swap_pager_getswapspace: failed : :and about 1 min later, it stops responding to any service requests. : :I would be gratefull for any hints or suggestions concerning what might :cause this fatal problem and possible solutions. : :CW It sounds like some process is running away on you. I recommend you open up several windows and run various system monitoring utilities in each one. 'vmstat 1', 'systat -vm 1', 'top', and so forth. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 9: 7:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mumble.frotz.net (mumble.frotz.net [216.15.97.250]) by hub.freebsd.org (Postfix) with SMTP id 08AFF15243 for ; Thu, 20 Jan 2000 09:07:19 -0800 (PST) (envelope-from swetland@frotz.net) Received: (qmail 33725 invoked by uid 1000); 20 Jan 2000 17:09:13 -0000 Date: Thu, 20 Jan 2000 09:09:13 -0800 From: "Brian J. Swetland" To: current@freebsd.org Subject: Re: devfs? Message-ID: <20000120090913.A32362@frotz.net> References: <20000119214258.A29986@frotz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6us In-Reply-To: <20000119214258.A29986@frotz.net>; from Brian J. Swetland on Wed, Jan 19, 2000 at 09:42:58PM -0800 Organization: Frotz Communications, Ltd. X-Mailer-Holy-War: Get Mutt, it bites! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ["Brian J. Swetland" ] > > I'm interested in mucking about with the devfs stuff a bit -- is there > currently any active developer/maintainer/docs? I grabbed the 4.0 > snapshot from the 17th, installed it, grabbed the kernel sources from > CVS, got stuff building and figured out how to enable DDB (not that > much different from the kdebug environment I'm used to from BeOS). I > figured I'd see if there was any more information than the sources. I see (after digging through some recent list archives) that I missed some discussion of this from as recent as a week ago. Also I notice that devfs does build, is mountable, is mountable, and shows a goodly number of the active devices in my system. Somebody mentioned the issue of figuring out when things change in sysctl/devfs/etc (and please excuse me if we've been here before), but there seem to be two non-polling solutions that are workable (though the second is much more work). Either provide /dev/devchanges or whatnot that interested processes can read (and block on) to receive change events (similar to the Linux cardmgr socket stuff) or provide general node monitoring (where processes can register for notifications for move/modify/remove/directorychanged with some entity that plugs into the vfs layer). The latter has some really neat effects (which BeOS makes heavy use of) generally involving not needing to poll for fs changes (input server node monitors /dev/input/... and sees new mice, etc as they're plugged in, GUI file browser gets events when third parties modify stuff in open windows, etc). Also, if anyone did reply to me over the last day or two, I've been having entertaining mail problems (now resolved) which probably resulted in me missing the reply. Brian -- Brian Swetland - swetland@frotz.net | "If I have hacked deeper than them, it http://www.frotz.net/swetland/ | is because I stand in their trenches." | -- Graham Nelson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 9:11:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax2-213.dialup.optusnet.com.au [198.142.241.213]) by hub.freebsd.org (Postfix) with ESMTP id 2E9A11504B for ; Thu, 20 Jan 2000 09:11:31 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 8089C55C3 for ; Fri, 21 Jan 2000 04:11:25 +1100 (EST) Message-Id: <4.2.2.20000121035238.01775a40@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 21 Jan 2000 04:11:24 +1100 To: freebsd-current@FreeBSD.ORG From: james Subject: sysinstall's fdisk/disklabel broken? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was going to use sysinstall's disklabel to repartition/relabel one of my drives, but when i went into it in the post-installation menu it said: No disks found! Please verify that your disk controller is being properly probed at boot time. See the Hardware Guide on the Documentation menu for clues on diagnosing this type of problem. My disks show up in dmesg as: ata-pci0: port 0x3000-0x300f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad2: ATA-0 disk at ata1 as master ad2: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 My kernel config (relevant bits) is: device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device atadisk0 options ATA_STATIC_ID options ATA_ENABLE_ATAPI_DMA Can somebody please fix this? Or is there a problem with my config? BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd about 2 days ago. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 9:53: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1901314E3F for ; Thu, 20 Jan 2000 09:52:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA52389; Thu, 20 Jan 2000 09:52:57 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Jan 2000 09:52:57 -0800 (PST) From: Matthew Dillon Message-Id: <200001201752.JAA52389@apollo.backplane.com> To: current@freebsd.org Subject: Still getting 'R/W mount of / denied ...' after valid fsck Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am still getting 'R/W mount of / denied' failures when rebooting a crashed -current machine. It thinks / is dirty but the fsck on it ran just fine. If I immediately /sbin/reboot again the machine comes up normally. The devices are all up to date (and in anycase couldn't be the cause since block devices no longer exist). This problem existed before and was fixed, but apparently someone has broken it again sometime in the last few weeks. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 10:44:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 3E39315105 for ; Thu, 20 Jan 2000 10:44:26 -0800 (PST) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id TAA19716; Thu, 20 Jan 2000 19:44:19 +0100 (CET) (envelope-from tobez) Date: Thu, 20 Jan 2000 19:44:19 +0100 From: Anton Berezin To: james Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall's fdisk/disklabel broken? Message-ID: <20000120194419.A16847@plab.ku.dk> References: <4.2.2.20000121035238.01775a40@mail.southcom.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <4.2.2.20000121035238.01775a40@mail.southcom.com.au>; from death@southcom.com.au on Fri, Jan 21, 2000 at 04:11:24AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 04:11:24AM +1100, james wrote: > I was going to use sysinstall's disklabel to repartition/relabel one > of my drives, but when i went into it in the post-installation menu it > said: > No disks found! > BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd > about 2 days ago. I just bumped into this, half an hour ago. :-) How old is your /stand/sysinstall (it does not get updated as a make world process)? # cd /usr/src/release/sysinstall && make all install Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 11: 7:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from herschel.bricoworks.com (sense-sea-MegaSub-1-446.oz.net [216.39.145.192]) by hub.freebsd.org (Postfix) with ESMTP id 1504914DC7 for ; Thu, 20 Jan 2000 11:03:52 -0800 (PST) (envelope-from moore@bricoworks.com) Received: from localhost (moore@localhost) by herschel.bricoworks.com (8.9.3/8.9.3) with ESMTP id LAA93745 for ; Thu, 20 Jan 2000 11:01:10 -0800 (PST) (envelope-from moore@herschel.bricoworks.com) Date: Thu, 20 Jan 2000 11:01:10 -0800 (PST) From: Tim Moore To: current@freebsd.org Subject: Error building current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CVS'uped today: cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools cannot open /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c: no such file "/usr/src/gnu/usr.bin/cc/cc_tools/../Makefile.inc", line 28: warning: "sed -e 's/.*\"\([^ \"]*\)[ \"].*/\1/' < /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c" returned non-zero status make: don't know how to make c-parse.gperf. Stop gcc/version.c is "dead" in my CVS repository. Has my repository been corrupted somehow? Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 11:24: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.jet.es (smtp.jet.es [194.179.100.25]) by hub.freebsd.org (Postfix) with ESMTP id 0BC5115291 for ; Thu, 20 Jan 2000 11:23:41 -0800 (PST) (envelope-from joanra@jet.es) Received: from daemon (infou333.jet.es [195.55.161.77]) by smtp.jet.es (8.9.3/8.9.1) with SMTP id UAA20202 for ; Thu, 20 Jan 2000 20:23:37 +0100 (MET) X-Envelope-To: Message-ID: <002801bf637c$dbf934a0$0164a8c0@daemon> From: "joanra" To: Subject: error wich devices ad* Date: Thu, 20 Jan 2000 20:27:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi when i run freebsd, display: Mounting root from ufs: /dev/ad2s1a no such device ad setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 mounting root from ufs: wd2s1a swapon: /dev/ad2s1b: device not configure Automatic reboot in ptogress can't open /dev/ad2s1a: device not configured my fstab: # Device Mountpoint /dev/ad2s1b none /dev/ad2s1a / /dev/ad2s1f /usr /dev/ad2s1e /var /dev/cd0c /cdrom cd9660 proc /proc anyone help me please? P.S: i recompiled a new kernel, and i create the new devices ad*, and my hd is seconday thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 11:53:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 72DCC14CCE for ; Thu, 20 Jan 2000 11:53:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA86214; Thu, 20 Jan 2000 11:53:36 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA16991; Thu, 20 Jan 2000 11:53:37 -0800 (PST) (envelope-from obrien) Date: Thu, 20 Jan 2000 11:53:36 -0800 From: "David O'Brien" To: Tim Moore Cc: current@freebsd.org Subject: Re: Error building current Message-ID: <20000120115336.A13225@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from moore@bricoworks.com on Thu, Jan 20, 2000 at 11:01:10AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote: > CVS'uped today: ... > gcc/version.c is "dead" in my CVS repository. Has my repository been > corrupted somehow? Please try again. Did you change release tags or something? Possibly checked out RELENG_3 on top of the HEAD or something? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 12:15:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from void.dynip.com (hobax2-213.dialup.optusnet.com.au [198.142.241.213]) by hub.freebsd.org (Postfix) with ESMTP id D756C14BE2 for ; Thu, 20 Jan 2000 12:15:38 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (windows.void.net [192.168.1.2]) by void.dynip.com (Postfix) with ESMTP id 97F3B55C3; Fri, 21 Jan 2000 07:15:31 +1100 (EST) Message-Id: <4.2.2.20000121071116.01b9c250@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 21 Jan 2000 07:15:28 +1100 To: Anton Berezin From: james Subject: Re: sysinstall's fdisk/disklabel broken? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20000120194419.A16847@plab.ku.dk> References: <4.2.2.20000121035238.01775a40@mail.southcom.com.au> <4.2.2.20000121035238.01775a40@mail.southcom.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 19:44 20/01/00 +0100, Anton Berezin wrote: >On Fri, Jan 21, 2000 at 04:11:24AM +1100, james wrote: > > > I was going to use sysinstall's disklabel to repartition/relabel one > > of my drives, but when i went into it in the post-installation menu it > > said: > > > No disks found! > > > BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd > > about 2 days ago. > >I just bumped into this, half an hour ago. :-) > >How old is your /stand/sysinstall (it does not get updated as a make >world process)? > ># cd /usr/src/release/sysinstall && make all install I tried that and it still didn't work. :( Somebody pointed out that it could be that i've accidently included non-PCI ata devices from LINT: device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 I'll get rid of them and recompile and reboot sometime soon and see how it goes. Don't know how much difference it'll make because: ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 is in my dmesg. I presume that means that those non-PCI ata device things weren't used anyway. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 13:49:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1CC1714EBF for ; Thu, 20 Jan 2000 13:49:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA14422 for freebsd-current@freebsd.org; Thu, 20 Jan 2000 22:40:58 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03546 for freebsd-current@freebsd.org; Thu, 20 Jan 2000 22:44:17 +0100 (CET) (envelope-from wilko) Date: Thu, 20 Jan 2000 22:44:17 +0100 From: Wilko Bulte To: "FreeBSD_current, mailing list" Subject: buildworld broken on alpha? Message-ID: <20000120224417.A3536@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG metoaddr.po.tmp etherent.po.tmp savefile.po.tmp bpf_filter.po.tmp bpf_image.po.tmp scanner.po.tmp version.po.tmp libpcap_p.a rm -f grammar.So pcap-bpf.So pcap.So inet.So gencode.So optimize.So nametoaddr.So etherent.So savefile.So bpf_filter.So bpf_image.So scanner.So version.So grammar.so pcap-bpf.so pcap.so inet.so gencode.so optimize.so nametoaddr.so etherent.so savefile.so bpf_filter.so bpf_image.so scanner.so version.so grammar.So.tmp pcap-bpf.So.tmp pcap.So.tmp inet.So.tmp gencode.So.tmp optimize.So.tmp nametoaddr.So.tmp etherent.So.tmp savefile.So.tmp bpf_filter.So.tmp bpf_image.So.tmp scanner.So.tmp version.So.tmp libpcap.so.2 libpcap.so libpcap.so.* libpcap.so libpcap_pic.a rm -f .depend /usr/src/lib/libpcap/GPATH /usr/src/lib/libpcap/GRTAGS /usr/src/lib/libpcap/GSYMS /usr/src/lib/libpcap/GTAGS ===> lib/libposix1e cd: can't cd to /usr/src/lib/libposix1e *** Error code 2 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 This is a fresh -current on alpha. On intel buildworld seems to continue. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 13:58:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2057B15318 for ; Thu, 20 Jan 2000 13:58:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA00569; Thu, 20 Jan 2000 22:57:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Still getting 'R/W mount of / denied ...' after valid fsck In-reply-to: Your message of "Thu, 20 Jan 2000 09:52:57 PST." <200001201752.JAA52389@apollo.backplane.com> Date: Thu, 20 Jan 2000 22:57:38 +0100 Message-ID: <567.948405458@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001201752.JAA52389@apollo.backplane.com>, Matthew Dillon writes: > I am still getting 'R/W mount of / denied' failures when rebooting a > crashed -current machine. It thinks / is dirty but the fsck on it ran > just fine. If I immediately /sbin/reboot again the machine comes up > normally. fsck fails to remount and fails to tell that, so despite the fact that the fs on the disk is clean the kernel doesn't get told. I belive Paul Saab is working on some improvements to fsck which will help this... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 14: 1:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 2340514DC4; Thu, 20 Jan 2000 14:01:52 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@woodstock.cs.rpi.edu [128.213.12.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA81879; Thu, 20 Jan 2000 16:30:21 -0500 (EST) Message-Id: <200001202130.QAA81879@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, dillon@backplane.com, gallatin@cs.duke.edu Subject: rpc.lockd Date: Thu, 20 Jan 2000 16:30:20 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is almost done. A working and very lightly tested version of the code will be made available on Monday (Jan 24). It should be considered alpha quality, I would not recommend running important NFS servers with this code. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 15:18:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C331C14E57; Thu, 20 Jan 2000 15:18:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA80601; Thu, 20 Jan 2000 16:18:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA06043; Thu, 20 Jan 2000 16:18:29 -0700 (MST) Message-Id: <200001202318.QAA06043@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: Error building current Cc: Tim Moore , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 20 Jan 2000 11:53:36 PST." <20000120115336.A13225@dragon.nuxi.com> References: <20000120115336.A13225@dragon.nuxi.com> Date: Thu, 20 Jan 2000 16:18:29 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000120115336.A13225@dragon.nuxi.com> "David O'Brien" writes: : On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote: : > CVS'uped today: : ... : > gcc/version.c is "dead" in my CVS repository. Has my repository been : > corrupted somehow? : : Please try again. Did you change release tags or something? Possibly : checked out RELENG_3 on top of the HEAD or something? I hit this problem as well. Put 'delete' in your cvsup file. Otherwise you'll get screwed. This is a misfeature of cvsup, imho, but if you don't have 'delete' in your cvsup file, versions that go away aren't removed and branch changes don't seem to happen... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 16:18:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.jet.es (smtp.jet.es [194.179.100.25]) by hub.freebsd.org (Postfix) with ESMTP id 3773514D7F for ; Thu, 20 Jan 2000 16:18:22 -0800 (PST) (envelope-from joanra@jet.es) Received: from daemon (infou381.jet.es [195.55.161.125]) by smtp.jet.es (8.9.3/8.9.1) with SMTP id BAA26137; Fri, 21 Jan 2000 01:13:12 +0100 (MET) Message-ID: <002c01bf63a5$537fc7a0$0164a8c0@daemon> From: "joanra" To: "Nick Hibma" Cc: Subject: RE: error wich devices ad* Date: Fri, 21 Jan 2000 01:19:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have done all what you have told me to do, but it still doesn't work. Now i have another problem, i have removed the DEVICES WD* (as you told me) and i can't mount partitions. It mounts WD on / but just as READ-ONLY and i can't do anything, How could i mount it whith writing permisions to continue trying things?? PS: the error message at init is the same that appeared me the first time when i make: mount /dev/as2s1f /usr (for example), the error is: mount: device block required please help -----Mensaje original----- De: Nick Hibma Para: joanra Fecha: jueves, 20 de enero de 2000 23:32 Asunto: Re: error wich devices ad* > >Boot with kernel.old and remake all your devices: > > cp /usr/src/etc/MAKEDEV /dev/MAKEDEV > cd /dev > sh MAKEDEV all > >and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then >do a to clean up your device tree: > > cd /dev > rm -f wcd* wd* rwcd* rwd* > >Nick > >On Thu, 20 Jan 2000, joanra wrote: > >> Hi when i run freebsd, display: >> >> Mounting root from ufs: /dev/ad2s1a >> no such device ad >> setrootbyname failed >> ffs_mountroot: can't find rootvp >> root mount failed: 6 >> mounting root from ufs: wd2s1a >> swapon: /dev/ad2s1b: device not configure >> Automatic reboot in ptogress >> can't open /dev/ad2s1a: device not configured >> >> my fstab: >> >> # Device Mountpoint >> /dev/ad2s1b none >> /dev/ad2s1a / >> /dev/ad2s1f /usr >> /dev/ad2s1e /var >> /dev/cd0c /cdrom cd9660 >> proc /proc >> >> anyone help me please? >> >> P.S: i recompiled a new kernel, and i create the new devices ad*, and my hd >> is seconday >> >> thanks >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > >-- >n_hibma@webweaving.org >n_hibma@freebsd.org USB project >http://www.etla.net/~n_hibma/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 16:30:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4048714D38 for ; Thu, 20 Jan 2000 16:29:54 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id QAA04215; Thu, 20 Jan 2000 16:29:36 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA20941; Thu, 20 Jan 2000 16:29:35 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id QAA28611; Thu, 20 Jan 2000 16:28:15 -0800 (PST) Message-ID: <3887A973.F632B014@softweyr.com> Date: Thu, 20 Jan 2000 17:33:55 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: current@freebsd.org Subject: Re: Problems with PCMCIA Cards References: <3885D9A4.8092A0F9@softweyr.com> <200001191626.JAA26180@harmony.village.org> <38863FC9.7B66BD3C@softweyr.com> <20000119201008.D33989@jade.chc-chimes.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > > On Wed, Jan 19, 2000 at 03:50:49PM -0700, Wes Peters wrote: > > > Mmm... Good point. This means updating code and compiling a new kernel > > every time Joe's hardware company sticks their own name on a generic OEM > > PCI or PCCard, doesn't it? I love this industry. > > Do the above and try and figure out and track down if the marketing information > matches what actually shows up on the product, now find out if it works exactly > the same or if there is some stupid quirk that Joe's Hardware added to the > chip.... Welcome to Bill Paul's hell. :-> I know, Bill, I know. I used to work for a company that made (well, OEM'd) PCMCIA cards, and made one of a very few PCMCIA-based routers in the world. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 16:54: 5 2000 Delivered-To: freebsd-current@freefall.freebsd.org Received: from rodia.zighelboim.com (rodia.zighelboim.com [204.27.67.106]) by hub.freebsd.org (Postfix) with SMTP id BFC7D152FD for ; Thu, 20 Jan 2000 16:54:01 -0800 (PST) (envelope-from mango@zighelboim.com) Received: from localhost (localhost [127.0.0.1]) by rodia.zighelboim.com (8.9.3/8.9.3) with ESMTP id SAA52944 for ; Thu, 20 Jan 2000 18:53:59 -0600 (CST) (envelope-from mango@zighelboim.com) Date: Thu, 20 Jan 2000 18:53:12 -0600 (CST) From: Raul Zighelboim To: freebsd-current@freefall.freebsd.org Subject: Current not compiling. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there the last 3 days of current 'make buildworld' have ended with: speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.a(rsa_lib.o): In function `RSA_new_method': rsa_lib.o(.text+0x91): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.a(err_all.o): In function `ERR_load_crypto_strings': err_all.o(.text+0x33): undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 Stop in /usr/src/secure. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 17:17:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9B49714C9E for ; Thu, 20 Jan 2000 17:17:47 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id RAA17651 for current@freebsd.org; Thu, 20 Jan 2000 17:41:17 -0800 (PST) Date: Thu, 20 Jan 2000 17:41:17 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: half-fix for stream.c Message-ID: <20000120174115.C14030@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you can find it at: http://www.freebsd.org/~alfred/tcp_fix.diff -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 17:39:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id C2AB315333 for ; Thu, 20 Jan 2000 17:39:01 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA28995; Thu, 20 Jan 2000 17:38:54 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id RAA44600; Thu, 20 Jan 2000 17:38:53 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA11083; Thu, 20 Jan 2000 17:38:52 -0800 (PST) Message-Id: <200001210138.RAA11083@salsa.gv.tsc.tdk.com> From: gdonl@tsc.tdk.com (Don Lewis) Date: Thu, 20 Jan 2000 17:38:52 -0800 In-Reply-To: Alfred Perlstein "half-fix for stream.c" (Jan 20, 5:41pm) X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: half-fix for stream.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 20, 5:41pm, Alfred Perlstein wrote: } Subject: half-fix for stream.c } you can find it at: } } http://www.freebsd.org/~alfred/tcp_fix.diff Don't you want to defer the checksum even further (after the bogus packets have been dropped)? It doesn't look like the change you made will save any unnecessary work. Also, it looks like you can save a few CPU cycles by only searching for wildcard sockets if the SYN flag is set, so only set the 6th argument to in_pcblookup_hash() if (thflags & TH_SYN) is true. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 17:44:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7A0ED1517E for ; Thu, 20 Jan 2000 17:44:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA19424; Thu, 20 Jan 2000 17:44:20 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA01860; Thu, 20 Jan 2000 17:44:17 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 20 Jan 2000 17:44:17 -0800 (PST) Message-Id: <200001210144.RAA01860@vashon.polstra.com> To: imp@village.org Subject: Re: Error building current In-Reply-To: <200001202318.QAA06043@harmony.village.org> References: <20000120115336.A13225@dragon.nuxi.com> <200001202318.QAA06043@harmony.village.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001202318.QAA06043@harmony.village.org>, Warner Losh wrote: > > I hit this problem as well. Put 'delete' in your cvsup file. > Otherwise you'll get screwed. This is a misfeature of cvsup, imho, I'm sorry you think so. I did it that way for backward compatibility with sup. If I hadn't made it compatible, I never could have persuaded anybody to try the software. Also, there are situations (e.g., maintaining local modifications in your repository) where delete should not be used. So it really needs to be an option. It would be better if the default were to delete and there was a "nodelete" option. But that wouldn't have been compatible. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 17:52: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D401415456 for ; Thu, 20 Jan 2000 17:51:54 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id SAA18540; Thu, 20 Jan 2000 18:15:23 -0800 (PST) Date: Thu, 20 Jan 2000 18:15:23 -0800 From: Alfred Perlstein To: Jim Bloom Cc: current@freebsd.org Subject: Re: half-fix for stream.c Message-ID: <20000120181523.F14030@fw.wintelcom.net> References: <20000120174115.C14030@fw.wintelcom.net> <3887B8AB.812B4D1A@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3887B8AB.812B4D1A@acm.org>; from bloom@acm.org on Thu, Jan 20, 2000 at 08:38:51PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jim Bloom [000120 18:02] wrote: > In you fix below, shouldn't the second block of NTOHx actually be HTONx. I > realize that this works because the functions are the same, but it should be > coded correctly. > > Jim Bloom > bloom@acm.org > > + NTOHL(th->th_seq); > + NTOHL(th->th_ack); > + NTOHS(th->th_win); > + NTOHS(th->th_urp); > + th->th_sum = in_cksum(m, len); > + if (th->th_sum) { > + tcpstat.tcps_rcvbadsum++; > + goto drop; > + } > + NTOHL(th->th_seq); > + NTOHL(th->th_ack); > + NTOHS(th->th_win); > + NTOHS(th->th_urp); hmm, that's prolly right, i've been on irc trying to discuss this with people and bit harried. I'm sure there's a better way to do this, but the idea is to move the checksum until after the pcb lookup, but i still have to look at this more. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 17:57: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (Postfix) with ESMTP id E859814F2C for ; Thu, 20 Jan 2000 17:56:57 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg136-175.ricochet.net [204.179.136.175]) by geocities.com (8.9.3/8.9.3) with ESMTP id RAA22312; Thu, 20 Jan 2000 17:56:40 -0800 (PST) Message-ID: <3887BDC4.A3AEBD35@geocities.com> Date: Thu, 20 Jan 2000 18:00:36 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: current@FreeBSD.ORG, Gerald Abshez Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? References: <387FDF2D.575DC537@geocities.com> <200001150528.VAA95955@apollo.backplane.com> <3883B0F4.60A1623F@geocities.com> <200001180226.SAA18343@apollo.backplane.com> <3886A6A9.12DA7F32@geocities.com> <200001200634.WAA42986@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :Fatal trap 12: page fault while in kernel mode > :fault virtual address = 0x8bc93139 > :fault code = supervisor read, page not present > :instruction pointer = 0x8:0xc018aa5f > :stack pointer = 0x10:0xc437be0c > :frame pointer = 0x10:0xc437be28 > :code segment = base 0x0, limit 0xfffff, type 0x1b > : = DPL 0, pres 1, def32 1, gran 1 > :processor eflags = interrupt enabled, resume, IOPL = 0 > :current process = 163 (smbd) > :interrupt mask = > :kernel: type 12 trap, code=0 > :Stopped at ip_input+0xc7: lock adcb $0x75,%al > :db> trace > :ip_input(c03ca500) at ip_input+0xc7 > :ipintr(c0209880,0,c021e3c2,c0156ac3,0) at ipintr+0x4b > :swi_net_next(c3fe1b40,c437bed0,c435bedc,0,0) at swi_net_next > :recvit(c410a400,7,c437bf20,0,c410a400) at recvit+0x101 > :recvfrom((c410a400,c437bf80,281b0ec8,6bbb,ffff) at recvfrom+0x6c > :syscall(bfbf002f,c437002f,bfbf002f,ffff,6bbb) at syscall+0x176 > :Xint0x80_syscall() at Xint0x80_syscall+0x26 > : > :By this time I am suspecting that it might be samba. So, I tried another scenario. > > This looks to me like a bug in either the ethernet driver or > the IP stack. > > Could you supply the output from 'dmesg'? With NFS and softupdates not > being the cause this isn't really in my court any more but maybe > someone else in -current has some ideas. > > -Matt > Matthew Dillon > Thanks for the help matt. Here is the 'dmesg'... arnee FreeBSD 4.0-CURRENT-20000118-08:18 #4: Tue Jan 18 13:17:49 PST 2000 root@groovinit:/usr/src/sys/compile/GROOVINIT Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 249919443 Hz CPU: Cyrix 6x86MX (249.92-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x601 Stepping = 1 DIR=0x1453 Features=0x80a135 real memory = 29360128 (28672K bytes) avail memory = 25792512 (25188K bytes) Preloaded elf kernel "kernel" at 0xc02c9000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ata-pci0: port 0x4000-0x400f,0xa8c42268-0xa8c4226b,0x35d8a0c0-0x35d8a0c7,0xc7cc0-0xc7cc3,0x42140728-0x4214072f irq 0 at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata-pci1: port 0xf080-0xf0bf,0xf7e0-0xf7e3,0xf790-0xf797,0xf7f0-0xf7f3,0xf7a0-0xf7a7 mem 0xffac0000-0xffadffff irq 11 at device 13.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xf7a0 irq 11 on ata-pci1 dc0: <82c169 PNIC 10/100BaseTX> port 0xf200-0xf2ff mem 0xffaaff00-0xffaaffff irq 9 at device 15.0 on pci0 dc0: Ethernet address: 00:a0:cc:58:fa:0f miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vga-pci0: port 0xf400-0xf47f mem 0xffaf0000-0xffafffff,0xff400000-0xff7fffff irq 10 at device 20.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ad4: ATA-4 disk at ata2 as master ad4: 16448MB (33687360 sectors), 33420 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA66 Mounting root from ufs:/dev/ad4s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 18: 4: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 4216615147 for ; Thu, 20 Jan 2000 18:03:47 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (Postfix) with ESMTP id 10E7217CD; Thu, 20 Jan 2000 18:03:36 -0800 (PST) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id SAA24542; Thu, 20 Jan 2000 18:03:35 -0800 (PST) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id SAA15304; Thu, 20 Jan 2000 18:03:34 -0800 (PST) Message-Id: <200001210203.SAA15304@mina.sr.hp.com> To: "joanra" Cc: "Nick Hibma" , current@FreeBSD.ORG Subject: Re: error wich devices ad* Reply-To: Darryl Okahata In-reply-to: Your message of "Fri, 21 Jan 2000 01:19:18 +0100." <002c01bf63a5$537fc7a0$0164a8c0@daemon> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 20 Jan 2000 18:03:33 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "joanra" wrote: > I have done all what you have told me to do, but it still doesn't work. Now > i have another problem, i have removed the DEVICES WD* (as you told me) and > i can't mount partitions. It mounts WD on / but just as READ-ONLY and i > can't do anything, How could i mount it whith writing permisions to continue > trying things?? At this point, you're slightly screwed -- you can probably fix your system, but it's going to take some work. I hope you have backups. > -----Mensaje original----- > De: Nick Hibma > > > > >Boot with kernel.old and remake all your devices: > > > > cp /usr/src/etc/MAKEDEV /dev/MAKEDEV > > cd /dev > > sh MAKEDEV all This will probably only work if you did an installworld, as MAKEDEV needs the new version of /sbin/mknod; the old, existing version won't work. Also note that "MAKEDEV all" doesn't make the slice devices (e.g., /dev/ad0s1a); you'll have to explicitly tell MAKEDEV to build those. If you didn't do an installworld, but did rebuild the kernel and attempted to mess with /dev, the general procedure for fixing this is: [ DANGER: I HAVE NOT TESTED THE FOLLOWING PROCEDURE. I AM CREATING THE FOLLOWING PROCEDURE FROM MEMORY, AND SO IT MAY BE MISSING KEY PARTS, WHICH COULD DESTROY ALL DATA ON YOUR SYSTEM. MAKE SURE YOU HAVE BACKED UP YOUR SYSTEM BEFORE TRYING ANY OF THE FOLLOWING. ] 1. Boot from a fixit floppy/CDROM. In the past, I've used a FreeBSD 3.3-RELEASE CDROM for this. [ I'm also amazed that the following procedure works, given that I'm running -current binaries under 3.3-RELEASE. ] 2. Mount the hard disk. I generally mount it as "/mnt". 3. Do (assuming /mnt as the mount point): cd /mnt mv dev dev.old mkdir dev cd dev cp /mnt/usr/src/etc/MAKEDEV . 4. If you did a buildworld: cp /mnt/usr/obj/usr/src/sbin/mknod/mknod /sbin If you did not do a buildworld (yes, this is messy, but it should work): cd /mnt/usr/src/sbin/mknod make cp mknod /sbin 5. Do: cp /mnt/usr/src/etc/group /etc # Needed for group "wheel" cd /mnt/dev sh ./MAKEDEV all sh ./MAKEDEV ad2s1a # since you use the ad2 slices NOTE 1: the first time you run MAKEDEV, it may complain about missing programs; if so, put/install the missing programs into the correct locations, and re-run MAKEDEV (until no errors occur). NOTE 2: You don't have to execute "sh MAKEDEV ad2s1b", etc., to make the other slice devices; running "sh MAKEDEV ad2s1a" will create all of the "ad2s1*" devices. > >and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then > >do a to clean up your device tree: > > > > cd /dev > > rm -f wcd* wd* rwcd* rwd* > > > >Nick > > > >On Thu, 20 Jan 2000, joanra wrote: > > > >> Hi when i run freebsd, display: > >> > >> Mounting root from ufs: /dev/ad2s1a > >> no such device ad > >> setrootbyname failed > >> ffs_mountroot: can't find rootvp > >> root mount failed: 6 > >> mounting root from ufs: wd2s1a > >> swapon: /dev/ad2s1b: device not configure > >> Automatic reboot in ptogress > >> can't open /dev/ad2s1a: device not configured > >> > >> my fstab: > >> > >> # Device Mountpoint > >> /dev/ad2s1b none > >> /dev/ad2s1a / > >> /dev/ad2s1f /usr > >> /dev/ad2s1e /var > >> /dev/cd0c /cdrom cd9660 > >> proc /proc > >> > >> anyone help me please? > >> > >> P.S: i recompiled a new kernel, and i create the new devices ad*, and my > hd > >> is seconday > >> > >> thanks > >> > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-current" in the body of the message > >> > > > >-- > >n_hibma@webweaving.org > >n_hibma@freebsd.org USB project > >http://www.etla.net/~n_hibma/ > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 19:27:13 2000 Delivered-To: freebsd-current@freefall.freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 09BE615187 for ; Thu, 20 Jan 2000 19:27:08 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12BUeP-00039B-00; Fri, 21 Jan 2000 05:22:17 +0200 From: Sheldon Hearn To: Raul Zighelboim Cc: freebsd-current@freefall.freebsd.org Subject: Re: Current not compiling. In-reply-to: Your message of "Thu, 20 Jan 2000 18:53:12 CST." Date: Fri, 21 Jan 2000 05:22:16 +0200 Message-ID: <12100.948424936@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jan 2000 18:53:12 CST, Raul Zighelboim wrote: > the last 3 days of current 'make buildworld' have ended with: > > speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' So you haven't been reading your -current mail for 3 days? Bad pussycat. :-) As stated several times on this mailing list by the guy who knows it's a problem and is working on it, the openssl build in CURRENT is picking up libcrypto in /usr/local/lib. Either pkg_delete or move aside your openssl installation. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 20:43:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id C390314D18 for ; Thu, 20 Jan 2000 20:43:49 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 28060 invoked from network); 21 Jan 2000 04:33:32 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 21 Jan 2000 04:33:32 -0000 Date: Fri, 21 Jan 2000 15:33:30 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Poul-Henning Kamp Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Still getting 'R/W mount of / denied ...' after valid fsck In-Reply-To: <567.948405458@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jan 2000, Poul-Henning Kamp wrote: > In message <200001201752.JAA52389@apollo.backplane.com>, Matthew Dillon writes: > > > I am still getting 'R/W mount of / denied' failures when rebooting a > > crashed -current machine. It thinks / is dirty but the fsck on it ran > > just fine. If I immediately /sbin/reboot again the machine comes up > > normally. > > fsck fails to remount and fails to tell that, so despite the fact > that the fs on the disk is clean the kernel doesn't get told. > > I belive Paul Saab is working on some improvements to fsck which > will help this... fsck is supposed to be improved already, but the improvements may have broken the (misconfigured) case where the root device is still a bdev. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 20:54:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6AA1C15218 for ; Thu, 20 Jan 2000 20:54:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA55592; Thu, 20 Jan 2000 20:02:01 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Jan 2000 20:02:01 -0800 (PST) From: Matthew Dillon Message-Id: <200001210402.UAA55592@apollo.backplane.com> To: arnee Cc: current@FreeBSD.ORG, Gerald Abshez Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? References: <387FDF2D.575DC537@geocities.com> <200001150528.VAA95955@apollo.backplane.com> <3883B0F4.60A1623F@geocities.com> <200001180226.SAA18343@apollo.backplane.com> <3886A6A9.12DA7F32@geocities.com> <200001200634.WAA42986@apollo.backplane.com> <3887BDC4.A3AEBD35@geocities.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Thanks for the help matt. Here is the 'dmesg'... : :arnee Hmm. If possible I would try backing away from the ata driver entirely and going back to the 'wd' driver. This isn't to say that the ata driver is the problem, but it *could* be the problem. A number of people have had problems with the ata driver. There isn't anything else in your config that strikes a chord... the rest of it looks ok to me. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 21:12:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id EE5DB153C3 for ; Thu, 20 Jan 2000 21:12:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 165DE1CA0; Fri, 21 Jan 2000 13:08:38 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: arnee , current@FreeBSD.ORG, Gerald Abshez Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? In-Reply-To: Message from Matthew Dillon of "Thu, 20 Jan 2000 20:02:01 PST." <200001210402.UAA55592@apollo.backplane.com> Date: Fri, 21 Jan 2000 13:08:38 +0800 From: Peter Wemm Message-Id: <20000121050838.165DE1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :Thanks for the help matt. Here is the 'dmesg'... > : > :arnee > > Hmm. If possible I would try backing away from the ata driver entirely > and going back to the 'wd' driver. This isn't to say that the ata > driver is the problem, but it *could* be the problem. A number of peopl e > have had problems with the ata driver. There isn't anything else in your > config that strikes a chord... the rest of it looks ok to me. Not possible. the wd driver doesn't support the Promise ATA-66 controllers that he is using. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 21:25:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from c000.sfo.cp.net (c000-h001.c000.sfo.cp.net [209.228.14.62]) by hub.freebsd.org (Postfix) with SMTP id DC27F14C18 for ; Thu, 20 Jan 2000 21:25:54 -0800 (PST) (envelope-from matt@boda.virtualave.net) Received: (cpmta 13945 invoked from network); 20 Jan 2000 21:21:16 -0800 Received: from slip-32-101-179-14.or.us.prserv.net (HELO boda.virtualave.net) (32.101.179.14) by smtp.worldspy.net with SMTP; 20 Jan 2000 21:21:16 -0800 X-Sent: 21 Jan 2000 05:21:16 GMT Message-ID: <3887ECC9.7A2625F5@boda.virtualave.net> Date: Thu, 20 Jan 2000 21:21:13 -0800 From: "Matt M." X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: cvsup 3.4-release to -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering what potential problems I am facing by going from 3.4-release to -current. I was told on irc that my chances may not be well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 21:26: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7DD9414C18 for ; Thu, 20 Jan 2000 21:26:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA56373; Thu, 20 Jan 2000 21:16:56 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Jan 2000 21:16:56 -0800 (PST) From: Matthew Dillon Message-Id: <200001210516.VAA56373@apollo.backplane.com> To: Peter Wemm Cc: arnee , current@FreeBSD.ORG, Gerald Abshez Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? References: <20000121050838.165DE1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Hmm. If possible I would try backing away from the ata driver entirely :> and going back to the 'wd' driver. This isn't to say that the ata :> driver is the problem, but it *could* be the problem. A number of peopl : e :> have had problems with the ata driver. There isn't anything else in your :> config that strikes a chord... the rest of it looks ok to me. : :Not possible. the wd driver doesn't support the Promise ATA-66 controllers :that he is using. : :Cheers, :-Peter Fubar. The crashes are occuring all over the place -- ip_input, ffs_blkfree, ip_output. Maybe it's a BIOS configuration problem... perhaps the ram is configured to be too fast or something like that. I don't know. This has all the earmarks of overclocking or a memory problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 21:37:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69]) by hub.freebsd.org (Postfix) with ESMTP id CE30915224 for ; Thu, 20 Jan 2000 21:37:45 -0800 (PST) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.9.3/ignatz) with ESMTP id VAA87604; Thu, 20 Jan 2000 21:34:55 -0800 (PST) Date: Thu, 20 Jan 2000 21:34:54 -0800 (PST) From: "f.johan.beisser" To: "Matt M." Cc: current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current In-Reply-To: <3887ECC9.7A2625F5@boda.virtualave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG that's very accurate. you'd be better off getting a SNAP image and upgrading your system from that. that is, if you really need to do it now. i'd just wait, untill the final release, since it's coming up Real Soon Now. -- jan On Thu, 20 Jan 2000, Matt M. wrote: > Just wondering what potential problems I am facing by going from > 3.4-release to -current. I was told on irc that my chances may not be > well. > +-----// f. johan beisser //------------------------------+ email: jan[at]caustic.org web: http://www.caustic.org/~jan "knowledge is power. power corrupts. study hard, be evil." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 21:49:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 04608155A3 for ; Thu, 20 Jan 2000 21:49:05 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA11760; Fri, 21 Jan 2000 00:52:52 -0500 From: Bill Paul Message-Id: <200001210552.AAA11760@skynet.ctr.columbia.edu> Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? To: arnee@geocities.com (arnee) Date: Fri, 21 Jan 2000 00:52:50 -0500 (EST) Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG, gerald@manhattanprojects.com In-Reply-To: <3887BDC4.A3AEBD35@geocities.com> from "arnee" at Jan 20, 2000 06:00:36 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 4697 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, arnee had to walk into mine and say: > FreeBSD 4.0-CURRENT-20000118-08:18 #4: Tue Jan 18 13:17:49 PST 2000 > root@groovinit:/usr/src/sys/compile/GROOVINIT > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 249919443 Hz > CPU: Cyrix 6x86MX (249.92-MHz 686-class CPU) Ack... > Origin = "CyrixInstead" Id = 0x601 Stepping = 1 DIR=0x1453 > Features=0x80a135 > real memory = 29360128 (28672K bytes) > avail memory = 25792512 (25188K bytes) > Preloaded elf kernel "kernel" at 0xc02c9000. > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard No, please... > pci0: on pcib0 > isab0: at device 1.0 on pci0 > isa0: on isab0 > ata-pci0: port > 0x4000-0x400f,0xa8c42268-0xa8c4226b,0x35d8a0c0-0x35d8a0c7,0xc7cc0-0xc7cc3,0x42140728-0x4214072f > irq 0 at device 1.1 on pci0 > ata-pci0: Busmastering DMA supported > ata-pci1: port > 0xf080-0xf0bf,0xf7e0-0xf7e3,0xf790-0xf797,0xf7f0-0xf7f3,0xf7a0-0xf7a7 mem > 0xffac0000-0xffadffff irq 11 at device 13.0 on pci0 > ata-pci1: Busmastering DMA supported Stop, you're killing me... > ata2 at 0xf7a0 irq 11 on ata-pci1 > dc0: <82c169 PNIC 10/100BaseTX> port 0xf200-0xf2ff mem 0xffaaff00-0xffaaffff irq 9 at > device 15.0 on pci0 Aieeeee! Oh for the love of *god*. Rip this thing out of your machine now. Put it on the ground. Stomp on it. Repeatedly. Then set it on fire. Bury the remains in the back yard. Then run - don't walk! - to your local computer store, put a crowbar in your wallet, and buy a better ethernet card. Don't whine, don't bitch, don't moan, don't complain that it works with Windows (actually, I bet it doesn't; not on that hardware, using bus master DMA for both controllers). Just do it. You have a Cyrix CPU, and I'm willing to bet you've overclocked it. ("What? You mean that might have some effect on the situation?") You have a PCI chipset which the probe messages don't even identify, and you're using not one but *two* bus master devices on it, one of which is a PNIC ethernet controller that can barely do bus master DMA correctly on a good day. Not only that, but you have two ATA controllers in this machine, one of which has no devices on it, and you have the damn hard disk on the *second* controller. Why do you have two controllers? Why not just use the built-in one! I'm also missing some information here since I arrived in the middle of this exchange. You didn't say if you're using 10Mbps or 100Mbps with this card. And you don't say what it's connected to (hub? switch? vendor? model?) Does this have something to do with the PNIC? Oh, probably. But I'm not going to even attempt to debug this. There's no way in hell I could duplicate this hardware configuration locally, and even if I did, I probably couldn't duplicate the exact same problem. And even if I could do *that*, I still wouldn't know how to fix it. I'm sorry, but I've pulled out enough hair over this damn chip. I'm sure I've wasted at least a couple months of my life trying to make this thing work reliably. I've added several software workarounds, I defaulted the stupid transmit threshold setting to store and forward mode. Well I've had it: no more. I'm through trying to bitchslap this rotten piece of silicon to its senses. I'm not going to go nuts every time somebody comes up with yet another oddball hardware combination. There's a limit to my patience and this chip has reached it. Now it's somebody else's turn to lose their sanity. I have the datasheet for the PNIC at http://www.freebsd.org/~wpaul/PNIC. You have the driver source. Somebody *else* try and figure it out, and then tell me then answer when you have it. That said, if you have overclocked this machine, then un-overclock it *right* *now* and never, ever do it again! PCI bus master DMA is goofy enough without people sticking their fingers in the works. Man, why does PC hardware have to suck so hard. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 21:59:59 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 9CEBE153EF; Thu, 20 Jan 2000 21:59:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 93CF81CD5E0; Thu, 20 Jan 2000 21:59:57 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 20 Jan 2000 21:59:57 -0800 (PST) From: Kris Kennaway To: Terje Elde Cc: current@FreeBSD.ORG Subject: Re: NO_IDEA In-Reply-To: <20000119213512.A40812@best.xti.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Terje Elde wrote: > Because of copyright issues OpenSSL is being built with -DNO_IDEA. IMHO > it's bad to do this for all systems, as it's only limited in some > countries. > > What I'm wondering if we could do is to add a COUNTRY=whatever, which > could be used to look up a value in a file which could provide information > about patent issues for algorithms like IDEA, as well as be a nice index > to which ftp server to use by default. This has already been suggested..it won't be implemented for 4.0, but might be looked at afterwards. The problem is the extra complexity it adds.. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 22:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from vajhost.nissho-ele.co.jp (fw.nissho-ele.co.jp [202.214.78.1]) by hub.freebsd.org (Postfix) with ESMTP id 724CA15232 for ; Thu, 20 Jan 2000 22:23:23 -0800 (PST) (envelope-from shimizu@nissho-ele.co.jp) Received: from scorpion.nissho-ele.co.jp (scorpion.nissho-ele.co.jp [10.10.33.203]) by vajhost.nissho-ele.co.jp (8.9.3/3.7W-9906111656) with ESMTP id PAA06670 for ; Fri, 21 Jan 2000 15:24:38 +0900 (JST) Received: from hawk ([10.10.33.95]) by scorpion.nissho-ele.co.jp (8.9.1b+Sun/8.9.1) with SMTP id PAA23135 for ; Fri, 21 Jan 2000 15:23:25 +0900 (JST) Message-Id: <200001210623.PAA23135@scorpion.nissho-ele.co.jp> X-Sender: shimizu@nissho-ele.co.jp X-Mailer: Windows Eudora Light Version 3.0.5-Jr1 (32) Date: Fri, 21 Jan 2000 15:26:22 +0900 To: freebsd-current@freebsd.org From: Keizo Shimizu Subject: boot.flp doesn't reconize dos partition Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I first made 50MB primary partition (MS-DOS's meaning) on my 20GB IDE disk and tried to use the rest for FreeBSD current. But boot.flp/mfsroot.flp made from current snapshots doesn't recognize dos partition. Anyone has any idea ? -- Keizo SHIMIZU ($B@6?eX*;0(B) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 20 23:20:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 793DE14C18 for ; Thu, 20 Jan 2000 23:19:54 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA61930 for freebsd-current@FreeBSD.ORG; Fri, 21 Jan 2000 09:19:22 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200001210719.JAA61930@zibbi.mikom.csir.co.za> Subject: make release broken To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Fri, 21 Jan 2000 09:19:22 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Make release on current is broken. It dies with: ------------------------------ >>> Filesystem is 1440 K, -52 left >>> 4000 bytes/inode, 10 left touch release.9 0 blocks Setting up CDROM distribution area 0 blocks 0 blocks 0 blocks 0 blocks ... 0 blocks 0 blocks 0 blocks cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ------------------------------- It looks like the handling of HARDWARE.TXT in release/Makefile is broken. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 0: 4:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0B0E314F97 for ; Fri, 21 Jan 2000 00:04:37 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA04952; Fri, 21 Jan 2000 08:54:59 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id IAA50642; Fri, 21 Jan 2000 08:55:00 +0100 (CET) (envelope-from wilko) Date: Fri, 21 Jan 2000 08:55:00 +0100 From: Wilko Bulte To: John Hay Cc: FreeBSD-current Subject: Re: make release broken Message-ID: <20000121085459.A50543@yedi.iaf.nl> References: <200001210719.JAA61930@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001210719.JAA61930@zibbi.mikom.csir.co.za>; from jhay@mikom.csir.co.za on Fri, Jan 21, 2000 at 09:19:22AM +0200 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 09:19:22AM +0200, John Hay wrote: > Make release on current is broken. It dies with: > > ------------------------------ > >>> Filesystem is 1440 K, -52 left > >>> 4000 bytes/inode, 10 left > touch release.9 > 0 blocks > Setting up CDROM distribution area > 0 blocks > 0 blocks > 0 blocks > 0 blocks > ... > 0 blocks > 0 blocks > 0 blocks > cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory > *** Error code 1 > > Stop in /usr/src/release. > *** Error code 1 > > Stop in /usr/src/release. > *** Error code 1 > > Stop in /usr/src/release. > ------------------------------- > > It looks like the handling of HARDWARE.TXT in release/Makefile is broken. Duh.. John Polstra is working on cvs-moving i386/HARDWARE.TXT to make this file the starting point for the generic HARDWARE.TXT There were some problems in doing this with cvs I guess this needs some time to get resolved. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 0:40:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 56A37151FF; Fri, 21 Jan 2000 00:40:44 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id RAA54431; Fri, 21 Jan 2000 17:40:41 +0900 (JST) To: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG Cc: FreeBSD98-hackers@jp.freebsd.org, nyan@jp.FreeBSD.ORG Subject: Re: indirection in bus space From: KATO Takenori In-Reply-To: Your message of "Mon, 27 Dec 1999 02:55:13 +0900" <19991227025513Z.kato@gneiss.eps.nagoya-u.ac.jp> References: <19991227025513Z.kato@gneiss.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000121174011G.kato@gneiss.eps.nagoya-u.ac.jp> Date: Fri, 21 Jan 2000 17:40:11 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 69 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you remember this topic? I have revised the indirection support patch. What I have changed are: - to make diff files more readable - introduce the bus_simple_create_bsh() that creates a bus_space_handle_tag from a base address. I have made PC98 GENERIC98 kernel and i386 LINT kernel and both of them can be compiled. Changed and new files are as follows: alpha/include/bus.h i386/include/bus.h i386/include/bus_at386.h (new file) i386/include/bus_pc98.h (new file) i386/i386/nexus.c i386/isa/isa.c dev/advansys/adv_isa.c dev/advansys/adv_pci.c pci/amd.c pci/isp_pci.c I put new files and diffs as follows: http://www.FreeBSD.ORG/~kato/busspace/index.html INDEX http://www.FreeBSD.ORG/~kato/busspace/alpha_bus.h.diff diff between old bus.h and new bus.h http://www.FreeBSD.ORG/~kato/busspace/i386_bus.h i386/include/bus.h http://www.FreeBSD.ORG/~kato/busspace/bus_at386.h i386/include/bus_at386.h http://www.FreeBSD.ORG/~kato/busspace/bus_at386.h.diff diff between old bus.h and bus_at386.h http://www.FreeBSD.ORG/~kato/busspace/bus_pc98.h i386/include/bus_pc98.h http://www.FreeBSD.ORG/~kato/busspace/bus_pc98.h.diff diff between old bus.h and bus_pc98.h http://www.FreeBSD.ORG/~kato/busspace/isa.c.diff diff of i386/isa/isa.c http://www.FreeBSD.ORG/~kato/busspace/nexus.c.diff diff of i386/i386/nexus.c http://www.FreeBSD.ORG/~kato/busspace/adv_isa.c.diff diff of dev/advansys/adv_isa.c http://www.FreeBSD.ORG/~kato/busspace/adv_pci.c.diff diff of dev/advansys/adv_pci.c http://www.FreeBSD.ORG/~kato/busspace/amd.c.diff diff of pci/amd.c http://www.FreeBSD.ORG/~kato/busspace/isp_pci.c.diff diff of pci/isp_pci.c Thank you. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 1:15:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1C92B15452 for ; Fri, 21 Jan 2000 01:15:40 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A8F181CA0; Fri, 21 Jan 2000 17:15:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilko Bulte Cc: John Hay , FreeBSD-current Subject: Re: make release broken In-Reply-To: Message from Wilko Bulte of "Fri, 21 Jan 2000 08:55:00 +0100." <20000121085459.A50543@yedi.iaf.nl> Date: Fri, 21 Jan 2000 17:15:36 +0800 From: Peter Wemm Message-Id: <20000121091536.A8F181CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > On Fri, Jan 21, 2000 at 09:19:22AM +0200, John Hay wrote: [..] > > cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory > > *** Error code 1 [..] > > It looks like the handling of HARDWARE.TXT in release/Makefile is broken. > > Duh.. John Polstra is working on cvs-moving i386/HARDWARE.TXT to make > this file the starting point for the generic HARDWARE.TXT > > There were some problems in doing this with cvs > > I guess this needs some time to get resolved. OK, here's the deal.. There is already a texts/HARDWARE.TXT, but it's been cvs rm'ed from -current. Since it's in use on 3.4, we can't just clobber it. So, if you want to move i386/HARDWARE.TXT up a level you're just going to have to copy the file and cvs add it in the new location. This will "revive" it in -current. We can't do anything about the lost history in i386/HARDWARE.TXT. Well, strictly speaking it can be merged but it's much more painful than it's worth. :-/ Just re-add the file and lets get on with it. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 1:53:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 6A3651543F for ; Fri, 21 Jan 2000 01:53:27 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id JAA01195; Fri, 21 Jan 2000 09:48:42 GMT (envelope-from n_hibma@webweaving.org) Date: Fri, 21 Jan 2000 09:48:42 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: joanra Cc: current@freebsd.org Subject: RE: error wich devices ad* In-Reply-To: <002c01bf63a5$537fc7a0$0164a8c0@daemon> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, joanra wrote: > I have done all what you have told me to do, but it still doesn't work. Now > i have another problem, i have removed the DEVICES WD* (as you told me) and > i can't mount partitions. It mounts WD on / but just as READ-ONLY and i > can't do anything, How could i mount it whith writing permisions to continue > trying things?? When in single user mode: mount -u -o rw / and then mount -a -t ufs When you then type mount you should see / /var /usr mounted. When you then exit from single user mode it should boot. > PS: the error message at init is the same that appeared me the first time > when i make: mount /dev/as2s1f /usr (for example), the error is: > mount: device block required You are sure you have an up to date kernel? This sounds very much like you have an up to date userland but an old kernel. Block devices have been removed from the kernel some weeks ago. Nick > > please help > -----Mensaje original----- > De: Nick Hibma > Para: joanra > Fecha: jueves, 20 de enero de 2000 23:32 > Asunto: Re: error wich devices ad* > > > > > >Boot with kernel.old and remake all your devices: > > > > cp /usr/src/etc/MAKEDEV /dev/MAKEDEV > > cd /dev > > sh MAKEDEV all > > > >and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then > >do a to clean up your device tree: > > > > cd /dev > > rm -f wcd* wd* rwcd* rwd* > > > >Nick > > > >On Thu, 20 Jan 2000, joanra wrote: > > > >> Hi when i run freebsd, display: > >> > >> Mounting root from ufs: /dev/ad2s1a > >> no such device ad > >> setrootbyname failed > >> ffs_mountroot: can't find rootvp > >> root mount failed: 6 > >> mounting root from ufs: wd2s1a > >> swapon: /dev/ad2s1b: device not configure > >> Automatic reboot in ptogress > >> can't open /dev/ad2s1a: device not configured > >> > >> my fstab: > >> > >> # Device Mountpoint > >> /dev/ad2s1b none > >> /dev/ad2s1a / > >> /dev/ad2s1f /usr > >> /dev/ad2s1e /var > >> /dev/cd0c /cdrom cd9660 > >> proc /proc > >> > >> anyone help me please? > >> > >> P.S: i recompiled a new kernel, and i create the new devices ad*, and my > hd > >> is seconday > >> > >> thanks > >> > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-current" in the body of the message > >> > > > >-- > >n_hibma@webweaving.org > >n_hibma@freebsd.org USB project > >http://www.etla.net/~n_hibma/ > > > > > > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 2: 3:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 4217715198 for ; Fri, 21 Jan 2000 02:03:46 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id PAA49540 for ; Fri, 21 Jan 2000 15:50:31 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 21 Jan 2000 15:50:30 +0600 (NS) From: Max Khon To: current@freebsd.org Subject: collect2 and cplus-dem.c in binutils Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! will collect2 be built in base system? btw binutils have in their libiberty cplus-dem.c which is incompatible with that which is used in gcc 2.9x.x. the result is broken -frepo in egcs and gcc-devel ports in -current. I filed one PR about it but I was rather tired yesterday and did not noticed that C++ demangler in gcc is more recent than that one in binutils. Affected tools are addr2line, nm, objdump and (most important) ld. The problem can be fixed by using demangle.h and cplus-dem.c from gcc when building libiberty for binutils. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 2:26:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 7394315333 for ; Fri, 21 Jan 2000 02:26:06 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id VAA00659; Fri, 21 Jan 2000 21:25:35 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Fri, 21 Jan 2000 21:25:34 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: "f.johan.beisser" Cc: "Matt M." , current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Jan 2000, f.johan.beisser wrote: > that's very accurate. you'd be better off getting a SNAP image and > upgrading your system from that. > > that is, if you really need to do it now. > > i'd just wait, untill the final release, since it's coming up Real Soon > Now. > > -- jan > > On Thu, 20 Jan 2000, Matt M. wrote: > > > Just wondering what potential problems I am facing by going from > > 3.4-release to -current. I was told on irc that my chances may not be > > well. > > > > +-----// f. johan beisser //------------------------------+ > email: jan[at]caustic.org web: http://www.caustic.org/~jan > "knowledge is power. power corrupts. study hard, be evil." Um, I thought we were supposed to be testing 4.0-current _before_ it goes -release... I am going to upgrade my workstation (from 3.4 to 4.0) over this weekend, to help further the cause... -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 4:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from inetfw.sonycsl.co.jp (inetfw.SonyCSL.Co.Jp [203.137.129.4]) by hub.freebsd.org (Postfix) with ESMTP id 5867E14C33 for ; Fri, 21 Jan 2000 04:17:51 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.9.3+3.2W/3.7Ws3/99071615/smtpfeed 1.01) with ESMTP id VAA94287; Fri, 21 Jan 2000 21:17:50 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.7Ws3/hotaka/99101212) with ESMTP id VAA23338; Fri, 21 Jan 2000 21:17:49 +0900 (JST) To: current@freebsd.org Cc: Yoichi Shinoda Subject: pci_write_config arg order X-Mailer: Mew version 1.95b3 on Emacs 20.5 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000121211748V.kjc@csl.sony.co.jp> Date: Fri, 21 Jan 2000 21:17:48 +0900 From: Kenjiro Cho X-Dispatcher: imput version 991025(IM133) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG pci_write_config() and pci_cfgwrite() defined in sys/pci/pcivar.h have an unusual argument order: pci_read_config(dev, reg, width) pci_write_config(dev, reg, val, width) pci_cfgread(cfg, offset, size) pci_cfgwrite(cfg, offset, val, size) Apparently, pcisupport.c and isp_pci.c misplace the 3rd and 4th args. Could someone take a look? Reported by Yoichi Shinoda -Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 4:43: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id D7BEF153F0 for ; Fri, 21 Jan 2000 04:42:54 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id SAA67465 for ; Fri, 21 Jan 2000 18:42:51 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 21 Jan 2000 18:42:51 +0600 (NS) From: Max Khon To: current@freebsd.org Subject: rtld-elf, java + tya Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! applet_viewer bombs out with a lot of stuff in the output like this (until killed -9): ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 lark:~/bin$ latest jdk-1.1.8 port, tya 1.4, -current built from sources from 19 Jan /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 5:21:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id BA53914E88 for ; Fri, 21 Jan 2000 05:21:29 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id IAA14392 for ; Fri, 21 Jan 2000 08:21:28 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA09544; Fri, 21 Jan 2000 08:20:58 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id IAA64454 for freebsd-current@freebsd.org; Fri, 21 Jan 2000 08:20:54 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001211320.IAA64454@bb01f39.unx.sas.com> Subject: make release failure (HARDWARE.TXT) To: freebsd-current@freebsd.org Date: Fri, 21 Jan 2000 08:20:54 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've seen the following error for the last 2 days since the make release change to HARDWARE.TXT. CVS shows this file as removed from the head of the tree at revision 1.30 but the Makefile is unconditionally attempting to copy them in the ftp.1 & cdrom.1 targets, followed by optionally concatinating the ${MACHINE_ARCH} specific file. It appears that DIST_DOCS needs to be broken up into common doc or the for loops over DIST_DOCS needs to become smarter. I have supplied a patch which I beleive fixes the problem by allowing files misssing to be ignored. This of course means accidental errors in DOC file removal or location movement become harder to detect until someone actually checks the doc and sees that portions are missing. The patch and actual error condition follow. Thanks! John FreeBSD(root)/snap/release/usr/src/release %cvs diff -u Makefile Index: Makefile =================================================================== RCS file: /mirror/ncvs/src/release/Makefile,v retrieving revision 1.527 diff -u -r1.527 Makefile --- Makefile 2000/01/19 22:48:50 1.527 +++ Makefile 2000/01/21 13:25:01 @@ -527,7 +527,11 @@ @cd ${RD} && find floppies -print | cpio -dumpl ${FD} @cd ${RD}/dists && find . -print | cpio -dumpl ${FD} @for i in ${DIST_DOCS}; do \ - cp ${.CURDIR}/texts/$${i} ${FD}; \ + if [ -f ${.CURDIR}/texts/$${i} ]; then \ + cp ${.CURDIR}/texts/$${i} ${FD}; \ + else \ + echo "=== No common ${i} documentation" > ${FD}/$${i}; \ + fi; \ if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ echo "=== Platform specifics for ${MACHINE_ARCH}" >> ${FD}/$${i}; \ cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} >> ${FD}/$${i}; \ @@ -560,7 +564,11 @@ @echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf @echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf @for i in ${DIST_DOCS}; do \ - cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \ + if [ -f ${.CURDIR}/texts/$${i} ]; then \ + cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \ + else \ + echo "=== No common ${i} documentation" > ${FD}/$${i}; \ + fi; \ if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ echo "=== Platform specifics for ${MACHINE_ARCH}" >> ${FD}/$${i}; \ cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} >> ${CD_DISC1}/$${i}; \ touch release.9 0 blocks Setting up CDROM distribution area 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory *** Error code 1 Stop in /usr/src/release. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 6:37:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 1C1F115430 for ; Fri, 21 Jan 2000 06:37:28 -0800 (PST) (envelope-from daeron@wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id BBE851FC4; Fri, 21 Jan 2000 15:37:25 +0100 (CET) Date: Fri, 21 Jan 2000 15:37:25 +0100 From: Pascal Hofstee To: Max Khon Cc: current@freebsd.org Subject: Re: rtld-elf, java + tya Message-ID: <20000121153725.A70181@shadowmere.student.utwente.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from fjoe@iclub.nsu.ru on Fri, Jan 21, 2000 at 06:42:51PM +0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 06:42:51PM +0600, Max Khon wrote: > hi, there! > > applet_viewer bombs out with a lot of stuff in the output like this > (until killed -9): > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 I just today experienced the Exact same assertion failure when trying to shutdown the GIMP. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 6:42:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.jet.es (smtp.jet.es [194.179.100.25]) by hub.freebsd.org (Postfix) with ESMTP id D6DD515403 for ; Fri, 21 Jan 2000 06:42:33 -0800 (PST) (envelope-from joanra@jet.es) Received: from daemon (info55.jet.es [194.224.180.55]) by smtp.jet.es (8.9.3/8.9.1) with SMTP id PAA26318; Fri, 21 Jan 2000 15:41:06 +0100 (MET) Message-ID: <000c01bf641e$90468380$0164a8c0@daemon> From: "joanra" To: "Nick Hibma" Cc: Subject: RE: error wich devices ad* Date: Fri, 21 Jan 2000 15:47:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # mount -u -o rw / mount: block device required what is the problem? :( thanks -----Mensaje original----- De: Nick Hibma Para: joanra CC: current@freebsd.org Fecha: viernes, 21 de enero de 2000 10:53 Asunto: RE: error wich devices ad* >On Fri, 21 Jan 2000, joanra wrote: > >> I have done all what you have told me to do, but it still doesn't work. Now >> i have another problem, i have removed the DEVICES WD* (as you told me) and >> i can't mount partitions. It mounts WD on / but just as READ-ONLY and i >> can't do anything, How could i mount it whith writing permisions to continue >> trying things?? > >When in single user mode: > > mount -u -o rw / > >and then > > mount -a -t ufs > >When you then type > > mount > >you should see > / > /var > /usr >mounted. When you then exit from single user mode it should boot. > >> PS: the error message at init is the same that appeared me the first time >> when i make: mount /dev/as2s1f /usr (for example), the error is: >> mount: device block required > >You are sure you have an up to date kernel? This sounds very much like >you have an up to date userland but an old kernel. Block devices have >been removed from the kernel some weeks ago. > >Nick > >> >> please help >> -----Mensaje original----- >> De: Nick Hibma >> Para: joanra >> Fecha: jueves, 20 de enero de 2000 23:32 >> Asunto: Re: error wich devices ad* >> >> >> > >> >Boot with kernel.old and remake all your devices: >> > >> > cp /usr/src/etc/MAKEDEV /dev/MAKEDEV >> > cd /dev >> > sh MAKEDEV all >> > >> >and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then >> >do a to clean up your device tree: >> > >> > cd /dev >> > rm -f wcd* wd* rwcd* rwd* >> > >> >Nick >> > >> >On Thu, 20 Jan 2000, joanra wrote: >> > >> >> Hi when i run freebsd, display: >> >> >> >> Mounting root from ufs: /dev/ad2s1a >> >> no such device ad >> >> setrootbyname failed >> >> ffs_mountroot: can't find rootvp >> >> root mount failed: 6 >> >> mounting root from ufs: wd2s1a >> >> swapon: /dev/ad2s1b: device not configure >> >> Automatic reboot in ptogress >> >> can't open /dev/ad2s1a: device not configured >> >> >> >> my fstab: >> >> >> >> # Device Mountpoint >> >> /dev/ad2s1b none >> >> /dev/ad2s1a / >> >> /dev/ad2s1f /usr >> >> /dev/ad2s1e /var >> >> /dev/cd0c /cdrom cd9660 >> >> proc /proc >> >> >> >> anyone help me please? >> >> >> >> P.S: i recompiled a new kernel, and i create the new devices ad*, and my >> hd >> >> is seconday >> >> >> >> thanks >> >> >> >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> >> with "unsubscribe freebsd-current" in the body of the message >> >> >> > >> >-- >> >n_hibma@webweaving.org >> >n_hibma@freebsd.org USB project >> >http://www.etla.net/~n_hibma/ >> > >> > >> >> > >-- >n_hibma@webweaving.org >n_hibma@freebsd.org USB project >http://www.etla.net/~n_hibma/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 7: 1:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 7DADF15494 for ; Fri, 21 Jan 2000 07:01:39 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 540AA199A; Tue, 18 Jan 2000 18:18:41 -0500 (EST) Date: Tue, 18 Jan 2000 18:18:41 -0500 From: Will Andrews To: Frank Mayhar Cc: FreeBSD Current Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Message-ID: <20000118181840.H457@argon.blackdawn.com> References: <20000118085605.E482@mojave.worldwide.lemis.com> <200001181048.CAA07011@realtime.exit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001181048.CAA07011@realtime.exit.com>; from frank@exit.com on Tue, Jan 18, 2000 at 02:48:25AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote: > Interestingly, I rebuilt world with the latest pccardd changes and, > suddenly, the 589D started working perfectly. Unfortunately, the > 574BT doesn't work at all now. It appears to configure properly, but > it doesn't transmit or receive. My 574BT works if you hardcode the pccardd IRQ to 9. I did this by editing rc.pccard and replaced the pccard line with: pccardd -i 9 -f ${pccard_conf} It works fine for me. I think there's something wrong with pccardd, and that's why it keeps using IRQs I don't even have specified in pccard.conf. I should do more research on this, though. --Will To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 7: 9:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 3903C14F3E for ; Fri, 21 Jan 2000 07:09:16 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 69D071984; Fri, 21 Jan 2000 10:09:13 -0500 (EST) Date: Fri, 21 Jan 2000 10:09:13 -0500 From: Will Andrews To: "Matt M." Cc: current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current Message-ID: <20000121100913.C436@argon.blackdawn.com> References: <3887ECC9.7A2625F5@boda.virtualave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3887ECC9.7A2625F5@boda.virtualave.net>; from matt@boda.virtualave.net on Thu, Jan 20, 2000 at 09:21:13PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 20, 2000 at 09:21:13PM -0800, Matt M. wrote: > Just wondering what potential problems I am facing by going from > 3.4-release to -current. I was told on irc that my chances may not be > well. You should read /usr/src/UPDATING (for -CURRENT). I won't say you shouldn't use it since 4.0-RELEASE is probably going out within a month, and bugs need to be worked out. However, I wouldn't upgrade if I was using that particular machine for production purposes. My -CURRENT box can crash to hell for all I care. My -STABLE will stay -STABLE since it needs to be depended on. -- Will Andrews 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 7:43:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 34EEE14A2C for ; Fri, 21 Jan 2000 07:43:36 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id PAA01759; Fri, 21 Jan 2000 15:27:25 GMT (envelope-from n_hibma@webweaving.org) Date: Fri, 21 Jan 2000 15:27:25 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: joanra Cc: current@freebsd.org Subject: RE: error wich devices ad* In-Reply-To: <000c01bf641e$90468380$0164a8c0@daemon> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your userland is out of sync with your kernel. I suggest you tell us what steps you took to get here. I'm referring to steps like: - make world - compile your kernel - update /etc/fstab and the likes - update /dev/MAKEDEV and other things you could come up with that might be related to modifying your system files. See if you can get someone to send you a kernel. Boot from the first CD, go to Fix-it/CDROM and then copy that kernel for example from a floppy onto the mounted root partition as kernel.CURRENT and reboot again, booting the new kernel.CURRENT. Big question: Why do you run current if you don't read the mail current@freebsd.org? Nick On Fri, 21 Jan 2000, joanra wrote: > # mount -u -o rw / > mount: block device required > > what is the problem? :( > > thanks > > -----Mensaje original----- > De: Nick Hibma > Para: joanra > CC: current@freebsd.org > Fecha: viernes, 21 de enero de 2000 10:53 > Asunto: RE: error wich devices ad* > > > >On Fri, 21 Jan 2000, joanra wrote: > > > >> I have done all what you have told me to do, but it still doesn't work. > Now > >> i have another problem, i have removed the DEVICES WD* (as you told me) > and > >> i can't mount partitions. It mounts WD on / but just as READ-ONLY and i > >> can't do anything, How could i mount it whith writing permisions to > continue > >> trying things?? > > > >When in single user mode: > > > > mount -u -o rw / > > > >and then > > > > mount -a -t ufs > > > >When you then type > > > > mount > > > >you should see > > / > > /var > > /usr > >mounted. When you then exit from single user mode it should boot. > > > >> PS: the error message at init is the same that appeared me the first time > >> when i make: mount /dev/as2s1f /usr (for example), the error is: > >> mount: device block required > > > >You are sure you have an up to date kernel? This sounds very much like > >you have an up to date userland but an old kernel. Block devices have > >been removed from the kernel some weeks ago. > > > >Nick > > > >> > >> please help > >> -----Mensaje original----- > >> De: Nick Hibma > >> Para: joanra > >> Fecha: jueves, 20 de enero de 2000 23:32 > >> Asunto: Re: error wich devices ad* > >> > >> > >> > > >> >Boot with kernel.old and remake all your devices: > >> > > >> > cp /usr/src/etc/MAKEDEV /dev/MAKEDEV > >> > cd /dev > >> > sh MAKEDEV all > >> > > >> >and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then > >> >do a to clean up your device tree: > >> > > >> > cd /dev > >> > rm -f wcd* wd* rwcd* rwd* > >> > > >> >Nick > >> > > >> >On Thu, 20 Jan 2000, joanra wrote: > >> > > >> >> Hi when i run freebsd, display: > >> >> > >> >> Mounting root from ufs: /dev/ad2s1a > >> >> no such device ad > >> >> setrootbyname failed > >> >> ffs_mountroot: can't find rootvp > >> >> root mount failed: 6 > >> >> mounting root from ufs: wd2s1a > >> >> swapon: /dev/ad2s1b: device not configure > >> >> Automatic reboot in ptogress > >> >> can't open /dev/ad2s1a: device not configured > >> >> > >> >> my fstab: > >> >> > >> >> # Device Mountpoint > >> >> /dev/ad2s1b none > >> >> /dev/ad2s1a / > >> >> /dev/ad2s1f /usr > >> >> /dev/ad2s1e /var > >> >> /dev/cd0c /cdrom cd9660 > >> >> proc /proc > >> >> > >> >> anyone help me please? > >> >> > >> >> P.S: i recompiled a new kernel, and i create the new devices ad*, and > my > >> hd > >> >> is seconday > >> >> > >> >> thanks > >> >> > >> >> > >> >> > >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> >> with "unsubscribe freebsd-current" in the body of the message > >> >> > >> > > >> >-- > >> >n_hibma@webweaving.org > >> >n_hibma@freebsd.org USB project > >> >http://www.etla.net/~n_hibma/ > >> > > >> > > >> > >> > > > >-- > >n_hibma@webweaving.org > >n_hibma@freebsd.org USB project > >http://www.etla.net/~n_hibma/ > > > > > > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 8:46:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id BEC57153F1 for ; Fri, 21 Jan 2000 08:46:40 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id LAA87347 for freebsd-current@freebsd.org; Fri, 21 Jan 2000 11:49:29 -0500 (EST) From: Brian Hechinger Message-Id: <200001211649.LAA87347@entropy.tmok.com> Subject: passwords got smashed by make installworld To: freebsd-current@freebsd.org Date: Fri, 21 Jan 2000 11:49:29 -0500 (EST) Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm just reporting this, i have no real info, other than it happened. i installed the 20000114 snapshot. SUPed -current, uhm, two days ago i think. did a make buildworld at that time. then yesterday evening i had a chance to reboot my machine so i did make installworld (as well as a new kernel with some options i wanted that i forgot to put in) rebooted, tried to log in and couldn't. not as root, not as my regular user. wanted to track it down but didn't have the time to, just needed my box to work. all i had to do was boot into single user mode and use passwd to set the passwords again. somebody should look at wednesdays' snapshot (unless this is known and fixed) and see why a make installworld would bash passwords. or maybe look at the 14th's snapshot, ah, whatever, in a rush, gotta go. keep up the good work. -current rocks. -wonko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 8:53: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5AB1015498; Fri, 21 Jan 2000 08:53:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 485A81CD5F0; Fri, 21 Jan 2000 08:53:06 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 21 Jan 2000 08:53:06 -0800 (PST) From: Kris Kennaway To: wonko@entropy.tmok.com Cc: freebsd-current@freebsd.org Subject: Re: passwords got smashed by make installworld In-Reply-To: <200001211649.LAA87347@entropy.tmok.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Brian Hechinger wrote: > rebooted, tried to log in and couldn't. not as root, not as my regular user. Sounds like you clobbered your DES libcrypt libraries with non-DES ones, and now you can't use your DES passwords. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 9: 9: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id ADEA115512 for ; Fri, 21 Jan 2000 09:09:05 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA22881; Fri, 21 Jan 2000 09:09:04 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA11095; Fri, 21 Jan 2000 09:09:03 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 21 Jan 2000 09:09:03 -0800 (PST) Message-Id: <200001211709.JAA11095@vashon.polstra.com> To: fjoe@iclub.nsu.ru Subject: Re: rtld-elf, java + tya In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > hi, there! > > applet_viewer bombs out with a lot of stuff in the output like this > (until killed -9): > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 Really?! Augh. Naturally this comes just hours after I have merged the latest changes into -stable *sigh*. Could you please make sure your src/libexec/rtld-elf is up-to-date? rtld.c should be at revision 1.41. Then if you can give me a stack backtrace it would help a lot. Thanks, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 9: 9:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id C31B615501 for ; Fri, 21 Jan 2000 09:09:37 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id JAA06286; Fri, 21 Jan 2000 09:09:39 -0800 Date: Fri, 21 Jan 2000 09:09:39 -0800 Message-Id: <200001211709.JAA06286@www.geocrawler.com> To: freebsd-current@freebsd.org Subject: problems with mylex raid scsi From: "Steven Jurczyk" Reply-To: "Steven Jurczyk" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Steven Jurczyk" Be sure to reply to that address. I try to install FreeBSD 4.0-CURRENT snapshot on server with have mylex accele raid 250 controler. FreeBSD installs on it without any problems, but can't boot from it. I try 2 and 8 GB BIOS mode, also FreeBSD and BIOS geometry (trick with small dos partition). Depending of situation boot loader shows Invalid slice, registers (int 0d, err 00, eip a658, cs f000) and System halted info or boot manager can't find loader (it bells when I select F1 - FreeBSD). steve Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 9:30: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DDE9F154F0 for ; Fri, 21 Jan 2000 09:29:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA84630; Fri, 21 Jan 2000 10:29:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA12226; Fri, 21 Jan 2000 10:29:56 -0700 (MST) Message-Id: <200001211729.KAA12226@harmony.village.org> To: Will Andrews Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Cc: Frank Mayhar , FreeBSD Current In-reply-to: Your message of "Tue, 18 Jan 2000 18:18:41 EST." <20000118181840.H457@argon.blackdawn.com> References: <20000118181840.H457@argon.blackdawn.com> <20000118085605.E482@mojave.worldwide.lemis.com> <200001181048.CAA07011@realtime.exit.com> Date: Fri, 21 Jan 2000 10:29:56 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000118181840.H457@argon.blackdawn.com> Will Andrews writes: : On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote: : > Interestingly, I rebuilt world with the latest pccardd changes and, : > suddenly, the 589D started working perfectly. Unfortunately, the : > 574BT doesn't work at all now. It appears to configure properly, but : > it doesn't transmit or receive. : : My 574BT works if you hardcode the pccardd IRQ to 9. I did this by : editing rc.pccard and replaced the pccard line with: : : pccardd -i 9 -f ${pccard_conf} : : It works fine for me. I think there's something wrong with pccardd, and : that's why it keeps using IRQs I don't even have specified in : pccard.conf. I should do more research on this, though. Are you sure that pccard_conf isn't set to /etc/pccard.conf.sample? I've *NEVER* seen pccardd use interrupts that it wasn't told about, and I've tried many times to reproduce this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 9:32:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id A76541558B for ; Fri, 21 Jan 2000 09:32:41 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id KAA12063; Fri, 21 Jan 2000 10:32:40 -0700 (MST) Date: Fri, 21 Jan 2000 10:32:40 -0700 (MST) From: "Russell L. Carter" Message-Id: <200001211732.KAA12063@vip.consys.com> To: fjoe@iclub.nsu.ru, jdp@polstra.com Subject: Re: rtld-elf, java + tya Cc: current@FreeBSD.ORG In-Reply-To: <200001211709.JAA11095@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen it with yesterdays current and libc_r threads, and it's intermittent. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 9:41:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 35CB91550C for ; Fri, 21 Jan 2000 09:41:46 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id JAA01795; Fri, 21 Jan 2000 09:41:45 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id JAA19914; Fri, 21 Jan 2000 09:41:44 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200001211741.JAA19914@realtime.exit.com> Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) In-Reply-To: <200001211729.KAA12226@harmony.village.org> from Warner Losh at "Jan 21, 2000 10:29:56 am" To: imp@village.org (Warner Losh) Date: Fri, 21 Jan 2000 09:41:44 -0800 (PST) Cc: andrews@technologist.com (Will Andrews), frank@exit.com (Frank Mayhar), current@FreeBSD.ORG (FreeBSD Current) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <20000118181840.H457@argon.blackdawn.com> Will Andrews writes: > : On Tue, Jan 18, 2000 at 02:48:25AM -0800, Frank Mayhar wrote: > : > Interestingly, I rebuilt world with the latest pccardd changes and, > : > suddenly, the 589D started working perfectly. Unfortunately, the > : > 574BT doesn't work at all now. It appears to configure properly, but > : > it doesn't transmit or receive. > : My 574BT works if you hardcode the pccardd IRQ to 9. I did this by > : editing rc.pccard and replaced the pccard line with: > : > : pccardd -i 9 -f ${pccard_conf} > : > : It works fine for me. I think there's something wrong with pccardd, and > : that's why it keeps using IRQs I don't even have specified in > : pccard.conf. I should do more research on this, though. > Are you sure that pccard_conf isn't set to /etc/pccard.conf.sample? > I've *NEVER* seen pccardd use interrupts that it wasn't told about, > and I've tried many times to reproduce this. Just for the record, it turned out that the problem I saw with the 574BT was cured by moving pcic0 from irq 11 (which the PCI bus had appropriated) to irq 10. I put the 574 on my last free IRQ, 3. (Don't you hate laptops?) Many, many thanks to Matt Dodd and Warner Losh for their help, patience, suggestions and code! They were terrific. Now I'm looking forward to the newcard cardbus support so I can finally use the 575BT which came with the laptop. (Tapping fingers impatiently. :-) -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 9:43:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0C0921540A for ; Fri, 21 Jan 2000 09:43:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA84725; Fri, 21 Jan 2000 10:43:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA12462; Fri, 21 Jan 2000 10:43:16 -0700 (MST) Message-Id: <200001211743.KAA12462@harmony.village.org> To: frank@exit.com Subject: Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th) Cc: andrews@technologist.com (Will Andrews), current@FreeBSD.ORG (FreeBSD Current) In-reply-to: Your message of "Fri, 21 Jan 2000 09:41:44 PST." <200001211741.JAA19914@realtime.exit.com> References: <200001211741.JAA19914@realtime.exit.com> Date: Fri, 21 Jan 2000 10:43:16 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001211741.JAA19914@realtime.exit.com> Frank Mayhar writes: : Now I'm looking forward to the newcard cardbus support so I can finally use : the 575BT which came with the laptop. (Tapping fingers impatiently. :-) Hope you are tapping something soft :-) Wouldn't want you to hurt yourself, or have others hurt you from the annoying racket :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10: 9:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mf006.infoweb.ne.jp (mf006.infoweb.ne.jp [210.131.99.16]) by hub.freebsd.org (Postfix) with ESMTP id DC5221550A for ; Fri, 21 Jan 2000 10:09:43 -0800 (PST) (envelope-from br_wink@anet.ne.jp) Received: from default by mf006.infoweb.ne.jp (8.9.3+3.2W/3.7W-10/13/99) with SMTP id DAA06010 for ; Sat, 22 Jan 2000 03:09:35 +0900 Message-ID: <1835.948478209230@anet.ne.jp> Date: Sat, 22 Jan 2000 03:10:09 +0900 (JST) From: b-support Reply-To: br_wink@anet.ne.jp To: "freebsd-current@freebsd.org" Subject: =?iso-2022-jp?B?GyRCOiMkLCVBJWMlcyU5JEckOSRoISoyPkVQGyhCGyhC?= =?iso-2022-jp?B?GyRCTz88dUlVQ2YhYyVAJSYlczwrRjA5PUNbIWQbKEIbKEI=?= Mime-Version: 1.0 Content-Type: text/plain; charset =ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B"#"#(B $B7HBSEEOC(B $B:G?75!$N:G?75!\$7$/$O2<5-#U#R#L$K%"%/%;%9$7$F2<$5$$!#(B http://cwj.to/link.cgi/ID=441/GO=linker/cwm/keitai_shop/gekiyasu/free.html $B"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#(B $BFMA3$N%a!<%k<:Ni$$$?$7$^$9!#$b$7!"A4$/6=L#$NL5$$FbMF$H(B $B$*46$8$K$J$kMM$G$7$?$i!"$*!'%3%9%b%a%G%#%"(B $B=j:_CO!'Bg:e;TMd@n6h(B $B!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1(B $B#1#17nCf=\$h$je$N%]%8%7%g%s$,3NJ]$G$-$^$9$h!#(B $B4X@>CO6h0J30$NJ}$O!"8r495!4pCO6I$,40@.$9$k$^$G(B $B2>2q0wEPO?$G>R2p3hF0$G$-$^$9!#2>EPO?$OL5NA$G$9!*(B $B!1!1!1!1!1!1!1!1!1(B $B#17nKv$K;%KZ!"El5~!";0=E!"9-Eg4pCO6I$,2TF03+;O$7$^$9!#(B $B<+F09=C[$J$N$GAa$$!$A!"EPO?$7$?!$A$G$9!#(B $B:#8=:_!"CN$j9g$$$NCf7xBgJ*%M%C%H%o!<%+!<$K@<$r$+$1$F$$$^$9$N$G!"(B $B$"$J$?$NEPO?$N$[$&$,Aa$1$l$P$=$NJ}$?$A$,$"$J$?$N%@%&%s$K(B $B$D$/2DG=@-$O$+$J$j$"$j$^$9!#(B $B$H$j$"$($:$@$1$NEPO?$b#O#K!#3hF0$9$k$7$J$$$O$^$C$?$/<+M3!#(B $B$b$&>/$7MM;R$r8+$?$$?M$bEPO?$@$1$J$i7P:QE*IiC4$O$$$C$5$$$J$7!#(B $B$I$&$;EPO?$O%?%@$@$+$i!&!&!&!!$=$l$G$b%@%&%s$OIU$-$^$9!#(B $B$H$j$"$($:EPO?$7$F$*$1$P!"$$$:$l$$$$$3$H$"$j!*!*!*(B $B4JC1$J35MW$r=q$$$F$*$-$^$9$N$G>\$7$/$O(B $B2qpJs#B#O#X!J(B06-6379-6583$B!!Am9g%a%K%e!<$O(B7000#$B!K(B $B$G0z$-=P$7$F$/$@$5$$!#(B $B$3$3$,%]%$%s%H!*!*(B $B!c0lHLBhFs&IJR2pNA$,H/@8(B $B#7!%3FCO$N%j!<%@!<$K$O!"7HBSEEOC$NDj3[%5!<%S%9$,$J$s$HL5NA!*(B $B!c2q0wFCE5!d(B $B#1!%@lMQ@~$rMxMQ$7$?;T30EEOC$NDj3[NA6b%5!<%S%9(B $B#2!%$o$:$+#1#0?M$N>R2p$G2qe$K$h$kG[J,$"$j(B $B#3!%8D?M8~$1%[!<%`%Z!<%8!J:n@.$+$i8x3+$^$G#1%v7n#8#3#31_!K(B $B#4!%%Q%=%3%sK\BN#3#9#8#0#01_$GHNGd!J?7IJ!K(B $B#5!%#N#T#T$h$j%Q%=%3%s$NL5NAG[I[!J(BIBM$B@=!K(B $B#6!%#F#A#X>pJs%\%C%/%9$,L5NA%l%s%?%k(B $B#7!%#W#e#b#T#V!J%$%s%?!<%M%C%HC@\%\!<%J%9(B $BAH?%$r>&IJ$K1~$8$F<+M3JQ49!J%f%K%l%Y%k!"%P%$%J%j!e$NG[J,$"$j!JG/6bE*%\!<%J%9!K(B $B#5?M>R2p$G$J$s$HKh7n$N2qHq$,L5NA$G$9!*(B $B2>EPO?$r$44uK>$5$l$k>l9g$O!"2<$NEPO??=$79~$_Ms$K(B $BI,MW;v9`$r5-F~$N>e!"JVAw$7$F2<$5$$!#(B $B!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~(B $B2>EPO??=$79~$_Ms(B ----------------------------------------------------------- $B!J%U%j%,%J!K!!(B ----------------------------------------------------------- $B$*L>A0(B ----------------------------------------------------------- $B!J%U%j%,%J!K(B ----------------------------------------------------------- $B")(B ($BI,$:(B7$B7eHV9f$r$45-F~$/$@$5$$(B) $B$4=;=j(B ----------------------------------------------------------- $BEEOCHV9f(B ----------------------------------------------------------- FAX$BHV9f(B ----------------------------------------------------------- $BEE;R%a!<%k%"%I%l%9(B ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10:12: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id A15AF1540A for ; Fri, 21 Jan 2000 10:12:00 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 19083 invoked by uid 1001); 21 Jan 2000 18:11:57 -0000 Date: 21 Jan 2000 10:11:57 -0800 Date: Fri, 21 Jan 2000 10:11:57 -0800 From: Bill Swingle To: current@freebsd.org Subject: even more breakage in current Message-ID: <20000121101157.A18956@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I updated my source tree around 10pm PST last night (01/20) and made world only to find it broken this morning. I reupdated my tree just now and it doesnt look like any files that might fix this have been touched. Anyone else seeing this? cc -pg -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/gen/wait3.c -o wait3.po cc -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.o cc -DPROF -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.po /tmp/ccg65684.s: Assembler messages: /tmp/cco65681.s: Assembler messages: /tmp/cco65681.s:361: Error: invalid character '(' in opcode /tmp/ccg65684.s:361: Error: invalid character '(' in opcode *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error root@rooter:/usr/src$ cvs -Rq update -PdA U etc/MAKEDEV U etc/pccard.conf.sample U usr.sbin/pccard/pccardd/cardd.c U usr.sbin/pccard/pccardd/cardd.h U usr.sbin/pccard/pccardd/file.c root@rooter:/usr/src$ -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10:23:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3E3E514C8C for ; Fri, 21 Jan 2000 10:23:11 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA23236; Fri, 21 Jan 2000 10:23:10 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA11556; Fri, 21 Jan 2000 10:23:09 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 21 Jan 2000 10:23:09 -0800 (PST) Message-Id: <200001211823.KAA11556@vashon.polstra.com> To: rcarter@pinyon.org Subject: Re: rtld-elf, java + tya In-Reply-To: <200001211732.KAA12063@vip.consys.com> References: <200001211732.KAA12063@vip.consys.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001211732.KAA12063@vip.consys.com>, Russell L. Carter wrote: > I've seen it with yesterdays current and libc_r threads, and it's intermittent. Did this problem just start, or has it been there for awhile? I haven't changed the dynamic linker in -current since January 9, and I'm wondering if a more recent change in a different part of the system is causing trouble. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10:30:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id CE19914CFA for ; Fri, 21 Jan 2000 10:30:36 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id KAA19611; Fri, 21 Jan 2000 10:29:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001211829.KAA19611@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: rcarter@pinyon.org, current@FreeBSD.ORG Subject: Re: rtld-elf, java + tya In-reply-to: Your message of "Fri, 21 Jan 2000 10:23:09 PST." <200001211823.KAA11556@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 10:29:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am fairly certain that Java + TYA worked before Jan 7 -- haven't upgraded my system since then. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10:31:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id CF3FD14D35 for ; Fri, 21 Jan 2000 10:31:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id KAA19611; Fri, 21 Jan 2000 10:29:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001211829.KAA19611@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: rcarter@pinyon.org, current@FreeBSD.ORG Subject: Re: rtld-elf, java + tya In-reply-to: Your message of "Fri, 21 Jan 2000 10:23:09 PST." <200001211823.KAA11556@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 10:29:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am fairly certain that Java + TYA worked before Jan 7 -- haven't upgraded my system since then. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10:43:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id F2E2D14CED for ; Fri, 21 Jan 2000 10:43:10 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id LAA12234; Fri, 21 Jan 2000 11:43:09 -0700 (MST) Date: Fri, 21 Jan 2000 11:43:09 -0700 (MST) From: "Russell L. Carter" Message-Id: <200001211843.LAA12234@vip.consys.com> To: jdp@polstra.com, rcarter@pinyon.org Subject: Re: rtld-elf, java + tya Cc: current@freebsd.org In-Reply-To: <200001211823.KAA11556@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |From jdp@polstra.com Fri Jan 21 11:23:14 2000 | |In article <200001211732.KAA12063@vip.consys.com>, |Russell L. Carter wrote: |> I've seen it with yesterdays current and libc_r threads, and it's intermittent. | |Did this problem just start, or has it been there for awhile? I |haven't changed the dynamic linker in -current since January 9, and |I'm wondering if a more recent change in a different part of the |system is causing trouble. I first saw it yesterday, and I've been building pretty regularly on a tracking current box. This is a CORBA C++ application linking against ACE/TAO, i.e., not easy to simplify. I think I saw it maybe twice out of 50 builds. I'm away from that box right now, I'll pay more attention when I get back to it tonight, and let you know if I can get any repeatability. Russell | |John |-- | John Polstra jdp@polstra.com | John D. Polstra & Co., Inc. Seattle, Washington USA | "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa | | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 10:43:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 306FF15503; Fri, 21 Jan 2000 10:43:41 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA23348; Fri, 21 Jan 2000 10:43:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA11593; Fri, 21 Jan 2000 10:43:39 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 21 Jan 2000 10:43:39 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: Please help spread the CVSup mirror load more evenly Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is another in my series of occasional nags to try to get people to use some of the less heavily loaded CVSup mirrors. In the US alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. The newest, cvsup8, is a very high-capacity and well-connected site, yet hardly anybody is using it. Please give it a try! You can find the full list of mirrors worldwide at: http://www.freebsd.org/handbook/mirrors-cvsup.html Remember, the mirrors are equivalent in the sense that they get their updates from the master server at the same intervals (hourly). There is nothing "better" about the lower-numbered mirrors, and they don't get their updates any sooner or more reliably. In fact, the higher-numbered mirrors often have faster hardware simply because they're newer. Also, in particular, there's nothing special about cvsup.FreeBSD.org -- it's simply an alias for cvsup1 and it gets its updates the same way at the same intervals from the same master server as all the other mirrors. To choose a mirror site, try pinging the mirrors in your country. Pick one with a low packet loss rate. The round trip time doesn't matter very much as long as it doesn't undergo wild variations. Second, pick a site that's not too heavily loaded. If your update _ever_ fails because the server is too busy, then you should try a different mirror -- because there are many mirrors that aren't even close to their full loads even at the busiest of times. Thanks for your cooperation. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11: 7:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id B9AB914FB7 for ; Fri, 21 Jan 2000 11:07:35 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id TAA03968; Fri, 21 Jan 2000 19:07:29 GMT (envelope-from joe) Date: Fri, 21 Jan 2000 19:07:29 +0000 From: Josef Karthauser To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121190729.C58872@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 10:43:39AM -0800, John Polstra wrote: > > To choose a mirror site, try pinging the mirrors in your country. > Pick one with a low packet loss rate. The round trip time doesn't > matter very much as long as it doesn't undergo wild variations. > Second, pick a site that's not too heavily loaded. If your update > _ever_ fails because the server is too busy, then you should try a > different mirror -- because there are many mirrors that aren't even > close to their full loads even at the busiest of times. > > Thanks for your cooperation. > > John Can you make cvsup accept multiple servers to try in it's configuration file? Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:10:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id D74C11556B for ; Fri, 21 Jan 2000 11:10:19 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id LAA20090; Fri, 21 Jan 2000 11:09:30 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001211909.LAA20090@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: Your message of "Fri, 21 Jan 2000 10:43:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 11:09:30 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If the user does specifiy a cvsup , can you decide for the user which server is best based upon some simple statistic? -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:11:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 25AEC154F9; Fri, 21 Jan 2000 11:11:19 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA23524; Fri, 21 Jan 2000 11:11:18 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA11686; Fri, 21 Jan 2000 11:11:17 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 21 Jan 2000 11:11:17 -0800 (PST) Message-Id: <200001211911.LAA11686@vashon.polstra.com> To: jdp@polstra.com Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , I wrote: > To choose a mirror site, try pinging the mirrors in your country. I have been reminded that a few mirrors (cvsup8 in particular) filter pings. Don't take ping failures as a certain indication that the server is down. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:11:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B50E4154FC for ; Fri, 21 Jan 2000 11:11:41 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA23529; Fri, 21 Jan 2000 11:11:40 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA11701; Fri, 21 Jan 2000 11:11:40 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 21 Jan 2000 11:11:40 -0800 (PST) Message-Id: <200001211911.LAA11701@vashon.polstra.com> To: joe@pavilion.net Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <20000121190729.C58872@florence.pavilion.net> References: <20000121190729.C58872@florence.pavilion.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can you make cvsup accept multiple servers to try in it's configuration > file? I'll add that to the to-do list. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:13:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id EA66E154F4 for ; Fri, 21 Jan 2000 11:13:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA23552; Fri, 21 Jan 2000 11:13:28 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA11732; Fri, 21 Jan 2000 11:13:28 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 21 Jan 2000 11:13:28 -0800 (PST) Message-Id: <200001211913.LAA11732@vashon.polstra.com> To: hasty@rah.star-gate.com Subject: Re: rtld-elf, java + tya In-Reply-To: <200001211829.KAA19611@rah.star-gate.com> References: <200001211829.KAA19611@rah.star-gate.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001211829.KAA19611@rah.star-gate.com>, Amancio Hasty wrote: > I am fairly certain that Java + TYA worked before Jan 7 -- haven't > upgraded my system since then. Yes, that assert that failed wasn't in the dynamic linker on January 7. What I need to know is: did it start failing soon after January 9, or only just in the past few days? Also I really need a stack trace of a failure to analyze. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:23:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 31BED15498 for ; Fri, 21 Jan 2000 11:23:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id LAA20233; Fri, 21 Jan 2000 11:22:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001211922.LAA20233@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: Your message of "Fri, 21 Jan 2000 11:11:17 PST." <200001211911.LAA11686@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 11:22:33 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So have the cvsup client do the pinging to the server and extract its current work load or other vital statistic. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:23:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 88CC315644 for ; Fri, 21 Jan 2000 11:23:55 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA23613; Fri, 21 Jan 2000 11:23:54 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA11779; Fri, 21 Jan 2000 11:23:54 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 21 Jan 2000 11:23:54 -0800 (PST) Message-Id: <200001211923.LAA11779@vashon.polstra.com> To: hasty@rah.star-gate.com Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001211909.LAA20090@rah.star-gate.com> References: <200001211909.LAA20090@rah.star-gate.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001211909.LAA20090@rah.star-gate.com>, Amancio Hasty wrote: > If the user does specifiy a cvsup , can you decide for the user which > server is best based upon some simple statistic? Some day I hope it's possible, but there's nothing like that implemented currently. Also there are some problems that must be solved first. CVSup needs a way to ensure that your "update" won't in fact be a step backward in time. For example, suppose you update twice in rapid succession, first from server A and then from server B. Both servers update hourly, but at different times. You happen to hit them at a point where A has updated more recently than B. In that case you'll be unhappy because your second "update" will instead be a "downdate" (backdate? bad date?). This is solvable, but not as easily as you might think. Lots of complications arise when, for example, you interrupt an update in the middle such that some files have been updated while others haven't. There is discussion on all this in the mailing list archives somewhere. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:40: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (Postfix) with ESMTP id 6078D15009 for ; Fri, 21 Jan 2000 11:40:01 -0800 (PST) (envelope-from arnee@geocities.com) Received: from geocities.com (mg136-175.ricochet.net [204.179.136.175]) by geocities.com (8.9.3/8.9.3) with ESMTP id LAA01691; Fri, 21 Jan 2000 11:39:05 -0800 (PST) Message-ID: <3888B6CC.B7842087@geocities.com> Date: Fri, 21 Jan 2000 11:43:09 -0800 From: arnee X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG, gerald@manhattanprojects.com Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? References: <200001210552.AAA11760@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > Of all the gin joints in all the towns in all the world, arnee had to walk > into mine and say: hehehhe... Oh no!! What did I walk into... a quicksand! :-) > Ack... > No, please... > Stop, you're killing me... > Aieeeee! > > Oh for the love of *god*. Rip this thing out of your machine now. Put it > on the ground. Stomp on it. Repeatedly. Then set it on fire. Bury the > remains in the back yard. Then run - don't walk! - to your local computer > store, put a crowbar in your wallet, and buy a better ethernet card. hahhaha!! :-) I knew I would get this... I got this machine for free and used to run BeOS on it. It is *not* a priority to have FreeBSD or any other OS running on this machine. Yes, I've thought of not even taking the damn thing... but since I have another closet to place it in, what the heck... I'll play with it. > Don't whine, don't bitch, don't moan, don't complain that it works with > Windows (actually, I bet it doesn't; not on that hardware, using bus > master DMA for both controllers). Just do it. Hmm... and yes not the best compare to my 3Coms, but I never thought that the ethernet card would be that bad. And I would never base my decisions ("..whine, ..bitch, ..moan, ..complain") of using it because the hardware works with win9x. I have 2 linux boxes, a freebsd 3.2 box, and 2 other win9x boxes using FA310TX and they work just fine. A couple of them connected to a 10Mbps 3com hub (with 2 other boxes with 3Com NICs) and the others, plus this machine, connected to a 100Mbps Netgear hub (with other boxes with 3Com NICs). > You have a Cyrix CPU, and I'm willing to bet you've overclocked it. ("What? > You mean that might have some effect on the situation?") You have a PCI > chipset which the probe messages don't even identify, and you're using > not one but *two* bus master devices on it, one of which is a PNIC ethernet > controller that can barely do bus master DMA correctly on a good day. Not > only that, but you have two ATA controllers in this machine, one of which has > no devices on it, and you have the damn hard disk on the *second* controller. > Why do you have two controllers? Why not just use the built-in one! Yes, one would wonder why. But, it is some what of a catch 22 installing 4.0-current. I am using a 17gig (Ultra-ATA/66 capable) harddrive with a MB bios that can only handle 8.4gig (Ultra-ATA/33) harddrive. And since I have a Promise Ultra-ATA/66 controller that 4.0-current supports.. why not! Yes, I know there are other, in fact many other ways to make it work... one is by compiling a 3.4 kernel with a patch--or does 3.4-stable now supports the card (ATA/66)? However, there is no point, and it's not feasible, of reverting the harddrive to an ATA/33, which the MB bios will not see anyway, to make it work. > Does this have something to do with the PNIC? Oh, probably. But I'm not going > to even attempt to debug this. There's no way in hell I could duplicate this > hardware configuration locally, and even if I did, I probably couldn't > duplicate the exact same problem. And even if I could do *that*, I > still wouldn't know how to fix it. I'm sorry, but I've pulled out enough > hair over this damn chip. I'm sure I've wasted at least a couple months > of my life trying to make this thing work reliably. I've added several > software workarounds, I defaulted the stupid transmit threshold setting > to store and forward mode. Well I've had it: no more. I'm through trying > to bitchslap this rotten piece of silicon to its senses. I'm not going to > go nuts every time somebody comes up with yet another oddball hardware > combination. There's a limit to my patience and this chip has reached it. > Now it's somebody else's turn to lose their sanity. I have the datasheet for > the PNIC at http://www.freebsd.org/~wpaul/PNIC. You have the driver source. > Somebody *else* try and figure it out, and then tell me then answer when > you have it. Well, I would say that my FreeBSD 3.2 box (with not so "oddball hardware combination" :-)) is doing just fine with this NIC... and I bow my hat to you, thank you. > That said, if you have overclocked this machine, then un-overclock it *right* > *now* and never, ever do it again! PCI bus master DMA is goofy enough without > people sticking their fingers in the works. Although I don't remember overclocking it... I'll take a look. > Man, why does PC hardware have to suck so hard. > > -Bill Thanks for the insight and help. arnee "Ackkkkk.. a spider!! That damn "bug" always *gets* my attention! :-) Sorry, just a little humor! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 11:53:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-33.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.161]) by hub.freebsd.org (Postfix) with ESMTP id 8B80E15135; Fri, 21 Jan 2000 11:53:12 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA14110; Fri, 21 Jan 2000 19:50:59 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00404; Fri, 21 Jan 2000 08:35:18 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001210835.IAA00404@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: current@FreeBSD.ORG, Jordan Hubbard Cc: Alfred Perlstein , des@FreeBSD.ORG, Brian Somers Subject: Warning: ioctl(... TUNSLMODE ...) to be depricated.... In-Reply-To: Message from Brian Somers of "Fri, 21 Jan 2000 00:36:58 GMT." <200001210036.AAA00691@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 08:35:18 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless there are objections in the next day or two, I'm going to deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD. Where TUNSLMODE prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a 4-byte network-byte-order address family. Jordan, I believe this change should go into 4.0-RELEASE rather than happening afterwards so that we have a minimal number of people (hopefully none) using TUNSLMODE. TUNSLMODE was never MFC'd. Cheers. I wrote (on freebsd-hackers@FreeBSD.org): > > * Brian Somers [000120 15:30] wrote: > > > Hi, > > > > > > I know this is a while in coming, but now that I'm looking at getting > > > ppp(8) to talk IPv6 (with the help of some KAME patches), I've looked > > > at how TUNSLMODE is implemented... it doesn't look good to me. > > > > > > What's the rationale behind stuffing the entire sockaddr in front of > > > the packet ? AFAIK the only information of any use is the address > > > family. > > > > > > By default, OpenBSD has a u_int32_t in front of every packet (I > > > believe this is unconfigurable), and I think this is about the most > > > sensible thing to do - I don't see that alignment issues will cause > > > problems. > > > > > > Alfred, this was originally submitted by you. Do you have any > > > argument against me changing it to just stuff the address family > > > as a 4-byte network-byte-order quantity there ? > > > > > > Any other opinions/arguments ? > > > > No objections, I just did it as an excercise to implement something > > in the manpages. > > I think the best plan is if I remove TUNSLMODE and introduce (say) > TUNSIFHEAD. If I reuse TUNSLMODE, I'll bump into all sorts of > problems. > > Now if someone was to say ``NetBSD does it this way'' I'd be > interested in copying that :*] > > > -- > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12: 0: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2EA0015156; Fri, 21 Jan 2000 12:00:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA19130; Fri, 21 Jan 2000 11:59:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brian Somers Cc: current@FreeBSD.ORG, Jordan Hubbard , Alfred Perlstein , des@FreeBSD.ORG Subject: Re: Warning: ioctl(... TUNSLMODE ...) to be depricated.... In-reply-to: Your message of "Fri, 21 Jan 2000 08:35:18 GMT." <200001210835.IAA00404@hak.lan.Awfulhak.org> Date: Fri, 21 Jan 2000 11:59:55 -0800 Message-ID: <19127.948484795@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan, I believe this change should go into 4.0-RELEASE rather than > happening afterwards so that we have a minimal number of people > (hopefully none) using TUNSLMODE. TUNSLMODE was never MFC'd. Do it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12: 8:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 08EC3154B6 for ; Fri, 21 Jan 2000 12:08:10 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA10331; Fri, 21 Jan 2000 20:54:00 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01189; Fri, 21 Jan 2000 20:45:44 +0100 (CET) (envelope-from wilko) Date: Fri, 21 Jan 2000 20:45:44 +0100 From: Wilko Bulte To: John Hay Cc: FreeBSD-current Subject: Re: make release broken Message-ID: <20000121204544.E741@yedi.iaf.nl> References: <200001210719.JAA61930@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001210719.JAA61930@zibbi.mikom.csir.co.za>; from jhay@mikom.csir.co.za on Fri, Jan 21, 2000 at 09:19:22AM +0200 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 09:19:22AM +0200, John Hay wrote: > Stop in /usr/src/release. > *** Error code 1 > > Stop in /usr/src/release. > *** Error code 1 > > Stop in /usr/src/release. > ------------------------------- > > It looks like the handling of HARDWARE.TXT in release/Makefile is broken. HARDWARE.TXT was missing. Should be corrected by a commit I've done 15 minutes ago. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12: 8:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 23F1F14D66 for ; Fri, 21 Jan 2000 12:08:42 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA10323; Fri, 21 Jan 2000 20:53:56 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA00882; Fri, 21 Jan 2000 20:19:25 +0100 (CET) (envelope-from wilko) Date: Fri, 21 Jan 2000 20:19:25 +0100 From: Wilko Bulte To: Peter Wemm Cc: John Hay , FreeBSD-current Subject: Re: make release broken Message-ID: <20000121201925.B741@yedi.iaf.nl> References: <20000121091536.A8F181CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121091536.A8F181CA0@overcee.netplex.com.au>; from peter@netplex.com.au on Fri, Jan 21, 2000 at 05:15:36PM +0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 05:15:36PM +0800, Peter Wemm wrote: > Wilko Bulte wrote: > > On Fri, Jan 21, 2000 at 09:19:22AM +0200, John Hay wrote: > [..] > > > cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory > > > *** Error code 1 > [..] > > > It looks like the handling of HARDWARE.TXT in release/Makefile is broken. > > > > Duh.. John Polstra is working on cvs-moving i386/HARDWARE.TXT to make > > this file the starting point for the generic HARDWARE.TXT > > > > There were some problems in doing this with cvs > > > > I guess this needs some time to get resolved. > > OK, here's the deal.. There is already a texts/HARDWARE.TXT, but it's been > cvs rm'ed from -current. Since it's in use on 3.4, we can't just clobber > it. > > So, if you want to move i386/HARDWARE.TXT up a level you're just going to > have to copy the file and cvs add it in the new location. This will > "revive" it in -current. We can't do anything about the lost history in > i386/HARDWARE.TXT. > > Well, strictly speaking it can be merged but it's much more painful than > it's worth. :-/ Just re-add the file and lets get on with it. Just commited this workaround. Thanks for your help/patience. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12:34:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id CA15714A23 for ; Fri, 21 Jan 2000 12:34:24 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA39870; Fri, 21 Jan 2000 15:34:14 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 21 Jan 2000 15:34:42 -0500 To: John Polstra , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Please help spread the CVSup mirror load more evenly Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:43 AM -0800 1/21/00, John Polstra wrote: >This is another in my series of occasional nags to try to get people >to use some of the less heavily loaded CVSup mirrors. In the US >alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. >The newest, cvsup8, is a very high-capacity and well-connected site, >yet hardly anybody is using it. Please give it a try! Maybe you should make cvsup.freebsd.org as a rotary (of sorts), which returns a different IP address based on the callers IP address. (or is that even possible?) That way, any given host will always try the same cvsup server, but you'll be spreading the load out among the servers. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12:42:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id C11E515403 for ; Fri, 21 Jan 2000 12:42:19 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id ABAB93E3D; Fri, 21 Jan 2000 21:42:18 +0100 (CET) Date: Fri, 21 Jan 2000 21:42:18 +0100 From: Jesper Skriver To: Garance A Drosihn Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121214218.A14016@skriver.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drosih@rpi.edu on Fri, Jan 21, 2000 at 03:34:42PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 03:34:42PM -0500, Garance A Drosihn wrote: > At 10:43 AM -0800 1/21/00, John Polstra wrote: > >This is another in my series of occasional nags to try to get people > >to use some of the less heavily loaded CVSup mirrors. In the US > >alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. > >The newest, cvsup8, is a very high-capacity and well-connected site, > >yet hardly anybody is using it. Please give it a try! > > Maybe you should make cvsup.freebsd.org as a rotary (of sorts), > which returns a different IP address based on the callers IP > address. (or is that even possible?) That way, any given > host will always try the same cvsup server, but you'll be > spreading the load out among the servers. Dial-up users with dynamic ip address assignment ... And to my best knowledge, BIND does not support anything like that. But what about simply changing cvsup.FreeBSD.org from cvsup1 to 8, that would probably help some ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12:56: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 09A3D14BDA for ; Fri, 21 Jan 2000 12:55:52 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA85636; Fri, 21 Jan 2000 13:55:46 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA13871; Fri, 21 Jan 2000 13:55:51 -0700 (MST) Message-Id: <200001212055.NAA13871@harmony.village.org> To: John Polstra Subject: Re: Please help spread the CVSup mirror load more evenly Cc: joe@pavilion.net, current@FreeBSD.ORG In-reply-to: Your message of "Fri, 21 Jan 2000 11:11:40 PST." <200001211911.LAA11701@vashon.polstra.com> References: <200001211911.LAA11701@vashon.polstra.com> <20000121190729.C58872@florence.pavilion.net> Date: Fri, 21 Jan 2000 13:55:51 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001211911.LAA11701@vashon.polstra.com> John Polstra writes: : > Can you make cvsup accept multiple servers to try in it's configuration : > file? : : I'll add that to the to-do list. I have a very crude script that does its own (fixed) round robin of multiple servers. It tries three times fast (yes, I know that's likely bad) and then goes to the next one on the list. If all else fails, it will try the first one on the list in "forever" mode (with the nice random retries). I'll have to see about puitting into good shape and posting it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 12:57: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id E22DE1555C; Fri, 21 Jan 2000 12:56:57 -0800 (PST) (envelope-from conrad@apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id MAA14298; Fri, 21 Jan 2000 12:56:52 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 21 Jan 2000 12:56:40 -0800 Received: from [17.202.45.145] (il0204a-dhcp17.apple.com [17.202.45.145]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id MAA21026; Fri, 21 Jan 2000 12:56:39 -0800 (PST) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <200001150920.KAA98140@freebsd.dk> References: <20000114214234.A14486@foobar.franken.de> MIME-Version: 1.0 Date: Fri, 21 Jan 2000 12:56:26 -0800 To: Soren Schmidt , logix@foobar.franken.de (Harold Gutch) From: Conrad Minshall Subject: Re: UDF Cc: beattie@aracnet.com (Brian Beattie), hackers@freebsd.org, current@freebsd.org Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:20 AM -0800 1/15/00, Soren Schmidt wrote: >It seems Harold Gutch wrote: >> On Fri, Jan 14, 2000 at 09:29:58AM +0100, Soren Schmidt wrote: >> > I have it on my TODO list, but I'm not started yet, and probably wont for >> > some time to come. >> > The reason I've put it on the backburner for now, is that DVD's can >> > be read using the cd9660 filesystem, and that is sufficient for my >> > needs for the time being. >> >> I was under the impression that this was only possible as long as >> the DVDs actually had an ISO9660 filesystem as well - which all >> of my DVDs have, but which still doesn't mean that there are no >> DVDs with only UDF, but no ISO9660 filesystem. > >I'm pretty sure all DVD's produced to date have an iso9660 file sys >on them, but they might change that in the future, so having UDF >support would be a win for us in the long run. DVD Forum's DVD-Video spec requires the UDF Bridge format, which gives you both UDF and 9660 metadata without duplicating file data. Commercial DVD videos are currently using this format. Bridge format is intended for read-only usage - as far as I know all DVD-RAM use is and will be restricted to "mono-metadata". -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Apple Computer ... Mac OS X Core Operating Systems ... NFS/UDF/etc Alternative email address: rad@acm.org. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 13: 7:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 1679214D00 for ; Fri, 21 Jan 2000 13:07:15 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id QAA55306; Fri, 21 Jan 2000 16:05:53 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 21 Jan 2000 16:05:53 -0500 (EST) From: Chuck Robey To: Warner Losh Cc: John Polstra , joe@pavilion.net, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001212055.NAA13871@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Warner Losh wrote: > In message <200001211911.LAA11701@vashon.polstra.com> John Polstra writes: > : > Can you make cvsup accept multiple servers to try in it's configuration > : > file? > : > : I'll add that to the to-do list. > > I have a very crude script that does its own (fixed) round robin of > multiple servers. It tries three times fast (yes, I know that's > likely bad) and then goes to the next one on the list. If all else > fails, it will try the first one on the list in "forever" mode (with > the nice random retries). > > I'll have to see about puitting into good shape and posting it. I would think using a fixed order would be a really bad thing, causing overload of the first server in line. Did I misunderstand you? How about doing a script (say in perl, it has random numbers) that randomly picks the server from a list? That way, the list could even be weighted, so as to allow for greater or lesser machine resources (like net access). ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 13:14: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 90A7E14D00 for ; Fri, 21 Jan 2000 13:14:00 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA85805; Fri, 21 Jan 2000 14:13:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA14047; Fri, 21 Jan 2000 14:14:01 -0700 (MST) Message-Id: <200001212114.OAA14047@harmony.village.org> To: Chuck Robey Subject: Re: Please help spread the CVSup mirror load more evenly Cc: John Polstra , joe@pavilion.net, current@FreeBSD.ORG In-reply-to: Your message of "Fri, 21 Jan 2000 16:05:53 EST." References: Date: Fri, 21 Jan 2000 14:14:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : I would think using a fixed order would be a really bad thing, causing : overload of the first server in line. Did I misunderstand you? How about : doing a script (say in perl, it has random numbers) that randomly picks : the server from a list? That way, the list could even be weighted, so as : to allow for greater or lesser machine resources (like net access). That's one of the things I have to fix up. This script is good for me, but bad for everyone. Enhancements like this would be a good thing. Got time? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 13:25:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 47114154FD for ; Fri, 21 Jan 2000 13:25:31 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id QAA55530; Fri, 21 Jan 2000 16:24:41 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 21 Jan 2000 16:24:41 -0500 (EST) From: Chuck Robey To: Warner Losh Cc: John Polstra , joe@pavilion.net, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001212114.OAA14047@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Warner Losh wrote: > In message Chuck Robey writes: > : I would think using a fixed order would be a really bad thing, causing > : overload of the first server in line. Did I misunderstand you? How about > : doing a script (say in perl, it has random numbers) that randomly picks > : the server from a list? That way, the list could even be weighted, so as > : to allow for greater or lesser machine resources (like net access). > > That's one of the things I have to fix up. This script is good for > me, but bad for everyone. Enhancements like this would be a good > thing. Got time? I don't know perl. Darn. Yes, I will learn perl. Now. > > Warner > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 13:26:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 6298A1542B for ; Fri, 21 Jan 2000 13:26:23 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id NAA19256; Fri, 21 Jan 2000 13:25:18 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id NAA05030; Fri, 21 Jan 2000 13:25:18 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id NAA29882; Fri, 21 Jan 2000 13:23:56 -0800 (PST) Message-ID: <3888CFC4.E130D88D@softweyr.com> Date: Fri, 21 Jan 2000 14:29:40 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: joe@pavilion.net, current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly References: <20000121190729.C58872@florence.pavilion.net> <200001211911.LAA11701@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > > Can you make cvsup accept multiple servers to try in it's configuration > > file? > > I'll add that to the to-do list. A nice heuristic that attempts to minimize latency and maximize throughput would be a nice feature to have. For extra credit, reverse entropy as well. Seriously, attempting to connect to a list of servers using record route and minimizing the latency and/or hop count would be a great little feature to add. It would be a great feature to package into a library. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 13:43:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 69F581527D for ; Fri, 21 Jan 2000 13:43:37 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA45646; Fri, 21 Jan 2000 16:42:46 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000121214218.A14016@skriver.dk> References: <20000121214218.A14016@skriver.dk> Date: Fri, 21 Jan 2000 16:43:17 -0500 To: Jesper Skriver From: Garance A Drosihn Subject: Re: Please help spread the CVSup mirror load more evenly Cc: John Polstra , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:42 PM +0100 1/21/00, Jesper Skriver wrote: >On Fri, Jan 21, 2000 at 03:34:42PM -0500, Garance A Drosihn wrote: > > At 10:43 AM -0800 1/21/00, John Polstra wrote: > > >This is another in my series of occasional nags to try to get > > >people to use some of the less heavily loaded CVSup mirrors. > > > > Maybe you should make cvsup.freebsd.org as a rotary (of sorts), > > which returns a different IP address based on the callers IP > > address. (or is that even possible?) That way, any given > > host will always try the same cvsup server, but you'll be > > spreading the load out among the servers. > >Dial-up users with dynamic ip address assignment ... You don't do it based on the last digit in the ip address. Do it based on the first number, or maybe the first two numbers. Ie, all IP addresses at RPI are 128.113.*.*, so they would all get the same value for this DNS rotary. If you did it in large enough ranges, it should be pretty consistent even for people coming in via dynamic IP addresses. It'd still be a problem for someone who's on the move a lot, of course (such as a laptop which is sometimes used on the RPI campus, and other times is dialing in thru various ISP's around the country). >And to my best knowledge, BIND does not support anything >like that. Not directly, but I think there are ways you can have it call some external procedure to do "load-balancing" for an IP rotary. We talked about doing this to address a problem here at RPI, but then we figured out an alternate solution so we didn't really get to the point of implementing it. I don't know if that external load-balancing procedure is given the IP address of the host doing the lookup, for instance. I'm just trying to come up with something that automatically balances the load, while still making it pretty likely that a given host will always get the same cvsup server. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14: 7:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id B2B281556F for ; Fri, 21 Jan 2000 14:07:26 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 2861 invoked from network); 21 Jan 2000 22:05:20 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 22:05:20 -0000 Message-ID: <3888D870.2416BFE8@pipeline.ch> Date: Fri, 21 Jan 2000 23:06:40 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Garance A Drosihn Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn wrote: > > At 10:43 AM -0800 1/21/00, John Polstra wrote: > >This is another in my series of occasional nags to try to get people > >to use some of the less heavily loaded CVSup mirrors. In the US > >alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. > >The newest, cvsup8, is a very high-capacity and well-connected site, > >yet hardly anybody is using it. Please give it a try! > > Maybe you should make cvsup.freebsd.org as a rotary (of sorts), > which returns a different IP address based on the callers IP > address. (or is that even possible?) That way, any given > host will always try the same cvsup server, but you'll be > spreading the load out among the servers. Thats not so easy. What about this: cvsup IN CNAME cvsup1.freebsd.org. cvsup IN CNAME cvsup2.freebsd.org. cvsup IN CNAME cvsup3.freebsd.org. cvsup IN CNAME cvsup4.freebsd.org. cvsup IN CNAME cvsup5.freebsd.org. cvsup IN CNAME cvsup6.freebsd.org. cvsup IN CNAME cvsup7.freebsd.org. cvsup IN CNAME cvsup8.freebsd.org. If you simply put "cvsup.freebsd.org" into your supfile you'll get randomly one of them. This should spread the load fairly well. If you want a special one then simply put "cvsupX.freebsd.org" into you supfile. Aint that easy? I don't see any appearant reson (short of network connectivity) that one *needs* to get always the *same* server. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14: 7:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id E687F1555D for ; Fri, 21 Jan 2000 14:07:49 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA02163; Fri, 21 Jan 2000 17:07:34 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001212207.RAA02163@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wes Peters Cc: John Polstra , joe@pavilion.net, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Please help spread the CVSup mirror load more evenly References: <20000121190729.C58872@florence.pavilion.net> <200001211911.LAA11701@vashon.polstra.com> <3888CFC4.E130D88D@softweyr.com> In-reply-to: Your message of "Fri, 21 Jan 2000 14:29:40 MST." <3888CFC4.E130D88D@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 17:07:34 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A nice heuristic that attempts to minimize latency and maximize throughput > would be a nice feature to have. For extra credit, reverse entropy as well. > > Seriously, attempting to connect to a list of servers using record route > and minimizing the latency and/or hop count would be a great little feature > to add. It would be a great feature to package into a library. I fear that the effort expended to do anything more than the easy 20% will be wasted. Trying to second-guess end-to-end network characteristics by reading the tea-leaves of a traceroute-like probe is going to be very hard. You should measure the characteristics which are exposed to your application, if possible, and make decisions based on that. For instance, on UUNET's backbone network (of which I happen to know quite a lot about since I did some of the original architecture) has an extensive layer-2 ATM and Frame Relay component used to do traffic engineering. Even though there are multiple layer-2 hops through switches, you can't see any of that using a traceroute-like mechanism. And forget about record route options; that's going to cause the packet to go through the slow forwarding path of the router, which is essentially completely unrelated to experience the packet has without the record route option, other than taking the same path. As John mentioned earlier, what your probably most interested in is patch quality (e.g., minimum packet loss) first and latency second as far as network characteristics are concerned. Simply measure them if you choose rather than trying to understand why the latency is what is. Trying to predict path quality based on observed topology is hard to do in an automated fashion. Sure, you can employ some simply heuristics as a human (e.g., don't go through MAE-EAST - it sucks there) and the occasional traceroute will reduce your candidate list of servers to a likely set which won't suck and are in the same hemisphere. I fear trying to be significantly more clever than that and simple measurements is Very Hard and can probably get you a Ph.D. or a bunch of $$$ or both. If you succeed. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:10:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id C00B5155C9 for ; Fri, 21 Jan 2000 14:10:51 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 899F63E3D; Fri, 21 Jan 2000 23:10:50 +0100 (CET) Date: Fri, 21 Jan 2000 23:10:50 +0100 From: Jesper Skriver To: Andre Oppermann Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121231050.A14324@skriver.dk> References: <3888D870.2416BFE8@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3888D870.2416BFE8@pipeline.ch>; from oppermann@pipeline.ch on Fri, Jan 21, 2000 at 11:06:40PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote: > Garance A Drosihn wrote: > > > > At 10:43 AM -0800 1/21/00, John Polstra wrote: > > >This is another in my series of occasional nags to try to get people > > >to use some of the less heavily loaded CVSup mirrors. In the US > > >alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. > > >The newest, cvsup8, is a very high-capacity and well-connected site, > > >yet hardly anybody is using it. Please give it a try! > > > > Maybe you should make cvsup.freebsd.org as a rotary (of sorts), > > which returns a different IP address based on the callers IP > > address. (or is that even possible?) That way, any given > > host will always try the same cvsup server, but you'll be > > spreading the load out among the servers. > > Thats not so easy. What about this: > > cvsup IN CNAME cvsup1.freebsd.org. > cvsup IN CNAME cvsup2.freebsd.org. > cvsup IN CNAME cvsup3.freebsd.org. > cvsup IN CNAME cvsup4.freebsd.org. > cvsup IN CNAME cvsup5.freebsd.org. > cvsup IN CNAME cvsup6.freebsd.org. > cvsup IN CNAME cvsup7.freebsd.org. > cvsup IN CNAME cvsup8.freebsd.org. > > If you simply put "cvsup.freebsd.org" into your supfile you'll get > randomly one of them. This should spread the load fairly well. If > you want a special one then simply put "cvsupX.freebsd.org" into > you supfile. > > Aint that easy? > > I don't see any appearant reson (short of network connectivity) that > one *needs* to get always the *same* server. This has been discussed regulary ... You will risk hitting 2 different server in 2 rapid cvsup run's, where the first may be more up to date than the next, as Jordan wrote earlier in this thread ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:13:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 1CBD41553B for ; Fri, 21 Jan 2000 14:13:29 -0800 (PST) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id JAA29613 for ; Sat, 22 Jan 2000 09:13:23 +1100 (EDT) Received: (qmail 39765 invoked by uid 1000); 21 Jan 2000 22:13:22 -0000 From: "Andrew Reilly" Date: Sat, 22 Jan 2000 09:13:21 +1100 To: Chuck Robey Cc: Warner Losh , John Polstra , joe@pavilion.net, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000122091321.A45218@gurney.reilly.home> References: <200001212114.OAA14047@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 04:24:41PM -0500, Chuck Robey wrote: > On Fri, 21 Jan 2000, Warner Losh wrote: > > In message Chuck Robey writes: > > : I would think using a fixed order would be a really bad thing, causing > > : overload of the first server in line. Did I misunderstand you? How about > > : doing a script (say in perl, it has random numbers) that randomly picks > > : the server from a list? That way, the list could even be weighted, so as > > : to allow for greater or lesser machine resources (like net access). > > > > That's one of the things I have to fix up. This script is good for > > me, but bad for everyone. Enhancements like this would be a good > > thing. Got time? > > I don't know perl. Darn. Yes, I will learn perl. Now. sh has random numbers. Spelled "jot -r". -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:14:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 4346E1558E for ; Fri, 21 Jan 2000 14:14:41 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA02259; Fri, 21 Jan 2000 17:14:21 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001212214.RAA02259@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andre Oppermann Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> In-reply-to: Your message of "Fri, 21 Jan 2000 23:06:40 +0100." <3888D870.2416BFE8@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 17:14:21 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Maybe you should make cvsup.freebsd.org as a rotary (of sorts), > > which returns a different IP address based on the callers IP > > address. (or is that even possible?) That way, any given > > host will always try the same cvsup server, but you'll be > > spreading the load out among the servers. > > Thats not so easy. What about this: > > cvsup IN CNAME cvsup1.freebsd.org. > cvsup IN CNAME cvsup2.freebsd.org. > cvsup IN CNAME cvsup3.freebsd.org. > cvsup IN CNAME cvsup4.freebsd.org. > cvsup IN CNAME cvsup5.freebsd.org. > cvsup IN CNAME cvsup6.freebsd.org. > cvsup IN CNAME cvsup7.freebsd.org. > cvsup IN CNAME cvsup8.freebsd.org. This is wrong two ways. First, the data associated with a CNAME is supposed to be the cannonical name of a host, and not another domain name with only a CNAME resource record. Second, a domain name can at most a single CNAME record associated with it, and other other record types. BIND will (should) barf on a zone file containing the example you listed. > If you simply put "cvsup.freebsd.org" into your supfile you'll get > randomly one of them. This should spread the load fairly well. If > you want a special one then simply put "cvsupX.freebsd.org" into > you supfile. You could play some DNS games to get this effect, though it's not clear what the randomness of the list of resource records is supposed to be. Certain the DNS protocol doesn't define any randomness. > I don't see any appearant reson (short of network connectivity) that > one *needs* to get always the *same* server. See previous mesasge from John regarding doing two successive updates where the servers are not synchronized with the same version files. Is this really a problem that demands solutions this complicated? The solution isn't necessarily a technological one; a simple email message reminding people of other servers might be sufficient :-) louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:15: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 2DB58155E3 for ; Fri, 21 Jan 2000 14:14:53 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id QAA17007 for freebsd-current@freebsd.org; Fri, 21 Jan 2000 16:14:47 -0600 (CST) Date: Fri, 21 Jan 2000 16:14:47 -0600 (CST) From: Mohit Aron Message-Id: <200001212214.QAA17007@cs.rice.edu> To: freebsd-current@freebsd.org Subject: when is FreeBSD-4.0 up for release ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, wasn't the release date set for Jan 15 ? Anyone knows the new tentative date ? Thanks, - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:24:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id E5C081561C for ; Fri, 21 Jan 2000 14:24:31 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 51367 invoked by uid 1001); 21 Jan 2000 22:22:52 -0000 Date: Fri, 21 Jan 2000 14:22:51 -0800 From: Jason Evans To: Bill Swingle Cc: current@freebsd.org Subject: Re: even more breakage in current Message-ID: <20000121142251.D27689@sturm.canonware.com> References: <20000121101157.A18956@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121101157.A18956@dub.net>; from unfurl@dub.net on Fri, Jan 21, 2000 at 10:11:57AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 10:11:57AM -0800, Bill Swingle wrote: > I updated my source tree around 10pm PST last night (01/20) and made > world only to find it broken this morning. I reupdated my tree just now > and it doesnt look like any files that might fix this have been touched. > Anyone else seeing this? > > cc -pg -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/gen/wait3.c -o wait3.po > cc -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.o > cc -DPROF -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.po > /tmp/ccg65684.s: Assembler messages: > /tmp/cco65681.s: Assembler messages: > /tmp/cco65681.s:361: Error: invalid character '(' in opcode > /tmp/ccg65684.s:361: Error: invalid character '(' in opcode > *** Error code 1 > *** Error code 1 > 2 errors > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > root@rooter:/usr/src$ cvs -Rq update -PdA > U etc/MAKEDEV > U etc/pccard.conf.sample > U usr.sbin/pccard/pccardd/cardd.c > U usr.sbin/pccard/pccardd/cardd.h > U usr.sbin/pccard/pccardd/file.c > root@rooter:/usr/src$ I moved some definitions from src/lib/libc/i386/DEFS.h to src/sys/i386/include/asm.h. If the build system is looking at the installed version of asm.h rather than the version in the source tree, this error will occur. I did a 'make includes' during my testing, so I didn't have this problem. It's my understanding that the build system is supposed to be sophisticated enough to avoid such bootstrapping issues, but I don't understand it all that well. Can someone explain whether this is a bug in the build system, or if I should be doing something different? In any case, doing a 'make includes' will get you past this. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:25:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 40318155AB for ; Fri, 21 Jan 2000 14:25:09 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA29190; Fri, 21 Jan 2000 23:24:36 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <3888D870.2416BFE8@pipeline.ch> References: <3888D870.2416BFE8@pipeline.ch> Date: Fri, 21 Jan 2000 23:24:17 +0100 To: Andre Oppermann , Garance A Drosihn From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: John Polstra , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:06 PM +0100 2000/1/21, Andre Oppermann wrote: > Thats not so easy. What about this: > > cvsup IN CNAME cvsup1.freebsd.org. > cvsup IN CNAME cvsup2.freebsd.org. > cvsup IN CNAME cvsup3.freebsd.org. > cvsup IN CNAME cvsup4.freebsd.org. > cvsup IN CNAME cvsup5.freebsd.org. > cvsup IN CNAME cvsup6.freebsd.org. > cvsup IN CNAME cvsup7.freebsd.org. > cvsup IN CNAME cvsup8.freebsd.org. As I understood the rules of good Domain Administration, everything that is publicly visible in your network needs to have an MX record. But with this scheme you can't give cvsup.freebsd.org an MX record, because pointing an MX at a CNAME violates the RFC. Personally, I would much prefer the CPAN solution of a program that takes the IP address of the query source, and then using knowledge of what IP addresses are generally located where in the world (available via the whois maps in the various regions, which could presumably be imported and stored locally), returns a short list of addresses in the preferred order. For those networks where multiple addresses may have equal "cost", it can then randomize for load balancing purposes. It requires either a hacked nameserver program for this one zone, or the code to handle this has to be incorporated into cvsup itself, so that you distribute the logic and CPU processing time to all the clients. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:34: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 1E4BA15530 for ; Fri, 21 Jan 2000 14:34:06 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 15-119.008.popsite.net ([209.69.195.119] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12Bmcx-0000UW-00; Fri, 21 Jan 2000 15:34:00 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 4EE961A06; Fri, 21 Jan 2000 17:33:53 -0500 (EST) Date: Fri, 21 Jan 2000 17:33:53 -0500 From: Will Andrews To: Mohit Aron Cc: freebsd-current@FreeBSD.ORG Subject: Re: when is FreeBSD-4.0 up for release ? Message-ID: <20000121173353.C541@shadow.blackdawn.com> References: <200001212214.QAA17007@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001212214.QAA17007@cs.rice.edu>; from aron@cs.rice.edu on Fri, Jan 21, 2000 at 04:14:47PM -0600 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 04:14:47PM -0600, Mohit Aron wrote: > Hi, > wasn't the release date set for Jan 15 ? Anyone knows the new > tentative date ? Thanks, That was the Feature Freeze (tm). Jordan hasn't made any "official" announcements about the Feature Freeze yet, I don't think. Anyway, the release should be out a few weeks after the Code Freeze (tm), which should be around February 7th or 15th. Personally, I think it'll be March before 4.0-RELEASE hits the door. -- Will Andrews 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:40:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id E86E514D14 for ; Fri, 21 Jan 2000 14:40:08 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 2946 invoked from network); 21 Jan 2000 22:38:04 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 22:38:04 -0000 Message-ID: <3888E01C.1E568130@pipeline.ch> Date: Fri, 21 Jan 2000 23:39:24 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Jesper Skriver Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <20000121231050.A14324@skriver.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jesper Skriver wrote: > > On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote: > > I don't see any appearant reson (short of network connectivity) that > > one *needs* to get always the *same* server. > > This has been discussed regulary ... Must have been some time ago... > You will risk hitting 2 different server in 2 rapid cvsup run's, where > the first may be more up to date than the next, as Jordan wrote earlier > in this thread ... Does it matter? Who cvsup's regulary more than once or twice a day? Committers AFAIK do cvs directly. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:42:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 47996155AF for ; Fri, 21 Jan 2000 14:42:36 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id XAA22468 for ; Fri, 21 Jan 2000 23:42:33 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma022465; Fri, 21 Jan 00 23:42:33 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id XAA15460 for ; Fri, 21 Jan 2000 23:42:32 +0100 (MET) Received: (qmail 32699 invoked by uid 666); 21 Jan 2000 23:35:15 -0000 Date: Sat, 22 Jan 2000 00:35:15 +0100 From: Jos Backus To: Barry Lustig Cc: current@freebsd.org Subject: Re: Possible IPv6-related problem Message-ID: <20000122003515.A32567@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <20000114203240.C1626@hal.mpn.cp.philips.com> <20000116224019.20160.qmail@devious.lustig.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000116224019.20160.qmail@devious.lustig.com>; from barry@lustig.com on Sun, Jan 16, 2000 at 05:40:18PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some more information: I can not reproduce the problem with a -current as of yesterday on my home system. I'll re-check my system at work next week and let you know. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:46:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id E737A14D14 for ; Fri, 21 Jan 2000 14:46:18 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 2957 invoked from network); 21 Jan 2000 22:44:13 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 22:44:13 -0000 Message-ID: <3888E18E.F1CBA39B@pipeline.ch> Date: Fri, 21 Jan 2000 23:45:34 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <200001212214.RAA02259@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos wrote: > > cvsup IN CNAME cvsup1.freebsd.org. > > cvsup IN CNAME cvsup2.freebsd.org. > > cvsup IN CNAME cvsup3.freebsd.org. > > cvsup IN CNAME cvsup4.freebsd.org. > > cvsup IN CNAME cvsup5.freebsd.org. > > cvsup IN CNAME cvsup6.freebsd.org. > > cvsup IN CNAME cvsup7.freebsd.org. > > cvsup IN CNAME cvsup8.freebsd.org. > > This is wrong two ways. > > First, the data associated with a CNAME is supposed to be the > cannonical name of a host, and not another domain name with only > a CNAME resource record. ??? Are all cvsupX.freebsd.org also CNAME's? > Second, a domain name can at most a single CNAME record associated > with it, and other other record types. BIND will (should) barf on a > zone file containing the example you listed. It does not. It will round-robin over the CNAME's. > > If you simply put "cvsup.freebsd.org" into your supfile you'll get > > randomly one of them. This should spread the load fairly well. If > > you want a special one then simply put "cvsupX.freebsd.org" into > > you supfile. > > You could play some DNS games to get this effect, though it's not > clear what the randomness of the list of resource records is supposed > to be. Certain the DNS protocol doesn't define any randomness. But bind does. > > I don't see any appearant reson (short of network connectivity) that > > one *needs* to get always the *same* server. > > See previous mesasge from John regarding doing two successive updates > where the servers are not synchronized with the same version files. Who cvsup's regurlary more than once or twice a day? Committers AFAIK do cvs directly. > Is this really a problem that demands solutions this complicated? The > solution isn't necessarily a technological one; a simple email message > reminding people of other servers might be sufficient :-) Yea, then all swamp cvsup8.freebsd.org and John has to send another message that there are still cvsup[2-7].freebsd.org idling around. Just kidding... But you get the point? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:48: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 9FDF21555F for ; Fri, 21 Jan 2000 14:48:02 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id OAA08212; Fri, 21 Jan 2000 14:47:56 -0800 (PST) (envelope-from mph) Date: Fri, 21 Jan 2000 14:47:56 -0800 From: Matthew Hunt To: Andre Oppermann Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121144756.A8163@wopr.caltech.edu> References: <3888D870.2416BFE8@pipeline.ch> <20000121231050.A14324@skriver.dk> <3888E01C.1E568130@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3888E01C.1E568130@pipeline.ch>; from oppermann@pipeline.ch on Fri, Jan 21, 2000 at 11:39:24PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 11:39:24PM +0100, Andre Oppermann wrote: > Does it matter? Who cvsup's regulary more than once or twice a day? > Committers AFAIK do cvs directly. I "cvs co" from my local copy of the repository, which is kept up-to-date using cvsup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:49: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id CC062150AB for ; Fri, 21 Jan 2000 14:49:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id OAA36108; Fri, 21 Jan 2000 14:46:58 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001212246.OAA36108@troutmask.apl.washington.edu> Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <3888E01C.1E568130@pipeline.ch> from Andre Oppermann at "Jan 21, 2000 11:39:24 pm" To: Andre Oppermann Date: Fri, 21 Jan 2000 14:46:58 -0800 (PST) Cc: Jesper Skriver , Garance A Drosihn , John Polstra , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Oppermann wrote: > Jesper Skriver wrote: > > > > > You will risk hitting 2 different server in 2 rapid cvsup run's, where > > the first may be more up to date than the next, as Jordan wrote earlier > > in this thread ... > > Does it matter? Who cvsup's regulary more than once or twice a day? > Committers AFAIK do cvs directly. > %cvsup Damn! Forgot I don't want src-sys --> Hit ^C. %vi ~/supfile Remove src-sys %cvsup or %cvsup Damn! Forgot I want to remove sup/src-sys/refuse --> Hit ^C. %rm sup/src-sys/refuse %cvsup Yes, I've done both scenarios. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:49:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 84D5C14D11 for ; Fri, 21 Jan 2000 14:49:25 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA86268; Fri, 21 Jan 2000 15:49:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA14936; Fri, 21 Jan 2000 15:49:29 -0700 (MST) Message-Id: <200001212249.PAA14936@harmony.village.org> To: Mohit Aron Subject: Re: when is FreeBSD-4.0 up for release ? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 21 Jan 2000 16:14:47 CST." <200001212214.QAA17007@cs.rice.edu> References: <200001212214.QAA17007@cs.rice.edu> Date: Fri, 21 Jan 2000 15:49:29 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001212214.QAA17007@cs.rice.edu> Mohit Aron writes: : wasn't the release date set for Jan 15 ? Anyone knows the new : tentative date ? Thanks, No. Jan 15 was a feature freeze. Likely first part of Feb for a release, but no date has been widely circulated. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:53:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id B12B6155D1 for ; Fri, 21 Jan 2000 14:53:11 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 2971 invoked from network); 21 Jan 2000 22:51:06 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 22:51:06 -0000 Message-ID: <3888E32A.522E1FE7@pipeline.ch> Date: Fri, 21 Jan 2000 23:52:26 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Brad Knowles Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 11:06 PM +0100 2000/1/21, Andre Oppermann wrote: > > > Thats not so easy. What about this: > > > > cvsup IN CNAME cvsup1.freebsd.org. > > cvsup IN CNAME cvsup2.freebsd.org. > > cvsup IN CNAME cvsup3.freebsd.org. > > cvsup IN CNAME cvsup4.freebsd.org. > > cvsup IN CNAME cvsup5.freebsd.org. > > cvsup IN CNAME cvsup6.freebsd.org. > > cvsup IN CNAME cvsup7.freebsd.org. > > cvsup IN CNAME cvsup8.freebsd.org. > > As I understood the rules of good Domain Administration, > everything that is publicly visible in your network needs to have an > MX record. But with this scheme you can't give cvsup.freebsd.org an > MX record, because pointing an MX at a CNAME violates the RFC. You can, simply do this: cvsup IN MX 10 hub.freebsd.org No violation of any RFC whatsoever. > Personally, I would much prefer the CPAN solution of a program > that takes the IP address of the query source, and then using > knowledge of what IP addresses are generally located where in the > world (available via the whois maps in the various regions, which > could presumably be imported and stored locally), returns a short > list of addresses in the preferred order. For those networks where > multiple addresses may have equal "cost", it can then randomize for > load balancing purposes. Don't go by whois, it does not reflect the physical connectivity. Go by BGP path length if you want to do something like this. > It requires either a hacked nameserver program for this one zone, > or the code to handle this has to be incorporated into cvsup itself, > so that you distribute the logic and CPU processing time to all the > clients. There are commecial nameservers which decide upon bgp path length but it'll cost some big $$$. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:56:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 4C19715661 for ; Fri, 21 Jan 2000 14:55:59 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 46033 invoked by uid 1001); 21 Jan 2000 22:55:56 +0000 (GMT) To: oppermann@pipeline.ch Cc: louie@TransSys.COM, drosih@rpi.edu, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 21 Jan 2000 23:45:34 +0100" References: <3888E18E.F1CBA39B@pipeline.ch> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 21 Jan 2000 23:55:56 +0100 Message-ID: <46031.948495356@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Second, a domain name can at most a single CNAME record associated > > with it, and other other record types. BIND will (should) barf on a > > zone file containing the example you listed. > > It does not. It will round-robin over the CNAME's. See the documentation for the multiple-cnames option in BIND 8.2.2: If yes, multiple CNAME resource records will be allowed for a domain name. The default is no. Allowing multiple CNAME records is against standards and is not recommended. Multiple CNAME support is available because previous versions of BIND allowed multiple CNAME records, and these records have been used for load balancing by a number of sites. So I'd say this is not a good idea. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:57: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 398CE1555F for ; Fri, 21 Jan 2000 14:56:56 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 2978 invoked from network); 21 Jan 2000 22:54:51 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 22:54:51 -0000 Message-ID: <3888E40B.4749ABB3@pipeline.ch> Date: Fri, 21 Jan 2000 23:56:11 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Matthew Hunt Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <20000121231050.A14324@skriver.dk> <3888E01C.1E568130@pipeline.ch> <20000121144756.A8163@wopr.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Hunt wrote: > > On Fri, Jan 21, 2000 at 11:39:24PM +0100, Andre Oppermann wrote: > > > Does it matter? Who cvsup's regulary more than once or twice a day? > > Committers AFAIK do cvs directly. > > I "cvs co" from my local copy of the repository, which is kept > up-to-date using cvsup. OK, then you should hardwire your cvsup server to cvsup[1-8]. You can master cvs so you can master this. Cvsup.freebsd.org is used by Joe Random and he wont be cvsupping more than once a day. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:59:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 4583615624 for ; Fri, 21 Jan 2000 14:59:41 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id OAA08436; Fri, 21 Jan 2000 14:59:36 -0800 (PST) (envelope-from mph) Date: Fri, 21 Jan 2000 14:59:36 -0800 From: Matthew Hunt To: Andre Oppermann Cc: current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121145936.A8411@wopr.caltech.edu> References: <3888D870.2416BFE8@pipeline.ch> <20000121231050.A14324@skriver.dk> <3888E01C.1E568130@pipeline.ch> <20000121144756.A8163@wopr.caltech.edu> <3888E40B.4749ABB3@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3888E40B.4749ABB3@pipeline.ch>; from oppermann@pipeline.ch on Fri, Jan 21, 2000 at 11:56:11PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 11:56:11PM +0100, Andre Oppermann wrote: > OK, then you should hardwire your cvsup server to cvsup[1-8]. You can > master cvs so you can master this. I do. Thanks for your vote of confidence in my abilities, though. If you meant "committers use cvs directly or hardwire their cvsup server", maybe you should have written that. -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 14:59:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 9E4661565B for ; Fri, 21 Jan 2000 14:59:49 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA02836; Fri, 21 Jan 2000 17:59:36 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001212259.RAA02836@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andre Oppermann Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <200001212214.RAA02259@whizzo.transsys.com> <3888E18E.F1CBA39B@pipeline.ch> In-reply-to: Your message of "Fri, 21 Jan 2000 23:45:34 +0100." <3888E18E.F1CBA39B@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 17:59:36 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Second, a domain name can at most a single CNAME record associated > > with it, and other other record types. BIND will (should) barf on a > > zone file containing the example you listed. > > It does not. It will round-robin over the CNAME's. If it does, than this is a bug in BIND. The DNS is not defined to work this way. Semantically, it doesn't make sense to have more than one CNAME record. The CNAME resource record is supposed to contain the cannonical name for the domain name that it's associated with. There can be only one cannonical name. And it appears that in the latest BIND, they've seen the error of their ways: multiple-cnames If yes, then multiple CNAME resource records will be allowed for a do- main name. The default is no. Allowing multiple CNAME records is against standards and is not recommended. Multiple CNAME support is available because previous versions of BIND allowed multiple CNAME records, and these records have been used for load balancing by a num- ber of sites. In any case, this has turned into a debate on how to (ab)use BIND and the DNS, and is well off topic. > Yea, then all swamp cvsup8.freebsd.org and John has to send another > message that there are still cvsup[2-7].freebsd.org idling around. > Just kidding... But you get the point? My only point is that the first response to a problem isn't to necessarily pull out emacs and start hacking away on code. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15: 3:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id F1AFE155C7 for ; Fri, 21 Jan 2000 15:03:34 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 3274 invoked from network); 21 Jan 2000 23:01:27 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 23:01:27 -0000 Message-ID: <3888E597.9D80E8EF@pipeline.ch> Date: Sat, 22 Jan 2000 00:02:47 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: sthaug@nethelp.no Cc: louie@TransSys.COM, drosih@rpi.edu, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888E18E.F1CBA39B@pipeline.ch> <46031.948495356@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > > > Second, a domain name can at most a single CNAME record associated > > > with it, and other other record types. BIND will (should) barf on a > > > zone file containing the example you listed. > > > > It does not. It will round-robin over the CNAME's. > > See the documentation for the multiple-cnames option in BIND 8.2.2: > > If yes, multiple CNAME resource records will be allowed for a domain > name. The default is no. Allowing multiple CNAME records is against > standards and is not recommended. Multiple CNAME support is available > because previous versions of BIND allowed multiple CNAME records, and > these records have been used for load balancing by a number of sites. > > So I'd say this is not a good idea. Ah, well, ok. I used it extensively with bind 8.1.2 in an internal application in a big bank to get approx. load distribution with Windumb clients (they always take the first record in the list returned). Anyway, if multi CNAME is no good then do: cvsup IN A 198.104.92.71 ; cvsup1.freebsd.org cvsup IN A 205.149.189.91 ; cvsup2.freebsd.org ... and so on This is legal, is it? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15: 6:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 2F99B15595 for ; Fri, 21 Jan 2000 15:06:07 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 3281 invoked from network); 21 Jan 2000 23:03:54 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 23:03:54 -0000 Message-ID: <3888E62A.B893AB69@pipeline.ch> Date: Sat, 22 Jan 2000 00:05:14 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Matthew Hunt Cc: current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <20000121231050.A14324@skriver.dk> <3888E01C.1E568130@pipeline.ch> <20000121144756.A8163@wopr.caltech.edu> <3888E40B.4749ABB3@pipeline.ch> <20000121145936.A8411@wopr.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Hunt wrote: > > On Fri, Jan 21, 2000 at 11:56:11PM +0100, Andre Oppermann wrote: > > > OK, then you should hardwire your cvsup server to cvsup[1-8]. You can > > master cvs so you can master this. > > I do. Thanks for your vote of confidence in my abilities, though. > If you meant "committers use cvs directly or hardwire their > cvsup server", maybe you should have written that. Sorry, I didn't want to offend you. I apologise. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15: 8:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 68C6B155B1 for ; Fri, 21 Jan 2000 15:08:22 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id SAA92841; Fri, 21 Jan 2000 18:20:38 -0500 (EST) Date: Fri, 21 Jan 2000 18:20:38 -0500 (EST) From: Ben Rosengart To: Andre Oppermann Cc: sthaug@nethelp.no, louie@TransSys.COM, drosih@rpi.edu, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <3888E597.9D80E8EF@pipeline.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, Andre Oppermann wrote: > Ah, well, ok. I used it extensively with bind 8.1.2 in an internal > application in a big bank to get approx. load distribution with > Windumb clients (they always take the first record in the list > returned). > > Anyway, if multi CNAME is no good then do: > > cvsup IN A 198.104.92.71 ; cvsup1.freebsd.org > cvsup IN A 205.149.189.91 ; cvsup2.freebsd.org > ... and so on > > This is legal, is it? Not only is it legal, but I believe BIND will return all the A records to any query, and will rotate them. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:14: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id DA6C61561E for ; Fri, 21 Jan 2000 15:13:53 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 3300 invoked from network); 21 Jan 2000 23:11:48 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 21 Jan 2000 23:11:48 -0000 Message-ID: <3888E804.1BA82919@pipeline.ch> Date: Sat, 22 Jan 2000 00:13:08 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: <3888D870.2416BFE8@pipeline.ch> <200001212214.RAA02259@whizzo.transsys.com> <3888E18E.F1CBA39B@pipeline.ch> <200001212259.RAA02836@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos wrote: > > > > Second, a domain name can at most a single CNAME record associated > > > with it, and other other record types. BIND will (should) barf on a > > > zone file containing the example you listed. > > > > It does not. It will round-robin over the CNAME's. > > If it does, than this is a bug in BIND. The DNS is not defined to > work this way. Semantically, it doesn't make sense to have more > than one CNAME record. The CNAME resource record is supposed to > contain the cannonical name for the domain name that it's associated > with. There can be only one cannonical name. > > And it appears that in the latest BIND, they've seen the error of their > ways: -snip- OK, I did it with bind 8.1.2, see my other response to Steinar. > In any case, this has turned into a debate on how to (ab)use BIND and > the DNS, and is well off topic. Back on topic. Do it instead with A records. Joe Random goes for cvsup.freebsd.org and highly likely wont be cvsupping more than once a day. Others who do can hardwire to one specific cvsup server. The best of both worlds with just a few key strokes and now complies with every imaginable RFC. Uh, I better don't pray for it. > > Yea, then all swamp cvsup8.freebsd.org and John has to send another > > message that there are still cvsup[2-7].freebsd.org idling around. > > Just kidding... But you get the point? > > My only point is that the first response to a problem isn't to necessarily > pull out emacs and start hacking away on code. Yea, it is easier to do in a regular zone file then to implement the network measurement logic into cvsup. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:15:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id EF68B15609 for ; Fri, 21 Jan 2000 15:15:36 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id SAA00583; Fri, 21 Jan 2000 18:15:24 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001212315.SAA00583@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3888E01C.1E568130@pipeline.ch> Date: Fri, 21 Jan 2000 18:15:24 -0500 (EST) From: John Baldwin To: Andre Oppermann Subject: Re: Please help spread the CVSup mirror load more evenly Cc: current@FreeBSD.org, John Polstra , Garance A Drosihn , Jesper Skriver Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Jan-00 Andre Oppermann wrote: > Jesper Skriver wrote: >> >> On Fri, Jan 21, 2000 at 11:06:40PM +0100, Andre Oppermann wrote: >> > I don't see any appearant reson (short of network connectivity) that >> > one *needs* to get always the *same* server. >> >> This has been discussed regulary ... > > Must have been some time ago... Yes, every few months it seems. >> You will risk hitting 2 different server in 2 rapid cvsup run's, where >> the first may be more up to date than the next, as Jordan wrote earlier >> in this thread ... > > Does it matter? Who cvsup's regulary more than once or twice a day? > Committers AFAIK do cvs directly. No, cvs is much slower than cvsup. I, for one, cvsup the repository itself and then do cvs operations locally against that. > -- > Andre > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:21:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id A5E7D156C8 for ; Fri, 21 Jan 2000 15:21:34 -0800 (PST) (envelope-from jstock@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 6D7AB37F6 for ; Fri, 21 Jan 2000 17:21:33 -0600 (CST) Received: from localhost (jstock@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id RAA17073 for ; Fri, 21 Jan 2000 17:21:33 -0600 (CST) X-Authentication-Warning: isis.visi.com: jstock owned process doing -bs Date: Fri, 21 Jan 2000 17:21:33 -0600 (CST) From: "Jeremy L. Stock" To: freebsd-current@FreeBSD.ORG Subject: Creative ViBRA16X Problem (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thought I'd post this to -current also since it gives a little more detail (I hope). I can't believe I'm the only one experiencing this since it's still around when I do a fresh install from a snapshot. Not a huge deal for me since I can use Windows for audio, but I'd rather use FreeBSD again. I'm sure this will get addressed before 4.0R. I just wanted to make sure it's a known issue. -- Jeremy L. Stock ICQ 46329337 Fax # 612-629-6540 ---------- Forwarded message ---------- Date: Tue, 18 Jan 2000 22:14:44 -0600 (CST) From: Jeremy L. Stock To: gandalf@vilnya.demon.co.uk Subject: Creative ViBRA16X Problem I posted this on -current almost a week ago and only received one response that didn't solve the problem. Audio hasn't played correctly for me since December 27th. Now when I try to play audio, it just stutters. I'm not sure when it broke since I went from -current as of the 27th to -current as of the 11th and now earlier today. The problem still remains even after a total reinstall. I just wanted to make sure you were aware of it and make sure you had a chance to correct it before 4.0R. Here's some info. Let me know if you need anything else. Copyright (c) 1992-2000 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: Tue Jan 18 20:00:28 CST 2000 root@nic-31-c23-178.mn.mediaone.net:/usr/src/sys/compile/NIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350796057 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 127315968 (124332K bytes) Preloaded elf kernel "kernel" at 0xc02c2000. sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 on isa0 sbc0: setting card to irq 10, drq 0, 1 pcm0: on sbc0 unknown0: at port 0x201 on isa0 And from boot -v (Let me know if I left an important section out) Trying Read_Port at 203 CTL0043: start dependant CTL0043: adding irq mask 0x20 CTL0043: adding dma mask 0x2 CTL0043: adding dma mask 0x8 CTL0043: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0043: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x10 CTL0043: adding io range 0x388-0x397, size=0x4, align=0x4 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: end dependant CTL7005: start dependant CTL7005: adding io range 0x201-0x201, size=0x1, align=0x1 CTL7005: start dependant CTL7005: adding io range 0x200-0x20f, size=0x1, align=0x1 CTL7005: end dependant isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 on isa0 sbc0: setting card to irq 10, drq 0, 1 pcm0: on sbc0 pcm: setmap 2d000, 2000; 0xc7814000 -> 2d000 pcm: setmap 2f000, 2000; 0xc7816000 -> 2f000 unknown0: at port 0x201 on isa0 pnpinfo output: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16X PnP Logical Device ID: CTL0043 0x43008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CTL7005 0x05708c0e #1 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game TAG Start DF Good Configuration I/O Range 0x201 .. 0x201, alignment 0x1, len 0x1 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1 [16-bit addr] TAG End DF End Tag Successfully got 48 resources, 2 logical fdevs -- card select # 0x0001 CSN CTL00f0 (0xf0008c0e), Serial Number 0xffffffff Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 10 0 DMA 0 1 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 I hope this is helpful and I appreciate the work you've put into this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:33:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A22C015769 for ; Fri, 21 Jan 2000 15:33:20 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA96227; Fri, 21 Jan 2000 15:33:18 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA43776; Fri, 21 Jan 2000 15:33:19 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 15:33:19 -0800 From: "David O'Brien" To: Will Andrews Cc: Mohit Aron , freebsd-current@FreeBSD.ORG Subject: Re: when is FreeBSD-4.0 up for release ? Message-ID: <20000121153318.A43755@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001212214.QAA17007@cs.rice.edu> <20000121173353.C541@shadow.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121173353.C541@shadow.blackdawn.com>; from andrews@technologist.com on Fri, Jan 21, 2000 at 05:33:53PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 05:33:53PM -0500, Will Andrews wrote: > On Fri, Jan 21, 2000 at 04:14:47PM -0600, Mohit Aron wrote: > > Hi, > > wasn't the release date set for Jan 15 ? Anyone knows the new > > tentative date ? Thanks, > > That was the Feature Freeze (tm). Jordan hasn't made any "official" > announcements about the Feature Freeze yet, I don't think. What do you mean? JKH said there would be a Feature Freeze on Jan 15 and it happened. What more did JKH need to say on the topic? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:35:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9BD4E15589 for ; Fri, 21 Jan 2000 15:35:19 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA86506; Fri, 21 Jan 2000 16:35:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA15455; Fri, 21 Jan 2000 16:35:21 -0700 (MST) Message-Id: <200001212335.QAA15455@harmony.village.org> To: Matthew Hunt Subject: Re: Please help spread the CVSup mirror load more evenly Cc: Andre Oppermann , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 21 Jan 2000 14:47:56 PST." <20000121144756.A8163@wopr.caltech.edu> References: <20000121144756.A8163@wopr.caltech.edu> <3888D870.2416BFE8@pipeline.ch> <20000121231050.A14324@skriver.dk> <3888E01C.1E568130@pipeline.ch> Date: Fri, 21 Jan 2000 16:35:21 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > Does it matter? Who cvsup's regulary more than once or twice a day? : > Committers AFAIK do cvs directly. : I "cvs co" from my local copy of the repository, which is kept : up-to-date using cvsup. When I'm making lots of commits, I'll do 10-20 cvsups in a day, but usually it is more like 3-5 depending on what I need to track. I cvsup the tree itself and co from there. That's why I wrote the script I did. I'll clean it up tonight and post it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:40:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9539F157C9 for ; Fri, 21 Jan 2000 15:40:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA96296; Fri, 21 Jan 2000 15:40:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA43831; Fri, 21 Jan 2000 15:40:14 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 15:40:14 -0800 From: "David O'Brien" To: John Polstra Cc: current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121154014.B43755@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200001211911.LAA11686@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001211911.LAA11686@vashon.polstra.com>; from jdp@polstra.com on Fri, Jan 21, 2000 at 11:11:17AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 11:11:17AM -0800, John Polstra wrote: > I have been reminded that a few mirrors (cvsup8 in particular) filter > pings. Don't take ping failures as a certain indication that the > server is down. On Fri, Jan 21, 2000 at 11:22:33AM -0800, Amancio Hasty wrote: > So have the cvsup client do the pinging to the server and extract > its current work load or other vital statistic. I have to agree with Amancio. Otherwise how are we to determine if cvsup8 is worth our time? I personally will not be switching to it until I can determine it is a better path for me. Possibly, being ping'able should be be a requirement to being a CVSup mirror. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:45:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4CF681587D for ; Fri, 21 Jan 2000 15:45:30 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id PAA21797; Fri, 21 Jan 2000 15:43:23 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id PAA12142; Fri, 21 Jan 2000 15:43:22 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id PAA08367; Fri, 21 Jan 2000 15:41:59 -0800 (PST) Message-ID: <3888F01E.AF550589@softweyr.com> Date: Fri, 21 Jan 2000 16:47:42 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve Kargl Cc: Andre Oppermann , Jesper Skriver , Garance A Drosihn , John Polstra , current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly References: <200001212246.OAA36108@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > > Andre Oppermann wrote: > > Jesper Skriver wrote: > > > > > > > > You will risk hitting 2 different server in 2 rapid cvsup run's, where > > > the first may be more up to date than the next, as Jordan wrote earlier > > > in this thread ... > > > > Does it matter? Who cvsup's regulary more than once or twice a day? > > Committers AFAIK do cvs directly. > > > > %cvsup > Damn! Forgot I don't want src-sys --> Hit ^C. > %vi ~/supfile Remove src-sys > %cvsup > > or > > %cvsup > Damn! Forgot I want to remove sup/src-sys/refuse --> Hit ^C. > %rm sup/src-sys/refuse > %cvsup > > Yes, I've done both scenarios. Perhaps an option to CVSup to test a group of servers and render a "rating" for each, or to choose a "best" one. Then an intelligent human being could use this information to occasionally change which cvsup server they use. Such a tool wouldn't be specific to CVSup, of course, and probably already exists in benchmarks. Suggestions? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:47:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D1BB8156CB for ; Fri, 21 Jan 2000 15:47:27 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA96344; Fri, 21 Jan 2000 15:47:27 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA43908; Fri, 21 Jan 2000 15:47:27 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 15:47:27 -0800 From: "David O'Brien" To: Jason Evans Cc: current@freebsd.org Subject: Re: even more breakage in current Message-ID: <20000121154727.C43755@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000121101157.A18956@dub.net> <20000121142251.D27689@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121142251.D27689@sturm.canonware.com>; from jasone@canonware.com on Fri, Jan 21, 2000 at 02:22:51PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 02:22:51PM -0800, Jason Evans wrote: > > I did a 'make includes' during my testing, so I didn't have this > problem. ... > > In any case, doing a 'make includes' will get you past this. But this is not a very satisfiable bootstrap requirement. We need to keep in mind that that cd /usr/src cvs up make world is how it is done. If things wont build, then a solution w/in the "world" Makefiles need to be found. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 15:48: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id E7AE0158F1 for ; Fri, 21 Jan 2000 15:48:00 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id PAA22521; Fri, 21 Jan 2000 15:46:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001212346.PAA22521@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andre Oppermann Cc: "Louis A. Mamakos" , Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: Your message of "Sat, 22 Jan 2000 00:13:08 +0100." <3888E804.1BA82919@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 15:46:17 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My only point is that the first response to a problem isn't to necessarily > > pull out emacs and start hacking away on code. > > Yea, it is easier to do in a regular zone file then to implement the > network measurement logic into cvsup. Yes, it is a rather cool idea to rotate on the cvs servers without respect to latency, work load or rate of service response from the server. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16: 2:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 02B431571C; Fri, 21 Jan 2000 16:02:28 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 15-119.008.popsite.net ([209.69.195.119] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12Bo0U-00065H-00; Fri, 21 Jan 2000 17:02:23 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 3AF24191D; Fri, 21 Jan 2000 19:02:10 -0500 (EST) Date: Fri, 21 Jan 2000 19:02:10 -0500 From: Will Andrews To: David O'Brien Cc: Will Andrews , Mohit Aron , freebsd-current@FreeBSD.ORG Subject: Re: when is FreeBSD-4.0 up for release ? Message-ID: <20000121190210.A7072@shadow.blackdawn.com> References: <200001212214.QAA17007@cs.rice.edu> <20000121173353.C541@shadow.blackdawn.com> <20000121153318.A43755@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121153318.A43755@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Jan 21, 2000 at 03:33:19PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 03:33:19PM -0800, David O'Brien wrote: > What do you mean? JKH said there would be a Feature Freeze on Jan 15 and > it happened. What more did JKH need to say on the topic? I lost some mail from early this week, but I didn't get anything from Jordan saying the FF was in effect. He said it would be in effect January 15th - not necessarily that it went into effect. Perhaps I'm just twisting words a little bit. -- Will Andrews 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16: 4:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5A4871564E; Fri, 21 Jan 2000 16:04:26 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id TAA71532; Fri, 21 Jan 2000 19:03:52 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 21 Jan 2000 19:03:51 -0500 (EST) From: Chuck Robey To: "David O'Brien" Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <20000121154014.B43755@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, David O'Brien wrote: > I have to agree with Amancio. Otherwise how are we to determine if > cvsup8 is worth our time? I personally will not be switching to it until > I can determine it is a better path for me. > > Possibly, being ping'able should be be a requirement to being a CVSup > mirror. I don't know ... I think it might be a good idea for the cvsup client to make a connection to a cvsup master, get redirected from that master to the actual handler of the connection, and then work. That way, a config file on the master could be set up to know the capabilities of the other machines (network availability, machine speed, etc) and dole out connections weighted on that. If a new machine comes on line, no one really needs to know about it except whoever does the config file for the master. Any slave machine, when connected, if it was overloaded, could send the client back to the master with a packet telling the master of the slave's overload condition. A little cryptography would make that hard to cheat on. That way, the master could stay updated on the various slaves conditions (to react to overload). This would need, tho, new clients that would be able to receive a redirection, to work. And, obviously a new master. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16:20: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id B36D214D14 for ; Fri, 21 Jan 2000 16:20:01 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id QAA03864; Fri, 21 Jan 2000 16:19:04 -0800 (PST) Date: Fri, 21 Jan 2000 16:19:04 -0800 From: Brooks Davis To: Wes Peters Cc: Steve Kargl , Andre Oppermann , Jesper Skriver , Garance A Drosihn , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121161904.B23771@orion.ac.hmc.edu> References: <200001212246.OAA36108@troutmask.apl.washington.edu> <3888F01E.AF550589@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <3888F01E.AF550589@softweyr.com>; from wes@softweyr.com on Fri, Jan 21, 2000 at 04:47:42PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 04:47:42PM -0700, Wes Peters wrote: > Perhaps an option to CVSup to test a group of servers and render a "rating" > for each, or to choose a "best" one. Then an intelligent human being could > use this information to occasionally change which cvsup server they use. > > Such a tool wouldn't be specific to CVSup, of course, and probably already > exists in benchmarks. Suggestions? For the actual testing, netperf would probalby be a good choice assuming the server admins will cooperate (or the server was integrated into cvsupd). The normal version is a standalone program, but there is a libritized version as part of the gloperf daemon which is part of the globus project (www.globus.org). As to storing the list of ratings, it would be really nice if such a tool cached them on a per-subnet bases so us telecommuters can move around and cvsup from random ethernet ports with dhcp support. In general, ratings based on network performance are likely to be good for quite some time. The things you probably wouldn't want to cache would be servers loads. Randomly wondering off on a tangent, if clients had nice caches of network information, it might be nice if servers would keep eachother informed of their loads so if they were unnecessicairly busy though could say "go away, here's a list of everyone else's loads so you can pick a good one next time." Of course this is all idle chit-chat until the decididly non-trivial problem of out of sync servers is solved. -- Brooks -- "They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16:22: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id E99C5156B4; Fri, 21 Jan 2000 16:22:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id QAA22981; Fri, 21 Jan 2000 16:21:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001220021.QAA22981@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@FreeBSD.ORG Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: Your message of "Fri, 21 Jan 2000 15:40:14 PST." <20000121154014.B43755@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 16:21:48 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David, John can implement a ping echo packet protocol for cvsup whose response can have "cool" information on the server. Steven's book on Networking already has the code for doing network latency calculations . It is more like if John has the time to implement such scheme .... -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16:27:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 814B415620 for ; Fri, 21 Jan 2000 16:27:19 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 51822 invoked by uid 1001); 22 Jan 2000 00:25:41 -0000 Date: Fri, 21 Jan 2000 16:25:41 -0800 From: Jason Evans To: David O'Brien Cc: current@freebsd.org Subject: Re: even more breakage in current Message-ID: <20000121162540.E27689@sturm.canonware.com> References: <20000121101157.A18956@dub.net> <20000121142251.D27689@sturm.canonware.com> <20000121154727.C43755@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121154727.C43755@dragon.nuxi.com>; from obrien@freebsd.org on Fri, Jan 21, 2000 at 03:47:27PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 03:47:27PM -0800, David O'Brien wrote: > On Fri, Jan 21, 2000 at 02:22:51PM -0800, Jason Evans wrote: > > > > I did a 'make includes' during my testing, so I didn't have this > > problem. > ... > > > > In any case, doing a 'make includes' will get you past this. > > But this is not a very satisfiable bootstrap requirement. > We need to keep in mind that that > cd /usr/src > cvs up > make world > > is how it is done. If things wont build, then a solution w/in the > "world" Makefiles need to be found. I often do a 'make includes' to be able to iteratively test changes. Once I'm happy that the changes are sound, there is no way to assure that the changes didn't cause a bootstrapping problem like this one. This is the second time that this has been a problem for me. The first time I caught it and put a hack in the libc_r Makefile: CFLAGS+=-I${.CURDIR}/../../include Marcel said that this is not appropriate for reasons I didn't understand. If this isn't appropriate, and the build system is structured such that it pulls definitions from the installed headers, then what *is* the correct solution? I enjoy breaking the world even less than people enjoy dealing with my breakage. I generally do a 'make world' before checking in non-trivial changes (and did so in this case), but obviously, that doesn't catch this kind of problem. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16:27:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 281CF150DD; Fri, 21 Jan 2000 16:27:32 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 15-119.008.popsite.net ([209.69.195.119] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12BoOZ-0007Rm-00; Fri, 21 Jan 2000 17:27:16 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id D4E4D1ABE; Fri, 21 Jan 2000 19:27:08 -0500 (EST) Date: Fri, 21 Jan 2000 19:27:08 -0500 From: Will Andrews To: David O'Brien Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121192708.E7072@shadow.blackdawn.com> References: <200001211911.LAA11686@vashon.polstra.com> <20000121154014.B43755@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121154014.B43755@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Jan 21, 2000 at 03:40:14PM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 03:40:14PM -0800, David O'Brien wrote: > I have to agree with Amancio. Otherwise how are we to determine if > cvsup8 is worth our time? I personally will not be switching to it until > I can determine it is a better path for me. > > Possibly, being ping'able should be be a requirement to being a CVSup > mirror. Traceroute works fine. If you knew the history of fadeto.blackened.com, you'd know why ICMPs are filtered out (not that I'm an authoritative source for that sort of thing, of course). -- Will Andrews 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16:46:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id CBED914E4A; Fri, 21 Jan 2000 16:46:29 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id TAA93427; Fri, 21 Jan 2000 19:58:50 -0500 (EST) Date: Fri, 21 Jan 2000 19:58:50 -0500 (EST) From: Ben Rosengart To: "David O'Brien" Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <20000121154014.B43755@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, David O'Brien wrote: > Possibly, being ping'able should be be a requirement to being a CVSup > mirror. I don't think it makes sense to try to dictate network policy to people who are doing the FreeBSD Project a favor. Anyway, an application-level round-trip time measurement would probably be more accurate, because some routers treat ICMP and TCP packets differently. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 16:47: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 3D498156DD; Fri, 21 Jan 2000 16:46:39 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id TAA73678; Fri, 21 Jan 2000 19:43:09 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 21 Jan 2000 19:42:54 -0500 (EST) From: Chuck Robey To: Will Andrews Cc: "David O'Brien" , Mohit Aron , freebsd-current@FreeBSD.ORG Subject: Re: when is FreeBSD-4.0 up for release ? In-Reply-To: <20000121190210.A7072@shadow.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Will Andrews wrote: > On Fri, Jan 21, 2000 at 03:33:19PM -0800, David O'Brien wrote: > > What do you mean? JKH said there would be a Feature Freeze on Jan 15 and > > it happened. What more did JKH need to say on the topic? > > I lost some mail from early this week, but I didn't get anything from > Jordan saying the FF was in effect. He said it would be in effect > January 15th - not necessarily that it went into effect. > > Perhaps I'm just twisting words a little bit. You really must not have been listening, Will. Jordan did everything *including* falling down laughing at about 3-4 different sets of folks who misinterpreted feature freeze to mean code freeze. I could understand, somewhat, you making that mistake, but missing the fact of the feature freeze itself? I think it was David O'Brien, in fact, who posted it here in 2 inch high letters! No kidding. You must have been hitting the delete key too fast, on several different days. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:13: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 24C8F1568E; Fri, 21 Jan 2000 17:12:59 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA32330; Sat, 22 Jan 2000 02:12:41 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Brian Somers Cc: current@FreeBSD.ORG, Jordan Hubbard , Alfred Perlstein Subject: Re: Warning: ioctl(... TUNSLMODE ...) to be depricated.... References: <200001210835.IAA00404@hak.lan.Awfulhak.org> From: Dag-Erling Smorgrav Date: 22 Jan 2000 02:12:40 +0100 In-Reply-To: Brian Somers's message of "Fri, 21 Jan 2000 08:35:18 +0000" Message-ID: Lines: 15 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: > Unless there are objections in the next day or two, I'm going to > deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD. Where TUNSLMODE > prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a > 4-byte network-byte-order address family. Don't take it out quite yet. I asked Alfred to implement TUNSLMODE for a reason; I was working on some VPN software at the time. There are cases where you want a full sockaddr, not just the address family. The next-hop address is not necessarily the same as the destination address, if the interface is in broadcast mode (as opposed to ptp). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:23:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id C95C815606; Fri, 21 Jan 2000 17:23:37 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA59410; Fri, 21 Jan 2000 17:23:18 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001220123.RAA59410@gndrsh.dnsmgr.net> Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001220021.QAA22981@rah.star-gate.com> from Amancio Hasty at "Jan 21, 2000 04:21:48 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 21 Jan 2000 17:23:17 -0800 (PST) Cc: obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi David, > > John can implement a ping echo packet protocol for cvsup whose > response can have "cool" information on the server. Steven's > book on Networking already has the code for doing network latency > calculations . It is more like if John has the time to implement > such scheme .... You don't even need to modify the protocol. Just write a small tcp program that times the 3 way handshake on open to all the servers, take the one with the sortest time and spit that out for the user to stuff in his cvsupfile. 15 lines of perl should be more than enough :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:31:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 68AC815562 for ; Fri, 21 Jan 2000 17:31:16 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id UAA11593; Fri, 21 Jan 2000 20:31:06 -0500 (EST) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA04694; Fri, 21 Jan 2000 20:31:10 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA04685; Fri, 21 Jan 2000 20:31:10 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Fri, 21 Jan 2000 20:31:10 -0500 (EST) From: Kenneth Wayne Culver To: "Jeremy L. Stock" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Creative ViBRA16X Problem (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same soundcard, and as of right now, the only problem I have with it is that sometimes it will play static instead of the sound I wanted it to play. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 21 Jan 2000, Jeremy L. Stock wrote: > Thought I'd post this to -current also since it gives a little more detail > (I hope). I can't believe I'm the only one experiencing this since it's > still around when I do a fresh install from a snapshot. Not a huge deal for > me since I can use Windows for audio, but I'd rather use FreeBSD again. I'm > sure this will get addressed before 4.0R. I just wanted to make sure it's a > known issue. > > -- > Jeremy L. Stock > ICQ 46329337 > Fax # 612-629-6540 > ---------- Forwarded message ---------- > Date: Tue, 18 Jan 2000 22:14:44 -0600 (CST) > From: Jeremy L. Stock > To: gandalf@vilnya.demon.co.uk > Subject: Creative ViBRA16X Problem > > I posted this on -current almost a week ago and only received one response > that didn't solve the problem. Audio hasn't played correctly for me since > December 27th. Now when I try to play audio, it just stutters. > > I'm not sure when it broke since I went from -current as of the 27th to > -current as of the 11th and now earlier today. The problem still remains > even after a total reinstall. > > I just wanted to make sure you were aware of it and make sure you had a > chance to correct it before 4.0R. Here's some info. Let me know if > you need anything else. > > Copyright (c) 1992-2000 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: Tue Jan 18 20:00:28 CST 2000 > root@nic-31-c23-178.mn.mediaone.net:/usr/src/sys/compile/NIC > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 350796057 Hz > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features=0x8021bf > AMD Features=0x80000800 > real memory = 134217728 (131072K bytes) > avail memory = 127315968 (124332K bytes) > Preloaded elf kernel "kernel" at 0xc02c2000. > sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 > drq 0,1 on isa0 > sbc0: setting card to irq 10, drq 0, 1 > pcm0: on sbc0 > unknown0: at port 0x201 on isa0 > > And from boot -v (Let me know if I left an important section out) > > Trying Read_Port at 203 > CTL0043: start dependant > CTL0043: adding irq mask 0x20 > CTL0043: adding dma mask 0x2 > CTL0043: adding dma mask 0x8 > CTL0043: adding io range 0x220-0x22f, size=0x10, align=0x1 > CTL0043: adding io range 0x330-0x331, size=0x2, align=0x1 > CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1 > CTL0043: start dependant > CTL0043: adding irq mask 0x6a0 > CTL0043: adding dma mask 0xb > CTL0043: adding dma mask 0xb > CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 > CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30 > CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1 > CTL0043: start dependant > CTL0043: adding irq mask 0x6a0 > CTL0043: adding dma mask 0xb > CTL0043: adding dma mask 0xb > CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 > CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30 > CTL0043: start dependant > CTL0043: adding irq mask 0x6a0 > CTL0043: adding dma mask 0xb > CTL0043: adding dma mask 0xb > CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 > CTL0043: start dependant > CTL0043: adding irq mask 0x6a0 > CTL0043: adding dma mask 0xb > CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 > CTL0043: adding io range 0x300-0x331, size=0x2, align=0x10 > CTL0043: adding io range 0x388-0x397, size=0x4, align=0x4 > CTL0043: start dependant > CTL0043: adding irq mask 0x6a0 > CTL0043: adding dma mask 0xb > CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 > CTL0043: end dependant > CTL7005: start dependant > CTL7005: adding io range 0x201-0x201, size=0x1, align=0x1 > CTL7005: start dependant > CTL7005: adding io range 0x200-0x20f, size=0x1, align=0x1 > CTL7005: end dependant > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 on isa0 > sbc0: setting card to irq 10, drq 0, 1 > pcm0: on sbc0 > pcm: setmap 2d000, 2000; 0xc7814000 -> 2d000 > pcm: setmap 2f000, 2000; 0xc7816000 -> 2f000 > unknown0: at port 0x201 on isa0 > > pnpinfo output: > > Checking for Plug-n-Play devices... > > Card assigned CSN #1 > Vendor ID CTL00f0 (0xf0008c0e), Serial Number 0xffffffff > PnP Version 1.0, Vendor Version 16 > Device Description: Creative ViBRA16X PnP > > Logical Device ID: CTL0043 0x43008c0e #0 > Device Description: Audio > TAG Start DF > Good Configuration > IRQ: 5 - only one type (true/edge) > DMA: channel(s) 1 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 > [16-bit addr] > I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > TAG Start DF > Sub-optimal Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 > [16-bit addr] > TAG Start DF > Sub-optimal Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > TAG End DF > > Logical Device ID: CTL7005 0x05708c0e #1 > Compatible Device ID: PNPb02f (2fb0d041) > Device Description: Game > TAG Start DF > Good Configuration > I/O Range 0x201 .. 0x201, alignment 0x1, len 0x1 > [16-bit addr] > TAG Start DF > Acceptable Configuration > I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1 > [16-bit addr] > TAG End DF > End Tag > > Successfully got 48 resources, 2 logical fdevs > -- card select # 0x0001 > > CSN CTL00f0 (0xf0008c0e), Serial Number 0xffffffff > > Logical device #0 > IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 > IRQ 10 0 > DMA 0 1 > IO range check 0x00 activate 0x01 > > Logical device #1 > IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 > IRQ 0 0 > DMA 4 4 > IO range check 0x00 activate 0x01 > > I hope this is helpful and I appreciate the work you've put into this. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:34:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id B8030155F4; Fri, 21 Jan 2000 17:34:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id RAA23696; Fri, 21 Jan 2000 17:33:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001220133.RAA23696@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Rodney W. Grimes" Cc: obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: Your message of "Fri, 21 Jan 2000 17:23:17 PST." <200001220123.RAA59410@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 17:33:21 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi David, > > > > John can implement a ping echo packet protocol for cvsup whose > > response can have "cool" information on the server. Steven's > > book on Networking already has the code for doing network latency > > calculations . It is more like if John has the time to implement > > such scheme .... > > You don't even need to modify the protocol. Just write a small > tcp program that times the 3 way handshake on open to all the > servers, take the one with the sortest time and spit that out > for the user to stuff in his cvsupfile. > > 15 lines of perl should be more than enough :-) > Hi, Thats gross server load balancing . The network travel time does not tell you how how loaded the machine is or the server. There are couple of RFCs on network load balancing with respect to servers or services and I am sure that there are also widely available research papers. Here is a "cool" pointer to a RFC archival with a query capability... http://sunsite.auc.dk/RFC/ Have Fun Guys! -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:34:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 591E61568C for ; Fri, 21 Jan 2000 17:34:20 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA97066; Fri, 21 Jan 2000 17:34:19 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA44119; Fri, 21 Jan 2000 17:34:20 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 17:34:20 -0800 From: "David O'Brien" To: Will Andrews Cc: freebsd-current@FreeBSD.ORG Subject: Re: when is FreeBSD-4.0 up for release ? Message-ID: <20000121173420.A44094@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <200001212214.QAA17007@cs.rice.edu> <20000121173353.C541@shadow.blackdawn.com> <20000121153318.A43755@dragon.nuxi.com> <20000121190210.A7072@shadow.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121190210.A7072@shadow.blackdawn.com>; from andrews@technologist.com on Fri, Jan 21, 2000 at 07:02:10PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 07:02:10PM -0500, Will Andrews wrote: > On Fri, Jan 21, 2000 at 03:33:19PM -0800, David O'Brien wrote: > > What do you mean? JKH said there would be a Feature Freeze on Jan 15 and > > it happened. What more did JKH need to say on the topic? > > I lost some mail from early this week, but I didn't get anything from > Jordan saying the FF was in effect. He said it would be in effect > January 15th - not necessarily that it went into effect. So every little date event needs a confirmation?? Why isn't the fact that JKH didn't resend the event not mean that it is in effect? Ok, for everyone that isn't sure that today is Friday after looking at you calander last night which announced Jan 21st is Friday: ### # ##### ### #### # # # # # # # #### # # # # # # # # # #### ####### # ##### # ##### ## # # # # # # # # # # # # ##### # # # # # # # # # ##### # # # ###### # # # # # # # # # # # # # # ##### # # # -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:39:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A92A7155A9 for ; Fri, 21 Jan 2000 17:39:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA97097; Fri, 21 Jan 2000 17:39:23 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA44157; Fri, 21 Jan 2000 17:39:23 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 17:39:23 -0800 From: "David O'Brien" To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121173923.A44132@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000121154014.B43755@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Fri, Jan 21, 2000 at 07:03:51PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote: > I don't know ... I think it might be a good idea for the cvsup client to > make a connection to a cvsup master, get redirected from that master to > the actual handler of the connection, and then work. That way, a config > file on the master could be set up to know the capabilities of the other > machines (network availability, machine speed, etc) and dole out > connections weighted on that. How is a cvsup master to know anything about the path from me to any given cvsup mirror? Knowing something about the path from me to the master and the path from the master to the mirror tells zero about the path from me to the mirror. Being on an .EDU network, I have a *very* different path to other .EDU machine participating in Inetnet2. My path to cvsup3 is a prime example. This "cvsup master" will have no idea about this. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:39:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1BED5155C5; Fri, 21 Jan 2000 17:39:43 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA59492; Fri, 21 Jan 2000 17:39:40 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001220139.RAA59492@gndrsh.dnsmgr.net> Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001220133.RAA23696@rah.star-gate.com> from Amancio Hasty at "Jan 21, 2000 05:33:21 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 21 Jan 2000 17:39:39 -0800 (PST) Cc: obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hi David, > > > > > > John can implement a ping echo packet protocol for cvsup whose > > > response can have "cool" information on the server. Steven's > > > book on Networking already has the code for doing network latency > > > calculations . It is more like if John has the time to implement > > > such scheme .... > > > > You don't even need to modify the protocol. Just write a small > > tcp program that times the 3 way handshake on open to all the > > servers, take the one with the sortest time and spit that out > > for the user to stuff in his cvsupfile. > > > > 15 lines of perl should be more than enough :-) > > > Hi, > > Thats gross server load balancing . The network travel time > does not tell you how how loaded the machine is or the server. It may be gross to the server but it is optimal to the networks :-) > > There are couple of RFCs on network load balancing with > respect to servers or services and I am sure that there > are also widely available research papers. Most of those concentrate on balancing the load on the server itself. How about balancing the load on the network paths, I doubt very much that we have a server load problem near as much as we have a network load problem due to people not having ready access to the data that says ``this server is closest network wise to me''. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 17:41:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3365415026 for ; Fri, 21 Jan 2000 17:41:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA97163; Fri, 21 Jan 2000 17:41:53 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA44175; Fri, 21 Jan 2000 17:41:54 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 17:41:54 -0800 From: "David O'Brien" To: Will Andrews Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121174154.B44132@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001211911.LAA11686@vashon.polstra.com> <20000121154014.B43755@dragon.nuxi.com> <20000121192708.E7072@shadow.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121192708.E7072@shadow.blackdawn.com>; from andrews@technologist.com on Fri, Jan 21, 2000 at 07:27:08PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 07:27:08PM -0500, Will Andrews wrote: > Traceroute works fine. Traceroute can be annoying to use as it is much slower. And not all routers respond "properly" to it. > If you knew the history of fadeto.blackened.com, you'd know why ICMPs > are filtered out I really don't give a rats a** about fadeto.blackened.com. I am part of FreeBSD and that is what I care about. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 18: 0:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 51A4514F87; Fri, 21 Jan 2000 17:59:27 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA73880; Fri, 21 Jan 2000 20:56:59 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 21 Jan 2000 20:56:29 -0500 (EST) From: Chuck Robey To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <20000121173923.A44132@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, David O'Brien wrote: > On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote: > > I don't know ... I think it might be a good idea for the cvsup client to > > make a connection to a cvsup master, get redirected from that master to > > the actual handler of the connection, and then work. That way, a config > > file on the master could be set up to know the capabilities of the other > > machines (network availability, machine speed, etc) and dole out > > connections weighted on that. > > How is a cvsup master to know anything about the path from me to any > given cvsup mirror? Knowing something about the path from me to the > master and the path from the master to the mirror tells zero about the > path from me to the mirror. > > Being on an .EDU network, I have a *very* different path to other .EDU > machine participating in Inetnet2. My path to cvsup3 is a prime example. > This "cvsup master" will have no idea about this. I guess it means, is the main component trying to be balanced the server resources or the network resources. I may be wrong, but I think that the server resources are more likely to be the most important bottleneck, and this method detects that, with minimal network effects. If you think that it's really the network that's going to be the bottleneck, then you wouldn't want to use this method. I don't think I'm wrong, but I'm willing to listen to arguments on it. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 18:10:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 0EE971574C for ; Fri, 21 Jan 2000 18:10:00 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA06441; Fri, 21 Jan 2000 18:18:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001220218.SAA06441@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Steven Jurczyk" Cc: freebsd-current@freebsd.org Subject: Re: problems with mylex raid scsi In-reply-to: Your message of "Fri, 21 Jan 2000 09:09:39 PST." <200001211709.JAA06286@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jan 2000 18:18:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I try to install FreeBSD 4.0-CURRENT snapshot on > server with have mylex accele raid 250 controler. > FreeBSD installs on it without any problems, but > can't boot from it. I try 2 and 8 GB BIOS mode, > also FreeBSD and BIOS geometry (trick with small > dos partition). Depending of situation boot > loader shows Invalid slice, registers (int 0d, > err 00, eip a658, cs f000) and System halted info > or boot manager can't find loader (it bells when > I select F1 - FreeBSD). It'd help if you could sort out this pile of details and list the actual combinations that you tried; at the moment I can't even begin to guess at the cause of your problem(s). More or less in summary: Invalid slice - you have the geometry mixed up Bootmanager beep - you have the geometry mixed up differently Register dump - looks like a BIOS bug, but hard to tell without eax System halted - should have register dump, see above If you can offer some more details, I can work on trying to reproduce the problem. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 18:10:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 233061518B for ; Fri, 21 Jan 2000 18:09:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA97304; Fri, 21 Jan 2000 18:09:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA44289; Fri, 21 Jan 2000 18:09:14 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2000 18:09:14 -0800 From: "David O'Brien" To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000121180914.C44132@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000121173923.A44132@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Fri, Jan 21, 2000 at 08:56:29PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 08:56:29PM -0500, Chuck Robey wrote: > I guess it means, is the main component trying to be balanced the server > resources or the network resources. I may be wrong, but I think that the > server resources are more likely to be the most important bottleneck, and Not really. If I have a poor network connection to the CVSup mirror used, then I'll spend much long connected to it. Thus causing a higher "load" on the mirror. Where "load" is either one of the connection slots, or actual kernel resource load if I have 20% packet loss and thus cause a lot of retransmissions to occur. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 18:20:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 8831715696 for ; Fri, 21 Jan 2000 18:20:46 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id SAA24103; Fri, 21 Jan 2000 18:20:14 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA27992; Fri, 21 Jan 2000 18:20:14 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id SAA17480; Fri, 21 Jan 2000 18:18:53 -0800 (PST) Message-ID: <388914E4.B508D919@softweyr.com> Date: Fri, 21 Jan 2000 19:24:36 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Amancio Hasty Cc: current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly References: <200001212346.PAA22521@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > > > My only point is that the first response to a problem isn't to necessarily > > > pull out emacs and start hacking away on code. > > > > Yea, it is easier to do in a regular zone file then to implement the > > network measurement logic into cvsup. > > Yes, it is a rather cool idea to rotate on the cvs servers without > respect to latency, work load or rate of service response from > the server. Thank you. I was beginning to wonder if I am the only one here who thinks blind round-robin DNS is a bad hack. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 18:21:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 2F27B15425; Fri, 21 Jan 2000 18:21:11 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA59574; Fri, 21 Jan 2000 18:19:39 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001220219.SAA59574@gndrsh.dnsmgr.net> Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: from Chuck Robey at "Jan 21, 2000 08:56:29 pm" To: chuckr@picnic.mat.net (Chuck Robey) Date: Fri, 21 Jan 2000 18:19:39 -0800 (PST) Cc: obrien@FreeBSD.ORG (David O'Brien), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 21 Jan 2000, David O'Brien wrote: > > > On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote: > > > I don't know ... I think it might be a good idea for the cvsup client to > > > make a connection to a cvsup master, get redirected from that master to > > > the actual handler of the connection, and then work. That way, a config > > > file on the master could be set up to know the capabilities of the other > > > machines (network availability, machine speed, etc) and dole out > > > connections weighted on that. > > > > How is a cvsup master to know anything about the path from me to any > > given cvsup mirror? Knowing something about the path from me to the > > master and the path from the master to the mirror tells zero about the > > path from me to the mirror. > > > > Being on an .EDU network, I have a *very* different path to other .EDU > > machine participating in Inetnet2. My path to cvsup3 is a prime example. > > This "cvsup master" will have no idea about this. > > I guess it means, is the main component trying to be balanced the server > resources or the network resources. I may be wrong, but I think that the > server resources are more likely to be the most important bottleneck, and > this method detects that, with minimal network effects. > > If you think that it's really the network that's going to be the > bottleneck, then you wouldn't want to use this method. I don't think I'm > wrong, but I'm willing to listen to arguments on it. I think, and am pretty sure as hostmaster for cvsup4, that the bottleneck is a combination of both. We use the max connection limit to control the load on the server, and simply refuse connections beyond the acceptable load limit. As far as I know none of the servers run unlimited connection counts so we already have a load controlling mechanism. I know from a network bandwidth point of view I can tell when someone with T-1 or better comes on and pulls a full copy from us, it shows up quite nicely in the load graphs. I also know from looking at our logs that some people would get faster cvsup's if they changed which mirror they are pulling from. (Anyone directly attached to Verio should no longer be using us, but the new Verio provided server instead.) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 18:26:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from srv1.nms.cv.net (srv1.nms.cv.net [167.206.112.64]) by hub.freebsd.org (Postfix) with ESMTP id 87A6314D81 for ; Fri, 21 Jan 2000 18:26:15 -0800 (PST) (envelope-from scott@wpsystems.net) Received: from s1.nassau.cv.net (s1.optonline.net [167.206.112.6]) by srv1.nms.cv.net (8.9.1b+Sun/8.9.1) with ESMTP id VAA18011; Fri, 21 Jan 2000 21:26:13 -0500 (EST) Received: from wpsystems.net (d147-66.frptny.optonline.net [24.188.147.66]) by s1.nassau.cv.net (8.9.1/8.9.1) with ESMTP id VAA17456; Fri, 21 Jan 2000 21:26:13 -0500 (EST) Message-ID: <388915EF.90D99DC6@wpsystems.net> Date: Fri, 21 Jan 2000 21:29:03 -0500 From: Scott Burns Organization: Whirlpool Systems X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matt M." , current@FreeBSD.org Subject: Re: cvsup 3.4-release to -current References: <3887ECC9.7A2625F5@boda.virtualave.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matt M." wrote: > Just wondering what potential problems I am facing by going from > 3.4-release to -current. I was told on irc that my chances may not be > well. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld worked fine, but the installworld was interrupted part of the way through the install by a signal 12 to sh. I tried doing it from 3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and I got the same error every time. I ended up booting to the 3.4 install disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh would crash with a signal 12 every time. I got the following error each time: ===> bin/sync install -c -s -o root -g wheel -m 555 sync /bin install -c -o root -g wheel -m 444 sync.8.gz /usr/share/man/man8 ===> bin/test install -c -s -o root -g wheel -m 555 test /bin *** Signal 12 Stop. *** Error code 12 ------- Scott Burns scott@wpsystems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 20:35: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 291C8156B1 for ; Fri, 21 Jan 2000 20:34:51 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 28994 invoked from network); 22 Jan 2000 04:34:42 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Jan 2000 04:34:42 -0000 Date: Sat, 22 Jan 2000 15:34:40 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Jason Evans Cc: Bill Swingle , current@FreeBSD.ORG Subject: Re: even more breakage in current In-Reply-To: <20000121142251.D27689@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Jason Evans wrote: > On Fri, Jan 21, 2000 at 10:11:57AM -0800, Bill Swingle wrote: >... > > cc -DPROF -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.po > > /tmp/ccg65684.s: Assembler messages: > > /tmp/cco65681.s: Assembler messages: > > /tmp/cco65681.s:361: Error: invalid character '(' in opcode > > /tmp/ccg65684.s:361: Error: invalid character '(' in opcode This happens when libc/i386/DEFS.h and libc/i386/gen/setjmp.S are current (as of Jan 21) but is out of date. > I moved some definitions from src/lib/libc/i386/DEFS.h to > src/sys/i386/include/asm.h. If the build system is looking at the > installed version of asm.h rather than the version in the source tree, this > error will occur. I did a 'make includes' during my testing, so I didn't > have this problem. > > It's my understanding that the build system is supposed to be sophisticated > enough to avoid such bootstrapping issues, but I don't understand it all > that well. Can someone explain whether this is a bug in the build system, > or if I should be doing something different? Everything should just work in this case, provided is up to date. All you could do better is commit first so that there is no window of inconsistency. > In any case, doing a 'make includes' will get you past this. Don't use `make includes' unless you are familiar enough with the build system not to need it. It _causes_ problems like this by defeating the build system (it gives a set of includes that tends not to match the libraries). It happens to fix the problem in this case (at least if you install only ). Test header changes using `NOCLEAN=1 make buildworld'. NOCLEAN is now fairly robust. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 21: 4:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 63EE414FC2; Fri, 21 Jan 2000 21:04:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA87635; Fri, 21 Jan 2000 21:59:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA17674; Fri, 21 Jan 2000 22:00:05 -0700 (MST) Message-Id: <200001220500.WAA17674@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Cc: Chuck Robey , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 21 Jan 2000 18:09:14 PST." <20000121180914.C44132@dragon.nuxi.com> References: <20000121180914.C44132@dragon.nuxi.com> <20000121173923.A44132@dragon.nuxi.com> Date: Fri, 21 Jan 2000 22:00:05 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000121180914.C44132@dragon.nuxi.com> "David O'Brien" writes: : "load" on the mirror. Where "load" is either one of the connection : slots, or actual kernel resource load if I have 20% packet loss and thus : cause a lot of retransmissions to occur. Hmmm. A thought just occurred to me. There's no need to measure these things. Lookup all the IP addresses. Do a non blocking connection to each of these machines. First one to come back with the REL16_1 response wins, and all the others get closed and you use that one. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 21: 6:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id D63CD15728 for ; Fri, 21 Jan 2000 21:06:22 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 31513 invoked from network); 22 Jan 2000 05:02:13 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Jan 2000 05:02:13 -0000 Date: Sat, 22 Jan 2000 16:02:10 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Jason Evans Cc: David O'Brien , current@FreeBSD.ORG Subject: Re: even more breakage in current In-Reply-To: <20000121162540.E27689@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Jason Evans wrote: > I often do a 'make includes' to be able to iteratively test changes. Once > I'm happy that the changes are sound, there is no way to assure that the > changes didn't cause a bootstrapping problem like this one. `make includes' breaks your test environment. The problem is harder for developers. Developers have to install new headers to test them (except for system header in the SHARED=symlinks case, which is very convenient for development but is almost equivalent to an automatic `make includes' since most header changes are in system headers). I don't see any better ways to test header changes before committing them than to keep a separate tree which is almost current, apply the changes to that tree, and do a `NOCLEAN=1 make buildworld' on it. I rarely do this :-). > This is the second time that this has been a problem for me. The first > time I caught it and put a hack in the libc_r Makefile: > > CFLAGS+=-I${.CURDIR}/../../include > > Marcel said that this is not appropriate for reasons I didn't understand. > If this isn't appropriate, and the build system is structured such that it > pulls definitions from the installed headers, then what *is* the correct > solution? The build system installs the necessary headers at the necessary times. The above gets in its way by doing the equivalent of installing headers before they are ready to be used. I think it currently doesn't actually cause in problems in libc_r/Makefile, because libc_r doesn't have any tools that need to be built with the old includes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 22:56:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D16C91553C for ; Fri, 21 Jan 2000 22:56:28 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA88066 for ; Fri, 21 Jan 2000 23:56:27 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA18881 for ; Fri, 21 Jan 2000 23:56:38 -0700 (MST) Message-Id: <200001220656.XAA18881@harmony.village.org> To: current@freebsd.org Subject: Here's what I'm using Date: Fri, 21 Jan 2000 23:56:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I said I'd clean this up and send this out. Well, I didn't get as much ceanup done as I'd have liked. The order of hosts is arbitrary and works for me. I'm sure this could be improved, especially to make the order random. Warner #!/bin/sh if [ -z "$1" ]; then hosts=" \ cvsup7.freebsd.org \ cvsup8.freebsd.org \ cvsup6.freebsd.org \ cvsup4.freebsd.org \ cvsup3.freebsd.org \ cvsup2.freebsd.org \ cvsup1.freebsd.org \ cvsup5.freebsd.org \ " else hosts=$1 shift fi echo "Will try hosts $hosts" for host in $hosts; do echo "Using host $host" for i in 1 2; do if cvsup -1 -P m -s -g ~/bin/sup/fbsd-supfile -L 2 -h $host $*; then exit; fi done done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 21 23:14: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 004861561D for ; Fri, 21 Jan 2000 23:13:57 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id NAA43869; Sat, 22 Jan 2000 13:13:13 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Sat, 22 Jan 2000 13:13:13 +0600 (NS) From: Max Khon To: John Polstra Cc: current@freebsd.org Subject: Re: rtld-elf, java + tya In-Reply-To: <200001211709.JAA11095@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Fri, 21 Jan 2000, John Polstra wrote: > Really?! Augh. Naturally this comes just hours after I have merged > the latest changes into -stable *sigh*. > > Could you please make sure your src/libexec/rtld-elf is > up-to-date? rtld.c should be at revision 1.41. yes. my src/libexec/rtld-elf/rtld.c is 1.41 > Then if you can give me a stack backtrace it would help a lot. I'll try to get backtrace on Monday (when I'll get to the office) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 0: 2: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 248B2150FC for ; Sat, 22 Jan 2000 00:02:04 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas2-43-10.dial.proxad.net [212.27.43.10]) by postfix1.free.fr (Postfix) with ESMTP id 4891D281C4; Sat, 22 Jan 2000 08:56:39 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id JAA00388; Sat, 22 Jan 2000 09:05:49 +0100 (CET) (envelope-from nsouch) Message-ID: <20000122090548.17844@armor.free.fr> Date: Sat, 22 Jan 2000 09:05:48 +0100 From: Nicolas Souchu To: "F. Heinrichmeyer" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Parallel Port Zip Drive works when EPP-Mode is choosen in Bios References: <3886F0D0.A523E8EB@fernuni-hagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3886F0D0.A523E8EB@fernuni-hagen.de>; from F. Heinrichmeyer on Thu, Jan 20, 2000 at 12:26:08PM +0100 X-Operating-System: FreeBSD armor 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 20, 2000 at 12:26:08PM +0100, F. Heinrichmeyer wrote: > > >Subject says all! This evening i will try a patch for the ata driver so >maybe all my >hardware at home will work again with current when certain patches are >applied. Nice. The newbus architecture introduces overhead in I/O and old chipsets (or old compatible modes) do not always support it. Your drive runs really faster too, doesn't it? > > >-- >Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de >FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) >tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2: 4:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from carlton.innotts.co.uk (carlton.innotts.co.uk [212.56.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 989241550D for ; Sat, 22 Jan 2000 02:04:06 -0800 (PST) (envelope-from robmel@nadt.org.uk) Received: from muffin.highwire.local (pool-1-p36.innotts.co.uk [212.56.33.36]) by carlton.innotts.co.uk (8.9.3/8.9.3) with ESMTP id KAA01822; Sat, 22 Jan 2000 10:04:03 GMT Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20]) by muffin.highwire.local (8.9.3/8.9.3) with ESMTP id KAA00390; Sat, 22 Jan 2000 10:02:25 GMT (envelope-from robmel@nadt.org.uk) Mime-Version: 1.0 X-Sender: robmel@mailhost Message-Id: In-Reply-To: References: Date: Sat, 22 Jan 2000 10:02:38 +0000 To: John Polstra , current@FreeBSD.ORG From: Robin Melville Subject: Re: Please help spread the CVSup mirror load more evenly Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:43 am -0800 21/1/00, John Polstra wrote: >[...] we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. >The newest, cvsup8, is a very high-capacity and well-connected site, >yet hardly anybody is using it. Please give it a try! Hi Might it be worth load sharing these via duplicate dns entries for cvsup.freebsd.org, so that callers get one at random? Best wishes Robin. ---------------------------------------------------------------------- Robin Melville, Addiction Information Service Nottingham Alcohol & Drug Team Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 work: robmel@nadt.org.uk Pages: http://www.nadt.org.uk/ ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2: 4:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 5F9F6155B2 for ; Sat, 22 Jan 2000 02:04:26 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 12BxP7-0005OH-0Y; Sat, 22 Jan 2000 10:04:25 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA56194; Sat, 22 Jan 2000 10:05:55 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 22 Jan 2000 10:03:25 +0000 (GMT) From: Doug Rabson To: Nicolas Souchu Cc: "F. Heinrichmeyer" , "freebsd-current@FreeBSD.ORG" Subject: Re: Parallel Port Zip Drive works when EPP-Mode is choosen in Bios In-Reply-To: <20000122090548.17844@armor.free.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, Nicolas Souchu wrote: > On Thu, Jan 20, 2000 at 12:26:08PM +0100, F. Heinrichmeyer wrote: > > > > > >Subject says all! This evening i will try a patch for the ata driver so > >maybe all my > >hardware at home will work again with current when certain patches are > >applied. > > Nice. The newbus architecture introduces overhead in I/O and old chipsets > (or old compatible modes) do not always support it. > > Your drive runs really faster too, doesn't it? Have you measured the overhead? I think it should be trivial compared to the effort of using inb/outb to poll a port. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2:34:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id B0E0D14BD4; Sat, 22 Jan 2000 02:34:55 -0800 (PST) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id XAA16002; Sat, 22 Jan 2000 23:34:35 +1300 (NZDT) Date: Sat, 22 Jan 2000 23:34:34 +1300 From: Joe Abley To: "Rodney W. Grimes" Cc: Amancio Hasty , obrien@FreeBSD.ORG, John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000122233433.A2555@patho.gen.nz> References: <200001220021.QAA22981@rah.star-gate.com> <200001220123.RAA59410@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001220123.RAA59410@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Fri, Jan 21, 2000 at 05:23:17PM -0800 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 05:23:17PM -0800, Rodney W. Grimes wrote: > You don't even need to modify the protocol. Just write a small > tcp program that times the 3 way handshake on open to all the > servers, take the one with the sortest time and spit that out > for the user to stuff in his cvsupfile. > > 15 lines of perl should be more than enough :-) Unfortunately, timing a three-way handshake would give you a very coarse measurement of the packet loss, jitter and bandwidth between the client and server. It would give you a better measurement of the latency, but still (statistically speaking) quite a poor one. Cvsup sessions tend to be long-lived, which means other factors can have much more dramatic effect on session performance: + packet loss + path bandwidth + optimisation of TCP stacks at either end to the round-trip latency of the network path (RFC1323 and SACK support, for example) The only effective way to _really_ measure the cumulative effect of all these is to model a representative cvsup session to multiple servers, and compare performance. This is pretty much what John was recommending in the first place by "why not try a different server every once in a while" :) You could automate this like this (and no doubt in other ways): + install a small, representatively-sized but junk collection on every cvsup mirror server + every week (say) pull the entire junk collection down from scratch from a selection of likely servers, and store the relative time taken to do so. This should give you a relative performance metric between the servers you measured, hopefully with local network performance variations cancelled out by the fact that all tests are run around the same time. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2:36:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6C6C214E7E for ; Sat, 22 Jan 2000 02:36:52 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA10054 for freebsd-current@freebsd.org; Sat, 22 Jan 2000 11:30:24 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA54487 for freebsd-current@freebsd.org; Sat, 22 Jan 2000 11:34:07 +0100 (CET) (envelope-from wilko) Date: Sat, 22 Jan 2000 11:34:07 +0100 From: Wilko Bulte To: "FreeBSD_current, mailing list" Subject: panic (softupdates??) on yesterdays -current (alpha machine) Message-ID: <20000122113407.A54350@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just was presented the following panic by my FreeBSD/alpha Miata box that was doing a make release: initiate_write_inode_block() at initiate_write_inode_block() +0x40 softdep_disk_io_initiation() at softdep_disk_io_initiation() + 0xac spec_strategy() at spec_strategy() +0x48 spec_vnoperate() at spec_vnoperate() +0x2c ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c bwrite() at bwrite() + 0x404 vop_stdbwrite() at vop_stdbwrite() +0x1c vop_defaultop() at vop_defaultop() + 0x2c spec_vnoperate() at spec_vnoperate() +0x2c ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c vfs_bio_awrite() at vfs_bio_awrite() + 0x484 flushbufqueues() at flushbufqueues() +0x1e8 buf_daemon() at buf_daemon() + 0x114 exception_return() at excpetion_return This is a manual transcript, no serial console. Softupdates only enabled on /usr, /usr/obj. Make release was putting it generated stuff on /usr No dump unfortunately, I'll see if I can catch it again -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2:40:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id C214A14C92 for ; Sat, 22 Jan 2000 02:40:18 -0800 (PST) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id XAA22814; Sat, 22 Jan 2000 23:39:29 +1300 (NZDT) Date: Sat, 22 Jan 2000 23:39:29 +1300 From: Joe Abley To: Ben Rosengart Cc: Andre Oppermann , sthaug@nethelp.no, louie@TransSys.COM, drosih@rpi.edu, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000122233927.B2555@patho.gen.nz> References: <3888E597.9D80E8EF@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from ben@skunk.org on Fri, Jan 21, 2000 at 06:20:38PM -0500 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 06:20:38PM -0500, Ben Rosengart wrote: > > Anyway, if multi CNAME is no good then do: > > > > cvsup IN A 198.104.92.71 ; cvsup1.freebsd.org > > cvsup IN A 205.149.189.91 ; cvsup2.freebsd.org > > ... and so on > > > > This is legal, is it? > > Not only is it legal, but I believe BIND will return all the A records > to any query, and will rotate them. The problem with this is that any time a cvsup server operator decides to renumber their mirror, they need to inform the soa for freebsd.org (and factor in the freebsd.org TTLs to manage the change). In practice this will not work, and will cause 1/n cvsup attempts to fail after a machine has been renumbered until TTLs expire. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2:56: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id CF59415597 for ; Sat, 22 Jan 2000 02:55:48 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id MAA08044; Sat, 22 Jan 2000 12:50:05 +0200 (EET) (envelope-from ru) Date: Sat, 22 Jan 2000 12:50:05 +0200 From: Ruslan Ermilov To: John Polstra Cc: current@FreeBSD.org Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000122125005.B3104@relay.ucb.crimea.ua> Mail-Followup-To: John Polstra , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from John Polstra on Fri, Jan 21, 2000 at 10:43:39AM -0800 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 10:43:39AM -0800, John Polstra wrote: > This is another in my series of occasional nags to try to get people > to use some of the less heavily loaded CVSup mirrors. In the US > alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. > The newest, cvsup8, is a very high-capacity and well-connected site, > yet hardly anybody is using it. Please give it a try! > What's wrong with DNS-based load-balancing solution? I.e. cvsup[1-8] CNAME cvsup ; for backward compatibility cvsup A x.x.x.x A y.y.y.y ... A z.z.z.z -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 2:57:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 2DE5015554 for ; Sat, 22 Jan 2000 02:57:45 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas5-23-235.dial.proxad.net [213.228.23.235]) by postfix2.free.fr (Postfix) with ESMTP id 01FBC7403E; Sat, 22 Jan 2000 11:57:42 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id NAA06525; Sat, 22 Jan 2000 13:05:53 +0100 (CET) (envelope-from nsouch) Message-ID: <20000122130552.35038@breizh.free.fr> Date: Sat, 22 Jan 2000 13:05:52 +0100 From: Nicolas Souchu To: Doug Rabson Cc: "F. Heinrichmeyer" , "freebsd-current@FreeBSD.ORG" Subject: Re: Parallel Port Zip Drive works when EPP-Mode is choosen in Bios References: <20000122090548.17844@armor.free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Doug Rabson on Sat, Jan 22, 2000 at 10:03:25AM +0000 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 10:03:25AM +0000, Doug Rabson wrote: >> >> Nice. The newbus architecture introduces overhead in I/O and old chipsets >> (or old compatible modes) do not always support it. >> >> Your drive runs really faster too, doesn't it? > >Have you measured the overhead? I think it should be trivial compared to >the effort of using inb/outb to poll a port. No, but each time function calls are introduced in the ppbus framework (initially to isolate ppbus layers and now with newbus) some parallel port stop working. Certainly more a timing issue than a performance issue I think. But some good hardware never failed, some bad hardware fails with either slow (486) or fast processors. > >-- >Doug Rabson Mail: dfr@nlsystems.com >Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 3: 7:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 3789D15622 for ; Sat, 22 Jan 2000 03:07:13 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 58640 invoked by uid 1001); 22 Jan 2000 11:07:11 +0000 (GMT) To: wilko@yedi.iaf.nl Cc: freebsd-current@freebsd.org Subject: Re: panic (softupdates??) on yesterdays -current (alpha machine) From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 22 Jan 2000 11:34:07 +0100" References: <20000122113407.A54350@yedi.iaf.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 22 Jan 2000 12:07:11 +0100 Message-ID: <58638.948539231@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just was presented the following panic by my FreeBSD/alpha Miata box that > was doing a make release: > > initiate_write_inode_block() at initiate_write_inode_block() +0x40 > softdep_disk_io_initiation() at softdep_disk_io_initiation() + 0xac > spec_strategy() at spec_strategy() +0x48 > spec_vnoperate() at spec_vnoperate() +0x2c > ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c > bwrite() at bwrite() + 0x404 > vop_stdbwrite() at vop_stdbwrite() +0x1c > vop_defaultop() at vop_defaultop() + 0x2c > spec_vnoperate() at spec_vnoperate() +0x2c > ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c > vfs_bio_awrite() at vfs_bio_awrite() + 0x484 > flushbufqueues() at flushbufqueues() +0x1e8 > buf_daemon() at buf_daemon() + 0x114 > exception_return() at excpetion_return > > This is a manual transcript, no serial console. This is similar to panics I've had during "make buildworld". I'm getting initiate_write_inodeblock softdep_disk_io_initiation spec_strategy bwrite vop_stdbwrite vop_defaultop vfs_bio_awrite spec_fsync sched_sync fork_trampoline This is with ffs_softdep.c 1.56. Matt Dillon has already received a core dump, and I believe it's on its way to Kirk McKusick for analysis. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 3:37:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 6F4B4155C1; Sat, 22 Jan 2000 03:37:56 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-14.ix.netcom.com [209.109.235.14]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id DAA09287; Sat, 22 Jan 2000 03:37:54 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA93326; Sat, 22 Jan 2000 03:37:47 -0800 (PST) Date: Sat, 22 Jan 2000 03:37:47 -0800 (PST) Message-Id: <200001221137.DAA93326@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: asami@FreeBSD.ORG Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG In-reply-to: (asami@FreeBSD.ORG) Subject: Re: crashes From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) References: <200001120008.QAA89430@silvia.hip.berkeley.edu> <200001120234.SAA66268@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to let you know how it went.... * * From: Matthew Dillon * * Please upgrade your system to the latest ffs_softdep.c, vers 1.47. This * * will fix a number of other problems but may not fix this one. I first upped it to 1.48 (I think) and was seeing hangs all over the place (telnet says "connected" but nothing shows up except empty lines, etc.), but the problems went away when I moved to 1.56. The machines have been running reliably for a few days now. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 3:41:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id C60F414CC4 for ; Sat, 22 Jan 2000 03:41:13 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (toulouse-51-200.dial.proxad.net [212.27.51.200]) by postfix1.free.fr (Postfix) with ESMTP id AB9D0282CC; Sat, 22 Jan 2000 12:35:48 +0100 (MET) Received: by titine.fr.eu.org (Postfix, from userid 1000) id F31C714C40; Sat, 22 Jan 2000 11:48:46 +0100 (CET) To: Scott Burns Cc: "Matt M." , current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current References: <3887ECC9.7A2625F5@boda.virtualave.net> <388915EF.90D99DC6@wpsystems.net> From: Eric Jacoboni Date: 22 Jan 2000 11:48:46 +0100 In-Reply-To: Scott Burns's message of "Fri, 21 Jan 2000 21:29:03 -0500" Message-ID: <87ogaes7ox.fsf@titine.fr.eu.org> Lines: 17 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Bryce Canyon" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Burns writes: > I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld > worked fine, but the installworld was interrupted part of the way > through the install by a signal 12 to sh. I tried doing it from > 3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and > I got the same error every time. I ended up booting to the 3.4 install > disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh > would crash with a signal 12 every time. Download the bin distribution from current, install it, then redo a make world : i've had the same pb, and i have resolved it like that. -- --------------------------------------------------------- Éric Jacoboni « No sport, cigars! » (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 3:51:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 7911615215 for ; Sat, 22 Jan 2000 03:51:15 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id LAA07875; Sat, 22 Jan 2000 11:51:01 GMT (envelope-from joe) Date: Sat, 22 Jan 2000 11:51:01 +0000 From: Josef Karthauser To: Warner Losh Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000122115101.E58872@florence.pavilion.net> References: <200001211911.LAA11701@vashon.polstra.com> <20000121190729.C58872@florence.pavilion.net> <200001211911.LAA11701@vashon.polstra.com> <200001212055.NAA13871@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001212055.NAA13871@harmony.village.org> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 01:55:51PM -0700, Warner Losh wrote: > In message <200001211911.LAA11701@vashon.polstra.com> John Polstra writes: > : > Can you make cvsup accept multiple servers to try in it's configuration > : > file? > : > : I'll add that to the to-do list. > > I have a very crude script that does its own (fixed) round robin of > multiple servers. It tries three times fast (yes, I know that's > likely bad) and then goes to the next one on the list. If all else > fails, it will try the first one on the list in "forever" mode (with > the nice random retries). > > I'll have to see about puitting into good shape and posting it. To tell you the truth I've never had that problem: genius% traceroute cvsup.uk.freebsd.org traceroute to bluecat.pavilion.net (194.242.144.8), 30 hops max, 40 byte packets 1 sunrise-fe0-0.router.pavilion.net (212.74.1.1) 1.076 ms 1.042 ms 1.039 ms 2 hydra-fa3-0v99.router.pavilion.net (212.74.0.226) 1.548 ms 1.376 ms 1.778 ms 3 unicorn-h0.router.pavilion.net (194.242.129.2) 57.441 ms 73.718 ms 8.765 ms 4 bluecat.pavilion.net (194.242.144.8) 22.837 ms 19.159 ms 67.939 ms genius% traceroute cvsup2.uk.freebsd.org traceroute to storm.freebsd.org.uk (194.242.128.198), 30 hops max, 40 byte packets 1 sunrise-fe0-0.router.pavilion.net (212.74.1.1) 1.124 ms 1.040 ms 1.103 ms 2 hydra-fa3-0v99.router.pavilion.net (212.74.0.226) 2.338 ms 1.305 ms 1.535 ms 3 storm.freebsd.org.uk (194.242.128.198) 1.105 ms 1.068 ms 0.980 ms genius% traceroute genius traceroute to genius (127.0.0.1), 30 hops max, 40 byte packets 1 localhost (127.0.0.1) 0.151 ms 0.059 ms 0.050 ms :-) Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 4:22: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id BF5D614C92 for ; Sat, 22 Jan 2000 04:21:53 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id OAA99330; Sat, 22 Jan 2000 14:21:20 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200001221221.OAA99330@zibbi.mikom.csir.co.za> Subject: Re: make release broken In-Reply-To: <20000121204544.E741@yedi.iaf.nl> from Wilko Bulte at "Jan 21, 2000 08:45:44 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sat, 22 Jan 2000 14:21:20 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Stop in /usr/src/release. > > *** Error code 1 > > > > Stop in /usr/src/release. > > *** Error code 1 > > > > Stop in /usr/src/release. > > ------------------------------- > > > > It looks like the handling of HARDWARE.TXT in release/Makefile is broken. > > HARDWARE.TXT was missing. Should be corrected by a commit I've done > 15 minutes ago. Ok it got a little further. Now it dies with: 0 blocks 0 blocks cp: /usr/src/release/texts/RELNOTES.TXT: No such file or directory *** Error code 1 Stop in /usr/src/release. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 5:31:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id D312115621 for ; Sat, 22 Jan 2000 05:31:22 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id XAA03544 for ; Fri, 21 Jan 2000 23:27:26 GMT (envelope-from n_hibma@webweaving.org) Date: Fri, 21 Jan 2000 23:27:26 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: With feature freeze being in place Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG we all should have time to fix up all those little things that needed to be done anyway. Like: - writing manpages (or send a skeleton of to someone who will finish it) - update HARDWARE.TXT - check UPDATING - replace controller with device in all manpages - improving manpages in general - FIXING PRs We should have a large list of these items circulate the next few weeks in order to make 4.x the best release of the best ever. Cheers, Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 7: 4:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gandalf.hk.linkage.net (gandalf.hk.linkage.net [202.76.4.1]) by hub.freebsd.org (Postfix) with ESMTP id 1406414C95 for ; Sat, 22 Jan 2000 07:04:42 -0800 (PST) (envelope-from satyajit@spnetctg.com) Received: from mail.spnetctg.com (qmailr@mail.spnetctg.com [210.184.28.8]) by gandalf.hk.linkage.net (8.9.1/8.8.8) with SMTP id XAA19152 for ; Sat, 22 Jan 2000 23:04:29 +0800 (HKT) Received: (qmail 4387 invoked from network); 22 Jan 2000 15:31:12 -0000 Received: from unknown (HELO spnetctg.com) (210.184.28.224) by mail.spnetctg.com with SMTP; 22 Jan 2000 15:31:12 -0000 Message-ID: <3889B667.C228500A@spnetctg.com> Date: Sat, 22 Jan 2000 13:53:43 +0000 From: Satyajit Das X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 7:36:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alltel.net (mail.alltel.net [166.102.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 2136415546 for ; Sat, 22 Jan 2000 07:36:45 -0800 (PST) (envelope-from matt@boda.virtualave.net) Received: from dns1 ([216.132.71.182]) by mail.alltel.net (8.9.3/ALLTEL Messaging Service) with SMTP id JAA08590 for ; Sat, 22 Jan 2000 09:36:38 -0600 (CST) Message-ID: <001301bf64ef$0cb038a0$b64784d8@dns1> From: "Matt M." To: Subject: cvsup current - problems with -release kernel Date: Sat, 22 Jan 2000 07:40:37 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupd current, and did a make buildworld last night - i didn't do make installworld - now when i boot my system (when it is initializing the network) I get a message that is similar to "cannot allocate llinfo for /kernel" - i tried an older kernel and i got the same message. I am using DHCP, so I thought maybe there was a problem with that, and I ran /stand/sysinstall to setup my system to NOT use DHCP and rebooted. Same message. What could be the problem? make buildworld doesn't actually change any installed files or settings does it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 7:40: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id F113515698 for ; Sat, 22 Jan 2000 07:40:02 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA73362 for ; Sat, 22 Jan 2000 07:39:55 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <3889CF47.C94F1BF0@MexComUSA.net> Date: Sat, 22 Jan 2000 07:39:51 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: This mornings make world stops at alpm.4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This mornings make world ended with ===> share/man/man4 gzip -cn /usr/src/share/man/man4/ahc.4 > ahc.4.gz make: don't know how to make alpm.4. Stop *** Error code 2 Stop in /usr/src/share/man. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code Thanks, ed P.S. from my cvsup log Delete src/share/man/man4/alpm.4 Edit src/share/man/man4/lpbb.4 Add delta 1.7 2000.01.22.10.49.36 nsouch Edit src/share/man/man4/man4.i386/alpm.4 Add delta 1.6 2000.01.22.10.49.41 nsouch Edit src/share/man/man4/ppbus.4 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 7:46:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id 19A8E14C40 for ; Sat, 22 Jan 2000 07:46:12 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 795407E for ; Sat, 22 Jan 2000 10:46:13 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: freebsd-current@freebsd.org Subject: Installing to a differnet root? Date: Sat, 22 Jan 2000 10:44:05 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0001221046080D.00537@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've briefly read various documents, and haven't discovered a way to installworld to a different path than /. In particular, I'd like to install to /remotefs/. I've got tftp, bootp, etc. all setup and ready to go but would like a clean 'world' to modify as opposed to a pre-existing one. Thanks! -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 7:48:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alltel.net (mail.alltel.net [166.102.165.30]) by hub.freebsd.org (Postfix) with ESMTP id DE27214DD8 for ; Sat, 22 Jan 2000 07:48:41 -0800 (PST) (envelope-from matt@boda.virtualave.net) Received: from dns1 ([216.132.71.182]) by mail.alltel.net (8.9.3/ALLTEL Messaging Service) with SMTP id JAA00316 for ; Sat, 22 Jan 2000 09:48:39 -0600 (CST) Message-ID: <003401bf64f0$b9da8de0$b64784d8@dns1> From: "Matt M." To: Subject: cvsup current - problems with -release kernel Date: Sat, 22 Jan 2000 07:52:44 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I forgot to mention that the network is no longer functional with these error messages. > I cvsupd current, and did a make buildworld last night - i didn't do make > installworld - now when i boot my system (when it is initializing the > network) I get a message that is similar to "cannot allocate llinfo for > /kernel" - i tried an older kernel and i got the same message. I am using > DHCP, so I thought maybe there was a problem with that, and I ran > /stand/sysinstall to setup my system to NOT use DHCP and rebooted. Same > message. What could be the problem? make buildworld doesn't actually change > any installed files or settings does it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 8: 5:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id 87BF614CE1 for ; Sat, 22 Jan 2000 08:05:27 -0800 (PST) (envelope-from hoek@FreeBSD.org) Received: from localhost.nowhere (ppp2016.on.bellglobal.com [206.172.235.96]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id LAA05576; Sat, 22 Jan 2000 11:10:15 -0500 (EST) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id LAA62284; Sat, 22 Jan 2000 11:05:18 -0500 (EST) (envelope-from tim) Date: Sat, 22 Jan 2000 11:05:18 -0500 From: Tim Vanderhoek To: Warner Losh Cc: current@FreeBSD.org Subject: Re: Here's what I'm using Message-ID: <20000122110518.A61361@mad> References: <200001220656.XAA18881@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <200001220656.XAA18881@harmony.village.org>; from Warner Losh on Fri, Jan 21, 2000 at 11:56:38PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 11:56:38PM -0700, Warner Losh wrote: > > arbitrary and works for me. I'm sure this could be improved, > especially to make the order random. It really isn't too hard... I wouldn't be surprised if this crosses another solution in email. :) #! /bin/sh if [ -z "$1" ]; then set cvsup7.freebsd.org \ cvsup8.freebsd.org \ cvsup6.freebsd.org \ cvsup4.freebsd.org \ cvsup3.freebsd.org \ cvsup2.freebsd.org \ cvsup1.freebsd.org \ cvsup5.freebsd.org for n in `jot -r $#` do fairings="${fairings} $n $1" shift done hosts=`echo "$fairings" | sort | awk '{print $2}'` else hosts=$1 shift fi echo "Will try hosts $(echo $hosts)" for host in $hosts; do echo "Using host $host" for i in 1 2; do if cvsup -1 -P m -s -g ~/bin/sup/fbsd-supfile -L 2 -h $host $*; then exit; fi done done -- Signature withheld by request of author. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 8:13:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from beholder.ods.org (ppp-047.m2-1.sub.ican.net [142.51.225.47]) by hub.freebsd.org (Postfix) with ESMTP id AE2F114A15 for ; Sat, 22 Jan 2000 08:13:22 -0800 (PST) (envelope-from beholder@beholder.ods.org) Received: from beholder.ods.org (laptop.unios.ca [192.168.0.21]) by beholder.ods.org (8.9.3/8.9.3) with ESMTP id LAA46111; Sat, 22 Jan 2000 11:12:58 -0500 (EST) (envelope-from beholder@beholder.ods.org) Message-ID: <3889D7A9.CAC21D2A@beholder.ods.org> Date: Sat, 22 Jan 2000 11:15:37 -0500 From: Pat Wendorf X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > This is another in my series of occasional nags to try to get people > to use some of the less heavily loaded CVSup mirrors. In the US > alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. > The newest, cvsup8, is a very high-capacity and well-connected site, > yet hardly anybody is using it. Please give it a try! Ok, I tried it and to my surprise the other ones are faster. I'm one of the many who probably didn't give it much thought and just stuck cvsup.freebsd.org in their cvsup config files. Now, I'm running off cvsup6, which gave me no packet loss, but also seems to have a very fast response time. I'm in Canada, and I've noticed that cvsup.ca.freebsd.org, is the absolute worst server I can possibly use. It seems the american ones are much better. Is cvsup.ca just another pointer to cvsup1 in the US? And I also update PAO3 on a regular basis, and that is the slowest one of them all (coming from cvsup.jp, in Japan). Do any of the US mirror's also mirror PAO3? -- ---------------------- Pat Wendorf beholder@unios.dhs.org ICQ: 1503733 --------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 8:21: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id 7B8C214CAB for ; Sat, 22 Jan 2000 08:20:57 -0800 (PST) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id IAA24850; Sat, 22 Jan 2000 08:20:53 -0800 (PST) (envelope-from ab@astralblue.com) Date: Sat, 22 Jan 2000 08:20:53 -0800 (PST) From: "Eugene M. Kim" To: Rod Taylor Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installing to a differnet root? In-Reply-To: <0001221046080D.00537@rbtBSD.intranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following should do it: cd /usr/src make installworld DESTDIR=/remotefs cd /usr/src/etc make distrib-dirs distribution DESTDIR=/remotefs Regards, Eugene On Sat, 22 Jan 2000, Rod Taylor wrote: | I've briefly read various documents, and haven't discovered a way to | installworld to a different path than /. | | In particular, I'd like to install to /remotefs/. | | I've got tftp, bootp, etc. all setup and ready to go but would like a clean | 'world' to modify as opposed to a pre-existing one. | | Thanks! -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 8:22:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C27BE14CC9 for ; Sat, 22 Jan 2000 08:22:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA04893; Sat, 22 Jan 2000 08:21:25 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA80861; Sat, 22 Jan 2000 08:21:21 -0800 (PST) (envelope-from obrien) Date: Sat, 22 Jan 2000 08:21:21 -0800 From: "David O'Brien" To: Maxim Sobolev Cc: current@freebsd.org, "Alexander N. Kabaev" Subject: Re: C++ exceptions doesn't work in shared libraries Message-ID: <20000122082121.B80777@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <387B1603.E353CD09@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <387B1603.E353CD09@altavista.net>; from sobomax@altavista.net on Tue, Jan 11, 2000 at 01:37:39PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:37:39PM +0200, Maxim Sobolev wrote: > It seems than long-standing problem (see PR dated May '97: > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3441) with C++ exceptions in shared Good news, a fix has been imported and merged. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 8:23:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alltel.net (mail.alltel.net [166.102.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 0405714E65 for ; Sat, 22 Jan 2000 08:23:48 -0800 (PST) (envelope-from matt@boda.virtualave.net) Received: from dns1 ([216.132.71.182]) by mail.alltel.net (8.9.3/ALLTEL Messaging Service) with SMTP id KAA07664 for ; Sat, 22 Jan 2000 10:23:46 -0600 (CST) Message-ID: <009901bf64f5$a1083ce0$b64784d8@dns1> From: "Matt M." To: Subject: cvsup current - problems with -release kernel Date: Sat, 22 Jan 2000 08:27:50 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupd current, and did a make buildworld last night - i didn't do make installworld - now when i boot my system (when it is initializing the network) I get a message that is similar to "cannot allocate llinfo for /kernel" - i tried an older kernel and i got the same message. I am using DHCP, so I thought maybe there was a problem with that, and I ran /stand/sysinstall to setup my system to NOT use DHCP and rebooted. Same message. What could be the problem? make buildworld doesn't actually change any installed files or settings does it? My network doesnt work in any configuration at this point. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9: 5:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id AD98614EF2 for ; Sat, 22 Jan 2000 09:05:22 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA00888; Sat, 22 Jan 2000 09:05:19 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA16332; Sat, 22 Jan 2000 09:05:19 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 22 Jan 2000 09:05:19 -0800 (PST) Message-Id: <200001221705.JAA16332@vashon.polstra.com> To: jasone@canonware.com Subject: Re: even more breakage in current In-Reply-To: <20000121162540.E27689@sturm.canonware.com> References: <20000121101157.A18956@dub.net> <20000121142251.D27689@sturm.canonware.com> <20000121154727.C43755@dragon.nuxi.com> <20000121162540.E27689@sturm.canonware.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000121162540.E27689@sturm.canonware.com>, Jason Evans wrote: > > I often do a 'make includes' to be able to iteratively test changes. Once > I'm happy that the changes are sound, there is no way to assure that the > changes didn't cause a bootstrapping problem like this one. It's feasible to perform valid tests, but it requires some care and planning. Whenever you're changing a system header file, write it down. When you are done making changes, re-install the virgin unadulterated copies of those header files. In general, do your best to restore your system to a pristine state. Then test with make world. Yes, this is a pain. But it's a pain for one person instead of for several hundred. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9: 8:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 18F8514E0E for ; Sat, 22 Jan 2000 09:08:41 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id KAA09255; Sat, 22 Jan 2000 10:08:34 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001221708.KAA09255@freeway.dcfinc.com> Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: from John Polstra at "Jan 21, 0 10:43:39 am" To: jdp@polstra.com (John Polstra) Date: Sat, 22 Jan 2000 10:08:34 -0700 (MST) Cc: current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, John Polstra wrote: > In fact, the higher-numbered mirrors often have faster hardware simply > because they're newer. Also, in particular, there's nothing special > about cvsup.FreeBSD.org -- it's simply an alias for cvsup1 and it gets > its updates the same way at the same intervals from the same master > server as all the other mirrors. Perhaps we should be so bold as to renumber the servers in the DNS such that the preferred servers have the lower numbers? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:15:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 2B26314C2D; Sat, 22 Jan 2000 09:15:39 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 18-108.008.popsite.net ([209.69.196.108] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12C48N-0007ar-00; Sat, 22 Jan 2000 10:15:36 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 72B961976; Sat, 22 Jan 2000 12:15:28 -0500 (EST) Date: Sat, 22 Jan 2000 12:15:28 -0500 From: Will Andrews To: David O'Brien Cc: Maxim Sobolev , current@FreeBSD.ORG, "Alexander N. Kabaev" Subject: Re: C++ exceptions doesn't work in shared libraries Message-ID: <20000122121528.B59732@shadow.blackdawn.com> References: <387B1603.E353CD09@altavista.net> <20000122082121.B80777@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000122082121.B80777@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sat, Jan 22, 2000 at 08:21:21AM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 08:21:21AM -0800, David O'Brien wrote: > Good news, a fix has been imported and merged. If I read the PR correctly, it states that ports like Mico were broken on account of this? And you just today fixed this? The reason I'm asking is because Mico seems to break when I compile it with g++295 and a g++295'd Qt library. See http://www.psn.net/~andrews/qtkde/mico.html. Is this problem the result of this "C++ exceptions don't work in shared libraries" thing? From my novice point of view, it looks to me more like the Mico people just forgot to put an include in the file that breaks. Can you tell me if any of the ports on the page labelled "Weird C++ problem" are having this particular problem? :-) Thanks, -- Will Andrews 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:31:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 9EB4C14F7B; Sat, 22 Jan 2000 09:31:14 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 18-108.008.popsite.net ([209.69.196.108] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 12C4NT-0000iy-00; Sat, 22 Jan 2000 10:31:13 -0700 Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 98EBC1B1C; Sat, 22 Jan 2000 12:31:09 -0500 (EST) Date: Sat, 22 Jan 2000 12:31:09 -0500 From: Will Andrews To: Shigeyuki Fukushima Cc: current@FreeBSD.org Subject: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000122123109.E59732@shadow.blackdawn.com> References: <86ya9j61fy.wl@localhost.local.idaemons.org> <20000121165416.NMLY2135.t-mta3.odn.ne.jp@athena.shige.org> <86vh4n5kae.wl@localhost.local.idaemons.org> <20000122154518.HPCY19862.t-mta1.odn.ne.jp@athena.shige.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000122154518.HPCY19862.t-mta1.odn.ne.jp@athena.shige.org>; from owner-freebsd-ports@FreeBSD.ORG on Sun, Jan 23, 2000 at 12:44:46AM +0900 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 12:44:46AM +0900, owner-freebsd-ports@FreeBSD.ORG wrote: > Truely, I wish to import bzip2 to -current src tree. :) > Is there a problem about some restriction for distributing bzip2? > # I'm sorry I don't know about that. <2 5003-0> (00-01-22 12:27:37) [will@shadow /usr/ports/archivers/bzip2]% cat pkg/DESCR This is bzip2, a advanced block-sorting file compressor. It is believed to be free from any patents. WWW: http://sourceware.cygnus.com/bzip2/ Nope - looks like it could be a candidate for importing to the source tree. However, I'm not sure everyone on current@ is going to agree, since we already have something for compression (gzip) that is pretty standard around the world. -- Will Andrews 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:33:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 90853157A0; Sat, 22 Jan 2000 09:33:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA72550; Sat, 22 Jan 2000 09:33:27 -0800 (PST) (envelope-from dillon) Date: Sat, 22 Jan 2000 09:33:27 -0800 (PST) From: Matthew Dillon Message-Id: <200001221733.JAA72550@apollo.backplane.com> To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: current@FreeBSD.ORG Subject: Re: crashes References: <200001120008.QAA89430@silvia.hip.berkeley.edu> <200001120234.SAA66268@apollo.backplane.com> <200001221137.DAA93326@silvia.hip.berkeley.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Just to let you know how it went.... : : * * From: Matthew Dillon : : * * Please upgrade your system to the latest ffs_softdep.c, vers 1.47. This : * * will fix a number of other problems but may not fix this one. : :I first upped it to 1.48 (I think) and was seeing hangs all over the :place (telnet says "connected" but nothing shows up except empty :lines, etc.), but the problems went away when I moved to 1.56. The :machines have been running reliably for a few days now. : :Satoshi Ah, that's good. I still have one person reporting a panic with 1.56 (which I have a core for). w/1.56 my own buildworld tests succeed and except for this one person everyone else is reporting their softupdates problems solved. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:42:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id B706514A11 for ; Sat, 22 Jan 2000 09:42:52 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 22007 invoked from network); 22 Jan 2000 17:42:50 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 22 Jan 2000 17:42:50 -0000 Message-ID: <3889EBFA.179F3866@cvzoom.net> Date: Sat, 22 Jan 2000 12:42:18 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) References: <86ya9j61fy.wl@localhost.local.idaemons.org> <20000121165416.NMLY2135.t-mta3.odn.ne.jp@athena.shige.org> <86vh4n5kae.wl@localhost.local.idaemons.org> <20000122154518.HPCY19862.t-mta1.odn.ne.jp@athena.shige.org> <20000122123109.E59732@shadow.blackdawn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will Andrews wrote: > Nope - looks like it could be a candidate for importing to the source > tree. However, I'm not sure everyone on current@ is going to agree, > since we already have something for compression (gzip) that is pretty > standard around the world. Ever notice how on some occasions bzip2 format is actually less effective than gzip? It depends on what you're compressing. For some things, gzip is better, and for yet other stuff, bzip2 gives much better compression. I think it would be neat to incorporate both gzip and and bzip2 into one executable, and have the compression program determine which algorithm is best. And then, when uncompressing, the program would autodetect which method (bzip2 or gzip) was used to compress the file. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:43:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C7291572C for ; Sat, 22 Jan 2000 09:43:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA72684; Sat, 22 Jan 2000 09:43:14 -0800 (PST) (envelope-from dillon) Date: Sat, 22 Jan 2000 09:43:14 -0800 (PST) From: Matthew Dillon Message-Id: <200001221743.JAA72684@apollo.backplane.com> To: Wilko Bulte Cc: "FreeBSD_current, mailing list" Subject: Re: panic (softupdates??) on yesterdays -current (alpha machine) References: <20000122113407.A54350@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Just was presented the following panic by my FreeBSD/alpha Miata box that :was doing a make release: : :initiate_write_inode_block() at initiate_write_inode_block() +0x40 :softdep_disk_io_initiation() at softdep_disk_io_initiation() + 0xac :spec_strategy() at spec_strategy() +0x48 :spec_vnoperate() at spec_vnoperate() +0x2c :ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c :bwrite() at bwrite() + 0x404 :vop_stdbwrite() at vop_stdbwrite() +0x1c :vop_defaultop() at vop_defaultop() + 0x2c :spec_vnoperate() at spec_vnoperate() +0x2c :ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c :vfs_bio_awrite() at vfs_bio_awrite() + 0x484 :flushbufqueues() at flushbufqueues() +0x1e8 :buf_daemon() at buf_daemon() + 0x114 :exception_return() at excpetion_return : :This is a manual transcript, no serial console. : :Softupdates only enabled on /usr, /usr/obj. Make release was :putting it generated stuff on /usr : :No dump unfortunately, I'll see if I can catch it again : :-- :Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project : WWW : http://www.tcja.nl http://www.freebsd.org Is this with the latest kernel? /usr/src/sys/contrib/softupdates/ffs_softdep.c rev 1.56 or later? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:49:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 067A914DB3; Sat, 22 Jan 2000 09:49:15 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA23335; Sat, 22 Jan 2000 12:42:59 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sat, 22 Jan 2000 12:42:55 -0500 (EST) From: Chuck Robey To: Will Andrews Cc: Shigeyuki Fukushima , current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: <20000122123109.E59732@shadow.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, Will Andrews wrote: > On Sun, Jan 23, 2000 at 12:44:46AM +0900, owner-freebsd-ports@FreeBSD.ORG wrote: > > Truely, I wish to import bzip2 to -current src tree. :) > > Is there a problem about some restriction for distributing bzip2? > > # I'm sorry I don't know about that. > > <2 5003-0> (00-01-22 12:27:37) [will@shadow /usr/ports/archivers/bzip2]% > cat pkg/DESCR > This is bzip2, a advanced block-sorting file compressor. It is > believed to be free from any patents. > > WWW: http://sourceware.cygnus.com/bzip2/ > > Nope - looks like it could be a candidate for importing to the source > tree. However, I'm not sure everyone on current@ is going to agree, > since we already have something for compression (gzip) that is pretty > standard around the world. You guys better understand, having software be legally *able* to be in the source tree is a *very* far way from needing it in the source tree. A very strong case would have to be built that we cannot really do without it. Seeing as gzip fills the requirement with undeniably maximum compatibility, the mere fact that bzip2 compresses smaller doesn't sound like a good reason in of and itself. We would not be able to get rid of gzip anyhow (for compatibility reasons) so we'd end up having to have two tools where one does the job well enough now. A case would have to be built that bzip2 does something critical that cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs is a fine port too, but it'll never get into the base system. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 9:59: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id 2D5A414E65 for ; Sat, 22 Jan 2000 09:59:03 -0800 (PST) (envelope-from hoek@FreeBSD.org) Received: from localhost.nowhere ([206.172.226.206]) by tomts3-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with ESMTP id <20000122172207.ZCXT627.tomts3-srv.bellnexxia.net@localhost.nowhere>; Sat, 22 Jan 2000 12:22:07 -0500 Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id MAA63141; Sat, 22 Jan 2000 12:21:20 -0500 (EST) (envelope-from tim) Date: Sat, 22 Jan 2000 12:21:20 -0500 From: Tim Vanderhoek To: Warner Losh Cc: current@FreeBSD.org Subject: Re: Here's what I'm using Message-ID: <20000122122120.A62964@mad> References: <200001220656.XAA18881@harmony.village.org> <20000122110518.A61361@mad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <20000122110518.A61361@mad>; from Tim Vanderhoek on Sat, Jan 22, 2000 at 11:05:18AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 11:05:18AM -0500, Tim Vanderhoek wrote: > On Fri, Jan 21, 2000 at 11:56:38PM -0700, Warner Losh wrote: > > > > arbitrary and works for me. I'm sure this could be improved, > > especially to make the order random. > > It really isn't too hard... I wouldn't be surprised if this > crosses another solution in email. :) It occurred to me that it would be a good and useful idea to weight the randomness such that certain favoured hosts have a greater chance of being the first host tried. This makes the script a little more useful (as opposed to just being a toy). Just change the multiplicative factor to increase the weighting factor. Order hosts in the set line from most to least favoured. As written, this gives cvsup7 and cvsup8 the greatest chance of being the first hosts tried. For even more fun, make this automatically keep a running track record of download speed and have it adjust the host weighting accordingly. #! /bin/sh if [ -z "$1" ] then set cvsup7.freebsd.org \ cvsup8.freebsd.org \ cvsup6.freebsd.org \ cvsup4.freebsd.org \ cvsup3.freebsd.org \ cvsup2.freebsd.org \ cvsup1.freebsd.org \ cvsup5.freebsd.org for n in `jot -r $#` do fairings="${fairings} $(($n - $# * 2)) $1" shift done hosts=`echo "$fairings" | sort -n | awk '{print $2}'` else hosts=$1 shift fi echo "Will try hosts $(echo $hosts)" for host in $hosts; do echo "Using host $host" for i in 1 2; do if cvsup -1 -P m -s -g ~/bin/sup/fbsd-supfile -L 2 -h $host $*; then exit; fi done done -- Signature withheld by request of author. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 10:11:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.jet.es (smtp.jet.es [194.179.100.25]) by hub.freebsd.org (Postfix) with ESMTP id 5887014D85 for ; Sat, 22 Jan 2000 10:11:46 -0800 (PST) (envelope-from joanra@jet.es) Received: from daemon (infou640.jet.es [195.55.162.128]) by smtp.jet.es (8.9.3/8.9.1) with SMTP id TAA22006 for ; Sat, 22 Jan 2000 19:11:39 +0100 (MET) X-Envelope-To: Message-ID: <000b01bf6505$272d8640$0164a8c0@daemon> From: "joanra" To: Subject: error in share/man/man4 Date: Sat, 22 Jan 2000 19:18:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ==> share/man/man4 gzip -cn /usr/src/share/man/man4/ahc-4 > ahc.4.gz make: don't know how to make alpm.4. Stop stop in /usr/src/share/man *** Error code 1 Stop in /usr/src/share *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src *** Errpr code 1 Stop in /usr/src any idea? thx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 10:52:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2C05F14C4F for ; Sat, 22 Jan 2000 10:52:04 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA28912; Sat, 22 Jan 2000 19:45:53 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA59502; Sat, 22 Jan 2000 19:43:27 +0100 (CET) (envelope-from wilko) Date: Sat, 22 Jan 2000 19:43:26 +0100 From: Wilko Bulte To: Matthew Dillon Cc: "FreeBSD_current, mailing list" Subject: Re: panic (softupdates??) on yesterdays -current (alpha machine) Message-ID: <20000122194326.B59196@yedi.iaf.nl> References: <20000122113407.A54350@yedi.iaf.nl> <200001221743.JAA72684@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001221743.JAA72684@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Jan 22, 2000 at 09:43:14AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 09:43:14AM -0800, Matthew Dillon wrote: > > :Just was presented the following panic by my FreeBSD/alpha Miata box that > :was doing a make release: > : > :initiate_write_inode_block() at initiate_write_inode_block() +0x40 > :softdep_disk_io_initiation() at softdep_disk_io_initiation() + 0xac > :spec_strategy() at spec_strategy() +0x48 > :spec_vnoperate() at spec_vnoperate() +0x2c > :ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c > :bwrite() at bwrite() + 0x404 > :vop_stdbwrite() at vop_stdbwrite() +0x1c > :vop_defaultop() at vop_defaultop() + 0x2c > :spec_vnoperate() at spec_vnoperate() +0x2c > :ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c > :vfs_bio_awrite() at vfs_bio_awrite() + 0x484 > :flushbufqueues() at flushbufqueues() +0x1e8 > :buf_daemon() at buf_daemon() + 0x114 > :exception_return() at excpetion_return > : > :This is a manual transcript, no serial console. > : > :Softupdates only enabled on /usr, /usr/obj. Make release was > :putting it generated stuff on /usr > : > :No dump unfortunately, I'll see if I can catch it again > : > :-- > :Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > : WWW : http://www.tcja.nl http://www.freebsd.org > > Is this with the latest kernel? > /usr/src/sys/contrib/softupdates/ffs_softdep.c rev 1.56 or later? I can't tell for sure as I lost part of /usr in crash. I just resurrected the machine, and it now definitely has a 1.56 ffs_softdep.c kernel. I started a new make release to see what happens. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11: 3:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 31A0014E19 for ; Sat, 22 Jan 2000 11:03:14 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id UAA23341; Sat, 22 Jan 2000 20:03:11 +0100 (CET) (envelope-from olli) Date: Sat, 22 Jan 2000 20:03:11 +0100 (CET) Message-Id: <200001221903.UAA23341@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: This mornings make world stops at alpm.4 X-Newsgroups: list.freebsd-current In-Reply-To: <86cj2r$1tod$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote in list.freebsd-current: > ===> share/man/man4 > gzip -cn /usr/src/share/man/man4/ahc.4 > ahc.4.gz > make: don't know how to make alpm.4. Stop > *** Error code 2 > [...] > Delete src/share/man/man4/alpm.4 The committer who deleted (moved) alpm.4 forgot to update the Makefile. This fixes it: --- src/share/man/man4/Makefile.orig Mon Jan 17 16:13:00 2000 +++ src/share/man/man4/Makefile Sat Jan 22 20:00:38 2000 @@ -1,7 +1,7 @@ # @(#)Makefile 8.1 (Berkeley) 6/18/93 # $FreeBSD: src/share/man/man4/Makefile,v 1.74 2000/01/17 15:13:00 asmodai Exp $ -MAN4= ahc.4 alpm.4 amd.4 an.4 atkbd.4 atkbdc.4 aue.4 blackhole.4 bpf.4 \ +MAN4= ahc.4 amd.4 an.4 atkbd.4 atkbdc.4 aue.4 blackhole.4 bpf.4 \ bridge.4 ccd.4 cd.4 ch.4 csa.4 cue.4 da.4 dc.4 ddb.4 de.4 \ divert.4 dummynet.4 faith.4 fd.4 fdc.4 fpa.4 fxp.4 \ gif.4 gusc.4 \ Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:12: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from smarkacz.agsmedia.pl (smarkacz.agsmedia.pl [195.205.87.210]) by hub.freebsd.org (Postfix) with ESMTP id 723F014C16 for ; Sat, 22 Jan 2000 11:09:36 -0800 (PST) (envelope-from jps@smarkacz.agsmedia.pl) Received: (from jps@localhost) by smarkacz.agsmedia.pl (8.9.3/8.9.3) id UAA14792; Sat, 22 Jan 2000 20:09:02 +0100 (CET) (envelope-from jps) To: Scott Burns Cc: "Matt M." , current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current References: <3887ECC9.7A2625F5@boda.virtualave.net> <388915EF.90D99DC6@wpsystems.net> X-Editor: Formerly /usr/bin/vi From: smarkacz@anathema.eu.org (smarkacz) In-Reply-To: Scott Burns's message of "Fri, 21 Jan 2000 21:29:03 -0500" Date: 22 Jan 2000 20:09:01 +0100 Message-ID: <86g0vply9e.fsf@smarkacz.agsmedia.pl> Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Burns wrote: > I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld > worked fine, but the installworld was interrupted part of the way > through the install by a signal 12 to sh. I tried doing it from > 3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and > I got the same error every time. I ended up booting to the 3.4 install > disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh > would crash with a signal 12 every time. Build 4.0-CURRENT kernel, boot it, THEN do `make installworld'. -- smarkacz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:27:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 5F68814DF0 for ; Sat, 22 Jan 2000 11:27:32 -0800 (PST) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id NAA14854; Sat, 22 Jan 2000 13:27:31 -0600 (CST) Message-Id: <200001221927.NAA14854@chiba.3jane.net> To: Wes Peters Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: <388914E4.B508D919@softweyr.com> References: <200001212346.PAA22521@rah.star-gate.com> <388914E4.B508D919@softweyr.com> Comments: In-reply-to Wes Peters message dated "Fri, 21 Jan 2000 19:24:36 -0700." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14851.948569250.1@chiba.3jane.net> Date: Sat, 22 Jan 2000 13:27:31 -0600 From: "Damon M. Conway" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: >Amancio Hasty wrote: >> >> > > My only point is that the first response to a problem isn't to necessarily >> > > pull out emacs and start hacking away on code. >> > >> > Yea, it is easier to do in a regular zone file then to implement the >> > network measurement logic into cvsup. >> >> Yes, it is a rather cool idea to rotate on the cvs servers without >> respect to latency, work load or rate of service response from >> the server. > >Thank you. I was beginning to wonder if I am the only one here who thinks >blind round-robin DNS is a bad hack. nope...i was keeping my mouth shut. there are several parts to "load balancing", and that isn't necessarily what we are trying to accomplish here. what is being discussed is a method for determining the best performing cvsup server for a given client. to do this you must check for the following things: 1. network performance from the client to a server - what is our latency? - what is our packet loss? - hop counts are largely irrelevant - icmp could be used to implement this as a start, but due to isps rate limiting icmp at their routers it is not totally reliable. ideally, you will have a tcp layer tansaction that can determine latency and packet loss. (NOTE: this has nothing to do with "balancing" network paths as was mentioned earlier. BGP handles that. your path to a given server from a given client will always be the same unless BGP decides otherwise.) 2. ability of a server to hand out data in a timely manner - what is the server's cpu load? - what is the server's memory capacity? - how many other clients is this server serving? - how quickly does it deliver a test load of data? this is important because while you may be able to reach this server quickly, it may not be able to hand out data in a timely manner. i would recommend writing a verification routine into the cvsup server and client that finds this info. it should look someting like this: client <------> server What is my network performance? Is it within tolerance? client -------> server What is your ability to serve data to me? client <------- server Sure, I can send you data at X tolerance level. client <------> server Test pattern... basically, a client can go through a list until it reaches a server within it's tolerance. if it doesn't find a server within tolerance, then it will take the one that is closest to tolerance levels. part one is pretty trivial to implement using icmp. part 2 is more interesting. unfortunatly, i'm not much of a coder and i wouldn't know where to start or i'd do it myself. word of advice tho, don't use the ping utility to do the icmp measurements. due to the interactive nature of it, it has a lot of extraneous junk that isn't relevant, and can skew data. damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:28:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alltel.net (mail.alltel.net [166.102.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 4E95514BC4 for ; Sat, 22 Jan 2000 11:28:13 -0800 (PST) (envelope-from matt@boda.virtualave.net) Received: from dns1 ([216.132.71.182]) by mail.alltel.net (8.9.3/ALLTEL Messaging Service) with SMTP id NAA27128; Sat, 22 Jan 2000 13:26:24 -0600 (CST) Message-ID: <008001bf650f$588b4420$b64784d8@dns1> From: "Matt M." To: "Scott Burns" , "smarkacz" Cc: References: <3887ECC9.7A2625F5@boda.virtualave.net> <388915EF.90D99DC6@wpsystems.net> <86g0vply9e.fsf@smarkacz.agsmedia.pl> Subject: Re: cvsup 3.4-release to -current Date: Sat, 22 Jan 2000 11:31:54 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would, but i keep getting a sig11 - i spent literally from 6:30am to 9:00pm yesterday trying to get this thing to compile. ----- Original Message ----- From: smarkacz To: Scott Burns Cc: Matt M. ; Sent: Saturday, January 22, 2000 11:09 AM Subject: Re: cvsup 3.4-release to -current > Scott Burns wrote: > > I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld > > worked fine, but the installworld was interrupted part of the way > > through the install by a signal 12 to sh. I tried doing it from > > 3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and > > I got the same error every time. I ended up booting to the 3.4 install > > disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh > > would crash with a signal 12 every time. > > Build 4.0-CURRENT kernel, boot it, THEN do `make installworld'. > -- > smarkacz > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:34:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id A65A414DEB for ; Sat, 22 Jan 2000 11:34:42 -0800 (PST) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id NAA14918; Sat, 22 Jan 2000 13:34:28 -0600 (CST) Message-Id: <200001221934.NAA14918@chiba.3jane.net> To: Robin Melville Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: References: Comments: In-reply-to Robin Melville message dated "Sat, 22 Jan 2000 10:02:38 +0000." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14915.948569668.1@chiba.3jane.net> Date: Sat, 22 Jan 2000 13:34:28 -0600 From: "Damon M. Conway" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robin Melville wrote: >At 10:43 am -0800 21/1/00, John Polstra wrote: >>[...] we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. >>The newest, cvsup8, is a very high-capacity and well-connected site, >>yet hardly anybody is using it. Please give it a try! > >Hi > >Might it be worth load sharing these via duplicate dns entries for >cvsup.freebsd.org, so that callers get one at random? due to dns caching and the totaly arbitrary nature of this method, it almost never does what you expect it to. damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:35:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alltel.net (mail.alltel.net [166.102.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 9D26314BC2 for ; Sat, 22 Jan 2000 11:35:53 -0800 (PST) (envelope-from matt@boda.virtualave.net) Received: from dns1 ([216.132.71.182]) by mail.alltel.net (8.9.3/ALLTEL Messaging Service) with SMTP id NAA12203; Sat, 22 Jan 2000 13:34:56 -0600 (CST) Message-ID: <009201bf6510$894d7460$b64784d8@dns1> From: "Matt M." To: "Matt M." , "Scott Burns" , "smarkacz" Cc: References: <3887ECC9.7A2625F5@boda.virtualave.net> <388915EF.90D99DC6@wpsystems.net> <86g0vply9e.fsf@smarkacz.agsmedia.pl> <008001bf650f$588b4420$b64784d8@dns1> Subject: Re: cvsup 3.4-release to -current Date: Sat, 22 Jan 2000 11:40:25 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oh sory. i replied to the wrong message. ----- Original Message ----- From: Matt M. To: Scott Burns ; smarkacz Cc: Sent: Saturday, January 22, 2000 11:31 AM Subject: Re: cvsup 3.4-release to -current > I would, but i keep getting a sig11 - i spent literally from 6:30am to > 9:00pm yesterday trying to get this thing to compile. > ----- Original Message ----- > From: smarkacz > To: Scott Burns > Cc: Matt M. ; > Sent: Saturday, January 22, 2000 11:09 AM > Subject: Re: cvsup 3.4-release to -current > > > > Scott Burns wrote: > > > I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld > > > worked fine, but the installworld was interrupted part of the way > > > through the install by a signal 12 to sh. I tried doing it from > > > 3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and > > > I got the same error every time. I ended up booting to the 3.4 install > > > disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh > > > would crash with a signal 12 every time. > > > > Build 4.0-CURRENT kernel, boot it, THEN do `make installworld'. > > -- > > smarkacz > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:37:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 81160156BC for ; Sat, 22 Jan 2000 11:37:21 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA31002; Sat, 22 Jan 2000 20:34:09 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA60196; Sat, 22 Jan 2000 20:37:23 +0100 (CET) (envelope-from wilko) Date: Sat, 22 Jan 2000 20:37:23 +0100 From: Wilko Bulte To: Matthew Dillon Cc: "FreeBSD_current, mailing list" Subject: Re: panic (softupdates??) on yesterdays -current (alpha machine) Message-ID: <20000122203723.A60139@yedi.iaf.nl> References: <20000122113407.A54350@yedi.iaf.nl> <200001221743.JAA72684@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001221743.JAA72684@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Jan 22, 2000 at 09:43:14AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 09:43:14AM -0800, Matthew Dillon wrote: > > :Softupdates only enabled on /usr, /usr/obj. Make release was > :putting it generated stuff on /usr > : > :No dump unfortunately, I'll see if I can catch it again > : > :-- > :Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > : WWW : http://www.tcja.nl http://www.freebsd.org > > Is this with the latest kernel? > /usr/src/sys/contrib/softupdates/ffs_softdep.c rev 1.56 or later? Continuing on a previous email on this subject: I now have a solid lockup of the alpha box. No keyboard, no kernel debugger either :( , no ping I had no other option than to press the halt switch. This is definitely rev 1.56 in the kernel. I am going to disable softupdates on all filesystems to see what happens next. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 11:37:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1E012152A1 for ; Sat, 22 Jan 2000 11:37:29 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA31001; Sat, 22 Jan 2000 20:34:08 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA59902; Sat, 22 Jan 2000 20:09:22 +0100 (CET) (envelope-from wilko) Date: Sat, 22 Jan 2000 20:09:22 +0100 From: Wilko Bulte To: sthaug@nethelp.no Cc: freebsd-current@FreeBSD.org Subject: Re: panic (softupdates??) on yesterdays -current (alpha machine) Message-ID: <20000122200922.F59196@yedi.iaf.nl> References: <20000122113407.A54350@yedi.iaf.nl> <58638.948539231@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <58638.948539231@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Jan 22, 2000 at 12:07:11PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 12:07:11PM +0100, sthaug@nethelp.no wrote: > > Just was presented the following panic by my FreeBSD/alpha Miata box that > > was doing a make release: > > > > initiate_write_inode_block() at initiate_write_inode_block() +0x40 > > softdep_disk_io_initiation() at softdep_disk_io_initiation() + 0xac > > spec_strategy() at spec_strategy() +0x48 > > spec_vnoperate() at spec_vnoperate() +0x2c > > ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c > > bwrite() at bwrite() + 0x404 > > vop_stdbwrite() at vop_stdbwrite() +0x1c > > vop_defaultop() at vop_defaultop() + 0x2c > > spec_vnoperate() at spec_vnoperate() +0x2c > > ufs_vnoperatespec() at ufs_vnoperatespec() + 0x2c > > vfs_bio_awrite() at vfs_bio_awrite() + 0x484 > > flushbufqueues() at flushbufqueues() +0x1e8 > > buf_daemon() at buf_daemon() + 0x114 > > exception_return() at excpetion_return > > > > This is a manual transcript, no serial console. > > This is similar to panics I've had during "make buildworld". I'm getting > > initiate_write_inodeblock > softdep_disk_io_initiation > spec_strategy > bwrite > vop_stdbwrite > vop_defaultop > vfs_bio_awrite > spec_fsync > sched_sync > fork_trampoline > > This is with ffs_softdep.c 1.56. Matt Dillon has already received a core > dump, and I believe it's on its way to Kirk McKusick for analysis. Thanks for the info. I just got my Alpha running again, and I am now 100% sure it has ffs_softdep.c 1.56 Are dumps from an Alpha of any use to Kirk BTW? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 12: 2:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 487CA14C2D for ; Sat, 22 Jan 2000 12:02:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.89]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6090; Sat, 22 Jan 2000 21:02:12 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA20273; Sat, 22 Jan 2000 21:01:36 +0100 (CET) (envelope-from asmodai) Date: Sat, 22 Jan 2000 21:01:36 +0100 From: Jeroen Ruigrok/Asmodai To: Nick Hibma Cc: FreeBSD CURRENT Mailing List Subject: Re: With feature freeze being in place Message-ID: <20000122210136.B18600@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from n_hibma@webweaving.org on Fri, Jan 21, 2000 at 11:27:26PM +0000 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000122 15:22], Nick Hibma (n_hibma@webweaving.org) wrote: > > - writing manpages (or send a skeleton of to someone who will > finish it) Damn right! =) > - update HARDWARE.TXT > - check UPDATING > - replace controller with device in all manpages I think I solved most, if not all, manpages by now, also changed most disk statements to device. What needs to be done is making sure our userland tools stop depending on /dev/r* device nodes, since they aren't needed anymore. > - improving manpages in general Always a good option. > - FIXING PRs Always a good option. Its saddening to see it alwyas being the same people taking care of this. Even if you don't have freebsd.org access you can easily check what the originator tried on your own system and submit a follow-up saying your system (uname -a) has the same problem or not. I am busy pulling newbus manpages out of my, erhm, head. =) But I also note a lack of ata/ad manpages. I offered sos that I'd be doing them or mdoc if someone wrote the bare text. But if someone takes this task from my shoulders, I'd be happy. Also, are GENERIC and LINT in sync? Are LINT and GENERIC in sync with the manpages and vice versa? Are there tools/manpages which need to be removed but were forgotten? Check the ports tree, there's tidy, libtool, leafnode+, diablo and more ports which need updating. Some ARE NOT even the Y2k ready ports yet!!! Compile world with a memleak package and check for memleaks. Help the audit project. Make sure cross compilation works. Verify the sysinstall. Alpha support for it greatly improved. We even have booting from CD if dfr's and o`brien's stuff works! wchar support, something we NEED if we want to use OpenJade someday. Heck, it's part of the SUSv2 and C specs. Test IPv6 support! You've all been asking for it, test it. Given stream.c recent affairs, check boundschecking in code. See how we can maintain our stack and other relevant subsystems as part of the best in the world. I am also working on an up-to-date tasklist which will allow everyone to look for tasks which measure up to his or her ability and be more active on the FreeBSD project. I can't believe that Linux with its ``rabid'' users and less stable source manages to have more enthusiatic supporters in terms of fixes, additions, documentation and all that. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 12:26:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 628DB14E6B for ; Sat, 22 Jan 2000 12:26:24 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 14086 invoked from network); 22 Jan 2000 20:26:21 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 22 Jan 2000 20:26:21 -0000 Message-ID: <388A1251.D7D0814D@cvzoom.net> Date: Sat, 22 Jan 2000 15:25:53 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Replacement for sys/scsiio.h Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So which include file do I use in its place? Is it one of /usr/src/sys/cam/scsi/scsi_*.h? AFAIK, this file isn't in -current any longer. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 13:52: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id CDA03150AF for ; Sat, 22 Jan 2000 13:51:55 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA02982; Sat, 22 Jan 2000 22:47:19 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA61024; Sat, 22 Jan 2000 21:28:51 +0100 (CET) (envelope-from wilko) Date: Sat, 22 Jan 2000 21:28:51 +0100 From: Wilko Bulte To: Jeroen Ruigrok/Asmodai Cc: Nick Hibma , FreeBSD CURRENT Mailing List Subject: Re: With feature freeze being in place Message-ID: <20000122212851.A60961@yedi.iaf.nl> References: <20000122210136.B18600@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000122210136.B18600@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sat, Jan 22, 2000 at 09:01:36PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 09:01:36PM +0100, Jeroen Ruigrok/Asmodai wrote: > -On [20000122 15:22], Nick Hibma (n_hibma@webweaving.org) wrote: > > - update HARDWARE.TXT Urgh... > doing them or mdoc if someone wrote the bare text. But if someone takes > this task from my shoulders, I'd be happy. > > Also, are GENERIC and LINT in sync? Do we want a LINT for alpha too? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 13:53:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 68D5D14DAB for ; Sat, 22 Jan 2000 13:53:35 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA17057; Sat, 22 Jan 2000 13:53:17 -0800 Date: Sat, 22 Jan 2000 13:53:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Jeroen Ruigrok/Asmodai , Nick Hibma , FreeBSD CURRENT Mailing List Subject: Re: With feature freeze being in place In-Reply-To: <20000122212851.A60961@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Jan 22, 2000 at 09:01:36PM +0100, Jeroen Ruigrok/Asmodai wrote: > > -On [20000122 15:22], Nick Hibma (n_hibma@webweaving.org) wrote: > > > > - update HARDWARE.TXT > > Urgh... > > > doing them or mdoc if someone wrote the bare text. But if someone takes > > this task from my shoulders, I'd be happy. > > > > Also, are GENERIC and LINT in sync? > > Do we want a LINT for alpha too? We do, but we're in no position to really respond to problems with it right now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 14: 4:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id C98F914EB7; Sat, 22 Jan 2000 14:04:42 -0800 (PST) (envelope-from musha@ms.tokyo.jcom.ne.jp) Received: from daemon.local.idaemons.org (pc062018.tokyo.jcom.ne.jp [210.155.62.18]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id HAA13382; Sun, 23 Jan 2000 07:03:52 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id HAA53227; Sun, 23 Jan 2000 07:03:20 +0900 (JST) Date: Sun, 23 Jan 2000 07:03:19 +0900 Message-ID: <86r9f9lq6w.wl@localhost.local.idaemons.org> From: Akinori MUSHA aka knu To: chuckr@picnic.mat.net Cc: andrews@technologist.com, shige@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: In your message of "Sat, 22 Jan 2000 12:42:55 -0500 (EST)" References: <20000122123109.E59732@shadow.blackdawn.com> User-Agent: Wanderlust/2.2.15 (More Than Words) EMIKO/1.13.9 (Euglena tripteris) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: A.I.D. MIME-Version: 1.0 (generated by EMIKO 1.13.9 - "Euglena tripteris") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sat, 22 Jan 2000 12:42:55 -0500 (EST), Chuck Robey wrote: > A case would have to be built that bzip2 does something critical that > cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs > is a fine port too, but it'll never get into the base system. Hmm... seems NetBSD folks already have bzip2 in their source tree, while OpenBSD folks not. Then how about us? IMHO, bzip2 tarballs are increasing in number out there because each software is growing bigger and bigger nowadays, and thus in great demand is the better compression: i.e. bzip2 rather than gzip. I don't think we should compress everything with bzip2 instead of gzip, however, I believe we'd better have bunzip2 by default as there are many software which both *.gz and *.bz2 are provided for download, such as Lynx, WindowMaker, GIMP, KDE and Linux kernel. Yes, they are pretty big enough to see the difference between two... .tar.bz2 .tar.gz lynx2.8.2rel1 1.4MB 1.8MB WindowMaeker 0.61.1 1.6MB 1.9MB gimp-1.1.13 6.2MB 8.0MB kdebase-1.1.2 7.0MB 8.9MB linux-2.2.14 12.3MB 15.2MB It's crystal clear bzip2 wins in these cases. and far enough. -- / /__ __ / ) ) ) ) / http://www.idaemons.org/knu/ Akinori MUSHA aka / (_ / ( (__( mailto:knu@idaemons.org "We are but hungry.. Associated Ita-meshi Daemons!" http://www.idaemons.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 14:28:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id D200214D87 for ; Sat, 22 Jan 2000 14:28:09 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 164EE70; Sat, 22 Jan 2000 17:28:12 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: Akinori MUSHA aka knu , freebsd-current@freebsd.org Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Date: Sat, 22 Jan 2000 17:25:09 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20000122123109.E59732@shadow.blackdawn.com> <86r9f9lq6w.wl@localhost.local.idaemons.org> In-Reply-To: <86r9f9lq6w.wl@localhost.local.idaemons.org> MIME-Version: 1.0 Message-Id: <0001221728060I.00537@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, you wrote: > At Sat, 22 Jan 2000 12:42:55 -0500 (EST), > Chuck Robey wrote: > > A case would have to be built that bzip2 does something critical that > > cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs > > is a fine port too, but it'll never get into the base system. > > I don't think we should compress everything with bzip2 instead of > gzip, however, I believe we'd better have bunzip2 by default as there When the port compressed with bzip2 is installed, the extraction mechanism is downloaded and installed on the fly. Thats more than enough. Personally, I'd like to see less stuff in the system source for smaller installs and lower compile time leaving it up to me to customize the individual stuff thats installed. Unless bzip is used by > 99.9% of the FreeBSD installs, I'm willing to let it 'auto-install itself'. -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 14:55:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id B70D614FA8 for ; Sat, 22 Jan 2000 14:55:21 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 2594 invoked by uid 1000); 22 Jan 2000 22:56:03 -0000 Date: Sat, 22 Jan 2000 23:56:03 +0100 From: Andreas Braukmann To: current@freebsd.org Cc: msmith@freebsd.org Subject: Mylex AcceleRAID 250 Message-ID: <20000122235603.C69151@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mike, ... today I tried to build our first Mylex-RAID based FreeBSD-system. Hardware (if you need any more details, just feel free to ask): Gigabyte Dual PPro Board, Natoma, 2*PPro/200 dual channel SymbiosLogic SCSI-Hostadapter (BIOS deactivated), - no disks - just one CD-ROM on the first channel Mylex AcceleRAID 250/8MB ECC-Cache - EzAssist 1.00-16 - Controller 0: DAC960PTL1, FW V4.07-29 - 8 GB BIOS translation - 3 * IBM DNES DNES-309170W - RAID-5, 2 logical disks FreeBSD 4.0-current snapshot 20000103 The installation (over nfs) went very well. I sliced and labeled just the mlxd0. mlxd0s1 was set bootable and I've chosen to install a standard mbr. On Reboot I just get an 'missing operating system'. If I boot from the install floppies again, the RAID-volume ist detected fine. Do you have any hints on what to try next? As I am talking to you yet in any case, I would like to ask you what cache-size to choose. Is it really advisable to stuff the full 64 MByte onto the controller? Where lies the 'sweet-spot' on the cache-size/performance curve? Kind regards and thanks in advance, Andreas P.S. Thanks for this very valuable driver. We're now able to support RAID-configurations even in a 'small-server' setup. The AccelRaid 250 is about $500 in Germany, very affordable compared to a full-blown SCSI2SCSI CMD5440 or the like. -- : TSE GmbH Neue Medien : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 15:22:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 2A38D14D5C for ; Sat, 22 Jan 2000 15:22:49 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 0303B137FBB for ; Sat, 22 Jan 2000 18:22:48 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id SAA90724; Sat, 22 Jan 2000 18:22:49 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14474.15305.507542.292721@trooper.velocet.net> Date: Sat, 22 Jan 2000 18:22:49 -0500 (EST) To: freebsd-current@freebsd.org Subject: On a lighter note... how-to upgrade X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have followed the UPDATES file... and I have source-make-world upgraded several machines from 3.3 and 3.4 to 4.0-CURRENT recently. I thought I'd contribute a method that is reasonably likely to work and reasonably likely to not be going overboard. Someone should maintain a file like this. (generate things needed to make kernel) make all->install usr.sbin/config make all->install usr.bin/genassym (it appears that a lot of things don't work right until the new kernel is in place, and it can be installed first) make 4.0 kernel reboot with 4.0 kernel (remember de->dc change and other device name changes.) (you will have trouble with root not being fsck'd if you crash in here requiring manual intervention. This goes away after you makedev your disks again.) (bootstap compile process) make all->install 1) lib/libc 2) lib/util 3) lib/kvm and usr.bin/top (if you like to watch things run) 4) usr.sbin/yacc 5) gnu/usr.bin/cc make world cp /usr/src/etc/MAKEDEV /dev; cd /dev; MAKEDEV all std (you might also want to MAKEDEV any disk devices that you like) reboot (Paranoia?) make kernel again make world again reboot again The only problem I've run into ... and it was a system that had been source upgraded repeatedly from somewhere back around 2.2.5 ... was that I had a /usr/local/bin/makeinfo lying around that caused trouble for the gnu/usr.bin/cc build. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 15:24:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 9531D1500F for ; Sat, 22 Jan 2000 15:24:53 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 79E5A3E3D; Sun, 23 Jan 2000 00:24:52 +0100 (CET) Date: Sun, 23 Jan 2000 00:24:52 +0100 From: Jesper Skriver To: current@FreeBSD.ORG Subject: Re: apm suspend ?? Message-ID: <20000123002452.A20926@skriver.dk> References: <20000116205650.A64495@skriver.dk> <200001171818.LAA10403@harmony.village.org> <20000117212038.A69519@skriver.dk> <20000117170014.A22939@netmonger.net> <20000117234623.A70090@skriver.dk> <20000119001306.A74876@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000119001306.A74876@skriver.dk>; from jesper@skriver.dk on Wed, Jan 19, 2000 at 12:13:06AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 12:13:06AM +0100, Jesper Skriver wrote: > On Mon, Jan 17, 2000 at 11:46:23PM +0100, Jesper Skriver wrote: > > On Mon, Jan 17, 2000 at 05:00:14PM -0500, Christopher Masto wrote: > > > On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote: > > > > On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: > > > > > In message <20000116205650.A64495@skriver.dk> Jesper Skriver writes: > > > > > : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now > > > > > : suspend doesn't work as expected. > > > > > : > > > > > : When I run 'apm -z' the laptop suspends as normal, but right after this > > > > > : the harddisk led turns on, and it powers up again. > > > > > > > > > > That's very odd. apm hasn't changed since Dec 2 and even that was > > > > > just deleting code that had been obsolete for a while now. > > > > > > > > I don't get it either - will try to revert to -CURRENT as of jan 5th, > > > > and see if it works again ... > > > > > > Sometimes the "enter" at the end of the command is sufficient to wake the > > > machine back up. Have you tried "sleep 2; apm -z"? > > > > Yep, that's not it. > > > > I've just verified, by reverting to -CURRENT as of > > *default date=2000.01.05.12.00.00 > > > > Suspend works as expected, tomorrow I'll try at 2 days intervals, to try > > to narrow down the commit making the difference ... > > And it also works as of > > *default date=2000.01.13.23.00.00 > > But didn't on the cvsup on the 16th ... will try to narrow it down even > further ... I've been trying to narrow it down as much as possible, but -CURRENT was very broken around this time ... *default date=2000.01.05.12.00.00 builds - and suspend works *default date=2000.01.13.23.00.00 builds - and suspend works *default date=2000.01.14.03.00.00 cannot build *default date=2000.01.14.06.00.00 cannot build *default date=2000.01.14.12.00.00 cannot build *default date=2000.01.15.03.00.00 cannot build *default date=2000.01.15.23.00.00 cannot build *default date=2000.01.16.08.00.00 cannot build *default date=2000.01.16.18.00.00 cannot build *default date=2000.01.17.02.00.00 cannot build *default date=2000.01.17.13.00.00 cannot build *default date=2000.01.17.23.00.00 cannot build *default date=2000.01.18.22.00.00 builds - but suspend doesn't work Does anyone have any ideas, on what happened, that made suspend not work ? To summarize, it suspends fine, but immediate power-up again ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 15:40:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 0FAA414FBD for ; Sat, 22 Jan 2000 15:40:46 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.89]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1E68 for ; Sun, 23 Jan 2000 00:40:44 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA20809 for freebsd-current@FreeBSD.ORG; Sun, 23 Jan 2000 00:40:41 +0100 (CET) (envelope-from asmodai) Date: Sun, 23 Jan 2000 00:40:41 +0100 From: Jeroen Ruigrok/Asmodai To: freebsd-current@FreeBSD.ORG Subject: Re: This mornings make world stops at alpm.4 Message-ID: <20000123004041.D18600@daemon.ninth-circle.org> References: <86cj2r$1tod$1@atlantis.rz.tu-clausthal.de> <200001221903.UAA23341@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001221903.UAA23341@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Sat, Jan 22, 2000 at 08:03:11PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000123 00:00], Oliver Fromme (olli@dorifer.heim3.tu-clausthal.de) wrote: >Edwin Culp wrote in list.freebsd-current: > > ===> share/man/man4 > > gzip -cn /usr/src/share/man/man4/ahc.4 > ahc.4.gz > > make: don't know how to make alpm.4. Stop > > *** Error code 2 > > [...] > > Delete src/share/man/man4/alpm.4 > >The committer who deleted (moved) alpm.4 forgot to update the >Makefile. This fixes it: [snip] This has been fixed. Sorry for inconvenience caused. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 15:41: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 9A64414FD8 for ; Sat, 22 Jan 2000 15:40:46 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.89]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB1E68; Sun, 23 Jan 2000 00:40:45 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA20799; Sun, 23 Jan 2000 00:38:57 +0100 (CET) (envelope-from asmodai) Date: Sun, 23 Jan 2000 00:38:57 +0100 From: Jeroen Ruigrok/Asmodai To: joanra Cc: current@freebsd.org Subject: Re: error in share/man/man4 Message-ID: <20000123003856.C18600@daemon.ninth-circle.org> References: <000b01bf6505$272d8640$0164a8c0@daemon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000b01bf6505$272d8640$0164a8c0@daemon>; from joanra@jet.es on Sat, Jan 22, 2000 at 07:18:49PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000122 20:00], joanra (joanra@jet.es) wrote: >==> share/man/man4 >gzip -cn /usr/src/share/man/man4/ahc-4 > ahc.4.gz >make: don't know how to make alpm.4. Stop >stop in /usr/src/share/man >*** Error code 1 I fixed this a few hours after Nicholas committed. Sorry for any inconvenience. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 15:47: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id DC4D714E6E; Sat, 22 Jan 2000 15:47:05 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.89]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1FB5; Sun, 23 Jan 2000 00:47:03 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA20818; Sun, 23 Jan 2000 00:47:00 +0100 (CET) (envelope-from asmodai) Date: Sun, 23 Jan 2000 00:47:00 +0100 From: Jeroen Ruigrok/Asmodai To: Akinori MUSHA aka knu Cc: chuckr@picnic.mat.net, andrews@technologist.com, shige@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123004700.E18600@daemon.ninth-circle.org> References: <20000122123109.E59732@shadow.blackdawn.com> <86r9f9lq6w.wl@localhost.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86r9f9lq6w.wl@localhost.local.idaemons.org>; from knu@idaemons.org on Sun, Jan 23, 2000 at 07:03:19AM +0900 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000123 00:01], Akinori MUSHA aka knu (knu@idaemons.org) wrote: >Yes, they are pretty big enough to see the difference between two... > > .tar.bz2 .tar.gz >lynx2.8.2rel1 1.4MB 1.8MB >WindowMaeker 0.61.1 1.6MB 1.9MB >gimp-1.1.13 6.2MB 8.0MB >kdebase-1.1.2 7.0MB 8.9MB >linux-2.2.14 12.3MB 15.2MB > >It's crystal clear bzip2 wins in these cases. and far enough. Then look at the memory overhead caused by bzipping versus gzipping and you'll loose. Anyways, we have had this discussion a few times in the past. Lets consult the archives and see what the reason was why we didn't do it back then. I am in favor with Chuck here. Its fine as it is, as a port. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 16:33:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2D34D14FD8 for ; Sat, 22 Jan 2000 16:33:31 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA88412; Sat, 22 Jan 2000 17:33:27 -0700 (MST) (envelope-from ken) Date: Sat, 22 Jan 2000 17:33:27 -0700 From: "Kenneth D. Merry" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Replacement for sys/scsiio.h Message-ID: <20000122173326.A88343@panzer.kdm.org> References: <388A1251.D7D0814D@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <388A1251.D7D0814D@cvzoom.net>; from dmmiller@cvzoom.net on Sat, Jan 22, 2000 at 03:25:53PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 22, 2000 at 15:25:53 -0500, Donn Miller wrote: > So which include file do I use in its place? Is it one of > /usr/src/sys/cam/scsi/scsi_*.h? AFAIK, this file isn't in -current > any longer. There are a number of include files for SCSI passthrough now, depending on what you want to do. You should probably take a look at camcontrol for an example of a program that uses SCSI passthrough. Also, see the cam(3), cam_cdbparse(3), pass(4), xpt(4), and camcontrol(8) man pages. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 17: 4:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id BA24614F8C for ; Sat, 22 Jan 2000 17:04:52 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.56]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOR000MQKBMW6@mta4.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Sat, 22 Jan 2000 17:04:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 8B498918D3; Sat, 22 Jan 2000 17:04:34 -0800 (PST) Date: Sat, 22 Jan 2000 17:04:34 -0800 (PST) From: Alex Zepeda Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-reply-to: <0001221728060I.00537@rbtBSD.intranet> To: Rod Taylor Cc: Akinori MUSHA aka knu , freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, Rod Taylor wrote: > Personally, I'd like to see less stuff in the system source for > smaller installs and lower compile time leaving it up to me to > customize the individual stuff thats installed. Unless bzip is used > by > 99.9% of the FreeBSD installs, I'm willing to let it > 'auto-install itself'. What if we began to use bzip2 instead of gzip for things like man pages, or releases, etc? I think gzip is somewhat like compress, in that it might never go away completely, but it's generally been superceded by (IMO) bzip2. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 17:12:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 99BDA14F6C for ; Sat, 22 Jan 2000 17:12:08 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.56]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOR006DVKNQY0@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Sat, 22 Jan 2000 17:11:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 92C26918D3; Sat, 22 Jan 2000 17:11:47 -0800 (PST) Date: Sat, 22 Jan 2000 17:11:47 -0800 (PST) From: Alex Zepeda Subject: Re: With feature freeze being in place In-reply-to: To: Nick Hibma Cc: FreeBSD CURRENT Mailing List Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Nick Hibma wrote: > - writing manpages (or send a skeleton of to someone who will > finish it) > - update HARDWARE.TXT > - check UPDATING > - replace controller with device in all manpages > - improving manpages in general > - FIXING PRs > > We should have a large list of these items circulate the next few > weeks in order to make 4.x the best release of the best ever. Quick question. Perhaps a dumb one. But, is there any way to use cvsup to get the gnats database? I'm looking at /usr/{src,}/share/examples/cvsup/gnats-supfile, and as "equipped" it's not working (well it goes through the motions but checks out no files). Hmm. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 17:18: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id CF4CC14F3A for ; Sat, 22 Jan 2000 17:17:58 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id 578FD70; Sat, 22 Jan 2000 20:18:01 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: Alex Zepeda , freebsd-current@freebsd.org Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Date: Sat, 22 Jan 2000 20:15:26 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: MIME-Version: 1.0 Message-Id: <0001222017550K.00537@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, you wrote: > On Sat, 22 Jan 2000, Rod Taylor wrote: > > > Personally, I'd like to see less stuff in the system source for > > smaller installs and lower compile time leaving it up to me to > > customize the individual stuff thats installed. Unless bzip is used > > by > 99.9% of the FreeBSD installs, I'm willing to let it > > 'auto-install itself'. > > What if we began to use bzip2 instead of gzip for things like man pages, > or releases, etc? > > I think gzip is somewhat like compress, in that it might never go away > completely, but it's generally been superceded by (IMO) bzip2. Agreed, then it'd be useful. I also noticed a message Jordan sent through the list oneday mentioning the possible use of Bzip2 for a new package structure. I do believe that the system should have bzip in it, but because it's being used by freebsd internals itself, not because a person may use it at one point. Make gzip the port in 5.0, and bzip the root compressor... :) -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 17:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A8D1414EC5 for ; Sat, 22 Jan 2000 17:34:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA02632; Sat, 22 Jan 2000 17:34:08 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA17430; Sat, 22 Jan 2000 17:34:07 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 22 Jan 2000 17:34:07 -0800 (PST) Message-Id: <200001230134.RAA17430@vashon.polstra.com> To: jazepeda@pacbell.net Subject: Re: With feature freeze being in place In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alex Zepeda wrote: > > I'm looking at /usr/{src,}/share/examples/cvsup/gnats-supfile, and as > "equipped" it's not working (well it goes through the motions but checks > out no files). Hmm. It works for me. Not all mirrors carry the more esoteric collections like gnats. I know that cvsup[15678] carry it. I think cvsup2 doesn't, and I'm not sure about 3 and 4. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 17:47:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-1.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.129]) by hub.freebsd.org (Postfix) with ESMTP id E9DBC14FB0; Sat, 22 Jan 2000 17:47:01 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA20842; Sun, 23 Jan 2000 01:28:30 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA02749; Sun, 23 Jan 2000 01:28:27 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001230128.BAA02749@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Dag-Erling Smorgrav Cc: Brian Somers , current@FreeBSD.ORG, Jordan Hubbard , Alfred Perlstein , brian@hak.lan.Awfulhak.org Subject: Re: Warning: ioctl(... TUNSLMODE ...) to be depricated.... In-Reply-To: Message from Dag-Erling Smorgrav of "22 Jan 2000 02:12:40 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jan 2000 01:28:27 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers writes: > > Unless there are objections in the next day or two, I'm going to > > deprecate the TUNSLMODE ioctl favour of TUNSIFHEAD. Where TUNSLMODE > > prepended a sockaddr to each packet, TUNSIFHEAD will instead prepend a > > 4-byte network-byte-order address family. > > Don't take it out quite yet. I asked Alfred to implement TUNSLMODE for > a reason; I was working on some VPN software at the time. There are > cases where you want a full sockaddr, not just the address family. The > next-hop address is not necessarily the same as the destination > address, if the interface is in broadcast mode (as opposed to ptp). [half-understanding-grumble] This sounds like a bit of a hack :-( I was seconds away from nuking TUNSLMODE ;oD [put that axe away !] [/half-understanding-grumble] I'll leave the support there, but TUNSIFHEAD will disable TUNSLMODE and vice versa. > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 17:56: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 8A58414FA4 for ; Sat, 22 Jan 2000 17:55:56 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA64409; Sat, 22 Jan 2000 17:55:45 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001230155.RAA64409@gndrsh.dnsmgr.net> Subject: Re: With feature freeze being in place In-Reply-To: <200001230134.RAA17430@vashon.polstra.com> from John Polstra at "Jan 22, 2000 05:34:07 pm" To: jdp@polstra.com (John Polstra) Date: Sat, 22 Jan 2000 17:55:44 -0800 (PST) Cc: jazepeda@pacbell.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article , > Alex Zepeda wrote: > > > > I'm looking at /usr/{src,}/share/examples/cvsup/gnats-supfile, and as > > "equipped" it's not working (well it goes through the motions but checks > > out no files). Hmm. > > It works for me. Not all mirrors carry the more esoteric > collections like gnats. I know that cvsup[15678] carry it. I think > cvsup2 doesn't, and I'm not sure about 3 and 4. cvsup4 carries it, as of the upgrade to cvsupd 16.1 (also added www and doc): Ohhh.. and please update your cvsup-mirror stats, the sizes of things are way way way out of date: {102}% ls CVSROOT distrib doc gnats ports src www {105}% du -sk * 15534 CVSROOT 411 distrib 64790 doc 104577 gnats 136353 ports 594028 src 56562 www -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 18:23: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id E4BA314C38 for ; Sat, 22 Jan 2000 18:22:52 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id SAA26811; Sat, 22 Jan 2000 18:22:49 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id SAA58436; Sat, 22 Jan 2000 18:22:48 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id SAA18355; Sat, 22 Jan 2000 18:22:47 -0800 (PST) From: Don Lewis Message-Id: <200001230222.SAA18355@salsa.gv.tsc.tdk.com> Date: Sat, 22 Jan 2000 18:22:47 -0800 In-Reply-To: References: X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Alex Zepeda Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Cc: Akinori MUSHA aka knu , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jan 22, 5:04pm, Alex Zepeda wrote: } Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip } What if we began to use bzip2 instead of gzip for things like man pages, } or releases, etc? Doesn't bzip2 require a lot more memory for decompression? As I recall, someone mentioned that this would cause problems for installing releases on machines with only a small amount of RAM. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 18:59: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id 79B2F14A14 for ; Sat, 22 Jan 2000 18:59:00 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.23]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOR000F4PI7AR@mta3.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Sat, 22 Jan 2000 18:58:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id F08EC918D3; Sat, 22 Jan 2000 18:56:32 -0800 (PST) Date: Sat, 22 Jan 2000 18:56:32 -0800 (PST) From: Alex Zepeda Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-reply-to: <200001230222.SAA18355@salsa.gv.tsc.tdk.com> To: Don Lewis Cc: Akinori MUSHA aka knu , freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, Don Lewis wrote: > Doesn't bzip2 require a lot more memory for decompression? As I > recall, someone mentioned that this would cause problems for installing > releases on machines with only a small amount of RAM. man bzip2, and then look at the memory management section. I'm sure bzip2 takes more memory to encode/decode but I wonder how it compares when using -s. FWIW, I think that there are already problems with installing with less than 12mb ram in the first place (or so I've heard). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 19: 3:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id DC2F014A11 for ; Sat, 22 Jan 2000 19:03:42 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.23]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOR00C67PO7FM@mta4.snfc21.pbi.net> for current@freebsd.org; Sat, 22 Jan 2000 19:00:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 8115D918D3; Sat, 22 Jan 2000 19:00:05 -0800 (PST) Date: Sat, 22 Jan 2000 19:00:05 -0800 (PST) From: Alex Zepeda Subject: Re: With feature freeze being in place In-reply-to: <200001230134.RAA17430@vashon.polstra.com> To: John Polstra Cc: current@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, John Polstra wrote: > It works for me. Not all mirrors carry the more esoteric > collections like gnats. I know that cvsup[15678] carry it. I think > cvsup2 doesn't, and I'm not sure about 3 and 4. Hah, I forgot to delete the tag=. line. Oops :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 19:26:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 335F814C1A; Sat, 22 Jan 2000 19:26:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id TAA37994; Sat, 22 Jan 2000 19:25:41 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001230325.TAA37994@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Rodney W. Grimes" Cc: obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: Your message of "Fri, 21 Jan 2000 17:39:39 PST." <200001220139.RAA59492@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Jan 2000 19:25:40 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > There are couple of RFCs on network load balancing with > > respect to servers or services and I am sure that there > > are also widely available research papers. > > Most of those concentrate on balancing the load on the server > itself. How about balancing the load on the network paths, > I doubt very much that we have a server load problem near as > much as we have a network load problem due to people not > having ready access to the data that says ``this server is > closest network wise to me''. > > Hi Rod! Perhaps RFC 2391 may be of use. Network Working Group P. Srisuresh Request for Comments: 2391 Lucent Technologies Category: Informational D. Gan Juniper Networks, Inc. August 1998 Load Sharing using IP Network Address Translation (LSNAT) Enjoy -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 20: 5:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 20A4F15068 for ; Sat, 22 Jan 2000 20:05:48 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id XAA56397; Sat, 22 Jan 2000 23:05:45 -0500 (EST) (envelope-from wollman) Date: Sat, 22 Jan 2000 23:05:45 -0500 (EST) From: Garrett Wollman Message-Id: <200001230405.XAA56397@khavrinen.lcs.mit.edu> To: Alex Zepeda Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: References: <200001230222.SAA18355@salsa.gv.tsc.tdk.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I may inject some possibly-irrelevant fact into this discussion... gzip (or rather, the ``deflate'' compression algorithm and the libz file format) has been adopted into a number of formal standards. It's likely that it will remain with us for a long time. For those of us who eschew bloatware, it continues to be entirely adequate. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 22: 5:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 9220014FDF for ; Sat, 22 Jan 2000 22:05:13 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com (j39.klt31.jaring.my [161.142.169.233]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id QAA11610; Sun, 23 Jan 2000 16:34:18 +1030 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id NAA00489; Sat, 22 Jan 2000 13:22:11 +0800 (SGT) (envelope-from grog) Date: Sat, 22 Jan 2000 13:22:11 +0800 From: Greg Lehey To: John Polstra Cc: joe@pavilion.net, current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000122132210.E391@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <20000121190729.C58872@florence.pavilion.net> <200001211911.LAA11701@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001211911.LAA11701@vashon.polstra.com>; from jdp@polstra.com on Fri, Jan 21, 2000 at 11:11:40AM -0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 21 January 2000 at 11:11:40 -0800, John Polstra wrote: >> Can you make cvsup accept multiple servers to try in it's configuration >> file? > > I'll add that to the to-do list. When you get the appropriate tuit, you might also consider checking which of the list is most accessible. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 22 22:51:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by hub.freebsd.org (Postfix) with ESMTP id F300514F6A for ; Sat, 22 Jan 2000 22:51:52 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (obica-2-185.mdm.mkt.execpc.com [169.207.90.123]) by mailgw01.execpc.com (8.9.1) id AAA06027; Sun, 23 Jan 2000 00:51:42 -0600 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 6E26E97; Sun, 23 Jan 2000 00:54:46 -0600 (CST) X-Mailer: exmh version 2.1.1 10/16/1999 To: Alex Zepeda Cc: Rod Taylor , Akinori MUSHA aka knu , freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-reply-to: Your message of "Sat, 22 Jan 2000 17:04:34 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jan 2000 00:54:46 -0600 From: Jon Hamilton Message-Id: <20000123065446.6E26E97@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Alex Zepeda wro te: } On Sat, 22 Jan 2000, Rod Taylor wrote: } } > Personally, I'd like to see less stuff in the system source for } > smaller installs and lower compile time leaving it up to me to } > customize the individual stuff thats installed. Unless bzip is used } > by > 99.9% of the FreeBSD installs, I'm willing to let it } > 'auto-install itself'. } } What if we began to use bzip2 instead of gzip for things like man pages, } or releases, etc? I did that (for man pages) out of curiosity a year or two ago, and the difference was negligible. bzip2 seems to do better on bigger files as a (very) general rule than on smaller ones. } I think gzip is somewhat like compress, in that it might never go away } completely, but it's generally been superceded by (IMO) bzip2. I don't agree at all, and all you have to do is visit a few web sites and ftp sites' download areas to see why. It's just not ubiquitous, or even close. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message