From owner-freebsd-bugs Sun Jan 14 0:30:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DC10E37B402 for ; Sun, 14 Jan 2001 00:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E8U1O28347; Sun, 14 Jan 2001 00:30:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1E39D37B402 for ; Sun, 14 Jan 2001 00:28:46 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E8Sku28210; Sun, 14 Jan 2001 00:28:46 -0800 (PST) (envelope-from nobody) Message-Id: <200101140828.f0E8Sku28210@freefall.freebsd.org> Date: Sun, 14 Jan 2001 00:28:46 -0800 (PST) From: h-hoshi@venus.dti.ne.jp To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24320: DMA doesn't work with Alladain V and K6-2 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24320 >Category: kern >Synopsis: DMA doesn't work with Alladain V and K6-2 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 14 00:30:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: HOSHIMOTO, Hiroyuki >Release: 4.2-STABLE >Organization: The University of Tokyo Hospital. >Environment: %uname -a FreeBSD neko.funyafunya.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 10 22:00:2 5 JST 2001 mizuho@neko.funyafunya.com:/usr/src/sys/compile/NEKO i386 % %dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Wed Jan 10 22:00:25 JST 2001 mizuho@neko.funyafunya.com:/usr/src/sys/compile/NEKO Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 127520768 (124532K bytes) Preloaded elf kernel "kernel" at 0xc0321000. 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 ohci0: mem 0xebfef000-0xebfeffff irq 10 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: at device 3.0 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xdf00-0xdf3f irq 9 at device 14.0 o n pci0 xl0: Ethernet address: 00:60:97:77:ef:41 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xffa0-0xffaf irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: <3Dfx Voodoo graphics accelerator> at 16.0 pci0: at 18.0 irq 11 pci0: (vendor=0x1092, dev=0x9999) at 20.0 irq 5 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,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ad0: 6149MB [13328/15/63] at ata0-master UDMA33 ad1: 1549MB [3148/16/63] at ata0-slave WDMA2 ata1-master: Aladdin: two atapi devices on this channel, no DMA acd0: CDROM at ata1-master using PIO4 ata1-slave: Aladdin: two atapi devices on this channel, no DMA afd0: 96MB [96/64/32] at ata1-slave using PIO0 Mounting root from ufs:/dev/ad0s2a ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ad0: trying fallback to PIO mode ata0: resetting devices .. done % >Description: When DMA enabled ,my machine fails to read ata disk with dma mode on startup, and fallback to PIO mode. After falling back to PIO mode, the machine works fine . >How-To-Repeat: Boot with ATA-DMA enabled KERNEL. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 0:50:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 854E337B402 for ; Sun, 14 Jan 2001 00:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E8o1V29640; Sun, 14 Jan 2001 00:50:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6EACC37B6BF for ; Sun, 14 Jan 2001 00:41:41 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E8ffW29111; Sun, 14 Jan 2001 00:41:41 -0800 (PST) (envelope-from nobody) Message-Id: <200101140841.f0E8ffW29111@freefall.freebsd.org> Date: Sun, 14 Jan 2001 00:41:41 -0800 (PST) From: davidx@viasoft.com.cn To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24321: cdcontrol default still using old device name cd0c Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24321 >Category: misc >Synopsis: cdcontrol default still using old device name cd0c >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 14 00:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: David Xu >Release: FreeBSD 4.2-stable >Organization: viasoft >Environment: FreeBSD davidbsd.viasoft.com.cn 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13: 02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 >Description: cdcontrol default is still using old device name cd0c while FreeBSD 4.x is already using new ATAPI interface and default cdrom device name is already changed to /dev/acd0c, cdcontrol is simply not follow-up. >How-To-Repeat: davidbsd# cdcontrol cdcontrol: no CD device name specified, defaulting to /dev/cd0c Compact Disc Control utility, version 2.0 Type `?' for command list cdcontrol> eject cdcontrol: no disc in drive /dev/cd0c cdcontrol> >Fix: I think it is simple to fix it. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 1:30:28 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4A1B837B404 for ; Sun, 14 Jan 2001 01:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E9U4q34281; Sun, 14 Jan 2001 01:30:04 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 01:30:04 -0800 (PST) Message-Id: <200101140930.f0E9U4q34281@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Soren Schmidt Subject: Re: misc/24318: burncd fails on fixate Reply-To: Soren Schmidt Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24318; it has been noted by GNATS. From: Soren Schmidt To: sjh13@po.cwru.edu Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/24318: burncd fails on fixate Date: Sun, 14 Jan 2001 10:28:39 +0100 (CET) It seems sjh13@po.cwru.edu wrote: I have committed a fix for this to -current, MFC will follow shortly. The problem is that some drives wont close a CD in multisession mode if the firmaware decides that there is not room enough for a new session. Dont you just love "smart" firmaware..... > > >Number: 24318 > >Category: misc > >Synopsis: burncd fails on fixate > >Confidential: no > >Severity: non-critical > >Priority: medium > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sat Jan 13 23:00:01 PST 2001 > >Closed-Date: > >Last-Modified: > >Originator: Steven Huwig > >Release: 4.2-RELEASE > >Organization: > Case Western Reserve University > >Environment: > FreeBSD mulder.student.cwru.edu 4.2-RELEASE FreeBSD 4.2-RELEASE #1: Sat Jan 13 17:01:33 EST 2001 steve@mulder.student.cwru.edu:/usr/src/sys/compile/MULDER i386 > > >Description: > Using a Creative Labs ATAPI CD-RW drive. > > >How-To-Repeat: > Try to burn a CD with this system. > > MSI-6330 Athlon Socket A MB > Creative Labs RW8438E > FreeBSD 4.2 > >Fix: > > > >Release-Note: > >Audit-Trail: > >Unformatted: > >ad0: 29314MB [59560/16/63] at ata0-master UDMA66 > >acd0: CDROM at ata1-master using PIO4 > >acd1: CD-RW at ata1-slave using WDMA2 > > The drive appears to write to the media, but burncd outputs: > > >mulder# cat ./4.2-install.iso | team 100k 8 | burncd -f /dev/acd1c -s 8 data /dev/stdin fixate > >next writeable LBA 0 > >writing from file /dev/stdin size 0 KB > >652450 kilobytes, 545 seconds(65179600%) total 651796 KB > >written this track 652450 KB (65245000%) total 652450 KB > >fixating CD, please wait.. > >burncd: ioctl(CDRIOCCLOSEDISK): Input/output error > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 1:30:32 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 02A5D37B402 for ; Sun, 14 Jan 2001 01:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E9U2734275; Sun, 14 Jan 2001 01:30:02 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 01:30:02 -0800 (PST) Message-Id: <200101140930.f0E9U2734275@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Soren Schmidt Subject: Re: kern/24320: DMA doesn't work with Alladain V and K6-2 Reply-To: Soren Schmidt Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24320; it has been noted by GNATS. From: Soren Schmidt To: h-hoshi@venus.dti.ne.jp Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24320: DMA doesn't work with Alladain V and K6-2 Date: Sun, 14 Jan 2001 10:25:41 +0100 (CET) It seems h-hoshi@venus.dti.ne.jp wrote: I did a fix that has been committed to -current, MFC will follow shortly... > > >Number: 24320 > >Category: kern > >Synopsis: DMA doesn't work with Alladain V and K6-2 > >Confidential: no > >Severity: serious > >Priority: high > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sun Jan 14 00:30:01 PST 2001 > >Closed-Date: > >Last-Modified: > >Originator: HOSHIMOTO, Hiroyuki > >Release: 4.2-STABLE > >Organization: > The University of Tokyo Hospital. > >Environment: > %uname -a > FreeBSD neko.funyafunya.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 10 22:00:2 > 5 JST 2001 mizuho@neko.funyafunya.com:/usr/src/sys/compile/NEKO i386 > % > > %dmesg > Copyright (c) 1992-2001 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-STABLE #0: Wed Jan 10 22:00:25 JST 2001 > mizuho@neko.funyafunya.com:/usr/src/sys/compile/NEKO > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 > Features=0x8001bf > AMD Features=0x80000800 > real memory = 134217728 (131072K bytes) > avail memory = 127520768 (124532K bytes) > Preloaded elf kernel "kernel" at 0xc0321000. > 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 > ohci0: mem 0xebfef000-0xebfeffff irq > 10 at device 2.0 on pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > chip1: at device 3.0 on pci0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xdf00-0xdf3f irq 9 at device 14.0 o > n pci0 > xl0: Ethernet address: 00:60:97:77:ef:41 > miibus0: on xl0 > nsphy0: on miibus0 > nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > atapci0: port 0xffa0-0xffaf irq 0 at device > 15.0 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: <3Dfx Voodoo graphics accelerator> at 16.0 > pci0: at 18.0 irq 11 > pci0: (vendor=0x1092, dev=0x9999) at 20.0 irq 5 > 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,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > 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 > ppbus0: IEEE1284 device found /NIBBLE/ECP > Probing for PnP devices on ppbus0: > ppbus0: MLC,PCL,PML > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ad0: 6149MB [13328/15/63] at ata0-master UDMA33 > ad1: 1549MB [3148/16/63] at ata0-slave WDMA2 > ata1-master: Aladdin: two atapi devices on this channel, no DMA > acd0: CDROM at ata1-master using PIO4 > ata1-slave: Aladdin: two atapi devices on this channel, no DMA > afd0: 96MB [96/64/32] at ata1-slave using PIO0 > Mounting root from ufs:/dev/ad0s2a > ad0: READ command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: READ command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: READ command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: READ command timeout tag=0 serv=0 - resetting > ad0: trying fallback to PIO mode > ata0: resetting devices .. done > % > >Description: > When DMA enabled ,my machine fails to read ata disk with dma mode on > startup, and fallback to PIO mode. > After falling back to PIO mode, the machine works fine . > > >How-To-Repeat: > Boot with ATA-DMA enabled KERNEL. > > >Fix: > > > >Release-Note: > >Audit-Trail: > >Unformatted: > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 1:40:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 55F6B37B400 for ; Sun, 14 Jan 2001 01:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0E9e2x34761; Sun, 14 Jan 2001 01:40:02 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 01:40:02 -0800 (PST) Message-Id: <200101140940.f0E9e2x34761@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Salvo Bartolotta Subject: Re: misc/24319: FreeBSD refuses to boot up. Reply-To: Salvo Bartolotta Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24319; it has been noted by GNATS. From: Salvo Bartolotta To: Mtaki_kat@hotmail.com Cc: freebsd-gnats-submit@freebsd.org Subject: Re: misc/24319: FreeBSD refuses to boot up. Date: Sun, 14 Jan 2001 09:41:32 GMT >Number: 24319 >Category: misc >Synopsis: FreeBSD refuses to boot up. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 13 23:10:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Charles Lefave >Release: 4.0 >Organization: MtakiSoft Webwork >Environment: >Description: .. I install FreeBSD, there's no problem.. I get to the bootloader..=20 It says press F1 for DOS, F2 for FreeBSD.. And when I press F2, I just=20 get a beep and it wont load. Dear Charles Lefave, Surely your "/" partition is **below** the deadly (BIOS) limit of ~=20 8.4 GB ? If it lies **past** the first 8.4 GB, I am afraid you won't be able to=20 boot. You'll have to rearrange things in order to meet the=20 aforementioned BIOS "boundary value condition" :-) Best regards/cordialement, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 2:50:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 28A2137B400 for ; Sun, 14 Jan 2001 02:50:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EAo3g40290; Sun, 14 Jan 2001 02:50:03 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 02:50:03 -0800 (PST) Message-Id: <200101141050.f0EAo3g40290@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Pentchev Subject: Re: bin/24228: /bin/sh problem : variable after pipeline won't be set Reply-To: Peter Pentchev Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24228; it has been noted by GNATS. From: Peter Pentchev To: imura@af.airnet.ne.jp Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/24228: /bin/sh problem : variable after pipeline won't be set Date: Sun, 14 Jan 2001 12:47:51 +0200 On Thu, Jan 11, 2001 at 01:32:48AM +0900, imura@af.airnet.ne.jp wrote: > > >Number: 24228 > >Category: bin > >Synopsis: when using /bin/sh, setting variable after pipeline won't work > >Originator: Ryuichiro Imura > >Release: FreeBSD 4.2-STABLE i386 > >Environment: > > FreeBSD 4.2-STABLE > > >Description: > > When using /bin/sh, setting variables after "|" > (in other words, I mean setting variables in a pipeline sequence), > will be ignored out of the pipeline sequence. > > If it is a definition of /bin/sh, it's ok, I'm sorry, > otherwise I think it should be fixed. AFAIK, yes, this is expected sh(1) behavior. From the manpage: Note that unlike some other shells, sh executes each process in the pipeline as a child of the sh process. Shell builtin commands are the exception to this rule. They are executed in the current shell, although they do not affect its environment when used in pipelines. That is, sh(1) forks a subshell for each subsequent command/construct in the pipe, and variable assignments within a construct are only valid for the subshell that construct is executing in, and not back-propagated to the main shell. Thus, in your example, 'variable' would only be set to 'bar' for the subshell executing the while loop. See below for a suggestion for a workaround. > >How-To-Repeat: > > write a simple shell script like this: > -----------starts here---------- > #/bin/sh > > cat FILE | while read line ; do > if [ $line = foo ]; then > variable=bar > fi > echo $variable <---- this will be printed > done > > echo $variable <---- this will NOT be printed > -----------ends here------------ You may do better with something like the following: #!/bin/sh # (make sure that's #!, not just # ;) exec < FILE while read line; do if [ "$line" = "foo" ]; then variable="bar" fi echo "line is $line, variable is $variable" done echo "after the loop, variable is $variable" Hope that makes things clearer :) G'luck, Peter -- Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 8: 0:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 80DDD37B400 for ; Sun, 14 Jan 2001 08:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EG04f47092; Sun, 14 Jan 2001 08:00:04 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 08:00:04 -0800 (PST) Message-Id: <200101141600.f0EG04f47092@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "R. Imura" Subject: Re: bin/24228: /bin/sh problem : variable after pipeline won't be set Reply-To: "R. Imura" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24228; it has been noted by GNATS. From: "R. Imura" To: Peter Pentchev Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/24228: /bin/sh problem : variable after pipeline won't be set Date: Mon, 15 Jan 2001 00:49:26 +0900 On Sun, Jan 14, 2001 at 12:47:51PM +0200, Peter Pentchev wrote: > AFAIK, yes, this is expected sh(1) behavior. From the manpage: > > Note that unlike some other shells, sh executes each process in the > pipeline as a child of the sh process. Shell builtin commands are the > exception to this rule. They are executed in the current shell, although > they do not affect its environment when used in pipelines. > > That is, sh(1) forks a subshell for each subsequent command/construct > in the pipe, and variable assignments within a construct are only valid > for the subshell that construct is executing in, and not back-propagated > to the main shell. > > Thus, in your example, 'variable' would only be set to 'bar' for > the subshell executing the while loop. See below for a suggestion > for a workaround. Thanks very much for your explanation. I got it. :) So, please close this PR. - R. Imura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 8:10:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 98F3537B402 for ; Sun, 14 Jan 2001 08:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EGA1L49905; Sun, 14 Jan 2001 08:10:01 -0800 (PST) (envelope-from gnats) Received: from ntua.gr (achilles.noc.ntua.gr [147.102.222.210]) by hub.freebsd.org (Postfix) with ESMTP id 2AAB337B401 for ; Sun, 14 Jan 2001 08:09:53 -0800 (PST) Received: from netmode.ntua.gr (dolly.netmode.ece.ntua.gr [147.102.13.10]) by ntua.gr (8.9.3/8.9.3) with ESMTP id SAA03008 for ; Sun, 14 Jan 2001 18:09:46 +0200 (EET) Received: from edgar.netmode.ece.ntua.gr (ppp079.dialup.ntua.gr [147.102.223.79]) by netmode.ntua.gr (8.11.1/8.11.1) with ESMTP id f0EGLeJ72343 for ; Sun, 14 Jan 2001 18:21:40 +0200 (EET) (envelope-from past@edgar.netmode.ece.ntua.gr) Received: (from past@localhost) by edgar (8.11.1/8.11.1) id f0EG4X801007; Sun, 14 Jan 2001 18:04:33 +0200 (EET) (envelope-from past) Message-Id: <200101141604.f0EG4X801007@edgar> Date: Sun, 14 Jan 2001 18:04:33 +0200 (EET) From: past@netmode.ntua.gr Reply-To: past@netmode.ntua.gr To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/24324: Greek console support Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24324 >Category: misc >Synopsis: Greek console support >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Jan 14 08:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Panagiotis Astithas >Release: FreeBSD 4.2-STABLE i386 >Organization: National Technical University of Athens >Environment: >Description: FreeBSD doesn't support the greek locale and it doesn't provide either the necessary keymap files for the syscons driver, nor the ISO-8859-7 fonts. Therefore, one cannot read or write greek text in the console, or use the familiar locale settings for most greek users. >How-To-Repeat: Try to read or write greek text in the console. Try to view the date in Greek using date(1) after having set the environment variable LC_ALL=el_GR.ISO_8859-7. >Fix: The necessary files are included here. The directories colldef, mklocale & timedef contain the locale files. The directory consolefonts contains the ISO_8859-7 fonts for the sizes 8x8, 8x14, 8x16. The directory keytables contains the necessary keymaps to provide the ability to write greek text in the console (courtesy of peppe@cs.uoi.gr). There are keymaps for standard PC keyboards (greek.us101.acc.kbd) and keyboards following the ELOT-1000 greek standard (greek.elot.acc.kbd). If it is necessary, I will submit patches to the necessary Makefiles in a followup-PR. This is the uuencoded attachment. begin 644 greek-console.tar.gz M'XL("/'#83H``V=R965K+6-O;G-O;&4N=&%R`.Q<76P45Y8N923OTFHY:)]: M&^140CPF))CJZK;=IBM-C''`";$]_.1O/$O_%CB4W8Z[;0QT.@&MHGV8AWU< M7E::AWW9MU5>]F&C=>)5:[/R9"-EA)`@!#+"*!D2S`[)H)&G>\_/O55UJTT3 M,AG0[/H:WU/WGGO/_3MUSSE?MSDR4R@MSHZ^G1-5V/ M]O5$_50F0]?[S)@1BT?-6!38T;Y87--[_C334=-LJ9R9T75M.E,JMVIW-_Z? M:3JBG'^NZ#CY@OT#Z\$]G7]/+[!CL9[8^OG?C[3V^1>/[1GFCP_*&YH>G&#[?,.Z?_Y^>_6=^#&K`=SEKG ML]:W9#.Y8\TI("-9R':/8K]\*MF9_#%TV="5'-^2''\RN37Y M5-)Z:AN(>3II;0.Z+=F=W(Y"]?S$D8DR#+[%>-J*FJDGD]'D%O-IRSP`CUMB M3ULQ?(C31/IY%CN2X\GDN)5\)IE*[H3I#,&8@T7(!LHT3SV7F9XH9YS0A@'J M]AK.Q!KHQ!9;(=N%V1[,=F,VA(PA?'H-LU<[4]3^52SLQ>QYS(:QU3`^O8#9 M/LQ>Q&QD*[YV>L.D$/AW#S,%L4JQN"@LYS(K8:IJ>,)O! MK(39UA)D9=%^%J7.8?4LMI_%)QNS>P.PX,H[+Q8Z?@JT$[:G`^>R"NC>3 MU:35_2(>TA[,#O+1SA0F,Q-3J*M=I'7]L"E65S^>#:K!;M3/D>=QKU'Z-NS? M)98\]PSNR_0-C>[&]&:4V?064Q,^V M'1K;/SQRD-B&CVVX[$,C@P=]O4T<+9:AY[@!64^6GGOQN2\K18`AV>".DNW! MK`^S+&9Y/71@;&!PB!;13TV,/*Z2EWAH;&QHOW_7[K)769Q2CH?*9T/[1E^F M[KZMSN'D\CFQLZ%7:(^\J]K=*WD^-CSQZ,]UA<":#N\>&H5M?!$>#XP-#0X/ M[(.GL;V@*E0;>G%@C$85\L#HNG/?@3)3:[1PIR=:N$TV6&*]^5Q*K737OP.Y M^0`7=\0.=G%W"+O8@2[NGA&W$.5)T/:OO9(!7DF@A7\E`UT^(30&;7TFI53F MZ?1Z`Y5YG@W/-9M0N062DPU4"BTVJ4LNJG+M&':)!2KCW(77G.\)<&EBN4!E M7KZ2-+$"K/#@J%^%8`]<#8(FJ6:V5"9@1]?BNVK'_`=]@_YY)]7^EROXSWU,:Y___<5_8KU]@?/OC?>8Z_[?_4B;P3B_/+!_!/RY'7II.I,K ME/3)S`D=C&&A5"I,E2N3Q:GR47TJ,XG=0Q]>^2IT[NKGH:4K-T/OK]P$^OO0AS>^ M@M_?A-[_YM>A3ZZNA/[[RUNA7]ZX&OJ/JU^2G'W%J2/-8FY\<_'F%S?^!Z7= ME,]+%V_>0@J2/_L-5_P>\@]O_.&K+YA2[?M_^/6-;WY["YY@N%N?7O^<.L.P M=7[ZY0U9!U.0C]Z*CL/+DX?=DI/YKV]N0L-O0K^Z^47H5U=OA3Z^>CWT,:SO MDRN?>_-?H],75[Z\A!UO?7KS"G3^[-8U[`Y+N!;Z^-/K*TBNW+SRVR^O?G,I M],G%SS^_8`JYV5E?GOGY/;.$U29DY49O;.@ M=V;USE?TSE>)E9D$LG*=GJ?Q^3H_YS/E0E.O5ZGC:X'3*/%B]"T9!_S\J4QY M8J[PY(,[G"%;SALGS57/^:IVK3L-,@7Q?Z(VG&GIAW,"[L7^QPW$_^/QGO7/ M_^Y+:G'^$Z6BT==M1WO_V#%:VW_@&L'S[S5B?>OV_\&DZNE_.GWZO;.G3U=% MN7&AT5B\UFA490NG#JF2V"C+&Q,5?S%B6=>N78M$++=F9M$^*E!Z=HB M#H")*BU[UR[;\OB+9]][[^RBX'>T_[4YOP1I7A.-(5D1&(#+.V,[4:.F5RYS M^:W<6SE(1ZXM+XC!(Q>L:]8%T?[MAKN&4!>55_&9.<'B5O M0*@*U\,1GS`C74\K+\?"PD+=5]SBU)TM7G%C(E&IU+T&<'B5A'=>@01G8^%D MQ'Q@J4^H#1R03K\\VTKM@X5*6]L[M8IU<,1(U][A4L)Q$G,7X;SF>.Z& MD5;$05M*D;!87"1,*>*MT+8:ENV?HG?:OCI?!ZVN-26OQT-M.#]QWAJ>UKES M>&*B76)>G`"7*S5N7JN[Y3:KK:U-'F]XD^4LU6'"'6)H.(Q5'S^1AG(-DBC7 MH3^O6PPH4/Q`NJW7;XA7!NB_79V:/S1]-9 MNZZ4T^D57_]+M9J]@\LX$@TGQK/$"R#OBP[2!N]]7X:AYN=AT&4NKZ0IN>/5 MOJ[7S_GDU9:_K5_ZR"O37OOVF]:7]N8G^.3\^#KSY-5K[^#A?2#USS)$DO M>^+7??Q>$^%WPW#U69O#YDN5,!TIR'?F;&]_02\3_OUL:]/:VRC9I'+0GA5` MM$\$]`72]3IL\#EOW1?%E>W-SW<^+K_BJH"[U_M&PUC% MY?5N-CDN__XOAI$RC&AT)Y???3<6 MVQF#)/C_]@_!^PV6[IQW^__CNS%*XJ[2TI>SM@/WQ44P&QU"'MG0#MG^,4RQ MOZ(!PG^IV>(*$??)W>Q_/^/Y[_^Z:[!]ZTTK][V2Z@O@4*%#*.0%[7_0?H.C?_;L MV:K//U#M?>0")H]OV8N8[">N47%1O=\7F^2#7W'J([0WI]PRV.=YU_Y"6=@_ M,*%<]I\WJNLU8GM*K%=@-"L>6//NNC+]*WC.D M^;!T:97YI"`XHP@MY?97]!'2LF+O'=#E7L6>L[BWX,RX?`;V&$RJ&#^],$\3 M@"#%\BW)9_\;`?_`DOZ`D)?*+2SX++[V5G"]`?L?W,]Q=$?.539NE"Y@P-Z? M"_!1`RXTQ'P6`_L1/"\Z;]]ZH!SD*_+4]!WPG_A:_>XEW>7SG[ZU\!\SMH[_ M/(BDHC]![$=%?A3<1T5]@IB/"_BH<`_6>&"/"O4$D1X5YU%1G@#&XT=X5'PG M@.ZHV$X`V7&!'2RPUZ*B.A+341$=%<]I0G-4+">`Y"@XCH+BJ!A."P2'X1OA M9@3!&X)M&+F1P(V+VWQ0VY1H`FTHA@E`-@*P$7&C@&L\\$4%:YJ@&@6G"<8@ MLJF"T!!`X\9/$IYAC13@C/`M!#0CCD@",^SW"%A&\"0HPR47DA%2&)"IN*6J M#XUA7U932F)!),.'P_AA&`1A7`R&(1@I!D?P\!?7_:*2=+[8]V+H12(O`G@1 MN`N[7=+KDJ#+BM?ODD1<7`>,>8JWU:%@+>1ZN9[7BH*SN&X7EZ33Y:[(LTC2 MH5KQ\22Z(L&59N)<&0B=B#1(XF?-X=9LWO4GT M$\"(YQ>IJ(B*B>`)>H@(.DCNG@?!D)\GIL7Y22A$>+(*#B)A$$1!FC"0=03D M_VA2T8L`=B&AB^^`7+`>26U2C+\*6-P5K5"1"A6G:(522(0BB$_XX0D%FU"1 M"167"*(2'BBA-2,2#$A(/$*%(R08(891D`@_$.$'(5*:!T)TB)8>`N$!$/P6 MM[)_$GI8\5JZKW'`_BGWO&KQ).#`MY1J_U2+YT(-+*6%Q1,@PYFZ.X)W?[H` M@[>B.Z`+!"VXR()J_U0[1J!"U;.-?HL74?`$AA,$FN"!"9H?2N"6$D@X)0K^ M*-X%$10(@4[,!1!-=T?(0`$,7+Q`10N6?19/ M0@62)W$"+C%,H*D0@>]3.,_5;RBVT1+FD$NIG!\;>$M!!BJ*_5-W:5S$_%Q2 M+)YV3N'97O2^J*Q6W7D)!+@GIO+L-3&`N\?_1B+8YU[37>+_^'K\_^`3QOT0 M]E'$_=^PH-6`%$T&S!@F M8Z`<2:6MM@HTK"U%#+L&5PK&Q7-NT$=A(X3"%`9CG0Q__8$O-_:L/3!D@`LO M_3ET@R,)#FHAA-UD@!$#:F&PRC%L!X:OJUB&P'457_%ZC0/6"L6J%:15"E)E M?"HB4QR'0U*.1C$.Q3"TPA$HT$N7+BW,XSS(Z*Z2O5V%XX1]@_.D(!-"S#I9 MUSI3,%[(_P@"2F%+A1FU*(#$"W!9!!XK(F04QA/-)EI-%[)<%9^[4OFC2OLJ MQ8/+(!\F"N.S$;0T:5!%W,<2$\2P1V"W0MQ\>$N&< M%8SE&M['WQBUS4'(A.X&Q@M@CG#_W8_",3JKP+S2M]EXSV$0=/LRQ6++&D=A MEM:F7Q+RPQ%>9^4,[T?E M#&D&Z#>7Y?N(\UNHAA.5,]R^)O;'$/UML1_0WW,7&UHC$F9Y\GV.&/6%V_"" M&I'ZPBK0Q&ZF*)?.6^.RK;&C,O^W<S;8C](/6O\3Q1+S36$WB78'Z1"/C\ M*VG0Y[3!]94S&M'V1R)6Y/RT%A&?38;=]YG'C;CR?=H2"<_/AQ/DDDCWO'K: M=:#JPL>IHY>26W:J,7OI8:`G>U__K.V*F=_Q[=;#9S2HM-'OA=Q>TK3'_XY_ M#OTS_QS_E'\BOG1;Y$A[(7T+OS0045G_;1O6RX33X/*W;7C]X5.=KAYH+^9^ M6\A_5&.O0JZI(>M%+-V0?%'[J)A''\GO,SA0V&EP^7=B;QK:[P2_C^;3H'KD M8SV.UA#SDNT;EA MD=SO&L(;\9\7YS3P1,\OU9;@_D"_$P\2O^3F0#DMX,7J^?/G$4P@YV\!NM%[ M58U89.!(JT'_Z*-MYVMX_\(I=KZJX(QC!(8TO=!AI*MIHT/&"`B!XH\;UM'U M#)2N;:#MCSSB*0).`!M%:-KT+OO"0_<+A)@]#+?==G%*?[F0AZW7 M!Z9G]&C/CI[^'1"S#0T=.*A'^_L3]'?[A>GIPK.Y4O=L<0+_9'^S_GU3QBGC M?SF3RTS=H4%NJCSC*.T]PCRGF#M&_]%0OJ#KV4P)ZVH6T8HG1,20;W*S9[G9K.,CK7A"1!SY,6ZV>:U9M.`)$3W(CW.S M)]82T8(G1/0BOX>;=:XEH@5/B.A#?B\W^QLB,R7=1UKQA(@$\ONXV8_7FD4+ MGA#1C_P$-]NZEH@6/!:!_\T:_=T]DBUKB6C!$R)0._$/^)$\N9:(%CPA@K1S M&S<[S,UXKP1IQ1,B2#N?X69/K36+%CPA`K4SRT(%R1<<'VG%$R)0.X^6N1F8 MS::16O&$"-+.-WBR/R&2ST5]I"O)O!UK\/1!$D':>9R;O4RD4,[ZB!DWB=#1 M!7A"!&EG@44,L8BI-WS$-%'YP`[T-?.$"-+.&1:Q7TS6]!$S3L.;I,8!'HLP M23O++.*@$!'W$3/.)&HV\X0(TLX3+.)57LBD[B-FO(=%Q)IY0@1IYRR+.,3J MDSGF(V:,UT-7?8`G1)!V3K"(82)"$P0Q8S$6$6WF"1%T=Q99Q"B1TH3N(V:L MGT7T-?.$"+H[IUG$&&^G4_`1,VZPB$0S3X@@[?PIBSC%VZD8GU8\5G"3M/-G MW.Q-(D?XC1*D%4^(P/GE9JA"D"G'3UKQA`C<+"='EO^>"8N(D79F>+(#?"+% MHSYBTH;#.Q)KYO%VQD@[2RSB@%#PF(^8<2;1:#-/B"#MS+.(W;SKQ;*/F+1; M,(O>9IX00=IILXCGB&1RQWS$C/?R+.+-/"&"M/,(B]A#)"LN328F'3O,HJ>9 M)T20=AYE$7M9A'+ATO\#C"+ZFWE"!&GGZRSB^:[FLS=CM!GPR+V$;%MW4?,&%\YY%$%>$($W9W*1:_: MBGPF-XLD/Y%!DIN8T0-VA%[EKBX6\?A:!K$%3X@@[4QSL^I:(EKPA`C<)8== MZWLF0@1IYSB/5.'MY$,7I!5/B"#M/,G-7N,W=3;K(R:]RZ!:B68>GPA9B:YY M%O$*$1&J"&+&2<%-<@$"/"&"M#/'(@:%69[W$3/.VAGM;>8)$:2=-L!*)]S3PA@K0SRR)VL0@>0A"3[GC8BW@S3X@@[9QB$2/BXM-]Q(SQ M7I"S'N"QB![2SDD6\>+_MG-%NVT;0?#9_@JB?6A3%*WV*%D24+3]@OZ#8[N! M82<.Y.2AW],?[=W.'$G9]$:\#5HTV7L94B3G*'&]O+L=#W[.HYR=>J06!7(+^+"^3(S-^Z#+,R"&"R!XJ+5:5(H%B# MX@(4.[THX2+`9(\44BG0O:#[_!94BKU>U.,BP&2/%*E2H'M!]_EU7B#G]W+1 M&AM$%+@),]DBQ MJ13H7M!]C^>3\WNY:-O-`RDN*@6Z3^B^Q_/)^;VOF@13;2H'N$[KO\7QR M?B]G[[MY(,6.%(+N$[KO\7QR?B]?>]7-`RD*V3O$ZV(`Q;:0/>*3Q4"*&ITY ME==UAI.A^T,I:G3F5%[7&4X&4M3HS*F\KC.<#*2HT9E3>5TD.!E(4:,SI_*Z M>'0RD*)&9T[E=?'H9"!%C-T($7-G3F5UQ7!DP$4 MNYH[;Q:=3K@+W57HM.W?+S3<>?1(/G)$,4X1HH:G8*DF9`T>[Q5UMO)R_0Y MD&+(G4B:"4FSQUMEO9N\3)\#*4IT^J;]^Q*=!\SB%P,I=-S)4=U20%SL4S<. MPCBA.UJT__1#U36%`T9?BX$4-7>N]\N!%$/N7"T'4@RY4Y8#*8;=._Z/#51Z'#5R>%^"F2GZ+W M4ZS]%.YWNNCDRDFQ]5/XHU/\T9G\T9G\T9G\T9G\T9G\T9G\T9G\T9F[86@3N317@CJ1![MA:!.Y-%>".I$'NV%H$[D MT5X(ZD0>[86@3N317@CJ1![MA:!.Y-%>".I$'NV%:)W(I;T0K1.YM!>".I&A MK[!T&5J5$*T36?H*2Y=!BA*=EK["TF608MO9^@I+ET&*76?K*RQ=!BGVG:VO ML'09H-`ZD:6OL'09I)#.UE=8N@Q2I,[65UBZ#%+TG:VOL'09I-#H]&@O!'4B MC_9"M$[D6H01K1.YM!>B=2)+7V'I,OAS(CI?UE=8N@Q0:)W(TE=8N@Q2:'0: M^@I+ET$*C4Y#7V'I,DBAT6GH*RQ=!BG6G:VOL'09I-#<:>@K+%T&*31W&OH* M2Y=!BO)#6OH*2Y>!Z-0ZD4M[(5HGDR2*'1Z=%>B-:)7-H+V4U7XINT%Z)U(I?V0K1.Y-)>B-:) M7-H+T3J12WLA6B=R:2]DJ!,U:R]DJ!,U:R]D-RA`6K47HG4BI6C57LA^4("T M:B]D/RA`6K47&!LI1:OV0H8Z4;/V0H8Z4;/V0H8Z4;/V`G,IE_8"+S!?76*H M$S5K+])8)VK57J2Q3M2JO4A#G:A9>X$1&@MQ;=H+O,"4HE5[@=)6B57N!>27+@6W:"\PK60YLTUY@L8#EP#;M19(:G8,#KFO8GK1:YM!<)_U/DT5XD5(L\VHND MU2*7]B*EFCN;M1X'55M<8)_6]3WN1^K5/>Y'ZC4=[<7[]YG!Y MMEJMSLM"T%F>K)Y]7T(]9X]7W?=E4)UGCGFK//*<#O2S;9G'O3H_RV?F<6W^ M\RS'\S`KSZO*5AYQY[]Z/7-?IFLX,P]]TT;/S"^;/.O0,S/G1ME7A7/',\NG M:SUS6R87K_)-7MT>\KT)>LRS!?:8,VW9*MQI3>Z<.LL5'V[O]6N=7[^]O.+6 MZ\,-MZX?/G#KX]MZWO7MY9E<[/BM-JOG?6SDN(_'^TM>>[A]QZVKFVMN7;Y_ MJ,S#'3R\J9]=71ZP]5^;('S%S?;_N+E_^."V_VCR_]ANPO_CWVCA_Q'^'W-W M,?7_^&:ZPOA$@S)WC!13_X^_Y^[".$:*\/\8*<+_8Z3X:OP_4)3C6GOX?^"+ MA/]'^'],(/P_1@C_CQ&^&/^/3VI0Z/_!!=#?9TX[EKC4#Z%T(<74_^.[N;LP MCI'B<_E_0)5,MDKPO]CA/#_&"'\ M/T8(_X\1PO]CA/^5_X=+>P'_#]-"Q-!ED&+J_]&DO?A\_A\>[47X?X3_QVQT MAO]'^'^$_T?X?]R%_T?X?X3_1_A_A/_'"Q3A_Q'^'W?/M!?A_W$3_A_'0(KP M_PC_C_#_B!8M6K1HT:)%BQ8M6K1HT:)%BQ8M6K1HT:)%BQ8M6K1H_P"Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 8:38:49 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D8F5C37B401; Sun, 14 Jan 2001 08:38:32 -0800 (PST) Received: (from joe@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EGcWX51978; Sun, 14 Jan 2001 08:38:32 -0800 (PST) (envelope-from joe) Date: Sun, 14 Jan 2001 08:38:32 -0800 (PST) From: Message-Id: <200101141638.f0EGcWX51978@freefall.freebsd.org> To: davidx@viasoft.com.cn, joe@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/24321: cdcontrol default still using old device name cd0c Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: cdcontrol default still using old device name cd0c State-Changed-From-To: open->closed State-Changed-By: joe State-Changed-When: Sun Jan 14 08:36:45 PST 2001 State-Changed-Why: I've MFC'd revision 1.29. This adds support for the CDROM enviroment settings to override the default cd device. http://www.freebsd.org/cgi/query-pr.cgi?pr=24321 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 8:40:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1519C37B401 for ; Sun, 14 Jan 2001 08:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EGe2952128; Sun, 14 Jan 2001 08:40:02 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 08:40:02 -0800 (PST) Message-Id: <200101141640.f0EGe2952128@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Josef Karthauser Subject: Re: misc/24321: cdcontrol default still using old device name cd0c Reply-To: Josef Karthauser Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24321; it has been noted by GNATS. From: Josef Karthauser To: davidx@viasoft.com.cn Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/24321: cdcontrol default still using old device name cd0c Date: Sun, 14 Jan 2001 16:35:53 +0000 On Sun, Jan 14, 2001 at 12:41:41AM -0800, davidx@viasoft.com.cn wrote: > cdcontrol default is still using old device name cd0c while FreeBSD 4.x > is already using new ATAPI interface and default cdrom device name is > already changed to /dev/acd0c, cdcontrol is simply not follow-up. cd0c isn't an old name, it's the name of the SCSI cdrom device. I've just MFC'd a fix from -current which allows you to define the default device to use in the CDROM environment variable. After cvsup'ing you should be able to add something like the following to your startup scripts: export CDROM=acd0 Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 10: 4:18 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from uvika.dn.ua (unknown [195.184.223.26]) by hub.freebsd.org (Postfix) with ESMTP id 9B02437B401 for ; Sun, 14 Jan 2001 10:03:41 -0800 (PST) Received: from uvika.dn.ua (i-ris.donbass.com [195.184.222.22]) by uvika.dn.ua (8.11.1/8.11.1) with SMTP id f0EI31899837 for ; Sun, 14 Jan 2001 20:03:03 +0200 (EET) Message-Id: <200101141803.f0EI31899837@uvika.dn.ua> From: "Igor E. Segal" To: Subject: Momentary readout information Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sun, 14 Jan 2001 20:03:28 +0200 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sears! We are glad to propose You the unique opportunity of fundamental life changing with the consultation of Universe Informational Center. We suggest momentary readout information from any animate and inanimate object independently from time and distance. Diagnostics of everything alive, that exists on the Earth and in the Space. It's enough for you to name the living being and the age or the object of your interest, its number and what you'd like to find out about it. The exactness of answer depends on the exactness of an asked question. Everything occurs as in computer system. You formulate your question, briefly and exactly, and receive a brief and exact answer. SCIENCE, TECHNICS, ASTRONAUTICS We can diagnose any facilities, buildings, constructions, examine the lands for construction. We can analyse of expedience and prospects of developed scientific, military and state programs, scientific hypothesis and discoveries. Drawing conclusions about all future positive and negative qualities of an invention, including every detail of a future machine. If it is a vehicle for Mars or Venus - we'll describe its mode of work and its service life at this planet. We'll say beforehand what detail will go out of service and why, what is desirable to improve, to change and so on. At the same time we can already now describe not only what your vehicle will find there, but also what is really exists there: kind of vegetation, its color, growth, taste, smell, presence of water, minerals, forms of intellect, etc. We know the time of contact failure with any apparatus at any planet, we can find the reason and re-establish the contact. For military, navy, space and other subdivisions of state and united forces without departure to the location we can instantly look through the technical condition of any fighting unit, warship, spaceship of any country, professional training of any separate serviceman, an expedience of war actions and their final result, and we can give answers to other questions of interest. Complete examination of all military and civil planes, rockets, etc. As to their security and a state of wear at the whole territory of any country. Instant checking of service ability of all devices, reactors, control instruments and sensors at any sections independently of its distance and location. Prediction of the any spaceship launch result 3-4 days before the event. In case of unsuccessful launch we can locate the cause of a fault in a spaceship beforehand. It's possible to invent the machines of the far future (XXI, XXII c.) now. Several minutes it is enough to form future staff of designers, scientists, leaders - to choose the most talented of all students of high schools (in any branch). It's possible to talk to any archaeological finding, to go with it deep through decades, centuries, millennium, etc. An instant answer whether there is a virus in your computer. Answers to the questions of science: structure of the Universe, genesis of human and all animate, the secrets of microcosm, of gene structures and activity of human brain, search of new sources of energy, mysteries of time, etc. Examination of the Earth, the Sun, the Moon, any planet, etc. in section. Questions should be asked by specialists, the answers will be given instantly and at once to any question. PUBLIC HEALTH, ECOLOGY According to your wish we can examine the state of each organ separately: blond circulatory, nervous and other systems. Complete diagnostics of any person health during several minutes independently of distance and location. ( It's enough to point out name and age). We can analyze suitability of any medicine to a definite person, expedience of an impending operation and its reasons. If you are still going to be operated, I can prompt a favorable dale and hour for a perfect operation. ( It's enough to point out a doctor's name and place of operation). We can predict and examine the course of pregnancy, sex and growth of a baby, etc. For specialists - the medicine of future, the methods of struggle with cancer, viruses, ageing, vaccine against AIDS and other questions. Examination of territory and food as to their ecological safety. ECONOMICS, POLITICS Prediction of real chances of victory in pre-election and election campaigns of this or that candidate. Any member of government can instantly find out what is dune in other government establishments, their true attitude to governments and to the country in the whole. It is possible to find out what is done in any town of country, etc. In case you have to lead business meetings, you may know it beforehand how negotiations will go what can be expected from your partners, to financial state, the results of negotiations, future deals, credit rating of your partners and whether al all they have that what they offer you. You may know it beforehand whether your money or credit you are going to lend be returnable. (It is enough to name a debtor). If you hire a man for work, it is enough for you to name a position he is hired for and you may know all about his professional, business and human qualities, etc. For the leaders of all levels - all questions related their life and activity, including the questions of security. PRIVATE With our help you may talk to any relatives and acquaintances at any distance, find out their true attitude towards you, their thoughts, thoughts and attitude to you of your pets, trees and flowers in your garden, your cars - of all animate and inanimate objects. You may know what name is suitable for your child, what occupation your child is intended for, whether it is worth for him or her to marry (expedience of this or that marriage and its reasons). Your past (including your last lives), present and future. Your predestination and tasks in this life. The ways of solving problems. You'll get assistance in buying any immovable property. It is possible to examine quality of any selected wares, safety of your trips, flights and voyages. If you want to know about the weather in a day of your interest, it is enough for you to point out a day of week, month, year and You will get all necessary information. We have a favour to ask for You don`t ask the questions about non-existent objects and criminal or heated - playing features. Our work is being constructed at the base of agreement or contract. Please, ask You first three questions for free and, if You will satisfied by the results, we shell sign agreement about consultation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 11: 0:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2ED1337B401 for ; Sun, 14 Jan 2001 11:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EJ01s65268; Sun, 14 Jan 2001 11:00:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8725A37B400 for ; Sun, 14 Jan 2001 10:59:05 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EIx5j65197; Sun, 14 Jan 2001 10:59:05 -0800 (PST) (envelope-from nobody) Message-Id: <200101141859.f0EIx5j65197@freefall.freebsd.org> Date: Sun, 14 Jan 2001 10:59:05 -0800 (PST) From: mbretter@inode.at To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24325: Athlon Thunderbird 700 on Asus K7M vs. FreeBSD4.2 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24325 >Category: kern >Synopsis: Athlon Thunderbird 700 on Asus K7M vs. FreeBSD4.2 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 14 11:00:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Michael Bretterklieber >Release: 4.2 >Organization: JAWA Management und Software >Environment: FreeBSD worf.jawa.at 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Sun Dec 3 16:30:36 CET 2000 root@worf.jawa.at:/usr/src/sys/compile/WORF i386 >Description: I have problems with my Athlon Thunderbird 700 on an Asus K7M Motherboard (Bios 1009) and FreeBSD 4.2. The system is very very slow, like on an old 386. Keyboard clicks are delayed, it like I work over a slow network. I have this problems since I updatet from an Athlon 500 to this Athlon Thunderbird 700. I have on the same Harddisk Win98 and Win2K and they work without problems, fast and stable. After the installation of the new processor I made a BIOS-Upgrade to the latest version. Before I made the BIOS-upgrade, the system was slow, like on an PII 200 and unstable on all Win98, Win2k and FreeBSD. The BIOS has not recognized the CPU correctly ("AMD-(unknown)"). With 3DMark2000 it only reached about 600 points. After the BIOS-upgrade everything worked great on Win98 and Win2k, I reached 1771 points with 3DMark2000, but FreeBSD not worked correctly. This situation is disastrous for me, because I had to work under FreeBSD, so I hope, that somebody can help. kernel output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #1: Sat Dec 2 21:47:42 CET 2000 root@worf.jawa.at:/usr/src/sys/compile/WORF Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (704.94-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 134152192 (131008K bytes) config> q avail memory = 127262720 (124280K bytes) Preloaded elf kernel "kernel" at 0xc0354000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc035409c. 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 pci1: at 5.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 9 chip1: at device 4.4 on pci0 pcm0: port 0xd000-0xd003,0xd400-0xd4ff irq 10 at device 4.5 on pci0 bktr0: mem 0xeddfd000-0xeddfdfff irq 5 at device 14.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 bktr0: Card has no configuration EEPROM. Cannot determine card make. bktr0: Pinnacle/Miro TV, Temic NTSC tuner. pci0: (vendor=0x109e, dev=0x0878) at 14.1 irq 5 sym0: <810a> port 0xd800-0xd8ff mem 0xefffff00-0xefffffff irq 10 at device 15.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using LOAD/STORE-based firmware. de0: port 0xc800-0xc87f mem 0xeffffe80-0xeffffeff irq 9 at device 16.0 on pci0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:99:b5:bf 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,0x64 on isa0 atkbd0: flags 0x1 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 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 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/8 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 joy0 at port 0x201 on isa0 de0: enabling 10baseT port ad0: 29314MB [59560/16/63] at ata0-master UDMA66 ad2: 9641MB [19590/16/63] at ata1-master UDMA33 ad3: 6197MB [12592/16/63] at ata1-slave UDMA33 Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (probe5:sym0:0:5:0): phase change 6-7 6@07e2ef8c resid=4. Mounting root from ufs:/dev/ad0s3a cd0 at sym0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da0 at sym0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present uhci0: port 0xcc00-0xcc1f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 14:27:30 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3C18037B401 for ; Sun, 14 Jan 2001 14:27:09 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Jan 2001 22:27:08 +0000 (GMT) Date: Sun, 14 Jan 2001 22:27:07 +0000 From: David Malone To: opentrax@email.com Cc: olgeni@uli.it, bugs@FreeBSD.ORG Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section Message-ID: <20010114222707.A44872@walton.maths.tcd.ie> References: <200101140257.SAA00295@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101140257.SAA00295@spammie.svbug.com>; from opentrax@email.com on Sat, Jan 13, 2001 at 06:57:08PM -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jan 13, 2001 at 06:57:08PM -0800, opentrax@email.com wrote: Sorry - I closed this PR accidently. I was going to point out that inetd doesn't use /etc/protocols, because it does not have to translate protocol names to protocol numbers. The tokens "tcp", "udp", ... used in inetd.conf are parsed by inetd as it has no need to know any protocol numbers. If this seems OK, then I'll leave the PR closed. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 14:29:11 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2F83037B401; Sun, 14 Jan 2001 14:28:54 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EMSsa89239; Sun, 14 Jan 2001 14:28:54 -0800 (PST) (envelope-from dwmalone) Date: Sun, 14 Jan 2001 14:28:54 -0800 (PST) From: Message-Id: <200101142228.f0EMSsa89239@freefall.freebsd.org> To: imura@af.airnet.ne.jp, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/24228: when using /bin/sh, setting variable after pipeline won't work Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: when using /bin/sh, setting variable after pipeline won't work State-Changed-From-To: open->closed State-Changed-By: dwmalone State-Changed-When: Sun Jan 14 14:27:33 PST 2001 State-Changed-Why: Satisfactory explaination provided by Peter Pentchev. http://www.freebsd.org/cgi/query-pr.cgi?pr=24228 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 15:10:37 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 476EC37B402; Sun, 14 Jan 2001 15:10:21 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ENAEk99250; Sun, 14 Jan 2001 15:10:14 -0800 (PST) (envelope-from dwmalone) Date: Sun, 14 Jan 2001 15:10:14 -0800 (PST) From: Message-Id: <200101142310.f0ENAEk99250@freefall.freebsd.org> To: jgrosch@mooseriver.com, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: calendar.judaic will be incorrect on Jan. 1, 2001 State-Changed-From-To: feedback->closed State-Changed-By: dwmalone State-Changed-When: Sun Jan 14 15:08:55 PST 2001 State-Changed-Why: Updated calendar now in -current and -stable. I didn't merge to 3.x 'cos the calendar there seems to be already out of daye. http://www.freebsd.org/cgi/query-pr.cgi?pr=23456 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 18:40:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C339137B400 for ; Sun, 14 Jan 2001 18:40:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0F2e6w52001; Sun, 14 Jan 2001 18:40:06 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 18:40:06 -0800 (PST) Message-Id: <200101150240.f0F2e6w52001@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tor.Egge@fast.no Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Reply-To: Tor.Egge@fast.no Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15070; it has been noted by GNATS. From: Tor.Egge@fast.no To: freebsd-gnats-submit@FreeBSD.ORG Cc: Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Date: Mon, 15 Jan 2001 03:35:04 +0100 One workaround for the race is to serialize vfprintf() calls that use floating point conversion specifications. Index: stdio/vfprintf.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdio/vfprintf.c,v retrieving revision 1.23 diff -u -r1.23 vfprintf.c --- stdio/vfprintf.c 2001/01/06 20:48:00 1.23 +++ stdio/vfprintf.c 2001/01/06 23:15:45 @@ -261,6 +261,17 @@ #include #include "floatio.h" +/* + * Serialize calls to cvt and __dtoa() and the usage of the result + * in threaded programs. + */ + +#include "libc_private.h" +#include "spinlock.h" +static spinlock_t thread_lock = _SPINLOCK_INITIALIZER; +#define THREAD_LOCK() if (__isthreaded) _SPINLOCK(&thread_lock); +#define THREAD_UNLOCK() if (__isthreaded) _SPINUNLOCK(&thread_lock); + #define BUF (MAXEXP+MAXFRACT+1) /* + decimal point */ #define DEFPREC 6 @@ -271,6 +282,9 @@ #define BUF 68 +#define THREAD_LOCK() +#define THREAD_UNLOCK() + #endif /* FLOATING_POINT */ #define STATIC_ARG_TBL_SIZE 8 /* Size of static argument table. */ @@ -303,6 +317,7 @@ int width; /* width from format (%8d), or 0 */ int prec; /* precision from format (%.3d), or -1 */ char sign; /* sign prefix (' ', '+', '-', or \0) */ + int didlock; /* have obtained thread lock */ #ifdef FLOATING_POINT char softsign; /* temporary negative sign for floats */ double _double; /* double precision arguments %[eEfgG] */ @@ -418,6 +433,7 @@ } + didlock = 0; FLOCKFILE(fp); /* sorry, fprintf(read_only_file, "") returns EOF, not 0 */ if (cantwrite(fp)) { @@ -608,6 +624,8 @@ break; } flags |= FPT; + THREAD_LOCK(); + didlock = 1; cp = cvt(_double, prec, flags, &softsign, &expt, ch, &ndig); if (ch == 'g' || ch == 'G') { @@ -849,6 +867,10 @@ PRINT(cp, 1); PRINT(expstr, expsize); } + if (didlock != 0) { + THREAD_UNLOCK(); + didlock = 0; + } } #else PRINT(cp, size); @@ -865,6 +887,10 @@ done: FLUSH(); error: + if (didlock != 0) { + THREAD_UNLOCK(); + didlock = 0; + } if (__sferror(fp)) ret = EOF; FUNLOCKFILE(fp); Index: stdlib/strtod.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdlib/strtod.c,v retrieving revision 1.3 diff -u -r1.3 strtod.c --- stdlib/strtod.c 1996/07/12 18:55:22 1.3 +++ stdlib/strtod.c 2000/06/15 03:48:29 @@ -371,6 +371,16 @@ static Bigint *freelist[Kmax+1]; + /* + * Make Balloc/Bfree thread-safe in libc for use with + * kernel threads. + */ +#include "libc_private.h" +#include "spinlock.h" +static spinlock_t thread_lock = _SPINLOCK_INITIALIZER; +#define THREAD_LOCK() if (__isthreaded) _SPINLOCK(&thread_lock); +#define THREAD_UNLOCK() if (__isthreaded) _SPINUNLOCK(&thread_lock); + static Bigint * Balloc #ifdef KR_headers @@ -382,9 +392,12 @@ int x; Bigint *rv; + THREAD_LOCK(); if ( (rv = freelist[k]) ) { freelist[k] = rv->next; + THREAD_UNLOCK(); } else { + THREAD_UNLOCK(); x = 1 << k; rv = (Bigint *)malloc(sizeof(Bigint) + (x-1)*sizeof(long)); rv->k = k; @@ -403,8 +416,10 @@ #endif { if (v) { + THREAD_LOCK(); v->next = freelist[v->k]; freelist[v->k] = v; + THREAD_UNLOCK(); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 19:30:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 83ECB37B401 for ; Sun, 14 Jan 2001 19:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0F3U2k87704; Sun, 14 Jan 2001 19:30:02 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 19:30:02 -0800 (PST) Message-Id: <200101150330.f0F3U2k87704@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Wemm Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Reply-To: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15070; it has been noted by GNATS. From: Peter Wemm To: Tor.Egge@fast.no Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Date: Sun, 14 Jan 2001 19:26:04 -0800 Tor.Egge@fast.no wrote: > One workaround for the race is to serialize vfprintf() calls that use > floating point conversion specifications. Umm.. I wonder if this is the cause of the 'FreeBSD libc sprintf bug' that the MySQL folks see and mention on their web site? They use libc_r and see problems with sprintf... 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-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 19:50:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A4ED337B401 for ; Sun, 14 Jan 2001 19:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0F3o1F01687; Sun, 14 Jan 2001 19:50:01 -0800 (PST) (envelope-from gnats) Received: from DARTH.seed.net.tw (R57-69.seed.net.tw [139.175.57.69]) by hub.freebsd.org (Postfix) with ESMTP id 66F3937B400 for ; Sun, 14 Jan 2001 19:48:43 -0800 (PST) Received: (from security@localhost) by DARTH.seed.net.tw (8.11.1/8.11.1) id f0F3mgA12050; Mon, 15 Jan 2001 11:48:42 +0800 (CST) (envelope-from security) Message-Id: <200101150348.f0F3mgA12050@DARTH.seed.net.tw> Date: Mon, 15 Jan 2001 11:48:42 +0800 (CST) From: eddie@eagle.seed.net.tw Reply-To: eddie@eagle.seed.net.tw To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24334: random kernel panic Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24334 >Category: kern >Synopsis: random kernel panic >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 14 19:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Eddie Wang >Release: FreeBSD 4.2-STABLE i386 >Organization: Digital United Inc. >Environment: FreeBSD DARTH.seed.net.tw 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Jan 13 15:26:41 CST 2001 security@DARTH.seed.net.tw:/usr/src/sys/compile/DARTH i386 It was build base on CTM:src-4.0398 source tree. dmesg output: ----------------------- Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Sat Jan 13 15:26:41 CST 2001 security@DARTH.seed.net.tw:/usr/src/sys/compile/DARTH Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 651481206 Hz CPU: Pentium III/Pentium III Xeon/Celeron (651.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 268435456 (262144K bytes) avail memory = 258383872 (252328K bytes) Preloaded elf kernel "kernel" at 0xc02d0000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 chip1: port 0x5000-0x500f at device 7.3 on pci0 fxp0: port 0xe400-0xe43f mem 0xeb900000-0xeb9fffff,0xeba11000-0xeba11fff irq 10 at device 17.0 on pci0 fxp0: Ethernet address 00:d0:b7:db:9c:ce fxp1: port 0xe800-0xe83f mem 0xeb800000-0xeb8fffff,0xeba10000-0xeba10fff irq 11 at device 18.0 on pci0 fxp1: Ethernet address 00:d0:b7:90:11:66 pci0: at 19.0 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,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 DUMMYNET initialized (000608) IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 14594MB [29651/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ----------------------- >Description: A series of reboots occurred to this machine. Sometimes the machine reset automatically without kernel coredump left over, sometimes it just frose. We had changed a new computer and had changed ipfw to ipfilter, but it didn't work. This is one of those coredumps which was saved after authomatic reboot. It runs ipfw and natd as a firewall. ----------------------- DARTH:/var/crash# gdb -k kernel.4 vmcore.4 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD 3076096 initial pcb at 268340 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa5c01900 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015199c stack pointer = 0x10:0xc024b438 frame pointer = 0x10:0xc024b444 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 = Idle interrupt mask = net trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01cd5a0 stack pointer = 0x10:0xc024b268 frame pointer = 0x10:0xc024b26c 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 = Idle interrupt mask = net bio cam trap number = 12 panic: page fault Uptime: 1m24s dumping to dev #ad/0x20001, offset 691857 dump ata0: resetting devices .. done 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 4 2 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc01324d6 in dumpsys () (kgdb) bt #0 0xc01324d6 in dumpsys () #1 0xc01322f7 in boot () #2 0xc0132674 in poweroff_wait () #3 0xc0216f55 in trap_fatal () #4 0xc0216c2d in trap_pfault () #5 0xc0216813 in trap () #6 0xc01cd5a0 in acquire_lock () #7 0xc01d1354 in softdep_update_inodeblock () #8 0xc01cc87d in ffs_update () #9 0xc01d45e0 in ffs_sync () #10 0xc016045b in sync () #11 0xc01320ca in boot () #12 0xc0132674 in poweroff_wait () #13 0xc0216f55 in trap_fatal () #14 0xc0216c2d in trap_pfault () #15 0xc0216813 in trap () #16 0xc015199c in sbappendaddr () #17 0xc017c47d in divert_packet () #18 0xc0182e84 in ip_input () #19 0xc0182f3b in ipintr () (kgdb) ----------------------- kernel config file: ----------------------- machine i386 cpu I686_CPU ident DARTH maxusers 128 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # PCI Ethernet NICs. device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device vn pseudo-device snp 4 # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter 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 IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPSTEALTH #support for stealth forwarding options TCPDEBUG options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options TCP_RESTRICT_RST #restrict emission of TCP RST options DUMMYNET ----------------------- >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 19:55:51 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from nakk.co.jp (firewall.nakk.co.jp [210.81.84.122]) by hub.freebsd.org (Postfix) with ESMTP id 1623637B400 for ; Sun, 14 Jan 2001 19:55:34 -0800 (PST) Received: from tk-ws1.nakk.co.jp (fwqfe1 [210.81.84.97]) by nakk.co.jp (8.9.3/8.9.3) with SMTP id MAA21340 for ; Mon, 15 Jan 2001 12:55:25 +0900 (JST) Received: FROM tk-exchange1.nakk.co.jp BY tk-ws1.nakk.co.jp ; Mon Jan 15 12:55:25 2001 +0900 Received: by TK-EXCHANGE1 with Internet Mail Service (5.5.2650.21) id ; Mon, 15 Jan 2001 12:55:25 +0900 Message-ID: From: "Matsuura, Ichiro" To: "'freebsd-bugs@freebsd.org'" Subject: Date: Mon, 15 Jan 2001 12:55:24 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="ISO-2022-JP" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org unsubscribe imatsuura@nai.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 20: 0:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EC47037B400 for ; Sun, 14 Jan 2001 20:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0F402c10633; Sun, 14 Jan 2001 20:00:02 -0800 (PST) (envelope-from gnats) Date: Sun, 14 Jan 2001 20:00:02 -0800 (PST) Message-Id: <200101150400.f0F402c10633@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tor.Egge@fast.no Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Reply-To: Tor.Egge@fast.no Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15070; it has been noted by GNATS. From: Tor.Egge@fast.no To: peter@netplex.com.au Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Date: Mon, 15 Jan 2001 04:51:54 +0100 > Umm.. I wonder if this is the cause of the 'FreeBSD libc sprintf bug' > that the MySQL folks see and mention on their web site? They use libc_r > and see problems with sprintf... Yes. The stack trace shown by gdb on the mysql mailing list is very similar to that generated by the sample program in this PR. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sun Jan 14 21:10:18 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3D96337B698 for ; Sun, 14 Jan 2001 21:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0F5A1o70904; Sun, 14 Jan 2001 21:10:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CD84237B401 for ; Sun, 14 Jan 2001 21:04:16 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0F54GA64551; Sun, 14 Jan 2001 21:04:16 -0800 (PST) (envelope-from nobody) Message-Id: <200101150504.f0F54GA64551@freefall.freebsd.org> Date: Sun, 14 Jan 2001 21:04:16 -0800 (PST) From: sven@devcon.net To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24335: Crash when returning from single user mode. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24335 >Category: kern >Synopsis: Crash when returning from single user mode. >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 14 21:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Sven Klose >Release: Freebsd-CURRENT >Organization: dev/consulting GmbH >Environment: FreeBSD copei.research.devcon.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jan 15 06:15:56 CET 2001 sven@copei.research.devcon.net:/usr/src/sys/compile/COPEI i386 >Description: When I put my machine into single user mode and then return into multi user mode the systems starts up as expected but crashes as soon as the login appears. A debugging kernel doesn't help. >How-To-Repeat: Do the same I did. >Fix: Looks to me like the pcvt terminal doesn't like come up again. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 0: 2:40 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id F29A537B400 for ; Mon, 15 Jan 2001 00:02:20 -0800 (PST) Received: (qmail 1775 invoked by uid 1000); 15 Jan 2001 08:00:57 -0000 Date: Mon, 15 Jan 2001 10:00:57 +0200 From: Peter Pentchev To: Josef Karthauser Cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/24321: cdcontrol default still using old device name cd0c Message-ID: <20010115100057.A1294@ringworld.oblivion.bg> Mail-Followup-To: Josef Karthauser , freebsd-bugs@FreeBSD.org References: <200101141640.f0EGe2952128@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101141640.f0EGe2952128@freefall.freebsd.org>; from joe@tao.org.uk on Sun, Jan 14, 2001 at 08:40:02AM -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jan 14, 2001 at 08:40:02AM -0800, Josef Karthauser wrote: > The following reply was made to PR misc/24321; it has been noted by GNATS. > > From: Josef Karthauser > To: davidx@viasoft.com.cn > Cc: freebsd-gnats-submit@FreeBSD.org > Subject: Re: misc/24321: cdcontrol default still using old device name cd0c > Date: Sun, 14 Jan 2001 16:35:53 +0000 > > On Sun, Jan 14, 2001 at 12:41:41AM -0800, davidx@viasoft.com.cn wrote: > > > cdcontrol default is still using old device name cd0c while FreeBSD 4.x > > is already using new ATAPI interface and default cdrom device name is > > already changed to /dev/acd0c, cdcontrol is simply not follow-up. > > cd0c isn't an old name, it's the name of the SCSI cdrom device. > I've just MFC'd a fix from -current which allows you to define the > default device to use in the CDROM environment variable. > > After cvsup'ing you should be able to add something like the following > to your startup scripts: > > export CDROM=acd0 Mmm.. am I missing something here? I thought cdcontrol(1) already checked four other environment variables - MUSIC_CD, CD_DRIVE, DISC and CDPLAY - and set the cdname variable appropriately before checking for -f? So the -f flag would override the environment default, and *both* the env vars and the -f flag would override the /dev/cd0c hardwired default? The checks are before the getopt() call, you have just added another one after the call.. is there a reason that those be separated? I personally have been setting MUSIC_CD in my profiles since forever, and it has worked perfectly well. And the manpage documented the old behavior too, near the top; true, it did not have an ENVIRONMENT section, but.. :) G'luck, Peter -- No language can express every thought unambiguously, least of all this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 0:19:17 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A05937B401 for ; Mon, 15 Jan 2001 00:18:54 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id AAA02492; Mon, 15 Jan 2001 00:17:03 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101150817.AAA02492@spammie.svbug.com> Date: Mon, 15 Jan 2001 00:17:00 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section To: dwmalone@maths.tcd.ie Cc: olgeni@uli.it, bugs@FreeBSD.ORG In-Reply-To: <20010114222707.A44872@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14 Jan, David Malone wrote: > On Sat, Jan 13, 2001 at 06:57:08PM -0800, opentrax@email.com wrote: > > Sorry - I closed this PR accidently. I was going to point out that > inetd doesn't use /etc/protocols, because it does not have to > translate protocol names to protocol numbers. The tokens "tcp", > "udp", ... used in inetd.conf are parsed by inetd as it has no > need to know any protocol numbers. > > If this seems OK, then I'll leave the PR closed. > Can I get a commit on the documentation? Even if is has no real use for inetd(8), it should be documented becuase it's mentioned. This provides consistent style. Commit and close would be the appropriate action. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 0:19:37 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 0A8D437B400; Mon, 15 Jan 2001 00:19:20 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id AAA02496; Mon, 15 Jan 2001 00:19:14 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101150819.AAA02496@spammie.svbug.com> Date: Mon, 15 Jan 2001 00:19:13 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 To: dwmalone@FreeBSD.ORG Cc: jgrosch@mooseriver.com, freebsd-bugs@FreeBSD.ORG In-Reply-To: <200101142310.f0ENAEk99250@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14 Jan, dwmalone@FreeBSD.ORG wrote: > Synopsis: calendar.judaic will be incorrect on Jan. 1, 2001 > > State-Changed-From-To: feedback->closed > State-Changed-By: dwmalone > State-Changed-When: Sun Jan 14 15:08:55 PST 2001 > State-Changed-Why: > Updated calendar now in -current and -stable. I didn't merge to 3.x > 'cos the calendar there seems to be already out of daye. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=23456 > > Can we get a merge to 3.x? Or was this a date sensitive bug? Some of us are still running 3.x. Also, if it is date sensitive, Can it be commented so? Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 0:32:22 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 0D07437B401; Mon, 15 Jan 2001 00:32:02 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id AAA02517; Mon, 15 Jan 2001 00:31:57 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101150831.AAA02517@spammie.svbug.com> Date: Mon, 15 Jan 2001 00:31:56 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: [Q] Transient Core Dumps To: bugs@freebsd.org Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a quick question. Tonight our DNS server dropped core after several other program misbehaved. Chief amoung then was one of our own. The problems thought seems to be more than one misbehaving programs. Along with DNS the machines runs, LiveCam, our video over the internet solution, NCSA webserver (part of LiveCam), Apache (port 8080) and Mason. The machine went into a spin when LiveCam swamped the swap space, then some tried to send email via Apache/mason. Eventually, named also dumped core. The machine is reset. I've turned off direct access to Apache/Mason. The machines is now fine. Granted one (very buggy) part of our LiveCam has problems, but along with Mason, it seems that the problems are hard to trace. The question is: How do we diagnos (sp?) random core dumps? I've seen quite a few go by in last days. And up till now we usually ask for a dmesg and one other thing. Any comments? Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 0:53:29 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id BBE1337B400 for ; Mon, 15 Jan 2001 00:53:08 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0F8r4Q01821; Mon, 15 Jan 2001 00:53:04 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101150853.f0F8r4Q01821@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: opentrax@email.com Cc: dwmalone@maths.tcd.ie, bugs@FreeBSD.ORG Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section In-Reply-To: <200101150817.AAA02492@spammie.svbug.com> Date: Mon, 15 Jan 2001 00:53:04 -0800 From: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org opentrax@email.com wrote: > > > On 14 Jan, David Malone wrote: > > On Sat, Jan 13, 2001 at 06:57:08PM -0800, opentrax@email.com wrote: > > > > Sorry - I closed this PR accidently. I was going to point out that > > inetd doesn't use /etc/protocols, because it does not have to > > translate protocol names to protocol numbers. The tokens "tcp", > > "udp", ... used in inetd.conf are parsed by inetd as it has no > > need to know any protocol numbers. > > > > If this seems OK, then I'll leave the PR closed. > > > Can I get a commit on the documentation? > Even if is has no real use for inetd(8), it should > be documented becuase it's mentioned. > This provides consistent style. > > Commit and close would be the appropriate action. There is no need. There is no point adding a '/etc/protocols' to the FILES list since inetd does not use the '/etc/protocols' file. At best it would be misinformation. 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-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 1:11:21 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id C8FB637B402 for ; Mon, 15 Jan 2001 01:11:02 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id BAA02569; Mon, 15 Jan 2001 01:09:30 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101150909.BAA02569@spammie.svbug.com> Date: Mon, 15 Jan 2001 01:09:27 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section To: peter@netplex.com.au Cc: dwmalone@maths.tcd.ie, bugs@FreeBSD.ORG In-Reply-To: <200101150853.f0F8r4Q01821@mobile.wemm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, Peter Wemm wrote: > opentrax@email.com wrote: >> >> >> On 14 Jan, David Malone wrote: >> > On Sat, Jan 13, 2001 at 06:57:08PM -0800, opentrax@email.com wrote: >> > >> > Sorry - I closed this PR accidently. I was going to point out that >> > inetd doesn't use /etc/protocols, because it does not have to >> > translate protocol names to protocol numbers. The tokens "tcp", >> > "udp", ... used in inetd.conf are parsed by inetd as it has no >> > need to know any protocol numbers. >> > >> > If this seems OK, then I'll leave the PR closed. >> > >> Can I get a commit on the documentation? >> Even if is has no real use for inetd(8), it should >> be documented becuase it's mentioned. >> This provides consistent style. >> >> Commit and close would be the appropriate action. > > There is no need. There is no point adding a '/etc/protocols' to the FILES > list since inetd does not use the '/etc/protocols' file. At best it would > be misinformation. > Wait. How is this misinformation? I must be missing something. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 1:13:51 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 12F3837B401 for ; Mon, 15 Jan 2001 01:13:33 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id 9B03B2B309; Mon, 15 Jan 2001 03:13:32 -0600 (CST) Date: Mon, 15 Jan 2001 03:13:32 -0600 From: Bill Fumerola To: opentrax@email.com Cc: peter@netplex.com.au, dwmalone@maths.tcd.ie, bugs@FreeBSD.ORG Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section Message-ID: <20010115031332.A61857@elvis.mu.org> References: <200101150853.f0F8r4Q01821@mobile.wemm.org> <200101150909.BAA02569@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101150909.BAA02569@spammie.svbug.com>; from opentrax@email.com on Mon, Jan 15, 2001 at 01:09:27AM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 15, 2001 at 01:09:27AM -0800, opentrax@email.com wrote: > > There is no need. There is no point adding a '/etc/protocols' to the FILES > > list since inetd does not use the '/etc/protocols' file. At best it would > > be misinformation. > > > Wait. How is this misinformation? I must be missing something. Because /etc/protocols doesn't have to exist, could be wrong, etc and it doesn't make a difference to inetd, because it _does not use it_. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:10:18 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 56FF137B698 for ; Mon, 15 Jan 2001 02:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FAA1t42163; Mon, 15 Jan 2001 02:10:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 13F5B37B400 for ; Mon, 15 Jan 2001 02:03:39 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FA3dl39380; Mon, 15 Jan 2001 02:03:39 -0800 (PST) (envelope-from nobody) Message-Id: <200101151003.f0FA3dl39380@freefall.freebsd.org> Date: Mon, 15 Jan 2001 02:03:39 -0800 (PST) From: kazarov@izmiran.rssi.ru To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: bin/24341: Another device for /usr/src/sys/devs/usb/usbdevs: ZyXEL Omni 56K Plus Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24341 >Category: bin >Synopsis: Another device for /usr/src/sys/devs/usb/usbdevs: ZyXEL Omni 56K Plus >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 02:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Dmitry Kazarov >Release: FreeBSD-4.2-STABLE >Organization: IZMIRAN >Environment: >Description: I've got a ZyXEL Omni 56K Plus. It's could be added to usbdevs. >How-To-Repeat: >Fix: *** usbdevs.orig Tue Jan 9 18:18:00 2001 --- usbdevs Tue Jan 9 18:19:23 2001 *************** product ZOOM 2986L 0x9700 2986L Fax mod *** 819,821 **** --- 819,822 ---- /* ZyXEL Communication Co. products */ product ZYXEL 980N 0x2011 Scorpion-980N keyboard + product ZYXEL OMNI56K 0x1500 Omni 56K Plus >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:24:46 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D591237B400 for ; Mon, 15 Jan 2001 02:24:28 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Jan 2001 10:24:28 +0000 (GMT) To: opentrax@email.com Cc: jgrosch@mooseriver.com, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 In-reply-to: Your message of "Mon, 15 Jan 2001 00:19:13 PST." <200101150819.AAA02496@spammie.svbug.com> X-Request-Do: Date: Mon, 15 Jan 2001 10:24:26 +0000 From: David Malone Message-ID: <200101151024.aa69276@salmon.maths.tcd.ie> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can we get a merge to 3.x? Or was this a date sensitive > bug? Some of us are still running 3.x. > Also, if it is date sensitive, Can it be commented so? The calendar in 3.X is the Judaic calendar for 1999, and no one noticed the whole way through 2000. I'll merge the new one shortly, all the same. I just noticed a problem with the one I committed earlier. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:27:17 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id AA2E437B400; Mon, 15 Jan 2001 02:26:57 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id CAA02883; Mon, 15 Jan 2001 02:24:01 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151024.CAA02883@spammie.svbug.com> Date: Mon, 15 Jan 2001 02:23:59 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section To: billf@mu.org Cc: peter@netplex.com.au, dwmalone@maths.tcd.ie, bugs@FreeBSD.ORG, doc@FreeBSD.ORG In-Reply-To: <20010115031332.A61857@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, Bill Fumerola wrote: > On Mon, Jan 15, 2001 at 01:09:27AM -0800, opentrax@email.com wrote: >> > There is no need. There is no point adding a '/etc/protocols' to the FILES >> > list since inetd does not use the '/etc/protocols' file. At best it would >> > be misinformation. >> > >> Wait. How is this misinformation? I must be missing something. > > Because /etc/protocols doesn't have to exist, could be wrong, etc and it doesn't > make a difference to inetd, because it _does not use it_. > Yes, I got that part. I'm sorry I was not clear. The question then should be: if what you are saying is correct, then the man page is wrong and we should remove or correct the part about /etc/protocols. The man page clearly says: "The protocol must be a valid protocol as given in /etc/protocols." As a matter of fact, the man page for 4.2 say so also. Now being even more annoying, decided to check the code. "$FreeBSD: /c/ncvs/src/usr.sbin/inetd/inetd.c,v 1.80.2.2 2000/10/24 19:18:29 dwmalone Exp $"; Comments in the code says: protocol must be in /etc/protocols Granted, I don't see where it is used, but I don't see where /etc/services is used either. If you are correct, then the man pages still needs a correction. In either case, I need to know what to put. Your assitance appreciated. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:40:17 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id CB71437B401 for ; Mon, 15 Jan 2001 02:39:58 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id CAA02905; Mon, 15 Jan 2001 02:38:48 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151038.CAA02905@spammie.svbug.com> Date: Mon, 15 Jan 2001 02:38:46 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 To: dwmalone@maths.tcd.ie Cc: jgrosch@mooseriver.com, freebsd-bugs@FreeBSD.ORG In-Reply-To: <200101151024.aa69276@salmon.maths.tcd.ie> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, David Malone wrote: >> Can we get a merge to 3.x? Or was this a date sensitive >> bug? Some of us are still running 3.x. >> Also, if it is date sensitive, Can it be commented so? > > The calendar in 3.X is the Judaic calendar for 1999, and no one > noticed the whole way through 2000. I'll merge the new one shortly, > all the same. I just noticed a problem with the one I committed > earlier. > Sorry, I'm not clear. Are you saying this bug does or does NOT affect machines in the field? Our company has many machines in the field; many running 3.4. If this effects any running 3.x machines, then a patch would allow use to fix without having to guess where it goes. :-) Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:46:38 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C16B137B404; Mon, 15 Jan 2001 02:46:17 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Jan 2001 10:46:16 +0000 (GMT) To: opentrax@email.com Cc: billf@mu.org, peter@netplex.com.au, dwmalone@maths.tcd.ie, bugs@FreeBSD.ORG, doc@FreeBSD.ORG, dwmalone@maths.tcd.ie Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section In-reply-to: Your message of "Mon, 15 Jan 2001 02:23:59 PST." <200101151024.CAA02883@spammie.svbug.com> X-Request-Do: Date: Mon, 15 Jan 2001 10:46:16 +0000 From: David Malone Message-ID: <200101151046.aa71577@salmon.maths.tcd.ie> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > is correct, then the man page is wrong and we should > remove or correct the part about /etc/protocols. > The man page clearly says: > "The protocol must be a valid protocol as given in /etc/protocols." Good point - I'll check the man page and comments and remove it if incorrect. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:52:43 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4E12E37B401 for ; Mon, 15 Jan 2001 02:52:20 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Jan 2001 10:52:19 +0000 (GMT) To: opentrax@email.com Cc: jgrosch@mooseriver.com, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 In-reply-to: Your message of "Mon, 15 Jan 2001 02:38:46 PST." <200101151038.CAA02905@spammie.svbug.com> X-Request-Do: Date: Mon, 15 Jan 2001 10:52:19 +0000 From: David Malone Message-ID: <200101151052.aa72616@salmon.maths.tcd.ie> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Sorry, I'm not clear. > Are you saying this bug does or does NOT affect machines in the field? It does - if you type: calendar -f /usr/src/usr.bin/calendar/calendars/calendar.judaic you get the Judaic calendar for 1999. No one has noticed, so I presume no one is using it. > Our company has many machines in the field; many running 3.4. > If this effects any running 3.x machines, then a patch would allow > use to fix without having to guess where it goes. :-) As I say, I'll import the patch in a day or two. If the 3.X people have survived all of they year 2000 with a incorrect Juadic calendar then I'm sure they'll survive a little longer ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 2:59:53 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mooseriver.com (erie.mooseriver.com [205.166.121.26]) by hub.freebsd.org (Postfix) with ESMTP id 6011937B402 for ; Mon, 15 Jan 2001 02:59:36 -0800 (PST) Received: (from jgrosch@localhost) by mooseriver.com (8.11.1/8.9.3) id f0FAxME93260; Mon, 15 Jan 2001 02:59:22 -0800 (PST) (envelope-from jgrosch) Date: Mon, 15 Jan 2001 02:59:22 -0800 From: Josef Grosch To: opentrax@email.com Cc: dwmalone@maths.tcd.ie, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 Message-ID: <20010115025922.A93176@mooseriver.com> Reply-To: jgrosch@mooseriver.com References: <200101151024.aa69276@salmon.maths.tcd.ie> <200101151038.CAA02905@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200101151038.CAA02905@spammie.svbug.com>; from opentrax@email.com on Mon, Jan 15, 2001 at 02:38:46AM -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 15, 2001 at 02:38:46AM -0800, opentrax@email.com wrote: > > > On 15 Jan, David Malone wrote: > >> Can we get a merge to 3.x? Or was this a date sensitive > >> bug? Some of us are still running 3.x. > >> Also, if it is date sensitive, Can it be commented so? > > > > The calendar in 3.X is the Judaic calendar for 1999, and no one > > noticed the whole way through 2000. I'll merge the new one shortly, > > all the same. I just noticed a problem with the one I committed > > earlier. > > > Sorry, I'm not clear. > Are you saying this bug does or does NOT affect machines in the field? > Our company has many machines in the field; many running 3.4. > If this effects any running 3.x machines, then a patch would allow > use to fix without having to guess where it goes. :-) OK, Please go to my anonymous ftp site (mooseriver.com). In /pub/FreeBSD/Calendar You will find calander.judaic.README and calendar.judaic.tgz. Within calendar.judaic.tgz you will find 2 files calendar.judaic and calendar.judaic.diff. Ignore The file calendar.judaic.diff. calendar.judaic is the complete calendar for the CE year 2001. This file is a drop in replacement for the existing calendar.judaic which can be found in /usr/src/usr.bin/calendar/calendars. This file should work for 3.X and 4.X. As I don't run a 5.x box I can't be sure but it should work unless calendar has changed between 4.x and 5.x. Please let me know if you have any questions. Josef -- Josef Grosch | Another day closer to a | FreeBSD 4.2 jgrosch@MooseRiver.com | Micro$oft free world | www.bafug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 3:27:47 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from sina.com (unknown [202.106.187.156]) by hub.freebsd.org (Postfix) with SMTP id B6AF637B69D for ; Mon, 15 Jan 2001 03:27:08 -0800 (PST) Received: (qmail 41269 invoked from network); 15 Jan 2001 11:21:32 -0000 Received: from unknown (HELO localhost) (202.105.12.29) by 202.106.187.156 with SMTP; 15 Jan 2001 11:21:32 -0000 X-Sender: hangersales@sina.com From: Trend Hanger To: freebsd-bugs@FreeBSD.ORG Date: Mon, 15 Jan 2001 19:25:57 +0800 Subject: We are exporting quality Hanger for cloth, pants Reply-To: hangersales@sina.com Organization: Trend Hanger Co. MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20010115112708.B6AF637B69D@hub.freebsd.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sir or Madam, Happy New Year! Here we send all the best wish to you. Trend Hanger, as a professional hanger manufacturer in China specializes in producing and designing various kinds of non-slip coated and chrome-plated metal frame clothes hangers. The company has been in the business for almost 10 years now. With experienced staff and workers, we always provide our customers from all over the world with good service, excellent quality and competitively-priced products. Today, people care a lot about environmental protection, and more and more people would choose to use low-waste materials, impressive and well-designed products. We are proud to say ours are among them. For this reason, during the past several years our selling records are quite well, and now the business is growing even faster than before--simply because our series of products are proven to be reliable and worthwhile in our consumers' eyes. Furthermore, we always observe a strict quality control system all throughout our production process. Each product must be carefully examined and tested in each stage so as to ensure excellent quality and nice packing order for our customers. If you are interested in our products, please do not hesitate to contact us. We are anxious to establish long-term, equal and mutual beneficial business relationship with you. Best wishes, Trend Hanger Manufacturer Contact Person: Mr Steve, Phoenix Sales Manager Zhen An Industrial Zone, Foshan City, Guangdong Province, China 528000 Tel: (86 757) 3982666 Fax: (86 757) 2282667 Email: brianced@21cn.com http://www.bosunnet.com/trendhanger/index/contacts.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 3:34: 5 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 817D537B400 for ; Mon, 15 Jan 2001 03:33:47 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id DAA02985; Mon, 15 Jan 2001 03:32:33 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151132.DAA02985@spammie.svbug.com> Date: Mon, 15 Jan 2001 03:32:32 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 To: dwmalone@maths.tcd.ie Cc: jgrosch@mooseriver.com, freebsd-bugs@FreeBSD.ORG In-Reply-To: <200101151052.aa72616@salmon.maths.tcd.ie> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, David Malone wrote: >> Sorry, I'm not clear. >> Are you saying this bug does or does NOT affect machines in the field? > > It does - if you type: > > calendar -f /usr/src/usr.bin/calendar/calendars/calendar.judaic > > you get the Judaic calendar for 1999. No one has noticed, so I > presume no one is using it. > >> Our company has many machines in the field; many running 3.4. >> If this effects any running 3.x machines, then a patch would allow >> use to fix without having to guess where it goes. :-) > > As I say, I'll import the patch in a day or two. If the 3.X people > have survived all of they year 2000 with a incorrect Juadic calendar > then I'm sure they'll survive a little longer ;-) > Okay, I guess, you are saying you'll add it into 3.x. I'm sorry if I seem dense. perhaps it's the 9 hours of reading mailng lists. ;+) BTW, if someone can email me on this Judaic calendar, I'd apprecite it. I have no idea what it is. Thanks again, Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 3:36:36 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F3C137B400 for ; Mon, 15 Jan 2001 03:36:19 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id DAA02992; Mon, 15 Jan 2001 03:35:09 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151135.DAA02992@spammie.svbug.com> Date: Mon, 15 Jan 2001 03:35:08 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 To: jgrosch@mooseriver.com Cc: dwmalone@maths.tcd.ie, freebsd-bugs@FreeBSD.ORG In-Reply-To: <20010115025922.A93176@mooseriver.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, Josef Grosch wrote: > On Mon, Jan 15, 2001 at 02:38:46AM -0800, opentrax@email.com wrote: >> On 15 Jan, David Malone wrote: >> >> Can we get a merge to 3.x? Or was this a date sensitive >>...[Trimmed]... > calendar has changed between 4.x and 5.x. > > Please let me know if you have any questions. > Thanks, I'll check it out. jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 3:37:56 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id B75B537B401; Mon, 15 Jan 2001 03:37:37 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id DAA02996; Mon, 15 Jan 2001 03:36:14 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151136.DAA02996@spammie.svbug.com> Date: Mon, 15 Jan 2001 03:36:13 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: docs/24307: man page for inetd(8) missing /etc/protocols in FIL ES section To: dwmalone@maths.tcd.ie Cc: billf@mu.org, peter@netplex.com.au, bugs@FreeBSD.ORG, doc@FreeBSD.ORG In-Reply-To: <200101151046.aa71577@salmon.maths.tcd.ie> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks David. Jessem. On 15 Jan, David Malone wrote: >> is correct, then the man page is wrong and we should >> remove or correct the part about /etc/protocols. >> The man page clearly says: > >> "The protocol must be a valid protocol as given in /etc/protocols." > > Good point - I'll check the man page and comments and remove it if > incorrect. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 3:39:41 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 463F537B404 for ; Mon, 15 Jan 2001 03:39:23 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0FBdHY02283; Mon, 15 Jan 2001 03:39:17 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101151139.f0FBdHY02283@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: opentrax@email.com Cc: dwmalone@maths.tcd.ie, jgrosch@mooseriver.com, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 In-Reply-To: <200101151132.DAA02985@spammie.svbug.com> Date: Mon, 15 Jan 2001 03:39:17 -0800 From: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org opentrax@email.com wrote: > > > On 15 Jan, David Malone wrote: > >> Sorry, I'm not clear. > >> Are you saying this bug does or does NOT affect machines in the field? > > > > It does - if you type: > > > > calendar -f /usr/src/usr.bin/calendar/calendars/calendar.judaic > > > > you get the Judaic calendar for 1999. No one has noticed, so I > > presume no one is using it. > > > >> Our company has many machines in the field; many running 3.4. > >> If this effects any running 3.x machines, then a patch would allow > >> use to fix without having to guess where it goes. :-) > > > > As I say, I'll import the patch in a day or two. If the 3.X people > > have survived all of they year 2000 with a incorrect Juadic calendar > > then I'm sure they'll survive a little longer ;-) > > > Okay, I guess, you are saying you'll add it into 3.x. > I'm sorry if I seem dense. perhaps it's the 9 hours > of reading mailng lists. ;+) > > BTW, if someone can email me on this Judaic calendar, I'd > apprecite it. I have no idea what it is. ARGH!! If you dont use it, and have no idea what it is, then why this endless thread about it?? -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 3:41: 8 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 7774337B401 for ; Mon, 15 Jan 2001 03:40:50 -0800 (PST) Received: by ada.eu.org (Postfix, from userid 10) id BCACD1909B; Mon, 15 Jan 2001 12:40:39 +0100 (CET) Received: by trillian.rfc1149.net (Postfix, from userid 1000) id 0CDEEBB2F; Mon, 15 Jan 2001 12:14:48 +0100 (CET) Date: Mon, 15 Jan 2001 12:14:47 +0100 To: Garrett Wollman Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/24271: dumpon should check its argument more References: <200101121610.f0CGA7a52473@freefall.freebsd.org> <20010113095245.A66238@wantadilla.lemis.com> <20010113004100.A12683@walton.maths.tcd.ie> <2001-01-13-13-41-54+trackit+sam@inf.enst.fr> <200101131418.JAA75138@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101131418.JAA75138@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Sat, Jan 13, 2001 at 09:18:20AM -0500 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.rfc1149.net/sam X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 X-Sam-Laptop: yes Message-Id: <2001-01-15-12-14-48+trackit+sam@inf.enst.fr> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13/01, Garrett Wollman wrote: | This patch introduces at least eleven new style bugs. I'm not a commiter, and doesn't even know what you are talking about (new style?). Do you have a pointer onto this "new style"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 5:10:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 071B437B69E for ; Mon, 15 Jan 2001 05:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FDA1371076; Mon, 15 Jan 2001 05:10:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 73EFC37B699 for ; Mon, 15 Jan 2001 05:08:57 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FD8v470958; Mon, 15 Jan 2001 05:08:57 -0800 (PST) (envelope-from nobody) Message-Id: <200101151308.f0FD8v470958@freefall.freebsd.org> Date: Mon, 15 Jan 2001 05:08:57 -0800 (PST) From: fishkin@port.ru To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24345: pthread library libc_r causes memory leak at termination of joinable thread Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24345 >Category: misc >Synopsis: pthread library libc_r causes memory leak at termination of joinable thread >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 05:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Andy Fedotov >Release: 3.5-STABLE, 4.1-STABLE >Organization: Port.RU, Inc. >Environment: FreeBSD xxxxxx.xxx.xxxx.xx 3.5-STABLE FreeBSD 3.5-STABLE #0: Tue Jan 9 13:49:27 MSK 2001 root@xxxxxx.xxx.xxxx.xx:/usr/src/sys/compile/HELL i386 FreeBSD xxx.xxxxx 4.1-STABLE FreeBSD 4.1-STABLE #3: Thu Nov 30 21:00:56 MSK 2000 root@xxx.xxxxx:/usr/src/sys/compile/MAC i386 >Description: Garbage collector looks into list of dead threads and freeing resources only for threads with PTHREAD_DETACHED flag. Unfortunattely pthread_join() doesn't set PTHREAD_DETACHED flag on thread after fetching it return value. So, garbage collector leave this thread in dead list and won't free() any resources associated with it. This causes memory leak. >How-To-Repeat: Simply start thread in joinable state, and then join on it. ------ #ifndef _THREAD_SAFE #define _THREAD_SAFE #endif #ifndef _REENTRANT #define _REENTRANT #endif #include #include #include #include #include unsigned long brk_value = 0; void *check_leak(void *arg) { unsigned long current_brk = (unsigned long) sbrk(0); if (current_brk > brk_value) if (brk_value != 0) fprintf(stdout, "Data segment grows up by 0x%lX bytes\n", current_brk - brk_value); brk_value = current_brk; pthread_exit(NULL); } int main() { pthread_t tid; pthread_attr_t attr; pthread_attr_init(&attr); pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_JOINABLE); for (;;) { if (pthread_create(&tid, &attr, check_leak, NULL)) { perror("pthread_create"); exit(0); } else pthread_join(tid, NULL); } } ----- >Fix: Should we simply set PTHREAD_DETACHED flag after sucessfuly joining on thread ? But this is not solution for pthread_cancel(), that also put threads in dead list w/o PTHREAD_DETACHED flag set. --- uthread_join.c.orig Mon Jan 15 15:11:30 2001 +++ uthread_join.c Mon Jan 15 15:12:34 2001 @@ -117,6 +117,8 @@ /* Return the thread's return value: */ *thread_return = pthread->ret; + pthread->attr.flags |= PTHREAD_DETACHED; + _thread_leave_cancellation_point(); /* Return the completion status: */ >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 5:10:54 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 648D537B404 for ; Mon, 15 Jan 2001 05:10:37 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id FAA03122; Mon, 15 Jan 2001 05:10:21 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151310.FAA03122@spammie.svbug.com> Date: Mon, 15 Jan 2001 05:10:19 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 To: peter@netplex.com.au Cc: freebsd-bugs@FreeBSD.ORG In-Reply-To: <200101151139.f0FBdHY02283@mobile.wemm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, Peter Wemm wrote: > opentrax@email.com wrote: >> On 15 Jan, David Malone wrote: >> >> Sorry, I'm not clear. >> >> Are you saying this bug does or does NOT affect machines in the field? >> > >> > It does - if you type: >> > >> >...[Trimmed]... > > ARGH!! If you dont use it, and have no idea what it is, then why this > endless thread about it?? > If I don't ask, I won't know. If the calendar fix effects, my servers, I'd like to know. People pay good money for our servers ($6K+ Retail). I think giving them the right time is not too much to ask. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 5:22:27 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id CB4D037B699 for ; Mon, 15 Jan 2001 05:22:09 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id FAA03133; Mon, 15 Jan 2001 05:21:28 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151321.FAA03133@spammie.svbug.com> Date: Mon, 15 Jan 2001 05:21:23 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: bin/24271: dumpon should check its argument more To: sam@inf.enst.fr Cc: wollman@khavrinen.lcs.mit.edu, freebsd-bugs@FreeBSD.ORG In-Reply-To: <2001-01-15-12-14-48+trackit+sam@inf.enst.fr> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, Samuel Tardieu wrote: > On 13/01, Garrett Wollman wrote: > > | This patch introduces at least eleven new style bugs. > > I'm not a commiter, and doesn't even know what you are talking about > (new style?). Do you have a pointer onto this "new style"? > I'm not answering for Garrett, but I took his meaning to be that the command line arguments introduced would create "new style bugs" there. That is to say, the order, use and interdependencies can be measured with introducing new command line arguments. I believe there is a formula for determining this, although I'm not familiar with it. So his number should be fairly accurate about that. BTW, I'm not a committer either. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 5:57:23 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id EC62437B6A1 for ; Mon, 15 Jan 2001 05:57:02 -0800 (PST) Received: by ada.eu.org (Postfix, from userid 10) id 1A9E01909A; Mon, 15 Jan 2001 14:57:00 +0100 (CET) Received: by trillian.rfc1149.net (Postfix, from userid 1000) id 3F937BB2F; Mon, 15 Jan 2001 14:56:51 +0100 (CET) Date: Mon, 15 Jan 2001 14:56:51 +0100 To: opentrax@email.com Cc: wollman@khavrinen.lcs.mit.edu, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/24271: dumpon should check its argument more References: <2001-01-15-12-14-48+trackit+sam@inf.enst.fr> <200101151321.FAA03133@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101151321.FAA03133@spammie.svbug.com>; from opentrax@email.com on Mon, Jan 15, 2001 at 05:21:23AM -0800 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.rfc1149.net/sam X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 X-Sam-Laptop: yes Message-Id: <2001-01-15-14-56-51+trackit+sam@inf.enst.fr> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15/01, opentrax@email.com wrote: | So his number should be fairly accurate about that. I believe you (and him), I just want to know what are those "new style bugs" :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 5:59:23 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id C6D4937B6A1 for ; Mon, 15 Jan 2001 05:59:05 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 163B61360C; Mon, 15 Jan 2001 08:59:05 -0500 (EST) Date: Mon, 15 Jan 2001 08:59:04 -0500 From: Chris Faulhaber To: Samuel Tardieu Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/24271: dumpon should check its argument more Message-ID: <20010115085904.A43912@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Samuel Tardieu , freebsd-bugs@FreeBSD.ORG References: <2001-01-15-12-14-48+trackit+sam@inf.enst.fr> <200101151321.FAA03133@spammie.svbug.com> <2001-01-15-14-56-51+trackit+sam@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <2001-01-15-14-56-51+trackit+sam@inf.enst.fr>; from sam@inf.enst.fr on Mon, Jan 15, 2001 at 02:56:51PM +0100 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 15, 2001 at 02:56:51PM +0100, Samuel Tardieu wrote: > On 15/01, opentrax@email.com wrote: > > | So his number should be fairly accurate about that. > > I believe you (and him), I just want to know what are those "new style bugs" :) > try 'man style' -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 6:40:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8134337B69E for ; Mon, 15 Jan 2001 06:40:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FEe4f02199; Mon, 15 Jan 2001 06:40:04 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 06:40:04 -0800 (PST) Message-Id: <200101151440.f0FEe4f02199@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Alex Kapranoff Subject: Re: bin/23501: pw destroy /etc/master.passwd when pw executing at the Reply-To: Alex Kapranoff Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/23501; it has been noted by GNATS. From: Alex Kapranoff To: akimoto@xephion.ne.jp Cc: dhagan@colltech.com, freebsd-gnats-submit@freebsd.org Subject: Re: bin/23501: pw destroy /etc/master.passwd when pw executing at the Date: Fri, 12 Jan 2001 20:47:34 +0300 > If anyone knows how to modify concretely, > please tell me that. > > On Thu, 04 Jan 2001 16:13:50 -0500 > Daniel Hagan wrote: > > > This is almost certainly the fault of fileupdate() in fileupd.c:72. The > > logic is too byzantine for me to figure out right now, but the comment > > at line 181 seems worrisome. > > > > Daniel Tomonobo, try the following patch and see if it helps. diff -ru /usr/src/usr.sbin/pw/edgroup.c ./edgroup.c --- /usr/src/usr.sbin/pw/edgroup.c Thu Dec 14 22:13:45 2000 +++ ./edgroup.c Fri Jan 12 20:21:42 2001 @@ -68,7 +68,7 @@ strcpy(grouptmp, groupfile); strcat(grouptmp, ".new"); - if ((infd = open(groupfile, O_RDWR | O_CREAT, 0644)) != -1) { + if ((infd = open(groupfile, O_RDWR | O_CREAT | O_EXLOCK, 0644)) != -1) { FILE *infp; if ((infp = fdopen(infd, "r+")) == NULL) @@ -76,7 +76,7 @@ else { int outfd; - if ((outfd = open(grouptmp, O_RDWR | O_CREAT | O_TRUNC | O_EXLOCK, 0644)) != -1) { + if ((outfd = open(grouptmp, O_RDWR | O_CREAT | O_TRUNC, 0644)) != -1) { FILE *outfp; if ((outfp = fdopen(outfd, "w+")) == NULL) @@ -207,8 +207,7 @@ /* * This is a gross hack, but we may have corrupted the - * original file. Unfortunately, it will lose preservation - * of the inode. + * original file. */ if (fflush(infp) == EOF || ferror(infp)) rc = rename(grouptmp, groupfile) == 0; diff -ru /usr/src/usr.sbin/pw/fileupd.c ./fileupd.c --- /usr/src/usr.sbin/pw/fileupd.c Thu Dec 14 22:13:45 2000 +++ ./fileupd.c Fri Jan 12 20:20:44 2001 @@ -76,7 +76,7 @@ if (pfxlen <= 1) rc = EINVAL; else { - int infd = open(filename, O_RDWR | O_CREAT, fmode); + int infd = open(filename, O_RDWR | O_CREAT | O_EXLOCK, fmode); if (infd == -1) rc = errno; @@ -92,7 +92,7 @@ strcpy(file, filename); strcat(file, ".new"); - outfd = open(file, O_RDWR | O_CREAT | O_TRUNC | O_EXLOCK, fmode); + outfd = open(file, O_RDWR | O_CREAT | O_TRUNC, fmode); if (outfd == -1) rc = errno; else { @@ -183,8 +183,6 @@ * to 'file'. * This is a gross hack, but we may have * corrupted the original file - * Unfortunately, it will lose the inode - * and hence the lock. */ if (fflush(infp) == EOF || ferror(infp)) rename(file, filename); -- Alex Kapranoff, Voice: +7(0832)791845 We've lived 11 days in the brand new millenium... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 9:30:43 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from yogi.urz.unibas.ch (yogi.urz.unibas.ch [131.152.1.4]) by hub.freebsd.org (Postfix) with ESMTP id C020B37B401 for ; Mon, 15 Jan 2001 09:30:17 -0800 (PST) Received: from unibas.ch ([131.152.105.161]) by ubaclu.unibas.ch (PMDF V5.2-29 #33343) with ESMTP id <01JYY2D59O9U8XAQDB@ubaclu.unibas.ch> for freebsd-bugs@FreeBSD.org; Mon, 15 Jan 2001 18:28:55 +0100 Date: Mon, 15 Jan 2001 18:39:43 +0100 From: Horatiu Palivan Subject: resource_list_alloc: resource entry is busy To: freebsd-bugs@FreeBSD.org Message-id: <3A6335DF.71CF8638@unibas.ch> Organization: Institut for Physical Chemistry, University of Basel MIME-version: 1.0 X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.6-16bpmac ppc) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a Gateway P5-90 Pentium computer with the following configuration: - Pentium Processor 90 MHz (without fdiv bug). - motherboard Intel Neptun (Zappa) 128 M memory (EDO memory: 4x32M) floppy disks: 3.5" / 5 " first IDE interface: hard disks: WD: 6400 G + 3200 G second IDE interface: CD-Rom (40x) + Iomega Zip (100M) ISA SCSI controller (AVA1505: IRQ=11 I/O=0x340 DMA=0) with: - SCSI CD Writer Yamaha CDR8424S - SCSI Harddisk (Seagate Barracuda) 4.2 G ISA Network card: NE2000+ (IRQ=10 I/O=0x300) ISA Creative Sound Blaster 16 Card (usually: IRQ=5 I/O=0x220, 0x330, 0x388 DMA: 1,5) ISA Modem Zoltrix (COM3) - PCI have IRQ=9 PCI TsengLab (ET4000/W32p) video card (1M). PCI Brooktree (BT848) video acquisition card PCI Hauppauge TV/PCI(604) (BT878) TV card I used once (in 1994) the 2.1 version of FreeBSD and I succedded to install it. OK, I didn't use it too much, because at that time I loaded the system from diskettes (I have had a CDROM IDE - the first IDE version, a NEC270 one, but you didn't have support for the IDE CDrom, only proprietary one... -> copy the distribution from CD to diskettes, and so on... ). It was when the linux kernel was 1.1.59.... NOW:..... On the computer there are installed (and working) the following operating systems: Windows95, Novell 5.0, NT4.0, Dos6.2 Linux (kernel: 2.0.29). The main boot loader is LILO (menu for 4 systems, except Novell -> the DOS starting partition for it is a logical one). I tried to install FreeBSD 4.1 on the computer, using the boot and root diskette (I don't have a bootable CDROM in BIOS, then I generated the diskettes from the CD), but I didn't succeed. It is the first time when it happen this to me. The messages when the kernel is booting are: ------------------------------------------------------------ avail memory: 124174336 (121264 K bytes) Preloaded elf kernel "kernel" at 0xc063e000 Preloaded mfs-root "/mfsroot" at 0xc063e084 Intel Pentium detected, installing workaround for F00F bug. md0: Preloaded image 2949120 bytes at 0xc036cd98 md1: Malloc disk. npx0: on motherboard. npx0: INT 16 interface pcib0: om motherboard. pci0: on pcib0 atapici0: port 0x3f4-ox3f7, 0x1f0-0x1f7 at device 1.0 on pci0. atapici0: Busmastering DMA not supported. panic: resource_list_alloc: resource entry is busy uptime: 0s ------------------------------------------------------------ On other systems where I tried, it seems to boot until the instalation menu........But because it seems that you do not have a possibility to review the booting messages (like SHIFT-Pg.UP in Linux), I do not know the exact boot messages and sequence on the other systems, bacause when I quit the installation menu, the system want to reboot). I tried the tricks with "flags npx0 1" (from trouble.txt), but it don't work. In the configuration of kernel, I disabled all possible features - in advanced mode - (except sc0 and keyboard), but the same things happen. If you need messages, I tried to give all possible messages: Booting messages: >> FreeBSD/i386 BOOT Default: 0: fd(0,a)/boot/loader boot: BTX Loader 1.00 .......1.01 Console: internal video/keyboard BIOS driveA: disk0 BIOS driveB: disk1 BIOS driveC: disk2 BIOS driveD: disk3 FreeBSD/i386 bootstrap loader, Revision 0.8 (jk4@ref4.freebsd.org, fri jul 28 12:39:58 GMT 2000) /kernel text=0x21e97e data=0x2cd8c+0x2068c (boot prompt) : ls mod: 0x100000: kernel (elf kernel, 0x26cd98) 0x36cd98: /mfsroot(mfs-root, 0x2d0000) : heap: Active Allocations: 455/457 155648 bytes reserved 64216 bytes allocated. 7 fragments (10868 bytes fragmented) heap base at 0x28600, top at 0x4e600 : ls dev: disk0: BIOS drive A: disk0a: FFS 1M (0-2880) disk0c: FFS 1M (0-2880) disk1: BIOS drive B: disk2: BIOS drive C: disk2s1: FAT-16 1004 MB (63-2056320) disk2s2: Unknown fs: 0x65 568 MB (2056320-3220560) <- Novell partition disk2s3: Unknown fs: 0x7 1380 MB (3220560-6048000) <- NTFS partition. disk2s5: FAT-16 494 MB (6048063-7061040) disk2s7: FAT-16 1004 MB (7061103-9117360) OBS: here are missing some partitions... why ??? disk3: BIOS drive D: disk3s1: FAT-16 511 MB (63-1048320) disk3s2: ext2fs 66 MB (1048320-1185408) disk3s3: ext2fs 346 MB (1185408-1895040) disk3s5: Linux swap 122 MB (1895103-2145024) disk3s7: ext2fs 1204 MB(2145087-4612608) OBS: also here are missing some partitions... why ??? The problemm is: what can I do ? How can I install the FreeBDS on the computer ? I do not know the order for the kernel to load drivers and probe them, then I could not figure out where the error is...(and in principle it must not be any errors, because it is not the first time when I install an operating system on it).... If you have some ideeas how to work around this, please let me know... Horatiu Palivan -- Dr. Horatiu Palivan Institut for Physical Chemistry University of Basel Klingelbergstr. 80 4056 - Basel Switzerland tel: +(41) 061 267 37 98 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 9:39:56 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id DBBF337B400 for ; Mon, 15 Jan 2001 09:39:39 -0800 (PST) Received: from sobek.openirc.co.uk ([62.252.9.121]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20010115173936.VUZD23225.mta02-svc.ntlworld.com@sobek.openirc.co.uk>; Mon, 15 Jan 2001 17:39:36 +0000 Date: Mon, 15 Jan 2001 17:45:52 +0000 (GMT) From: George Reid X-Sender: geeorgy@sobek.openirc.co.uk To: Horatiu Palivan Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: resource_list_alloc: resource entry is busy In-Reply-To: <3A6335DF.71CF8638@unibas.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 15 Jan 2001, Horatiu Palivan wrote: > atapici0: > port 0x3f4-ox3f7, 0x1f0-0x1f7 at device 1.0 on pci0. > atapici0: Busmastering DMA not supported. > panic: resource_list_alloc: resource entry is busy > uptime: 0s The RZ1000/RZ1001 chips are physically faulty. Software patches exist, but they are not 100% reliable (and are therefore useless). Your best bet is to spent $15 or so on a cheap ISA/PCI IDE card. G "And then it comes to be that the soothing light at the end of your tunnel was just a freight train, comin' your way." George Reid * greid@ukug.uk.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 9:42:25 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mooseriver.com (erie.mooseriver.com [205.166.121.26]) by hub.freebsd.org (Postfix) with ESMTP id A216137B400 for ; Mon, 15 Jan 2001 09:42:07 -0800 (PST) Received: (from jgrosch@localhost) by mooseriver.com (8.11.1/8.9.3) id f0FHfxh95871; Mon, 15 Jan 2001 09:41:59 -0800 (PST) (envelope-from jgrosch) Date: Mon, 15 Jan 2001 09:41:59 -0800 From: Josef Grosch To: opentrax@email.com Cc: dwmalone@maths.tcd.ie, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/23456: calendar.judaic will be incorrect on Jan. 1, 2001 Message-ID: <20010115094159.B95698@mooseriver.com> Reply-To: jgrosch@mooseriver.com References: <200101151052.aa72616@salmon.maths.tcd.ie> <200101151132.DAA02985@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200101151132.DAA02985@spammie.svbug.com>; from opentrax@email.com on Mon, Jan 15, 2001 at 03:32:32AM -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 15, 2001 at 03:32:32AM -0800, opentrax@email.com wrote: [ DELETED ] > BTW, if someone can email me on this Judaic calendar, I'd > apprecite it. I have no idea what it is. [ DELETED ] I assume you know what calendar does. If not then type the command "man calendar" and read. The file in question, calendar.judaic, has all the holidays, parashot, the beginnings of the months, etc of the jewish calendar. We, the Jewish nation, have our own calendar. This calendar is lunar based. There are 12 or 13 months in the year, depending where we are in the lunar cycle. In our calendar it is the year 5761. If you have any futher questions please email me off the mailing lists and I'll be glad to answer any questions. Josef -- Josef Grosch | Another day closer to a | FreeBSD 4.2 jgrosch@MooseRiver.com | Micro$oft free world | www.bafug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 10: 6:29 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 3E21C37B400 for ; Mon, 15 Jan 2001 10:06:12 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id B77062B515; Mon, 15 Jan 2001 12:06:01 -0600 (CST) Date: Mon, 15 Jan 2001 12:06:01 -0600 From: Bill Fumerola To: opentrax@email.com Cc: sam@inf.enst.fr, wollman@khavrinen.lcs.mit.edu, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/24271: dumpon should check its argument more Message-ID: <20010115120601.B61857@elvis.mu.org> References: <2001-01-15-12-14-48+trackit+sam@inf.enst.fr> <200101151321.FAA03133@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101151321.FAA03133@spammie.svbug.com>; from opentrax@email.com on Mon, Jan 15, 2001 at 05:21:23AM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 15, 2001 at 05:21:23AM -0800, opentrax@email.com wrote: > > | This patch introduces at least eleven new style bugs. > > > > I'm not a commiter, and doesn't even know what you are talking about > > (new style?). Do you have a pointer onto this "new style"? > > > I'm not answering for Garrett, but I took his meaning to be > that the command line arguments introduced would create > "new style bugs" there. That is to say, the order, use > and interdependencies can be measured with introducing > new command line arguments. I believe there is a formula > for determining this, although I'm not familiar with it. > > So his number should be fairly accurate about that. > BTW, I'm not a committer either. I won't speak for Garrett either, but I'll at least come close to his original intent: Code in the project is supposed to conform to a specific style, which is defined in 'man 9 style'. The patch violated the rules in that manpage and should be cleaned up before committing (if its even worth committing). I've been a native English speaker all my life and consider myself fairly decent with the language. I, however, cannot figure out what the hell... "use and interdepedencies can be measured with introducing new command line arguments" ... is even supposed to mean. I'd suggest that whoever is running the jmjr.pl script on our mailing lists turn down the "random words from the jargon file" setting a notch or two. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 11:17:28 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 955E137B401 for ; Mon, 15 Jan 2001 11:17:11 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA97602; Mon, 15 Jan 2001 14:16:57 -0500 (EST) (envelope-from wollman) Date: Mon, 15 Jan 2001 14:16:57 -0500 (EST) From: Garrett Wollman Message-Id: <200101151916.OAA97602@khavrinen.lcs.mit.edu> To: Tor.Egge@fast.no Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs In-Reply-To: <200101150240.f0F2e6w52001@freefall.freebsd.org> References: <200101150240.f0F2e6w52001@freefall.freebsd.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < One workaround for the race is to serialize vfprintf() calls that use > floating point conversion specifications. Since the interface is purely internal, it would be better to simply *fix* it.... -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 11:27:28 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 703E437B401 for ; Mon, 15 Jan 2001 11:27:10 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id LAA00483; Mon, 15 Jan 2001 11:26:27 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151926.LAA00483@spammie.svbug.com> Date: Mon, 15 Jan 2001 11:26:26 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: bin/24271: dumpon should check its argument more To: billf@mu.org Cc: sam@inf.enst.fr, wollman@khavrinen.lcs.mit.edu, freebsd-bugs@FreeBSD.ORG In-Reply-To: <20010115120601.B61857@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15 Jan, Bill Fumerola wrote: > On Mon, Jan 15, 2001 at 05:21:23AM -0800, opentrax@email.com wrote: > >...[Trimmed]... > > I've been a native English speaker all my life and consider myself > fairly decent with the language. I, however, cannot figure out > what the hell... > > "use and interdepedencies can be measured with introducing new > command line arguments" > > .... is even supposed to mean. I'd suggest that whoever is running > the jmjr.pl script on our mailing lists turn down the "random words > from the jargon file" setting a notch or two. > Apparently, my statements were incorrect. Apparently, you don't do User Interfaces. The new book by Jef Raskin gets into many UI and GUI issues. I won't bore anyone with the details. If you are interested, it's called The Humane Interface (ISBN 0-2-1-37937-6) Have a nice day in the jargon file. :-) Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 11:30:29 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 379AE37B401 for ; Mon, 15 Jan 2001 11:30:10 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FJUA700808; Mon, 15 Jan 2001 11:30:10 -0800 (PST) (envelope-from gnats) Received: from laptop.bsmith (c8366-a.snvl1.sfba.home.com [65.0.152.119]) by hub.freebsd.org (Postfix) with ESMTP id D81AD37B401 for ; Mon, 15 Jan 2001 11:28:03 -0800 (PST) Received: (from root@localhost) by laptop.bsmith (8.11.1/8.11.1) id f0FJS2g00704; Mon, 15 Jan 2001 11:28:03 -0800 (PST) (envelope-from bsmith) Message-Id: <200101151928.f0FJS2g00704@laptop.bsmith> Date: Mon, 15 Jan 2001 11:28:03 -0800 (PST) From: root@laptop.bsmith Reply-To: ben@owns.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: i386/24351: setkey(8) typo. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24351 >Category: i386 >Synopsis: setkey(8) man page has multiple spelling errors. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 11:30:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Charlie & >Release: FreeBSD 5.0-CURRENT i386 >Organization: Atomz.com >Environment: System: FreeBSD laptop.bsmith 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sun Jan 14 14:45:42 PST 2001 root@laptop.bsmith:/usr/src/sys/compile/LAPTOP-5-C i386 >Description: from the setkey(8) manpage in FreeBSD 5-CURRENT DESCRIPTION setkey addes, updates, dumpes, or flushes Security Association Database (SAD) entries as well as Security Policy Database (SPD) entries in the kernel. from the current KAME snap: DESCRIPTION setkey adds, updates, dumps, or flushes Security Association Database (SAD) entries as well as Security Policy Database (SPD) entries in the kernel. >How-To-Repeat: read the man page. >Fix: update the kame/wide man page documentation. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 12:20:29 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 95E5237B699 for ; Mon, 15 Jan 2001 12:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FKK2B07618; Mon, 15 Jan 2001 12:20:02 -0800 (PST) (envelope-from gnats) Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 4876B37B698 for ; Mon, 15 Jan 2001 12:19:29 -0800 (PST) Received: (qmail 6184 invoked by uid 0); 15 Jan 2001 20:19:27 -0000 Received: from p3ee2166d.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.109) by mail.gmx.net (mp004-rz3) with SMTP; 15 Jan 2001 20:19:27 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA09309 for FreeBSD-gnats-submit@freebsd.org; Mon, 15 Jan 2001 19:46:03 +0100 Message-Id: <20010115194603.Y253@speedy.gsinet> Date: Mon, 15 Jan 2001 19:46:03 +0100 From: Gerhard Sittig To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: conf/24358: [PATCH] etc/rc variables for cron(8) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24358 >Category: conf >Synopsis: [PATCH] etc/rc variables for cron(8) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 12:20:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Gerhard Sittig >Release: FreeBSD 4.2-STABLE i386 >Organization: in private >Environment: any FreeBSD system with cron(8) invocation in /etc/rc >Description: Currently it's neither possible to pass command line options to the cron daemon nor can one choose which cron executable to run. Although public discussion proves that there are different preferences among users as well as a certain wish to escape from fixed values (while preserving current behaviour as a default). >How-To-Repeat: Try to tell your FreeBSD system to run a different cron program or to pass (e.g. some "-x KEY") command line parameters to it without touching /etc/rc. It's only possible by setting "cron_enable=NO" and introducing a new /usr/local/etc/rc.d script. Which in turn might ask for another config file ... >Fix: Apply the following patch which introduces two new rc.conf variables named "cron_program" and "cron_flags". The manpage wording is copied over from the named section. # 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: # # cronvars.diff # echo x - cronvars.diff sed 's/^X//' >cronvars.diff << 'END-of-cronvars.diff' XIndex: etc/rc X=================================================================== XRCS file: /CVSREPO/fbsd/src/etc/rc,v Xretrieving revision 1.240 Xdiff -u -u -r1.240 rc X--- etc/rc 2000/11/21 04:21:54 1.240 X+++ etc/rc 2001/01/15 19:11:53 X@@ -502,7 +502,7 @@ X [Nn][Oo]) X ;; X *) X- echo -n ' cron'; cron X+ echo -n ' cron'; ${cron_program:-cron} ${cron_flags} X ;; X esac X XIndex: etc/defaults/rc.conf X=================================================================== XRCS file: /CVSREPO/fbsd/src/etc/defaults/rc.conf,v Xretrieving revision 1.83 Xdiff -u -u -r1.83 rc.conf X--- etc/defaults/rc.conf 2000/10/29 19:59:04 1.83 X+++ etc/defaults/rc.conf 2001/01/15 18:53:03 X@@ -295,6 +295,8 @@ X ############################################################## X X cron_enable="YES" # Run the periodic job daemon. X+cron_program="cron" # Which cron executable to run (if enabled). X+cron_flags="" # Which options to pass to the cron daemon. X lpd_enable="NO" # Run the line printer daemon. X lpd_program="/usr/sbin/lpd" # path to lpd, if you want a different one. X lpd_flags="" # Flags to lpd (if enabled). XIndex: share/man/man5/rc.conf.5 X=================================================================== XRCS file: /CVSREPO/fbsd/src/share/man/man5/rc.conf.5,v Xretrieving revision 1.84 Xdiff -u -u -r1.84 rc.conf.5 X--- share/man/man5/rc.conf.5 2000/10/28 13:35:30 1.84 X+++ share/man/man5/rc.conf.5 2001/01/15 19:08:44 X@@ -1302,6 +1302,18 @@ X then run the X .Xr cron 8 X daemon at system boot time. X+.It Ar cron_program X+(str) path to X+.Xr cron 8 X+(default X+.Pa cron ) . X+.It Ar cron_flags X+(str) if X+.Ar cron_enable X+is set to X+.Ar YES , X+these are the flags to pass to X+.Xr cron 8 . X .It Ar lpd_program X (str) path to X .Xr lpd 8 END-of-cronvars.diff exit virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 13:50:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 431ED37B401 for ; Mon, 15 Jan 2001 13:50:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0FLo6P19676; Mon, 15 Jan 2001 13:50:06 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 13:50:06 -0800 (PST) Message-Id: <200101152150.f0FLo6P19676@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tor.Egge@fast.no Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Reply-To: Tor.Egge@fast.no Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15070; it has been noted by GNATS. From: Tor.Egge@fast.no To: wollman@khavrinen.lcs.mit.edu Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Date: Mon, 15 Jan 2001 22:48:55 +0100 > Since the interface is purely internal, it would be better to simply > *fix* it.... Like this ? Index: lib/libc/stdlib/strtod.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdlib/strtod.c,v retrieving revision 1.3 diff -u -r1.3 strtod.c --- lib/libc/stdlib/strtod.c 1996/07/12 18:55:22 1.3 +++ lib/libc/stdlib/strtod.c 2001/01/15 21:06:01 @@ -371,6 +371,16 @@ static Bigint *freelist[Kmax+1]; + /* + * Make Balloc/Bfree thread-safe in libc for use with + * kernel threads. + */ +#include "libc_private.h" +#include "spinlock.h" +static spinlock_t thread_lock = _SPINLOCK_INITIALIZER; +#define THREAD_LOCK() if (__isthreaded) _SPINLOCK(&thread_lock); +#define THREAD_UNLOCK() if (__isthreaded) _SPINUNLOCK(&thread_lock); + static Bigint * Balloc #ifdef KR_headers @@ -382,9 +392,12 @@ int x; Bigint *rv; + THREAD_LOCK(); if ( (rv = freelist[k]) ) { freelist[k] = rv->next; + THREAD_UNLOCK(); } else { + THREAD_UNLOCK(); x = 1 << k; rv = (Bigint *)malloc(sizeof(Bigint) + (x-1)*sizeof(long)); rv->k = k; @@ -403,8 +416,10 @@ #endif { if (v) { + THREAD_LOCK(); v->next = freelist[v->k]; freelist[v->k] = v; + THREAD_UNLOCK(); } } @@ -1839,10 +1854,11 @@ char * __dtoa #ifdef KR_headers - (d, mode, ndigits, decpt, sign, rve) - double d; int mode, ndigits, *decpt, *sign; char **rve; + (d, mode, ndigits, decpt, sign, rve, resultp) + double d; int mode, ndigits, *decpt, *sign; char **rve, **resultp; #else - (double d, int mode, int ndigits, int *decpt, int *sign, char **rve) + (double d, int mode, int ndigits, int *decpt, int *sign, char **rve, + char **resultp) #endif { /* Arguments ndigits, decpt, sign are similar to those @@ -1890,15 +1906,6 @@ Bigint *b, *b1, *delta, *mlo, *mhi, *S; double d2, ds, eps; char *s, *s0; - static Bigint *result; - static int result_k; - - if (result) { - result->k = result_k; - result->maxwds = 1 << result_k; - Bfree(result); - result = 0; - } if (word0(d) & Sign_bit) { /* set sign for everything, including 0's and NaNs */ @@ -2057,11 +2064,8 @@ if (i <= 0) i = 1; } - j = sizeof(unsigned long); - for (result_k = 0; sizeof(Bigint) - sizeof(unsigned long) + j < i; - j <<= 1) result_k++; - result = Balloc(result_k); - s = s0 = (char *)result; + *resultp = (char *) malloc(i); + s = s0 = *resultp; if (ilim >= 0 && ilim <= Quick_max && try_quick) { Index: lib/libc/stdio/vfprintf.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdio/vfprintf.c,v retrieving revision 1.23 diff -u -r1.23 vfprintf.c --- lib/libc/stdio/vfprintf.c 2001/01/06 20:48:00 1.23 +++ lib/libc/stdio/vfprintf.c 2001/01/15 21:43:09 @@ -264,7 +264,7 @@ #define BUF (MAXEXP+MAXFRACT+1) /* + decimal point */ #define DEFPREC 6 -static char *cvt __P((double, int, int, char *, int *, int, int *)); +static char *cvt __P((double, int, int, char *, int *, int, int *, char **)); static int exponent __P((char *, int, int)); #else /* no FLOATING_POINT */ @@ -310,6 +310,7 @@ int expsize; /* character count for expstr */ int ndig; /* actual number of digits returned by cvt */ char expstr[7]; /* buffer for exponent string */ + char *dtoaresult; /* buffer allocated by dtoa */ #endif u_long ulval; /* integer arguments %[diouxX] */ u_quad_t uqval; /* %q integers */ @@ -418,6 +419,9 @@ } +#ifdef FLOATING_POINT + dtoaresult = NULL; +#endif FLOCKFILE(fp); /* sorry, fprintf(read_only_file, "") returns EOF, not 0 */ if (cantwrite(fp)) { @@ -608,8 +612,12 @@ break; } flags |= FPT; + if (dtoaresult != NULL) { + free(dtoaresult); + dtoaresult = NULL; + } cp = cvt(_double, prec, flags, &softsign, - &expt, ch, &ndig); + &expt, ch, &ndig, &dtoaresult); if (ch == 'g' || ch == 'G') { if (expt <= -4 || expt > prec) ch = (ch == 'g') ? 'e' : 'E'; @@ -865,6 +873,10 @@ done: FLUSH(); error: +#ifdef FLOATING_POINT + if (dtoaresult != NULL) + free(dtoaresult); +#endif if (__sferror(fp)) ret = EOF; FUNLOCKFILE(fp); @@ -1203,13 +1215,14 @@ #ifdef FLOATING_POINT -extern char *__dtoa __P((double, int, int, int *, int *, char **)); +extern char *__dtoa __P((double, int, int, int *, int *, char **, char **)); static char * -cvt(value, ndigits, flags, sign, decpt, ch, length) +cvt(value, ndigits, flags, sign, decpt, ch, length, dtoaresultp) double value; int ndigits, flags, *decpt, ch, *length; char *sign; + char **dtoaresultp; { int mode, dsgn; char *digits, *bp, *rve; @@ -1231,7 +1244,8 @@ *sign = '-'; } else *sign = '\000'; - digits = __dtoa(value, mode, ndigits, decpt, &dsgn, &rve); + digits = __dtoa(value, mode, ndigits, decpt, &dsgn, &rve, + dtoaresultp); if ((ch != 'g' && ch != 'G') || flags & ALT) { /* print trailing zeros */ bp = digits + ndigits; - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 17:10:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E129C37B6C7 for ; Mon, 15 Jan 2001 17:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G1A1N47283; Mon, 15 Jan 2001 17:10:01 -0800 (PST) (envelope-from gnats) Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by hub.freebsd.org (Postfix) with ESMTP id 2739537B6C4 for ; Mon, 15 Jan 2001 17:01:31 -0800 (PST) Received: from citylink.dinoex.sub.org (uucp@localhost) by net2.dinoex.sub.org (8.11.2/8.11.2) with UUCP id f0G11E106717 for freebsd.org!FreeBSD-gnats-submit; Tue, 16 Jan 2001 02:01:14 +0100 (CET) (envelope-from citylink.dinoex.sub.de!admin%dyn@citylink.dinoex.sub.org) Received: from dyn.oper.dinoex.org by citylink.dinoex.sub.org (8.8.5/PMuch-B3b) with ESMTP id BAA22853 for ; Tue, 16 Jan 2001 01:51:03 +0100 (CET) Received: (from admin@localhost) by dyn.oper.dinoex.org (8.11.1/8.11.1) id f0G0ou735410; Tue, 16 Jan 2001 01:50:56 +0100 (CET) (envelope-from admin) Message-Id: <200101160050.f0G0ou735410@dyn.oper.dinoex.org> Date: Tue, 16 Jan 2001 01:50:56 +0100 (CET) From: System Admin Account Reply-To: peter.much@sercon.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24365: ifconfig inet6 delete -> kernelpanic Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24365 >Category: kern >Synopsis: delete alias from ipv6 p-t-p iface will crash kernel >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 17:10:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: System Admin Account >Release: FreeBSD 4.2-RELEASE i386 >Organization: >Environment: kernel built with INET6 >Description: this works with loopback and p-t-p ifaces. $ ifconfig lo0 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 $ ifconfig lo0 inet6 delete ::1 -> this works as one would expect $ ifconfig lo0 inet6 delete fe80::1%lo0 -> but this one panics! Functions called: rtalloc1 from rtinit " in6_ifscrub " in6_purgeaddr " in6_control " ifioctl >How-To-Repeat: not applicable, see piece-of-code below for the failure-reason. >Fix: Thats what I have done, and what made it work here. As I have configured IPv6 just out of curiousity and have no real usage yet for it, I cannot say about side-effects, possibly with a routing daemon or such. The code obviousely considers _every_ immanent route on a loopback or p-t-p iface as a _host_route (and afaik this is true for classic IP), but the fe80::1%lo0 is some kind of cloneable route: $ netstat -r Destination Gateway Flags Netif Expire fe80::%lo0 fe80::1%lo0 Uc lo0 *** sys/netinet6/in6.c.orig Sat Jul 15 09:14:33 2000 --- sys/netinet6/in6.c Sun Jan 14 04:03:37 2001 *************** *** 1219,1227 **** { if ((ia->ia_flags & IFA_ROUTE) == 0) return; ! if (ifp->if_flags & (IFF_LOOPBACK | IFF_POINTOPOINT)) rtinit(&(ia->ia_ifa), (int)RTM_DELETE, RTF_HOST); ! else rtinit(&(ia->ia_ifa), (int)RTM_DELETE, 0); ia->ia_flags &= ~IFA_ROUTE; --- 1219,1227 ---- { if ((ia->ia_flags & IFA_ROUTE) == 0) return; ! /* if (ifp->if_flags & (IFF_LOOPBACK | IFF_POINTOPOINT)) rtinit(&(ia->ia_ifa), (int)RTM_DELETE, RTF_HOST); ! else */ rtinit(&(ia->ia_ifa), (int)RTM_DELETE, 0); ia->ia_flags &= ~IFA_ROUTE; >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 17:40:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BBF9637B6A2 for ; Mon, 15 Jan 2001 17:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G1e1250207; Mon, 15 Jan 2001 17:40:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5591C37B69E for ; Mon, 15 Jan 2001 17:36:03 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G1a3Z49854; Mon, 15 Jan 2001 17:36:03 -0800 (PST) (envelope-from nobody) Message-Id: <200101160136.f0G1a3Z49854@freefall.freebsd.org> Date: Mon, 15 Jan 2001 17:36:03 -0800 (PST) From: klui@cup.hp.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24367: ATA driver finds non-existent drives Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24367 >Category: kern >Synopsis: ATA driver finds non-existent drives >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 17:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Ken Lui >Release: 4.2-RELEASE >Organization: N/A >Environment: FreeBSD black 4.2-RELEASE FreeBSD 4.2-RELEASE #10: Mon Jan 15 17:16:06 PST 2001 klui@black:/usr/src/sys/compile/A7V i386 >Description: Sometimes, the ATA driver will find drives that doesn't exist on my A7V system. When this happens, I get the following error: ata3-slave: ata_command: timeout waiting for intr ata3-slave: identify failed ata3-master: ata_command: timeout waiting for intr ata3-master: identify failed My A7V (board rev 1.02, BIOS 1005C) with Duron (800MHz) has a UDMA66 drive on the Primary ATA100 (Promise, onboard) controller (only drive on this cable) as master, and a DVD-ROM drive on the Secondary IDE controller (only drive on this cable) as master. On boot, I sometimes see the following: [DVD-ROM/master] atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata1: at 0x170 irq 15 on atapci0 . . . atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9 407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 on pci0 [Quantum Fireball Plus LM/master] ata2: at 0xa000 on atapci1 [??] ata3: at 0x9400 on atapci1 Sometimes, ata3 doesn't show up, but sometimes, it does. My current ATA settings are all PIO. I have no cable dangling off the secondary ATA100 connector. Ken >How-To-Repeat: Intermittent >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 17:50:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8324637B69F for ; Mon, 15 Jan 2001 17:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G1o1851024; Mon, 15 Jan 2001 17:50:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2FE2B37B69E for ; Mon, 15 Jan 2001 17:45:46 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G1jk350647; Mon, 15 Jan 2001 17:45:46 -0800 (PST) (envelope-from nobody) Message-Id: <200101160145.f0G1jk350647@freefall.freebsd.org> Date: Mon, 15 Jan 2001 17:45:46 -0800 (PST) From: klui@cup.hp.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24368 >Category: kern >Synopsis: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 17:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Ken Lui >Release: 4.2-RELEASE >Organization: N/A >Environment: FreeBSD black 4.2-RELEASE FreeBSD 4.2-RELEASE #10: Mon Jan 15 17:16:06 PST 2001 klui@black:/usr/src/sys/compile/A7V i386 >Description: I, like a lot of other people with the Asus A7V, have drive timeouts when using the onboard ATA100 controller with UDMA drives. The kernel configuration says that if ATA_ENABLE_ATAPI_DMA isn't defined, DMA mode is not used. However, I have found that, for my A7V anyway, DMA is always enabled during boot time and /etc/sysctl.conf doesn't always turn off DMA mode before I get the timeouts and PIO fallback routines. >How-To-Repeat: Intermittent >Fix: Patch /usr/src/sys/dev/ata/ata-all.c. *** ata-all.c.orig Mon Jan 15 17:42:52 2001 --- ata-all.c Mon Jan 15 16:27:01 2001 *************** *** 1750,1757 **** --- 1750,1759 ---- for (i = 0; i < 2; i++) { if (!scp->dev_softc[i]) strcat(ata_conf, "---,"); + #ifdef ATA_ENABLE_ATAPI_DMA else if (scp->mode[i] >= ATA_DMA) strcat(ata_conf, "dma,"); + #endif else strcat(ata_conf, "pio,"); } >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 17:50:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 212F937B6A0 for ; Mon, 15 Jan 2001 17:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G1o2P51033; Mon, 15 Jan 2001 17:50:02 -0800 (PST) (envelope-from gnats) Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132]) by hub.freebsd.org (Postfix) with ESMTP id A480937B69F for ; Mon, 15 Jan 2001 17:48:43 -0800 (PST) Received: from (hand.dotat.at) [127.0.0.1] (root) by chiark.greenend.org.uk with esmtp (Exim 3.12 #2) id 14ILEo-0004mH-00 (Debian); Tue, 16 Jan 2001 01:48:43 +0000 Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 14HJBr-000I9p-00 for FreeBSD-gnats-submit@freebsd.org; Sat, 13 Jan 2001 05:25:23 +0000 Message-Id: Date: Sat, 13 Jan 2001 05:25:23 +0000 From: Tony Finch Reply-To: Tony Finch To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24369: typo "millenium" in units.lib Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24369 >Category: bin >Synopsis: typo "millenium" in units.lib >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 17:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Tony Finch >Release: FreeBSD 4.2-BETA-20001113 i386 >Organization: Covalent Technologoes Inc. >Environment: >Description: typo "millenium" in units.lib >How-To-Repeat: >Fix: Index: units.lib =================================================================== RCS file: /home/ncvs/src/usr.bin/units/units.lib,v retrieving revision 1.5.2.1 diff -u -r1.5.2.1 units.lib --- units.lib 2000/04/18 16:38:47 1.5.2.1 +++ units.lib 2001/01/13 05:22:24 @@ -454,7 +454,7 @@ mh millihenry mhz 1e+6 /sec mil 1e-3 in -millenium 1000 year +millennium 1000 year minersinch 1.5 ft3/min minim 1|60 fldr mo month >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 18:20:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 56E9E37B6A6 for ; Mon, 15 Jan 2001 18:20:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G2K3I56464; Mon, 15 Jan 2001 18:20:03 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 18:20:03 -0800 (PST) Message-Id: <200101160220.f0G2K3I56464@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Brooks Davis Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Reply-To: Brooks Davis Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24368; it has been noted by GNATS. From: Brooks Davis To: klui@cup.hp.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Date: Mon, 15 Jan 2001 18:13:00 -0800 On Mon, Jan 15, 2001 at 05:45:46PM -0800, klui@cup.hp.com wrote: > I, like a lot of other people with the Asus A7V, have drive timeouts > when using the onboard ATA100 controller with UDMA drives. The kernel > configuration says that if ATA_ENABLE_ATAPI_DMA isn't defined, DMA mode > is not used. However, I have found that, for my A7V anyway, DMA is > always enabled during boot time and /etc/sysctl.conf doesn't always turn > off DMA mode before I get the timeouts and PIO fallback routines. I think you're confused (this could be the fault of the docs). ATA_ENABLE_ATAPI_DMA only controls ATAPI DMA which only applies to things like CD-ROMs, Zip drives, TAPEs, etc. It will have no effect on your hard drives. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 18:20:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E05A37B69C for ; Mon, 15 Jan 2001 18:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G2K2q56458; Mon, 15 Jan 2001 18:20:02 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 18:20:02 -0800 (PST) Message-Id: <200101160220.f0G2K2q56458@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tor.Egge@fast.no Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Reply-To: Tor.Egge@fast.no Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15070; it has been noted by GNATS. From: Tor.Egge@fast.no To: wollman@khavrinen.lcs.mit.edu Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/15070: vfprintf/cvt/__dtoa race condition in threaded programs Date: Tue, 16 Jan 2001 03:11:04 +0100 This uncovered another old __dtoa() bug. *resultp = (char *) malloc(i); in the patch must be changed to *resultp = (char *) malloc(i + 1); in order to avoid writing beyond the end of the allocated memory. Otherwise the sample program #include #include int main(int argc,char **argv) { (void) malloc(4); printf("%.23e\n", 2.4); return 0; } linked with Electric Fence crashes on the i386 platform. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 18:30:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0BDF637B6AD for ; Mon, 15 Jan 2001 18:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G2U2S57400; Mon, 15 Jan 2001 18:30:02 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 18:30:02 -0800 (PST) Message-Id: <200101160230.f0G2U2S57400@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ken Lui Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Reply-To: Ken Lui Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24368; it has been noted by GNATS. From: Ken Lui To: Brooks Davis Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Date: Mon, 15 Jan 2001 18:26:17 -0800 (PST) On Mon, 15 Jan 2001, Brooks Davis wrote: > On Mon, Jan 15, 2001 at 05:45:46PM -0800, klui@cup.hp.com wrote: > > I, like a lot of other people with the Asus A7V, have drive timeouts > > when using the onboard ATA100 controller with UDMA drives. The kernel > > configuration says that if ATA_ENABLE_ATAPI_DMA isn't defined, DMA mode > > is not used. However, I have found that, for my A7V anyway, DMA is > > always enabled during boot time and /etc/sysctl.conf doesn't always turn > > off DMA mode before I get the timeouts and PIO fallback routines. > > I think you're confused (this could be the fault of the docs). > ATA_ENABLE_ATAPI_DMA only controls ATAPI DMA which only applies to things > like CD-ROMs, Zip drives, TAPEs, etc. It will have no effect on your > hard drives. I've also been told by Gregory Bond of the same thing. Sorry, but I'm used to SCSI and ATA/ATAPI kinda sorta looks the same to me. So what's the proper way to fix my problem? Perhaps a ATA_DISABLE_ATA_DMA flag? Sounds kinda repetitive. I will probably move the drive to the primary IDE connector of my A7V. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 21:50:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 512EE37B698 for ; Mon, 15 Jan 2001 21:50:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G5o6D82636; Mon, 15 Jan 2001 21:50:06 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 21:50:06 -0800 (PST) Message-Id: <200101160550.f0G5o6D82636@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Brooks Davis Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Reply-To: Brooks Davis Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24368; it has been noted by GNATS. From: Brooks Davis To: Ken Lui Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Date: Mon, 15 Jan 2001 21:19:32 -0800 On Mon, Jan 15, 2001 at 06:26:17PM -0800, Ken Lui wrote: > I've also been told by Gregory Bond of the same thing. Sorry, but > I'm used to SCSI and ATA/ATAPI kinda sorta looks the same to me. So > what's the proper way to fix my problem? Perhaps a ATA_DISABLE_ATA_DMA > flag? Sounds kinda repetitive. I will probably move the drive to the > primary IDE connector of my A7V. I think you're currently kinda stuck with things as they are, but I really haven't looked into it. I don't have anything better then UDMA33 in ATA land so I've never had any problems with it. I don't think the downgrades are harmful unless you get a panic. Ignoring the messages is probably the easiest thing to do. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 22:40:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4B93D37B401 for ; Mon, 15 Jan 2001 22:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G6e1t93440; Mon, 15 Jan 2001 22:40:01 -0800 (PST) (envelope-from gnats) Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 2FA7137B400 for ; Mon, 15 Jan 2001 22:32:10 -0800 (PST) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id B284E3E02 for ; Mon, 15 Jan 2001 22:32:09 -0800 (PST) Received: (from dima@localhost) by hornet.unixfreak.org (8.11.1/8.11.1) id f0G6W9v43972; Mon, 15 Jan 2001 22:32:09 -0800 (PST) (envelope-from dima) Message-Id: <200101160632.f0G6W9v43972@hornet.unixfreak.org> Date: Mon, 15 Jan 2001 22:32:09 -0800 (PST) From: dima@unixfreak.org Reply-To: dima@unixfreak.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: gnu/24372: [PATCH] (cosmetic) -current send-pr breaks NIS support Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24372 >Category: gnu >Synopsis: [PATCH] (cosmetic) -current send-pr breaks NIS support >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 22:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Dima Dorfman >Release: FreeBSD 5.0-20010101-CURRENT i386 >Organization: Private >Environment: System: FreeBSD spike.unixfreak.org 5.0-20010101-CURRENT FreeBSD 5.0-20010101-CURRENT #6: Tue Jan 2 03:14:04 PST 2001 dima@spike.unixfreak.org:/usr/home/dima/w/f/src/sys/compile/SPIKE i386 >Description: send-pr on -current uses `cat /etc/passwd` when looking for the default name for the ``Originator'' field. If the user filing the problem report doesn't have a local account (authenticated via NIS, for example), the field will be left blank. Of course, one can always set the field manually, but this works in RELENG_4, so why shouldn't it work in 5-CURRENT? >How-To-Repeat: Sign on using an account authenticated via NIS or anything which doesn't require an entry in the local password database, then do: send-pr -P | grep '^>Originator' and notice how the field is blank. Now sign on with a local account, repeat the above command, and notice how your name appears. >Fix: The following patch employs a different method from that in RELENG_4. The latter uses something to the effect of, ypcat passwd | cat - /etc/passwd which fixes the problem, but is not the Right Way(tm). The following patch uses pw(8) to do the dirty work. Index: send-pr.sh =================================================================== RCS file: /st/src/FreeBSD/src/gnu/usr.bin/send-pr/send-pr.sh,v retrieving revision 1.20 diff -u -r1.20 send-pr.sh --- send-pr.sh 2000/10/29 22:11:39 1.20 +++ send-pr.sh 2001/01/16 06:23:59 @@ -58,8 +58,8 @@ # host-dependent. MAIL_AGENT="${MAIL_AGENT:-/usr/sbin/sendmail -oi -t}" -# How to read the passwd database. -PASSWD="cat /etc/passwd" +# Path to pw(8) +PW="/usr/sbin/pw" ECHON=bsd @@ -97,7 +97,7 @@ PTEMP=`mktemp -t p` || exit 1 # Must use temp file due to incompatibilities in quoting behavior # and to protect shell metacharacters in the expansion of $LOGNAME - $PASSWD | grep "^$LOGNAME:" | awk -F: '{print $5}' | sed -e 's/,.*//' > $PTEMP + $PW usershow $LOGNAME | awk -F: '{ print $8 }' | sed -e 's/,.*//' > $PTEMP ORIGINATOR="`cat $PTEMP`" rm -f $PTEMP fi >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:30:27 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C586137B698 for ; Mon, 15 Jan 2001 23:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7U3400371; Mon, 15 Jan 2001 23:30:03 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 23:30:03 -0800 (PST) Message-Id: <200101160730.f0G7U3400371@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Soren Schmidt Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Reply-To: Soren Schmidt Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24368; it has been noted by GNATS. From: Soren Schmidt To: klui@cup.hp.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Date: Tue, 16 Jan 2001 08:24:40 +0100 (CET) It seems klui@cup.hp.com wrote: > >Description: > I, like a lot of other people with the Asus A7V, have drive timeouts > when using the onboard ATA100 controller with UDMA drives. The kernel > configuration says that if ATA_ENABLE_ATAPI_DMA isn't defined, DMA mode > is not used. However, I have found that, for my A7V anyway, DMA is > always enabled during boot time and /etc/sysctl.conf doesn't always turn > off DMA mode before I get the timeouts and PIO fallback routines. The ATA_ENABLE_ATAPI_DMA only switches the _ATAPI_ DMA support, for _ATA_ disks it is enabled if the HW says it supports it. I think the problem here might be that some of the newer VIA based board might in fact have a VIA '686B southbridge, which apparantly needs different setups. Could you mail me the dmesg output from a verbose boot, and the output from a pciconf -l please ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:30:27 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6057237B404 for ; Mon, 15 Jan 2001 23:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7U2d00326; Mon, 15 Jan 2001 23:30:02 -0800 (PST) (envelope-from gnats) Date: Mon, 15 Jan 2001 23:30:02 -0800 (PST) Message-Id: <200101160730.f0G7U2d00326@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Soren Schmidt Subject: Re: kern/24367: ATA driver finds non-existent drives Reply-To: Soren Schmidt Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24367; it has been noted by GNATS. From: Soren Schmidt To: klui@cup.hp.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24367: ATA driver finds non-existent drives Date: Tue, 16 Jan 2001 08:21:52 +0100 (CET) It seems klui@cup.hp.com wrote: > >Description: > Sometimes, the ATA driver will find drives that doesn't exist on my A7V > system. When this happens, I get the following error: > ata3-slave: ata_command: timeout waiting for intr > ata3-slave: identify failed > ata3-master: ata_command: timeout waiting for intr > ata3-master: identify failed > > My A7V (board rev 1.02, BIOS 1005C) with Duron (800MHz) has a UDMA66 > drive on the Primary ATA100 (Promise, onboard) controller (only drive on > this cable) as master, and a DVD-ROM drive on the Secondary IDE > controller (only drive on this cable) as master. Uhm firstly the Promise isn't the primary adaptor on those baords, the VIA '686 is, that migth lead to some confusion. > On boot, I sometimes see the following: > [DVD-ROM/master] > atapci0: port 0xd800-0xd80f at device 4.1 on pci0 > ata1: at 0x170 irq 15 on atapci0 > . > . > . > atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9 > 407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 > on pci0 > [Quantum Fireball Plus LM/master] > ata2: at 0xa000 on atapci1 > [??] > ata3: at 0x9400 on atapci1 > > Sometimes, ata3 doesn't show up, but sometimes, it does. My current > ATA settings are all PIO. I have no cable dangling off the secondary > ATA100 connector. How have you setup your BIOS ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:44:55 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4858F37B401; Mon, 15 Jan 2001 23:44:39 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7idS01916; Mon, 15 Jan 2001 23:44:39 -0800 (PST) (envelope-from mjacob) Date: Mon, 15 Jan 2001 23:44:39 -0800 (PST) From: Message-Id: <200101160744.f0G7idS01916@freefall.freebsd.org> To: jseidel@kodiak.sdsmt.edu, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/13352: No support for Promise Ultra/66 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: No support for Promise Ultra/66 State-Changed-From-To: open->closed State-Changed-By: mjacob State-Changed-When: Mon Jan 15 23:44:12 PST 2001 State-Changed-Why: There is support for Ultra/66 Promise controllers now. http://www.freebsd.org/cgi/query-pr.cgi?pr=13352 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:52:41 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C686337B400; Mon, 15 Jan 2001 23:52:22 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7qM703245; Mon, 15 Jan 2001 23:52:22 -0800 (PST) (envelope-from mjacob) Date: Mon, 15 Jan 2001 23:52:22 -0800 (PST) From: Message-Id: <200101160752.f0G7qM703245@freefall.freebsd.org> To: tdwyer@bigpond.com, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/17779: ADIC 1200d (DAT changer) and Symbios SCSI controller: does not work as expected using chio Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: ADIC 1200d (DAT changer) and Symbios SCSI controller: does not work as expected using chio State-Changed-From-To: open->feedback State-Changed-By: mjacob State-Changed-When: Mon Jan 15 23:51:31 PST 2001 State-Changed-Why: Is this still a problem? http://www.freebsd.org/cgi/query-pr.cgi?pr=17779 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:55:17 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 39A9837B401; Mon, 15 Jan 2001 23:55:01 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7t1I03529; Mon, 15 Jan 2001 23:55:01 -0800 (PST) (envelope-from mjacob) Date: Mon, 15 Jan 2001 23:55:01 -0800 (PST) From: Message-Id: <200101160755.f0G7t1I03529@freefall.freebsd.org> To: campt@miralink.com, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21139: IBM DNES drives need 'quirk table' entry. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: IBM DNES drives need 'quirk table' entry. State-Changed-From-To: open->feedback State-Changed-By: mjacob State-Changed-When: Mon Jan 15 23:53:28 PST 2001 State-Changed-Why: Are any of these drives still around and/or is this a problem? http://www.freebsd.org/cgi/query-pr.cgi?pr=21139 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:56:33 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6639E37B400; Mon, 15 Jan 2001 23:56:17 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7uF103744; Mon, 15 Jan 2001 23:56:15 -0800 (PST) (envelope-from mjacob) Date: Mon, 15 Jan 2001 23:56:15 -0800 (PST) From: Message-Id: <200101160756.f0G7uF103744@freefall.freebsd.org> To: christian@it-netservice.de, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21736: Source-tree broken, can't compile Kernel Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Source-tree broken, can't compile Kernel State-Changed-From-To: open->feedback State-Changed-By: mjacob State-Changed-When: Mon Jan 15 23:55:39 PST 2001 State-Changed-Why: Is this still a problem for you? http://www.freebsd.org/cgi/query-pr.cgi?pr=21736 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Mon Jan 15 23:58:31 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 469DC37B401; Mon, 15 Jan 2001 23:58:15 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G7wF204000; Mon, 15 Jan 2001 23:58:15 -0800 (PST) (envelope-from mjacob) Date: Mon, 15 Jan 2001 23:58:15 -0800 (PST) From: Message-Id: <200101160758.f0G7wF204000@freefall.freebsd.org> To: klh@netcom.com, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/16016: cam/scsi/scsi_da.c: Fujitsu M2952 doesn't like synch cache either Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: cam/scsi/scsi_da.c: Fujitsu M2952 doesn't like synch cache either State-Changed-From-To: open->feedback State-Changed-By: mjacob State-Changed-When: Mon Jan 15 23:57:46 PST 2001 State-Changed-Why: Per Justin's request, can you supply the requested info or state that this is no longer a problem? http://www.freebsd.org/cgi/query-pr.cgi?pr=16016 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 0: 0:48 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8564037B400; Tue, 16 Jan 2001 00:00:31 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G80Uh04430; Tue, 16 Jan 2001 00:00:30 -0800 (PST) (envelope-from mjacob) Date: Tue, 16 Jan 2001 00:00:30 -0800 (PST) From: Message-Id: <200101160800.f0G80Uh04430@freefall.freebsd.org> To: root@chv.ukrpack.net, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21683: Unable to compile kernel after CVSUP. CVSUP was made 30.09.2000 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Unable to compile kernel after CVSUP. CVSUP was made 30.09.2000 State-Changed-From-To: open->closed State-Changed-By: mjacob State-Changed-When: Mon Jan 15 23:59:54 PST 2001 State-Changed-Why: I know that I've used cvsup and built 3.5 since this PR was filed. http://www.freebsd.org/cgi/query-pr.cgi?pr=21683 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 1:50:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1721E37B69B for ; Tue, 16 Jan 2001 01:50:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0G9o5h19957; Tue, 16 Jan 2001 01:50:05 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 01:50:05 -0800 (PST) Message-Id: <200101160950.f0G9o5h19957@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ken Lui Subject: Re: kern/24367: ATA driver finds non-existent drives Reply-To: Ken Lui Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24367; it has been noted by GNATS. From: Ken Lui To: Soren Schmidt Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24367: ATA driver finds non-existent drives Date: Tue, 16 Jan 2001 01:40:41 -0800 (PST) On Tue, 16 Jan 2001, Soren Schmidt wrote: > Uhm firstly the Promise isn't the primary adaptor on those baords, the > VIA '686 is, that migth lead to some confusion. Sorry about the confusing terminology. I read the labels off of the A7V (1.02) motherboard. The Promise ATA100 is labeled Primary/Secondary ATA100 while the '686A is Primary/Secondary IDE. > > > On boot, I sometimes see the following: > > [DVD-ROM/master] > > atapci0: port 0xd800-0xd80f at device 4.1 on pci0 > > ata1: at 0x170 irq 15 on atapci0 > > . > > . > > . > > atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9 > > 407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 > > on pci0 > > [Quantum Fireball Plus LM/master] > > ata2: at 0xa000 on atapci1 > > [??] > > ata3: at 0x9400 on atapci1 > > > > Sometimes, ata3 doesn't show up, but sometimes, it does. My current > > ATA settings are all PIO. I have no cable dangling off the secondary > > ATA100 connector. > > How have you setup your BIOS ? When I was using this configuration, I was had the system boot in this order: DVD-ROM (on VIA '686 secondary-master) ATA100/SCSI (Promise primary-master) Floppy IDE (disabled, as I didn't have any other drives attached) The boot order of the Promise/SCSI is as per above (ATA100, then SCSI). My SCSI card isn't installed. Anything in particular you're interested in my BIOS configuration? I also get this behavior if I run only on the VIA '686 primary and secondary connectors: UDMA66 drive on primary-master DVD-ROM on secondary-master Boot order is DVD-ROM IDE floppy ATA100/SCSI is disabled I've also disabled the Promise ATA100 bus's BIOS in my current setup. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 2: 0:34 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6957937B69C for ; Tue, 16 Jan 2001 02:00:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GA05n21132; Tue, 16 Jan 2001 02:00:05 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 02:00:05 -0800 (PST) Message-Id: <200101161000.f0GA05n21132@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ken Lui Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Reply-To: Ken Lui Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24368; it has been noted by GNATS. From: Ken Lui To: Soren Schmidt Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Date: Tue, 16 Jan 2001 01:51:45 -0800 (PST) On Tue, 16 Jan 2001, Soren Schmidt wrote: > I think the problem here might be that some of the newer VIA based > board might in fact have a VIA '686B southbridge, which apparantly > needs different setups. My A7V has a '686A southbridge--clearly marked on the BGA chip. Only the A7V133 has '686Bs. > Could you mail me the dmesg output from a verbose boot, and the > output from a pciconf -l please ? Here you go. This is my current config though, not using the Promise ATA100 bus: dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Mon Jan 15 22:24:24 PST 2001 root@blck:/usr/src/sys/compile/A7V Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 807192760 Hz CPU: AMD Duron(tm) Processor (807.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x631 Stepping = 1 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 134135808 (130992K bytes) avail memory = 127459328 (124472K bytes) Preloaded elf kernel "kernel" at 0xc031f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031f09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 5 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 5 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered pci0: at 12.0 irq 11 ed0: port 0xa400-0xa41f irq 5 at device 13.0 on pci0 ed0: address 00:80:c8:fd:90:ae, type NE2000 (16 bit) atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 on pci0 ata2: at 0xa000 on atapci1 ata3: at 0x9400 on atapci1 pcib1: on motherboard pci2: on pcib1 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,0x64 on isa0 atkbd0: flags 0x1 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 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ata2-slave: ata_command: timeout waiting for intr ata2-slave: identify failed ata2-master: ata_command: timeout waiting for intr ata2-master: identify failed ata3-slave: ata_command: timeout waiting for intr ata3-slave: identify failed ata3-master: ata_command: timeout waiting for intr ata3-master: identify failed ad0: 19595MB [39813/16/63] at ata0-master UDMA66 acd0: DVD-ROM at ata1-master using WDMA2 pciconf -l: chip0@pci0:0:0: class=0x060000 card=0x80331043 chip=0x03051106 rev=0x02 hdr=0x00 pcib2@pci0:1:0: class=0x060400 card=0x00000080 chip=0x83051106 rev=0x00 hdr=0x01 isab0@pci0:4:0: class=0x060100 card=0x80331043 chip=0x06861106 rev=0x22 hdr=0x00 atapci0@pci0:4:1: class=0x01018a card=0x00000000 chip=0x05711106 rev=0x10 hdr=0x00 uhci0@pci0:4:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00 uhci1@pci0:4:3: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00 chip1@pci0:4:4: class=0x060000 card=0x80331043 chip=0x30571106 rev=0x30 hdr=0x00 none0@pci0:12:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 ed0@pci0:13:0: class=0x020000 card=0x802910ec chip=0x802910ec rev=0x00 hdr=0x00 atapci1@pci0:17:0: class=0x018000 card=0x4d33105a chip=0x0d30105a rev=0x02 hdr=0x00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 2: 8: 1 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8CAC137B401; Tue, 16 Jan 2001 02:07:44 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GA7iI24203; Tue, 16 Jan 2001 02:07:44 -0800 (PST) (envelope-from dwmalone) Date: Tue, 16 Jan 2001 02:07:44 -0800 (PST) From: Message-Id: <200101161007.f0GA7iI24203@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, dwmalone@FreeBSD.org Subject: Re: bin/24369: typo "millenium" in units.lib Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: typo "millenium" in units.lib Responsible-Changed-From-To: freebsd-bugs->dwmalone Responsible-Changed-By: dwmalone Responsible-Changed-When: Tue Jan 16 02:07:16 PST 2001 Responsible-Changed-Why: I'll MFC in a few days. http://www.freebsd.org/cgi/query-pr.cgi?pr=24369 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 2:10:29 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4860737B401 for ; Tue, 16 Jan 2001 02:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GAA5C24585; Tue, 16 Jan 2001 02:10:05 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 02:10:05 -0800 (PST) Message-Id: <200101161010.f0GAA5C24585@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ken Lui Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Reply-To: Ken Lui Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24368; it has been noted by GNATS. From: Ken Lui To: Soren Schmidt Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/24368: Not having ATA_ENABLE_ATAPI_DMA still has DMA enabled in the kernel Date: Tue, 16 Jan 2001 02:02:08 -0800 (PST) On Tue, 16 Jan 2001, Soren Schmidt wrote: > Could you mail me the dmesg output from a verbose boot, and the > output from a pciconf -l please ? Oops, I just realized the dmesg output from a verbose boot is not the same as a normal dmesg. Here's the output from a boot -v. Ken Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Mon Jan 15 22:24:24 PST 2001 root@blck:/usr/src/sys/compile/A7V Calibrating clock(s) ... TSC clock: 807163548 Hz, i8254 clock: 1193146 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 Timecounter "TSC" frequency 807193540 Hz CPU: AMD Duron(tm) Processor (807.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x631 Stepping = 1 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 134135808 (130992K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00338000 - 0x07fe3fff, 130727936 bytes (31916 pages) avail memory = 127459328 (124472K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f92a0 bios32: Entry = 0xf0f50 (c00f0f50) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x1150 pnpbios: Found PnP BIOS data at 0xc00fc2b0 pnpbios: Entry = f0000:c2e0 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 000f67c0 Preloaded elf kernel "kernel" at 0xc031f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031f0a8. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80000060 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=03051106) pcib-: pcib0 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=03051106) pcib0: on motherboard found-> vendor=0x1106, dev=0x0305, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e4000000, size 26 found-> vendor=0x1106, dev=0x8305, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1106, dev=0x0686, revid=0x22 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x10 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000d800, size 4 found-> vendor=0x1106, dev=0x3038, revid=0x10 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=5 map[20]: type 1, range 32, base 0000d400, size 5 found-> vendor=0x1106, dev=0x3038, revid=0x10 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=5 map[20]: type 1, range 32, base 0000d000, size 5 found-> vendor=0x1106, dev=0x3057, revid=0x30 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e2800000, size 14 map[14]: type 1, range 32, base e3800000, size 23 found-> vendor=0x10ec, dev=0x8029, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base 0000a400, size 5 found-> vendor=0x105a, dev=0x0d30, revid=0x02 class=01-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000a000, size 3 map[14]: type 1, range 32, base 00009800, size 2 map[18]: type 1, range 32, base 00009400, size 3 map[1c]: type 1, range 32, base 00009000, size 2 map[20]: type 1, range 32, base 00008800, size 6 map[24]: type 1, range 32, base e2000000, size 17 pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd800 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd808 ata1: mask=01 status0=50 status1=ff ata1: mask=01 ostat0=50 ostat2=ff ata1-master: ATAPI probe a=14 b=eb ata1: mask=01 status0=00 status1=ff ata1: devices=04 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 5 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 5 at device 4.3 on pci0 using shared irq5. usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered pci0: (vendor=0x102b, dev=0x0519) at 12.0 irq 11 ed0: port 0xa400-0xa41f irq 5 at device 13.0 on pci0 bpf: ed0 attached ed0: address 00:80:c8:fd:90:ae, type NE2000 (16 bit) atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xe2000000-0xe201ffff irq 10 at device 17.0 on pci0 ata-: ata2 exists, using next available unit number ata2: iobase=0xa000 altiobase=0x9802 bmaddr=0x8800 ata2: mask=00 status0=ff status1=ff ata2: probe allocation failed ata3: iobase=0x9400 altiobase=0x9002 bmaddr=0x8808 ata3: mask=00 status0=ff status1=ff ata3: probe allocation failed 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=03051106) pci-: pci1 exists, using next available unit number pcib1: on motherboard pci2: on pcib1 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number ed-: ed0 exists, using next available unit number 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 ata4 failed to probe at port 0x1f0 irq 14 on isa0 ata5 failed to probe at port 0x170 irq 15 on isa0 adv0 failed to probe at port 0x330 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-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 60 4f 50 83 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 60 4f 50 83 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 60 4f 50 83 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: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP 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/8 bytes threshold ed1 failed to probe at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached Linux-ELF exec handler installed ata0-master: success setting UDMA4 on VIA chip Creating DISK ad0 Creating DISK wd0 ad0: ATA-5 disk at ata0-master ad0: 19595MB (40132503 sectors), 39813 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 ad0: 19595MB [39813/16/63] at ata0-master UDMA66 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting WDMA2 on VIA chip acd0: DVD-ROM drive at ata1 as master acd0: read 687KB/s (5500KB/s), 512KB buffer, WDMA2 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 16064999, size 16064937 : OK ad0s2: type 0xa5, start 16065000, end = 40130369, size 24065370 : OK start_init: trying /sbin/init splash: image decoder found: blank_saver pciconf -l su> pciconf -l chip0@pci0:0:0: class=0x060000 card=0x80331043 chip=0x03051106 rev=0x02 hdr=0x00 pcib2@pci0:1:0: class=0x060400 card=0x00000080 chip=0x83051106 rev=0x00 hdr=0x01 isab0@pci0:4:0: class=0x060100 card=0x80331043 chip=0x06861106 rev=0x22 hdr=0x00 atapci0@pci0:4:1: class=0x01018a card=0x00000000 chip=0x05711106 rev=0x10 hdr=0x00 uhci0@pci0:4:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00 uhci1@pci0:4:3: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00 chip1@pci0:4:4: class=0x060000 card=0x80331043 chip=0x30571106 rev=0x30 hdr=0x00 none0@pci0:12:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 ed0@pci0:13:0: class=0x020000 card=0x802910ec chip=0x802910ec rev=0x00 hdr=0x00 atapci1@pci0:17:0: class=0x018000 card=0x4d33105a chip=0x0d30105a rev=0x02 hdr=0x00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 2:50:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id AE0D737B69B for ; Tue, 16 Jan 2001 02:50:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GAo3p29434; Tue, 16 Jan 2001 02:50:03 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7CB7C37B69B for ; Tue, 16 Jan 2001 02:44:12 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GAiCb28930; Tue, 16 Jan 2001 02:44:12 -0800 (PST) (envelope-from nobody) Message-Id: <200101161044.f0GAiCb28930@freefall.freebsd.org> Date: Tue, 16 Jan 2001 02:44:12 -0800 (PST) From: Jens.Schweikhardt@marconi.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: bin/24377: make(1) does not correctly substitute in internal macros like $(@F:.o=.c) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24377 >Category: bin >Synopsis: make(1) does not correctly substitute in internal macros like $(@F:.o=.c) >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 02:50:03 PST 2001 >Closed-Date: >Last-Modified: >Originator: Jens Schweikhardt >Release: 4.2-RELEASE >Organization: Marconi >Environment: FreeBSD bk4957 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 >Description: hello, world\n It seems, make(1) doesn't understand substitutions in what the POSIX standard calls internal variables ($@, $%, $?, $< and $*). In the following example, the intent is to substitute any *.o in a *.c, i.e. echo foo.c. >How-To-Repeat: $ cat Makefile .POSIX: foo.o: echo $(@F:.o=.c) $ /usr/bin/make echo foo.o.o=.c) Syntax error: ")" unexpected *** Error code 2 Stop in /usr/home/sje2bk. GNU make works correctly, as well as Sun's /usr/ccs/bin/make: $ /usr/local/bin/gmake echo foo.c foo.c $ Is this a bug, a feature, lack of interest in POSIX conformance or am I just confused? :-) >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 3:30:36 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BA37B37B69F for ; Tue, 16 Jan 2001 03:30:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GBU5I35363; Tue, 16 Jan 2001 03:30:05 -0800 (PST) (envelope-from gnats) Received: from sep.hamburg.com (sep.hamburg.com [194.64.112.14]) by hub.freebsd.org (Postfix) with ESMTP id A518337B404 for ; Tue, 16 Jan 2001 03:21:36 -0800 (PST) Received: (from hmo@localhost) by sep.hamburg.com (8.11.1/8.11.1/hmo03sep00) id f0GBLR346483; Tue, 16 Jan 2001 12:21:27 +0100 (CET) (envelope-from hmo) Message-Id: <200101161121.f0GBLR346483@sep.hamburg.com> Date: Tue, 16 Jan 2001 12:21:27 +0100 (CET) From: send-pr@oldach.net Reply-To: send-pr@oldach.net To: FreeBSD-gnats-submit@freebsd.org Cc: hmo@sep.hamburg.com X-Send-Pr-Version: 3.2 Subject: kern/24378: ahc broken in STABLE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24378 >Category: kern >Synopsis: ahc broken in STABLE >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 03:30:05 PST 2001 >Closed-Date: >Last-Modified: >Originator: Helge Oldach >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: The ahc/aic driver changes that were MFC'd to -STABLE between 20th December 2000 and yesterday (15th January 2001) break a HP NetServer 4/66 LC (EISA box) with AIC-7770 twin channel controller. >Description: dmesg of a working 4.2-STABLE of 20th December 2000: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Wed Dec 20 14:55:40 CET 2000 toor@com:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping = 5 Features=0x3 real memory = 41943040 (40960K bytes) config> eisa 12 config> di adv0 config> di aha0 config> di aic0 config> di ata1 config> di bt0 config> di cs0 config> di ed0 config> di fe0 config> di ie0 config> di lnc0 config> di pcic0 config> di sn0 config> q avail memory = 36581376 (35724K bytes) Preloaded elf kernel "kernel" at 0xc0438000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043809c. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface eisa0: on motherboard mainboard0: on eisa0 slot 0 ep0: <3Com 3C579-BNC EISA Network Adapter> at 0x1000-0x100f, 0x1c80-0x1c89 ep0: irq 5 (level) on eisa0 slot 1 ep0: Ethernet address 00:20:af:73:f3:48 ahc0: at 0xbc00-0xbcff, irq 15 (level) ahc0: on eisa0 slot 11 aic7770: Twin Channel, A SCSI Id=7, B SCSI Id=7, primary A, 4/255 SCBs isa0: on motherboard 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,0x64 on isa0 atkbd0: flags 0x1 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 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 Waiting 15 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/da0s1a dmesg of a broken kernel as of today: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Tue Jan 16 08:13:04 CET 2001 toor@com:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping = 5 Features=0x3 real memory = 41943040 (40960K bytes) config> eisa 12 config> di adv0 config> di aha0 config> di aic0 config> di ata1 config> di bt0 config> di cs0 config> di ed0 config> di fe0 config> di ie0 config> di lnc0 config> di pcic0 config> di sn0 config> q avail memory = 36581376 (35724K bytes) Preloaded elf kernel "kernel.broken" at 0xc043e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043e0a4. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface eisa0: on motherboard mainboard0: on eisa0 slot 0 ep0: <3Com 3C579-BNC EISA Network Adapter> at 0x1000-0x100f, 0x1c80-0x1c89 ep0: irq 5 (level) on eisa0 slot 1 ep0: Ethernet address 00:20:af:73:f3:48 ahc0: at 0xbc00-0xbcff, irq 15 (level) ahc0: on eisa0 slot 11 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01af866 stack pointer = 0x10:0xc045fea0 frame pointer = 0x10:0xc045fea0 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 = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 3:30:37 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D94E137B6A0 for ; Tue, 16 Jan 2001 03:30:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GBU5C35372; Tue, 16 Jan 2001 03:30:05 -0800 (PST) (envelope-from gnats) Received: from sep.hamburg.com (sep.hamburg.com [194.64.112.14]) by hub.freebsd.org (Postfix) with ESMTP id 0792737B699 for ; Tue, 16 Jan 2001 03:24:48 -0800 (PST) Received: (from hmo@localhost) by sep.hamburg.com (8.11.1/8.11.1/hmo03sep00) id f0GBKXS46352; Tue, 16 Jan 2001 12:20:33 +0100 (CET) (envelope-from hmo) Message-Id: <200101161120.f0GBKXS46352@sep.hamburg.com> Date: Tue, 16 Jan 2001 12:20:33 +0100 (CET) From: send-pr@oldach.net Reply-To: send-pr@oldach.net To: FreeBSD-gnats-submit@freebsd.org Cc: send-pr@oldach.net X-Send-Pr-Version: 3.2 Subject: kern/24379: ahc broken in STABLE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24379 >Category: kern >Synopsis: ahc broken in STABLE >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 03:30:05 PST 2001 >Closed-Date: >Last-Modified: >Originator: Helge Oldach >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: The ahc/aic driver changes that were MFC'd to -STABLE between 20th December 2000 and yesterday (15th January 2001) break a HP NetServer 4/66 LC (EISA box) with AIC-7770 twin channel controller. >Description: dmesg of a working 4.2-STABLE of 20th December 2000: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Wed Dec 20 14:55:40 CET 2000 toor@com:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping = 5 Features=0x3 real memory = 41943040 (40960K bytes) config> eisa 12 config> di adv0 config> di aha0 config> di aic0 config> di ata1 config> di bt0 config> di cs0 config> di ed0 config> di fe0 config> di ie0 config> di lnc0 config> di pcic0 config> di sn0 config> q avail memory = 36581376 (35724K bytes) Preloaded elf kernel "kernel" at 0xc0438000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043809c. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface eisa0: on motherboard mainboard0: on eisa0 slot 0 ep0: <3Com 3C579-BNC EISA Network Adapter> at 0x1000-0x100f, 0x1c80-0x1c89 ep0: irq 5 (level) on eisa0 slot 1 ep0: Ethernet address 00:20:af:73:f3:48 ahc0: at 0xbc00-0xbcff, irq 15 (level) ahc0: on eisa0 slot 11 aic7770: Twin Channel, A SCSI Id=7, B SCSI Id=7, primary A, 4/255 SCBs isa0: on motherboard 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,0x64 on isa0 atkbd0: flags 0x1 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 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 Waiting 15 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/da0s1a dmesg of a broken kernel as of today: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Tue Jan 16 08:13:04 CET 2001 toor@com:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping = 5 Features=0x3 real memory = 41943040 (40960K bytes) config> eisa 12 config> di adv0 config> di aha0 config> di aic0 config> di ata1 config> di bt0 config> di cs0 config> di ed0 config> di fe0 config> di ie0 config> di lnc0 config> di pcic0 config> di sn0 config> q avail memory = 36581376 (35724K bytes) Preloaded elf kernel "kernel.broken" at 0xc043e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043e0a4. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface eisa0: on motherboard mainboard0: on eisa0 slot 0 ep0: <3Com 3C579-BNC EISA Network Adapter> at 0x1000-0x100f, 0x1c80-0x1c89 ep0: irq 5 (level) on eisa0 slot 1 ep0: Ethernet address 00:20:af:73:f3:48 ahc0: at 0xbc00-0xbcff, irq 15 (level) ahc0: on eisa0 slot 11 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01af866 stack pointer = 0x10:0xc045fea0 frame pointer = 0x10:0xc045fea0 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 = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 4: 1: 6 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 10AE337B69E; Tue, 16 Jan 2001 04:00:49 -0800 (PST) Received: (from sobomax@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GC0SQ37576; Tue, 16 Jan 2001 04:00:28 -0800 (PST) (envelope-from sobomax) Date: Tue, 16 Jan 2001 04:00:28 -0800 (PST) From: Message-Id: <200101161200.f0GC0SQ37576@freefall.freebsd.org> To: andrew@ugh.net.au, sobomax@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/24310: pkg_add has a misplaced ) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: pkg_add has a misplaced ) State-Changed-From-To: open->closed State-Changed-By: sobomax State-Changed-When: Tue Jan 16 03:56:44 PST 2001 State-Changed-Why: Similar fix was committed. Anyway, thank you for reporting! http://www.freebsd.org/cgi/query-pr.cgi?pr=24310 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 6:30:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E851137B404 for ; Tue, 16 Jan 2001 06:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GEU1w61699; Tue, 16 Jan 2001 06:30:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C8D5737B698 for ; Tue, 16 Jan 2001 06:23:47 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GENlw61093; Tue, 16 Jan 2001 06:23:47 -0800 (PST) (envelope-from nobody) Message-Id: <200101161423.f0GENlw61093@freefall.freebsd.org> Date: Tue, 16 Jan 2001 06:23:47 -0800 (PST) From: john.r.king@bt.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24384: 4.1 Cant add entry to neighbour discovery table Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24384 >Category: misc >Synopsis: 4.1 Cant add entry to neighbour discovery table >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 06:30:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: John King >Release: FreeBSD 4.1 >Organization: BT >Environment: FreeBSD bsd 4.1-RELEASE FreeBSD 4.1-Release #0: Fri Dec 1 12:02:50 GMT 2000 root@bsd:/usr/src/sys/compile/GENERIC i386 >Description: I am trying to add an entry to the neighbour discovery table using ndp. The command I am using is: ndp -s aaaa:bbbb:cccc:dddd:eeee:ffff:8492:a829 0:90:27:9f:c9:2d Each time I try I get the same error message: cannot intuit interface index and type for aaaa:bbbb:cccc:dddd:eeee:ffff:8492:a829 I have even added an entry into the routing table to indicate the interface for that prefix but this does not seem to help. The entry from netstat -rn reads: aaaa:bbbb:cccc:dddd:eeee:ffff::/96 2001:618:5:0:290:27ff:fe9f:c92d UGSc fxp1 >How-To-Repeat: Run the command: ndp -s aaaa:bbbb:cccc:dddd:eeee:ffff:8492:a829 0:90:27:9f:c9:2d Error message is given on each occasion >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 6:50:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1A11C37B404 for ; Tue, 16 Jan 2001 06:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GEo2E14646; Tue, 16 Jan 2001 06:50:02 -0800 (PST) (envelope-from gnats) Received: from default.the.net (unknown [217.70.108.9]) by hub.freebsd.org (Postfix) with ESMTP id 694F537B401 for ; Tue, 16 Jan 2001 06:47:24 -0800 (PST) Received: (from semen@localhost) by default.the.net (8.11.1/8.11.0) id f0GEpT702670; Tue, 16 Jan 2001 20:51:29 +0600 (GMT+6) (envelope-from semen) Message-Id: <200101161451.f0GEpT702670@default.the.net> Date: Tue, 16 Jan 2001 20:51:29 +0600 (GMT+6) From: semenu@freebsd.org Reply-To: semenu@freebsd.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: conf/24385: Generic timezone entries wrong Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24385 >Category: conf >Synopsis: GMT+N and GMT-N timezones are wrong defined >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 06:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Semen A. Ustimenko >Release: FreeBSD 4.2-RELEASE i386 >Organization: >Environment: timezones defined in src/share/zoneinfo/etcetera >Description: The correct way to define an entry is to give an offset from GMT as a third parameter, not back offset. Even comment say this in src/share/zoneinfo/etcetera: # Earlier incarnations of this package were not POSIX-compliant, # and had lines such as # Zone GMT-12 -12 - GMT-1200 >How-To-Repeat: Try to use any of GMT+N or GMT-N timezones, and see your time shifts right in another way of what you supposed. >Fix: Index: src/share/zoneinfo/etcetera =================================================================== RCS file: /usr/home/ncvs/src/share/zoneinfo/etcetera,v retrieving revision 1.1.2.4 diff -c -r1.1.2.4 etcetera *** src/share/zoneinfo/etcetera 1999/01/21 21:35:07 1.1.2.4 --- src/share/zoneinfo/etcetera 2000/12/04 15:14:56 *************** *** 37,65 **** # zic -l GMT-12 # so we moved the names into the Etc subdirectory. ! Zone Etc/GMT-14 14 - GMT-14 # 14 hours ahead of GMT ! Zone Etc/GMT-13 13 - GMT-13 ! Zone Etc/GMT-12 12 - GMT-12 ! Zone Etc/GMT-11 11 - GMT-11 ! Zone Etc/GMT-10 10 - GMT-10 ! Zone Etc/GMT-9 9 - GMT-9 ! Zone Etc/GMT-8 8 - GMT-8 ! Zone Etc/GMT-7 7 - GMT-7 ! Zone Etc/GMT-6 6 - GMT-6 ! Zone Etc/GMT-5 5 - GMT-5 ! Zone Etc/GMT-4 4 - GMT-4 ! Zone Etc/GMT-3 3 - GMT-3 ! Zone Etc/GMT-2 2 - GMT-2 ! Zone Etc/GMT-1 1 - GMT-1 ! Zone Etc/GMT+1 -1 - GMT+1 ! Zone Etc/GMT+2 -2 - GMT+2 ! Zone Etc/GMT+3 -3 - GMT+3 ! Zone Etc/GMT+4 -4 - GMT+4 ! Zone Etc/GMT+5 -5 - GMT+5 ! Zone Etc/GMT+6 -6 - GMT+6 ! Zone Etc/GMT+7 -7 - GMT+7 ! Zone Etc/GMT+8 -8 - GMT+8 ! Zone Etc/GMT+9 -9 - GMT+9 ! Zone Etc/GMT+10 -10 - GMT+10 ! Zone Etc/GMT+11 -11 - GMT+11 ! Zone Etc/GMT+12 -12 - GMT+12 --- 37,65 ---- # zic -l GMT-12 # so we moved the names into the Etc subdirectory. ! Zone Etc/GMT-14 -14 - GMT-14 # 14 hours ahead of GMT ! Zone Etc/GMT-13 -13 - GMT-13 ! Zone Etc/GMT-12 -12 - GMT-12 ! Zone Etc/GMT-11 -11 - GMT-11 ! Zone Etc/GMT-10 -10 - GMT-10 ! Zone Etc/GMT-9 -9 - GMT-9 ! Zone Etc/GMT-8 -8 - GMT-8 ! Zone Etc/GMT-7 -7 - GMT-7 ! Zone Etc/GMT-6 -6 - GMT-6 ! Zone Etc/GMT-5 -5 - GMT-5 ! Zone Etc/GMT-4 -4 - GMT-4 ! Zone Etc/GMT-3 -3 - GMT-3 ! Zone Etc/GMT-2 -2 - GMT-2 ! Zone Etc/GMT-1 -1 - GMT-1 ! Zone Etc/GMT+1 1 - GMT+1 ! Zone Etc/GMT+2 2 - GMT+2 ! Zone Etc/GMT+3 3 - GMT+3 ! Zone Etc/GMT+4 4 - GMT+4 ! Zone Etc/GMT+5 5 - GMT+5 ! Zone Etc/GMT+6 6 - GMT+6 ! Zone Etc/GMT+7 7 - GMT+7 ! Zone Etc/GMT+8 8 - GMT+8 ! Zone Etc/GMT+9 9 - GMT+9 ! Zone Etc/GMT+10 10 - GMT+10 ! Zone Etc/GMT+11 11 - GMT+11 ! Zone Etc/GMT+12 12 - GMT+12 >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 7:11:44 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from thalvors.miralink.com (sub19-210.member.dsl-only.net [63.105.19.210]) by hub.freebsd.org (Postfix) with ESMTP id 175C937B69C; Tue, 16 Jan 2001 07:11:27 -0800 (PST) Received: by thalvors.miralink.com (Postfix, from userid 1003) id 9B0F7BB83F; Tue, 16 Jan 2001 07:10:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by thalvors.miralink.com (Postfix) with ESMTP id 95D8C4405C; Tue, 16 Jan 2001 07:10:40 -0800 (PST) Date: Tue, 16 Jan 2001 07:10:40 -0800 (PST) From: Tracy Camp To: mjacob@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/21139: IBM DNES drives need 'quirk table' entry. In-Reply-To: <200101160755.f0G7t1I03529@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 15 Jan 2001 mjacob@FreeBSD.org wrote: > Synopsis: IBM DNES drives need 'quirk table' entry. > > State-Changed-From-To: open->feedback > State-Changed-By: mjacob > State-Changed-When: Mon Jan 15 23:53:28 PST 2001 > State-Changed-Why: > Are any of these drives still around and/or is this a problem? It was the opinion from some of the developers (I forget who) that these drives where problably okay. I'm somewhat inclined to believe them, however I can attest that they have problems when coupled with adaptec2940UW controllers (haven't tried anything else...) so the problem may actually lie with the adaptec controller? Anyways somewhere or another on my particular combination of hardware the tagged queue size was not being set properly and the quirk entry fixed this. t. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=21139 > Tracy Camp Product Development Miralink Corp.PDX Portland OR 503-223-3140 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 7:18:49 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 73D0D37B401; Tue, 16 Jan 2001 07:18:30 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 331EC1360C; Tue, 16 Jan 2001 10:18:30 -0500 (EST) Date: Tue, 16 Jan 2001 10:18:30 -0500 From: Chris Faulhaber To: Tracy Camp Cc: mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21139: IBM DNES drives need 'quirk table' entry. Message-ID: <20010116101830.C66321@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Tracy Camp , mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org References: <200101160755.f0G7t1I03529@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from campt@thalvors.miralink.com on Tue, Jan 16, 2001 at 07:10:40AM -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 16, 2001 at 07:10:40AM -0800, Tracy Camp wrote: > On Mon, 15 Jan 2001 mjacob@FreeBSD.org wrote: > > > Synopsis: IBM DNES drives need 'quirk table' entry. > > > > State-Changed-From-To: open->feedback > > State-Changed-By: mjacob > > State-Changed-When: Mon Jan 15 23:53:28 PST 2001 > > State-Changed-Why: > > Are any of these drives still around and/or is this a problem? > It was the opinion from some of the developers (I forget who) that these > drives where problably okay. I'm somewhat inclined to believe them, > however I can attest that they have problems when coupled with > adaptec2940UW controllers (haven't tried anything else...) so the problem > may actually lie with the adaptec controller? Anyways somewhere or > another on my particular combination of hardware the tagged queue size was > not being set properly and the quirk entry fixed this. > My IBM DNES suffered a hardware failure a few months ago, so I cannot provide any more feedback. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 8:20:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8CD4937B401 for ; Tue, 16 Jan 2001 08:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GGK2E62305; Tue, 16 Jan 2001 08:20:02 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 08:20:02 -0800 (PST) Message-Id: <200101161620.f0GGK2E62305@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Garrett Wollman Subject: conf/24385: Generic timezone entries wrong Reply-To: Garrett Wollman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/24385; it has been noted by GNATS. From: Garrett Wollman To: semenu@FreeBSD.ORG Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: conf/24385: Generic timezone entries wrong Date: Tue, 16 Jan 2001 11:10:47 -0500 (EST) < Try to use any of GMT+N or GMT-N timezones, and see your > time shifts right in another way of what you supposed. These zones are included for compatibility with ancient UNIX systems. You are more likely to convince the TZ database developers to drop them altogether than you are to get them to change the definitions. In any case, FreeBSD will follow the practice of the TZ database. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 8:23:12 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D9F9337B401; Tue, 16 Jan 2001 08:22:51 -0800 (PST) Received: (from wollman@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GGMp862673; Tue, 16 Jan 2001 08:22:51 -0800 (PST) (envelope-from wollman) Date: Tue, 16 Jan 2001 08:22:51 -0800 (PST) From: Message-Id: <200101161622.f0GGMp862673@freefall.freebsd.org> To: semenu@freebsd.org, wollman@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: conf/24385: GMT+N and GMT-N timezones are wrong defined Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: GMT+N and GMT-N timezones are wrong defined State-Changed-From-To: open->closed State-Changed-By: wollman State-Changed-When: Tue Jan 16 08:21:57 PST 2001 State-Changed-Why: This database is externally maintained; any changes need to be coordinated with the originators. http://www.freebsd.org/cgi/query-pr.cgi?pr=24385 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 8:40:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1125937B404 for ; Tue, 16 Jan 2001 08:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GGe1R64463; Tue, 16 Jan 2001 08:40:01 -0800 (PST) (envelope-from gnats) Received: from hlmailer.hilliard.com (unknown [198.184.127.28]) by hub.freebsd.org (Postfix) with ESMTP id 6F65837B402 for ; Tue, 16 Jan 2001 08:30:51 -0800 (PST) Received: from fbsd.hilliard.com ([198.184.69.200]) by hlmailer.hilliard.com (Netscape Messaging Server 3.6) with ESMTP id AAA6478 for ; Tue, 16 Jan 2001 11:30:21 -0500 Received: (from root@localhost) by fbsd.hilliard.com (8.9.3/8.9.3) id LAA94810; Tue, 16 Jan 2001 11:30:49 -0500 (EST) (envelope-from cisco) Message-Id: <200101161630.LAA94810@fbsd.hilliard.com> Date: Tue, 16 Jan 2001 11:30:49 -0500 (EST) From: root@fbsd.hilliard.com Reply-To: root@fbsd.hilliard.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: i386/24387: Can't compile 4.2 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24387 >Category: i386 >Synopsis: 4.2 compile bombs at PERL build >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 08:40:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Michael Harpe >Release: FreeBSD 3.4-STABLE i386 >Organization: Hilliard-Lyons, Inc. >Environment: FreeBSD 4.2 CVSup'ed numerous times. This also happens when building from source tree shipped on the 4.2 CDROM set. >Description: make buildworld bombs out with the folllwing: cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl -static -o miniperl miniperlmain.o opmini.o /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): In function `Perl_pp_aassign': pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I have tried this with vanilla 4.2 sources and cvsup'ed sources as new as 1/16/2000. >How-To-Repeat: Do a make buildworld. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 9: 3: 5 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5FFAA37B400; Tue, 16 Jan 2001 09:02:48 -0800 (PST) Received: (from mjacob@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GH2m066941; Tue, 16 Jan 2001 09:02:48 -0800 (PST) (envelope-from mjacob) Date: Tue, 16 Jan 2001 09:02:48 -0800 (PST) From: Message-Id: <200101161702.f0GH2m066941@freefall.freebsd.org> To: campt@miralink.com, mjacob@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21139: IBM DNES drives need 'quirk table' entry. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: IBM DNES drives need 'quirk table' entry. State-Changed-From-To: feedback->closed State-Changed-By: mjacob State-Changed-When: Tue Jan 16 09:02:21 PST 2001 State-Changed-Why: Added quirk. We really gotta do a loader object for this stuff. http://www.freebsd.org/cgi/query-pr.cgi?pr=21139 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 10:50:27 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B97D037B6A3 for ; Tue, 16 Jan 2001 10:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GIo1f96376; Tue, 16 Jan 2001 10:50:01 -0800 (PST) (envelope-from gnats) Received: from iraun1.ira.uka.de (iraun1.ira.uka.de [129.13.10.90]) by hub.freebsd.org (Postfix) with ESMTP id 7982D37B69F for ; Tue, 16 Jan 2001 10:46:22 -0800 (PST) Received: from i30nb2.ira.uka.de by iraun1 (PP) with ESMTP; Tue, 16 Jan 2001 19:45:42 +0100 Received: (from esk@localhost) by i30nb2.ira.uka.de (8.11.1/8.11.1) id f0GIjbV02366; Tue, 16 Jan 2001 19:45:37 +0100 (CET) (envelope-from esk) Message-Id: <200101161845.f0GIjbV02366@i30nb2.ira.uka.de> Date: Tue, 16 Jan 2001 19:45:37 +0100 (CET) From: esk@ira.uka.de Reply-To: esk@ira.uka.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24390: Replacing old dir-symlinks when using /bin/ln Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24390 >Category: bin >Synopsis: Replacing old dir-symlinks when using /bin/ln >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 10:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Espen Skoglund >Release: FreeBSD 4.2-STABLE i386 >Organization: Karlsruhe Inversity >Environment: >Description: I'm wondering about the semantics of the replacement functionality in `ln' when the file to be replaced is a symlink to a directory. I would have thought that this should behave in the same manner as if the target of `ln' was a normal file (i.e., the old symlink would be deleted, and a new link would be installed). This is, however, not the case. What happens is that `ln' follows the symlink into the directory and tries to install a symlink there instead. Is this really the desired behaviour? >How-To-Repeat: ; mkdir foo ; chmod a-w foo ; ln -sf foo bar ; ln -sf foo bar ln: bar/foo: Permission denied >Fix: --- /usr/src/bin/ln/ln.c Mon Sep 18 04:07:11 2000 +++ ln.c Tue Jan 16 19:27:41 2001 @@ -162,7 +162,8 @@ } /* If the source is a directory, append the target's name. */ - if (isdir || ((exists = !stat(source, &sb)) && S_ISDIR(sb.st_mode))) { + if ((isdir || ((exists = !stat(source, &sb)) && S_ISDIR(sb.st_mode))) + && !(!lstat(source, &sb) && S_ISLNK(sb.st_mode))) { if ((p = strrchr(target, '/')) == NULL) p = target; else >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 11: 3:18 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id EB15637B69F; Tue, 16 Jan 2001 11:03:00 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA08328; Tue, 16 Jan 2001 14:02:56 -0500 (EST) Date: Tue, 16 Jan 2001 14:02:56 -0500 (EST) From: "Matthew N. Dodd" To: jau@iki.fi Cc: freebsd-gnats-submit@FreeBSD.ORG, GNATS Management , freebsd-bugs@FreeBSD.ORG Subject: Re: kern/24100: Having a 3c589 PCMCIA/PCCARD inserted prevents boot or crashes a Dell Latitude 366 laptop In-Reply-To: <200101060918.f069IUA76950@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 6 Jan 2001 jau@iki.fi wrote: > The system will invariably go south immediately after the ppi0 has > been reported during autoconfig. Sounds like an interrupt conflict. -- | 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-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 11: 9:18 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from relay1.9netave.com (unknown [216.156.2.49]) by hub.freebsd.org (Postfix) with ESMTP id F2D3A37B401 for ; Tue, 16 Jan 2001 11:08:56 -0800 (PST) Received: from www-u-037.9netave.com (www-u-037.9netave.com [216.22.151.137]) by relay1.9netave.com (8.9.3/8.8.8) with ESMTP id OAA61730 for ; Tue, 16 Jan 2001 14:08:43 -0500 (EST) Received: (from ux371078@localhost) by www-u-037.9netave.com (8.9.3/8.8.8) id OAA63227 for bugs@freebsd.org; Tue, 16 Jan 2001 14:08:43 -0500 (EST) Date: Tue, 16 Jan 2001 14:08:43 -0500 (EST) Message-Id: <200101161908.OAA63227@www-u-037.9netave.com> Subject: Home delivery of agoodblackman.com From: info@agoodblackman.com To: bugs@freebsd.org Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello from agoodblackman.com, the only 100% Black-owned web site dedicated to celebrating the beauty, honor the history and continue the legacy of excellence of Black men. HELP SPREAD THE WORD BY FORWARDING THIS INFORMATION TO ALL THE EMAIL RECIPIENTS IN YOUR ADDRESS BOOK! Click here to unsubscribe or copy and paste into browser: http://www.agoodblackman.com/cgi-bin/ml10/ml10_00314/main/mailpub.cgi Here's your Home Delivery for January 2001 *********************************************** This Month's Special Announcement *********************************************** Currently, agoodblackman.com is being funded exclusively by D. Brown and is staffed entirely by her one volunteer. We believe that agoodblackman.com will make a powerful, positive impact on the Internet and African American community. In order to achieve this, we'll need much more funding than an individual alone can currently provide. So, we have developed a modest advertising program that allows companies, organizations and individuals who also believe in us and believe in the mission of agoodblackman.com to help us keep this site alive. We already have the talent and tools required to make agoodblackman.com happen. We’ve already planted the seeds of revolution. All we need now is the funding to maintain our presence on The World Wide Web. Check out our advertising and sponsorship opportunities at: http://www.agoodblackman.com/advertising.shtml *********************************************** This Month's Legacy of Excellence *********************************************** Happy New Year! Welcome to agoodblackman.com and to the new millennium. Many thanks for the emails and letters in support of AGBM. In 2000, AGBM received comments from all over the world. We look forward to another year of providing information and inspiration to our visitors. Join us as we continue our mission to celebrate the beauty, honor the history and continue the legacy of excellence of Black men. · Get home delivery of agoodblackman.com. · Read excerpts from: That Old Black Magic: Essays, Images & Verse on the Joys of Loving Black Men · Check out the 2000 "Year in Review" archives · Order agoodblackman.com screensavers · Post your salute in our guest book · Post your thoughts on our FREE bulletin board *********************************************** FEATURES *********************************************** We celebrate the love of family in our heritage, in our traditions and in the hopes and dreams we pass on to our children. From December 26 through January 1, Kwanzaa is celebrated. Kwanzaa is an original African-American holiday created by Dr. Maulana Karenga. This month with the help of Vernon Simms, AGBM is proud to present Black men as the embodiment of the seven principles of Kwanzaa. Click the link to visit the web site. · Principle 1: Umoja (unity) Elijah Muhammad · Principle 2: Kujichagulia (self determination) Marcus Garvey · Principle 3: Ujima (collective work and responsibility) Adam Clayton Powell · Principle 4: Ujamaa (cooperative economics) Reginald Lewis · Principle 5: Nia (purpose) Malcolm X · Principle 6: Kuumba (creativity) Paul Robeson · Principle 7: Imani (faith) Rev. Dr. Martin Luther King, Jr. Be certain to visit the official Kwanzaa web site of Dr. Maulana Kerenga. *********************************************** From the Desk of George E. Curry *********************************************** For the new year, AGBM is launching its newest section "From The Desk Of" with feature articles by syndicated columnist and AGBM online partner, George E. Curry. Mr. Curry is the former editor-in-chief of Emerge: Black America's Newsmagazine. His submissions for January 2001 are: n Special Report: The End of Kemba’s Nightmare n George W. Bush Tries To Bypass Black Leaders *********************************************** Reflections on Black History *********************************************** AGBM is honored to feature the work of Sun Reporter and journalist, Mr. Thomas C. Fleming. Mr. Fleming is the west coast’s oldest and longest-running Black journalist and is also the co-founder of the Sun Reporter, Northern California’s largest weekly African American newspaper. This month’s feature articles are: n Why The Black Press Is Still Needed n The National Negro Congress of 1936 n Herbert Hoover and Black Republicans *********************************************** AGBM MINISTRIES *********************************************** AGBM is pleased to launch it's Ministries Section. This month, the articles, information and features are courtesy of Bryan Trussell the web master for our online partner, blackandchristian.com. The Black Church has historically been a source of hope and strength for the African American community. Read about the history and learn the history of each Denomination associated with the Black Church. n History of the Black Church n The Convention Movement of the Black Baptist Church n The Full Gospel Baptist Church Fellowship *********************************************** MAN TALK *********************************************** We ring in the New Year with this Man Talk submission from Richard Rowe. Through his prose, "The Moment Black Men Unite", we are reminded that: "The moment Black men unite, our families will change. Black women will feel safe and loved like smooth sand on the Sahara Desert..." *********************************************** OUR NETWORK NEEDS YOU! *********************************************** Agoodblackman.com wants to hear from and about the countless numbers of Black men out there who have devoted their lives to building strong communities, families, and relationships. We want to celebrate it. Email us at: info@agoodblackman.com. Interested in purchasing advertising? Check out our sponsorship and advertising opportunities at: http://www.agoodblackman.com/sponsor.html We'd also like to hear about the good Black men in your community. So, if you have an essay, article, poem, or story to tell, share it with us and we'll share it with the world. http://www.agoodblackman.com/submissions.html Want home delivery of agoodblackman.com? It's easy. Just join our mailing list at: http://www.hostedscripts.com/scripts/maillist.cgi?user=agbm *********************************************** Submissions Guidelines *********************************************** Agoodblackman.com is an on-line magazine dedicated to honoring and uplifting Black men. With the exception of advertisements, we update information monthly. All submissions must be submitted electronically or digitally one month in advance by the 15th of that month. Sorry, no exceptions. Looking forward to hearing from you soon, D. Browne Web Site Designer/Site Manager http://www.agoodblackman.com Email me at: info@agoodblackman.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 11:10:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6BBCC37B402 for ; Tue, 16 Jan 2001 11:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GJA4k01113; Tue, 16 Jan 2001 11:10:04 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 11:10:04 -0800 (PST) Message-Id: <200101161910.f0GJA4k01113@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Matthew N. Dodd" Subject: Re: kern/24100: Having a 3c589 PCMCIA/PCCARD inserted prevents boot or crashes a Dell Latitude 366 laptop Reply-To: "Matthew N. Dodd" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24100; it has been noted by GNATS. From: "Matthew N. Dodd" To: jau@iki.fi Cc: freebsd-gnats-submit@FreeBSD.ORG, GNATS Management , freebsd-bugs@FreeBSD.ORG Subject: Re: kern/24100: Having a 3c589 PCMCIA/PCCARD inserted prevents boot or crashes a Dell Latitude 366 laptop Date: Tue, 16 Jan 2001 14:02:56 -0500 (EST) On Sat, 6 Jan 2001 jau@iki.fi wrote: > The system will invariably go south immediately after the ppi0 has > been reported during autoconfig. Sounds like an interrupt conflict. -- | 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-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 11:10:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 29D8837B401 for ; Tue, 16 Jan 2001 11:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GJA3W01108; Tue, 16 Jan 2001 11:10:03 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 11:10:03 -0800 (PST) Message-Id: <200101161910.f0GJA3W01108@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Matthew N. Dodd" Subject: Re: kern/24379: ahc broken in STABLE Reply-To: "Matthew N. Dodd" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24379; it has been noted by GNATS. From: "Matthew N. Dodd" To: send-pr@oldach.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24379: ahc broken in STABLE Date: Tue, 16 Jan 2001 14:01:45 -0500 (EST) On Tue, 16 Jan 2001 send-pr@oldach.net wrote: > ahc0: at 0xbc00-0xbcff, irq 15 (level) > ahc0: on eisa0 slot 11 > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x40 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01af866 > stack pointer = 0x10:0xc045fea0 > frame pointer = 0x10:0xc045fea0 > 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 = 0 (swapper) > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault > Uptime: 0s > Automatic reboot in 15 seconds - press a key on the console to abort 'rid' is not being initialized to '0' in ahc_eisa.c:aic7770_map_registers() before being used in the first bus_alloc_resource() call. (IIRC and have not already fixed this problem.) -- | 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-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 11:10:54 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A0A9837B69B for ; Tue, 16 Jan 2001 11:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GJA4101122; Tue, 16 Jan 2001 11:10:04 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0BF9437B6A5 for ; Tue, 16 Jan 2001 11:05:19 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GJ5IE98885; Tue, 16 Jan 2001 11:05:18 -0800 (PST) (envelope-from nobody) Message-Id: <200101161905.f0GJ5IE98885@freefall.freebsd.org> Date: Tue, 16 Jan 2001 11:05:18 -0800 (PST) From: larse@isi.edu To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24391: cannot kill amd after interface disappears Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24391 >Category: misc >Synopsis: cannot kill amd after interface disappears >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 11:10:04 PST 2001 >Closed-Date: >Last-Modified: >Originator: Lars Eggert >Release: 4.2-RELEASE >Organization: USC Information Sciences Institute >Environment: FreeBSD hbo.isi.edu 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Jan 15 17:36:41 PST 2001 larse@hbo.isi.edu:/usr/src/sys/compile/KERNEL-1.9 i386 >Description: Killing amd after a network interface dissappears (e.g., due to ejected PC card) fails. Kill -9 works (of course) but leaves the mount map in such a state that amd cannot be restarted. We found this when changing pccard_ether to automatically kill and restart network services based on card insertions/ejections. Since amd can't be killed once the card is out, this scheme can't be made to work. >How-To-Repeat: start amd eject pccard kill amd restart amd >Fix: Kill amd before ejecting pccard. Requires user interaction. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 12: 4:19 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from alf.uib.no (alf.uib.no [129.177.30.3]) by hub.freebsd.org (Postfix) with ESMTP id 9251237B404 for ; Tue, 16 Jan 2001 12:04:01 -0800 (PST) Received: from tunnel-44-135.vpn.uib.no ([192.168.1.2]) [129.177.44.135] by alf.uib.no for freebsd-bugs@freebsd.org with esmtp (Exim 3.16) id 14IcKk-0002Xs-00; Tue, 16 Jan 2001 21:03:59 +0100 User-Agent: Microsoft-Entourage/9.0.2509 Date: Tue, 16 Jan 2001 21:03:00 +0100 Subject: From: "Frank H. Pierce" To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth a4bb9055 subscribe freebsd-bugs frank.pierce@hedb.uib.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 12:20:28 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8388337B404 for ; Tue, 16 Jan 2001 12:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GKK4P11509; Tue, 16 Jan 2001 12:20:04 -0800 (PST) (envelope-from gnats) Received: from pancake.netability.ie (unknown [159.134.183.12]) by hub.freebsd.org (Postfix) with ESMTP id 9041537B401 for ; Tue, 16 Jan 2001 12:13:52 -0800 (PST) Received: (from nick@localhost) by pancake.netability.ie (8.11.1/8.11.0) id f0GKDqG04219; Tue, 16 Jan 2001 20:13:52 GMT (envelope-from nick) Message-Id: <200101162013.f0GKDqG04219@pancake.netability.ie> Date: Tue, 16 Jan 2001 20:13:52 GMT From: nick@netability.ie Reply-To: nick@netability.ie To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24392: bogons in kernel linker Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24392 >Category: kern >Synopsis: panic() if kldload used to load module which is already compiled into kernel >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 12:20:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Nick Hilliard >Release: FreeBSD 4.2-STABLE i386 >Organization: Network Ability Ltd. >Environment: ipfw statically compiled into kernel >Description: FreeBSD will reliably panic if ipfw is compiled into the kernel, and if an attempt is then made to load it dynamically and then unload it using kldload/kldunload. Looking at the code, I'd say that there was nothing particularly special about ipfw, and that it was a more generic problem which affects all kernel modules which register sysctls. What appears to be happening is this: "kldload ipfw" attempts to register ipfw module. This first registers all of the sysctls (kern/kern_linker.c:284 in linker_load_file()), and the on the next line attempts to initialise the module using linker_file_sysinit(). This function calls module_register() which then returns an error (EEXIST), but this error is ignored, and the registration of the module completes further on down the function (oopsie - this is bad!) "kldload ipfw" then unloads the kernel module and de-registers the sysctls which are in use by the statically compiled ipfw module, and panic occurs (didn't get any time to look into what's going on here). >How-To-Repeat: Create kernel with ipfw compiled in statically, then: # kldload ipfw # kldunload ipfw >Fix: Ran out of time for a fix. Looks relatively easy to put in a quick fix, but I'm not familiar enough with the code to feel confident about fixing it - it's very likely that some sublety has escaped me. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 12:20:28 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C17F237B69B for ; Tue, 16 Jan 2001 12:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GKK4R11518; Tue, 16 Jan 2001 12:20:04 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 770CA37B699 for ; Tue, 16 Jan 2001 12:16:13 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GKGCU11053; Tue, 16 Jan 2001 12:16:12 -0800 (PST) (envelope-from nobody) Message-Id: <200101162016.f0GKGCU11053@freefall.freebsd.org> Date: Tue, 16 Jan 2001 12:16:12 -0800 (PST) From: semenu@FreeBSD.org To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24393: Patch to msdosfs to handle a kind of incorrect filesystems Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24393 >Category: kern >Synopsis: Patch to msdosfs to handle a kind of incorrect filesystems >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 12:20:04 PST 2001 >Closed-Date: >Last-Modified: >Originator: Semen A. Ustimenko >Release: 4.2-RELEASE >Organization: >Environment: FreeBSD dev.the.net 4.2-RELEASE FreeBSD 4.2-RELEASE #3: Tue Dec 12 15:23:17 GMT+6 2000 root@default.the.net:/usr/src/sys/compile/DEFAULT i386 >Description: There are sometimes a FAT filesystems not handled correctly by msdosfs driver, but handled by mtools and other OSes. The problem is that msdosfs assume . entry in directory have cluster number set to real directory cluster number. But sometimes cluster number for . entry is set to 0, and msdosfs behaves wrong with such filesystems. >How-To-Repeat: Take a FAT12 formatted diskette image from vmware2 distribution (vmware-distrib/lib/floppies/windows.flp): without patch: # ls -lR /floppy ls: win2k: directory causes a cycle ls: win9x: directory causes a cycle ls: winnt: directory causes a cycle total 850 -rwxr-xr-x 1 root wheel 870002 Nov 1 17:36 VMwareTools.exe drwxr-xr-x 1 root wheel 0 Nov 1 17:36 win2k drwxr-xr-x 1 root wheel 0 Nov 1 17:36 win9x drwxr-xr-x 1 root wheel 0 Nov 1 17:36 winnt with patch: # ls -lR /floppy total 852 -rwxr-xr-x 1 root wheel 870002 Nov 1 17:36 VMwareTools.exe drwxr-xr-x 1 root wheel 512 Nov 1 17:36 win2k drwxr-xr-x 1 root wheel 512 Nov 1 17:36 win9x drwxr-xr-x 1 root wheel 512 Nov 1 17:36 winnt /floppy/win2k: total 28 -rwxr-xr-x 1 root wheel 18432 Nov 1 17:36 vmx_fb.dll -rwxr-xr-x 1 root wheel 2274 Nov 1 17:36 vmx_svga.inf -rwxr-xr-x 1 root wheel 7440 Nov 1 17:36 vmx_svga.sys /floppy/win9x: total 25 -rwxr-xr-x 1 root wheel 17136 Nov 1 17:36 VMX_SVGA.DRV -rwxr-xr-x 1 root wheel 5991 Nov 1 17:36 VMX_SVGA.vxd -rwxr-xr-x 1 root wheel 1669 Nov 1 17:36 vmx_svga.inf /floppy/winnt: total 38 -rwxr-xr-x 1 root wheel 17408 Nov 1 17:36 vmx_fb.dll -rwxr-xr-x 1 root wheel 13637 Nov 1 17:36 vmx_svga.inf -rwxr-xr-x 1 root wheel 7440 Nov 1 17:36 vmx_svga.sys >Fix: Use following patch: Index: src/sys/msdosfs/msdosfs_denode.c =================================================================== RCS file: /usr/home/ncvs/src/sys/msdosfs/msdosfs_denode.c,v retrieving revision 1.47.2.1 diff -c -r1.47.2.1 msdosfs_denode.c *** src/sys/msdosfs/msdosfs_denode.c 2000/07/08 14:34:27 1.47.2.1 --- src/sys/msdosfs/msdosfs_denode.c 2001/01/16 19:30:13 *************** *** 356,361 **** --- 356,371 ---- */ u_long size; + /* + * XXX Sometimes, there arrives that . entry have cluster + * number 0, when it shouldn't. Use real cluster number + * instead of what is written in directory entry. + */ + if ((diroffset == 0) && (ldep->de_StartCluster != dirclust)) { + printf("deget(): . entry at clust %ld != %ld\n", dirclust, ldep->de_StartCluster); + ldep->de_StartCluster = dirclust; + } + nvp->v_type = VDIR; if (ldep->de_StartCluster != MSDOSFSROOT) { error = pcbmap(ldep, 0xffff, 0, &size, 0); >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 15:10:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3DEFD37B400 for ; Tue, 16 Jan 2001 15:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0GNA2W33653; Tue, 16 Jan 2001 15:10:02 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 15:10:02 -0800 (PST) Message-Id: <200101162310.f0GNA2W33653@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: alo@iki.fi (Antti Louko) Subject: Re: misc/24048: natd/libalias doesn't always properly modify FTP PORT command Reply-To: alo@iki.fi (Antti Louko) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24048; it has been noted by GNATS. From: alo@iki.fi (Antti Louko) To: ru@FreeBSD.org Cc: bug-followup@FreeBSD.org Subject: Re: misc/24048: natd/libalias doesn't always properly modify FTP PORT command Date: Wed, 17 Jan 2001 01:04:45 +0200 (EET) > natd (actually libalias/alias_db.c) only modifies FTP PORT commands > if they are immediately in the beginning of a new line. > This is implemented by having a flag which is set when a CR/LF > pair is detected. This works well except when PORT command > happens to be first command in the FTP session. > I don't see the major problem with this change, but is this allowed by FTP protocol specs? (The first command being a PORT command.) I would guess so. In RFC959, page 45, there is an example of a client transferring data between two servers. In that example, the first command to one of the servers is a PORT command. Of course one could argue that the authentication has been left out of the example but I cannot see any place where the authentication would be required. Regards, Antti Louko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 18:50:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0F51C37B402 for ; Tue, 16 Jan 2001 18:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H2o2i63111; Tue, 16 Jan 2001 18:50:02 -0800 (PST) (envelope-from gnats) Received: from radix.cryptio.net (radix.cryptio.net [199.181.107.213]) by hub.freebsd.org (Postfix) with ESMTP id C708A37B402 for ; Tue, 16 Jan 2001 18:41:22 -0800 (PST) Received: (from emechler@localhost) by radix.cryptio.net (8.11.0/8.11.0) id f0H2fMN28914; Tue, 16 Jan 2001 18:41:22 -0800 (PST) Message-Id: <200101170241.f0H2fMN28914@radix.cryptio.net> Date: Tue, 16 Jan 2001 18:41:22 -0800 (PST) From: Erick Mechler Reply-To: emechler@radix.cryptio.net To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24397: Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24397 >Category: bin >Synopsis: >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 18:50:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Erick Mechler >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: FreeBSD 4.x >Description: This patch is just a way to easily restart the sendmail process using the Makefile installed into /etc/mail/Makefile. Although this isn't necessary a lot of the time, it's proven useful for me in several cases and might be a good addition to the system. >How-To-Repeat: >Fix: *** Makefile.orig Tue Jan 16 18:05:40 2001 --- Makefile Tue Jan 16 17:02:52 2001 *************** *** 29,31 **** --- 29,34 ---- clean: rm -f access.db virtusertable.db mailertable.db + + restart: + kill -HUP `head -1 /var/run/sendmail.pid` >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 19:50:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9B5D737B402 for ; Tue, 16 Jan 2001 19:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H3o1G71207; Tue, 16 Jan 2001 19:50:01 -0800 (PST) (envelope-from gnats) Received: from kwanon.research.canon.com.au (kwanon.research.canon.com.au [203.12.172.254]) by hub.freebsd.org (Postfix) with ESMTP id 42EE837B401 for ; Tue, 16 Jan 2001 19:44:55 -0800 (PST) Received: from rice.research.canon.com.au (rice.research.canon.com.au [10.2.2.91]) by kwanon.research.canon.com.au (Postfix) with ESMTP id 94CE28A8B2 for ; Wed, 17 Jan 2001 03:51:17 +0000 (UTC) Received: (from iain@localhost) by rice.research.canon.com.au (8.11.0/8.11.1) id f0H3irq00407; Wed, 17 Jan 2001 14:44:53 +1100 (EST) (envelope-from iain) Message-Id: <200101170344.f0H3irq00407@rice.research.canon.com.au> Date: Wed, 17 Jan 2001 14:44:53 +1100 (EST) From: iain@research.canon.com.au Reply-To: iain@research.canon.com.au To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24398: Unit number is not set in ahc driver. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24398 >Category: kern >Synopsis: Unit number is not set in ahc driver. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 19:50:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Iain Templeton >Release: FreeBSD 4.2-STABLE i386 >Organization: Canon Information Systems Research Australia >Environment: 4.2-STABLE, current version of aic7xxx driver. >Description: The ahc->unit field is not being set in the softc structure. This effects the test against AHC_TARGET_MODE since it uses that field. If it is not set it is 0, and the test happens as if all the devices were ahc0. I suspect it doesn't effect anything else (the field isn't used elsewhere). >How-To-Repeat: Use AHC_TARGET_MODE set to some value with bits other than bit 0 set. It won't activate target mode on any units higher than 0. >Fix: Try this patch. It simply sets the unit number after allocating the ahc_softc structure. *** ahc_eisa.c.old Wed Jan 17 14:37:08 2001 --- ahc_eisa.c Wed Jan 17 14:37:56 2001 *************** *** 126,131 **** --- 126,134 ---- if (ahc == NULL) return (ENOMEM); + /* Set the unit number of the ahc instance */ + ahc_set_unit(ahc, device_get_unit(dev)); + /* Allocate a dmatag for our SCB DMA maps */ /* XXX Should be a child of the PCI bus dma tag */ error = bus_dma_tag_create(/*parent*/NULL, /*alignment*/1, *** ahc_pci.c.old Wed Jan 17 14:36:26 2001 --- ahc_pci.c Wed Jan 17 14:36:09 2001 *************** *** 98,103 **** --- 98,106 ---- if (ahc == NULL) return (ENOMEM); + /* Set the unit number of the ahc instance */ + ahc_set_unit(ahc, device_get_unit(dev)); + /* Allocate a dmatag for our SCB DMA maps */ /* XXX Should be a child of the PCI bus dma tag */ error = bus_dma_tag_create(/*parent*/NULL, /*alignment*/1, >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 23:20:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CAD1C37B400 for ; Tue, 16 Jan 2001 23:20:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H7K3b03014; Tue, 16 Jan 2001 23:20:03 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Jan 2001 23:20:03 -0800 (PST) Message-Id: <200101170720.f0H7K3b03014@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tomonobu AKIMOTO Subject: Re: bin/23501: pw destroy /etc/master.passwd when pw executing at the Reply-To: Tomonobu AKIMOTO Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/23501; it has been noted by GNATS. From: Tomonobu AKIMOTO To: Alex Kapranoff Cc: dhagan@colltech.com, freebsd-gnats-submit@freebsd.org Subject: Re: bin/23501: pw destroy /etc/master.passwd when pw executing at the Date: Wed, 17 Jan 2001 16:11:31 +0900 Hello,Alex. I tried your patch and tested it. Then the problem is solved. Thanks a lot. > try the following patch and see if it helps. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Tue Jan 16 23:40:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BBD2137B402 for ; Tue, 16 Jan 2001 23:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H7e1o04769; Tue, 16 Jan 2001 23:40:01 -0800 (PST) (envelope-from gnats) Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 9EB1637B400 for ; Tue, 16 Jan 2001 23:37:09 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 16 Jan 2001 23:35:22 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0H7b7t60224; Tue, 16 Jan 2001 23:37:07 -0800 (PST) (envelope-from cjc) Message-Id: <200101170737.f0H7b7t60224@rfx-64-6-211-149.users.reflexcom.com> Date: Tue, 16 Jan 2001 23:37:07 -0800 (PST) From: cjclark@reflexcom.com Reply-To: cjclark@alum.mit.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24399: OpenSSH forced commands munge output Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24399 >Category: bin >Synopsis: OpenSSH forced commands munge output >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 16 23:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Crist J. Clark >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: FreeBSD 4.2-STABLE SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). >Description: OpenSSH "forced commands," a command specified in the authorized_keys file, have their output mangled. It looks like their is some UNIX-MSDOS conversion going on. Newlines, \n, are substituted with \r\n. >How-To-Repeat: Assuming you have sshd running locally and don't have anything in your configs to break this kind of thing. $ man ssh > ssh_1.cat $ ssh-keygen -f sshtest -N "" -C SSH-Test $ { echo 'command="cat ssh_1.cat" '; cat sshtest.pub; } >> .ssh/authorized_keys $ ssh -i sshtest localhost > ssh_2.cat $ cmp ssh_1.cat ssh_2.cat ssh_1.cat ssh_2.cat differ: char 79, line 1 $ tr -d '\r' < ssh_2.cat > ssh_3.cat $ cmp ssh_1.cat ssh_3.cat $ But this works, $ ssh localhost "cat ssh_1.cat" > ssh_4.cat cjc@localhost's password: $ cmp ssh_1.cat ssh_4.cat $ >Fix: No workaround other than to not use forced commands. After a quick look at the code, I can't see how a "forced command" would produce different results than one provided on the command line. But that's what the tests show. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 0:30:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 073B137B400 for ; Wed, 17 Jan 2001 00:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H8U2T12451; Wed, 17 Jan 2001 00:30:02 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 00:30:02 -0800 (PST) Message-Id: <200101170830.f0H8U2T12451@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: helge@oldach.net (Helge Oldach) Subject: Re: kern/24379: ahc broken in STABLE Reply-To: helge@oldach.net (Helge Oldach) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24379; it has been noted by GNATS. From: helge@oldach.net (Helge Oldach) To: winter@jurai.net (Matthew N. Dodd) Cc: send-pr@oldach.net, FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24379: ahc broken in STABLE Date: Wed, 17 Jan 2001 09:24:54 +0100 (CET) Matthew N. Dodd: > 'rid' is not being initialized to '0' in > ahc_eisa.c:aic7770_map_registers() before being used in the first > bus_alloc_resource() call. (IIRC and have not already fixed this > problem.) The same is also in aic7770_probe. I have fixed both, but still get the same trap at the same virtual address. I suspect that it happens a bit earlier, e.g. during device probe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 1:30:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5226537B401 for ; Wed, 17 Jan 2001 01:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H9U1c20282; Wed, 17 Jan 2001 01:30:01 -0800 (PST) (envelope-from gnats) Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id 5F62137B401 for ; Wed, 17 Jan 2001 01:21:11 -0800 (PST) Received: (from rfg@localhost) by mail.monkeys.com (8.11.1/8.11.1) id f0H9L5203676; Wed, 17 Jan 2001 01:21:05 -0800 (PST) Message-Id: <200101170921.f0H9L5203676@mail.monkeys.com> Date: Wed, 17 Jan 2001 01:21:05 -0800 (PST) From: "Ronald F. Guilmette" Reply-To: rfg@monkeys.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24401 >Category: kern >Synopsis: Advansys SCSI driver crashes random userland progs w/SIGPROF >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 17 01:30:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 4.2-RELEASE i386 >Organization: Infinite Monkeys & Co. >Environment: System consists of: ASUS P5A motherboard 256 MB SDRAM 3 different PCI 10/100 ethernet controllers (xl0 rl0 rl1) ATAPI/EIDE CD ROM drive (ASUS 40x) Advansys model ASB3940UA Ultra/Narrow PCI SCSI controller 3 different SCSI hard drives >Description: (Note: This system was crashing random userland processes under FreeBSD 4.0, usually with spurious SIGVTALRM signals being sent to random processes at seemingly random times. Now I suspect that at last I know why, however I'm not 100% sure that those incidents were directly related to the bug that I am reporting here. THOSE problems with FreeBSD 4.0 got so bad that I had to back out of my upgrade to 4.0 and go back to 3.3.) Now, on to the current problem/bug... I recently was in the process of decomissioning an old (but large) Narrow/Ultra SCSI drive that was in the system (along with some others) i.e. an IBM model DCAS-34330 (4.3 GB). I backed up everything useful from that drive (a complete 4.1.1 system) onto my trusty old HP 35470A SCSI DAT/DSS tape drive and removed the drive physically from the system. I then installed a Quantum 4.5 GB SCSI drive (Quantum Viking 4.5) and loaded up FreeBSD 4.2 onto it. I then powered down, attached the the old IBM SCSI drive back to the system (in an external cases this time), did a low-level format on it and then made a fresh file system on it and then tried to restore my important stuff from my backup tape back onto the old IBM drive (using cpio). That restore from tape seemed to work OK until about half-way through when cpio crashed, apparently because it had received a totally unexpected SIGPROF. (The console message at the time cpio crashed said "Profiling time alarm" aka SIGPROF.) At first, I just chalked this up to sunspots or to gremlins or to the phase of the moon or something, and I just shrugged it off. (I didn't really need to do this restore from tape anyway.) A little later, I decided to sell the old IBM drive on eBay, but first I wanted to make sure that there would not be any incriminating White House E-mail message left intact on the drive. :-) So I did the following to try to erase whatever was on there formerly, and to wipe the drive totally clean: dd if=/dev/zero of=/dev/da1 bs=4096 This also seemed to be working ok... for awhile. But after awhile, the dd process also crashed and the console said "Profiling time alarm" (aka SIGPROF). I did the dd again and the same exact thing happened. I then decided to try to see if these failures were random or if they were always happening at the same spot on the disk. So I wrote a little C program (attached below) which would just write 4 KB sized blocks of zeros to any device it was told to write them to... while printing the block numbers as it was writing... and then I ran that against /dev/da1. Sure enough, after 485207 4KB blocks had been written (about half the disk) the system locked up. The X server stopped responding to the mouse and to keyboard input and about a minute later, the system rebooted on its own accord. I figured that the Advansys driver was sending the spurious SIGPROF signals to whatever userland process happened to be running at the unfortunate moment when it (the Advansys driver) tried to throw one of these signals. So I decided that it would be best to try running my little "zerodisk" test program when X was *not* running. I then did that... several times. In all cases (4) my little "zerodisk" program crashed unexpectedly (console message was always "Profiling time alarm") after it had already written several hundred thousand 4KB blocks of zeros to /dev/da1. Here are some of the block counts at the times of the crashes: 344449 329357 314214 As you can see, it may take awhile, but with the Advansys controller in the system, I could *always* and *repeatedly* get the driver to send one of these spurious SIGPROF signals to some undeserving userland process. (On an otherwise quite system, my little "zerodisk" program itself was the one most likely to be scheduled for execution by the kernel at any given instant in time, so it usually received these signals. But I believe that I have evidence that these spurious SIGPROF signals might also get sent in some cases to other random userland processes... depending on the exact timing of their genera- tion within the kernel.) After this, I gen'd up a new kernel (with Adaptech support in it), installed that, yanked the Advansys SCSI card out and plugged in an Adaptec 3940AU and re-ran my "zerodisk" test program against /dev/da1. I did this THREE TIMES, just to be sure, and it worked flawlessly each time, all the way to the end of the disk... over 1,000,000 4 KB block writes in each case. The bottom line is that if you do enough writes (several hundred thousand, typically) using an Advansys 3940UA controller, and an ordinary Ultra/Narrow SCSI drive (note: the IBM I used does NOT support tagged command queueing) using FreeBSD 4.2 and the Advansys driver contained therein, then eventually you are going to work the Advansys driver into a state where it will start throwing SIGPROF signals at random times to random useland processes for no apparent reason. This _does not_ occur with other SCSI controllers (e.g. AHA-3940AU) in the exact same system/environment. Clearly the Advansys driver has a VERY subtle, but very bad bug which, it appears, can only be consistantly/dependably elicited via a very intense stress test, e.g. several hundred thousand writes to disk before you can be assured of seeing the bug.) I am filing this bug report as critical/high-priority because the the effects of this bug are so nefarious, i.e. crashing random userland programs (maybe even init and/or the X server) at totally unpredictable and random times. (This sort of thing could give FreeBSD a bad reputation for unreliability!) >How-To-Repeat: Get yourself a Advansys ASB3940UA Ultra/Narrow PCI SCSI controller. Put it into an otherwise unremarkable x86/PCI system. Plug in one SCSI drive and install FreeBSD 4.2 on it. Plug in a second SCSI drive (at least 2GB, but 4GB would be better) that you can afford to overwrite entirely, and then just do: dd if=/dev/zero of=/dev/da1 bs=4096 (preferably on a quiet system, without any X server running) and then just sit back and wait. After awhile, the dd process will crash and you'll get the message: Profiling time alarm (I will even loan this exact IBM drive, and the controller, to anyone who wants to work on this bug. Just ask. The controller is useless to me now anyway... until someone fixes this bug... and I was gonna sell the drive on eBay anyway.) Alternatively, you can run the following simple "zerodisk" program that I cooked up. This will give you essentially the same results, but will show how many blocks got written before the spurious SIGPROF arrives. (BE VERY CAREFUL USING THIS PROGRAM. It must be run as root to access the disk device files and it can easily wipe out an entire disk permanently. In fact that is the purpose for which it was written!) /* zerodisk.c */ #include #include #include #include #include #include #include static char const *pname; static void usage (void) { fprintf (stderr, "%s: Usage: `%s device'\n", pname, pname); exit (1); } static void errorv (register char const *const fmt, va_list ap) { fprintf (stderr, "%s: ", pname); vfprintf (stderr, fmt, ap); fputc ('\n', stderr); } static void error (register char const *const fmt, ...) { va_list ap; va_start (ap, fmt); errorv (fmt, ap); va_end (ap); } static void fatal (register char const *const fmt, ...) { va_list ap; va_start (ap, fmt); errorv (fmt, ap); va_end (ap); exit (1); } int main (register int const argc, char *argv[]) { enum { block_size = 4096 }; static char zeros[block_size]; register int fd; register unsigned long blockno = 0; pname = strrchr (argv[0], '/'); pname = pname ? pname+1 : argv[0]; if (argc != 2) usage (); if ((fd = open (argv[1], O_WRONLY)) == -1) fatal ("Error opening `%s': %s", argv[1], strerror (errno)); for (;;) { register ssize_t n; printf ("\rWriting block %lu", ++blockno); fflush (stdout); if ((n = write (fd, zeros, block_size)) == -1) { putchar ('\n'); fatal ("Error writing `%s': %s", argv[1], strerror (errno)); } if (n < block_size) { putchar ('\n'); error ("EOF detected on `%s'", argv[1]); exit (0); } } } >Fix: Buy and install a non-Advansys brand of SCSI controller. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 1:39: 4 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A85E837B698; Wed, 17 Jan 2001 01:38:48 -0800 (PST) Received: (from kris@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H9cm821249; Wed, 17 Jan 2001 01:38:48 -0800 (PST) (envelope-from kris) Date: Wed, 17 Jan 2001 01:38:48 -0800 (PST) From: Message-Id: <200101170938.f0H9cm821249@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, green@FreeBSD.org Subject: Re: bin/24399: OpenSSH forced commands munge output Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: OpenSSH forced commands munge output Responsible-Changed-From-To: freebsd-bugs->green Responsible-Changed-By: kris Responsible-Changed-When: Wed Jan 17 01:38:37 PST 2001 Responsible-Changed-Why: Over to the maintainer http://www.freebsd.org/cgi/query-pr.cgi?pr=24399 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 1:57:18 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B3B5637B400; Wed, 17 Jan 2001 01:57:02 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H9v2w22941; Wed, 17 Jan 2001 01:57:02 -0800 (PST) (envelope-from dwmalone) Date: Wed, 17 Jan 2001 01:57:02 -0800 (PST) From: Message-Id: <200101170957.f0H9v2w22941@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, gibbs@FreeBSD.org Subject: Re: kern/24398: Unit number is not set in ahc driver. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Unit number is not set in ahc driver. Responsible-Changed-From-To: freebsd-bugs->gibbs Responsible-Changed-By: dwmalone Responsible-Changed-When: Wed Jan 17 01:56:22 PST 2001 Responsible-Changed-Why: The ahc driver is Justin's. http://www.freebsd.org/cgi/query-pr.cgi?pr=24398 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 1:58:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EAE9237B402; Wed, 17 Jan 2001 01:57:59 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0H9vxH23112; Wed, 17 Jan 2001 01:57:59 -0800 (PST) (envelope-from dwmalone) Date: Wed, 17 Jan 2001 01:57:59 -0800 (PST) From: Message-Id: <200101170957.f0H9vxH23112@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, gibbs@FreeBSD.org Subject: Re: kern/24379: ahc broken in STABLE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: ahc broken in STABLE Responsible-Changed-From-To: freebsd-bugs->gibbs Responsible-Changed-By: dwmalone Responsible-Changed-When: Wed Jan 17 01:57:15 PST 2001 Responsible-Changed-Why: The ahc driver is Justin's. . http://www.freebsd.org/cgi/query-pr.cgi?pr=24379 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 3: 0:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C0ED837B699 for ; Wed, 17 Jan 2001 03:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HB02f30871; Wed, 17 Jan 2001 03:00:02 -0800 (PST) (envelope-from gnats) Received: from po.iijnet.or.jp (ppp10159.po.iijnet.or.jp [202.232.19.159]) by hub.freebsd.org (Postfix) with ESMTP id 34A1337B400 for ; Wed, 17 Jan 2001 02:53:27 -0800 (PST) Received: (from hidero@localhost) by po.iijnet.or.jp (8.11.1/8.11.1) id f0HAqYa01315; Wed, 17 Jan 2001 19:52:34 +0900 (JST) (envelope-from hidero) Message-Id: <200101171052.f0HAqYa01315@po.iijnet.or.jp> Date: Wed, 17 Jan 2001 19:52:34 +0900 (JST) From: hidero@po.iijnet.or.jp Reply-To: hidero@po.iijnet.or.jp To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24406: USB Image scanner not worked Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24406 >Category: kern >Synopsis: USB Image scanner not worked >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 17 03:00:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Sasaki Hideo >Release: FreeBSD 4.2-RELEASE i386 >Organization: >Environment: CPU: IBM ThinkPad X20 (2662-34J) Scanner: Seiko Epson GT-7700U (has USB interface) >Description: My image scanner "Epson GT-7700U" not work on FreeBSD 4.2R. This scanner connect on USB interface, kernel wrote following message. /kernel: ugen0: EPSON GT-7700, rev 1.00/1.03, addr 3 >How-To-Repeat: That scanner connect on any USB interfaces, not work all time. >Fix: Apply this patches. *** /usr/src/sys/dev/usb/usbdevs.h.org Tue Jan 16 21:51:41 2001 --- /usr/src/sys/dev/usb/usbdevs.h Tue Jan 16 19:03:43 2001 *************** *** 459,462 **** --- 459,463 ---- #define USB_PRODUCT_EPSON_1200 0x0104 /* Perfection 1200U / 1200Photo scanner */ #define USB_PRODUCT_EPSON_1600 0x0107 /* Expression 1600 */ + #define USB_PRODUCT_EPSON_GT7700 0x010b /* GT-7700U */ /* e-TEK Labs products */ *** /usr/src/sys/dev/usb/usbdevs_data.h.org Tue Jan 16 21:51:59 2001 --- /usr/src/sys/dev/usb/usbdevs_data.h Tue Jan 16 19:05:41 2001 *************** *** 575,578 **** --- 575,584 ---- }, { + USB_VENDOR_EPSON, USB_PRODUCT_EPSON_GT7700, + 0, + "Seiko Epson Corp.", + "GT-7700U", + }, + { USB_VENDOR_ETEK, USB_PRODUCT_ETEK_1COM, 0, *** /usr/src/sys/dev/usb/uscanner.c.org Tue Jan 16 21:52:09 2001 --- /usr/src/sys/dev/usb/uscanner.c Tue Jan 16 19:06:11 2001 *************** *** 144,147 **** --- 144,148 ---- { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_1200 }, { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_1600 }, + { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_GT7700 }, /* UMAX */ >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 7:14:54 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id E457337B400 for ; Wed, 17 Jan 2001 07:14:37 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA17887; Wed, 17 Jan 2001 10:14:33 -0500 (EST) (envelope-from wollman) Date: Wed, 17 Jan 2001 10:14:33 -0500 (EST) From: Garrett Wollman Message-Id: <200101171514.KAA17887@khavrinen.lcs.mit.edu> To: alo@iki.fi (Antti Louko) Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: misc/24048: natd/libalias doesn't always properly modify FTP PORT command In-Reply-To: <200101162310.f0GNA2W33653@freefall.freebsd.org> References: <200101162310.f0GNA2W33653@freefall.freebsd.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < Of course one could argue that the authentication has been left out of > the example but I cannot see any place where the authentication would > be required. At the time RFC 959 was written, many FTP servers did not require authentication. Users were assumed to be ``anonymous'' unless they requested a specific login with USER. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 8:30:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 269D437B402 for ; Wed, 17 Jan 2001 08:30:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HGU5F65477; Wed, 17 Jan 2001 08:30:05 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 08:30:05 -0800 (PST) Message-Id: <200101171630.f0HGU5F65477@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Panagiotis Astithas Subject: Re: misc/24324: Greek console support Reply-To: Panagiotis Astithas Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24324; it has been noted by GNATS. From: Panagiotis Astithas To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: misc/24324: Greek console support Date: Wed, 17 Jan 2001 18:35:43 +0200 I forgot to send the colldef/map.ISO_8859-7 with the original PR. Here it is. begin 644 map.ISO_8859-7.gz M'XL("*W(93H``VUA<"Y)4T]?.#@U.2TW`!W367/<1!3%\??_I\`/U"2A3+3- MJ$694+-Y2>SQQ/(24[RHM8#9#"3.]NGI_*,32YS-H4LV)2R9%/)BIWZYG/:>[E@NY(UZYT,;"]D0^OK'=NU3/VU MO[SGQ`YQY_DH.S.S([""Y MR'@FZ\B![3EX+M.ZG^3(1GG4$_ME,F2:)Z1YE4M(\WI] MFE?[#36G-N7]6C;2O/D/)6+DW&7GDW.7O= M;PJN]9ZF9.W[%1=W,O4_D:F_K6F]+G#B=2EOV[%6OR;2:LZFY]+7!_8ZEV9D MZ7IBI^>[C&8F"@';K^5(X?:1Y?FUQPQXSO=CSF%^L2"TI;,M*]8,=-S,7WO=L'W M>C[6;%T'[FW#F>UXI>\A1BY=]^3*-0[TXMY$+V[.S`VL['C"N;\_%'6="Z+KFV M%3=VSK%=\,[6O+6!.]OPVJ;_W48ZS3GTC';@BQUYL!-/FG_,Z+1^S(FVX%=; M,MB*T<[Y:A=\L36_V<"#;?C#=OQI(W_9GK_M0&]''NW$/W+*^,_FO'@O"]Z[ M+OE@*Y[LG,DN^&QK_K6!3[;A=]OQT48>->?4\V0'/MF1X:N<^!\Z.;8]<`4` !`/E@ ` end -past To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 8:49:32 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DF4F137B400; Wed, 17 Jan 2001 08:49:15 -0800 (PST) Received: (from ache@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HGnFB67904; Wed, 17 Jan 2001 08:49:15 -0800 (PST) (envelope-from ache) Date: Wed, 17 Jan 2001 08:49:15 -0800 (PST) From: Message-Id: <200101171649.f0HGnFB67904@freefall.freebsd.org> To: past@netmode.ntua.gr, ache@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/24324: Greek console support Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Greek console support State-Changed-From-To: open->analyzed State-Changed-By: ache State-Changed-When: Wed Jan 17 08:48:40 PST 2001 State-Changed-Why: Commited to -current http://www.freebsd.org/cgi/query-pr.cgi?pr=24324 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 9:33:21 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from anubis.ecci.ucr.ac.cr (anubis.ecci.ucr.ac.cr [163.178.104.133]) by hub.freebsd.org (Postfix) with ESMTP id A24AA37B401; Wed, 17 Jan 2001 09:32:55 -0800 (PST) Received: from localhost (bsolano@localhost) by anubis.ecci.ucr.ac.cr (8.9.3+Sun/8.9.1) with ESMTP id LAA16870; Wed, 17 Jan 2001 11:33:24 -0600 (CST) Date: Wed, 17 Jan 2001 11:33:24 -0600 (CST) From: =?iso-8859-1?Q?Braulio_Jos=E9_Solano_Rojas?= X-Sender: bsolano@anubis To: freebsd-bugs@freebsd.org, freebsd-config@freebsd.org Subject: I have found an error in pccard_ether and I think I solved it. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I have FreeBSD 4.1 release. My computer is a laptop, so I use pccards. I found that with /stand/sysinstall the lan can be configured automatically, but for pccards it doesn't work. So, after a debugging of the scripts (just because I like automation and ease of use) I found a mistake in /etc/pccard_ether. I have changed the line 43 and added a new line before, so that line 43 is now line 44. This is the line 43 (the new line 44) after my changes: ' ifconfig ${interface} ${configuration} $* ' And this is the line I added before the line 43 (the new line 43): ' eval configuration=\$ifconfig_${interface} ' I don't now if this problem has been solved before sending this email, but my hope is that I can help. Please, forgive my english. Sincerely yours, Braulio Jose Solano To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 10:10:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5E45437B6C7 for ; Wed, 17 Jan 2001 10:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HIA1280203; Wed, 17 Jan 2001 10:10:01 -0800 (PST) (envelope-from gnats) Received: from smtp3.dti.ne.jp (smtp3.dti.ne.jp [202.216.228.38]) by hub.freebsd.org (Postfix) with ESMTP id 20FDD37B69C for ; Wed, 17 Jan 2001 10:03:42 -0800 (PST) Received: from merchior.Earthtia.elh (PPP660.aichi-ip.dti.ne.jp [211.132.88.160]) by smtp3.dti.ne.jp (8.9.3/3.7W) with ESMTP id DAA18725 for ; Thu, 18 Jan 2001 03:03:34 +0900 (JST) Received: (from yusuke@localhost) by merchior.Earthtia.elh (8.11.1/8.11.1) id f0HI3W378363; Thu, 18 Jan 2001 03:03:32 +0900 (JST) Message-Id: <200101171803.DAA18725@smtp3.dti.ne.jp> Date: Thu, 18 Jan 2001 03:03:32 +0900 (JST) From: yusmat@iris.dti.ne.jp To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24412: kernel fail to probe 'EPSON GT-8700F' Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24412 >Category: kern >Synopsis: kernel fail to probe EPSON GT-8700F (USB Image Scanner) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 17 10:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Yusuke Matsuoka >Release: FreeBSD 4.2-RELEASE i386 >Organization: >Environment: FreeBSD puffy.Earthtia.elh 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Sun Dec 31 16:17:50 JST 2000 yusuke@puffy.Earthtia.elh:/usr/src/sys/compile/PUFFY i386 >Description: 'EPSON GT-8700' not probed by /dev/uscanner0. /kernel: ugen0: EPSON GT-8700, rev 1.10/1.03, addr 3 >How-To-Repeat: Always. >Fix: Use following patch: *** /sys/dev/usb/usbdevs.h.orig Thu Nov 23 16:06:30 2000 --- /sys/dev/usb/usbdevs.h Thu Jan 18 00:16:14 2001 *************** *** 458,463 **** --- 458,464 ---- #define USB_PRODUCT_EPSON_610 0x0103 /* Perfection 610 scanner */ #define USB_PRODUCT_EPSON_1200 0x0104 /* Perfection 1200U / 1200Photo scanner */ #define USB_PRODUCT_EPSON_1600 0x0107 /* Expression 1600 */ + #define USB_PRODUCT_EPSON_8700 0x010a /* EPSON GT-8700 / GT-8700F */ /* e-TEK Labs products */ #define USB_PRODUCT_ETEK_1COM 0x8007 /* Serial port */ *** /sys/dev/usb/usbdevs_data.h.orig Thu Nov 23 16:06:32 2000 --- /sys/dev/usb/usbdevs_data.h Thu Jan 18 00:24:18 2001 *************** *** 574,579 **** --- 574,585 ---- "Expression 1600", }, { + USB_VENDOR_EPSON, USB_PRODUCT_EPSON_8700, + 0, + "Seiko Epson Corp.", + "GT-8700 / GT-8700F scanner", + }, + { USB_VENDOR_ETEK, USB_PRODUCT_ETEK_1COM, 0, "e-TEK Labs", *** /sys/dev/usb/uscanner.c.orig Wed Nov 1 09:48:41 2000 --- /sys/dev/usb/uscanner.c Thu Jan 18 00:23:44 2001 *************** *** 143,148 **** --- 143,149 ---- { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_610 }, { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_1200 }, { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_1600 }, + { USB_VENDOR_EPSON, USB_PRODUCT_EPSON_8700 }, /* UMAX */ { USB_VENDOR_UMAX, USB_PRODUCT_UMAX_ASTRA1220U }, >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 10:19:42 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 2162437B6C9 for ; Wed, 17 Jan 2001 10:19:09 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0HIIms01611; Wed, 17 Jan 2001 11:18:48 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101171818.f0HIIms01611@aslan.scsiguy.com> To: helge@oldach.net (Helge Oldach) Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/24379: ahc broken in STABLE In-Reply-To: Your message of "Wed, 17 Jan 2001 00:30:02 PST." <200101170830.f0H8U2T12451@freefall.freebsd.org> Date: Wed, 17 Jan 2001 11:18:48 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >The following reply was made to PR kern/24379; it has been noted by GNATS. > >From: helge@oldach.net (Helge Oldach) >To: winter@jurai.net (Matthew N. Dodd) >Cc: send-pr@oldach.net, FreeBSD-gnats-submit@FreeBSD.ORG >Subject: Re: kern/24379: ahc broken in STABLE >Date: Wed, 17 Jan 2001 09:24:54 +0100 (CET) > > Matthew N. Dodd: > > 'rid' is not being initialized to '0' in > > ahc_eisa.c:aic7770_map_registers() before being used in the first > > bus_alloc_resource() call. (IIRC and have not already fixed this > > problem.) > > The same is also in aic7770_probe. I have fixed both, but still get the > same trap at the same virtual address. I suspect that it happens a bit > earlier, e.g. during device probe. I have already corrected the problem and should be committing the fix soon. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 10:20:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CC25837B401 for ; Wed, 17 Jan 2001 10:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HIK1N81091; Wed, 17 Jan 2001 10:20:01 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 10:20:01 -0800 (PST) Message-Id: <200101171820.f0HIK1N81091@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Justin T. Gibbs" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Justin T. Gibbs" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Justin T. Gibbs" To: rfg@monkeys.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 11:17:24 -0700 >>Synopsis: Advansys SCSI driver crashes random userland progs w/SIGPROF In all likelyhood, this has nothing to do with the AdvanSys controller. It smells like a faulty or overclocked CPU or faulty RAM. Performing disk I/O is quite memory intensive (lots of DMA active), so RAM is where I would start looking first. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 10:30:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DCCB037B6C9 for ; Wed, 17 Jan 2001 10:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HIU2D81853; Wed, 17 Jan 2001 10:30:02 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 10:30:02 -0800 (PST) Message-Id: <200101171830.f0HIU2D81853@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ronald F. Guilmette" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Ronald F. Guilmette" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Ronald F. Guilmette" To: "Justin T. Gibbs" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 10:23:36 -0800 In message <200101171817.f0HIHOs01442@aslan.scsiguy.com>, you wrote: >>>Synopsis: Advansys SCSI driver crashes random userland progs w/SIGPROF > >In all likelyhood, this has nothing to do with the AdvanSys controller. >It smells like a faulty or overclocked CPU... The CPU is definitely *not* overclocked. It an AMD K6-II/450 running at its rated speed in a well-cooled system. >... or faulty RAM. Performing disk >I/O is quite memory intensive (lots of DMA active), so RAM is where I >would start looking first. OK, so why does it fail consistantly with the Advansys controller, and yet it NEVER seems to fail with an Adaptec controller? I think that your theory about it being bad RAM is clearly incorrect, but I'm willing to try additional tests to rule out this possibility entirely. What would you suggest? I have memtest-86 here. If I run that for several hours and it shows now errors, then will you be convinced that there's a problem with the Advansys controller driver? P.S. I would like to get to the bottom of this as much as anyone, and I'm willing to do anything and everything on my end to aid the FreeBSD maintainers to isolate and then solve this problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 10:40:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A41E937B400 for ; Wed, 17 Jan 2001 10:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HIe2h82619; Wed, 17 Jan 2001 10:40:02 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 10:40:02 -0800 (PST) Message-Id: <200101171840.f0HIe2h82619@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Justin T. Gibbs" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Justin T. Gibbs" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Justin T. Gibbs" To: "Ronald F. Guilmette" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 11:33:21 -0700 >>... or faulty RAM. Performing disk >>I/O is quite memory intensive (lots of DMA active), so RAM is where I >>would start looking first. > >OK, so why does it fail consistantly with the Advansys controller, and >yet it NEVER seems to fail with an Adaptec controller? Most likely because the Adaptec accesses memory in a different pattern. This type of this happens all the time. >I think that your theory about it being bad RAM is clearly incorrect, but >I'm willing to try additional tests to rule out this possibility entirely. > >What would you suggest? I have memtest-86 here. If I run that for several >hours and it shows now errors, then will you be convinced that there's a >problem with the Advansys controller driver? Memory testors (other than the ones built in hardware) rarely find flaky memory problems. Your best bet is to trace out memory and see if the problem persists. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 10:50:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E9B6737B6C1 for ; Wed, 17 Jan 2001 10:50:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HIo3683225; Wed, 17 Jan 2001 10:50:03 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 10:50:03 -0800 (PST) Message-Id: <200101171850.f0HIo3683225@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ronald F. Guilmette" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Ronald F. Guilmette" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Ronald F. Guilmette" To: "Justin T. Gibbs" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 10:40:52 -0800 In message <200101171833.f0HIXLs02023@aslan.scsiguy.com>, you wrote: >Memory testors (other than the ones built in hardware) rarely find >flaky memory problems. Your best bet is to trace out memory and see >if the problem persists. I assume that you meant to say that I should "swap" out the memory for some other memory and then see what happens, yes? I'll try that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 11:20:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5E30837B6DD for ; Wed, 17 Jan 2001 11:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HJK1X87246; Wed, 17 Jan 2001 11:20:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 72F6537B6DF for ; Wed, 17 Jan 2001 11:10:22 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HJAMm86536; Wed, 17 Jan 2001 11:10:22 -0800 (PST) (envelope-from nobody) Message-Id: <200101171910.f0HJAMm86536@freefall.freebsd.org> Date: Wed, 17 Jan 2001 11:10:22 -0800 (PST) From: susan_giuliano@sbei.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24414: Replace Lan Media Corp., by SBE to read LMC by SBE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24414 >Category: misc >Synopsis: Replace Lan Media Corp., by SBE to read LMC by SBE >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 17 11:20:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Susan Giuliano >Release: >Organization: SBE, Inc. >Environment: >Description: Please correct the reading of the listing of LMC >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 12:10:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 380A037B6D6 for ; Wed, 17 Jan 2001 12:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HKA3B94023; Wed, 17 Jan 2001 12:10:03 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 12:10:03 -0800 (PST) Message-Id: <200101172010.f0HKA3B94023@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Justin T. Gibbs" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Justin T. Gibbs" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Justin T. Gibbs" To: "Ronald F. Guilmette" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 13:04:17 -0700 > >In message <200101171833.f0HIXLs02023@aslan.scsiguy.com>, you wrote: > >>Memory testors (other than the ones built in hardware) rarely find >>flaky memory problems. Your best bet is to trace out memory and see >>if the problem persists. > >I assume that you meant to say that I should "swap" out the memory for >some other memory and then see what happens, yes? I meant "trade", but yes. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 12:53:25 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B07C437B698; Wed, 17 Jan 2001 12:53:06 -0800 (PST) Received: (from jedgar@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HKr6j98686; Wed, 17 Jan 2001 12:53:06 -0800 (PST) (envelope-from jedgar) Date: Wed, 17 Jan 2001 12:53:06 -0800 (PST) From: Message-Id: <200101172053.f0HKr6j98686@freefall.freebsd.org> To: dot@dotat.at, jedgar@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/24278: strlcat may read from inaccessible memory Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: strlcat may read from inaccessible memory State-Changed-From-To: open->closed State-Changed-By: jedgar State-Changed-When: Wed Jan 17 12:51:50 PST 2001 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=24278 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 12:53:40 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0CB0637B404; Wed, 17 Jan 2001 12:53:23 -0800 (PST) Received: (from jedgar@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HKrMZ98757; Wed, 17 Jan 2001 12:53:22 -0800 (PST) (envelope-from jedgar) Date: Wed, 17 Jan 2001 12:53:22 -0800 (PST) From: Message-Id: <200101172053.f0HKrMZ98757@freefall.freebsd.org> To: dot@dotat.at, jedgar@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/24295: incorrect comment in strlcat.c Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: incorrect comment in strlcat.c State-Changed-From-To: open->closed State-Changed-By: jedgar State-Changed-When: Wed Jan 17 12:53:10 PST 2001 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=24295 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 14: 0:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id F3EA137B400 for ; Wed, 17 Jan 2001 14:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HM02207143; Wed, 17 Jan 2001 14:00:02 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 14:00:02 -0800 (PST) Message-Id: <200101172200.f0HM02207143@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ronald F. Guilmette" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Ronald F. Guilmette" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Ronald F. Guilmette" To: "Justin T. Gibbs" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 13:50:40 -0800 In message <200101172004.f0HK4Hs03305@aslan.scsiguy.com>, you wrote: >> >>In message <200101171833.f0HIXLs02023@aslan.scsiguy.com>, you wrote: >> >>>Memory testors (other than the ones built in hardware) rarely find >>>flaky memory problems. Your best bet is to trace out memory and see >>>if the problem persists. >> >>I assume that you meant to say that I should "swap" out the memory for >>some other memory and then see what happens, yes? > >I meant "trade", but yes. OK. It has been done. I hate to say you told me so, but you told me so. The system in question had two (2) 128MB SDRAM DIMMs in it, so it was easy enough for me to re-run my tests with first one of those two DIMMs in the system, and then the other. I did that, and sure enough, my little test failed consistantly (3 times) with one of the two DIMMs installed, and it passed the test consistantly (3 times0 with the other DIMM installed. So yea, I guess you were right. I looks like the memory. And yea, the one pass of memtest-86 I ran on the bad one did not show anything wrong. Thanks for your help. Ok, so how does one cancel/retract a FreeBSD PR? P.S. Anybody want to buy a single DIMM of 128MB of (almost) PC100 memory cheap? I'm selling it at a STEEP discount. :-) P.P.S. I guess we now have a brand new memory testing method... Install and Advansys SCSI controller into a FreeBSD 4.2 system and then just `dd' zeros to some big SCSI drive. (1/2 :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 14:30:20 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id D92D837B699 for ; Wed, 17 Jan 2001 14:30:02 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA33828; Wed, 17 Jan 2001 17:29:57 -0500 (EST) Date: Wed, 17 Jan 2001 17:29:57 -0500 (EST) From: "Matthew N. Dodd" To: Helge Oldach Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/24379: ahc broken in STABLE In-Reply-To: <200101170830.f0H8U2T12451@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 17 Jan 2001, Helge Oldach wrote: > The same is also in aic7770_probe. I have fixed both, but still get > the same trap at the same virtual address. I suspect that it happens a > bit earlier, e.g. during device probe. Except its not blowing up in the probe since it announces the device (which happens after the probe succeeds). -- | 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-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 14:34:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F6A237B400; Wed, 17 Jan 2001 14:34:02 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HMY2712227; Wed, 17 Jan 2001 14:34:02 -0800 (PST) (envelope-from dwmalone) Date: Wed, 17 Jan 2001 14:34:02 -0800 (PST) From: Message-Id: <200101172234.f0HMY2712227@freefall.freebsd.org> To: rfg@monkeys.com, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Advansys SCSI driver crashes random userland progs w/SIGPROF State-Changed-From-To: open->closed State-Changed-By: dwmalone State-Changed-When: Wed Jan 17 14:33:33 PST 2001 State-Changed-Why: Problem turned out to be a sick DIMM - closed at submitters request. http://www.freebsd.org/cgi/query-pr.cgi?pr=24401 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 17: 0:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5AB9737B69C for ; Wed, 17 Jan 2001 17:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0I101M28056; Wed, 17 Jan 2001 17:00:01 -0800 (PST) (envelope-from gnats) Received: from shasta.panasas.com (dsl-237-43-22-64.cust.dslnetworks.net [64.22.43.237]) by hub.freebsd.org (Postfix) with ESMTP id 2113C37B400 for ; Wed, 17 Jan 2001 16:58:16 -0800 (PST) Received: (from jin@localhost) by shasta.panasas.com (8.11.1/8.11.1) id f0I0wEs01319; Wed, 17 Jan 2001 16:58:14 -0800 (PST) (envelope-from jin) Message-Id: <200101180058.f0I0wEs01319@shasta.panasas.com> Date: Wed, 17 Jan 2001 16:58:14 -0800 (PST) From: Jin Guojun Reply-To: jin@panasas.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24418: read/write in thread library (-lc_r) does not do context switch Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24418 >Category: kern >Synopsis: read/write in thread library (-lc_r) does not do context switch >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 17 17:00:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Jin Guojun >Release: FreeBSD 4.2-RELEASE i386 >Organization: >Environment: FreeBSD STABLE and CURRENT >Description: threaded read/write shoule not block on I/O till I/O completion. Blocking on I/O causes thread I/O meaningless. read does context switch on stdin, and this is probably only I/O sys-call that FreeBSD does the context switch on thread. Thread does not do context switch on disk I/O and timed select(). I have not tested accept() and network I/O yet. Linux 2.2.x does not do context switch on thread I/O either, but linux 2.4.0 fixed it. Solaris does this well. Both Solaris and Linux 2.4.0 submit the I/O job to the driver, and immediately switch context to another thread regardless how less the I/O data is. This contest switch utilizes both system CPU and I/O CPU time. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Wed Jan 17 23:24:39 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 8043837B400 for ; Wed, 17 Jan 2001 23:24:21 -0800 (PST) Received: from hermes.hrz.uni-bielefeld.de (hermes.hrz.uni-bielefeld.de [129.70.4.55]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0G7C0082QKKJ1V@mail.uni-bielefeld.de> for freebsd-bugs@freebsd.org; Thu, 18 Jan 2001 08:24:19 +0100 (MET) Received: from hermes.hrz.uni-bielefeld.de (lkoeller@localhost) by hermes.hrz.uni-bielefeld.de (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id IAA20389; Thu, 18 Jan 2001 08:24:19 +0100 (MET) Date: Thu, 18 Jan 2001 08:24:19 +0100 From: Lars =?iso-8859-1?Q?K=F6ller?= X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~, lkoeller@cc.fh-lippe.de Message-id: <200101180724.IAA20389@hermes.hrz.uni-bielefeld.de> MIME-version: 1.0 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -------- Hi! It seem, that this bug dosen't hit a lot of people, but it's really = surprising, when a simple lptcontol -e (sometimes the next lpr file leads to the panic) can crash your machine! If there is noone who can/has time to fix = this problem, what about disabeling the functionality, to avoid = crashing a server when just playing around with printers :-( Thanks and best regards Lars -- = E-Mail: Lars.Koeller@Uni-Bielefeld.DE \ Lars K=F6ller lkoeller@FreeBSD.org \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany = Key-ID: A430D499 \ Tel: +49 521 106 4964 ----------- FreeBSD, what else? ---- http://www.freebsd.org -------------= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 1:20:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ACB9137B404 for ; Thu, 18 Jan 2001 01:20:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0I9K0T00244; Thu, 18 Jan 2001 01:20:00 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0671137B400 for ; Thu, 18 Jan 2001 01:18:20 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0I9IKc99980; Thu, 18 Jan 2001 01:18:20 -0800 (PST) (envelope-from nobody) Message-Id: <200101180918.f0I9IKc99980@freefall.freebsd.org> Date: Thu, 18 Jan 2001 01:18:20 -0800 (PST) From: michiel.dewilde@rug.ac.be To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24423: [Fix] syscons VT switching code errors Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24423 >Category: kern >Synopsis: [Fix] syscons VT switching code errors >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 01:20:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Michiel De Wilde >Release: 4.2-STABLE (actually RELENG_4 as of 2001/01/17) >Organization: University of Gent, Belgium >Environment: FreeBSD mdw.elis.rug.ac.be 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 17 17:30:08 CET 2001 root@mdw.elis.rug.ac.be:/usr/src/sys/compile/MDW_20001209_FBSD42_TOSHIBA_SATELLITE_2540CDT i386 >Description: I ran across these minor errors in syscons: In src/sys/dev/syscons/syscons.c [rev. 1.336.2.3], lines 954-963: When using ioctl VT_WAITACTIVE, parameter "data" is checked to see if it references a valid vty on the same adapter as the vty used for the request (lines 961-962). This check is "one off", because "data" is decremented by one later on. Furthermore, when looking at the code at line 969, I presume a value of 0 was meant to block the calling process until the requesting vty is activated. The same initial parameter check at lines 961-962 doesn't like zero, however. Finally, for conformity with VT_WAITACTIVE, VT_ACTIVATE should also be adapted to interpret a vty index of zero as "the requesting vty". In src/usr.sbin/vidcontrol/vidcontrol.c [rev. 1.32] (line 326): When switching back to VESA mode, "_IO('V', cur_mode - M_VESA_BASE)" should be used instead of "_IO('V', cur_mode)". Please take a look at the bottom of include file for the reason why this should be. >How-To-Repeat: syscons.c: Try to VT_WAITACTIVE the last vty and watch it fail. vidcontrol.c: (somewhat elaborate, sorry) Use a machine which hasn't compiled rastered text support into the kernel. Write an application to switch to some VESA mode and draw something, and quit the app without restoring text mode. Now you need vidcontrol to fix things. Try to switch back to rastered SW_VESA_800x600 using vidcontrol. It will fail, of course, but to which mode will it switch? >Fix: You can apply the following patches (please check for correctness first, we all make mistakes and I in particular): First, in plain text (for easy reference). Use the uuencoded versions below for the real stuff. === BEGIN syscons.c.diff --- src/sys/dev/syscons/syscons.c 2000/10/29 16:59:27 1.336.2.3 +++ src/sys/dev/syscons/syscons.c 2001/01/10 10:14:54 @@ -955,11 +955,14 @@ s = spltty(); sc_clean_up(sc->cur_scp); splx(s); - return sc_switch_scr(sc, *(int *)data - 1); + if (*(int *)data != 0) + return sc_switch_scr(sc, *(int *)data - 1); + else + return sc_switch_scr(sc, scp->index); case VT_WAITACTIVE: /* wait for switch to occur */ - if ((*(int *)data >= sc->first_vty + sc->vtys) - || (*(int *)data < sc->first_vty)) + if (((*(int *)data > sc->first_vty + sc->vtys) + || (*(int *)data <= sc->first_vty)) && (*(int *)data != 0)) return EINVAL; s = spltty(); error = sc_clean_up(sc->cur_scp); === END syscons.c.diff === BEGIN vidcontrol.c.diff --- src/usr.sbin/vidcontrol/vidcontrol.c 2000/01/12 12:30:33 1.32 +++ src/usr.sbin/vidcontrol/vidcontrol.c 2001/01/10 10:04:15 @@ -323,7 +323,7 @@ if (ioctl(0, KDRASTER, size)) { ioerr = errno; if (cur_mode >= M_VESA_BASE) - ioctl(0, _IO('V', cur_mode), NULL); + ioctl(0, _IO('V', cur_mode - M_VESA_BASE), NULL); else ioctl(0, _IO('S', cur_mode), NULL); warnc(ioerr, "cannot activate raster display"); === END vidcontrol.c.diff Here they are again tar-gzip-uuencoded, because if GNATS chooses to wrap lines, you'd better use these instead: begin 644 patch-syscons-vidcontrol.tgz M'XL(`'^Q9CH``^V5WV_:,!#'>0U_Q:T/;4(28N<'4=.U@FT\H'6=5!A[C#(G M:)9H@F(#9>L?/R=`!Q5MMX=NVG0?13B)[X[SV?F>6`E6Y*+-VBF?3!HO`B6D MX_O0`*!A0';'&NJ&'D#H>C3PB!]2]<8+W$X#R,NDL\]LA)-FBVJLSL-V;#/-)80XE#CN*=!.%)Q&;KC>MK;G==IN MVVN:IOE\#.JHBQ*@)*)^%/C-;A?LTR"P*`6S'GWH=IN@"3@',9M*N=*-L^J9 MQ6R:)7D\G^F"V1=L7L:"S=9SL^FM+M2MK969G)@I?-< M0LM($YF`#519FQJ?@+XW\>H_G/^#!4_5-RK+8OIR+>`9_8=.&-SK M?T!\->W3T$7]_Q-L]7\NRK;XPG/GYX%P=L_&N@U4$NZJAAUY)/*\;1MP[SO` MKT39:03$CVA0-P+/]:P0S/50MP&MUB5>,#G5B07OWUWWAJ/^M=)3_BU3^O*] MMM%XH91"Z83ZS8NSS3OE6.G$39%FE41^B,?]82]^TQOV:U6LW39QX\%'_61\ M8L'6P;#@ZM/E92WN3UNJ'K`;^=ZOSJ'N"W`@PO#@?]66RZ3,F5ZOR((CEN1Y M(2%ADB\2F4&9")F5D'(ED\GJ"!4001`$01`$01`$01`$01`$01`$01`$V>$' (88DQ^0`H``"9 ` end >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 2: 0:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E5B5B37B69E for ; Thu, 18 Jan 2001 02:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IA01804692; Thu, 18 Jan 2001 02:00:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0746437B6A0 for ; Thu, 18 Jan 2001 01:51:01 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0I9p1N03430; Thu, 18 Jan 2001 01:51:01 -0800 (PST) (envelope-from nobody) Message-Id: <200101180951.f0I9p1N03430@freefall.freebsd.org> Date: Thu, 18 Jan 2001 01:51:01 -0800 (PST) From: malte.sackmann@physik.uni-bremen.de To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24424: linux-programms under BSD cannot display all files in the directory Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24424 >Category: misc >Synopsis: linux-programms under BSD cannot display all files in the directory >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: wish >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 02:00:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Malte Sackmann >Release: 4.1.1 as well as 4.2 >Organization: Institute of Experimental Physics >Environment: FreeBSD gradient.physik.uni-bremen.de 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE #0: Mon Nov 13 15:35:13 CET 2000 sbosse@gradient.physik.uni-bremen.de: /usr/src/sys/compile/MYKERNEL i386 >Description: Its not possible to lookup all files in an directory if using a linux binary under xwindows. >How-To-Repeat: Install a linux binary and open for example "/etc/*". You will not see all existent files in that directory. You will see always the same randomly chosen 8 files. Try it with acroread or scilab. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 3:20:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 00EF937B69C for ; Thu, 18 Jan 2001 03:20:09 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IBK8f17406; Thu, 18 Jan 2001 03:20:08 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 03:20:08 -0800 (PST) Message-Id: <200101181120.f0IBK8f17406@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24424; it has been noted by GNATS. From: David Malone To: malte.sackmann@physik.uni-bremen.de Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Date: Thu, 18 Jan 2001 11:15:59 +0000 On Thu, Jan 18, 2001 at 01:51:01AM -0800, malte.sackmann@physik.uni-bremen.de wrote: > Install a linux binary and open for example "/etc/*". > You will not see all existent files in that directory. > You will see always the same randomly chosen 8 files. You are probably seeing the contents of /compat/linux/etc because programs run under Linux compatability look for a version of the file/directory under /compat/linux before they look starting at /. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 4:29:10 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from theo.physik.uni-bremen.de (theo.physik.uni-bremen.de [134.102.192.10]) by hub.freebsd.org (Postfix) with ESMTP id CB38D37B402 for ; Thu, 18 Jan 2001 04:28:52 -0800 (PST) Received: from localhost (maltes@localhost) by theo.physik.uni-bremen.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id NAA15494; Thu, 18 Jan 2001 13:18:53 +0100 Date: Thu, 18 Jan 2001 13:18:53 +0100 (MET) From: Malte Sackmann To: freebsd-bugs@FreeBSD.org Cc: sbosse@physik.uni-bremen.de Subject: Problem Report misc/24424 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have shortly discovered that the content from the /etc diretory comes of course from /compat/linux/etc. No question. But the problem with other directory contents is still the same!!!! For example a mounted cdrom /cdrom with strongly missing directories (some appeared, most disappeared) and files or various user/system directories. Tested for example with linux netscape (from FreeBSD-4.1.1 packages), acrobat4 . All programs show the same files/dirs or not. We have done some debugging in the kernel source code (mainly sys/i386/linux/linux_file.c) and have seen, that indeed the getdents function only returns some of the entries of the specific directory. But, from this already shrinked converted dir list (with missing entries), additionaly some files/dirs lost "on the way" to the user program and were never shown by the user program. Very strange and serious problem. Bye, Malte & Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 4:50:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6B37937B402 for ; Thu, 18 Jan 2001 04:50:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ICo6i31737; Thu, 18 Jan 2001 04:50:06 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 04:50:06 -0800 (PST) Message-Id: <200101181250.f0ICo6i31737@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Malte Sackmann Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Reply-To: Malte Sackmann Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24424; it has been noted by GNATS. From: Malte Sackmann To: David Malone Cc: malte.sackmann@physik.uni-bremen.de, freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Date: Thu, 18 Jan 2001 13:32:58 +0100 (MET) On Thu, 18 Jan 2001, David Malone wrote: > On Thu, Jan 18, 2001 at 01:51:01AM -0800, malte.sackmann@physik.uni-bremen.de wrote: > > Install a linux binary and open for example "/etc/*". > > You will not see all existent files in that directory. > > You will see always the same randomly chosen 8 files. > > You are probably seeing the contents of /compat/linux/etc because > programs run under Linux compatability look for a version of the > file/directory under /compat/linux before they look starting at /. > > David. > We have shortly discovered that the content from the /etc diretory comes of course from /compat/linux/etc. No question. But the problem with other directory contents is still the same!!!! For example a mounted cdrom /cdrom with strongly missing directories (some appeared, most disappeared) and files or various user/system directories. Tested for example with linux netscape (from FreeBSD-4.1.1 packages), acrobat4 . All programs show the same files/dirs or not. We have done some debugging in the kernel source code (mainly sys/i386/linux/linux_file.c) and have seen, that indeed the getdents function only returns some of the entries of the specific directory. But, from this already shrinked converted dir list (with missing entries), additionaly some files/dirs lost "on the way" to the user program and were never shown by the user program. Very strange and serious problem. Bye, Malte & Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 5: 0:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 250E137B404 for ; Thu, 18 Jan 2001 05:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ID03K33029; Thu, 18 Jan 2001 05:00:03 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 21BB537B698 for ; Thu, 18 Jan 2001 04:50:32 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ICoWv31766; Thu, 18 Jan 2001 04:50:32 -0800 (PST) (envelope-from nobody) Message-Id: <200101181250.f0ICoWv31766@freefall.freebsd.org> Date: Thu, 18 Jan 2001 04:50:32 -0800 (PST) From: barak@cwnt.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24426: CDROM not detected on a multi processosr Compaq DL360 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24426 >Category: misc >Synopsis: CDROM not detected on a multi processosr Compaq DL360 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 05:00:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Barak Enat >Release: 4.2-release with the MP patch from pr19338 >Organization: Charlotte Networks >Environment: FreeBSD simba.cwnt.co.il 4.2-RELEASE FreeBSD 4.2-RELEASE #2: Wed Jan 17 16:22:29 GMT 2001 barak@simba.cwnt.co.il:/usr/src/sys/compile/COMPAQ_DL360 i386 >Description: Hi, I'm using FreeBSD 4.2 release on a dual CPU DL360 machine. I have used the patch in pr19338 to fix the MP problem. However, when booting up the MP kernel, the CDROM is no longer detected, while it is detected under the GENERIC kernel. The relevant dmesg lines: ... ata1-master: ata_command: timeout waiting for intr ata1-master: identify failed ... In the GENERIC boot the regular acd0 detection appear, instead. Thanks, Barak barak@cwnt.com >How-To-Repeat: boot a recent MP kernel on a DL360. look at the dmesg, or try to operate the cdrom. >Fix: none >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 6:30:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4726D37B6A0 for ; Thu, 18 Jan 2001 06:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IEU3245698; Thu, 18 Jan 2001 06:30:03 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 06:30:03 -0800 (PST) Message-Id: <200101181430.f0IEU3245698@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Josef Karthauser Subject: Re: misc/24414: Replace Lan Media Corp., by SBE to read LMC by SBE Reply-To: Josef Karthauser Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24414; it has been noted by GNATS. From: Josef Karthauser To: susan_giuliano@sbei.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/24414: Replace Lan Media Corp., by SBE to read LMC by SBE Date: Thu, 18 Jan 2001 14:20:24 +0000 On Wed, Jan 17, 2001 at 11:10:22AM -0800, susan_giuliano@sbei.com wrote: > > >Number: 24414 > >Category: misc > >Synopsis: Replace Lan Media Corp., by SBE to read LMC by SBE > >Description: > Please correct the reading of the listing of LMC Hi, In which document? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 6:50:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 64EAF37B69B for ; Thu, 18 Jan 2001 06:50:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IEo7T18234; Thu, 18 Jan 2001 06:50:07 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2CCED37B400 for ; Thu, 18 Jan 2001 06:48:45 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IEmjT10960; Thu, 18 Jan 2001 06:48:45 -0800 (PST) (envelope-from nobody) Message-Id: <200101181448.f0IEmjT10960@freefall.freebsd.org> Date: Thu, 18 Jan 2001 06:48:45 -0800 (PST) From: kirma@cs.hut.fi To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/24433: NFSv3 service hangs when writing large amounts of data to FIFO Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24433 >Category: kern >Synopsis: NFSv3 service hangs when writing large amounts of data to FIFO >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 06:50:07 PST 2001 >Closed-Date: >Last-Modified: >Originator: Jari Kirma >Release: 4.0-STABLE >Organization: Helsinki University of Technology >Environment: FreeBSD nfs 4.0-STABLE FreeBSD 4.0-STABLE #2: Mon May 22 10:52:30 EEST 2000 root@nfs:/usr/src/sys/compile/NFSKERN i386 >Description: NFSv3 service stops functioning when large amount of data is written to FIFO in filesystem mounted from Solaris. NFS client: SunOS dev 5.7 Generic_106541-12 sun4u sparc SUNW,Ultra-4 >How-To-Repeat: Write lots of data to a FIFO, with configuration described above. "Small" amounts (that do not fill the Solaris internal buffers before getting read?) do not cause this effect. >Fix: Reboot the server. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 9:10:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id AB89837B404 for ; Thu, 18 Jan 2001 09:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IHA1w53298; Thu, 18 Jan 2001 09:10:01 -0800 (PST) (envelope-from gnats) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 12FED37B401 for ; Thu, 18 Jan 2001 09:09:32 -0800 (PST) Received: (from robert@localhost) by fledge.watson.org (8.11.1/8.11.1) id f0IH9Va82930; Thu, 18 Jan 2001 12:09:31 -0500 (EST) (envelope-from robert) Message-Id: <200101181709.f0IH9Va82930@fledge.watson.org> Date: Thu, 18 Jan 2001 12:09:31 -0500 (EST) From: rwatson@freebsd.org Reply-To: rwatson@freebsd.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24435: Unable to create root partition. Too big? Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24435 >Category: bin >Synopsis: Changing slice type causes Auto-partition to not work >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 09:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Robert Watson >Release: FreeBSD 4.2-RELEASE i386 >Organization: NAI Labs >Environment: 4.2-RELEASE install >Description: A co-worker of mine was installing FreeBSD 4.2-RELEASE on a machine that previously held two FAT partitions. Rather than delete and recreate the first partition to change it to a FreeBSD partition, he changed the partition "type" using T. The slice editor then showed "the right thing". However, when he then got to partition allocation, hitting A resulted in the following message: Unable to create the root partition. Too big? Going back and deleting the FreeBSD slice (was a FAT slice), then creating it again caused auto-partitioning to work fine. It sounds like the change in slice type is not being propagated properly to the partitioning phase. Also, it sounds like the debugging output from the partition creation is a tad on the not-so-specific-side. >How-To-Repeat: Use Partition Magic, DOS Fdisk, or some other magic tool to create two FAT partitions on a disk. Then run the 4.2-RELEASE install floppies and use T to change the first slice to a FreeBSD partition. Then continue to the FreeBSD partitioning screen, and hit A for automatic partition creation. The failure should occur. >Fix: Not attached. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 9:54:39 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5B14237B400; Thu, 18 Jan 2001 09:54:23 -0800 (PST) Received: (from gshapiro@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IHsNp57620; Thu, 18 Jan 2001 09:54:23 -0800 (PST) (envelope-from gshapiro) Date: Thu, 18 Jan 2001 09:54:23 -0800 (PST) From: Message-Id: <200101181754.f0IHsNp57620@freefall.freebsd.org> To: gshapiro@FreeBSD.org, freebsd-bugs@FreeBSD.org, gshapiro@FreeBSD.org Subject: Re: bin/24397: Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Responsible-Changed-From-To: freebsd-bugs->gshapiro Responsible-Changed-By: gshapiro Responsible-Changed-When: Thu Jan 18 09:53:47 PST 2001 Responsible-Changed-Why: Given to sendmail maintainer http://www.freebsd.org/cgi/query-pr.cgi?pr=24397 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 10:20:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4612537B400 for ; Thu, 18 Jan 2001 10:20:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IIK3E62239; Thu, 18 Jan 2001 10:20:03 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 10:20:03 -0800 (PST) Message-Id: <200101181820.f0IIK3E62239@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Mark W. Krentel" Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Reply-To: "Mark W. Krentel" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24424; it has been noted by GNATS. From: "Mark W. Krentel" To: malte.sackmann@physik.uni-bremen.de Cc: dwmalone@maths.tcd.ie, freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Date: Thu, 18 Jan 2001 13:14:01 -0500 (EST) > For example a mounted cdrom /cdrom with strongly missing directories > (some appeared, most disappeared) and files or various user/system > directories. I'm pretty sure this is the same problem reported in PR kern/19407. There was a bug in the Linuxulator that caused the linux readdir(3) to prematurely return NULL on non-UFS partitions. Your Linux programs can correctly read Freebsd partitions, right? Marcel Moolenaar fixed the problem shortly before 4.2-Release. So, upgrade to 4.2 or later and see if that fixes the problem. --Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 10:39:18 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from relay3.inwind.it (relay3.inwind.it [212.141.53.74]) by hub.freebsd.org (Postfix) with ESMTP id 63CE037B69B for ; Thu, 18 Jan 2001 10:39:00 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.154.184) by relay3.inwind.it (5.1.056) id 3A40BF86005CDF97; Thu, 18 Jan 2001 19:37:57 +0100 From: Salvo Bartolotta Date: Thu, 18 Jan 2001 18:40:29 GMT Message-ID: <20010118.18402900@bartequi.ottodomain.org> Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory To: Malte Sackmann , David Malone Cc: freebsd-bugs@FreeBSD.ORG References: <200101181250.f0ICo6i31737@freefall.freebsd.org> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/18/01, 1:50:06 PM, Malte Sackmann wrote regarding Re: misc/24424: linux-programms under BSD cannot display all files in the directory: > The following reply was made to PR misc/24424; it has been noted by GNATS. > From: Malte Sackmann > To: David Malone > Cc: malte.sackmann@physik.uni-bremen.de, > freebsd-gnats-submit@FreeBSD.org > Subject: Re: misc/24424: linux-programms under BSD cannot display all files > in the directory > Date: Thu, 18 Jan 2001 13:32:58 +0100 (MET) > On Thu, 18 Jan 2001, David Malone wrote: > > On Thu, Jan 18, 2001 at 01:51:01AM -0800, malte.sackmann@physik.uni-bremen.de wrote: > > > Install a linux binary and open for example "/etc/*". > > > You will not see all existent files in that directory. > > > You will see always the same randomly chosen 8 files. > > > > You are probably seeing the contents of /compat/linux/etc because > > programs run under Linux compatability look for a version of the > > file/directory under /compat/linux before they look starting at /. > > > > David. > > > We have shortly discovered that the content from the /etc diretory > comes of course from /compat/linux/etc. No question. > But the problem with other directory contents is still the same!!!! > For example a mounted cdrom /cdrom with strongly missing directories > (some appeared, most disappeared) and files or various user/system > directories. Tested for example with linux netscape (from FreeBSD-4.1.1 > packages), acrobat4 . All programs show the same files/dirs or not. > We have done some debugging in the kernel source code (mainly > sys/i386/linux/linux_file.c) and have seen, that indeed the > getdents function only returns some of the entries of the specific > directory. But, from this already shrinked converted dir list (with > missing entries), additionaly some files/dirs lost "on the way" to the > user program and were never shown by the user program. > Very strange and serious problem. Dear Malte Sackmann and David Malone, I seem to understand that the problem is, as it were, somewhat cosmetic. The "features" described below might be relevant to your discussion. When I fire up eg StarOffice-5.X and I access various directories from its "open window" (absit iniuria verbis :-), I can only see **part** of their content(s). So far so good. However, if I specify an existing filename (or directory name) not shown in the tree by the dialog box, the name is completed, and it is also shown on the filename line (but NOT within the directory tree); besides -- wait for it -- I can **load** the file, or access the directory. Further, the above ahem "method" seems to recall these linux programs -- or rather the underlying filesystem facilities -- to a... sense of duty, and I can see much more directory content (if not all of it). Best regards & best of luck, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 10:47:47 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id A5AEE37B404 for ; Thu, 18 Jan 2001 10:47:28 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.154.184) by relay4.inwind.it (5.1.056) id 3A5C385100200A6E; Thu, 18 Jan 2001 19:47:11 +0100 From: Salvo Bartolotta Date: Thu, 18 Jan 2001 18:49:43 GMT Message-ID: <20010118.18494300@bartequi.ottodomain.org> Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory To: "Mark W. Krentel" Cc: freebsd-bugs@FreeBSD.org, "Mark W. Krentel" , dwmalone@maths.tcd.ie In-Reply-To: <200101181820.f0IIK3E62239@freefall.freebsd.org> References: <200101181820.f0IIK3E62239@freefall.freebsd.org> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/18/01, 7:20:03 PM, "Mark W. Krentel" wrote= =20 regarding Re: misc/24424: linux-programms under BSD cannot display all=20 files in the directory: > I'm pretty sure this is the same problem reported in PR kern/19407. > There was a bug in the Linuxulator that caused the linux readdir(3) > to prematurely return NULL on non-UFS partitions. Your Linux > programs can correctly read Freebsd partitions, right? > Marcel Moolenaar fixed the problem shortly before 4.2-Release. > So, upgrade to 4.2 or later and see if that fixes the problem. ^^^^^^^^^^^^^^ =20 ^^^^^^^^^^^^^^ =20 *sigh* I apologize for omitting a relevant item of information in my=20 previous message: what I described still occurs under 4.2-STABLE,=20 sources as of January, 5, 2001. Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 11:20:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6833937B400 for ; Thu, 18 Jan 2001 11:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0IJK2p70794; Thu, 18 Jan 2001 11:20:02 -0800 (PST) (envelope-from gnats) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 4485737B400 for ; Thu, 18 Jan 2001 11:14:19 -0800 (PST) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.2/8.11.2) with ESMTP id f0IJEHo99157 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 18 Jan 2001 20:14:17 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.0/8.11.0) id f0IJEGZ35527; Thu, 18 Jan 2001 20:14:16 +0100 (CET) Message-Id: <200101181914.f0IJEGZ35527@kazi.dcse.fee.vutbr.cz> Date: Thu, 18 Jan 2001 20:14:16 +0100 (CET) From: cejkar@dcse.fee.vutbr.cz Reply-To: cejkar@dcse.fee.vutbr.cz To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24437: syscons - MOUSE_MOUSECHAR fix Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24437 >Category: kern >Synopsis: syscons - MOUSE_MOUSECHAR fix >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 11:20:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Rudolf Cejka >Release: FreeBSD 5.0-CURRENT i386 >Organization: Brno University of Technology, FEE&CS, Czech Republic >Environment: All systems with MOUSE_MOUSECHAR ioctl. >Description: When changing MOUSE_MOUSECHAR over vidcontrol, original characters are not restored correcty. Instead, characters 0, 1, 2, and 3 are loaded in their position: Patch #1, lower change. Right values for MOUSE_MOUSECHAR (c) are 0 <= c <= UCHAR_MAX - 3, but kernel allows only 0 <= c <= UCHAR_MAX - 5 and vidcontrol allows 0 <= c <= UCHAR_MAX. Kernel fix: Patch #1, upper change. Vidcontrol fix: Patch #2. >How-To-Repeat: >Fix: $FreeBSD: src/sys/dev/syscons/scmouse.c,v 1.16 2000/10/09 08:08:28 phk Exp $ --- scmouse.c.orig Thu Jan 18 18:18:32 2001 +++ scmouse.c Thu Jan 18 19:35:38 2001 @@ -874,13 +874,15 @@ if (mouse->u.mouse_char < 0) { mouse->u.mouse_char = scp->sc->mouse_char; } else { - if (mouse->u.mouse_char >= UCHAR_MAX - 4) + if (mouse->u.mouse_char > UCHAR_MAX - 3) return EINVAL; s = spltty(); sc_remove_all_mouse(scp->sc); #ifndef SC_NO_FONT_LOADING if (ISTEXTSC(cur_scp) && (cur_scp->font != NULL)) - sc_load_font(cur_scp, 0, cur_scp->font_size, cur_scp->font, + sc_load_font(cur_scp, 0, cur_scp->font_size, + cur_scp->font + cur_scp->font_size + * cur_scp->sc->mouse_char, cur_scp->sc->mouse_char, 4); #endif scp->sc->mouse_char = mouse->u.mouse_char; "$FreeBSD: src/usr.sbin/vidcontrol/vidcontrol.c,v 1.33 2000/10/08 21:34:00 phk Exp $"; --- vidcontrol.c.orig Thu Jan 18 19:44:17 2001 +++ vidcontrol.c Thu Jan 18 19:44:31 2001 @@ -415,8 +415,8 @@ long l; l = strtol(arg, NULL, 0); - if ((l < 0) || (l > UCHAR_MAX)) { - warnx("argument to -M must be 0 through %d", UCHAR_MAX); + if ((l < 0) || (l > UCHAR_MAX - 3)) { + warnx("argument to -M must be 0 through %d", UCHAR_MAX - 3); return; } mouse.operation = MOUSE_MOUSECHAR; >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 13: 7:48 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from ns1.virtuale.ws (ns1.virtuale.ws [210.155.63.114]) by hub.freebsd.org (Postfix) with ESMTP id EFF6437B699 for ; Thu, 18 Jan 2001 13:07:03 -0800 (PST) Received: (from nobody@localhost) by ns1.virtuale.ws (8.9.3/8.9.3) id GAA14335; Fri, 19 Jan 2001 06:09:10 +0900 Date: Fri, 19 Jan 2001 06:09:10 +0900 Message-Id: <200101182109.GAA14335@ns1.virtuale.ws> To: freebsd-bugs@freebsd.org Subject: Internet Entertainment Solution From: swesu@hotmail.com Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ccccccccccccccccccccccccc @@@ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€”Ì”„‚Ì‚š’m‚点 ccccccccccccccccccccccccc ‚Šz‚Ì”ï—p‚ª‚©‚©‚Á‚Ä‚¢‚œ“®‰æ‚̃VƒXƒeƒ€‚ðA‚±‚Ì“x ’ቿŠi‚Ŕ̔„‚·‚鎖‚É‚È‚è‚Ü‚µ‚œB ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€‚Ƃ́EEE „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚PDƒXƒ^ƒWƒI‚ð—pˆÓ‚µA‚»‚±‚ɃrƒfƒIƒJƒƒ‰‚ðÝ’uB @@—«‚ªƒXƒ^ƒ“ƒoƒC‚µ‚Ü‚·B ‚QD‰ïˆõ‚Ì’j«‚́Aƒƒ“ƒo[“o˜^‚ð‚·‚Ü‚¹AID‚ÆPW‚ð @@“ü—Í‚µA‚»‚Ì“®‰æ‚ð‰{——‚µ‚Ü‚·B ‚RD’j«‚́Auƒ`ƒƒƒbƒgv‚Æ‚¢‚€ƒVƒXƒeƒ€‚ðŽg‚¢A @@•¶Žš‚Ÿ‚¯‚ŏ—«‚ƃRƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“‚ð‚Æ‚è‚Ü‚·B ‚SD‚»‚Ì•¶Žš‚ðƒXƒ^ƒWƒI‚̏—‚ÌŽq‚̓fƒBƒXƒvƒŒ[‚Å @@Œ©‚È‚ª‚ç‰ï˜b‚µ‚Ü‚·B—‚ÌŽq‚̓rƒfƒIƒJƒƒ‰‚É @@Œü‚©‚Á‚Ęb‚ð‚µ‚œ‚èA—lX‚È“®ì‚ð‚µ‚œ‚è‚·‚ê‚Î @@‚¢‚¢‚Ÿ‚¯‚Å‚·B‚»‚ꂪ‰ïˆõ’j«‚ɃCƒ“ƒ^[ƒlƒbƒg @@‚ð—˜—p‚µ‚Ä”zM‚³‚ê‚Ü‚·B ‚TD—˜—p‚µ‚œŽžŠÔ•ª‚Ì‰Û‹à‚ª‹L˜^‚³‚êAˆê’è‚ÌŽžŠÔ‚Å @@¿‹ƒ[ƒ‹‚𑗐M‚µ‚Ü‚·B „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚±‚Ì‘S‚ẴVƒXƒeƒ€‚ð—pˆÓ‚·‚é‚Ì‚É—lX‚ȃ‰ƒCƒZƒ“ƒX ‚â‹@Þ‚ȂǍž‚݂ŁA1ç–œŽã‚Ì”ï—p‚ª‚©‚©‚è‚Ü‚·B ¡‰ñ‚́A‚±‚̈ê˜A‚̃VƒXƒeƒ€Eƒ‰ƒCƒZƒ“ƒXE‹@Þ‚ðA ‚܂Ƃ߂ĒቿŠi‚Ŕ̔„’v‚µ‚Ü‚·BŒã‚́AADSL‚È‚Ç‚Ì o—ˆ‚é‚Ÿ‚¯‘¬‚¢‰ñü‚Ə­X‚Ì‹@Þ‚ð—pˆÓ‚·‚é‚Ÿ‚¯‚ŁA ‚·‚®‚É‚±‚́uƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€v‚ð—˜—p‚·‚鎖 ‚ªo—ˆ‚Ü‚·Bo‰ï‚¢ƒTƒCƒg‚Ŗڋʂ̃Rƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“ ‚É—˜—p‚·‚é‚Ì‚à‚悵AƒAƒ_ƒ‹ƒgŠÖ˜A‚Å—˜—p‚·‚é‚à‚悵A ‚±‚̒ቿŠi‚Å—pˆÓ‚Å‚«‚é—l‚ȃVƒXƒeƒ€‚Å‚Í‚ ‚è‚Ü‚¹‚ñB ¥”ñ‚±‚Ì‹@‰ï‚ðŒ©“Š‚³‚žAVƒrƒWƒlƒX‚Ŗׂ¯‚ĉº‚³‚¢B “Á‚É‚Ç‚ñ‚ȃWƒƒƒ“ƒ‹‚Å‚àu—«‚Ì’²’B‚ɍ¢‚ç‚È‚¢v—l ‚ÈŽ–‹Æ‚ɍłàƒ}ƒbƒ`‚µ‚Ä‚¢‚Ü‚·B ƒVƒXƒeƒ€‡@ Windows NT „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MSSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽè“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ Eƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ EDual CPU(P‡U400x2jNTƒT[ƒo[ EƒrƒfƒIƒJƒƒ‰ EPCiNECj „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‘Šz1ç–œŽã‚ō\\’z‚µ‚œƒVƒXƒeƒ€‡@‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒVƒXƒeƒ€‡A Redhat Linux 6.2 „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MYSQLAMSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽ©“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ Eƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ŠJ”­”ï—p500–œŽã‚ō\\’zo—ˆ‚éƒVƒXƒeƒ€‡A‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Łuƒ‰ƒCƒuƒ`ƒƒƒbƒgv‚ðs‚€ê‡A Šù‚ÉŽÀÑ‚Ì‚ ‚éƒRƒ“ƒeƒ“ƒc–ˆ‚š÷‚è‚·‚鎖‚ào—ˆ‚Ü‚·B ‚±‚̏ꍇAŠù‚É1–œl’ö“x‚̌ڋqƒf[ƒ^‚à‚š÷‚è‚·‚é Ž–‚ªo—ˆ‚Ü‚·Bwebƒy[ƒW‚àŠù‚É’m–Œ“x‚Ì‚à‚Ì‚ð‚»‚Ì‚Ü ‚܁A—˜—p‚Å‚«‚Ü‚·‚µAŠeŽíƒT[ƒ`ƒGƒ“ƒWƒ“‚È‚Ç‚É‚à “o˜^Ï‚݂̃hƒƒCƒ“‚ª‚»‚Ì‚Ü‚Ü—˜—p‚Å‚«‚Ü‚·B—v‚·‚é‚É ŽÀÑ‚Ì‚ ‚éƒTƒCƒg‚ð‚»‚Ì‚Ü‚ÜƒVƒXƒeƒ€E‹@Þ–ˆA‚š÷‚è o—ˆ‚é‚ÆŒŸ‚€‚±‚Æ‚Å‚·BV‹K‚̃vƒƒ‚[ƒVƒ‡ƒ“‚È‚Ç‚Ì •K—v‚à‚È‚­A‚ ‚é’ö“x‚ׂ̖¯‚à–ñ‘©‚³‚ê‚Ä‚¢‚é‚킯‚Å‚·B ‚±‚¿‚ç‚ð‚²Šó–]‚̏ꍇ‚́A‚²‘Š’k‰º‚³‚¢B ‚Ü‚œAƒvƒƒOƒ‰ƒ€‚âƒT[ƒo[‚ȂǁA’P‘̂ł̔̔„‚à l‚Š‚Ä‚š‚è‚Ü‚·BReal Server‚Ȃǂ̃‰ƒCƒZƒ“ƒX‚́A 300–œ’ö‚µ‚Ü‚·‚ªA“–ŽÐ‚ł́Aƒ‰ƒCƒZƒ“ƒX–ˆA’ቿŠi‚Å ‚š÷‚è‚·‚邱‚Æ‚ªo—ˆ‚Ü‚·‚̂ŁA‚²‘Š’k‰º‚³‚¢B ‹ï‘Ì“I‚É‚Ç‚€‚¢‚Á‚œƒVƒXƒeƒ€‚È‚Ì‚©‘ÌŒ±‚µ‚œ‚¢•û‚́A ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Å‚·‚ªAŽÀÛ‚É‚²——‚É‚È‚ê‚Ü‚·‚̂ŁA ‰º‹LURL‚ð–K–₵‚Ä‚Ý‚Ä‚­‚Ÿ‚³‚¢B http://www.dreamroom.ws/ ‚±‚Ì‹@‰ï‚ð“Š‚·Žè‚Í‚ ‚è‚Ü‚¹‚ñBV‹KŽ–‹Æ‚ðŒŸ“¢‚Ì•ûA ¡‚·‚®A‚²˜A—‰º‚³‚¢B‚ ‚ç‚ä‚錏‚ŁA‘Š’k‚³‚¹‚Ä ’ž‚«‚Ü‚·B ccccccccccccccccccccccccc <‚š–â‚¢‡‚¹‚Í‚±‚¿‚ç‚Ü‚Å>@š@info@dreamroom.ws ccccccccccccccccccccccccc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 13: 7:50 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from ns1.virtuale.ws (ns1.virtuale.ws [210.155.63.114]) by hub.freebsd.org (Postfix) with ESMTP id 202D937B69B for ; Thu, 18 Jan 2001 13:07:05 -0800 (PST) Received: (from nobody@localhost) by ns1.virtuale.ws (8.9.3/8.9.3) id GAA14389; Fri, 19 Jan 2001 06:09:13 +0900 Date: Fri, 19 Jan 2001 06:09:13 +0900 Message-Id: <200101182109.GAA14389@ns1.virtuale.ws> To: freebsd-bugs@freebsd.org Subject: Internet Entertainment Solution From: swesu@hotmail.com Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ccccccccccccccccccccccccc @@@ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€”Ì”„‚Ì‚š’m‚点 ccccccccccccccccccccccccc ‚Šz‚Ì”ï—p‚ª‚©‚©‚Á‚Ä‚¢‚œ“®‰æ‚̃VƒXƒeƒ€‚ðA‚±‚Ì“x ’ቿŠi‚Ŕ̔„‚·‚鎖‚É‚È‚è‚Ü‚µ‚œB ƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€‚Ƃ́EEE „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚PDƒXƒ^ƒWƒI‚ð—pˆÓ‚µA‚»‚±‚ɃrƒfƒIƒJƒƒ‰‚ðÝ’uB @@—«‚ªƒXƒ^ƒ“ƒoƒC‚µ‚Ü‚·B ‚QD‰ïˆõ‚Ì’j«‚́Aƒƒ“ƒo[“o˜^‚ð‚·‚Ü‚¹AID‚ÆPW‚ð @@“ü—Í‚µA‚»‚Ì“®‰æ‚ð‰{——‚µ‚Ü‚·B ‚RD’j«‚́Auƒ`ƒƒƒbƒgv‚Æ‚¢‚€ƒVƒXƒeƒ€‚ðŽg‚¢A @@•¶Žš‚Ÿ‚¯‚ŏ—«‚ƃRƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“‚ð‚Æ‚è‚Ü‚·B ‚SD‚»‚Ì•¶Žš‚ðƒXƒ^ƒWƒI‚̏—‚ÌŽq‚̓fƒBƒXƒvƒŒ[‚Å @@Œ©‚È‚ª‚ç‰ï˜b‚µ‚Ü‚·B—‚ÌŽq‚̓rƒfƒIƒJƒƒ‰‚É @@Œü‚©‚Á‚Ęb‚ð‚µ‚œ‚èA—lX‚È“®ì‚ð‚µ‚œ‚è‚·‚ê‚Î @@‚¢‚¢‚Ÿ‚¯‚Å‚·B‚»‚ꂪ‰ïˆõ’j«‚ɃCƒ“ƒ^[ƒlƒbƒg @@‚ð—˜—p‚µ‚Ä”zM‚³‚ê‚Ü‚·B ‚TD—˜—p‚µ‚œŽžŠÔ•ª‚Ì‰Û‹à‚ª‹L˜^‚³‚êAˆê’è‚ÌŽžŠÔ‚Å @@¿‹ƒ[ƒ‹‚𑗐M‚µ‚Ü‚·B „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‚±‚Ì‘S‚ẴVƒXƒeƒ€‚ð—pˆÓ‚·‚é‚Ì‚É—lX‚ȃ‰ƒCƒZƒ“ƒX ‚â‹@Þ‚ȂǍž‚݂ŁA1ç–œŽã‚Ì”ï—p‚ª‚©‚©‚è‚Ü‚·B ¡‰ñ‚́A‚±‚̈ê˜A‚̃VƒXƒeƒ€Eƒ‰ƒCƒZƒ“ƒXE‹@Þ‚ðA ‚܂Ƃ߂ĒቿŠi‚Ŕ̔„’v‚µ‚Ü‚·BŒã‚́AADSL‚È‚Ç‚Ì o—ˆ‚é‚Ÿ‚¯‘¬‚¢‰ñü‚Ə­X‚Ì‹@Þ‚ð—pˆÓ‚·‚é‚Ÿ‚¯‚ŁA ‚·‚®‚É‚±‚́uƒ‰ƒCƒuƒ`ƒƒƒbƒgƒVƒXƒeƒ€v‚ð—˜—p‚·‚鎖 ‚ªo—ˆ‚Ü‚·Bo‰ï‚¢ƒTƒCƒg‚Ŗڋʂ̃Rƒ~ƒ…ƒjƒP[ƒVƒ‡ƒ“ ‚É—˜—p‚·‚é‚Ì‚à‚悵AƒAƒ_ƒ‹ƒgŠÖ˜A‚Å—˜—p‚·‚é‚à‚悵A ‚±‚̒ቿŠi‚Å—pˆÓ‚Å‚«‚é—l‚ȃVƒXƒeƒ€‚Å‚Í‚ ‚è‚Ü‚¹‚ñB ¥”ñ‚±‚Ì‹@‰ï‚ðŒ©“Š‚³‚žAVƒrƒWƒlƒX‚Ŗׂ¯‚ĉº‚³‚¢B “Á‚É‚Ç‚ñ‚ȃWƒƒƒ“ƒ‹‚Å‚àu—«‚Ì’²’B‚ɍ¢‚ç‚È‚¢v—l ‚ÈŽ–‹Æ‚ɍłàƒ}ƒbƒ`‚µ‚Ä‚¢‚Ü‚·B ƒVƒXƒeƒ€‡@ Windows NT „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MSSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽè“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ Eƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ EDual CPU(P‡U400x2jNTƒT[ƒo[ EƒrƒfƒIƒJƒƒ‰ EPCiNECj „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ‘Šz1ç–œŽã‚ō\\’z‚µ‚œƒVƒXƒeƒ€‡@‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒVƒXƒeƒ€‡A Redhat Linux 6.2 „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ EReal Server EDataBase(MYSQLAMSQL) EŒŸjƒvƒƒOƒ‰ƒ€•¿‹ƒvƒƒOƒ‰ƒ€iŽ©“®j Eƒƒ“ƒo[“o˜^ƒvƒƒOƒ‰ƒ€ ? ƒ`ƒƒƒbƒgƒvƒƒOƒ‰ƒ€ „Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ„Ÿ ŠJ”­”ï—p500–œŽã‚ō\\’zo—ˆ‚éƒVƒXƒeƒ€‡A‚ð300–œ‰~‚Å ”Ì”„‚µ‚Ü‚·B ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Łuƒ‰ƒCƒuƒ`ƒƒƒbƒgv‚ðs‚€ê‡A Šù‚ÉŽÀÑ‚Ì‚ ‚éƒRƒ“ƒeƒ“ƒc–ˆ‚š÷‚è‚·‚鎖‚ào—ˆ‚Ü‚·B ‚±‚̏ꍇAŠù‚É1–œl’ö“x‚̌ڋqƒf[ƒ^‚à‚š÷‚è‚·‚é Ž–‚ªo—ˆ‚Ü‚·Bwebƒy[ƒW‚àŠù‚É’m–Œ“x‚Ì‚à‚Ì‚ð‚»‚Ì‚Ü ‚܁A—˜—p‚Å‚«‚Ü‚·‚µAŠeŽíƒT[ƒ`ƒGƒ“ƒWƒ“‚È‚Ç‚É‚à “o˜^Ï‚݂̃hƒƒCƒ“‚ª‚»‚Ì‚Ü‚Ü—˜—p‚Å‚«‚Ü‚·B—v‚·‚é‚É ŽÀÑ‚Ì‚ ‚éƒTƒCƒg‚ð‚»‚Ì‚Ü‚ÜƒVƒXƒeƒ€E‹@Þ–ˆA‚š÷‚è o—ˆ‚é‚ÆŒŸ‚€‚±‚Æ‚Å‚·BV‹K‚̃vƒƒ‚[ƒVƒ‡ƒ“‚È‚Ç‚Ì •K—v‚à‚È‚­A‚ ‚é’ö“x‚ׂ̖¯‚à–ñ‘©‚³‚ê‚Ä‚¢‚é‚킯‚Å‚·B ‚±‚¿‚ç‚ð‚²Šó–]‚̏ꍇ‚́A‚²‘Š’k‰º‚³‚¢B ‚Ü‚œAƒvƒƒOƒ‰ƒ€‚âƒT[ƒo[‚ȂǁA’P‘̂ł̔̔„‚à l‚Š‚Ä‚š‚è‚Ü‚·BReal Server‚Ȃǂ̃‰ƒCƒZƒ“ƒX‚́A 300–œ’ö‚µ‚Ü‚·‚ªA“–ŽÐ‚ł́Aƒ‰ƒCƒZƒ“ƒX–ˆA’ቿŠi‚Å ‚š÷‚è‚·‚邱‚Æ‚ªo—ˆ‚Ü‚·‚̂ŁA‚²‘Š’k‰º‚³‚¢B ‹ï‘Ì“I‚É‚Ç‚€‚¢‚Á‚œƒVƒXƒeƒ€‚È‚Ì‚©‘ÌŒ±‚µ‚œ‚¢•û‚́A ƒAƒ_ƒ‹ƒgƒTƒCƒg‚Å‚·‚ªAŽÀÛ‚É‚²——‚É‚È‚ê‚Ü‚·‚̂ŁA ‰º‹LURL‚ð–K–₵‚Ä‚Ý‚Ä‚­‚Ÿ‚³‚¢B http://www.dreamroom.ws/ ‚±‚Ì‹@‰ï‚ð“Š‚·Žè‚Í‚ ‚è‚Ü‚¹‚ñBV‹KŽ–‹Æ‚ðŒŸ“¢‚Ì•ûA ¡‚·‚®A‚²˜A—‰º‚³‚¢B‚ ‚ç‚ä‚錏‚ŁA‘Š’k‚³‚¹‚Ä ’ž‚«‚Ü‚·B ccccccccccccccccccccccccc <‚š–â‚¢‡‚¹‚Í‚±‚¿‚ç‚Ü‚Å>@š@info@dreamroom.ws ccccccccccccccccccccccccc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 13:10:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5F42C37B698 for ; Thu, 18 Jan 2001 13:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ILA1O84726; Thu, 18 Jan 2001 13:10:01 -0800 (PST) (envelope-from gnats) Received: from yog-sothoth.sgi.com (unknown [192.48.160.10]) by hub.freebsd.org (Postfix) with ESMTP id DD89B37B698 for ; Thu, 18 Jan 2001 13:09:52 -0800 (PST) Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id WAA10802386 for <@eugate.sgi.com:FreeBSD-gnats-submit@freebsd.org>; Thu, 18 Jan 2001 22:08:28 +0100 (CET) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id WAA09127; Thu, 18 Jan 2001 22:08:08 +0100 Received: from sgi.com (private-gk.munich.sgi.com [144.253.196.49]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id WAA40054; Thu, 18 Jan 2001 22:08:07 +0100 (MET) Message-Id: <3A675AF7.11C46322@sgi.com> Date: Thu, 18 Jan 2001 22:07:04 +0100 From: "Georg-W. Koltermann" To: FreeBSD-gnats-submit@freebsd.org Subject: bin/24438: sys.mk is lacking single suffix rules for C++ Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24438 >Category: bin >Synopsis: sys.mk is lacking single suffix rules for C++ >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 13:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Georg-W. Koltermann >Release: FreeBSD 4.2-RELEASE i386 >Organization: SGI >Environment: >Description: /usr/share/mk/sys.mk contains only double suffix rules for C++ sources: .cc.o .cpp.o .cxx.o .C.o. The single suffix rules .cc .cpp .cxx .C are missing. See fix section for a suitable patch. >How-To-Repeat: Create a C++ source file, e.g. sample.C, without a Makefile. Type "make sample". Make barfs "make: don't know how to make sample. Stop". >Fix: --- sys.mk.old Mon Nov 20 13:01:21 2000 +++ sys.mk Thu Jan 18 21:55:20 2001 @@ -181,6 +181,9 @@ .cc.o .cpp.o .cxx.o .C.o: ${CXX} ${CXXFLAGS} -c ${.IMPSRC} +.cc .cpp .cxx .C: + ${CXX} ${CXXFLAGS} ${LDFLAGS} ${.IMPSRC} ${LDLIBS} -o ${.TARGET} + .m.o: ${OBJC} ${OBJCFLAGS} -c ${.IMPSRC} >Release-Note: >Audit-Trail: >Unformatted: X-send-pr-version: 3.2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 13:20:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C34BF37B400 for ; Thu, 18 Jan 2001 13:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ILK4b85846; Thu, 18 Jan 2001 13:20:04 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 13:20:04 -0800 (PST) Message-Id: <200101182120.f0ILK4b85846@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kris Kennaway Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Reply-To: Kris Kennaway Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24424; it has been noted by GNATS. From: Kris Kennaway To: malte.sackmann@physik.uni-bremen.de Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/24424: linux-programms under BSD cannot display all files in the directory Date: Thu, 18 Jan 2001 13:17:28 -0800 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 18, 2001 at 01:51:01AM -0800, malte.sackmann@physik.uni-bremen.= de wrote: > 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE #0:=20 ISTR this problem being fixed recently in -stable - can you confirm? Kris -- NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6Z11oWry0BWjoQKURAkN1AJ9C2Li7B0fLPj9InsftrdgO3ReZGQCeOEEJ IVB7Ln++t1GQCVHdoubpaOI= =QDrb -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 13:50:27 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3957E37B401 for ; Thu, 18 Jan 2001 13:50:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0ILo5S90332; Thu, 18 Jan 2001 13:50:05 -0800 (PST) (envelope-from gnats) Received: from cronic.tellme.com (cronic.tellme.com [209.157.156.28]) by hub.freebsd.org (Postfix) with ESMTP id 340EA37B400 for ; Thu, 18 Jan 2001 13:46:04 -0800 (PST) Received: by cronic.tellme.com (Postfix, from userid 501) id D9A9768A06; Thu, 18 Jan 2001 13:45:59 -0800 (PST) Message-Id: <20010118214559.D9A9768A06@cronic.tellme.com> Date: Thu, 18 Jan 2001 13:45:59 -0800 (PST) From: dannyman@toldme.com Reply-To: dannyman@toldme.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24439: suggested replament for adduser(8) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24439 >Category: bin >Synopsis: suggested replament for adduser(8) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 13:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: >Release: FreeBSD 4.1.1-RELEASE i386 >Organization: >Environment: >Description: Useradd is old, and does a decent job, but it pre-dates pw, which means it edits /etc/master.passwd and runs pwd_mkdb by hand. It is scarey to hack on for these reasons. It is also not maintained. In August, 1999 I submitted a script I had written to replace adduser, called enteruser, to Daemon News. An article talking about the rational for the script, how it works, and how it can be hacked on, can be found at http://www.daemonnews.org/199908/enteruser.html Occasionally I get e-mail from people asking about the "latest version" of Enteruser ... but it kinda like adduser, it does my bidding already, so what's this latest version stuff? Anyway, if you guys wanted to replace adduser, I would be happy to maintain it, by addressing bugs and feature requests. EnterUser is implicitly licensed under BSD terms anyway. You are more than welcome to it. >How-To-Repeat: >Fix: A copy of the article can be found at: http://dell.dannyland.org/~dannyman/stuff/enteruser/ The script itself: http://dell.dannyland.org/~dannyman/stuff/enteruser/enteruser >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 16:20:18 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5E59237B404 for ; Thu, 18 Jan 2001 16:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J0K1Z10937; Thu, 18 Jan 2001 16:20:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E4DF537B404 for ; Thu, 18 Jan 2001 16:19:13 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J0JDJ10859; Thu, 18 Jan 2001 16:19:13 -0800 (PST) (envelope-from nobody) Message-Id: <200101190019.f0J0JDJ10859@freefall.freebsd.org> Date: Thu, 18 Jan 2001 16:19:13 -0800 (PST) From: benway666@cs.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24441: cant shut down one icon says its not finished but can't get it to go away Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24441 >Category: misc >Synopsis: cant shut down one icon says its not finished but can't get it to go away >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: wish >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 16:20:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: jimrobinson >Release: >Organization: >Environment: >Description: >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 17:17:54 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7625B37B6A6; Thu, 18 Jan 2001 17:17:35 -0800 (PST) Received: (from billf@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J1HZf21246; Thu, 18 Jan 2001 17:17:35 -0800 (PST) (envelope-from billf) Date: Thu, 18 Jan 2001 17:17:35 -0800 (PST) From: Message-Id: <200101190117.f0J1HZf21246@freefall.freebsd.org> To: benway666@cs.com, billf@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/24441: cant shut down one icon says its not finished but can't get it to go away Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: cant shut down one icon says its not finished but can't get it to go away State-Changed-From-To: open->closed State-Changed-By: billf State-Changed-When: Thu Jan 18 17:16:47 PST 2001 State-Changed-Why: Whatever this user is talking about we may never know. I do however know that its not related to FreeBSD... http://www.freebsd.org/cgi/query-pr.cgi?pr=24441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 18:10:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5C93F37B69D for ; Thu, 18 Jan 2001 18:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J2A1134190; Thu, 18 Jan 2001 18:10:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 66A2C37B69B for ; Thu, 18 Jan 2001 18:09:20 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J29KO34102; Thu, 18 Jan 2001 18:09:20 -0800 (PST) (envelope-from nobody) Message-Id: <200101190209.f0J29KO34102@freefall.freebsd.org> Date: Thu, 18 Jan 2001 18:09:20 -0800 (PST) From: hunt@iprg.nokia.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: bin/24443: Fix for spurious "arith: syntax error: " problem in sh Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24443 >Category: bin >Synopsis: Fix for spurious "arith: syntax error: " problem in sh >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 18:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Peter Hunt >Release: 3.4-RELEASE >Organization: Nokia IP Inc. >Environment: FreeBSD rebempire.iprg.nokia.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Mon Mar 13 06:51:40 PST 2000 root@rebempire.iprg.nokia.com:/usr/src/sys/compile/IPRG i386 >Description: The symptom of the problem is a spurious arithmetic expression syntax error when executing a shell script line of the form: VARIABLE=$((1000 * 1024)) The error that appears is of the form: scriptname: arith: syntax error: "o" The problem is caused by an error in expari() in expand.c in sh. >How-To-Repeat: This problem is extremely hard to reproduce, as it depends on the specifics of previous arithmetic expressions in the shell script. I could reproduce it all the time with one very large script, which I can't submit, but wasn't able to do so with smaller scripts. >Fix: The existing code does the following: CHECKSTRSPACE(12 - 2, expdest); USTPUTC('\0', expdest); start = stackblock(); p = expdest; while (*p != CTLARI && p >= start) --p; The problem is that expdest points to the next unused location on the stack, so the character at that location is just garbage left over from a previous expression. p is set to that location, so the first iteration of the while loop will test that garbage character for CTLARI. If it happens to be CTLARI, the code will attempt to evaluate the characters above the top of the stack as an arithmetic expression, and (likely) fail. This is what was happening in the case I saw. The solution I propose is to change the while loop to a do loop: CHECKSTRSPACE(12 - 2, expdest); USTPUTC('\0', expdest); start = stackblock(); p = expdest; do { --p; } while (*p != CTLARI && p >= start); ... so that p gets decremented before the first test. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 19:40:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E628837B401 for ; Thu, 18 Jan 2001 19:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J3e1B44944; Thu, 18 Jan 2001 19:40:01 -0800 (PST) (envelope-from gnats) Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 827F037B69B; Thu, 18 Jan 2001 19:30:41 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 18 Jan 2001 19:28:39 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0J3UPa75677; Thu, 18 Jan 2001 19:30:25 -0800 (PST) (envelope-from cjc) Message-Id: <200101190330.f0J3UPa75677@rfx-216-196-73-168.users.reflexcom.com> Date: Thu, 18 Jan 2001 19:30:25 -0800 (PST) From: cjclark@reflexcom.com Reply-To: cjclark@alum.mit.edu To: FreeBSD-gnats-submit@freebsd.org Cc: current@freebsd.org X-Send-Pr-Version: 3.113 Subject: bin/24444: syslogd(8) does not update hostname Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24444 >Category: bin >Synopsis: syslogd(8) does not update hostname >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 19:40:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Crist J. Clark >Release: FreeBSD 5.0-CURRENT i386 >Organization: >Environment: All standard FreeBSD distributions. The code discussed is from 5.0-CURRENT, but should trivially merge back to -STABLE. >Description: Many tools and progams within FreeBSD date back to a time when it was expected that a machines IP and hostname seldom, if ever, changed. Even when a IP and hostname were received at boot, it rarely changed until shutdown. With many users using protocols like DHCP where IP and hostname change with time, many tools do not deal well with this behavior. One of these tools is syslogd(8). syslogd(8) is typically started at boot time and runs until shutdown. However, syslogd(8) loads the hostname at startup and syslogd(8)'s idea of the hostname can never change while it is running. One might expect that a SIGHUP would cause syslogd(8) to load the new hostname since a SIGHUP can cause syslogd(8) to re-read its configuration file and re-open the log files, but it does not. The fact that the hostname does not change can cause confusion in the log files. It could be especially troublesome when a machine is logging to a central loghost. At any given time, the names in the log files may not have any correspondence to the names the hosts currently have. There are even issues on a host that gets its IP and hostname via DHCP at boot and the name never changes. syslogd(8) is started before any network services are initialized in /etc/rc. I propose that syslogd(8) should reload the hostname with a SIGHUP. I cannot think of any reason that one should not update the hostname, but as I pointed out, there are reasons why one would want that behavior. >How-To-Repeat: # hostname -s bubbles # hostname bubbles-test.domain.org # kill -HUP `cat /var/run/syslog.pid` # logger -p user.notice "hostname test" # tail -4 /var/log/messages Jan 17 21:45:00 bubbles /boot/kernel/kernel: acd0: CDROM at ata0-slave using BIOSPIO Jan 17 21:45:00 bubbles /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s1a Jan 18 00:41:14 bubbles su: cjc to root on /dev/ttyp0 Jan 18 00:58:34 bubbles cjc: hostname test >Fix: I do not see any reason we cannot move the code that gets the hostname from the main() function into init(). init() is called when to "reload" settings. The hostname is never used in main() before init() is called. The patch is against -CURRENT and my box has not exploded yet. Here is what the above test looks like with the change in place. # hostname -s bubbles # hostname bubbles-test.cjclark.org # kill -HUP `cat /var/run/syslog.pid ` # logger -p user.notice "syslogd hostname test" # hostname bubbles.cjclark.org # kill -HUP `cat /var/run/syslog.pid ` # logger -p user.notice "syslogd hostname test" # tail -4 /var/log/messages Jan 18 13:36:58 bubbles su: BAD SU cjc to root on /dev/ttyp0 Jan 18 13:37:03 bubbles su: cjc to root on /dev/ttyp0 Jan 18 13:38:40 bubbles-test cjc: syslogd hostname test Jan 18 13:39:11 bubbles cjc: syslogd hostname test --- syslogd.c 2001/01/18 08:06:34 +++ syslogd.c 2001/01/18 08:09:23 @@ -395,12 +395,6 @@ consfile.f_type = F_CONSOLE; (void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1); - (void)gethostname(LocalHostName, sizeof(LocalHostName)); - if ((p = strchr(LocalHostName, '.')) != NULL) { - *p++ = '\0'; - LocalDomain = p; - } else - LocalDomain = ""; (void)strcpy(bootfile, getbootfile()); (void)signal(SIGTERM, die); (void)signal(SIGINT, Debug ? die : SIG_IGN); @@ -1342,6 +1336,16 @@ char host[MAXHOSTNAMELEN+1]; dprintf("init\n"); + + /* + * Load hostname (may have changed) + */ + (void)gethostname(LocalHostName, sizeof(LocalHostName)); + if ((p = strchr(LocalHostName, '.')) != NULL) { + *p++ = '\0'; + LocalDomain = p; + } else + LocalDomain = ""; /* * Close all open log files. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 19:40:27 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9512C37B400 for ; Thu, 18 Jan 2001 19:40:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J3e3q44953; Thu, 18 Jan 2001 19:40:03 -0800 (PST) (envelope-from gnats) Received: from mail.tucheng.generalresources.com (a1.tucheng.generalresources.com [211.21.4.234]) by hub.freebsd.org (Postfix) with ESMTP id B14B937B400 for ; Thu, 18 Jan 2001 19:36:34 -0800 (PST) Received: from w40.tucheng.generalresources.com (w40.tucheng.generalresources.com [192.168.1.40]) by mail.tucheng.generalresources.com (8.11.1/8.11.1) with ESMTP id f0J3aWh33472 for ; Fri, 19 Jan 2001 11:36:37 +0800 (CST) (envelope-from hsw@generalresources.com) Received: (from hsw@localhost) by w40.tucheng.generalresources.com (8.11.1/8.11.1) id f0J3aVe43887; Fri, 19 Jan 2001 11:36:31 +0800 (CST) (envelope-from hsw) Message-Id: <200101190336.f0J3aVe43887@w40.tucheng.generalresources.com> Date: Fri, 19 Jan 2001 11:36:31 +0800 (CST) From: Christopher Hall Reply-To: Christopher Hall To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: gnu/24445: ipnat does not parse its file properly Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24445 >Category: gnu >Synopsis: ipnat does not parse its file properly >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 19:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Christopher Hall >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan 18 13:15:08 CST 2001 >Description: Using the following configuration file: map fxp1 192.168.1.250/16 -> 1.2.3.4/32 portmap tcp/udp 40000:60000 map fxp1 192.168.1.250/16 -> 1.2.3.4/32 ##rdr fxp0 192.168.1.250/32 port 80 -> 4.5.6.7 port 80 rdr fxp0 192.168.1.250/32 port http -> 4.5.6.7 port http rdr fxp0 192.168.1.250/32 port https -> 4.5.6.7 port https Get errors like this 4: unknown service "http". 4: syntax error in "rdr" 5: unknown service "https". 5: syntax error in "rdr" can stop error by: a) remove the '##' in line 3 b) comment out line 1 c) move line 1 to end of file The problem is caused by a global variable in the file common.c its definition is: char *proto = NULL; the file natparse.c uses the routine "portnum" to convert the string "http" to a number 'proto' is now pointing at the position in the line buffer where the string "tcp/udp" used to be from line 1 of config file. Therefore the variable 'proto' points at the ".7" of the ip number when parsing line 4. Using numeric port number does not access the global 'proto' variable in portnum and later in natparse sets 'proto' pointing to static string "tcp" for parsing the remaining lines. Any line that contains a protocol will set the 'proto' variable for the next line. If this line is longer the 'proto' variable will be pointing at an invalid string. >How-To-Repeat: ipnat -f ipnat.conf (see above for for config file contents) >Fix: Don't use global variables like this! Should eliminate the global proto variable and pass the protocol as a parameter to portnum. It looks like proto variable is only shared by natparse.c parse.c and common.c. As far as I can tell only the 'rdr' command is affected, because the protocol specified on the end of the line so the 'proto' variable gets set too late. In natparse.c the is a section to decode the protocol, this would have to be move before the first portnum call. However the method of parsing the command line by using "cpp++;" to bump the toke pointer. The easiest would be to change the syntax of the "rdr" command from: rdr le0 203.1.2.3/32 port 80 -> 203.1.2.3,203.1.2.4 port 80 tcp to: rdr tcp le0 203.1.2.3/32 port 80 -> 203.1.2.3,203.1.2.4 port 80 Temporary Fix: Assume the protocol will be tcp or udp and that the same number applies to both. To do this, just add the following line to the start of the function natparse in natparse.c: proto = NULL; Any better ideas? >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 20: 0:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 00C2037B400 for ; Thu, 18 Jan 2001 20:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J402h47258; Thu, 18 Jan 2001 20:00:02 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 20:00:02 -0800 (PST) Message-Id: <200101190400.f0J402h47258@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Christopher Hall Subject: Re: gnu/24445: ipnat does not parse its file properly Reply-To: Christopher Hall Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR gnu/24445; it has been noted by GNATS. From: Christopher Hall To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: Subject: Re: gnu/24445: ipnat does not parse its file properly Date: Fri, 19 Jan 2001 11:54:00 +0800 setting 'proto' to NULL did not work completely as there some protocols e.g pop3s that have no corresponding udp number Since I am only redirecting tcp add: proto = "tcp"; to start of natparse instead. In message <200101190336.f0J3aVe43887@w40.tucheng.generalresources.com>, Christopher Hall writes: > >>Number: 24445 >>Category: gnu >>Synopsis: ipnat does not parse its file properly >>Confidential: no >>Severity: serious >>Priority: high >>Responsible: freebsd-bugs >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Thu Jan 18 19:40:01 PST 2001 >>Closed-Date: >>Last-Modified: >>Originator: Christopher Hall >>Release: FreeBSD 4.2-STABLE i386 >>Organization: >>Environment: > > 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan 18 13:15:08 CST 2001 > >>Description: > > Using the following configuration file: > > map fxp1 192.168.1.250/16 -> 1.2.3.4/32 portmap tcp/udp 40000:60000 > map fxp1 192.168.1.250/16 -> 1.2.3.4/32 > ##rdr fxp0 192.168.1.250/32 port 80 -> 4.5.6.7 port 80 > rdr fxp0 192.168.1.250/32 port http -> 4.5.6.7 port http > rdr fxp0 192.168.1.250/32 port https -> 4.5.6.7 port https > > >Get errors like this > > 4: unknown service "http". > 4: syntax error in "rdr" > 5: unknown service "https". > 5: syntax error in "rdr" > > can stop error by: > a) remove the '##' in line 3 > b) comment out line 1 > c) move line 1 to end of file > > >The problem is caused by a global variable in the file common.c >its definition is: char *proto = NULL; > >the file natparse.c uses the routine "portnum" to convert the >string "http" to a number > >'proto' is now pointing at the position in the line buffer where >the string "tcp/udp" used to be from line 1 of config file. > >Therefore the variable 'proto' points at the ".7" of the ip number when >parsing line 4. > >Using numeric port number does not access the global 'proto' variable in >portnum and later in natparse sets 'proto' pointing to static string "tcp" >for parsing the remaining lines. > >Any line that contains a protocol will set the 'proto' variable for >the next line. If this line is longer the 'proto' variable will be >pointing at an invalid string. > > >>How-To-Repeat: > > ipnat -f ipnat.conf (see above for for config file contents) > >>Fix: > > Don't use global variables like this! > > Should eliminate the global proto variable and pass the protocol > as a parameter to portnum. It looks like proto variable > is only shared by natparse.c parse.c and common.c. > > As far as I can tell only the 'rdr' command is affected, because > the protocol specified on the end of the line so the 'proto' variable > gets set too late. > > In natparse.c the is a section to decode the protocol, this would > have to be move before the first portnum call. However the method > of parsing the command line by using "cpp++;" to bump the toke pointer. > The easiest would be to change the syntax of the "rdr" command > from: > rdr le0 203.1.2.3/32 port 80 -> 203.1.2.3,203.1.2.4 port 80 tcp > to: > rdr tcp le0 203.1.2.3/32 port 80 -> 203.1.2.3,203.1.2.4 port 80 > > > Temporary Fix: > > Assume the protocol will be tcp or udp and that the same number > applies to both. > > To do this, just add the following line to the start of the > function natparse in natparse.c: > > proto = NULL; > > > Any better ideas? > >>Release-Note: >>Audit-Trail: >>Unformatted: > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-bugs" in the body of the message > --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 21:20:31 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D6CE237B69C for ; Thu, 18 Jan 2001 21:20:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J5K3F58675; Thu, 18 Jan 2001 21:20:03 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 712D337B400 for ; Thu, 18 Jan 2001 21:14:56 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J5Eu858194; Thu, 18 Jan 2001 21:14:56 -0800 (PST) (envelope-from nobody) Message-Id: <200101190514.f0J5Eu858194@freefall.freebsd.org> Date: Thu, 18 Jan 2001 21:14:56 -0800 (PST) From: oleg_s@ok.ru To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: i386/24449: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) no Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24449 >Category: i386 >Synopsis: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 21:20:03 PST 2001 >Closed-Date: >Last-Modified: >Originator: Oleg >Release: 4.1 >Organization: none >Environment: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî ïûòàþñü êîäèðîâàòü: /dev/dsp Ñïàñèáî >Description: >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî ïûòàþñü êîäèðîâàòü: /dev/dsp0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 21:20:41 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B05FB37B401 for ; Thu, 18 Jan 2001 21:20:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J5K3258666; Thu, 18 Jan 2001 21:20:03 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 27DBE37B400 for ; Thu, 18 Jan 2001 21:14:53 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J5Ert58188; Thu, 18 Jan 2001 21:14:53 -0800 (PST) (envelope-from nobody) Message-Id: <200101190514.f0J5Ert58188@freefall.freebsd.org> Date: Thu, 18 Jan 2001 21:14:53 -0800 (PST) From: oleg_s@ok.ru To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: i386/24448: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) no Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24448 >Category: i386 >Synopsis: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 18 21:20:03 PST 2001 >Closed-Date: >Last-Modified: >Originator: Oleg >Release: 4.1 >Organization: none >Environment: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî ïûòàþñü êîäèðîâàòü: /dev/dsp Ñïàñèáî >Description: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî ïûòàþñü êîäèðîâàòü: /dev/dsp Ñïàñèáî >How-To-Repeat: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî ïûòàþñü êîäèðîâàòü: /dev/dsp Ñïàñèáî >Fix: Èìååòñÿ ïðîãðàììà (RealProducer) ïîä Linux, çàïóñêàþ åå ïîä FreeBSD, îíà ðàáîòàåò êàê êîäåð ôàéëîâ áåç ïðîáëåì, íî êàê òîëüêî çàñòàâëÿþ åå êîäèðîâàòü ñ óñòðîéñòâà, òî íè÷åãî íå âûõîäèò, âîò ÷òî ïîëó÷àþ: linux: 'ioctl' fd=4, cmd=4dff ('M',255) not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî %E >Release-Note: >Audit-Trail: >Unformatted: not implemented... encoding failed, A GENERAL ERROR OCCURRED! ×òî ýòî çíà÷èò? è êàê ìîæíî èñïðàâèòü åëè ìîæíî? Óñòðîéñòâî ñ êîòîðîãî ïûòàþñü êîäèðîâàòü: /dev/dsp0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 22:10:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BBFCF37B698 for ; Thu, 18 Jan 2001 22:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J6A2n66340; Thu, 18 Jan 2001 22:10:02 -0800 (PST) (envelope-from gnats) Date: Thu, 18 Jan 2001 22:10:02 -0800 (PST) Message-Id: <200101190610.f0J6A2n66340@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Vallo Kallaste Subject: Re: bin/24435: Unable to create root partition. Too big? Reply-To: Vallo Kallaste Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24435; it has been noted by GNATS. From: Vallo Kallaste To: rwatson@FreeBSD.ORG Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/24435: Unable to create root partition. Too big? Date: Fri, 19 Jan 2001 08:04:59 +0200 On Thu, Jan 18, 2001 at 12:09:31PM -0500, rwatson@FreeBSD.ORG wrote: > > >Number: 24435 > >Category: bin > >Synopsis: Changing slice type causes Auto-partition to not work > > A co-worker of mine was installing FreeBSD 4.2-RELEASE on a machine > that previously held two FAT partitions. Rather than delete and > recreate the first partition to change it to a FreeBSD partition, > he changed the partition "type" using T. The slice editor then showed > "the right thing". However, when he then got to partition allocation, > hitting A resulted in the following message: > > Unable to create the root partition. Too big? > > Going back and deleting the FreeBSD slice (was a FAT slice), then creating > it again caused auto-partitioning to work fine. It sounds like the > change in slice type is not being propagated properly to the partitioning > phase. Also, it sounds like the debugging output from the partition > creation is a tad on the not-so-specific-side. I've encountered this bug also. 4.2-stable as I remember. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 18 23:24:43 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from kumi.webnewslink.com (unknown [64.132.3.187]) by hub.freebsd.org (Postfix) with ESMTP id 4336D37B401; Thu, 18 Jan 2001 23:24:16 -0800 (PST) Received: from pc ([64.132.3.188]) by kumi.webnewslink.com (8.9.3/8.9.3) with SMTP id VAA18949; Thu, 18 Jan 2001 21:10:02 -1000 Date: Thu, 18 Jan 2001 21:10:02 -1000 From: ami@e-hiddencam.com Message-Id: <200101190710.VAA18949@kumi.webnewslink.com> To: ami@e-hiddencam.com Subject: NEWS MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ‰Ä”ü‚Å‚·B —F’B‚ƈꏏ‚ɃAƒ_ƒ‹ƒgƒTƒCƒg‚ðì‚è‚Ü‚µ‚œB Ž„‚ào‰‰‚µ‚Ä‚¢‚Ü‚·B ‚³‚­‚ç‚ÆŒŸ‚€–Œ‘O‚ŏo‚Ä‚¢‚Ü‚·B ’T‚µ‚Ă݂āAŠŽ‘z‚Å‚à•·‚©‚¹‚ĉº‚³‚¢B ‰Ä”ü http://63.100.42.104/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ If you are under 18 years of age or if it is illegal to view adult material in your community, please erase this message. _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ ********************************************************** ‚±‚̃[ƒŠƒ“ƒOƒŠƒXƒg‚©‚çA‚ ‚È‚œ‚Ì‚š–Œ‘O‚ðíœ‚µ‚œ‚¢ê‡‚́A Œ–Œ‚ð"remove" ‚Æ‚µA‚±‚̃[ƒ‹‚É‚»‚̂܂ܕԐM‚µ‚Ä‚­‚Ÿ‚³ ‚¢B‚æ‚낵‚­‚šŠè‚¢‚µ‚Ü‚·B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 1: 0:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F3C937B69C for ; Fri, 19 Jan 2001 01:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J901H89389; Fri, 19 Jan 2001 01:00:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BF47A37B699 for ; Fri, 19 Jan 2001 00:57:55 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J8vt989056; Fri, 19 Jan 2001 00:57:55 -0800 (PST) (envelope-from nobody) Message-Id: <200101190857.f0J8vt989056@freefall.freebsd.org> Date: Fri, 19 Jan 2001 00:57:55 -0800 (PST) From: bryn@nwlink.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/24452: random panics with Fatal trap 19 and OpenSSH Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24452 >Category: misc >Synopsis: random panics with Fatal trap 19 and OpenSSH >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 19 01:00:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Bryn Moslow >Release: FreeBSD i386 4.2-STABLE >Organization: Northwest Link >Environment: FreeBSD authoritah.nwlink.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Jan 16 01:22:02 PST 2001 root@authoritah.nwlink.com:/usr/src/sys/compile/AUTHORITAH i386 >Description: Cron job uses scp to copy files to other machines, crashes randomly at least once a day while doing scp: Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer = 0x8:0xc03060f5 stack pointer = 0x10:0xd0d9fdc8 frame pointer = 0x10:0xd0d9ff2c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 37245 (ssh) interrupt mask = none trap number = 19 panic: non-maskable interrupt trap syncing disks... 28 28 23 2 done Uptime: 1d12h51m28s amr0: flushing cache...done Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... >How-To-Repeat: Set up a cron job to use the system-included scp to copy a file regularly to another machine and let run, seems to happen every 30-40 hours. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 1:30:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 370FD37B698 for ; Fri, 19 Jan 2001 01:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J9U2L95409; Fri, 19 Jan 2001 01:30:02 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 01:30:02 -0800 (PST) Message-Id: <200101190930.f0J9U2L95409@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kris Kennaway Subject: Re: misc/24452: random panics with Fatal trap 19 and OpenSSH Reply-To: Kris Kennaway Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24452; it has been noted by GNATS. From: Kris Kennaway To: bryn@nwlink.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/24452: random panics with Fatal trap 19 and OpenSSH Date: Fri, 19 Jan 2001 01:24:26 -0800 --f2QGlHpHGjS2mn6Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 19, 2001 at 12:57:55AM -0800, bryn@nwlink.com wrote: > Cron job uses scp to copy files to other machines, crashes randomly at le= ast once a day while doing scp: Sounds like hardware problems, possibly caused by the CPU or hardware load when you do things like scp: > Fatal trap 19: non-maskable interrupt trap while in kernel mode Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --f2QGlHpHGjS2mn6Y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6aAfJWry0BWjoQKURAmkwAJ9oZ50EtAb/VYwxEXBiC1P8wHLHJACeIKlA g3MTVZyRWHsQDIVXPCaPc6o= =kUCh -----END PGP SIGNATURE----- --f2QGlHpHGjS2mn6Y-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 1:50:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A42A637B6A0 for ; Fri, 19 Jan 2001 01:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0J9o2b97350; Fri, 19 Jan 2001 01:50:02 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 01:50:02 -0800 (PST) Message-Id: <200101190950.f0J9o2b97350@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Bryn Wm. Moslow" Subject: Re: misc/24452: random panics with Fatal trap 19 and OpenSSH Reply-To: "Bryn Wm. Moslow" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24452; it has been noted by GNATS. From: "Bryn Wm. Moslow" To: Kris Kennaway Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/24452: random panics with Fatal trap 19 and OpenSSH Date: Fri, 19 Jan 2001 01:41:36 -0800 (PST) This box was running nonstop since October and this only started happening after my last two -STABLE syncs. Pushing the hardware hasn't caused any other problems, buildworlds go great. I just haven't seen any evidence of other hardware issues, the load was 0.01 during the last panic and iostat showed only a few K of disk activity. I know better than to rule out a hardware issue but the panics literally started the day after my second last cvsup and buildworld (last week) after months of solid operation. I'll certainly take your suggestion to heart as I've seen certainly more bizarre coincidences. I wonder if you might take a look at my dmesg and see if you see any sore thumbs? Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Tue Jan 16 01:22:02 PST 2001 root@authoritah.nwlink.com:/usr/src/sys/compile/AUTHORITAH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (746.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x387fbff real memory = 268369920 (262080K bytes) config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di ata1 config> di ata0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 256598016 (250584K bytes) Preloaded elf kernel "kernel" at 0xc043e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043e09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pcib3: at device 15.0 on pci1 pci2: on pcib3 ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: port 0x2800-0x283f mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0 fxp0: Ethernet address 00:d0:b7:89:7a:0f pcib4: at device 16.0 on pci0 pci3: on pcib4 amr0: mem 0xf4400000-0xf47fffff irq 5 at device 16.1 on pci0 amr0: Firmware GH6E, BIOS 1.48, 16MB RAM isab0: at device 18.0 on pci0 isa0: on isab0 atapci0: port 0x2860-0x286f at device 18.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x2840-0x285f irq 10 at device 18.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 0x1040-0x104f at device 18.3 on pci0 pci0: at 20.0 pcib1: on motherboard pci4: on pcib1 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,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 Waiting 5 seconds for SCSI devices to settle amrd0: on amr0 amrd0: 17460MB (35758080 sectors) RAID 1 (optimal) no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/amrd0s1a On Fri, 19 Jan 2001, Kris Kennaway wrote: |On Fri, Jan 19, 2001 at 12:57:55AM -0800, bryn@nwlink.com wrote: | |> Cron job uses scp to copy files to other machines, crashes randomly at least once a day while doing scp: | |Sounds like hardware problems, possibly caused by the CPU or hardware |load when you do things like scp: | |> Fatal trap 19: non-maskable interrupt trap while in kernel mode | |Kris | |-- |NOTE: To fetch an updated copy of my GPG key which has not expired, |finger kris@FreeBSD.org | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 2:10:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7241937B6A4 for ; Fri, 19 Jan 2001 02:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JAA2k01659; Fri, 19 Jan 2001 02:10:02 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 02:10:02 -0800 (PST) Message-Id: <200101191010.f0JAA2k01659@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kris Kennaway Subject: Re: misc/24452: random panics with Fatal trap 19 and OpenSSH Reply-To: Kris Kennaway Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24452; it has been noted by GNATS. From: Kris Kennaway To: "Bryn Wm. Moslow" Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/24452: random panics with Fatal trap 19 and OpenSSH Date: Fri, 19 Jan 2001 02:10:59 -0800 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 19, 2001 at 01:41:36AM -0800, Bryn Wm. Moslow wrote: > This box was running nonstop since October and this only started > happening after my last two -STABLE syncs. Pushing the hardware hasn't > caused any other problems, buildworlds go great. I just haven't seen any > evidence of other hardware issues, the load was 0.01 during the last panic > and iostat showed only a few K of disk activity. I know better than to > rule out a hardware issue but the panics literally started the day after > my second last cvsup and buildworld (last week) after months of solid > operation. I'll certainly take your suggestion to heart as I've seen > certainly more bizarre coincidences. I wonder if you might take a look at > my dmesg and see if you see any sore thumbs? You should be able to test this by reverting back to a previously-working stable snapshot and see if the problems persist. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6aBKzWry0BWjoQKURAiaZAKD1Cl00wfcVByzXDP/oN1UQdExYCwCg9k86 mspaF+UIPy/uLoTAcz5r7Yc= =74HG -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 3:40:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5D43737B401 for ; Fri, 19 Jan 2001 03:40:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JBe6T10870; Fri, 19 Jan 2001 03:40:06 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 03:40:06 -0800 (PST) Message-Id: <200101191140.f0JBe6T10870@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Dag-Erling Smorgrav Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: Dag-Erling Smorgrav Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: Dag-Erling Smorgrav To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: 19 Jan 2001 12:32:53 +0100 cjclark@reflexcom.com writes: > I propose that syslogd(8) should reload the hostname with a > SIGHUP. I cannot think of any reason that one should not update the > hostname, but as I pointed out, there are reasons why one would want > that behavior. It should also log a message if the hostname changes. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 6:10:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 27E5B37B402 for ; Fri, 19 Jan 2001 06:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JEA2Y32778; Fri, 19 Jan 2001 06:10:02 -0800 (PST) (envelope-from gnats) Received: from jimex.jinr.ru (jimex.jinr.ru [159.93.17.7]) by hub.freebsd.org (Postfix) with ESMTP id D814137B404 for ; Fri, 19 Jan 2001 06:08:40 -0800 (PST) Received: from moonhe.jinr.ru (root@moonhe.jinr.ru [159.93.18.27]) by jimex.jinr.ru (8.11.1/8.11.1) with ESMTP id f0JE8UI07528 for ; Fri, 19 Jan 2001 17:08:30 +0300 (MSK) Received: (from isupov@localhost) by moonhe.jinr.ru (8.11.0/8.11.0) id f0JEEI389616; Fri, 19 Jan 2001 17:14:18 +0300 (MSK) (envelope-from isupov) Message-Id: <200101191414.f0JEEI389616@moonhe.jinr.ru> Date: Fri, 19 Jan 2001 17:14:18 +0300 (MSK) From: isupov@moonhe.jinr.ru Reply-To: isupov@moonhe.jinr.ru To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24458: named-xfer executed at 20 priority level instead of wanted 0 level Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24458 >Category: bin >Synopsis: named-xfer executed at 20 priority level instead of wanted 0 level >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 19 06:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Isupov A.Yu. >Release: FreeBSD 4.1.1-RELEASE i386 >Organization: LHE, JINR >Environment: FreeBSD 4.1.1-RELEASE i386 >Description: /usr/libexec/named-xfer, executed by /usr/sbin/named, re'nice(3)'ing itself to 20 priority level instead of wanted 0 (default) level. This occurs because respective (to strange :-) code from /usr/src/contrib/bind/bin/named-xfer/named-xfer.c, lines 351-355 : #ifdef RENICE nice(-40); nice(20); nice(0); #endif works correctly (= sets 0 priority, see comments near) only for process owned by super-user. But named (and named-xfer) now owned by bind:bind >How-To-Repeat: Run code mentioned above not under super-user. >Fix: I think, we need to do nothing with priority in the named-xfer.c and inherit priority level from named process. This behaviour can be achieved by #undef'ing RENICE in the /usr/src/contrib/bind/bin/named/named.h >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 8:40:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7B83B37B698 for ; Fri, 19 Jan 2001 08:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JGe1V36109; Fri, 19 Jan 2001 08:40:01 -0800 (PST) (envelope-from gnats) Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 115DA37B401 for ; Fri, 19 Jan 2001 08:33:39 -0800 (PST) Received: from pain10.corp.disney.com (root@pain10.corp.disney.com [153.7.110.100]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id f0JGXDp29544 for ; Fri, 19 Jan 2001 08:33:13 -0800 (PST) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP for FreeBSD-gnats-submit@freebsd.org; Fri, 19 Jan 2001 08:34:12 -0800 Received: from plio.fan.fa.disney.com (plio.fan.fa.disney.com [153.7.118.2]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id IAA11017 for ; Fri, 19 Jan 2001 08:33:35 -0800 (PST) (envelope-from Jim.Pirzyk@fa.disney.com) Received: from snoopy.fan.fa.disney.com (snoopy.fan.fa.disney.com [153.7.117.170]) by plio.fan.fa.disney.com (8.9.2/8.9.2) with ESMTP id IAA20932 for ; Fri, 19 Jan 2001 08:33:34 -0800 (PST) (envelope-from Jim.Pirzyk@fa.disney.com) Received: (from Jim.Pirzyk@localhost) by snoopy.fan.fa.disney.com (8.11.1/8.9.3) id f0JGXYc30557; Fri, 19 Jan 2001 08:33:34 -0800 (PST) (envelope-from Jim.Pirzyk@fa.disney.com) Message-Id: <200101191633.f0JGXYc30557@snoopy.fan.fa.disney.com> Date: Fri, 19 Jan 2001 08:33:34 -0800 (PST) From: Jim.Pirzyk@disney.com Reply-To: Jim.Pirzyk@disney.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24461: YP library timeout Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24461 >Category: bin >Synopsis: Being able to increase the YP timeout without rebuilding libc.so >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jan 19 08:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Jim Pirzyk >Release: FreeBSD 4.2-RELEASE i386 >Organization: >Environment: We have a mixed enviroment with our YP servers being Solaris 2.x systems. We are using our FreeBSD boxes as YP client machines. >Description: We have edited the /usr/src/lib/yp/yplib.c file to increase the timeout from 10 to 30 seconds. It would be nice if we could do it at run time with either a config file change or a sysctl call. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 11: 0:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E11D437B400 for ; Fri, 19 Jan 2001 11:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JJ02X52896; Fri, 19 Jan 2001 11:00:02 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 11:00:02 -0800 (PST) Message-Id: <200101191900.f0JJ02X52896@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ronald F. Guilmette" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Ronald F. Guilmette" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Ronald F. Guilmette" To: "Justin T. Gibbs" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Fri, 19 Jan 2001 10:59:21 -0800 Just one further follow-up on this problem... After having replaced ALL the memory on the system, I coutinued to see the X server die at seemlingly random times. In short, it was clear that I still had a problem. Now however I had some reason to suspect that my video card might be playing a role in this. Then I remembered what I had in there... It was a relatively ancient PCI video card... an S3-based Number Nine Motion 771, circa 1995. I swapped that out and dropped in a low-end ATI AGP card that I had on another system *and* I put back all of the original SDRAM DIMMS and then I re-ran my test that was consistantly failing before (i.e. the small pro- gram that just zwrite a big stream of zeros to a second SCSI disk). That worked flawlessly now. I ran two full tests, writing all the way to the end of the disk (4GB) with no problems. That's enough to convince me that the original problem I reported must have been due to some bad interaction between the Advansys PCI SCSI controller and this particular old PCI video card. It seems that these two just don't play well together. Serves me right for trying to use antiquated components. Humph. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 11:10:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3223E37B699 for ; Fri, 19 Jan 2001 11:10:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JJA7v55867; Fri, 19 Jan 2001 11:10:07 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 11:10:07 -0800 (PST) Message-Id: <200101191910.f0JJA7v55867@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Crist J. Clark" Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: "Crist J. Clark" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: "Crist J. Clark" To: Dag-Erling Smorgrav Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: Fri, 19 Jan 2001 11:03:41 -0800 On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > cjclark@reflexcom.com writes: > > I propose that syslogd(8) should reload the hostname with a > > SIGHUP. I cannot think of any reason that one should not update the > > hostname, but as I pointed out, there are reasons why one would want > > that behavior. > > It should also log a message if the hostname changes. Should that be a responsibility of syslogd(8) or hostname(1)? Personally, it might be a slippery slope to start adding things that syslogd(8) should maintain state on, but since syslogd(8) actually uses the hostname... One also could start arguing that syslogd(8) should check the hostname everytime it logs something despite the performance hit. As for what syslogd(8) does now, if you look at the example output in the PR, notice syslogd(8) didn't even log when it was HUP'ed. IMHO, I think it is beyond the scope of syslogd(8) to actually track changes in the hostname in real-time. Noticing a change when given a HUP signal, would seem reasonable, but if hostname(1) were to log changes, that would also be fairly redundant. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 13:10:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 888D737B699 for ; Fri, 19 Jan 2001 13:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JLA3w70161; Fri, 19 Jan 2001 13:10:03 -0800 (PST) (envelope-from gnats) Received: from skalman.campus.luth.se (skalman.campus.luth.se [130.240.197.52]) by hub.freebsd.org (Postfix) with ESMTP id 3166D37B400 for ; Fri, 19 Jan 2001 13:04:08 -0800 (PST) Received: (from pantzer@localhost) by skalman.campus.luth.se (8.11.1/8.11.0) id f0JL46504697; Fri, 19 Jan 2001 22:04:06 +0100 (CET) (envelope-from pantzer) Message-Id: <200101192104.f0JL46504697@skalman.campus.luth.se> Date: Fri, 19 Jan 2001 22:04:06 +0100 (CET) From: pantzer@ludd.luth.se Reply-To: pantzer@ludd.luth.se To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/24465: Will process packets not for this host if using netgraph and ip forwarding. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24465 >Category: kern >Synopsis: Will process packets not for this host if using netgraph and ip forwarding. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 19 13:10:02 PST 2001 >Closed-Date: >Last-Modified: >Originator: Mattias Pantzare >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: FreeBSD running vmware in bridged mode using netgraph and IP forwarding on. >Description: FreeBSD will respond to ethernet packets for other computers if IP forwarding is on and netgraph is used for bridging. It will send packets with a mac adress that is diffrent from the interfaces adress to the IP layer. If IP forwaring is on then the IP layer will try to route the packets even if they where sent to a diffrent computer. >How-To-Repeat: >Fix: There is a check for the mac adress in ether_input in net/if_ethersubr.c: /* Discard packet if upper layers shouldn't see it. This should only happen when the interface is in promiscuous mode. */ if ((ifp->if_flags & IFF_PROMISC) != 0 && (eh->ether_dhost[0] & 1) == 0 && bcmp(eh->ether_dhost, IFP2AC(ifp)->ac_enaddr, ETHER_ADDR_LEN) != 0) { m_freem(m); return; } That check will not be done if netgraph is used on the interface, from what I can find it shoud be added to ng_ether_rcv_upper in netgraph/ng_ether.c >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 14:30:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D634E37B698 for ; Fri, 19 Jan 2001 14:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JMU4q82680; Fri, 19 Jan 2001 14:30:04 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 14:30:04 -0800 (PST) Message-Id: <200101192230.f0JMU4q82680@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kris Kennaway Subject: Re: bin/24458: named-xfer executed at 20 priority level instead of wanted 0 level Reply-To: Kris Kennaway Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24458; it has been noted by GNATS. From: Kris Kennaway To: isupov@moonhe.jinr.ru Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/24458: named-xfer executed at 20 priority level instead of wanted 0 level Date: Fri, 19 Jan 2001 14:30:33 -0800 --5xSkJheCpeK0RUEJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline IMO, this bug report should be taken up with the BIND developers. It affects other platforms similarly when run as a non-privileged user. Kris --5xSkJheCpeK0RUEJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6aMAJWry0BWjoQKURAsvWAJ43t2t4F5qC4D4sV5npkojXfJx2VACgiiwE CBgj6FrI3RoXglNXkjKcjqs= =3cZe -----END PGP SIGNATURE----- --5xSkJheCpeK0RUEJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 14:50:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7158737B404 for ; Fri, 19 Jan 2001 14:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JMo2q84558; Fri, 19 Jan 2001 14:50:02 -0800 (PST) (envelope-from gnats) Date: Fri, 19 Jan 2001 14:50:02 -0800 (PST) Message-Id: <200101192250.f0JMo2q84558@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Dag-Erling Smorgrav Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: Dag-Erling Smorgrav Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: Dag-Erling Smorgrav To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: 19 Jan 2001 23:09:24 +0100 "Crist J. Clark" writes: > On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > > It should also log a message if the hostname changes. > Should that be a responsibility of syslogd(8) or hostname(1)? I meant syslogd(8), but putting it in hostname(1) might makes sense, except that hostname(1) is not the only way to set the hostname ('sysctl -w kern.hostname=foo' is another) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 15:40:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E0C0437B698 for ; Fri, 19 Jan 2001 15:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0JNe1D90896; Fri, 19 Jan 2001 15:40:01 -0800 (PST) (envelope-from gnats) Received: from postal.incyte.com (postal.incyte.com [198.31.37.2]) by hub.freebsd.org (Postfix) with ESMTP id 62CD137B400 for ; Fri, 19 Jan 2001 15:36:28 -0800 (PST) Received: from blah.incyte.com (blah.incyte.com [10.99.1.40]) by postal.incyte.com (8.11.1/8.11.1) with ESMTP id f0JNaNf02061; Fri, 19 Jan 2001 15:36:23 -0800 (PST) Received: from blah.incyte.com (bl@localhost) by blah.incyte.com (8.9.1a/8.9.1) with ESMTP id PAA158459; Fri, 19 Jan 2001 15:36:27 -0800 (PST) Message-Id: <200101192336.PAA158459@blah.incyte.com> Date: Fri, 19 Jan 2001 15:36:27 -0800 From: "Brett G. Lemoine" Reply-To: bl@incyte.com To: FreeBSD-gnats-submit@freebsd.org Cc: bl@incyte.com X-Send-Pr-Version: 3.2 Subject: i386/24469: system hangs on scsi disk access error Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24469 >Category: i386 >Synopsis: system hangs on scsi disk access error >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 19 15:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Brett G Lemoine >Release: FreeBSD 4.2-RELEASE i386 >Organization: Incyte Genomics, Inc >Environment: TYAN Thunderbolt S1837 motherboard w/ onboard Adaptec AIC-7896 dual channel Ultra2 LVD SCSI FreeBSD 4.2-RELEASE #1: Fri Jan 12 19:52:23 CST 2001 root@blur.unixshaman.com:/usr/src/sys/compile/SHAMAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (751.71-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383fbff real memory = 1073741824 (1048576K bytes) config> di aha0 config> q avail memory = 1042231296 (1017804K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 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 0xc0392000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039209c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pcib3: at device 1.0 on pci1 pci2: on pcib3 pci2: at 1.0 pci2: at 2.0 pci2: at 3.0 pci2: at 4.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x440-0x44f at device 7.3 on pci0 ahc0: port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 11.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 16 at device 11.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: port 0xef00-0xef3f irq 18 at device 12.0 on pci0 fxp0: port 0xee80-0xeebf mem 0xfea00000-0xfeafffff,0xfebfd000-0xfebfdfff irq 19 at device 13.0 on pci0 fxp0: Ethernet address 00:e0:81:10:c9:0e fxp1: port 0xed80-0xedbf mem 0xfe800000-0xfe8fffff,0xfebfc000-0xfebfcfff irq 17 at device 17.0 on pci0 fxp1: Ethernet address 00:d0:b7:73:39:03 pcib1: on motherboard pci3: on pcib1 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,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! acd0: CDROM at ata1-master using PIO4 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-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) WARNING: / was not properly dismounted cd0 at ahc1 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da2 at ahc1 bus 0 target 6 lun 0 da2: Removable Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15) da2: Attempt to query device size failed: NOT READY, Medium not present pid 217 (Xaccel): trap 12 with interrupts disabled pid 217 (Xaccel): trap 7 with interrupts disabled cd9660: RockRidge Extension >Description: Sporadically (5 times in the last two weeks, including 3 times on one day), I get the below errors on one of my two disks. (da1:ahc0:0:1:0): SCB 0x1d - timed out while idle, SEQADDR == 0x5 STACK == 0x13, 0x174, 0x15e, 0x174 SXFRCTL0 == 0x80 SCB count = 110 QINFIFO entries: 34 18 46 1 19 31 52 20 33 9 3 67 57 45 0 30 54 22 50 40 23 8 36 2 32 44 35 5 17 11 28 10 101 15 51 26 6 Waiting Queue entries: 11:66 Disconnected Queue entries: 17:39 27:29 QOUTFIFO entries: Sequencer Free SCB List: 20 2 0 28 14 10 29 31 15 24 7 19 6 23 18 21 12 26 13 22 4 30 9 3 16 8 25 1 5 Pending list: 6 26 51 15 101 10 28 11 17 5 35 44 32 2 36 8 23 40 50 22 54 30 0 45 57 67 3 9 33 20 52 31 19 1 46 18 34 66 39 29 Kernel Free SCB list: 24 58 25 47 59 55 27 42 4 49 3 8 37 43 21 41 53 48 16 12 69 56 68 13 83 14 82 81 80 99 98 97 96 95 94 93 92 91 90 109 108 107 106 105 104 103 102 65 84 85 86 87 88 89 70 71 72 73 74 75 76 77 78 79 60 61 62 63 64 100 sg[0] - Addr 0x1a608800 : Length 1024 (da1:ahc0:0:1:0): SCB 29: Immediate reset. Flags = 0x4040 (da1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 40 SCBs aborted After looking for similar problems in the GNATs database, I saw suggestions to disable tagged queueing, which I then did on both disks (using camcontrol). I then didn't see the problem for a while, so I thought that it had been taken care of, but today, I get the following: (da0:ahc0:0:0:0): SCB 0x8 - timed out while idle, SEQADDR == 0x3e STACK == 0x1, 0x1, 0x1, 0x1 SXFRCTL0 == 0x80 SCB count = 20 QINFIFO entries: 8 14 Waiting Queue entries: Disconnected Queue entrties: QOUTFIFO entries: Sequencer Free SCB List: 1 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Pending list: 14 8 Kernel Free SCB list: 15 16 17 18 18 0 1 2 3 4 5 6 7 13 12 11 10 Untagged Q(0): 8 Untagged Q(1): 14 sg[0] - Addr 0x3c381000 : Length 4096 sg[1] - Addr 0x35ce2000 : Length 2048 (da0:ahc0:0:0:0): SCB 8: Immediate reset. Flags = 0x6040 (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (da0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0x3e STACK == 0x1, 0x1, 0x1, 0x1 SXFRCTL0 == 0x80 SCB count = 20 QINFIFO entries: 9 14 Waiting Queue entries: Disconnected Queue entrties: QOUTFIFO entries: Sequencer Free SCB List: 1 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Pending list: 14 9 Kernel Free SCB list: 15 16 17 18 18 0 1 2 3 4 5 6 7 13 12 11 10 Untagged Q(0): 9 Untagged Q(1): 14 sg[0] - Addr 0x3c381000 : Length 4096 sg[1] - Addr 0x35ce2000 : Length 2048 (da0:ahc0:0:0:0): SCB 8: Immediate reset. Flags = 0x6040 (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted I'm somewhat new to PC-type hardware, so this may be nothing, but are the two channels on the ahc's _supposed_ to have the same IRQ? I couldn't find a way to alter either ahc's IRQ from either the system or scsi bios, so I'm assuming they're setup correctly. Given that there was no activity on the other bus (nothing in either the cd-writer or zip drive) at the time of the problems, I don't believe it's likely to be simply an IRQ issue. >How-To-Repeat: The problems seem to occur most frequenly when there's heavy disk activity, but I can't seem to reproduce it on demand. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 16:26:17 2001 Delivered-To: freebsd-bugs@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 E57BB37B402 for ; Fri, 19 Jan 2001 16:25:53 -0800 (PST) Received: from backup.af.speednet.com.au (backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.1/8.11.1) with ESMTP id f0K0PQm25365; Sat, 20 Jan 2001 11:25:28 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Sat, 20 Jan 2001 11:25:26 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Bruce Evans Cc: bauerp , freebsd-bugs@FreeBSD.ORG Subject: Re: serial port problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 10 Jan 2001, Bruce Evans wrote: > > I hope this is something that can be addressed. Last night i went to > > attach a console to a switch i was working on. Every time i went to > > attach to the serial port my system locked. cu -l /dev/cuaa0 minicom and > > tip all displayed the same results. > > > > I looked through dmesg to see nothing out of the ordinary. sio0 and sio1 > > found properly, all appeared normal. Fortunately being untrusting of pc > > hardware i checked the bios to find that the serial ports had been > > disabled. After re-enabling them this behavior went away. > > > > Is it possible to have some change in status mentioned in dmesg stating > > that the serial ports are infact not operational? Probing them and > > assigning irq's to the device that isn't enabled is not very intuitive > > when it comes to trouble shooting this. > > The driver already does an unreasonable amount of checking at probe > time that the ports work. It even checks that interrupts work. > Non-working interrupts caused the probe to fail in FreeBSD-2, but now > certain types of broken interrupts only result in a boot message like > "configured irq 4 not in bitmap of probed irqs 0". I don't know how > this particular failure would cause a lockup. > > Bruce Well, I think something is wrong with the probe, 'cause this machine does not have any serial ports (it used to) yet says: ... FreeBSD 4.1.1-STABLE #0: Sat Oct 14 19:20:47 EST 2000 ... 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 ... The probe did not pick up the fact that there is no serial port. This is an old dual P90 MB with no onboard coms or lpt. -- :{ 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-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 17:35:46 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 04C8F37B402; Fri, 19 Jan 2001 17:35:29 -0800 (PST) Received: (from jedgar@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0K1ZS605204; Fri, 19 Jan 2001 17:35:28 -0800 (PST) (envelope-from jedgar) Date: Fri, 19 Jan 2001 17:35:28 -0800 (PST) From: Message-Id: <200101200135.f0K1ZS605204@freefall.freebsd.org> To: jedgar@fxp.org, jedgar@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/20993: many ftpd commands not limited to logins Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: many ftpd commands not limited to logins State-Changed-From-To: open->closed State-Changed-By: jedgar State-Changed-When: Fri Jan 19 17:35:15 PST 2001 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=20993 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Jan 19 18:30:32 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D010337B699 for ; Fri, 19 Jan 2001 18:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0K2U1011045; Fri, 19 Jan 2001 18:30:01 -0800 (PST) (envelope-from gnats) Received: from atlas.home.dynas.se (adsl-64-165-200-109.dsl.snfc21.pacbell.net [64.165.200.109]) by hub.freebsd.org (Postfix) with ESMTP id 6E4C437B698 for ; Fri, 19 Jan 2001 18:23:34 -0800 (PST) Received: (from mikko@localhost) by atlas.home.dynas.se (8.11.1/8.11.1) id f0K2NSe08062; Fri, 19 Jan 2001 18:23:28 -0800 (PST) (envelope-from mikko) Message-Id: Date: Fri, 19 Jan 2001 18:23:11 -0800 (PST) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= Reply-To: mikko@dynas.se To: FreeBSD-gnats-submit@freebsd.org Subject: bin/24472: libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket options Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24472 >Category: bin >Synopsis: libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket options >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 19 18:30:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Mikko Tyolajarvi >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: 4.2-STABLE as of Jan 19, 2001 >Description: The socket options SO_SNDTIMEO and SO_RCVTIMEO which can be used to make blocking socket I/O operations time out are ignored by libc_r. >How-To-Repeat: Uh, like, try to use them... Operations will block forever. >Fix: The patch below adds support for the missing socket options in the uthread library. In short: - Timeout values are cached per fd - The timeouts are imported when data on the fd is initialised - They are updated when calling {set,get}sockopt() - When blocking on an I/O operation, and the fd is a socket, and it has a timeout defined, limit the time to sleep, and return an error code (or in some cases a short count) on timeout. Affected functions are: Sets timeout values: getsockopt, setsockopt, dup, dup2, fcntl I/O: read, readv, recvfrom, recvmsg, sendfile, sendmsg, sendto, write, writev The patch has been somewhat tested, but I wouldn't install it in a live system controlling nuclear power plants without some additional review. $.02, /Mikko diff -ru uthread.org/pthread_private.h uthread/pthread_private.h --- uthread.org/pthread_private.h Sat Nov 25 10:10:27 2000 +++ uthread/pthread_private.h Fri Jan 19 17:26:49 2001 @@ -550,6 +550,8 @@ int r_lockcount; /* Count for FILE read locks. */ int w_lockcount; /* Count for FILE write locks. */ int flags; /* Flags used in open. */ + struct timespec rcvtimeo; /* Input timeout for sockets */ + struct timespec sndtimeo; /* Output timeout for sockets */ }; struct pthread_poll_data { @@ -1193,6 +1195,11 @@ #define _FD_LOCK(_fd,_type,_ts) _thread_fd_lock(_fd, _type, _ts) #define _FD_UNLOCK(_fd,_type) _thread_fd_unlock(_fd, _type) #endif + +/* Get a suitable argument for _thread_kern_set_timeout(), given an fd */ +#define _FD_TIMEO(_ts) (((_ts)->tv_sec || (_ts)->tv_nsec) ? (_ts) : NULL) +#define _FD_RCVTIMEO(_fd) _FD_TIMEO(&_thread_fd_table[(_fd)]->rcvtimeo) +#define _FD_SNDTIMEO(_fd) _FD_TIMEO(&_thread_fd_table[(_fd)]->sndtimeo) /* * Function prototype definitions. diff -ru uthread.org/uthread_dup.c uthread/uthread_dup.c --- uthread.org/uthread_dup.c Sat Jan 29 14:53:41 2000 +++ uthread/uthread_dup.c Fri Jan 19 16:26:34 2001 @@ -59,6 +59,10 @@ * checked later: */ _thread_fd_table[ret]->flags = _thread_fd_table[fd]->flags; + + /* Copy socket timeouts: */ + _thread_fd_table[ret]->rcvtimeo = _thread_fd_table[fd]->rcvtimeo; + _thread_fd_table[ret]->sndtimeo = _thread_fd_table[fd]->sndtimeo; } /* Unlock the file descriptor: */ diff -ru uthread.org/uthread_dup2.c uthread/uthread_dup2.c --- uthread.org/uthread_dup2.c Sat Jan 29 14:53:42 2000 +++ uthread/uthread_dup2.c Fri Jan 19 16:26:53 2001 @@ -71,6 +71,10 @@ * be checked later: */ _thread_fd_table[ret]->flags = _thread_fd_table[fd]->flags; + + /* Copy socket timeouts: */ + _thread_fd_table[ret]->rcvtimeo = _thread_fd_table[fd]->rcvtimeo; + _thread_fd_table[ret]->sndtimeo = _thread_fd_table[fd]->sndtimeo; } /* Unlock the file descriptor: */ diff -ru uthread.org/uthread_fcntl.c uthread/uthread_fcntl.c --- uthread.org/uthread_fcntl.c Fri Jan 28 14:10:27 2000 +++ uthread/uthread_fcntl.c Fri Jan 19 16:27:12 2001 @@ -78,6 +78,10 @@ * be checked later: */ _thread_fd_table[ret]->flags = _thread_fd_table[fd]->flags; + + /* Copy socket timeouts: */ + _thread_fd_table[ret]->rcvtimeo = _thread_fd_table[fd]->rcvtimeo; + _thread_fd_table[ret]->sndtimeo = _thread_fd_table[fd]->sndtimeo; } break; case F_SETFD: diff -ru uthread.org/uthread_fd.c uthread/uthread_fd.c --- uthread.org/uthread_fd.c Sat Nov 25 10:10:27 2000 +++ uthread/uthread_fd.c Fri Jan 19 17:40:31 2001 @@ -39,6 +39,7 @@ #ifdef _THREAD_SAFE #include #include "pthread_private.h" +#include #define FDQ_INSERT(q,p) \ do { \ @@ -76,6 +77,8 @@ int ret = 0; struct fd_table_entry *entry; int saved_errno; + struct timeval tv; + socklen_t tlen; /* Check if the file descriptor is out of range: */ if (fd < 0 || fd >= _thread_dtablesize) { @@ -112,6 +115,19 @@ /* Initialise the read/write queues: */ TAILQ_INIT(&entry->r_queue); TAILQ_INIT(&entry->w_queue); + + /* Initialise socket timeouts: */ + tlen = sizeof(tv); + if (_thread_sys_getsockopt(fd, SOL_SOCKET, SO_RCVTIMEO, &tv, &tlen) < 0) { + entry->rcvtimeo.tv_sec = 0; + entry->rcvtimeo.tv_nsec = 0; + entry->sndtimeo.tv_sec = 0; + entry->sndtimeo.tv_nsec = 0; + } else { + TIMEVAL_TO_TIMESPEC(&tv, &entry->rcvtimeo); + _thread_sys_getsockopt(fd, SOL_SOCKET, SO_SNDTIMEO, &tv, &tlen); + TIMEVAL_TO_TIMESPEC(&tv, &entry->sndtimeo); + } /* Get the flags for the file: */ if (((fd >= 3) || (_pthread_stdio_flags[fd] == -1)) && diff -ru uthread.org/uthread_getsockopt.c uthread/uthread_getsockopt.c --- uthread.org/uthread_getsockopt.c Sat Jan 29 14:53:48 2000 +++ uthread/uthread_getsockopt.c Fri Jan 19 17:24:47 2001 @@ -45,6 +45,16 @@ if ((ret = _FD_LOCK(fd, FD_RDWR, NULL)) == 0) { ret = _thread_sys_getsockopt(fd, level, optname, optval, optlen); + if (ret == 0 && level == SOL_SOCKET) { + switch (optname) { + case SO_SNDTIMEO: + TIMEVAL_TO_TIMESPEC((struct timeval *)optval, &_thread_fd_table[fd]->sndtimeo); + break; + case SO_RCVTIMEO: + TIMEVAL_TO_TIMESPEC((struct timeval *)optval, &_thread_fd_table[fd]->rcvtimeo); + break; + } + } _FD_UNLOCK(fd, FD_RDWR); } return ret; diff -ru uthread.org/uthread_read.c uthread/uthread_read.c --- uthread.org/uthread_read.c Thu Jan 27 15:07:13 2000 +++ uthread/uthread_read.c Fri Jan 19 16:56:15 2001 @@ -70,10 +70,11 @@ if ((_thread_fd_table[fd]->flags & O_NONBLOCK) == 0 && (errno == EWOULDBLOCK || errno == EAGAIN)) { _thread_run->data.fd.fd = fd; - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_RCVTIMEO(fd)); /* Reset the interrupted operation flag: */ _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDR_WAIT, __FILE__, __LINE__); @@ -87,6 +88,10 @@ ret = -1; break; } + + /* Socket timer timed out: */ + if (_thread_run->timeout) + break; } else { break; } diff -ru uthread.org/uthread_readv.c uthread/uthread_readv.c --- uthread.org/uthread_readv.c Sat Jan 29 14:53:49 2000 +++ uthread/uthread_readv.c Fri Jan 19 16:56:05 2001 @@ -65,10 +65,11 @@ if ((_thread_fd_table[fd]->flags & O_NONBLOCK) == 0 && (errno == EWOULDBLOCK || errno == EAGAIN)) { _thread_run->data.fd.fd = fd; - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_RCVTIMEO(fd)); /* Reset the interrupted operation flag: */ _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDR_WAIT, __FILE__, __LINE__); @@ -82,6 +83,10 @@ ret = -1; break; } + + /* Socket timer timed out: */ + if (_thread_run->timeout) + break; } else { break; } diff -ru uthread.org/uthread_recvfrom.c uthread/uthread_recvfrom.c --- uthread.org/uthread_recvfrom.c Sat Jan 29 14:53:50 2000 +++ uthread/uthread_recvfrom.c Fri Jan 19 16:57:03 2001 @@ -51,8 +51,9 @@ _thread_run->data.fd.fd = fd; /* Set the timeout: */ - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_RCVTIMEO(fd)); _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDR_WAIT, __FILE__, __LINE__); /* Check if the wait was interrupted: */ @@ -62,6 +63,8 @@ ret = -1; break; } + if (_thread_run->timeout) + break; } else { ret = -1; break; diff -ru uthread.org/uthread_recvmsg.c uthread/uthread_recvmsg.c --- uthread.org/uthread_recvmsg.c Sat Jan 29 14:53:50 2000 +++ uthread/uthread_recvmsg.c Fri Jan 19 16:57:55 2001 @@ -50,8 +50,9 @@ _thread_run->data.fd.fd = fd; /* Set the timeout: */ - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_RCVTIMEO(fd)); _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDR_WAIT, __FILE__, __LINE__); /* Check if the wait was interrupted: */ @@ -61,6 +62,8 @@ ret = -1; break; } + if (_thread_run->timeout) + break; } else { ret = -1; break; diff -ru uthread.org/uthread_sendfile.c uthread/uthread_sendfile.c --- uthread.org/uthread_sendfile.c Sat Nov 25 10:10:28 2000 +++ uthread/uthread_sendfile.c Fri Jan 19 17:17:59 2001 @@ -109,10 +109,11 @@ num += n; _thread_run->data.fd.fd = fd; - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_SNDTIMEO(fd)); /* Reset the interrupted operation flag. */ _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDW_WAIT, __FILE__, __LINE__); @@ -121,6 +122,8 @@ /* Interrupted by a signal. Return an error. */ break; } + if (_thread_run->timeout) + break; } else { /* Incomplete non-blocking syscall, or error. */ break; diff -ru uthread.org/uthread_sendmsg.c uthread/uthread_sendmsg.c --- uthread.org/uthread_sendmsg.c Sat Jan 29 14:53:51 2000 +++ uthread/uthread_sendmsg.c Fri Jan 19 17:08:02 2001 @@ -50,8 +50,9 @@ _thread_run->data.fd.fd = fd; /* Set the timeout: */ - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_SNDTIMEO(fd)); _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDW_WAIT, __FILE__, __LINE__); /* Check if the operation was interrupted: */ @@ -60,6 +61,8 @@ ret = -1; break; } + if (_thread_run->timeout) + break; } else { ret = -1; break; diff -ru uthread.org/uthread_sendto.c uthread/uthread_sendto.c --- uthread.org/uthread_sendto.c Sat Jan 29 14:53:51 2000 +++ uthread/uthread_sendto.c Fri Jan 19 17:09:12 2001 @@ -51,8 +51,9 @@ _thread_run->data.fd.fd = fd; /* Set the timeout: */ - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_SNDTIMEO(fd)); _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDW_WAIT, __FILE__, __LINE__); /* Check if the operation was interrupted: */ @@ -61,6 +62,8 @@ ret = -1; break; } + if (_thread_run->timeout) + break; } else { ret = -1; break; diff -ru uthread.org/uthread_setsockopt.c uthread/uthread_setsockopt.c --- uthread.org/uthread_setsockopt.c Sat Jan 29 14:53:52 2000 +++ uthread/uthread_setsockopt.c Fri Jan 19 17:25:41 2001 @@ -45,6 +45,16 @@ if ((ret = _FD_LOCK(fd, FD_RDWR, NULL)) == 0) { ret = _thread_sys_setsockopt(fd, level, optname, optval, optlen); + if (ret == 0 && level == SOL_SOCKET) { + switch (optname) { + case SO_SNDTIMEO: + TIMEVAL_TO_TIMESPEC((struct timeval *)optval, &_thread_fd_table[fd]->sndtimeo); + break; + case SO_RCVTIMEO: + TIMEVAL_TO_TIMESPEC((struct timeval *)optval, &_thread_fd_table[fd]->rcvtimeo); + break; + } + } _FD_UNLOCK(fd, FD_RDWR); } return ret; diff -ru uthread.org/uthread_write.c uthread/uthread_write.c --- uthread.org/uthread_write.c Sat Nov 25 10:10:31 2000 +++ uthread/uthread_write.c Fri Jan 19 17:15:57 2001 @@ -95,10 +95,11 @@ if (blocking && ((n < 0 && (errno == EWOULDBLOCK || errno == EAGAIN)) || (n >= 0 && num < nbytes))) { _thread_run->data.fd.fd = fd; - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_SNDTIMEO(fd)); /* Reset the interrupted operation flag: */ _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDW_WAIT, __FILE__, __LINE__); @@ -110,6 +111,15 @@ if (_thread_run->interrupted) { /* Return an error: */ ret = -1; + } + if (_thread_run->timeout) { + /* Return a short count or an error */ + if (num > 0) { + ret = num; + } else { + ret = -1; + errno = EWOULDBLOCK; + } } /* diff -ru uthread.org/uthread_writev.c uthread/uthread_writev.c --- uthread.org/uthread_writev.c Sat Jan 29 14:53:55 2000 +++ uthread/uthread_writev.c Fri Jan 19 17:20:59 2001 @@ -159,10 +159,11 @@ if (blocking && ((n < 0 && (errno == EWOULDBLOCK || errno == EAGAIN)) || (n >= 0 && idx < iovcnt))) { _thread_run->data.fd.fd = fd; - _thread_kern_set_timeout(NULL); + _thread_kern_set_timeout(_FD_SNDTIMEO(fd)); /* Reset the interrupted operation flag: */ _thread_run->interrupted = 0; + _thread_run->timeout = 0; _thread_kern_sched_state(PS_FDW_WAIT, __FILE__, __LINE__); @@ -174,6 +175,15 @@ if (_thread_run->interrupted) { /* Return an error: */ ret = -1; + } + if (_thread_run->timeout) { + /* Return a short count or an error */ + if (num > 0) { + ret = num; + } else { + ret = -1; + errno = EWOULDBLOCK; + } } /* Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 0:16: 6 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from erika.sixgirls.org (erika.sixgirls.org [209.208.150.50]) by hub.freebsd.org (Postfix) with ESMTP id 9874A37B401 for ; Sat, 20 Jan 2001 00:15:49 -0800 (PST) Received: from localhost (localhost [[UNIX: localhost]]) by erika.sixgirls.org (8.11.2/8.11.1) with ESMTP id f0K8FmE00144 for ; Sat, 20 Jan 2001 03:15:48 -0500 (EST) Date: Sat, 20 Jan 2001 03:15:47 -0500 (EST) From: John Klos To: Subject: Nonexistent upgrade kit Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I sent this email almost three weeks ago, but received no response, and the FreeBSD 4.0 to 4-stable kit, which is so blatantly advertised on the www.freebsd.org/ports/ page, still does not exist. As I am already on lots of NetBSD email lists, I really do not want to join any FreeBSD lists (the FreeBSD machine I'd like to upgrade belongs to my girlfriend), so could someone please forward this along to the appropriate list? Thank you, John Klos ---------- Forwarded message ---------- Date: Mon, 1 Jan 2001 18:20:15 -0500 (EST) From: John Klos To: webmaster@freebsd.org Subject: Broken link... Hello, on the http://www.freebsd.org/ports/ page, the 4.0 to 4-stable upgrade kit is improperly linked. The link points to ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/Latest/40upgrade.tgz which does not exist. There is a 4.1upgrade.tgz, but apparently this doesn't work with 4.0. Thanks, John Klos -- Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 3:30:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1A05A37B6A2 for ; Sat, 20 Jan 2001 03:30:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KBU7c82715; Sat, 20 Jan 2001 03:30:07 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 03:30:07 -0800 (PST) Message-Id: <200101201130.f0KBU7c82715@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Crist J. Clark" Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: "Crist J. Clark" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: "Crist J. Clark" To: Dag-Erling Smorgrav Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: Fri, 19 Jan 2001 11:03:41 -0800 *This message was transferred with a trial version of CommuniGate(tm) Pro* On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > cjclark@reflexcom.com writes: > > I propose that syslogd(8) should reload the hostname with a > > SIGHUP. I cannot think of any reason that one should not update the > > hostname, but as I pointed out, there are reasons why one would want > > that behavior. > > It should also log a message if the hostname changes. Should that be a responsibility of syslogd(8) or hostname(1)? Personally, it might be a slippery slope to start adding things that syslogd(8) should maintain state on, but since syslogd(8) actually uses the hostname... One also could start arguing that syslogd(8) should check the hostname everytime it logs something despite the performance hit. As for what syslogd(8) does now, if you look at the example output in the PR, notice syslogd(8) didn't even log when it was HUP'ed. IMHO, I think it is beyond the scope of syslogd(8) to actually track changes in the hostname in real-time. Noticing a change when given a HUP signal, would seem reasonable, but if hostname(1) were to log changes, that would also be fairly redundant. -- Crist J. Clark cjclark@alum.mit.edu 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-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 4:20:25 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7AC0237B401 for ; Sat, 20 Jan 2001 04:20:09 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KCK9992893; Sat, 20 Jan 2001 04:20:09 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 04:20:09 -0800 (PST) Message-Id: <200101201220.f0KCK9992893@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "A.Yu.Isupov" Subject: Re: bin/24458: named-xfer executed at 20 priority level instead of wanted 0 level Reply-To: "A.Yu.Isupov" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24458; it has been noted by GNATS. From: "A.Yu.Isupov" To: Kris Kennaway Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/24458: named-xfer executed at 20 priority level instead of wanted 0 level Date: Sat, 20 Jan 2001 15:18:19 +0300 (MSK) Are you can follow up this bug report to BIND team ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 6:30:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 50F3637B699 for ; Sat, 20 Jan 2001 06:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KEU2m08253; Sat, 20 Jan 2001 06:30:02 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 06:30:02 -0800 (PST) Message-Id: <200101201430.f0KEU2m08253@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Dag-Erling Smorgrav Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: Dag-Erling Smorgrav Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: Dag-Erling Smorgrav To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: 19 Jan 2001 23:09:24 +0100 *This message was transferred with a trial version of CommuniGate(tm) Pro* "Crist J. Clark" writes: > On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > > It should also log a message if the hostname changes. > Should that be a responsibility of syslogd(8) or hostname(1)? I meant syslogd(8), but putting it in hostname(1) might makes sense, except that hostname(1) is not the only way to set the hostname ('sysctl -w kern.hostname=foo' is another) DES -- Dag-Erling Smorgrav - des@ofug.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-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 6:50:47 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8128C37B698 for ; Sat, 20 Jan 2001 06:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KEo2k94042; Sat, 20 Jan 2001 06:50:02 -0800 (PST) (envelope-from gnats) Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id B90B137B401 for ; Sat, 20 Jan 2001 06:42:21 -0800 (PST) Received: (qmail 2622 invoked by uid 0); 20 Jan 2001 14:42:06 -0000 Received: from p3ee21676.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.118) by mail.gmx.net (mp006-rz3) with SMTP; 20 Jan 2001 14:42:06 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id PAA21274 for FreeBSD-gnats-submit@freebsd.org; Sat, 20 Jan 2001 15:39:41 +0100 Message-Id: <20010120153941.L253@speedy.gsinet> Date: Sat, 20 Jan 2001 15:39:41 +0100 From: Gerhard Sittig To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/24485: [PATCH] to make cron(8) handle clock jumps Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24485 >Category: bin >Synopsis: [PATCH] to make cron(8) handle clock jumps >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jan 20 06:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Gerhard Sittig >Release: FreeBSD 5.0-CURRENT i386 >Organization: in private >Environment: typical: FreeBSD installation with neither NTP setup nor absent time correction -- i.e. administrator's (manual?) intervention by means of date(8), netdate(8), ntpdate(8), or any other method of _changing_ or _setting_ the system clock instead of _adjusting_ it much unexpected: FreeBSD installation with such high a load that cron(8) wakes up minutes after its last tick *not* applicable for DST changes (in its original form), but followups expected to maybe turn this approach into a solution for DST issues; see the audit trail for this aspect >Description: cron(8) by design only looks at the current time at wakeup and runs (schedules) jobs for the current time only. This could make it skip jobs in the rare case where load prevents cron(8) from waking up fast enough / often enough to catch up with the current minute (quite inprobable). But all of the above mentioned manual clock correction (wall clock triggered date(8) invocation, manual or cron scheduled netdate(8) invocation, etc) will make the clock jump, too, and cron could skip jobs scheduled for the time jumped over forward as well as cron could run jobs scheduled to run once multiple times in case the clock is corrected backwards. One suggestion in related public discussion has been that a clean setup would make use of NTP, but this is not always an option when there's no permanent connection to suport the ntp client's communication needs. And after all it may not be important to run jobs at exact times but much more to run them with the frequency specified. DST changes have a similar "visible" effect of turning the "once a day" specification provided by the admin into "maybe not at all" or "at least once" behaviour -- which makes discussions bubble up twice a year in public lists. But the patch attached below does not solve this situation. Although the doc suggests it does, the time(3) result the "jump detection" is based on is not affected by differently interpreting local time presentation and thus the mechanism doesn't jump into action should the local clock be switched due to a DST change. Although one could think of extending the way "wakeupKind" is determined by additionally taking some localtime(3) result into consideration. There has been and will be strong reservation against touching cron(8) and leaving it in its current state was demanded to not introduce new bugs as well as to stick with POLA while leaving "intelligence" out of such a simple mechanism as cron(8) is designed to be. So this PR is accompanied by PR conf/24358 ("[PATCH] etc/rc variables for cron(8)") and - in case the patch gets accepted - the suggestion to make the modified cron tree a copy of the currently established src/usr.sbin/cron tree or some port. The minimum modification making the change acceptable to those who demand cron(8) to stick with current behaviour would be to wrap the new code into an option defaulting to "off". The rc.conf knobs allow for passing a newly introduced command line switch should the admin want the new behaviour. >How-To-Repeat: For the manual correction: Schedule a job to execute at a given daytime (i.e. maximum frequency "daily"). Wait for a short moment before its expected execution and make the clock jump forward by means of 'date -v +1H' or something. The job will be skipped. Issue some 'date -v -1H' command after the job's execution and see how the job gets executed righ away -- for a second time at the current date. When the patch got applied, the job will run exactly once in any of the above situations. For comparison and to make sure the old behaviour still applies to jobs with wildcard specs: Schedule a job with a higher execution frequency of, say, 5 minutes. See this job getting executed as scheduled without as well as with the attached patch. For the DST change: Schedule a cronjob for a daytime which falls into the timeframe skipped over or passed repeatedly by the DST change (see /usr/src/share/zoneinfo/ or zdump(8) -v output for details on your region / timezone) and watch its execution happen one times, two times or not at all when running without DST changes and when the DST change takes place (from ST to DST as well as from DST to ST). >Fix: [ intro: The origin of my effort was the DST discussion bubbling up twice a year. I believed the OpenBSD project to have a solution (the manpage read this way) and tried to port it to FreeBSD. While in tests the patch turned out to not work for DST changes, yet I feel it to be of benefit where the clock is not run freely or under graceful correction methods like NTP daemons. And the code could serve as a skeleton to be extended for DST handling (which cannot be solved by means of NTP). ] The OpenBSD team has taken action and modified their vixie cron version in December 1997. I extracted the diff between the OpenBSD and FreeBSD versions of cron and stripped it down to the DST relevant parts only, so this functionality is "obtained from OpenBSD". The patch is cited here in verbatim form "for the record" although it could benefit from some further mangling. Due to the nature of the diff (heavy modification with still some single lines "being the same" -- mostly comment closing brackets) this seems to be one of the rare cases where context diff format is more appropriate than unified diff format. So I will enclose both for the readers' comfort. There's no doubt about what further modifications could look like: - the manpage shouldn't promise to handle DST but should mention one of the situations it really does handle, like date(8) - everything not covering the "most common case" of just one minute passed by should be made optional, defaulting to being turned off (the wakeupKind determination and its switch contruct) - the trigger level for "way too far a jump to be a valid correction, so it is some kind of new setup" could be made a knob tweakable by compile time options or command line parameters - maybe some localtime(3) call could be considered when determining wakeupKind, with another command line option to turn this new behaviour on -- this could support DST changes to be handled in a way most humans expect it to be There's been a rather lengthy thread on freebsd-hackers about this proposal, started by <20001205225656.Z27042@speedy.gsinet> as of December 5th, 2000, which is archived at http://www.freebsd.org/cgi/getmsg.cgi?fetch=211030+217815+/usr/local/www/db/text/2000/freebsd-hackers/20001210.freebsd-hackers. In its course I came to the conclusion that more appropriate ways to solve the DST issue (I don't want to call it a "problem" any longer) would be to - make admins more aware of the consequences to schedule jobs (and have them check the installed crontab they didn't provide themselves!) which is an educational issue and turns out to be just as ever lasting as the current debate is - provide some translater to / from a unified coordinate system which doesn't change in a day's run, proposals in the thread included - interpreting the daytime in the job specs read "passed since midnight no matter what the wallclock says" in combination with a comment that some days have 23 or 25 hours - specifying a TZ variable in the crontab file to determine how the job specs are to be interpreted - passing another command line option to read all crontab entries to be UTC plus maybe - wrapping 'crontab -e' into some converter presenting to / taking from the user local time representation and storing it in UTC which is what the cron daemon expects them to be # 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: # # cron-diff.context # cron-diff.unified # echo x - cron-diff.context sed 's/^X//' >cron-diff.context << 'END-of-cron-diff.context' XIndex: cron/cron.8 X=================================================================== XRCS file: /CVSREPO/fbsd/src/usr.sbin/cron/cron/cron.8,v Xretrieving revision 1.7 Xdiff -u -c -r1.7 cron.8 Xcvs diff: conflicting specifications of output style X*** cron/cron.8 1999/08/28 01:15:49 1.7 X--- cron/cron.8 2000/11/28 21:45:13 X*************** X*** 68,73 **** X--- 68,92 ---- X .Xr crontab 1 X command updates the modtime of the spool directory whenever it changes a X crontab. X+ .Pp X+ Special considerations exist when the clock is changed by less than 3 X+ hours; for example, at the beginning and end of Daylight Saving X+ Time. X+ If the time has moved forward, those jobs which would have X+ run in the time that was skipped will be run soon after the change. X+ Conversely, if the time has moved backward by less than 3 hours, X+ those jobs that fall into the repeated time will not be run. X+ .Pp X+ Only jobs that run at a particular time (not specified as @hourly, nor with X+ .Ql * X+ in the hour or minute specifier) X+ are X+ affected. X+ Jobs which are specified with wildcards are run based on the X+ new time immediately. X+ .Pp X+ Clock changes of more than 3 hours are considered to be corrections to X+ the clock, and the new time is used immediately. X .Sh SEE ALSO X .Xr crontab 1 , X .Xr crontab 5 XIndex: cron/cron.c X=================================================================== XRCS file: /CVSREPO/fbsd/src/usr.sbin/cron/cron/cron.c,v Xretrieving revision 1.9 Xdiff -u -c -r1.9 cron.c Xcvs diff: conflicting specifications of output style X*** cron/cron.c 1999/08/28 01:15:49 1.9 X--- cron/cron.c 2000/11/28 21:58:22 X*************** X*** 34,42 **** X X static void usage __P((void)), X run_reboot_jobs __P((cron_db *)), X! cron_tick __P((cron_db *)), X! cron_sync __P((void)), X! cron_sleep __P((void)), X #ifdef USE_SIGCHLD X sigchld_handler __P((int)), X #endif X--- 34,42 ---- X X static void usage __P((void)), X run_reboot_jobs __P((cron_db *)), X! find_jobs __P((time_min, cron_db *, int, int)), X! set_time __P((void)), X! cron_sleep __P((time_min)), X #ifdef USE_SIGCHLD X sigchld_handler __P((int)), X #endif X*************** X*** 121,143 **** X database.tail = NULL; X database.mtime = (time_t) 0; X load_database(&database); X run_reboot_jobs(&database); X! cron_sync(); X while (TRUE) { X # if DEBUGGING X /* if (!(DebugFlags & DTEST)) */ X # endif /*DEBUGGING*/ X! cron_sleep(); X X load_database(&database); X X! /* do this iteration X */ X! cron_tick(&database); X X! /* sleep 1 minute X */ X! TargetTime += 60; X } X } X X--- 121,246 ---- X database.tail = NULL; X database.mtime = (time_t) 0; X load_database(&database); X+ X+ set_time(); X run_reboot_jobs(&database); X! timeRunning = virtualTime = clockTime; X! X! /* X! * too many clocks, not enough time (Al. Einstein) X! * These clocks are in minutes since the epoch (time()/60). X! * virtualTime: is the time it *would* be if we woke up X! * promptly and nobody ever changed the clock. It is X! * monotonically increasing... unless a timejump happens. X! * At the top of the loop, all jobs for 'virtualTime' have run. X! * timeRunning: is the time we last awakened. X! * clockTime: is the time when set_time was last called. X! */ X while (TRUE) { X # if DEBUGGING X /* if (!(DebugFlags & DTEST)) */ X # endif /*DEBUGGING*/ X! time_min timeDiff; X! int wakeupKind; X X load_database(&database); X X! /* ... wait for the time (in minutes) to change ... */ X! do { X! cron_sleep(timeRunning + 1); X! set_time(); X! } while (clockTime == timeRunning); X! timeRunning = clockTime; X! X! /* X! * ... calculate how the current time differs from X! * our virtual clock. Classify the change into one X! * of 4 cases X */ X! timeDiff = timeRunning - virtualTime; X X! /* shortcut for the most common case */ X! if (timeDiff == 1) { X! virtualTime = timeRunning; X! find_jobs(virtualTime, &database, TRUE, TRUE); X! } else { X! wakeupKind = -1; X! if (timeDiff > -(3*MINUTE_COUNT)) X! wakeupKind = 0; X! if (timeDiff > 0) X! wakeupKind = 1; X! if (timeDiff > 5) X! wakeupKind = 2; X! if (timeDiff > (3*MINUTE_COUNT)) X! wakeupKind = 3; X! X! switch (wakeupKind) { X! case 1: X! /* X! * case 1: timeDiff is a small positive number X! * (wokeup late) run jobs for each virtual minute X! * until caught up. X! */ X! Debug(DSCH, ("[%d], normal case %d minutes to go\n", X! getpid(), timeRunning - virtualTime)) X! do { X! if (job_runqueue()) X! sleep(10); X! virtualTime++; X! find_jobs(virtualTime, &database, TRUE, TRUE); X! } while (virtualTime< timeRunning); X! break; X! X! case 2: X! /* X! * case 2: timeDiff is a medium-sized positive number, X! * for example because we went to DST run wildcard X! * jobs once, then run any fixed-time jobs that would X! * otherwise be skipped if we use up our minute X! * (possible, if there are a lot of jobs to run) go X! * around the loop again so that wildcard jobs have X! * a chance to run, and we do our housekeeping X */ X! Debug(DSCH, ("[%d], DST begins %d minutes to go\n", X! getpid(), timeRunning - virtualTime)) X! /* run wildcard jobs for current minute */ X! find_jobs(timeRunning, &database, TRUE, FALSE); X! X! /* run fixed-time jobs for each minute missed */ X! do { X! if (job_runqueue()) X! sleep(10); X! virtualTime++; X! find_jobs(virtualTime, &database, FALSE, TRUE); X! set_time(); X! } while (virtualTime< timeRunning && X! clockTime == timeRunning); X! break; X! X! case 0: X! /* X! * case 3: timeDiff is a small or medium-sized X! * negative num, eg. because of DST ending just run X! * the wildcard jobs. The fixed-time jobs probably X! * have already run, and should not be repeated X! * virtual time does not change until we are caught up X! */ X! Debug(DSCH, ("[%d], DST ends %d minutes to go\n", X! getpid(), virtualTime - timeRunning)) X! find_jobs(timeRunning, &database, TRUE, FALSE); X! break; X! default: X! /* X! * other: time has changed a *lot*, X! * jump virtual time, and run everything X! */ X! Debug(DSCH, ("[%d], clock jumped\n", getpid())) X! virtualTime = timeRunning; X! find_jobs(timeRunning, &database, TRUE, TRUE); X! } X! } X! /* jobs to be run (if any) are loaded. clear the queue */ X! job_runqueue(); X } X } X X*************** X*** 161,170 **** X X X static void X! cron_tick(db) X cron_db *db; X { X! register struct tm *tm = localtime(&TargetTime); X register int minute, hour, dom, month, dow; X register user *u; X register entry *e; X--- 264,277 ---- X X X static void X! find_jobs(vtime, db, doWild, doNonWild) X! time_min vtime; X cron_db *db; X+ int doWild; X+ int doNonWild; X { X! time_t virtualSecond = vtime * SECONDS_PER_MINUTE; X! register struct tm *tm = localtime(&virtualSecond); X register int minute, hour, dom, month, dow; X register user *u; X register entry *e; X*************** X*** 197,204 **** X && ( ((e->flags & DOM_STAR) || (e->flags & DOW_STAR)) X ? (bit_test(e->dow,dow) && bit_test(e->dom,dom)) X : (bit_test(e->dow,dow) || bit_test(e->dom,dom)) X! ) X! ) { X job_add(e, u); X } X } X--- 304,314 ---- X && ( ((e->flags & DOM_STAR) || (e->flags & DOW_STAR)) X ? (bit_test(e->dow,dow) && bit_test(e->dom,dom)) X : (bit_test(e->dow,dow) || bit_test(e->dom,dom)) X! ) X! ) { X! if ((doNonWild && !(e->flags & (MIN_STAR|HR_STAR))) X! || (doWild && (e->flags & (MIN_STAR|HR_STAR))) X! ) X job_add(e, u); X } X } X*************** X*** 206,267 **** X } X X X! /* the task here is to figure out how long it's going to be until :00 of the X! * following minute and initialize TargetTime to this value. TargetTime X! * will subsequently slide 60 seconds at a time, with correction applied X! * implicitly in cron_sleep(). it would be nice to let cron execute in X! * the "current minute" before going to sleep, but by restarting cron you X! * could then get it to execute a given minute's jobs more than once. X! * instead we have the chance of missing a minute's jobs completely, but X! * that's something sysadmin's know to expect what with crashing computers.. X */ X static void X! cron_sync() { X! register struct tm *tm; X! X! TargetTime = time((time_t*)0); X! tm = localtime(&TargetTime); X! TargetTime += (60 - tm->tm_sec); X } X X- X- static void X- cron_sleep() { X- int seconds_to_wait = 0; X- X- /* X- * Loop until we reach the top of the next minute, sleep when possible. X- */ X- X- for (;;) { X- seconds_to_wait = (int) (TargetTime - time((time_t*)0)); X- X /* X! * If the seconds_to_wait value is insane, jump the cron X */ X! X! if (seconds_to_wait < -600 || seconds_to_wait > 600) { X! cron_sync(); X! continue; X! } X X Debug(DSCH, ("[%d] TargetTime=%ld, sec-to-wait=%d\n", X! getpid(), (long)TargetTime, seconds_to_wait)) X X! /* X! * If we've run out of wait time or there are no jobs left X! * to run, break X! */ X! X! if (seconds_to_wait <= 0) X! break; X! if (job_runqueue() == 0) { X! Debug(DSCH, ("[%d] sleeping for %d seconds\n", X! getpid(), seconds_to_wait)) X! X! sleep(seconds_to_wait); X! } X! } X } X X X--- 316,348 ---- X } X X X! /* X! * set StartTime and clockTime to the current time. X! * these are used for computing what time it really is right now. X! * note that clockTime is a unix wallclock time converted to minutes X */ X static void X! set_time() X! { X! StartTime = time((time_t *)0); X! clockTime = StartTime / (unsigned long)SECONDS_PER_MINUTE; X } X X /* X! * try to just hit the next minute X */ X! static void X! cron_sleep(target) X! time_min target; X! { X! register int seconds_to_wait; X X+ seconds_to_wait = (int)(target*SECONDS_PER_MINUTE - time((time_t*)0)) + 1; X Debug(DSCH, ("[%d] TargetTime=%ld, sec-to-wait=%d\n", X! getpid(), (long)target*SECONDS_PER_MINUTE, seconds_to_wait)) X X! if (seconds_to_wait > 0 && seconds_to_wait< 65) X! sleep((unsigned int) seconds_to_wait); X } X X XIndex: cron/cron.h X=================================================================== XRCS file: /CVSREPO/fbsd/src/usr.sbin/cron/cron/cron.h,v Xretrieving revision 1.10 Xdiff -u -c -r1.10 cron.h Xcvs diff: conflicting specifications of output style X*** cron/cron.h 2000/07/01 22:58:16 1.10 X--- cron/cron.h 2000/11/28 21:45:13 X*************** X*** 122,127 **** X--- 122,131 ---- X LineNumber = ln; \ X } X X+ typedef int time_min; X+ X+ #define SECONDS_PER_MINUTE 60 X+ X #define FIRST_MINUTE 0 X #define LAST_MINUTE 59 X #define MINUTE_COUNT (LAST_MINUTE - FIRST_MINUTE + 1) X*************** X*** 172,177 **** X--- 176,183 ---- X #define DOM_STAR 0x01 X #define DOW_STAR 0x02 X #define WHEN_REBOOT 0x04 X+ #define MIN_STAR 0x08 X+ #define HR_STAR 0x10 X } entry; X X /* the crontab database will be a list of the X*************** X*** 266,272 **** X X char *ProgramName; X int LineNumber; X! time_t TargetTime; X X # if DEBUGGING X int DebugFlags; X--- 272,281 ---- X X char *ProgramName; X int LineNumber; X! time_t StartTime; X! time_min timeRunning; X! time_min virtualTime; X! time_min clockTime; X X # if DEBUGGING X int DebugFlags; X*************** X*** 281,287 **** X *DowNames[], X *ProgramName; X extern int LineNumber; X! extern time_t TargetTime; X # if DEBUGGING X extern int DebugFlags; X extern char *DebugFlagNames[]; X--- 290,299 ---- X *DowNames[], X *ProgramName; X extern int LineNumber; X! extern time_t StartTime; X! extern time_min timeRunning; X! extern time_min virtualTime; X! extern time_min clockTime; X # if DEBUGGING X extern int DebugFlags; X extern char *DebugFlagNames[]; END-of-cron-diff.context echo x - cron-diff.unified sed 's/^X//' >cron-diff.unified << 'END-of-cron-diff.unified' XIndex: cron/cron.8 X=================================================================== XRCS file: /CVSREPO/fbsd/src/usr.sbin/cron/cron/cron.8,v Xretrieving revision 1.7 Xdiff -u -u -r1.7 cron.8 X--- cron/cron.8 1999/08/28 01:15:49 1.7 X+++ cron/cron.8 2000/11/28 21:45:13 X@@ -68,6 +68,25 @@ X .Xr crontab 1 X command updates the modtime of the spool directory whenever it changes a X crontab. X+.Pp X+Special considerations exist when the clock is changed by less than 3 X+hours; for example, at the beginning and end of Daylight Saving X+Time. X+If the time has moved forward, those jobs which would have X+run in the time that was skipped will be run soon after the change. X+Conversely, if the time has moved backward by less than 3 hours, X+those jobs that fall into the repeated time will not be run. X+.Pp X+Only jobs that run at a particular time (not specified as @hourly, nor with X+.Ql * X+in the hour or minute specifier) X+are X+affected. X+Jobs which are specified with wildcards are run based on the X+new time immediately. X+.Pp X+Clock changes of more than 3 hours are considered to be corrections to X+the clock, and the new time is used immediately. X .Sh SEE ALSO X .Xr crontab 1 , X .Xr crontab 5 XIndex: cron/cron.c X=================================================================== XRCS file: /CVSREPO/fbsd/src/usr.sbin/cron/cron/cron.c,v Xretrieving revision 1.9 Xdiff -u -u -r1.9 cron.c X--- cron/cron.c 1999/08/28 01:15:49 1.9 X+++ cron/cron.c 2000/11/28 21:58:22 X@@ -34,9 +34,9 @@ X X static void usage __P((void)), X run_reboot_jobs __P((cron_db *)), X- cron_tick __P((cron_db *)), X- cron_sync __P((void)), X- cron_sleep __P((void)), X+ find_jobs __P((time_min, cron_db *, int, int)), X+ set_time __P((void)), X+ cron_sleep __P((time_min)), X #ifdef USE_SIGCHLD X sigchld_handler __P((int)), X #endif X@@ -121,23 +121,126 @@ X database.tail = NULL; X database.mtime = (time_t) 0; X load_database(&database); X+ X+ set_time(); X run_reboot_jobs(&database); X- cron_sync(); X+ timeRunning = virtualTime = clockTime; X+ X+ /* X+ * too many clocks, not enough time (Al. Einstein) X+ * These clocks are in minutes since the epoch (time()/60). X+ * virtualTime: is the time it *would* be if we woke up X+ * promptly and nobody ever changed the clock. It is X+ * monotonically increasing... unless a timejump happens. X+ * At the top of the loop, all jobs for 'virtualTime' have run. X+ * timeRunning: is the time we last awakened. X+ * clockTime: is the time when set_time was last called. X+ */ X while (TRUE) { X # if DEBUGGING X /* if (!(DebugFlags & DTEST)) */ X # endif /*DEBUGGING*/ X- cron_sleep(); X+ time_min timeDiff; X+ int wakeupKind; X X load_database(&database); X X- /* do this iteration X+ /* ... wait for the time (in minutes) to change ... */ X+ do { X+ cron_sleep(timeRunning + 1); X+ set_time(); X+ } while (clockTime == timeRunning); X+ timeRunning = clockTime; X+ X+ /* X+ * ... calculate how the current time differs from X+ * our virtual clock. Classify the change into one X+ * of 4 cases X */ X- cron_tick(&database); X+ timeDiff = timeRunning - virtualTime; X X- /* sleep 1 minute X+ /* shortcut for the most common case */ X+ if (timeDiff == 1) { X+ virtualTime = timeRunning; X+ find_jobs(virtualTime, &database, TRUE, TRUE); X+ } else { X+ wakeupKind = -1; X+ if (timeDiff > -(3*MINUTE_COUNT)) X+ wakeupKind = 0; X+ if (timeDiff > 0) X+ wakeupKind = 1; X+ if (timeDiff > 5) X+ wakeupKind = 2; X+ if (timeDiff > (3*MINUTE_COUNT)) X+ wakeupKind = 3; X+ X+ switch (wakeupKind) { X+ case 1: X+ /* X+ * case 1: timeDiff is a small positive number X+ * (wokeup late) run jobs for each virtual minute X+ * until caught up. X+ */ X+ Debug(DSCH, ("[%d], normal case %d minutes to go\n", X+ getpid(), timeRunning - virtualTime)) X+ do { X+ if (job_runqueue()) X+ sleep(10); X+ virtualTime++; X+ find_jobs(virtualTime, &database, TRUE, TRUE); X+ } while (virtualTime< timeRunning); X+ break; X+ X+ case 2: X+ /* X+ * case 2: timeDiff is a medium-sized positive number, X+ * for example because we went to DST run wildcard X+ * jobs once, then run any fixed-time jobs that would X+ * otherwise be skipped if we use up our minute X+ * (possible, if there are a lot of jobs to run) go X+ * around the loop again so that wildcard jobs have X+ * a chance to run, and we do our housekeeping X */ X- TargetTime += 60; X+ Debug(DSCH, ("[%d], DST begins %d minutes to go\n", X+ getpid(), timeRunning - virtualTime)) X+ /* run wildcard jobs for current minute */ X+ find_jobs(timeRunning, &database, TRUE, FALSE); X+ X+ /* run fixed-time jobs for each minute missed */ X+ do { X+ if (job_runqueue()) X+ sleep(10); X+ virtualTime++; X+ find_jobs(virtualTime, &database, FALSE, TRUE); X+ set_time(); X+ } while (virtualTime< timeRunning && X+ clockTime == timeRunning); X+ break; X+ X+ case 0: X+ /* X+ * case 3: timeDiff is a small or medium-sized X+ * negative num, eg. because of DST ending just run X+ * the wildcard jobs. The fixed-time jobs probably X+ * have already run, and should not be repeated X+ * virtual time does not change until we are caught up X+ */ X+ Debug(DSCH, ("[%d], DST ends %d minutes to go\n", X+ getpid(), virtualTime - timeRunning)) X+ find_jobs(timeRunning, &database, TRUE, FALSE); X+ break; X+ default: X+ /* X+ * other: time has changed a *lot*, X+ * jump virtual time, and run everything X+ */ X+ Debug(DSCH, ("[%d], clock jumped\n", getpid())) X+ virtualTime = timeRunning; X+ find_jobs(timeRunning, &database, TRUE, TRUE); X+ } X+ } X+ /* jobs to be run (if any) are loaded. clear the queue */ X+ job_runqueue(); X } X } X X@@ -161,10 +264,14 @@ X X X static void X-cron_tick(db) X+find_jobs(vtime, db, doWild, doNonWild) X+ time_min vtime; X cron_db *db; X+ int doWild; X+ int doNonWild; X { X- register struct tm *tm = localtime(&TargetTime); X+ time_t virtualSecond = vtime * SECONDS_PER_MINUTE; X+ register struct tm *tm = localtime(&virtualSecond); X register int minute, hour, dom, month, dow; X register user *u; X register entry *e; X@@ -197,8 +304,11 @@ X && ( ((e->flags & DOM_STAR) || (e->flags & DOW_STAR)) X ? (bit_test(e->dow,dow) && bit_test(e->dom,dom)) X : (bit_test(e->dow,dow) || bit_test(e->dom,dom)) X- ) X- ) { X+ ) X+ ) { X+ if ((doNonWild && !(e->flags & (MIN_STAR|HR_STAR))) X+ || (doWild && (e->flags & (MIN_STAR|HR_STAR))) X+ ) X job_add(e, u); X } X } X@@ -206,62 +316,33 @@ X } X X X-/* the task here is to figure out how long it's going to be until :00 of the X- * following minute and initialize TargetTime to this value. TargetTime X- * will subsequently slide 60 seconds at a time, with correction applied X- * implicitly in cron_sleep(). it would be nice to let cron execute in X- * the "current minute" before going to sleep, but by restarting cron you X- * could then get it to execute a given minute's jobs more than once. X- * instead we have the chance of missing a minute's jobs completely, but X- * that's something sysadmin's know to expect what with crashing computers.. X+/* X+ * set StartTime and clockTime to the current time. X+ * these are used for computing what time it really is right now. X+ * note that clockTime is a unix wallclock time converted to minutes X */ X static void X-cron_sync() { X- register struct tm *tm; X- X- TargetTime = time((time_t*)0); X- tm = localtime(&TargetTime); X- TargetTime += (60 - tm->tm_sec); X+set_time() X+{ X+ StartTime = time((time_t *)0); X+ clockTime = StartTime / (unsigned long)SECONDS_PER_MINUTE; X } X X- X-static void X-cron_sleep() { X- int seconds_to_wait = 0; X- X- /* X- * Loop until we reach the top of the next minute, sleep when possible. X- */ X- X- for (;;) { X- seconds_to_wait = (int) (TargetTime - time((time_t*)0)); X- X /* X- * If the seconds_to_wait value is insane, jump the cron X+ * try to just hit the next minute X */ X- X- if (seconds_to_wait < -600 || seconds_to_wait > 600) { X- cron_sync(); X- continue; X- } X+static void X+cron_sleep(target) X+ time_min target; X+{ X+ register int seconds_to_wait; X X+ seconds_to_wait = (int)(target*SECONDS_PER_MINUTE - time((time_t*)0)) + 1; X Debug(DSCH, ("[%d] TargetTime=%ld, sec-to-wait=%d\n", X- getpid(), (long)TargetTime, seconds_to_wait)) X+ getpid(), (long)target*SECONDS_PER_MINUTE, seconds_to_wait)) X X- /* X- * If we've run out of wait time or there are no jobs left X- * to run, break X- */ X- X- if (seconds_to_wait <= 0) X- break; X- if (job_runqueue() == 0) { X- Debug(DSCH, ("[%d] sleeping for %d seconds\n", X- getpid(), seconds_to_wait)) X- X- sleep(seconds_to_wait); X- } X- } X+ if (seconds_to_wait > 0 && seconds_to_wait< 65) X+ sleep((unsigned int) seconds_to_wait); X } X X XIndex: cron/cron.h X=================================================================== XRCS file: /CVSREPO/fbsd/src/usr.sbin/cron/cron/cron.h,v Xretrieving revision 1.10 Xdiff -u -u -r1.10 cron.h X--- cron/cron.h 2000/07/01 22:58:16 1.10 X+++ cron/cron.h 2000/11/28 21:45:13 X@@ -122,6 +122,10 @@ X LineNumber = ln; \ X } X X+typedef int time_min; X+ X+#define SECONDS_PER_MINUTE 60 X+ X #define FIRST_MINUTE 0 X #define LAST_MINUTE 59 X #define MINUTE_COUNT (LAST_MINUTE - FIRST_MINUTE + 1) X@@ -172,6 +176,8 @@ X #define DOM_STAR 0x01 X #define DOW_STAR 0x02 X #define WHEN_REBOOT 0x04 X+#define MIN_STAR 0x08 X+#define HR_STAR 0x10 X } entry; X X /* the crontab database will be a list of the X@@ -266,7 +272,10 @@ X X char *ProgramName; X int LineNumber; X-time_t TargetTime; X+time_t StartTime; X+time_min timeRunning; X+time_min virtualTime; X+time_min clockTime; X X # if DEBUGGING X int DebugFlags; X@@ -281,7 +290,10 @@ X *DowNames[], X *ProgramName; X extern int LineNumber; X-extern time_t TargetTime; X+extern time_t StartTime; X+extern time_min timeRunning; X+extern time_min virtualTime; X+extern time_min clockTime; X # if DEBUGGING X extern int DebugFlags; X extern char *DebugFlagNames[]; END-of-cron-diff.unified exit This patch was tested in the following environment: FreeBSD 4.2-STABLE as well as FreeBSD-4.1-RELEASE got installed and the patch was applied to the source tree. Timezone data was modified to make the next DST changes come sooner without artificially jumping the clock by means of date(1) and thus falsifying the test result. Several cronjobs were sheduled to see how they're dispatched. In parallel a stock OpenBSD 2.7 installation was fed with a modified zoneinfo data as well as a list of test case cronjobs. Emulating DST changes with 'echo date 0300 | at 0200' is what failed, as I stated above (a few times:). That's what the following modification is for: ----------------------------------------------------------------- Index: /usr/src/share/zoneinfo/europe =================================================================== RCS file: /usr/fcvs/src/share/zoneinfo/europe,v retrieving revision 1.18.2.2 diff -u -r1.18.2.2 europe --- /usr/src/share/zoneinfo/europe 2000/10/25 19:44:08 1.18.2.2 +++ /usr/src/share/zoneinfo/europe 2000/12/03 12:36:54 @@ -406,6 +406,10 @@ Rule EU 1981 max - Mar lastSun 1:00u 1:00 S Rule EU 1996 max - Oct lastSun 1:00u 0 - +# this is my private modification to test out DST handling code in cron(8). +Rule EU 2000 only - Dec 4 1:00u 1:00 S +Rule EU 2000 only - Dec 5 1:00u 0 - + # W-Eur differs from EU only in that W-Eur uses standard time. Rule W-Eur 1977 1980 - Apr Sun>=1 1:00s 1:00 S Rule W-Eur 1977 only - Sep lastSun 1:00s 0 - ----------------------------------------------------------------- This TZ manipulation was done on several machines for several dates and needs customization for those people to reproduce the setup, of course. But the idea should be clear: I want to arrange for my "personal" DST period to happen when it fits best in my test scenario and as many times a year as I want it to. :) There's no need to wait a whole year, as well as it would be dangerous and contrary to the test goal to manipulate the system clock. This manipulation can be installed together with a world or by means of zic(8) and cp(1): zic -d . edited_zonefile cp Europe/Berlin /etc/localtime Successful installation can be tested by some command like zdump -v /etc/localtime | grep `date '+%Y'` The test case cronjob and crontab look like this: ----------------------------------------------------------------- #!/bin/sh # test case cronjob, script file ~/bin/crontest.sh echo `date '+%d.%m.%Y %H:%M:%S'` "$# args: [$@]" | \ /usr/bin/logger -t crontest ----------------------------------------------------------------- ----------------------------------------------------------------- --- /etc/crontab 2001/01/06 21:45:44 1.1 +++ /etc/crontab 2001/01/06 22:02:32 @@ -22,3 +22,23 @@ # does nothing, if you have UTC cmos clock. # See adjkerntz(8) for details. 1,31 0-5 * * * root adjkerntz -a + +# ----- test scenario for cron DST extension -------------------- + +0 0-1 * * * root $HOME/bin/crontest.sh daily 0:00, 1:00 +0 1 * * * root $HOME/bin/crontest.sh daily 1:00 +0 1-2 * * * root $HOME/bin/crontest.sh daily 1:00, 2:00 +0 2 * * * root $HOME/bin/crontest.sh daily 2:00 +0 2-3 * * * root $HOME/bin/crontest.sh daily 2:00, 3:00 +0 3 * * * root $HOME/bin/crontest.sh daily 3:00 +0 3-4 * * * root $HOME/bin/crontest.sh daily 3:00, 4:00 +0 4 * * * root $HOME/bin/crontest.sh daily 4:00 + +2 1 * * * root $HOME/bin/crontest.sh daily 1:02 +2 2 * * * root $HOME/bin/crontest.sh daily 2:02 +2 3 * * * root $HOME/bin/crontest.sh daily 3:02 +2 4 * * * root $HOME/bin/crontest.sh daily 4:02 + +*/5 1-4 * * * root $HOME/bin/crontest.sh every 5 min @ 1:00 - 4:00 + +# ----- end of cron DST test ------------------------------------ ----------------------------------------------------------------- The modified cron is run like this: # tail -f /var/log/messages & # kill `cat /var/run/cron.pid` # cron -x sch & This will produce a whole lot of debugging output with cron's decision about scheduling. One might want to run this in a script(1) environment for later reference. What we (don't) see: When DST jumps happen to set the system clock (better: its localtime representation), cron won't notice. Jobs will miss or run twice. What we see: Manual correction like 'date 1315' at 12:15 and 'date 1615' at 17:15 will be recognized as "DST begins" and "DST ends". Special action is taken to catch up with the skipped over timeframe's jobs as well as to not again execute the repeatedly passed timeframe's jobs. This is what most users seem to expect when doing manual corrections. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 7:37:25 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DBBCC37B402; Sat, 20 Jan 2001 07:37:08 -0800 (PST) Received: (from ume@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KFb8799126; Sat, 20 Jan 2001 07:37:08 -0800 (PST) (envelope-from ume) Date: Sat, 20 Jan 2001 07:37:08 -0800 (PST) From: Message-Id: <200101201537.f0KFb8799126@freefall.freebsd.org> To: ume@FreeBSD.org, freebsd-bugs@FreeBSD.org, ume@FreeBSD.org Subject: Re: kern/24248: Broken getsockopt(IPV6_FW_GET) with IPv6 Firewall on FreeBSD 4.1-STABLE and 4.2-STABLE locks system Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Broken getsockopt(IPV6_FW_GET) with IPv6 Firewall on FreeBSD 4.1-STABLE and 4.2-STABLE locks system Responsible-Changed-From-To: freebsd-bugs->ume Responsible-Changed-By: ume Responsible-Changed-When: Sat Jan 20 07:35:43 PST 2001 Responsible-Changed-Why: I'll take a look this pr. http://www.freebsd.org/cgi/query-pr.cgi?pr=24248 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 8:12: 1 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 73DE937B401; Sat, 20 Jan 2001 08:11:45 -0800 (PST) Received: (from johan@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KGBjt04248; Sat, 20 Jan 2001 08:11:45 -0800 (PST) (envelope-from johan) Date: Sat, 20 Jan 2001 08:11:45 -0800 (PST) From: Message-Id: <200101201611.f0KGBjt04248@freefall.freebsd.org> To: johan@FreeBSD.org, freebsd-bugs@FreeBSD.org, archie@FreeBSD.org Subject: Re: kern/24465: Will process packets not for this host if using netgraph and ip forwarding. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Will process packets not for this host if using netgraph and ip forwarding. Responsible-Changed-From-To: freebsd-bugs->archie Responsible-Changed-By: johan Responsible-Changed-When: Sat Jan 20 08:10:53 PST 2001 Responsible-Changed-Why: Over to netgraph maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=24465 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 10: 0:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2E41F37B401 for ; Sat, 20 Jan 2001 10:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KI01L15396; Sat, 20 Jan 2001 10:00:01 -0800 (PST) (envelope-from gnats) Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id B833737B400 for ; Sat, 20 Jan 2001 09:51:27 -0800 (PST) Received: (qmail 12842 invoked by uid 0); 20 Jan 2001 17:51:25 -0000 Received: from p3ee21650.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.80) by mail.gmx.net (mail04) with SMTP; 20 Jan 2001 17:51:25 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA21390 for FreeBSD-gnats-submit@freebsd.org; Sat, 20 Jan 2001 18:48:40 +0100 Message-Id: <20010120184840.M253@speedy.gsinet> Date: Sat, 20 Jan 2001 18:48:40 +0100 From: Gerhard Sittig To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: gnu/24487: [PATCH] libdialog's no/yes box jumps buttons around Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24487 >Category: gnu >Synopsis: [PATCH] libdialog's no/yes box jumps buttons around >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jan 20 10:00:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Gerhard Sittig >Release: FreeBSD 5.0-CURRENT i386 >Organization: System Defenestrators Inc. >Environment: mostly sysinstall(8), but could be any application making use of the newly introduced no/yes question box in libdialog I'm not certain of the above classification: It's a FreeBSD customization in GNU derived code, and it's sysinstall annoying users thus leaving an impression at first encounter we don't want to ... :> >Description: In mid December libdialog was extended to not only have a Yes/No question box, but to have another box with No as the default answer (called No/Yes box). This was done so sysinstall(8) could suggest better suited answers when asking security related questions (the reasoning I understand for this feature, but I could be wrong). While I welcome being offered more appropriate defaults when questions arise at installation time, I'm really annoyed by the need to look twice which button has what meaning in this very moment. I would *always* expect the left one to be the "yes" button while the right one is labeled "no". Any other arrangement will dazzle users, and when these arrangements differ between different questions it's really easy to provide the wrong answer and regretting right afterwards (I've been bitten myself, that's when I decided the current state is not acceptable:). >How-To-Repeat: just use sysinstall (maybe from recent install floppies) or use the below test sequence without applying the patch >Fix: Apply the patch cited below. It is written quite aggressivly concerning the TRUE/FALSE vs 0/1 thingy. I understand that the button 0 and 1 numbering is not meant to read boolean but more of an index. But I was ready to misuse the fact that it could be used this way (keeping in mind the "reversed" boolean meaning with YES being 0 and NO being 1). Feel free to tell me when you want a more conservative patch (but the libdialog code is already guilty of "hardcoding" TRUE to 1 and FALSE to 0 which I feel to be at least dangerous if not wrong). I don't care very much that the dialog gets redrawn on every key press. They should happen quite rarely and this construction allows for elimination of the print_button code duplicates. Honestly I don't expect very much key presses apart from TAB, SPC, the Y and N shortcuts, and their equivalents. All of them need a (kind of) redraw. Any other keypress means that the user is misguided anyway. :> # 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: # # aggressive.diff # echo x - aggressive.diff sed 's/^X//' >aggressive.diff << 'END-of-aggressive.diff' XIndex: yesno.c X=================================================================== XRCS file: /CVSREPO/fbsd/src/gnu/lib/libdialog/yesno.c,v Xretrieving revision 1.12 Xdiff -u -r1.12 yesno.c X--- yesno.c 2000/12/14 02:35:22 1.12 X+++ yesno.c 2001/01/20 17:45:08 X@@ -50,7 +50,7 @@ X static int X dialog_yesno_proc(unsigned char *title, unsigned char *prompt, int height, int width, int yesdefault) X { X- int i, j, x, y, key = 0, button = 0; X+ int i, j, x, y, key, button; X WINDOW *dialog; X char *tmphlp; X X@@ -114,11 +114,15 @@ X X x = width/2-10; X y = height-2; X- print_button(dialog, yesdefault ? " No " : " Yes ", y, x+13, FALSE); X- print_button(dialog, yesdefault ? " Yes " : " No ", y, x, TRUE); X- wrefresh(dialog); X X+ /* preset button 0 or 1 for YES or NO as the default */ X+ key = 0; X+ button = !yesdefault; X while (key != ESC) { X+ print_button(dialog, " No ", y, x+13, button); X+ print_button(dialog, " Yes " , y, x , !button); X+ wrefresh(dialog); X+ X key = wgetch(dialog); X switch (key) { X case 'Y': X@@ -137,27 +141,15 @@ X case KEY_DOWN: X case KEY_LEFT: X case KEY_RIGHT: X- if (!button) { X- button = 1; /* Indicates "No" button is selected */ X- print_button(dialog, yesdefault ? " Yes " : " No ", y, x, FALSE); X- print_button(dialog, yesdefault ? " No " : " Yes ", y, x+13, TRUE); X- } X- else { X- button = 0; /* Indicates "Yes" button is selected */ X- print_button(dialog, yesdefault ? " No " : " Yes ", y, x+13, FALSE); X- print_button(dialog, yesdefault ? " Yes " : " No ", y, x, TRUE); X- } X- wrefresh(dialog); X+ button = !button; X+ /* redrawn at the loop's entry */ X break; X case ' ': X case '\r': X case '\n': X delwin(dialog); X restore_helpline(tmphlp); X- if (yesdefault) X- return button; X- else X- return !button; X+ return button; X case ESC: X break; X case KEY_F(1): END-of-aggressive.diff exit The patch was tested the following way: cvs co libdialog cd libdialog patch yesno.c < /path/to/aggressive.diff make cd TESTS cc -O -pipe -Wall -Wstrict-prototypes -static -I.. -L.. yesno.c -ldialog -lncurses -o yesno ./yesno The static linking and not using TESTS/Makefile saved me from installing the -CURRENT libdialog stuff on the -STABLE machine I did this modification on. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 11: 0:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DF0B037B698 for ; Sat, 20 Jan 2001 11:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KJ01N21851; Sat, 20 Jan 2001 11:00:01 -0800 (PST) (envelope-from gnats) Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id D90D337B401 for ; Sat, 20 Jan 2001 10:50:40 -0800 (PST) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id f0KIobC27519 for ; Sat, 20 Jan 2001 19:50:39 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.11.0/8.11.0) with ESMTP id f0KIobS07232 for ; Sat, 20 Jan 2001 19:50:37 +0100 (MET) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.2/8.11.2/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id f0KIobB30674 for ; Sat, 20 Jan 2001 19:50:37 +0100 (CET) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.2/8.11.2/alaska [ $Revision: 1.5 ]) id f0KIoaB92829; Sat, 20 Jan 2001 19:50:36 +0100 (CET) Message-Id: <200101201850.f0KIoaB92829@alaska.cert.siemens.de> Date: Sat, 20 Jan 2001 19:50:36 +0100 (CET) From: Udo Schweigert Reply-To: ust@cert.siemens.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: conf/24490: Missing entry in /etc/newsyslog.conf Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24490 >Category: conf >Synopsis: Subject: Missing entry in /etc/newsyslog.conf >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jan 20 11:00:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Udo Schweigert >Release: FreeBSD 4.2-STABLE i386 >Organization: >Environment: -current and -stable >Description: /etc/syslog.conf now includes an optional entry for /var/log/console but /etc/newsyslog.conf does not. >How-To-Repeat: >Fix: --- /usr/src/etc/newsyslog.conf Wed Sep 20 04:43:46 2000 +++ ./newsyslog.conf Sat Jan 20 19:49:10 2001 @@ -10,6 +10,7 @@ /var/log/sendmail.st 644 10 * 168 B /var/log/messages 644 5 100 * Z /var/log/all.log 600 7 * @T00 Z +/var/log/console 600 7 * @T00 Z /var/log/slip.log 600 3 100 * Z /var/log/ppp.log 600 3 100 * Z /var/log/security 600 10 100 * Z >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 12:10:28 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5A26737B400 for ; Sat, 20 Jan 2001 12:10:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KKA6r30809; Sat, 20 Jan 2001 12:10:06 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 12:10:06 -0800 (PST) Message-Id: <200101202010.f0KKA6r30809@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Martin Birgmeier Subject: Re: kern/24092: Disk data corruption using FreeBSD_4_2_0_RELEASE Reply-To: Martin Birgmeier Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24092; it has been noted by GNATS. From: Martin Birgmeier To: freebsd-gnats-submit@FreeBSD.org, Martin.Birgmeier@aon.at Cc: Subject: Re: kern/24092: Disk data corruption using FreeBSD_4_2_0_RELEASE Date: Sat, 20 Jan 2001 21:00:31 +0100 This indeed seems to have been a bios problem. No more data corruption since bios update. Someone please close this PR. -- Martin Birgmeier Vienna Austria To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 12:40:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 752A837B402 for ; Sat, 20 Jan 2001 12:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KKe1Q32431; Sat, 20 Jan 2001 12:40:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2766637B400 for ; Sat, 20 Jan 2001 12:39:59 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KKdxq32408; Sat, 20 Jan 2001 12:39:59 -0800 (PST) (envelope-from nobody) Message-Id: <200101202039.f0KKdxq32408@freefall.freebsd.org> Date: Sat, 20 Jan 2001 12:39:59 -0800 (PST) From: babkin@FreeBSD.org To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: bin/24494: daylight time change support in cron Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24494 >Category: bin >Synopsis: daylight time change support in cron >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jan 20 12:40:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Sergey Babkin >Release: 5.0-current >Organization: >Environment: >Description: Cron may skip or repeat the jobs falling into the interval that gets missing or duplicated during the time change to daylight saving or back. I'll commit my change directly to -current, here is description and test example for tracking purposes: Now the jobs run as intuitively expected. If a job falls into time interval that disappears during switch from standard time (ST) to daylight saving time (DST) or is duplicated during the reverse switch, then it's handled in one of 2 ways. The jobs that run every hour work as before, they skip the skipped hour or run in the added hour as usual. But the jobs that run less frequently are executed exactly once, they are not skipped nor executed twice (unless cron is restarted or the user's crontab is changed during such a time interval). Test crontab: 0 1 * * * /home/guest/testdst at one OCLOCK 0 0-1 * * * /home/guest/testdst at zero to one range OCLOCK 0 2 * * * /home/guest/testdst at two OCLOCK 0 1-2 * * * /home/guest/testdst at one to two range OCLOCK 0 3 * * * /home/guest/testdst at three OCLOCK 1 1 * * * /home/guest/testdst at one 1 0-1 * * * /home/guest/testdst at zero to one range 1 2 * * * /home/guest/testdst at two 1 1-2 * * * /home/guest/testdst at one to two range 1 3 * * * /home/guest/testdst at three test script testdst: #!/bin/sh date "+%D %T %Z testdst $* " >> /home/guest/dst.log (trace excerpt starts at 1:55 EST) 04/02/00 03:00:00 EDT testdst at two OCLOCK 04/02/00 03:00:00 EDT testdst at three OCLOCK 04/02/00 03:01:01 EDT testdst at two 04/02/00 03:01:01 EDT testdst at three (trace excerpt ends at 3:05 EDT) (trace excerpt starts at 0:55 EDT) 10/29/00 01:00:00 EDT testdst at zero to one range OCLOCK 10/29/00 01:00:00 EDT testdst at one OCLOCK 10/29/00 01:00:01 EDT testdst at one to two range OCLOCK 10/29/00 01:01:00 EDT testdst at zero to one range 10/29/00 01:01:00 EDT testdst at one 10/29/00 01:01:00 EDT testdst at one to two range 10/29/00 01:00:00 EST testdst at zero to one range OCLOCK 10/29/00 01:00:00 EST testdst at one to two range OCLOCK 10/29/00 01:01:00 EST testdst at zero to one range 10/29/00 01:01:00 EST testdst at one to two range 10/29/00 02:00:00 EST testdst at one to two range OCLOCK 10/29/00 02:00:00 EST testdst at two OCLOCK 10/29/00 02:01:02 EST testdst at two 10/29/00 02:01:02 EST testdst at one to two range 10/29/00 03:00:00 EST testdst at three OCLOCK 10/29/00 03:01:00 EST testdst at three (trace excerpt ends at 3:05 EST) >How-To-Repeat: >Fix: will commit to -current >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 13: 5:58 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5DAA437B402; Sat, 20 Jan 2001 13:05:41 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KL5fu36498; Sat, 20 Jan 2001 13:05:41 -0800 (PST) (envelope-from dwmalone) Date: Sat, 20 Jan 2001 13:05:41 -0800 (PST) From: Message-Id: <200101202105.f0KL5fu36498@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, phk@FreeBSD.org Subject: Re: conf/24490: Subject: Missing entry in /etc/newsyslog.conf Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Subject: Missing entry in /etc/newsyslog.conf Responsible-Changed-From-To: freebsd-bugs->phk Responsible-Changed-By: dwmalone Responsible-Changed-When: Sat Jan 20 13:04:41 PST 2001 Responsible-Changed-Why: Over to the console log's creator. http://www.freebsd.org/cgi/query-pr.cgi?pr=24490 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 13: 7:15 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D1F1037B402; Sat, 20 Jan 2001 13:06:58 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KL6we36667; Sat, 20 Jan 2001 13:06:58 -0800 (PST) (envelope-from dwmalone) Date: Sat, 20 Jan 2001 13:06:58 -0800 (PST) From: Message-Id: <200101202106.f0KL6we36667@freefall.freebsd.org> To: Martin.Birgmeier@aon.at, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/24092: Disk data corruption using FreeBSD_4_2_0_RELEASE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Disk data corruption using FreeBSD_4_2_0_RELEASE State-Changed-From-To: open->closed State-Changed-By: dwmalone State-Changed-When: Sat Jan 20 13:06:07 PST 2001 State-Changed-Why: Closed at request of submitter. http://www.freebsd.org/cgi/query-pr.cgi?pr=24092 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 13:35: 6 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1BEDD37B401; Sat, 20 Jan 2001 13:34:50 -0800 (PST) Received: (from babkin@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0KLYoi39147; Sat, 20 Jan 2001 13:34:50 -0800 (PST) (envelope-from babkin) Date: Sat, 20 Jan 2001 13:34:50 -0800 (PST) From: Message-Id: <200101202134.f0KLYoi39147@freefall.freebsd.org> To: babkin@FreeBSD.org, babkin@FreeBSD.org, freebsd-bugs@FreeBSD.org, babkin@FreeBSD.org Subject: Re: bin/24494: daylight time change support in cron Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: daylight time change support in cron State-Changed-From-To: open->closed State-Changed-By: babkin State-Changed-When: Sat Jan 20 13:30:43 PST 2001 State-Changed-Why: Committed the changes to -current. Responsible-Changed-From-To: freebsd-bugs->babkin Responsible-Changed-By: babkin Responsible-Changed-When: Sat Jan 20 13:30:43 PST 2001 Responsible-Changed-Why: Assigned PR to myself as I did the commit in CVS. . http://www.freebsd.org/cgi/query-pr.cgi?pr=24494 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 16:10:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 55C1F37B401 for ; Sat, 20 Jan 2001 16:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0L0A1456171; Sat, 20 Jan 2001 16:10:01 -0800 (PST) (envelope-from gnats) Received: from prserv.net (out1.prserv.net [32.97.166.31]) by hub.freebsd.org (Postfix) with ESMTP id 802F137B400 for ; Sat, 20 Jan 2001 16:09:26 -0800 (PST) Received: from dell.mynet (slip-32-102-104-81.nc.us.prserv.net[32.102.104.81]) by prserv.net (out1) with ESMTP id <2001012100092020103isofge>; Sun, 21 Jan 2001 00:09:21 +0000 Received: from dumas.mynet (dumas.mynet [192.168.0.1]) by dell.mynet (8.9.3/8.9.3) with ESMTP id TAA30767 for ; Sat, 20 Jan 2001 19:09:16 -0500 (EST) Received: from fs.mynet ([192.168.0.27]) by dumas.mynet (8.9.3/8.8.7) with ESMTP id SAA00741 for ; Sat, 20 Jan 2001 18:43:13 -0500 Message-Id: Date: Sat, 20 Jan 2001 18:43:36 -0500 (EST) From: Dan Poirier To: Subject: conf/24495: Default /etc/printcap refers to wrong handbook chapter Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24495 >Category: conf >Synopsis: Default /etc/printcap refers to wrong handbook chapter >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 20 16:10:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Dan Poirier >Release: FreeBSD 4.2-RELEASE i386 >Organization: Very little >Environment: >Description: The default /etc/printcap in 4.2 RELEASE includes these lines: # Do also refer to section 7 (Printing) of the handbook. A local copy # can be found under /usr/share/doc/handbook/handbook.{html,latin1}. Checking the handbook, printing is now covered under chapter 9, not chapter 7. >How-To-Repeat: >Fix: Suggested patch for /usr/src/etc/printcap to remove the explicit chapter number (since it might change again): --- etc/printcap Fri Aug 27 19:23:43 1999 +++ etc/printcap.new Sat Jan 20 18:16:04 2001 @@ -16,7 +16,7 @@ # format. If you don't have a PostScript(tm) printer, don't panic, # but do also install the "ghostscript" package. # -# Do also refer to section 7 (Printing) of the handbook. A local copy +# Do also refer to the Printing chapter of the handbook. A local copy # can be found under /usr/share/doc/handbook/handbook.{html,latin1}. # # Banner pages are now suppressed by default. Remove the :sh: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 16:20:58 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1C84137B400; Sat, 20 Jan 2001 16:20:42 -0800 (PST) Received: (from kris@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0L0Kgx56919; Sat, 20 Jan 2001 16:20:42 -0800 (PST) (envelope-from kris) Date: Sat, 20 Jan 2001 16:20:42 -0800 (PST) From: Message-Id: <200101210020.f0L0Kgx56919@freefall.freebsd.org> To: kris@FreeBSD.org, freebsd-bugs@FreeBSD.org, jkh@FreeBSD.org Subject: Re: gnu/24487: [PATCH] libdialog's no/yes box jumps buttons around Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: [PATCH] libdialog's no/yes box jumps buttons around Responsible-Changed-From-To: freebsd-bugs->jkh Responsible-Changed-By: kris Responsible-Changed-When: Sat Jan 20 16:20:17 PST 2001 Responsible-Changed-Why: jkh committed the change to which this refers http://www.freebsd.org/cgi/query-pr.cgi?pr=24487 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 17:10:21 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 312FE37B400 for ; Sat, 20 Jan 2001 17:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0L1A3u61861; Sat, 20 Jan 2001 17:10:03 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 17:10:03 -0800 (PST) Message-Id: <200101210110.f0L1A3u61861@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Crist J. Clark" Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: "Crist J. Clark" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: "Crist J. Clark" To: Dag-Erling Smorgrav Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: Sat, 20 Jan 2001 17:01:55 -0800 On Fri, Jan 19, 2001 at 11:09:24PM +0100, Dag-Erling Smorgrav wrote: > "Crist J. Clark" writes: > > On Fri, Jan 19, 2001 at 12:32:53PM +0100, Dag-Erling Smorgrav wrote: > > > It should also log a message if the hostname changes. > > Should that be a responsibility of syslogd(8) or hostname(1)? > > I meant syslogd(8), but putting it in hostname(1) might makes sense, > except that hostname(1) is not the only way to set the hostname > ('sysctl -w kern.hostname=foo' is another) How about just logging a sethostname(3) call? But anyway, syslogd(8) does not track the state of any other system parameters, I think asking syslogd(8) to notice a change in the hostname on its own in a real-time fashion is beyond its scope. That said, I agree that syslogd(8) making a note when its own idea of the hostname changes would be useful. If one is analyzing logs, an entry indicating that messages from a given machine no longer will be labeled as coming from 'foo' but 'foobar' would be very helpful. Patches, patches, patches: --- usr.sbin/syslogd/syslogd.c 2001/01/18 08:06:34 1.1 +++ usr.sbin/syslogd/syslogd.c 2001/01/21 00:55:53 1.3 @@ -318,7 +318,7 @@ struct sockaddr_un sunx, fromunix; struct sockaddr_storage frominet; FILE *fp; - char *p, *hname, line[MAXLINE + 1]; + char *hname, line[MAXLINE + 1]; struct timeval tv, *tvp; struct sigaction sact; sigset_t mask; @@ -395,12 +395,6 @@ consfile.f_type = F_CONSOLE; (void)strcpy(consfile.f_un.f_fname, ctty + sizeof _PATH_DEV - 1); - (void)gethostname(LocalHostName, sizeof(LocalHostName)); - if ((p = strchr(LocalHostName, '.')) != NULL) { - *p++ = '\0'; - LocalDomain = p; - } else - LocalDomain = ""; (void)strcpy(bootfile, getbootfile()); (void)signal(SIGTERM, die); (void)signal(SIGINT, Debug ? die : SIG_IGN); @@ -1340,10 +1334,23 @@ char cline[LINE_MAX]; char prog[NAME_MAX+1]; char host[MAXHOSTNAMELEN+1]; + char oldLocalHostName[MAXHOSTNAMELEN+1]; + char hostMsg[2*(MAXHOSTNAMELEN+1)+40]; dprintf("init\n"); /* + * Load hostname (may have changed) + */ + strncpy(oldLocalHostName, LocalHostName, sizeof(LocalHostName)); + (void)gethostname(LocalHostName, sizeof(LocalHostName)); + if ((p = strchr(LocalHostName, '.')) != NULL) { + *p++ = '\0'; + LocalDomain = p; + } else + LocalDomain = ""; + + /* * Close all open log files. */ Initialized = 0; @@ -1492,6 +1499,17 @@ logmsg(LOG_SYSLOG|LOG_INFO, "syslogd: restart", LocalHostName, ADDDATE); dprintf("syslogd: restarted\n"); + /* + * Log a change in hostname, but only on a restart + */ + if ((signo != 0) && + (strncmp(oldLocalHostName, LocalHostName, sizeof(LocalHostName)) != 0)) { + snprintf(hostMsg, sizeof(hostMsg), + "syslogd: hostname changed, \"%s\" to \"%s\"", + oldLocalHostName, LocalHostName); + logmsg(LOG_SYSLOG|LOG_INFO, hostMsg, LocalHostName, ADDDATE); + dprintf("%s\n", hostMsg); + } } /* -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 19:20:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9EB8737B402 for ; Sat, 20 Jan 2001 19:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0L3K2r74551; Sat, 20 Jan 2001 19:20:02 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 19:20:02 -0800 (PST) Message-Id: <200101210320.f0L3K2r74551@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Gerhard Sittig Subject: Re: conf/22859: rc.network should start ipf/ipnat AFTER ppp (like ipfw/natd) Reply-To: Gerhard Sittig Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/22859; it has been noted by GNATS. From: Gerhard Sittig To: eliyanah@techie.com Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: conf/22859: rc.network should start ipf/ipnat AFTER ppp (like ipfw/natd) Date: Sat, 20 Jan 2001 22:29:38 +0100 On Tue, Nov 14, 2000 at 21:38 -0800, eliyanah@techie.com wrote: > > >Description: > If ipfilter, ipnat, and ppp are enabled in rc.conf, rc.network > will start ipfilter and ipnat BEFORE user ppp, which does not > work if you are using ipf/ipnat with tun0. rc.network > correctly starts ipfw/natd AFTER ppp, and even states "Start > user ppp if required. This must happen before natd." What is > true for ipfw/natd is also true for ipf/ipnat - User ppp needs > to be started BEFORE ipf/ipnat for proper operation. I dare to disagree. :) AFAIK the only prerequisite may be that the *interface* has to be available when the filter / natd starts up. I'm not positive about the details, but since I did the rc.network stuff for hooking ipf in I'm absolutely sure that it works for me on several machines. :> > >Fix: > Change rc.network so ipf/ipnat are started after ppp. Starting ipf this early was done on purpose. That's why there is so big a comment in rc.network. I've been through this in Linux land: ipfwadm (the filter when kernel 2.0 was active) couldn't work on interfaces that haven't been *up* yet. This changed with ipchains (fitting kernel 2.2) which can load the filter and afterwards config and up the interface. I like this better since *every* action with this interface is done at a time when there's an established ruleset. I tried to discuss this in some freebsd-* list (don't know which one it was) and to get myself clear if there's a similar issue with FreeBSD and ipfw / ipf. The result is that I started ipf as soon as I could (read: before any outside communication can occur). And I never had any problem with it. Nor did others that I could hear of. I can see two (or three, depends on your configuration) solutions which keep the early ipf startup and possibly solve your problem: - compile the tun interfaces into your kernel instead of using modules (it's what I have and I never experienced that NAT wouldn't work -- but it could be due to the next item, too) - _sync_ your ipf/ipnat setup after ppp is up (it's what I do in ppp.link{up,down} since I get IPs assigned dynamically), see "man 8 ipf" and the -y option - make sure your interfaces are there when they're needed, which could be achieved with some lines just before calling ipf: for IF in ${ipfilter_interfaces}; do < /dev/$IF # or: dd if=/dev/$IF of=/dev/null count=0 done I feel when moving the invocation of ipf/ipnat behind ppp is the solution for you, you only see the effect of ppp working with tun0 -- tun interfaces magically jump into existence when they are opened. So the third item of the above would be a solution for you. And when it works with other NIFs besides tunN, it could be extended for any case where NIC drivers are loaded as modules. Although the second item would be the simplest: Insert some case ${ipfilter_enable} in [Yy][Ee][Ss]) /sbin/ipf -y;; esac before or after the ipfw code in rc.network. But to repeat it: I never had to do this, something in your setup must be different and you don't describe it. Do you use modules? virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Jan 20 19:40:20 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 791D537B402 for ; Sat, 20 Jan 2001 19:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0L3e2j75681; Sat, 20 Jan 2001 19:40:02 -0800 (PST) (envelope-from gnats) Date: Sat, 20 Jan 2001 19:40:02 -0800 (PST) Message-Id: <200101210340.f0L3e2j75681@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Dag-Erling Smorgrav Subject: Re: bin/24444: syslogd(8) does not update hostname Reply-To: Dag-Erling Smorgrav Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/24444; it has been noted by GNATS. From: Dag-Erling Smorgrav To: cjclark@alum.mit.edu Cc: FreeBSD-gnats-submit@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/24444: syslogd(8) does not update hostname Date: 21 Jan 2001 04:32:33 +0100 "Crist J. Clark" writes: > How about just logging a sethostname(3) call? Still doesn't help. There are (at least) two different ways of setting the hostname, one being a syscall and the other being a sysctl. One could of course have the kernel print a message to the console about it, syslogd(8) would pick that up. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message