From owner-freebsd-hackers Sun Oct 24 0: 7:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from area51.fremont.ca.us (adsl-63-195-147-14.dsl.scrm01.pacbell.net [63.195.147.14]) by hub.freebsd.org (Postfix) with ESMTP id 8C97E1505F; Sun, 24 Oct 1999 00:07:35 -0700 (PDT) (envelope-from mharo@area51.fremont.ca.us) Received: (from mharo@localhost) by area51.fremont.ca.us (8.9.3/8.9.2) id AAA21080; Sun, 24 Oct 1999 00:07:29 -0700 (PDT) (envelope-from mharo) Date: Sun, 24 Oct 1999 00:07:29 -0700 From: Michael Haro To: Wes Peters Cc: freebsd-hackers@freebsd.org, cvs-committers@freebsd.org, andrews@technologist.com Subject: Re: FreeBSD xearth markers file Message-ID: <19991024000728.A21055@FreeBSD.org> Reply-To: mharo@freebsd.org References: <38129FF4.6F751203@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38129FF4.6F751203@softweyr.com>; from Wes Peters on Sat, Oct 23, 1999 at 11:58:12PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add it separately, isn't it freebsd.committer.markers or developers or something like that? Michael On Sat, Oct 23, 1999 at 11:58:12PM -0600, Wes Peters wrote: > OK, I collected several more addresses at FreeBSD Con and it's time to get > this into CVS and out of my hands. ;^) > > Should I overwrite ports/astro/xearth/files/freebsd.core.markers with this > monster, or add it separately? > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 24 2:12:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id F145B14EEA; Sun, 24 Oct 1999 02:12:23 -0700 (PDT) (envelope-from cc@137.org) Received: from ameslab.gov (friley-160-235.res.iastate.edu [129.186.160.235]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 2CFA6FC; Sun, 24 Oct 1999 04:11:56 -0500 (CDT) Message-ID: <3812CD5C.1E990C73@ameslab.gov> Date: Sun, 24 Oct 1999 04:11:56 -0500 From: Chris Csanady X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, ru, ja, ko MIME-Version: 1.0 To: freebsd-smp@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: IO APIC misdirecting irq (Re: SMP/interrupt problems..) References: <381159FF.D38E76FD@ameslab.gov> <38115BD9.6B8BE3BA@ameslab.gov> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the post to both lists--the original message probably belonged on freebsd-smp. Anyways, please follow up there only. I have tracked down the problem with the Megaraid controller in SMP, and it seems it is due to an irq being misrouted. While the controller thinks it is on irq 11, all the interrupts are actually going to apic irq 17. I have confirmed this by hardwiring amr0's interrupt to be irq 17--in which case it works perfectly. :) It is not clear to me whether the irq should or should not be routed to irq 17 though--only that it is what is happening with the current configuration. Does anyone know in particular how this should work? (Or better yet, have a fix? ;) It is kind of weird, because the amr0 controller is actually the same device as the pci-pci bridge, just a different function. So, I assume it is just on the host bus. In any case, even though the irq/int pin match in the mptable, the device (slot) does not. :\ I have included my dmesg, pciconf output, and mptable output. The device in question is the vendor=0x8086, dev=0x1960. Anyone have any ideas? Chris Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #14: Sat Oct 23 19:15:37 CDT 1999 ccsanady@friley-160-235.res.iastate.edu:/usr/src/sys/compile/EUROPA Calibrating clock(s) ... TSC clock: 198655681 Hz, i8254 clock: 1193129 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium Pro (198.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00322000 - 0x07ff7fff, 130899968 bytes (31958 pages) avail memory = 126820352 (123848K bytes) Programming 24 pins in IOAPIC #0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00fd970 bios32: Entry = 0xfd980 (c00fd980) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xd9a1 pnpbios: Found PnP BIOS data at 0xc00fa170 pnpbios: Entry = f0000:a270 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc0306000. Pentium Pro MTRR support enabled SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) 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=12378086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x8086, dev=0x1229, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[0]: type 1, range 32, base ffbae000, size 12 map[1]: type 1, range 32, base 0000ff40, size 5 map[2]: type 1, range 32, base fef00000, size 20 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[4]: type 1, range 32, base 0000ffa0, size 4 found-> vendor=0x8086, dev=0x7020, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[4]: type 1, range 32, base 0000ff80, size 5 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x9004, dev=0x8078, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[0]: type 1, range 32, base 0000f400, size 8 map[1]: type 1, range 32, base ffbaf000, size 12 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x1000, dev=0x000f, revid=0x14 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 1, range 32, base 0000f800, size 8 map[1]: type 1, range 32, base ffbea800, size 8 map[2]: type 1, range 32, base ffbe8000, size 12 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x1000, dev=0x000f, revid=0x14 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 1, range 32, base 0000fc00, size 8 map[1]: type 1, range 32, base ffbeac00, size 8 map[2]: type 1, range 32, base ffbe9000, size 12 found-> vendor=0x8086, dev=0x0960, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=1 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x1960, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base ffbd0000, size 16 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x109e, dev=0x0350, revid=0x12 class=04-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[0]: type 1, range 32, base ffbeb000, size 12 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[0]: type 1, range 32, base ffbec000, size 14 map[1]: type 1, range 32, base ff000000, size 23 pci0: on pcib0 fxp0: irq 18 at device 6.0 on pci0 fxp0: Ethernet address 00:a0:c9:55:9e:4f bpf: fxp0 attached isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ10, B: IRQ11, C: IRQ9, D: IRQ9 MB0: , MB1: Trying Read_Port at 203 CSC0000: start dependant CSC0000: adding dma mask 0x2 CSC0000: adding dma mask 0x9 CSC0000: adding irq mask 0x20 CSC0000: adding io range 0x534-0x537, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x22f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xa CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0x9aa0 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x26f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0x9aa0 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x3fb, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x30f, size=0x10, align=0x20 CSC0000: end dependant CSC0001: start dependant CSC0001: adding io range 0x200-0x207, size=0x8, align=0x8 CSC0001: start dependant CSC0001: adding io range 0x208-0x20f, size=0x8, align=0x8 CSC0001: end dependant CSC0010: adding io range 0x120-0xfff, size=0x8, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x200 CSC0003: adding io range 0x330-0x331, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x9a00 CSC0003: adding io range 0x300-0x3f9, size=0x2, align=0x8 CSC0003: end dependant isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=00 status0=ff status1=ff chip1: irq 9 at device 7.2 on pci0 ahc0: irq 17 at device 9.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 411 instructions downloaded ncr0: irq 16 at device 11.0 on pci0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM ncr1: irq 16 at device 11.1 on pci0 ncr1: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr1: single-ended, open drain IRQ driver, using on-chip SRAM using shared irq16. pcib1: at device 15.0 on pci0 pci1: on pcib1 amr0: irq 11 at device 15.1 on pci0 amr0: firmware GH6B bios 1.41 32MB memory, chipset 61 amrd0: on amr0 amrd0: 1553MB (3180544 sectors), state 0x2 properties 0x1 Creating DISK amrd0 amrd1: on amr0 amrd1: 3072MB (6291456 sectors), state 0x2 properties 0x0 Creating DISK amrd1 bktr0: irq 18 at device 17.0 on pci0 using shared irq18. iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicbus: iic devclass not found smbus0: on bti2c0 smbus: smb devclass not found brooktree0: PCI bus latency is 136. bktr0: buffer size 3555328, addr 0x5000000 bktr: GPIO is 0x003ffffb bktr0: Hauppauge Model 56131 E Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. vga-pci0: irq 19 at device 19.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 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 b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 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, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 06 40 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: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 sio0: irq maps: 0x8063 0x8073 0x8063 0x8063 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1: irq maps: 0x8063 0x806b 0x8063 0x8063 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 pcm: setmap 40000, ff00; 0xc88d3000 -> 40000 pcm: setmap 50000, ff00; 0xc88e3000 -> 50000 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x120-0x127 on isa0 unknown2: at port 0x330-0x331 irq 9 on isa0 SMP: enabled INTs: 1, 3, 4, 5, 6, 11, 12, 14, 16, 17, 18, apic_imen: 0x00f8a785 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 1:00c4fe3f 0..196=197 cylinders, 0..254=255 heads, 1..63=63 sectors 2:0186fe3f 0..390=391 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: routing 8254 via 8259 on pin 0 bpf: lo0 attached Linux-ELF exec handler installed SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff ata0: master: success setting up WDMA2 mode on PIIX4 chip ad0: piomode=4 dmamode=2 udmamode=2 ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, DMA Creating DISK ad0 Creating DISK wd0 Waiting 2 seconds for SCSI devices to settle [scsi device probing deleted..] chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00 fxp0@pci0:6:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x02 hdr=0x00 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00 ata-pci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x00 chip1@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x70208086 rev=0x01 hdr=0x00 ahc0@pci0:9:0: class=0x010000 card=0x00000000 chip=0x80789004 rev=0x00 hdr=0x00 ncr0@pci0:11:0: class=0x010000 card=0x87601092 chip=0x000f1000 rev=0x14 hdr=0x00 ncr1@pci0:11:1: class=0x010000 card=0x87601092 chip=0x000f1000 rev=0x14 hdr=0x00 pcib1@pci0:15:0: class=0x060400 card=0x00000000 chip=0x09608086 rev=0x03 hdr=0x01 amr0@pci0:15:1: class=0x010000 card=0x0466101e chip=0x19608086 rev=0x03 hdr=0x00 bktr0@pci0:17:0: class=0x040000 card=0x00000000 chip=0x0350109e rev=0x12 hdr=0x00 vga-pci0@pci0:19:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f80f0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x10 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f8100 signature: 'PCMP' base table length: 260 version: 1.4 checksum: 0x30 OEM ID: 'INTEL ' Product ID: 'PR440FX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 24 local APIC address: 0xfec08000 extended table length: 120 extended table checksum: 15 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 1 9 0xfbff 12 0x11 AP, usable 6 1 9 0xfbff -- Bus: Bus ID Type 0 PCI 1 PCI 18 ISA -- I/O APICs: APIC ID Version State Address 13 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 18 0 13 0 INT active-hi edge 18 1 13 1 INT active-hi edge 18 3 13 3 INT active-hi edge 18 4 13 4 INT active-hi edge 18 5 13 5 INT active-hi edge 18 6 13 6 INT active-hi edge 18 7 13 7 INT active-hi edge 18 8 13 8 INT active-hi edge 18 12 13 12 INT active-hi edge 18 14 13 14 INT active-hi edge 18 15 13 15 INT active-lo level 0 19:A 13 19 INT active-lo level 0 17:A 13 18 INT active-lo level 0 11:A 13 16 INT active-lo level 0 9:A 13 17 INT active-lo level 0 6:A 13 18 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 18 0 255 0 NMI active-hi edge 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- bus ID: 0 address type: memory address address base: 0xd4000 address range: 0x4000 -- bus ID: 0 address type: memory address address base: 0xd8000 address range: 0x4000 -- bus ID: 0 address type: memory address address base: 0xdc000 address range: 0x4000 -- bus ID: 0 address type: memory address address base: 0xa0000 address range: 0x20000 -- bus ID: 0 address type: memory address address base: 0x8000000 address range: 0xf8000000 -- bus ID: 0 address type: I/O address address base: 0x0 address range: 0x10000 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=3 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 24 15:59: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0073715141; Sun, 24 Oct 1999 15:59:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA05537; Sun, 24 Oct 1999 15:59:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA32745; Sun, 24 Oct 1999 15:59:00 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 24 Oct 1999 15:59:00 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: FreeBSDCon pictures Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I put a few pictures from FreeBSDCon here for your enjoyment: http://www.freebsd.org/~jdp/freebsdcon1999/ John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 24 16:29:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 232571511A for ; Sun, 24 Oct 1999 16:29:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA23417; Sun, 24 Oct 1999 16:29:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: John Polstra Cc: hackers@freebsd.org Subject: Re: FreeBSDCon pictures In-reply-to: Your message of "Sun, 24 Oct 1999 15:59:00 PDT." Date: Sun, 24 Oct 1999 16:29:34 -0700 Message-ID: <23413.940807774@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I put a few pictures from FreeBSDCon here for your enjoyment: > > http://www.freebsd.org/~jdp/freebsdcon1999/ This is a nice set of pictures, thanks! I'd also like to add that webmagic is installed on freefall and anyone wishing to use it to create their thumbnails need do nothing more than: 1. Unpack the jpeg files into some subdirectory of $HOME/public_html 2. cd to this directory and type "webmagick" That's it! It will create the index.html file automatically along with all the navigation frobs one needs - it's truly trivial to use. The only caveat is that it will write over any other index.html file you have in the same directory so don't run it over your public_html directory or, if you do, be sure and save a copy of your previous index.html file and then move the new "picture index" index.html aside and just point to it from the previous copy. Even so, webmagick likes to "own" the top referenced directory and even if you do as I outlined above, indexing the pictures directly under $HOME/public_html probably isn't worth the navigation weirdness you'll have to put up with as a result. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 24 16:35:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 881231511A for ; Sun, 24 Oct 1999 16:35:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA05686; Sun, 24 Oct 1999 16:35:11 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA32829; Sun, 24 Oct 1999 16:35:10 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 24 Oct 1999 16:35:10 -0700 (PDT) Message-Id: <199910242335.QAA32829@vashon.polstra.com> To: julian@whistle.com Subject: Re: cvsup not being updated? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Julian Elischer wrote: > I checked in stuff about 3 hours ago but it's still not showing up on > either of cvsup2 or svsup3 > > anything funny going on? Yes, freefall was screwed up again. Something has been causing its amd to hang occasionally, and that hoses the updates to cvsup-master. I intend to add a monitoring process to raise the alarm sooner, but FreeBSDCon week wasn't a likely time for that to happen. To everybody: when you think something is wrong with our mirror system as a whole, please tell me, . Writing to a list like -hackers generally won't cut it. You need to let me personally know as soon as possible. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 7:34: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 50CD014FF7 for ; Mon, 25 Oct 1999 07:34:05 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA65956; Mon, 25 Oct 1999 16:34:01 +0200 (CEST) (envelope-from des) To: James Howard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: replacing grep (again) and regex speed ups References: From: Dag-Erling Smorgrav Date: 25 Oct 1999 16:34:01 +0200 In-Reply-To: James Howard's message of "Sat, 23 Oct 1999 01:51:35 -0400 (EDT)" Message-ID: Lines: 9 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Howard writes: > I submitted a PR (bin/14342) which adds a lot of speed to mismatches in > Henry Spencer's regex code. Who knows a lot about regex whom I can bug? Umm, how about Henry Spencer ? :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 7:48:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id D622A15022 for ; Mon, 25 Oct 1999 07:48:38 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id KAA26396; Mon, 25 Oct 1999 10:48:25 -0400 (EDT) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA24726; Mon, 25 Oct 1999 10:48:30 -0400 (EDT) Received: from localhost (howardjp@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA24722; Mon, 25 Oct 1999 10:48:29 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: howardjp owned process doing -bs Date: Mon, 25 Oct 1999 10:48:29 -0400 (EDT) From: James Howard To: Dag-Erling Smorgrav Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: replacing grep (again) and regex speed ups In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Oct 1999, Dag-Erling Smorgrav wrote: > James Howard writes: > > I submitted a PR (bin/14342) which adds a lot of speed to mismatches in > > Henry Spencer's regex code. Who knows a lot about regex whom I can bug? > > Umm, how about Henry Spencer ? :) That does little to help FreeBSD's regex. I'll email him though, that seems like a pretty good idea. BTW, this is the Boyer-Moore code pulled from grep so now grep behaves itself. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 10:18:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from doggate.exchange.microsoft.com (doggate.exchange.microsoft.com [131.107.88.55]) by hub.freebsd.org (Postfix) with ESMTP id 4D04514BCD; Mon, 25 Oct 1999 10:18:22 -0700 (PDT) (envelope-from minwei@Exchange.Microsoft.com) Received: by doggate.exchange.microsoft.com with Internet Mail Service (5.5.2232.9) id <42Y7ABCC>; Mon, 25 Oct 1999 10:18:24 -0700 Message-ID: <01D6C7224936D211BA450000F805D5380F8D0486@TOTO> From: "Min Wei (Exchange)" To: freebsd-net@FreeBSD.ORG, "'hackers@freebsd.org'" Subject: FreeBSD reboots Date: Mon, 25 Oct 1999 10:18:13 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I have a situation where FreeBSD 3.2 reboots once a while (less than every 12 hours). My net environment is, FreeBSD 3.2 sits behind a Cisco LocalDirector. The FreeBSD machine is a Dell dual-proc with 512M RAM. I recompiled the kernel with SMP options and set MAXMEM to 512M (since by default FreeBSD thinks it only has 64M). I have apache installed as the Web server. However during our Web stress run, FreeBSD reboots periodically. I wonder if it's because a lot of TCP connections at FIN_WAIT_2 state, which causes the kernel crash. The load on the machine is not high (CPU is about 90% idle from top). I could only guess Cisco LD might not be configured properly which causes a lot of open connections. Anyone sees this kind of problem before? Any advice would be greatly appreciated. Thanks, --min To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 10:52:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id E92A315194; Mon, 25 Oct 1999 10:52:26 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA10877; Mon, 25 Oct 1999 10:52:24 -0700 (PDT) Date: Mon, 25 Oct 1999 10:52:24 -0700 (PDT) From: Julian Elischer To: "Min Wei (Exchange)" Cc: freebsd-net@FreeBSD.ORG, "'hackers@freebsd.org'" Subject: Re: FreeBSD reboots In-Reply-To: <01D6C7224936D211BA450000F805D5380F8D0486@TOTO> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-453316678-940873944=:7282" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-453316678-940873944=:7282 Content-Type: TEXT/PLAIN; charset=US-ASCII why do you have a lot of connections in 'fin-wait-2 state? do you have windows clients? how many is 'a lot' if you leave the console on and so NOT have X11 runjing you may see mesages on the console. (possibly install DDB so that it doesn't fully reboot, but stops in the debugger) I have a patch to fix the fin-wait-2 problem.. I have included it. (It was last tested in 3.2) What it does is allow probing of the client so that the client will send an RST if the session is really closed, and if no response for a while, it will time out. You need to enable it in the config file too julian On Mon, 25 Oct 1999, Min Wei (Exchange) wrote: > Hi. I have a situation where FreeBSD 3.2 reboots once a while (less than > every > 12 hours). My net environment is, FreeBSD 3.2 sits behind a Cisco > LocalDirector. > The FreeBSD machine is a Dell dual-proc with 512M RAM. I recompiled the > kernel > with SMP options and set MAXMEM to 512M (since by default FreeBSD thinks it > only > has 64M). I have apache installed as the Web server. > > However during our Web stress run, FreeBSD reboots periodically. I wonder > if it's because a lot of TCP connections at FIN_WAIT_2 state, which causes > the kernel crash. The load on the machine is not high (CPU is about 90% idle > from > top). I could only guess Cisco LD might not be configured properly which > causes > a lot of open connections. > > Anyone sees this kind of problem before? Any advice would be greatly > appreciated. > > Thanks, > --min > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > --0-453316678-940873944=:7282 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="FINWAIT2.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="FINWAIT2.patch" SW5kZXg6IG5ldGluZXQvdGNwX2lucHV0LmMNCj09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT0NClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3NyYy9zeXMvbmV0aW5ldC90 Y3BfaW5wdXQuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuODQNCmRpZmYg LWMgLXIxLjg0IG5ldGluZXQvdGNwX2lucHV0LmMNCioqKiBuZXRpbmV0L3Rj cF9pbnB1dC5jCTE5OTkvMDIvMDYgMDA6NDc6NDUJMS44NA0KLS0tIG5ldGlu ZXQvdGNwX2lucHV0LmMJMTk5OS8wNC8wOCAwMDo0NTo1NA0KKioqKioqKioq KioqKioqDQoqKiogODgsOTMgKioqKg0KLS0tIDg4LDk5IC0tLS0NCiAgU1lT Q1RMX0lOVChfbmV0X2luZXRfdGNwLCBPSURfQVVUTywgZGVsYXllZF9hY2ss IENUTEZMQUdfUlcsIA0KICAJJnRjcF9kZWxhY2tfZW5hYmxlZCwgMCwgIiIp Ow0KICANCisgI2lmZGVmCVRDUF9VU09GVF9CVUcNCisgaW50IHRjcF9maW5f cmV0cnlfZW5hYmxlID0gMDsNCisgU1lTQ1RMX0lOVChfbmV0X2luZXRfdGNw LCBPSURfQVVUTywgZmluX3JldHJ5LCBDVExGTEFHX1JXLCANCisgCSZ0Y3Bf ZmluX3JldHJ5X2VuYWJsZSwgMCwgIiIpOw0KKyAjZW5kaWYJLyogVENQX1VT T0ZUX0JVRyAqLw0KKyANCiAgdV9sb25nCXRjcF9ub3c7DQogIHN0cnVjdCBp bnBjYmhlYWQgdGNiOw0KICBzdHJ1Y3QgaW5wY2JpbmZvIHRjYmluZm87DQoq KioqKioqKioqKioqKioNCioqKiAxNDk1LDE1MDQgKioqKg0KLS0tIDE1MDEs MTU0MCAtLS0tDQogIAkJCQkgKiBzcGVjaWZpY2F0aW9uLCBidXQgaWYgd2Ug ZG9uJ3QgZ2V0IGEgRklODQogIAkJCQkgKiB3ZSdsbCBoYW5nIGZvcmV2ZXIu DQogIAkJCQkgKi8NCisgI2lmZGVmIFRDUF9VU09GVF9CVUcNCisgCQkJCS8q DQorIAkJCQkgKiBXYWl0IGxvbmdlciBhbmQgbG9uZ2VyIGZvciB0aGUgb3Ro ZXINCisgCQkJCSAqIGVuZCB0byByZXNwb25kIHdpdGggc29tZXRoaW5nLg0K KyAJCQkJICogRXZlbnR1YWxseSB0aGV5IHNob3VsZCBlaXRoZXINCisgCQkJ CSAqIFJTVCBvciBGSU4uIElmIHRoZXkgYXJlIHN0aWxsIGFsaXZlDQorIAkJ CQkgKiBhbmQgYWN0dWFsbHkgd2FudCB1cyB0byByZW1haW4gaW4gdGhpcw0K KyAJCQkJICogc3RhdGUsIHRoZXkgd2lsbCBrZWVwIEFDS2luZyBhbmQNCisg CQkJCSAqIHdlJ2xsIHN0YXkgaGVyZSBpbmRlZmluaXRseS4NCisgCQkJCSAq IElmIHRoZXkgZG9uJ3QgcmVzcG9uZCBhdCBhbGwsIHdlIHdpbGwNCisgCQkJ CSAqIHJldmVydCB0byBGSU5fV0FJVF8xIGFuZCBldmVudHVhbGx5DQorIAkJ CQkgKiB0aW1lIG91dCBhcyBpdCB3b3VsZC4gSG93IHRvIGNvcGUgd2l0aA0K KyAJCQkJICogdGhlIGNhc2Ugb2YgYnJva2VuIGNsaWVudHMgd2hvIGFyZSBz dGlsbA0KKyAJCQkJICogYWxpdmUgYnV0IG5ldmVyIEZJTiBpcyBhcmd1YWJs ZS4gQ2VydGFpbmx5DQorIAkJCQkgKiBpZiB3ZSd2ZSBjbG9zZWQgb3VyIGVu ZCBlbnRpcmVseSwgd2UNCisgCQkJCSAqIG1pZ2h0IGFzIHdlbGwganVzdCBj bG9zZSB0aGUgY29ubmVjdGlvbi4NCisgCQkJCSAqLw0KKyAJCQkJaWYgKHRj cF9maW5fcmV0cnlfZW5hYmxlKSB7DQorIAkJCQl0cC0+dF90aW1lcltUQ1BU XzJNU0xdID0gDQorIAkJCQkJKCh0cC0+dF9pZGxlID4gVENQVFZfTVNMKSA/ DQorIAkJCQkJdHAtPnRfaWRsZSA6IFRDUFRWX01TTCk7DQorIAkJCQl9IGVs c2Ugew0KKyAJCQkJCWlmIChzby0+c29fc3RhdGUgJiBTU19DQU5UUkNWTU9S RSkgew0KKyAJCQkJCQlzb2lzZGlzY29ubmVjdGVkKHNvKTsNCisgCQkJCQkJ dHAtPnRfdGltZXJbVENQVF8yTVNMXQ0KKyAJCQkJCQkJCT0gdGNwX21heGlk bGU7DQorIAkJCQkJfQ0KKyAJCQkJfQ0KKyAjZWxzZQkvKiBUQ1BfVVNPRlRf QlVHICovDQogIAkJCQlpZiAoc28tPnNvX3N0YXRlICYgU1NfQ0FOVFJDVk1P UkUpIHsNCiAgCQkJCQlzb2lzZGlzY29ubmVjdGVkKHNvKTsNCiAgCQkJCQl0 cC0+dF90aW1lcltUQ1BUXzJNU0xdID0gdGNwX21heGlkbGU7DQogIAkJCQl9 DQorICNlbmRpZgkvKiBUQ1BfVVNPRlRfQlVHICovDQogIAkJCQl0cC0+dF9z dGF0ZSA9IFRDUFNfRklOX1dBSVRfMjsNCiAgCQkJfQ0KICAJCQlicmVhazsN CkluZGV4OiBuZXRpbmV0L3RjcF90aW1lci5jDQo9PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL25ldGluZXQv dGNwX3RpbWVyLmMsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjI4DQpkaWZm IC1jIC1yMS4yOCBuZXRpbmV0L3RjcF90aW1lci5jDQoqKiogbmV0aW5ldC90 Y3BfdGltZXIuYwkxOTk4LzA0LzI0IDA5OjI1OjM1CTEuMjgNCi0tLSBuZXRp bmV0L3RjcF90aW1lci5jCTE5OTkvMDQvMDggMDA6NDU6NTQNCioqKioqKioq KioqKioqKg0KKioqIDIxMywyMjIgKioqKg0KICAJICogY29udHJvbCBibG9j ay4gIE90aGVyd2lzZSwgY2hlY2sgYWdhaW4gaW4gYSBiaXQuDQogIAkgKi8N CiAgCWNhc2UgVENQVF8yTVNMOg0KISAJCWlmICh0cC0+dF9zdGF0ZSAhPSBU Q1BTX1RJTUVfV0FJVCAmJg0KISAJCSAgICB0cC0+dF9pZGxlIDw9IHRjcF9t YXhpZGxlKQ0KISAJCQl0cC0+dF90aW1lcltUQ1BUXzJNU0xdID0gdGNwX2tl ZXBpbnR2bDsNCiEgCQllbHNlDQogIAkJCXRwID0gdGNwX2Nsb3NlKHRwKTsN CiAgCQlicmVhazsNCiAgDQotLS0gMjEzLDI0NiAtLS0tDQogIAkgKiBjb250 cm9sIGJsb2NrLiAgT3RoZXJ3aXNlLCBjaGVjayBhZ2FpbiBpbiBhIGJpdC4N CiAgCSAqLw0KICAJY2FzZSBUQ1BUXzJNU0w6DQohIAkJaWYgKHRwLT50X3N0 YXRlICE9IFRDUFNfVElNRV9XQUlUDQohIAkJJiYgdHAtPnRfaWRsZSA8PSB0 Y3BfbWF4aWRsZSkgew0KISAjaWZkZWYgVENQX1VTT0ZUX0JVRw0KISAJCQlp ZiAodGNwX2Zpbl9yZXRyeV9lbmFibGUNCiEgCQkJJiYgKHRwLT50X3N0YXRl ID09IFRDUFNfRklOX1dBSVRfMikpIHsNCiEgCQkJCS8qDQohIAkJCQkgKiBX ZSd2ZSB0aW1lZCBvdXQgd2FpdGluZyBmb3IgdGhlIG90aGVyIGVuZCANCiEg CQkJCSAqIHRvIGZpbmlzaCB1cC4gUXVpdGUgcG9zc2libHkgaXQncyBhIFdp bjl4DQohIAkJCQkgKiBtYWNoaW5lLg0KISAJCQkJICogSWYgc28gd2UgY291 bGQgYmUgd2FpdGluZyBoZXJlIGZvcmV2ZXIuDQohIAkJCQkgKiBQcmV0ZW5k IHdlIHdlcmUgbmV2ZXIgYWNrJ2QgYW5kIHJlc2V0DQohIAkJCQkgKiBvdXJz ZWx2ZXMgdG8gYSByZXRyeSBvZiBGSU5fV0FJVF8xLiBJZg0KISAJCQkJICog aXQncyBzdGlsbCBhbGl2ZSwgdGhpcyBzaG91bGQgYXQgbGVhc3QNCiEgCQkJ CSAqIGVsaWNpdCBhIFJTVCBmcm9tIGl0IHdoaWNoDQohIAkJCQkgKiB3aWxs IGxldCB1cyBrbm93IHdlIGNhbiBzaHV0IGRvd24uDQohIAkJCQkgKiBJZiBp dCBoYXMgb25seSBkb25lIGEgaGFsZiBjbG9zZSwNCiEgCQkJCSAqIGl0J2xs IEFDSyBvdXIgcmV0cmllcyBzbyB3ZSdsbA0KISAJCQkJICoga2VlcCB3YWl0 aW5nIGluIEZJTl9XQUlUXzIuDQohIAkJCQkgKiBJZiBpdCdzIGRlYWQsIHdl J2xsIHRpbWUgb3V0Lg0KISAJCQkJICovDQohIAkJCQl0cC0+dF9zdGF0ZSA9 IFRDUFNfRklOX1dBSVRfMTsNCiEgCQkJCXRwLT50X2ZsYWdzICY9IH5URl9T RU5URklOOw0KISAJCQkJdHAtPnNuZF91bmEgPSAodHAtPnNuZF9ueHQgLT0g MSk7DQohIAkJCQl0Y3Bfb3V0cHV0KHRwKTsNCiEgCQkJfSBlbHNlDQohICNl bmRpZg0KISAJCQkJdHAtPnRfdGltZXJbVENQVF8yTVNMXSA9IHRjcF9rZWVw aW50dmw7DQohIAkJfSBlbHNlDQogIAkJCXRwID0gdGNwX2Nsb3NlKHRwKTsN CiAgCQlicmVhazsNCiAgDQpJbmRleDogbmV0aW5ldC90Y3BfdmFyLmgNCj09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3Ny Yy9zeXMvbmV0aW5ldC90Y3BfdmFyLmgsdg0KcmV0cmlldmluZyByZXZpc2lv biAxLjUwDQpkaWZmIC1jIC1yMS41MCBuZXRpbmV0L3RjcF92YXIuaA0KKioq IG5ldGluZXQvdGNwX3Zhci5oCTE5OTkvMDIvMTYgMTA6NDk6NTIJMS41MA0K LS0tIG5ldGluZXQvdGNwX3Zhci5oCTE5OTkvMDQvMDggMDA6NDU6NTQNCioq KioqKioqKioqKioqKg0KKioqIDMzNCwzMzkgKioqKg0KLS0tIDMzNCwzNDAg LS0tLQ0KICBleHRlcm4JaW50IHRjcF9tc3NkZmx0OwkvKiBYWFggKi8NCiAg ZXh0ZXJuCXVfbG9uZyB0Y3Bfbm93OwkJLyogZm9yIFJGQyAxMzIzIHRpbWVz dGFtcHMgKi8NCiAgZXh0ZXJuCWludCB0Y3BfZGVsYWNrX2VuYWJsZWQ7DQor IGV4dGVybglpbnQgdGNwX2Zpbl9yZXRyeV9lbmFibGU7DQogIA0KICB2b2lk CSB0Y3BfY2FuY2VsdGltZXJzIF9fUCgoc3RydWN0IHRjcGNiICopKTsNCiAg c3RydWN0IHRjcGNiICoNCg== --0-453316678-940873944=:7282-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 14:12:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (Postfix) with ESMTP id 3819A14D54 for ; Mon, 25 Oct 1999 14:12:54 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id 25DA3A84A; Mon, 25 Oct 1999 23:12:54 +0200 (CEST) Date: Mon, 25 Oct 1999 23:12:54 +0200 From: Guido van Rooij To: FreeBSD-hackers Subject: vaio z505sx and fxp suspend/resume problem Message-ID: <19991025231253.A43197@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I suspend and later resume a VAIO z505sx, the fxp interface seems not to be able to send out packets. Receiving goes okay (as tcpdump -n will actually dump all packets on the wire). No errors are reporteed on the interface (kernel or netstat -ni). Ifconfig-ing the interface down and up again does not seem to make a difference. It seems after 1-2 minutes the interface is okay again. The interface was both tried with mdia selection to auto and to UTP (both worked in the same way) Have others seen the same and is thyere a known fix? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15: 0:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id DFF3B14CC1 for ; Mon, 25 Oct 1999 15:00:37 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1001) id DFBFA221; Tue, 26 Oct 1999 00:00:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 6607D20A for ; Tue, 26 Oct 1999 00:00:32 +0200 (CEST) Date: Tue, 26 Oct 1999 00:00:32 +0200 (CEST) From: Pascal Hofstee To: freebsd-hackers@freebsd.org Subject: module names Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With the recent addition of more and more KLDs to the /modules directory i was wondering if perhaps it would be a good idea to name these modules more consistantly: if_* : For all network modules (done already) ng_* : For all netgraph related modules (done already) fs_* : For all filesystem modules saver_* : For all screensavers (probably would prefer a shorter prefix) emu_* : For binary compatibilty modules like linux/ibcs2/svr4 of course this is just a suggestion ... just thought i would voice it here. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15: 1:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E7B3F14CC1 for ; Mon, 25 Oct 1999 15:01:56 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id WAA77211; Mon, 25 Oct 1999 22:59:56 +0100 (BST) (envelope-from nik) Date: Mon, 25 Oct 1999 22:59:56 +0100 From: Nik Clayton To: John Polstra Cc: hackers@freebsd.org Subject: Re: FreeBSDCon pictures Message-ID: <19991025225955.A71828@catkin.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from John Polstra on Sun, Oct 24, 1999 at 03:59:00PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 24, 1999 at 03:59:00PM -0700, John Polstra wrote: > I put a few pictures from FreeBSDCon here for your enjoyment: > > http://www.freebsd.org/~jdp/freebsdcon1999/ Ugh! That's a horrible picture of me on there. Similarly, http://www.freebsd.org/~nik/freebsdcon-1999/pictures/ No captions yet though. Of those, http://www.freebsd.org/~nik/freebsdcon-1999/pictures/Tuesday/P0000118.JPG is really quite amusing. . . More pics to follow. N To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15: 6: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id DC43D14CC1 for ; Mon, 25 Oct 1999 15:06:02 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FK6004NWIPQU6@mta1.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Mon, 25 Oct 1999 17:05:56 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA35778; Mon, 25 Oct 1999 17:05:27 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 25 Oct 1999 17:05:27 -0500 From: Chris Costello Subject: Re: module names In-reply-to: To: Pascal Hofstee Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991025170527.K452@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 26, 1999, Pascal Hofstee wrote: > Hi, > > With the recent addition of more and more KLDs to the /modules directory i > was wondering if perhaps it would be a good idea to name these modules > more consistantly: > > if_* : For all network modules (done already) > ng_* : For all netgraph related modules (done already) > fs_* : For all filesystem modules > saver_* : For all screensavers (probably would prefer a shorter prefix) > emu_* : For binary compatibilty modules like linux/ibcs2/svr4 I agree with the idea but some of the name ideas are a little off. What would Vinum go under? I also disagree with your usage of ``emu_''. I would prefer ``compat_''. -- |Chris Costello |If at first you don't succeed, you must be a programmer. `-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15: 6:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 031E615287 for ; Mon, 25 Oct 1999 15:06:31 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA24136 for FreeBSD-hackers@freebsd.org; Tue, 26 Oct 1999 00:06:24 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 04236885C; Mon, 25 Oct 1999 23:38:53 +0200 (CEST) Date: Mon, 25 Oct 1999 23:38:53 +0200 From: Ollivier Robert To: FreeBSD-hackers Subject: Re: vaio z505sx and fxp suspend/resume problem Message-ID: <19991025233853.A60175@keltia.freenix.fr> Mail-Followup-To: FreeBSD-hackers References: <19991025231253.A43197@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991025231253.A43197@gvr.gvr.org> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Guido van Rooij: > When I suspend and later resume a VAIO z505sx, the fxp interface seems > not to be able to send out packets. Receiving goes okay (as tcpdump -n > will actually dump all packets on the wire). I've seen that when this happen (it doesn't happen every resume), running "tcpdump" seems to wake the interface up. Nice to see you've installed your VAIO now :-) Mine made a buildworld for 3.3-RELEASE in 3422s... Way faster than my K6/200 (around 2 hours) and my dual PPro/200 (4915 s). 3422.40 real 2227.82 user 460.99 sys This laptop is now my fastest machine, wow! :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15: 8:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id EA7301527B for ; Mon, 25 Oct 1999 15:08:54 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1001) id 9A3EB13C; Tue, 26 Oct 1999 00:08:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by shadowmere.student.utwente.nl (Postfix) with ESMTP id 9341DCC for ; Tue, 26 Oct 1999 00:08:53 +0200 (CEST) Date: Tue, 26 Oct 1999 00:08:53 +0200 (CEST) From: Pascal Hofstee To: freebsd-hackers@FreeBSD.ORG Subject: Re: module names In-Reply-To: <19991025170527.K452@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Oct 1999, Chris Costello wrote: > I agree with the idea but some of the name ideas are a little > off. What would Vinum go under? > > I also disagree with your usage of ``emu_''. I would prefer > ``compat_''. I agree the names were not choosen perfectly ... I agree on compat_ the suggestions i provided were just to illustrate the idea ... in the hopes to get some discussion and attention on the whole idea. -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15:29: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id ADB3114C4E; Mon, 25 Oct 1999 15:29:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9B76F1CD43E; Mon, 25 Oct 1999 15:29:00 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Mon, 25 Oct 1999 15:29:00 -0700 (PDT) From: Kris Kennaway To: Pascal Hofstee Cc: freebsd-hackers@freebsd.org, arch@freebsd.org Subject: Re: module names In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This kind of stuff is better suited to the arch mailing list..cross-posting. Kris On Tue, 26 Oct 1999, Pascal Hofstee wrote: > Hi, > > With the recent addition of more and more KLDs to the /modules directory i > was wondering if perhaps it would be a good idea to name these modules > more consistantly: > > if_* : For all network modules (done already) > ng_* : For all netgraph related modules (done already) > fs_* : For all filesystem modules > saver_* : For all screensavers (probably would prefer a shorter prefix) > emu_* : For binary compatibilty modules like linux/ibcs2/svr4 > > of course this is just a suggestion ... just thought i would voice it > here. > > -------------------- > Pascal Hofstee - daeron@shadowmere.student.utwente.nl > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- > t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ > ------END GEEK CODE BLOCK------ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ---- XOR for AES -- join the campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 15:52:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id EC67614DAA for ; Mon, 25 Oct 1999 15:52:07 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA26393 for FreeBSD-hackers@FreeBSD.ORG; Tue, 26 Oct 1999 00:52:06 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C4ED9885C; Tue, 26 Oct 1999 00:03:05 +0200 (CEST) Date: Tue, 26 Oct 1999 00:03:05 +0200 From: Ollivier Robert To: FreeBSD-hackers@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness Message-ID: <19991026000305.B60175@keltia.freenix.fr> Mail-Followup-To: FreeBSD-hackers@FreeBSD.ORG References: <199910120408.VAA04018@dingo.cdrom.com> <38094BC8.B4040C5C@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <38094BC8.B4040C5C@gorean.org> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Doug: > Heh... well I've already enabled flags 0xb0ff, which has improved things Speaking of flags for ATA disks, I'm using 0xa0ff for my laptop drive and wonders if there a better setting...? found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000fcb0, size 4 ide_pci0: rev 0x01 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000fcb2 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000fcba ... wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 18:31:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by hub.freebsd.org (Postfix) with ESMTP id 7B86B15286; Mon, 25 Oct 1999 18:31:07 -0700 (PDT) (envelope-from ssamalin@ionet.net) Received: from ionet.net (sam.ops.best.com [205.149.163.53]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id SAA09771; Mon, 25 Oct 1999 18:29:55 -0700 (PDT) Message-ID: <38150409.FF8BE621@ionet.net> Date: Mon, 25 Oct 1999 21:29:45 -0400 From: Sam Samalin X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-ipfw@freebsd.org, "freebsd-hackers@Freebsd.org" Subject: ftp dir fails with ipfw fwd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get this when I try to ftp dir: Can't create data socket (n.n.n.n,20) : Can't assign requested address. I'm using ipfw fwd. Do I need a rule? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 25 22:19:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 2C87B152EA for ; Mon, 25 Oct 1999 22:19:50 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id OAA03724 for ; Tue, 26 Oct 1999 14:19:49 +0900 (JST) To: hackers@freebsd.org Subject: [freebsdcon] slides for IPv6/IPsec talk X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 From: itojun@iijlab.net Date: Tue, 26 Oct 1999 14:19:49 +0900 Message-ID: <3722.940915189@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to troubles on my notebook PC:-), I was unable to show you the last dozen of slides to you at the event. I made the slides available at: http://www.itojun.org/diary/19991019/ It will also be included into to-appear freebsdcon proceedings webpage. BTW the blue-screen-of-death was due to my fault. I forgot to make clean before building a new kernel. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 8:24:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id ADF9B14EEE for ; Tue, 26 Oct 1999 08:24:07 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id LAA23812; Tue, 26 Oct 1999 11:22:42 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Tue, 26 Oct 1999 11:22:41 -0400 (EDT) From: Chuck Youse To: Julian Elischer Cc: Jerry Bell , freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW Improvements. (comments?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Oct 1999, Julian Elischer wrote: > > The real advantage is being able to do somethine like this: > > > > #!/bin/sh > > dnservers=10.0.0.1,10.0.0.2,10.0.0.3 > > smtpservers=10.0.0.4,10.0.0.5,10.0.0.6 > > ipfw add pass udp from any to $dnservers 53 > > ipfw add pass tcp from any to $smtpservers 25 > > > > ... and so on. > but you need to store this somewhere.. > the present system of fixed structures doesn't support this without an > enormous waste of space...I'm not sure how useful it would be in > practice.. Actually, for what he's describing, we could simply modify /sbin/ipfw to add multiple rules. For example, the first ipfw example above would be expanded to: ipfw add pass udp from any to 10.0.0.1 53 ipfw add pass udp from any to 10.0.0.2 53 ipfw add pass udp from any to 10.0.0.3 53 I'm not quite sure of the value of this in practice either (as one could easily expand the rules by hand), but it's not too difficult to implement. Chuck Youse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 9:20:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 5CC7D14EBC for ; Tue, 26 Oct 1999 09:20:54 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA02534; Tue, 26 Oct 1999 12:17:48 -0400 (EDT) Message-Id: <199910261617.MAA02534@etinc.com> X-Sender: dennis@etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 26 Oct 1999 11:19:47 -0400 To: mike@sentex.net (Mike Tancsa) From: Dennis Subject: Re: if_fxp driver error messages - Still Cc: hackers@freebsd.org In-Reply-To: <380e6b3f.1203532608@mail.sentex.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:25 AM 10/21/99 +0000, you wrote: >On 20 Oct 1999 17:42:58 -0400, in sentex.lists.freebsd.hackers you wrote: > >> >>Running a late 3.2-stable, im getting >> >>fxp0: warning: unsupported PHY, type = 0, addr = 0 >> >>the card has a GD82559 Intel part on it.... >> >> >>Is there an updated version of the driver that supports this? > >If this is the newer rev cards, I think > >$FreeBSD: src/sys/pci/if_fxp.c,v 1.59.2.4 1999/08/29 16:31:37 peter Exp $ > >addresses it. Nope, that version still get the error message. I guess Intel has "yet another" rev. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 10:33:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B8F5114D4E; Tue, 26 Oct 1999 10:33:12 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11gAT2-000GhY-00; Tue, 26 Oct 1999 13:33:04 -0400 Date: Tue, 26 Oct 1999 13:33:02 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Kris Kennaway Cc: Pascal Hofstee , freebsd-hackers@freebsd.org, arch@freebsd.org Subject: Re: module names In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I, for one, like what was suggested a long time ago, by someone who I cannot really remember. It separated driver "classes" in /modules subdirectories. For instance, we could have a "net" for the if_foo drivers, "storage" for CAM/ATA/RAID/Vinum/CCD/etc., "periph" for various esoteric peripherals, "exec" for exec formats like svr4/linux/ ibcs2, "video" for vesa/*_saver, "fs" for filesystems (separate from storage), and "netsub" for ipfw/streams/loadable socket domains. I think that, perhaps, there should be a "bus" where pccard, usb, and SCSI cards would go (instead of "storage"). Currently, we don't have way too many modules, so I'm happy with what's here now. I definitely think there's room for improvement in how /modules is organized, but remember that the format came straight from what we used to have in /lkm. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 10:41:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3310C14EDE for ; Tue, 26 Oct 1999 10:41:31 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA61444; Tue, 26 Oct 1999 10:41:16 -0700 (PDT) Date: Tue, 26 Oct 1999 10:41:17 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Chuck Youse Cc: Jerry Bell , freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW Improvements. (comments?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG check how the netatalk code expands a range in to teh minumm set of netmasks needed to cover that range. (somewhere in /sys/netatalk). On Tue, 26 Oct 1999, Chuck Youse wrote: > > > On Tue, 19 Oct 1999, Julian Elischer wrote: > > > > The real advantage is being able to do somethine like this: > > > > > > #!/bin/sh > > > dnservers=10.0.0.1,10.0.0.2,10.0.0.3 > > > smtpservers=10.0.0.4,10.0.0.5,10.0.0.6 > > > ipfw add pass udp from any to $dnservers 53 > > > ipfw add pass tcp from any to $smtpservers 25 > > > > > > ... and so on. > > but you need to store this somewhere.. > > the present system of fixed structures doesn't support this without an > > enormous waste of space...I'm not sure how useful it would be in > > practice.. > > Actually, for what he's describing, we could simply modify /sbin/ipfw to > add multiple rules. For example, the first ipfw example above would be > expanded to: > > ipfw add pass udp from any to 10.0.0.1 53 > ipfw add pass udp from any to 10.0.0.2 53 > ipfw add pass udp from any to 10.0.0.3 53 > > I'm not quite sure of the value of this in practice either (as one could > easily expand the rules by hand), but it's not too difficult to implement. > > Chuck Youse > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 11:17:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.2.10]) by hub.freebsd.org (Postfix) with ESMTP id 1435614A2A for ; Tue, 26 Oct 1999 11:17:20 -0700 (PDT) (envelope-from joe@monk.via.net) Received: (from joe@localhost) by monk.via.net (8.9.3/8.9.3) id LAA42698; Tue, 26 Oct 1999 11:18:13 -0700 (PDT) (envelope-from joe) From: Joe McGuckin Message-Id: <199910261818.LAA42698@monk.via.net> Date: Tue, 26 Oct 1999 11:18:13 -0700 (PDT) To: dg@root.com Cc: hackers@freebsd.org, lewis@lppi.com Subject: fxp related kernel panic X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a 3.3-stable machine that I use as a news router (running diablo). The fxp0 interface averages 10-15 Mbps bandwidth continously. About once a week the machine crashes & reboots. We enabled the debugger this time and captured the following debug output: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x382e4641 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01a372e stack pointer = 0x10:0xc02523b0 frame pointer = 0x10:0xc02523c0 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 kernel: type 12 trap, code=0 Stopped at fxp_add_rfabuf+0x1de: movw %ax,0x4(%esi) db> %uname -a FreeBSD feeder.via.net 3.3-STABLE FreeBSD 3.3-STABLE #7: Mon Oct 18 17:14:40 PDT 1999 lewis@feeder.via.net:/usr/src/sys/compile/DIABLO i386 %dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #7: Mon Oct 18 17:14:40 PDT 1999 lewis@feeder.via.net:/usr/src/sys/compile/DIABLO Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 498752616 Hz CPU: Pentium III (498.75-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387fbff,MMX,FXSR,> real memory = 536870912 (524288K bytes) avail memory = 519340032 (507168K bytes) Preloaded elf kernel "kernel" at 0xc02ca000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 ncr0: rev 0x37 int a irq 11 on pci0.13.0 ncr1: rev 0x37 int b irq 10 on pci0.13.1 fxp0: rev 0x05 int a irq 5 on pci0.15. 0 fxp0: Ethernet address 00:a0:c9:fc:45:7f chip1: rev 0x02 on pci0.18.0 ide_pci0: rev 0x01 on pci0.18.1 chip2: rev 0x02 on pci0.18.3 vga0: rev 0x23 on pci0.2 0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16 wd0: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , LBA, DMA, 32-bit, multi-block-16 wd1: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) WARNING: / was not properly dismounted Any ideas ? Thanks, Joe -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 11:27:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (oberon.ntu-kpi.kiev.ua [195.178.136.20]) by hub.freebsd.org (Postfix) with ESMTP id 8D87614F53 for ; Tue, 26 Oct 1999 11:26:31 -0700 (PDT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (eth0.comsys.ntu-kpi.kiev.ua [10.0.1.184]) by relay1.ntu-kpi.kiev.ua (Postfix) with ESMTP id 954832FA24 for ; Tue, 26 Oct 1999 21:26:25 +0300 (EEST) Received: from comsys.ntu-kpi.kiev.ua (c514-9.comsys.ntu-kpi.kiev.ua [10.18.54.59]) by comsys.ntu-kpi.kiev.ua (8.9.2/8.8.7) with ESMTP id VAA11892 for ; Tue, 26 Oct 1999 21:26:11 +0300 (EEST) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Message-ID: <3815E447.76532CF5@comsys.ntu-kpi.kiev.ua> Date: Tue, 26 Oct 1999 21:26:31 +0400 From: Andrey Simonenko X-Mailer: Mozilla 4.07 [en] (Win98; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: UNILOAD v.1.2 (boot loader/manager) is ready Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I made some days ago UNILOAD v.1.2, the main feature of this version is the ability to load system from beyond 1024 cylinder mark. Here it is list of some changes: -------------------------------------------------------------------------- Changes in version 1.2 - UNILOAD uses IBM/MS INT 0x13 extensions and can load partitions beyond 1024 cylinder mark - install program checks if IBM/MS INT 0x13 extensions are supported, item 'Drive geometry' in install program can show right geometry - unknown type of partition is printed as hexadecimal number - length of highlighted bar in menu is equal to length of longest line -------------------------------------------------------------------------- Here it is some lines from README file: -------------------------------------------------------------------------- You shouldn't make any configuration to force the ability of UNILOAD to use LBA packet interface. At first time UNILOAD tries to use LBA packet interface to read sector. If that attempt failed then UNILOAD use standard INT 0x13 call. -------------------------------------------------------------------------- You can download it on following URL in 'Software' menu item: http://comsys.ntu-kpi.kiev.ua/~simon On this URL online documentation for UNILOAD is also available, *please read it before install UNILOAD on your system*. If you have problem with access to this site (our university has problem with outgoing channel) please inform me about it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 11:46: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 2DBA314D3A for ; Tue, 26 Oct 1999 11:45:51 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA23132; Tue, 26 Oct 1999 11:43:02 -0700 (PDT) Message-Id: <199910261843.LAA23132@implode.root.com> To: Joe McGuckin Cc: hackers@freebsd.org, lewis@lppi.com Subject: Re: fxp related kernel panic In-reply-to: Your message of "Tue, 26 Oct 1999 11:18:13 PDT." <199910261818.LAA42698@monk.via.net> From: David Greenman Reply-To: dg@root.com Date: Tue, 26 Oct 1999 11:43:02 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me guess...your system has an Intel N440BX motherboard, right? If so, then it's a known problem with no solution yet. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. >I have a 3.3-stable machine that I use as a news router (running diablo). The >fxp0 interface averages 10-15 Mbps bandwidth continously. > >About once a week the machine crashes & reboots. We enabled the debugger this time >and captured the following debug output: > > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x382e4641 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xc01a372e >stack pointer = 0x10:0xc02523b0 >frame pointer = 0x10:0xc02523c0 >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 >kernel: type 12 trap, code=0 >Stopped at fxp_add_rfabuf+0x1de: movw %ax,0x4(%esi) >db> > >%uname -a >FreeBSD feeder.via.net 3.3-STABLE FreeBSD 3.3-STABLE #7: Mon Oct 18 17:14:40 PDT 1999 lewis@feeder.via.net:/usr/src/sys/compile/DIABLO i386 > >%dmesg >Copyright (c) 1992-1999 FreeBSD Inc. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. >FreeBSD 3.3-STABLE #7: Mon Oct 18 17:14:40 PDT 1999 > lewis@feeder.via.net:/usr/src/sys/compile/DIABLO >Timecounter "i8254" frequency 1193182 Hz >Timecounter "TSC" frequency 498752616 Hz >CPU: Pentium III (498.75-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x672 Stepping = 2 > Features=0x387fbffOV,PAT,PSE36,,MMX,FXSR,> >real memory = 536870912 (524288K bytes) >avail memory = 519340032 (507168K bytes) >Preloaded elf kernel "kernel" at 0xc02ca000. >Pentium Pro MTRR support enabled >Probing for devices on PCI bus 0: >chip0: rev 0x03 on pci0.0.0 >ncr0: rev 0x37 int a irq 11 on pci0.13.0 >ncr1: rev 0x37 int b irq 10 on pci0.13.1 >fxp0: rev 0x05 int a irq 5 on pci0.15. >0 >fxp0: Ethernet address 00:a0:c9:fc:45:7f >chip1: rev 0x02 on pci0.18.0 >ide_pci0: rev 0x01 on pci0.18.1 >chip2: rev 0x02 on pci0.18.3 >vga0: rev 0x23 on pci0.2 >0.0 >Probing for PnP devices: >Probing for devices on the ISA bus: >sc0 on isa >sc0: VGA color <16 virtual consoles, flags=0x0> >atkbdc0 at 0x60-0x6f on motherboard >atkbd0 irq 1 on isa >sio0: configured irq 4 not in bitmap of probed irqs 0 >sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa >sio0: type 8250 >sio1: configured irq 3 not in bitmap of probed irqs 0 >sio1 not found at 0x2f8 >fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa >wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16 >wd0: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S >wdc0: unit 1 (wd1): , LBA, DMA, 32-bit, multi-block-16 >wd1: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S >wdc1 not found at 0x170 >vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa >npx0 on motherboard >npx0: INT 16 interface >ccd0-3: Concatenated disk drivers >Waiting 15 seconds for SCSI devices to settle >changing root device to da0s1a >da0 at ncr0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-2 device >da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled >da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) >WARNING: / was not properly dismounted > > > >Any ideas ? > >Thanks, > >Joe > > > >-- > >Joe McGuckin > >ViaNet Communications >994 San Antonio Road >Palo Alto, CA 94303 > >Phone: 650-969-2203 >Cell: 650-207-0372 >Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 12:21:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.lppi.com (relay.lppi.com [207.138.32.245]) by hub.freebsd.org (Postfix) with ESMTP id 3117814F5C for ; Tue, 26 Oct 1999 12:21:25 -0700 (PDT) (envelope-from lew@lppi.com) Date: Tue, 26 Oct 1999 12:21:15 -0700 (PDT) Message-Id: <199910261921.MAA07922@relay.lppi.com> From: Lew Payne To: dg@root.com Cc: hackers@freebsd.org, Joe McGuckin Subject: Re: fxp related kernel panic In-Reply-To: <199910261843.LAA23132@implode.root.com> References: <199910261818.LAA42698@monk.via.net> <199910261843.LAA23132@implode.root.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David -- What if I install a *real* EtherExpress Pro-100B (or whatever it's known as today) in the PCI slot, and use it instead of the on-board (N440BX motherboard) fxp0 interface? Judging that you probably know the nature of the problem, do you think this might circumvent it? Regards, Lew Payne > Let me guess...your system has an Intel N440BX motherboard, right? > If so, then it's a known problem with no solution yet. -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org > Creator of high-performance Internet servers - http://www.terasolutions.com > Pave the road of life with opportunities. --- Lew Payne Publishing, Inc. Dunn & Bradstreet listed 994 San Antonio Road DUNS # 055037852 Palo Alto, CA 94303 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 13:15:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id C21BC14CC4; Tue, 26 Oct 1999 13:15:19 -0700 (PDT) (envelope-from steveb@veriohosting.com) Received: by gatekeeper.veriohosting.com; Tue, 26 Oct 1999 14:15:14 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma021951; Tue, 26 Oct 99 14:15:03 -0600 Received: from iserver.com (glacier.orem.iserver.com [192.168.1.111]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id OAA79261; Tue, 26 Oct 1999 14:16:18 -0600 (MDT) Message-ID: <38160B6A.5568F6D1@iserver.com> Date: Tue, 26 Oct 1999 14:13:31 -0600 From: Steve Bishop X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-database@freebsd.org, freebsd-hackers@freebsd.org Cc: "Paul.Marquess@btinternet.com" Subject: mbuf problem (panic)--possibly related to Berkeley DB 2.7.7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using FreeBSD 3.3-RELEASE, and it is running on a single processor PII 400. At first, I thought the problem was due to the network driver, so I swapped network cards. But, the problem still continues to occur. At first, I used a DEC (de0) NIC. Then, I switched to an Intel EtherExpress Pro 10/100B Ethernet (fxp0). My machine dies when it runs out of mbufs. Normally, one only associates mbufs with network usage, and network (NIC) drivers. I have tried to investigate this possibility, as mentioned, but to no avail. The problem is either a kernel problem, or is related to the Berkeley DB, and/or perl module - BerkeleyDB-0.07.pm. I have written to Paul Marquess who is the author of this perl module. He did not respond, and may not have any idea. The latest release of this perl module is a significant update to the perl support for the latest releases of Berkeley DB. It provides for concurrency and database integrity (consistency) between processes sharing or using the same database simultaneously. There are a number of scripts, I have written, in the system that run (as processes) in parallel. This is why I am using the Concurrent Access Method (CAM) to allow multiple simultaneous readers along with sequential write (one writer at a time) access. Berkeley DB keeps everything consistent. The scripts are designed to use the database a lot, and they also use a significant amount of network resources. The scripts sometimes can have up to 900 open tcp connections, and consistently use almost 600. I have increased the number of mbuf clusters (NMBCLUSTERS) from 1024 to 4096. I have also increased maxusers to 64. The "panics" seem to occur when my scripts or processes prematurely exit without shutting down Berkeley DB in the standard, proper fashion. As I explained, I have upped the number of mbuf clusters from the default 1024, to 4096. The actual number probably wouldn't matter a whole lot as long as it is sufficient to meet the needs of the system were being met. What I'm trying to say, is that when the script(s) crash, the system then begins to use mbufs exponentially, until they're completely exhausted within minutes. The system panics, and reboots. I know the association is loose, but nothing else presents itself as the problem. Is there some kernel resource that Berkeley DB gets a hold of, and never properly releases due to an improper, fatal termination of my script, which could indirectly cause my system to run out of mbufs? I know that the close_everything routine in BerkeleyDB.pm still runs when perl exits, but perhaps, it doesn't work properly in this case? Any ideas or leads as to why this is occuring would be sincerely appreciated. Thanks, Steve Bishop Developer Verio, Inc. verio.com -- the new world of business PS Here's some more background info. In perl, to setup Berkeley DB, I use the shared memory pool. Here is how I setup the environment, and open my database. $env = new BerkeleyDB::Env -Flags => DB_CREATE| DB_INIT_MPOOL| DB_INIT_CDB, -ErrFile => "db-errors"; $DB = tie %db, 'BerkeleyDB::Btree', -Filename => 'servers.db', -Mode => 0600, -Flags => DB_CREATE, -Pagesize => 4096, # default = 8192 -Env => $env or die "Cannot open db: $! $BerkeleyDB::Error"; I think I have discovered an association between my system crashes ("out of mbufs"), and the usage of Berkeley DB. When my script prematurely crashes or exits without following the proper database shutdown procedure, as outlined below, it isn't very long before the machine crashes (usually a few minutes). undef($DB); undef($env); untie(%db); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 13:22:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 0BFA614CC4 for ; Tue, 26 Oct 1999 13:22:38 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA23488; Tue, 26 Oct 1999 13:19:45 -0700 (PDT) Message-Id: <199910262019.NAA23488@implode.root.com> To: Lew Payne Cc: hackers@freebsd.org, Joe McGuckin Subject: Re: fxp related kernel panic In-reply-to: Your message of "Tue, 26 Oct 1999 12:21:15 PDT." <199910261921.MAA07922@relay.lppi.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 26 Oct 1999 13:19:45 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi David -- What if I install a *real* EtherExpress Pro-100B (or >whatever it's known as today) in the PCI slot, and use it instead >of the on-board (N440BX motherboard) fxp0 interface? > >Judging that you probably know the nature of the problem, do you >think this might circumvent it? I think it is caused by the NCR/Symbios controller. It might be a side effect of the NCR just using up a lot of PCI bandwidth, with the real bug being in the fxp driver (although I've looked and haven't found one). So I don't think putting in a real Pro/100 will have any effect on the problem. Of course I don't really know what is causing it, so just about anything is possible. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 13:46:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3E07414F4C for ; Tue, 26 Oct 1999 13:46:06 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA12795; Tue, 26 Oct 1999 14:08:25 -0700 (PDT) Date: Tue, 26 Oct 1999 14:08:25 -0700 (PDT) From: Alfred Perlstein To: Steve Bishop Cc: freebsd-hackers@FreeBSD.ORG, "Paul.Marquess@btinternet.com" Subject: Re: mbuf problem (panic)--possibly related to Berkeley DB 2.7.7 In-Reply-To: <38160B6A.5568F6D1@iserver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Steve Bishop wrote: > I am using FreeBSD 3.3-RELEASE, and it is running on a single processor PII 400. > > At first, I thought the problem was due to the network driver, so I swapped network > cards. But, the problem still continues to occur. At first, I used a DEC (de0) NIC. > Then, I switched to an Intel EtherExpress Pro 10/100B Ethernet (fxp0). > > My machine dies when it runs out of mbufs. Normally, one only associates mbufs with > network usage, and network (NIC) drivers. I have tried to investigate this possibility, > as mentioned, but to no avail. Gah! wrap long lines please! > The problem is either a kernel problem, or is related to the Berkeley DB, and/or > perl module - BerkeleyDB-0.07.pm. I have written to Paul Marquess who is the > author of this perl module. He did not respond, and may not have any idea. The latest > release of this perl module is a significant update to the perl support for the latest releases of Berkeley DB. > It provides for concurrency and database integrity (consistency) between processes sharing > or using the same database simultaneously. > > There are a number of scripts, I have written, in the system that run (as processes) in parallel. > This is why I am using the Concurrent Access Method (CAM) to allow multiple simultaneous > readers along with sequential write (one writer at a time) access. Berkeley DB keeps everything > consistent. > > The scripts are designed to use the database a lot, and they also use a significant amount > of network resources. The scripts sometimes can have up to 900 open tcp connections, > and consistently use almost 600. I have increased the number of mbuf clusters (NMBCLUSTERS) > from 1024 to 4096. I have also increased maxusers to 64. please up maxusers to 256 and NMBCLUSTERS to 32768 or 16384 you may also want to increase the Kernel's memory area via kern.vm.kmem.size in the loader (see LOADER(8)). I would suggest upping maxusers, then NMBCLUSTERS and finally kern.vm.kmem.size in that order inclusive. good luck, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 13:54:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.lppi.com (relay.lppi.com [207.138.32.245]) by hub.freebsd.org (Postfix) with ESMTP id 2D80914F4C for ; Tue, 26 Oct 1999 13:54:23 -0700 (PDT) (envelope-from lew@lppi.com) Date: Tue, 26 Oct 1999 13:54:19 -0700 (PDT) Message-Id: <199910262054.NAA07956@relay.lppi.com> From: Lew Payne To: dg@root.com Cc: hackers@freebsd.org, Joe McGuckin Subject: Re: fxp related kernel panic In-Reply-To: <199910262019.NAA23488@implode.root.com> References: <199910261921.MAA07922@relay.lppi.com> <199910262019.NAA23488@implode.root.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the sake of experimentation, I'll throw in a *real* Pro-100B card and see if it happens again (it takes 8 days for the panic to happen). I can also measure the consistency of this "8 day" phenomena. As an aside, there's not much SCSI activity on this system. I've had very good results with 7200 RPM ATA-66 IDE drives, and kernel tweaks for the wd controller (flags 0xb0ffb0ff): wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16 wd0: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , LBA, DMA, 32-bit, multi-block-16 wd1: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S These IDE drives, in a ccd array, are the ones that get pounded, compared to the "da0" SCSI system drive. Soft-updates are also enabled... (please forward to list if appropriate - I'm not a sub). % iostat 30 10 (truncated) ccd0 da0 wd0 cpu KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 27.61 124 3.34 7.80 108 0.82 19.31 91 1.72 19 0 15 8 57 32.06 115 3.60 7.92 72 0.56 21.26 88 1.83 18 0 13 8 60 25.95 110 2.79 7.99 63 0.49 18.46 81 1.46 15 0 11 6 68 24.84 111 2.70 7.86 55 0.42 17.29 84 1.42 13 0 10 7 71 27.77 118 3.21 7.98 67 0.52 19.18 86 1.62 17 0 13 8 62 25.78 106 2.68 8.05 61 0.48 18.07 77 1.36 13 0 11 7 70 23.61 121 2.79 8.00 71 0.55 16.45 88 1.42 15 0 12 7 66 David Greenman: > I think it is caused by the NCR/Symbios controller. It might be a side > effect of the NCR just using up a lot of PCI bandwidth, with the real > bug being in the fxp driver (though I've looked and haven't found one). > So I don't think putting in a real Pro/100 will have any effect on the > problem. Of course I don't really know what is causing it, so just > about anything is possible. --- Lew Payne Publishing, Inc. Dunn & Bradstreet listed 994 San Antonio Road DUNS # 055037852 Palo Alto, CA 94303 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 16:15: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from screech.weirdnoise.com (adsl-63-194-195-22.dsl.snfc21.pacbell.net [63.194.195.22]) by hub.freebsd.org (Postfix) with ESMTP id C4A8014CEC for ; Tue, 26 Oct 1999 16:14:55 -0700 (PDT) (envelope-from edhall@screech.weirdnoise.com) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id QAA28528; Tue, 26 Oct 1999 16:17:40 -0700 Message-Id: <199910262317.QAA28528@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: dg@root.com Cc: hackers@FreeBSD.ORG, Joe McGuckin , Lew Payne , edhall@yahoo-inc.com Reply-To: edhall@yahoo-inc.com Subject: Re: fxp related kernel panic In-Reply-To: Your message of "Tue, 26 Oct 1999 13:19:45 PDT." <199910262019.NAA23488@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Oct 1999 16:17:40 -0700 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have an application under development at Yahoo! which can provoke a similar crash on an N440BX-based system running 3.3-RELEASE in about half an hour. The application is both disk and network intensive--under test both are pretty close to being maxed out. Although crashes most frequently occur during fxp interrupts, this is not always the case; what IS always the case is that stack variables are getting clobbered. We've been able to compare identical configurations except for SCSI vs. IDE. Only the SCSI (using the on-board Symbios controller) system has failed so far. This failure has been replicated on several boxes (it's not just a single bad board). A 2.2.8 system with identical hardware (including SCSI) running the same application doesn't seem to be failing. More testing is required to establish this pattern with certainty, however. Peter Wemm is up here in Santa Clara and is studying the problem as I write. More information will be upcoming... -Ed Hall edhall@yahoo-inc.com edhall@weirdnoise.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 18:35:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 45D7214FE2 for ; Tue, 26 Oct 1999 18:35:43 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA10381 for ; Tue, 26 Oct 1999 21:35:24 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 26 Oct 1999 21:35:24 -0400 (EDT) From: Chuck Robey To: FreeBSD Hackers List Subject: X11/C++ question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone (anyone, that is, who's coded X11 applications) know how you handle X11 callbacks to C++ object methods? Thanks, ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 18:42:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id C097314C2D for ; Tue, 26 Oct 1999 18:42:14 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id VAA15841; Tue, 26 Oct 1999 21:42:05 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id VAA48948; Tue, 26 Oct 1999 21:42:03 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id VAA31089; Tue, 26 Oct 1999 21:42:03 -0400 (EDT) Date: Tue, 26 Oct 1999 21:42:03 -0400 (EDT) From: Thomas David Rivers Message-Id: <199910270142.VAA31089@lakes.dignus.com> To: chuckr@picnic.mat.net, freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Does anyone (anyone, that is, who's coded X11 applications) know how you > handle X11 callbacks to C++ object methods? > > Thanks, If you mean Xt (and possibly Motif) - the answer is "very carefully." The Xt callbacks are C based, so you typically can't directly call a C++ method. But, you can have an extern "C" block that declares the call back function (the extern "C" basically keeps any name mangling from going on) and then, in that function, invoke the method as appropriate. I believe you do something like: class myclass { void mymethod(void * arg1) { cout << "Ha! I got to the class" << '\n'; }; } extern "C" { void callback_function(arg1) void *arg1; { /* Call the method */ myclass::mymethod(arg1); } } Then, you register "callback_function" as the Xt/Motif callback. I've at least "heard" of doing that kind of thing before... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 18:44:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 10BB914C2D for ; Tue, 26 Oct 1999 18:44:35 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA03864; Wed, 27 Oct 1999 11:14:17 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910270142.VAA31089@lakes.dignus.com> Date: Wed, 27 Oct 1999 11:14:16 +0930 (CST) From: "Daniel O'Connor" To: Thomas David Rivers Subject: Re: X11/C++ question Cc: freebsd-hackers@FreeBSD.ORG, chuckr@picnic.mat.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-99 Thomas David Rivers wrote: > If you mean Xt (and possibly Motif) - the answer is "very carefully." Or you could just use a toolkit written for C++ or with C++ shims already.. ie Qt or GTK.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 18:46:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 3FDB214C2D for ; Tue, 26 Oct 1999 18:46:32 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id VAA16885; Tue, 26 Oct 1999 21:46:11 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id VAA48980; Tue, 26 Oct 1999 21:46:08 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id VAA31164; Tue, 26 Oct 1999 21:46:08 -0400 (EDT) Date: Tue, 26 Oct 1999 21:46:08 -0400 (EDT) From: Thomas David Rivers Message-Id: <199910270146.VAA31164@lakes.dignus.com> To: doconnor@gsoft.com.au, rivers@dignus.com Subject: Re: X11/C++ question Cc: chuckr@picnic.mat.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 27-Oct-99 Thomas David Rivers wrote: > > If you mean Xt (and possibly Motif) - the answer is "very carefully." > > Or you could just use a toolkit written for C++ or with C++ shims already.. ie > Qt or GTK.. > Good point! Also - I think there were some articles on how to do this in the X11 journals... if you happen to have those lying around. And, wasn't there a freely available C++ shim for motif floating around at one time? - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 18:52:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 540A814C2D for ; Tue, 26 Oct 1999 18:52:22 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA04755; Wed, 27 Oct 1999 11:22:09 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910270146.VAA31164@lakes.dignus.com> Date: Wed, 27 Oct 1999 11:22:08 +0930 (CST) From: "Daniel O'Connor" To: Thomas David Rivers Subject: Re: X11/C++ question Cc: freebsd-hackers@FreeBSD.ORG, chuckr@picnic.mat.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-99 Thomas David Rivers wrote: > And, wasn't there a freely available C++ shim for motif floating around > at one time? I don't know.. My X experience begins and ends with Tk :) (Don't like Motif either ;) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 19: 5: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id 603F614FC5 for ; Tue, 26 Oct 1999 19:05:05 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FK800D1XOGAHG@mta3.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Tue, 26 Oct 1999 21:04:59 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id VAA39320; Tue, 26 Oct 1999 21:04:29 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 26 Oct 1999 21:04:29 -0500 From: Chris Costello Subject: Re: X11/C++ question In-reply-to: <199910270142.VAA31089@lakes.dignus.com> To: Thomas David Rivers Cc: chuckr@picnic.mat.net, freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991026210429.Q452@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199910270142.VAA31089@lakes.dignus.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 26, 1999, Thomas David Rivers wrote: > extern "C" { > > void > callback_function(arg1) > void *arg1; > { > /* Call the method */ > myclass::mymethod(arg1); As far as I've seen, you can't directly call a class method without an object. -- |Chris Costello |A closed mouth gathers no feet. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 19:30: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id E7C1D14D6F for ; Tue, 26 Oct 1999 19:29:49 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox.bogus.net (ell430.acadia.net [208.244.135.130]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id WAA05289; Tue, 26 Oct 1999 22:39:59 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox.bogus.net (8.9.3/8.9.3) id WAA00674; Tue, 26 Oct 1999 22:27:40 -0400 (EDT) (envelope-from tbuswell) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 26 Oct 1999 22:27:39 -0400 (EDT) To: Thomas David Rivers Cc: chuckr@picnic.mat.net, freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: <199910270142.VAA31089@lakes.dignus.com> References: <199910270142.VAA31089@lakes.dignus.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14358.24618.511570.857726@localhost.bogus.net> From: tbuswell@acadia.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers writes: > If you mean Xt (and possibly Motif) - the answer is "very carefully." [...] You're approach would probably work, but there's an easier way. See topic 28 in the Xt FAQ. ftp://ftp.x.org/contrib/faqs/FAQ-Xt It's not name mangling causing problems, it's lack of "this" when the method is invoked as a callback from Xt. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 19:45:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6720B14D27 for ; Tue, 26 Oct 1999 19:45:33 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA10564; Tue, 26 Oct 1999 22:44:58 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 26 Oct 1999 22:44:57 -0400 (EDT) From: Chuck Robey To: Thomas David Rivers Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: <199910270142.VAA31089@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Thomas David Rivers wrote: > > > > Does anyone (anyone, that is, who's coded X11 applications) know how you > > handle X11 callbacks to C++ object methods? > > > > Thanks, > > If you mean Xt (and possibly Motif) - the answer is "very carefully." > > The Xt callbacks are C based, so you typically can't directly call a > C++ method. > > But, you can have an extern "C" block that declares the call back > function (the extern "C" basically keeps any name mangling from going on) > and then, in that function, invoke the method as appropriate. > > I believe you do something like: [example deleted] Then you just stick a C wrapper function around every C++ callback you want to register, is that it? Seems a bit inelegant, but I suppose, if the ultimate test of elegance is that "it's the only one that works", then it's perhaps elegant *enough*. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 19:49:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id AAC1814D0F for ; Tue, 26 Oct 1999 19:49:14 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id WAA27423; Tue, 26 Oct 1999 22:49:07 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id WAA49271; Tue, 26 Oct 1999 22:49:05 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id WAA32016; Tue, 26 Oct 1999 22:49:05 -0400 (EDT) Date: Tue, 26 Oct 1999 22:49:05 -0400 (EDT) From: Thomas David Rivers Message-Id: <199910270249.WAA32016@lakes.dignus.com> To: chuckr@picnic.mat.net, rivers@dignus.com Subject: Re: X11/C++ question Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Then you just stick a C wrapper function around every C++ callback you > want to register, is that it? Seems a bit inelegant, but I suppose, if > the ultimate test of elegance is that "it's the only one that works", then > it's perhaps elegant *enough*. I believe someone posted a better solution... from the Xt FAQ. - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 19:49:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D68F1152F5 for ; Tue, 26 Oct 1999 19:49:42 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA10589; Tue, 26 Oct 1999 22:49:02 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 26 Oct 1999 22:49:02 -0400 (EDT) From: Chuck Robey To: "Daniel O'Connor" Cc: Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Daniel O'Connor wrote: > > On 27-Oct-99 Thomas David Rivers wrote: > > If you mean Xt (and possibly Motif) - the answer is "very carefully." > > Or you could just use a toolkit written for C++ or with C++ shims already.. ie > Qt or GTK.. If I wanted to just get X11 done, I would just call some toolkit. I didn't want to be told to go get something else that does it, I wanted to know the right way to do it myself. Thomas's post, at least, was really helpful. I wonder if that's really the way to go, but he surely did give me *one* method, and explained it easily enough so that I can *do* it. Boy, I sure wish Java compiled and ran natively. I'd stop using C++ forever. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 19:54:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6031C14D1F for ; Tue, 26 Oct 1999 19:54:42 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA10609; Tue, 26 Oct 1999 22:54:15 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 26 Oct 1999 22:54:15 -0400 (EDT) From: Chuck Robey To: tbuswell@acadia.net Cc: Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: <14358.24618.511570.857726@localhost.bogus.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999 tbuswell@acadia.net wrote: > > Thomas David Rivers writes: > > If you mean Xt (and possibly Motif) - the answer is "very carefully." > [...] > > You're approach would probably work, but there's an easier way. > See topic 28 in the Xt FAQ. > > ftp://ftp.x.org/contrib/faqs/FAQ-Xt > > It's not name mangling causing problems, it's lack of "this" when the > method is invoked as a callback from Xt. Yes! This is the method! I like it, or at least, it's as close (in C++ code) to something I do like. Thanks very much, Ted. Nice catch. > > -Ted > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 20:39:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73]) by hub.freebsd.org (Postfix) with ESMTP id 5B26414E5C for ; Tue, 26 Oct 1999 20:39:34 -0700 (PDT) (envelope-from bakul@torrentnet.com) Received: from chai.torrentnet.com (localhost [127.0.0.1]) by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id XAA11567; Tue, 26 Oct 1999 23:39:24 -0400 (EDT) Message-Id: <199910270339.XAA11567@chai.torrentnet.com> To: Chuck Robey Cc: tbuswell@acadia.net, Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-reply-to: Your message of "Tue, 26 Oct 1999 22:54:15 EDT." Date: Tue, 26 Oct 1999 23:39:24 -0400 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Allow me add something to what the FAQ-Xt says. I find it more convenient to immediately call a non-static function as shown below (using a slightly modified example from the FAQ). class Icon { public: Icon(Widget*); private: static void static_callback(Icon*); inline void real_callback(); Widget* button; int count; ... }; Icon::Icon(Widget* parent): count(0) { button = XtVaCreateWidget("Boo!", xmPushButtonWidgetClass, parent, 0); XtAddCallback(button, XmNselectCallback, &Icon::static_callback, (XtPointer)this); ... } inline void Icon::real_callback() { count++; ... } void Icon::static_callback(Icon* icon) { icon->real_callback(); } The reason for calling real_callback from static_callback is to avoid having to specify icon->count etc. to reference components of the Icon object. This makes a difference in readability if your callback function does a bunch of stuff. The reason for inlining to not incur the cost of an additional call (if this matters -- usually it doesn't). Inlining can get in your way during debugging (atleast gdb loses its mind) so provide a way to disable it. BTW, this idiom is useful pretty much any time you have to use C++ callbacks from C code, not just for X11. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 21: 9:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 50B4014CCF for ; Tue, 26 Oct 1999 21:09:09 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA10785; Wed, 27 Oct 1999 00:08:31 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 27 Oct 1999 00:08:31 -0400 (EDT) From: Chuck Robey To: Bakul Shah Cc: tbuswell@acadia.net, Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: <199910270339.XAA11567@chai.torrentnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Bakul Shah wrote: > Allow me add something to what the FAQ-Xt says. > > I find it more convenient to immediately call a non-static > function as shown below (using a slightly modified example > from the FAQ). Just got out of the shower, where I was wondering why they didn't suggest the same thing. I was going to experiment with this way, since it fit more closely with the way I like to code C++ (I don't like to code C++, you understand, so my C++ code is always straining to look like C). Thanks, Bakul. This looks much better. Thanks, folks, for letting me pull hackers away from FreeBSD for a minute, but let's not let it get out of hand; we better stop before we strain other's patience. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 21:12:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BFB5152AD for ; Tue, 26 Oct 1999 21:12:05 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11gJEH-0001Sg-00; Tue, 26 Oct 1999 22:54:25 -0400 Date: Tue, 26 Oct 1999 22:54:23 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Chris Costello Cc: Thomas David Rivers , chuckr@picnic.mat.net, freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: <19991026210429.Q452@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Chris Costello wrote: > On Tue, Oct 26, 1999, Thomas David Rivers wrote: > > extern "C" { > > > > void > > callback_function(arg1) > > void *arg1; > > { > > /* Call the method */ > > myclass::mymethod(arg1); > > As far as I've seen, you can't directly call a class method > without an object. Sure you can. It won't have any access to "this" or any part thereof, however. > > -- > |Chris Costello > |A closed mouth gathers no feet. > `---------------------------------- > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 26 21:22: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id B50EB14A18; Tue, 26 Oct 1999 21:22:02 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11gJ6Q-0006v8-00; Tue, 26 Oct 1999 19:46:18 -0700 Date: Tue, 26 Oct 1999 19:46:15 -0700 (PDT) From: Tom To: Steve Bishop Cc: freebsd-database@freebsd.org, freebsd-hackers@freebsd.org, "Paul.Marquess@btinternet.com" Subject: Re: mbuf problem (panic)--possibly related to Berkeley DB 2.7.7 In-Reply-To: <38160B6A.5568F6D1@iserver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Steve Bishop wrote: > The scripts are designed to use the database a lot, and they also use a significant amount > of network resources. The scripts sometimes can have up to 900 open tcp connections, > and consistently use almost 600. I have increased the number of mbuf clusters (NMBCLUSTERS) > from 1024 to 4096. I have also increased maxusers to 64. 4096 isn't really that many mbufs. You should double or triple that. I think that large web hosting people use 20000 mbufs. That eats a LOT of RAM, but at least you can shrug off the heaviest DoS attack. In fact, if you don't specify a number of mbufs in your kernel file, MAXUSERS set to 64 will probably give you more than 4096 mbufs! Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 0:33:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 195EE1530E for ; Wed, 27 Oct 1999 00:33:10 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id KAA04636; Wed, 27 Oct 1999 10:37:38 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id KAA10106; Wed, 27 Oct 1999 10:23:48 +0400 (MSD) Date: Wed, 27 Oct 1999 10:23:48 +0400 (MSD) From: Alexey Zelkin Message-Id: <199910270623.KAA10106@scorpion.crimea.ua> To: rivers@dignus.com (Thomas David Rivers), hackers@FreeBSD.org Subject: Re: X11/C++ question X-Newsgroups: cris.gate.freebsd.hackers In-Reply-To: <199910270142.VAA31089@lakes.dignus.com> User-Agent: tin/pre-1.4-980618 (UNIX) (FreeBSD/2.2.7-RELEASE (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, >> Does anyone (anyone, that is, who's coded X11 applications) know how you >> handle X11 callbacks to C++ object methods? >> >> Thanks, TDR> If you mean Xt (and possibly Motif) - the answer is "very carefully." TDR> The Xt callbacks are C based, so you typically can't directly call a TDR> C++ method. TDR> But, you can have an extern "C" block that declares the call back TDR> function (the extern "C" basically keeps any name mangling from going on) TDR> and then, in that function, invoke the method as appropriate. TDR> I believe you do something like: TDR> class myclass { TDR> void mymethod(void * arg1) { TDR> cout << "Ha! I got to the class" << '\n'; TDR> }; TDR> } TDR> extern "C" { TDR> void TDR> callback_function(arg1) TDR> void *arg1; TDR> { TDR> /* Call the method */ TDR> myclass::mymethod(arg1); TDR> } TDR> } Looks good except one point -- mymethod should be static, i.e. static void mymethod (...) { ... } TDR> Then, you register "callback_function" as the Xt/Motif callback. TDR> I've at least "heard" of doing that kind of thing before... -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 1: 1:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 8B626152C4 for ; Wed, 27 Oct 1999 01:01:23 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id LAA26587; Wed, 27 Oct 1999 11:00:51 +0300 (EEST) (envelope-from will) To: chuckr@picnic.mat.net (Chuck Robey) Cc: hackers@freebsd.org Subject: Re: X11/C++ question References: From: Ville-Pertti Keinonen Date: 27 Oct 1999 11:00:50 +0300 In-Reply-To: chuckr@picnic.mat.net's message of "27 Oct 1999 05:51:21 +0300" Message-ID: <863dux6xn1.fsf@not.demophon.com> Lines: 16 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG chuckr@picnic.mat.net (Chuck Robey) writes: > Boy, I sure wish Java compiled and ran natively. I'd stop using C++ > forever. gcc-2.95.1 + libgcj already works, at least for simple programs. On FreeBSD 3.x programs seem to work as long as you use statically linked libraries (shared libraries cause the garbage collector to dump core). There already seems to be some awt code in libgcj, I have no idea whether it's actually functional. And the speed isn't quite comparable to what you can achieve lower-level languages (pretty close to the equivalent C++ code with all methods virtual, heavy use of rtti and common-base-class-based containers), but probably good enough for a lot of things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 1:34:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web1402.mail.yahoo.com (web1402.mail.yahoo.com [128.11.23.166]) by hub.freebsd.org (Postfix) with SMTP id D0EDE14FAF for ; Wed, 27 Oct 1999 01:34:42 -0700 (PDT) (envelope-from etdebruin@yahoo.com) Message-ID: <19991027083557.22017.rocketmail@web1402.mail.yahoo.com> Received: from [194.245.91.1] by web1402.mail.yahoo.com; Wed, 27 Oct 1999 01:35:57 PDT Date: Wed, 27 Oct 1999 01:35:57 -0700 (PDT) From: =?iso-8859-1?q?eT?= Reply-To: eT@post.com Subject: PCI bus Latency To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings .. When doing a pci_read_config(dev, PCI_LATENCY_TIMER, 4) I get varying values on different hardware configurations. On Machine A the value is 32 and my device driver (using DMA) works fine. On Machine B the value is 64 and my device driver doesn't work fine - there seem s to be these hickups in which the Chip writing to the PCI controller says it ha s finished transferring data but the write counters are still > 0. My card works closely with two network cards in the system. Actually, I reckon I just need some pointers and things to remember when it come s to dealing with latency. Any help? Regards eT ===== Etienne de Bruin http://www.geocities.com/etdebruin __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 1:52:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2A93C1533D for ; Wed, 27 Oct 1999 01:52:31 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11gOoT-0008h1-00; Wed, 27 Oct 1999 10:52:09 +0200 From: Sheldon Hearn To: Robert Watson Cc: mcglk@serv.net, hackers@freebsd.org Subject: Re: Staroffice 5.1 on 3.3-RELEASE (how I ended up getting it to work) In-reply-to: Your message of "Thu, 21 Oct 1999 13:44:47 -0400." Date: Wed, 27 Oct 1999 10:52:09 +0200 Message-ID: <33418.941014329@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Oct 1999 13:44:47 -0400, Robert Watson wrote: > I have not yet figured out how to get rid of the two warning messages at > startup, which are irritating but appear not to actually break anything. http://www.stat.duke.edu/~sto/StarOffice51a/install.html Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 2:35:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id CCF3414FF5 for ; Wed, 27 Oct 1999 02:35:23 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11gPTt-0007e5-00; Wed, 27 Oct 1999 16:34:57 +0700 Date: Wed, 27 Oct 1999 16:34:57 +0700 (ALMST) From: Boris Popov To: Andrey Simonenko Cc: hackers@FreeBSD.ORG Subject: Re: UNILOAD v.1.2 (boot loader/manager) is ready In-Reply-To: <3815E447.76532CF5@comsys.ntu-kpi.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Andrey Simonenko wrote: > I made some days ago UNILOAD v.1.2, the main feature of this version is > the ability to load system from beyond 1024 cylinder mark. Here it is Woo, that feature is _very_ useful. What about incorporating this into FreeBSD's boot code ? Regarding to UNILOAD - it is possible to remove unbootable partitions from boot menu ? -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 2:38:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mpp.pro-ns.net (pppdsle45.mpls.uswest.net [216.160.23.45]) by hub.freebsd.org (Postfix) with ESMTP id 2B56614FF5 for ; Wed, 27 Oct 1999 02:38:08 -0700 (PDT) (envelope-from mpp@mpp.pro-ns.net) Received: (from mpp@localhost) by mpp.pro-ns.net (8.9.3/8.9.3) id EAA13728 for freebsd-hackers@freebsd.org; Wed, 27 Oct 1999 04:38:08 -0500 (CDT) (envelope-from mpp) Date: Wed, 27 Oct 1999 04:38:08 -0500 From: Mike Pritchard To: freebsd-hackers@freebsd.org Subject: xntpd & xcdplayer Message-ID: <19991027043807.A13608@mpp.pro-ns.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed something peculiar over the past week or so with xntpd and I think xcdplayer (from ports). I am running xntpd to keep my clock right. I have an always on DSL connection, so I almost never see any output from xntpd. However, I've noticed that the past few times I've started playing a CD with xcdplayer, I get the following out of xntpd: Oct 27 04:10:44 mpp xntpd[153]: Previous time adjustment didn't complete Which is somewhat odd, because the last message from xntpd about adjusting the time was over 13 hours ago (and it was a 0.129016 s adjustment). Right now I am running a -current kernel from 10/17. The CD drive in question is an ATAPI device. Vendor supplied generic CD drive and builtin IDE on the mother board, so I have no idea what exactly what hardware I have :-(. Usually on the first spin up of the CD after a long period of inactivity, the machine will "pause" (mouse won't move, etc...), so I'm thinking that this might be causing something in the clock code to suffer a small stutter and cause xntpd to print out its message. Normally I ignore whatever xntpd tells me, unless it reports a large time difference. But, tonight when I was checking my mail and decided to listen to a CD while doing so, I got the "Previous time adjustment..." message right away after starting to play the CD. And after thinking back, it seems to me that I see more of around the time when I'm playing CDs, so it seems like the two might be related. It isn't a big deal to me, but I thought I would ask about it. Now, if anyone wants to donate me a nice Adaptec SCSI controller and SCSI CD drive, and maybe a hard drive....:-) -Mike -- Mike Pritchard mpp@FreeBSD.org or mpp@mpp.pro-ns.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 2:57:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.aha.ru (relay2.aha.ru [195.2.64.35]) by hub.freebsd.org (Postfix) with ESMTP id 831BB14BEB for ; Wed, 27 Oct 1999 02:57:44 -0700 (PDT) (envelope-from abb@zenon.net) Received: from pb.hq.zenon.net (pb [195.2.64.18]) by relay2.aha.ru (8.9.3/8.9.3/aha-r/0.04B) with ESMTP id NAA74183 for ; Wed, 27 Oct 1999 13:57:24 +0400 (MSD) Received: from mp.hq.zenon.net (mp [192.168.9.150]) by pb.hq.zenon.net (8.9.3/8.9.3) with ESMTP id NAA59974 for ; Wed, 27 Oct 1999 13:57:24 +0400 (MSD) Received: (from uucp@localhost) by mp.hq.zenon.net (8.9.3/8.9.3) id NAA75519 for ; Wed, 27 Oct 1999 13:57:24 +0400 (MSD) Received: from abb.hq.zenon.net(192.168.9.25) by mp via smap (V1.3) id sma075494; Wed Oct 27 13:57:00 1999 Message-ID: <381704EC.C123F121@zenon.net> Date: Wed, 27 Oct 1999 13:58:04 +0000 From: Alexander Bezroutchko X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-19990918-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: lookup() deadlock in 3.3-stable ? Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have box running 3.3-STABLE which locks up several times per day. After system hangs, ps command in DDB displays a lot of processes in "inode" state. I suspect deadlock occurs:  process 45676 unlink("msg/..") holds lock to "msg" tries to acquire lock to "msg/..", i.e. "."  process 45678 stat("msg") holds lock to "." tries to acquire lock to "msg" How-To-Repeat: 1. create test directory: mkdir t 2. run first process perl -e 'for(;;) { stat("t") || die }' 3. run second process perl -e 'for(;;) { unlink("t/..") || die }' 4. run disk-bound process (one or move) find / > /dev/null I have kernel core and ready to provide additional information. -------------------------------------------------------------------------------- (kgdb) proc 45676 (kgdb) where #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0141c91 in tsleep (ident=0xc2e02400, priority=8, wmesg=0xc01f229b "inode", timo=0) at ../../kern/kern_synch.c:443 #2 0xc013b613 in acquire (lkp=0xc2e02400, extflags=16777216, wanted=1536) at ../../kern/kern_lock.c:145 #3 0xc013b8a0 in debuglockmgr (lkp=0xc2e02400, flags=16842754, interlkp=0xd56529f0, p=0xd54dff40, name=0xc01ea7e3 "vop_stdlock", file=0xc01eaad7 "../../kern/vfs_subr.c", line=1275) at ../../kern/kern_lock.c:343 #4 0xc016234d in vop_stdlock (ap=0xd550cca8) at ../../kern/vfs_default.c:211 #5 0xc01a8ac9 in ufs_vnoperate (ap=0xd550cca8) at ../../ufs/ufs/ufs_vnops.c:2299 #6 0xc016b375 in debug_vn_lock (vp=0xd5652980, flags=65538, p=0xd54dff40, filename=0xc01eaad7 "../../kern/vfs_subr.c", line=1275) at vnode_if.h:811 #7 0xc0164d45 in vget (vp=0xd5652980, flags=65538, p=0xd54dff40) at ../../kern/vfs_subr.c:1275 #8 0xc01a3307 in ufs_ihashget (dev=1048, inum=899385) at ../../ufs/ufs/ufs_ihash.c:113 #9 0xc01a0c23 in ffs_vget (mp=0xc2d05e00, ino=899385, vpp=0xd550cdd0) at ../../ufs/ffs/ffs_vfsops.c:1053 #10 0xc01a3cb2 in ufs_lookup (ap=0xd550ce28) at ../../ufs/ufs/ufs_lookup.c:455 #11 0xc01a8ac9 in ufs_vnoperate (ap=0xd550ce28) at ../../ufs/ufs/ufs_vnops.c:2299 #12 0xc0160f2a in vfs_cache_lookup (ap=0xd550ce84) at vnode_if.h:55 #13 0xc01a8ac9 in ufs_vnoperate (ap=0xd550ce84) at ../../ufs/ufs/ufs_vnops.c:2299 #14 0xc0163429 in lookup (ndp=0xd550cf1c) at vnode_if.h:31 #15 0xc0162ee4 in namei (ndp=0xd550cf1c) at ../../kern/vfs_lookup.c:152 #16 0xc0168135 in unlink (p=0xd54dff40, uap=0xd550cf94) at ../../kern/vfs_syscalls.c:1311 #17 0xc01d1d0b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134537740, tf_esi = 134781872, tf_ebp = -1077946144, tf_isp = -716124188, tf_ebx = 672080476, tf_edx = 134718596, tf_ecx = 1, tf_eax = 10, tf_trapno = 7, tf_err = 2, tf_eip = 672495280, tf_cs = 31, tf_eflags = 514, tf_esp = -1077946192, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #18 0xc01c711c in Xint0x80_syscall () #19 0x280882c4 in ?? () #20 0x28079c3d in ?? () #21 0x280df0be in ?? () #22 0x8048da8 in ?? () #23 0x8048cd5 in ?? () (kgdb) p *(struct lock*)0xc2e02400 $17 = {lk_interlock = {lock_data = 0}, lk_flags = 2098176, lk_sharecount = 0, lk_waitcount = 2, lk_exclusivecount = 1, lk_prio = 8, lk_wmesg = 0xc01f229b "inode", lk_timo = 0, lk_lockholder = 45678, ^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^ lk_filename = 0xc01eaa0c "../../kern/vfs_lookup.c", lk_lockername = 0xc01ea7e3 "vop_stdlock", lk_lineno = 293} (kgdb) p *(char**)0xd550cf94 $18 = 0x8089bb0 "msg/.." (kgdb) -------------------------------------------------------------------------------- (kgdb) proc 45678 (kgdb) where #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0141c91 in tsleep (ident=0xc2e03e00, priority=8, wmesg=0xc01f229b "inode", timo=0) at ../../kern/kern_synch.c:443 #2 0xc013b613 in acquire (lkp=0xc2e03e00, extflags=16777216, wanted=1536) at ../../kern/kern_lock.c:145 #3 0xc013b8a0 in debuglockmgr (lkp=0xc2e03e00, flags=16842754, interlkp=0xd565d4f0, p=0xd5402b80, name=0xc01ea7e3 "vop_stdlock", file=0xc01eaad7 "../../kern/vfs_subr.c", line=1275) at ../../kern/kern_lock.c:343 #4 0xc016234d in vop_stdlock (ap=0xd5493d74) at ../../kern/vfs_default.c:211 #5 0xc01a8ac9 in ufs_vnoperate (ap=0xd5493d74) at ../../ufs/ufs/ufs_vnops.c:2299 #6 0xc016b375 in debug_vn_lock (vp=0xd565d480, flags=65538, p=0xd5402b80, filename=0xc01eaad7 "../../kern/vfs_subr.c", line=1275) at vnode_if.h:811 #7 0xc0164d45 in vget (vp=0xd565d480, flags=2, p=0xd5402b80) at ../../kern/vfs_subr.c:1275 #8 0xc0160e43 in vfs_cache_lookup (ap=0xd5493e3c) at ../../kern/vfs_cache.c:449 #9 0xc01a8ac9 in ufs_vnoperate (ap=0xd5493e3c) at ../../ufs/ufs/ufs_vnops.c:2299 #10 0xc0163429 in lookup (ndp=0xd5493ebc) at vnode_if.h:31 #11 0xc0162ee4 in namei (ndp=0xd5493ebc) at ../../kern/vfs_lookup.c:152 #12 0xc0168690 in stat (p=0xd5402b80, uap=0xd5493f94) at ../../kern/vfs_syscalls.c:1614 #13 0xc01d1d0b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134537728, tf_esi = 134649276, tf_ebp = -1077946352, tf_isp = -716619804, tf_ebx = 672745064, tf_edx = 134649228, tf_ecx = 134852364, tf_eax = 188, tf_trapno = 12, tf_err = 2, tf_eip = 672492080, tf_cs = 31, tf_eflags = 514, tf_esp = -1077946768, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #14 0xc01c711c in Xint0x80_syscall () #15 0x28177e0a in ?? () #16 0x28088a7a in ?? () #17 0x28079c3d in ?? () #18 0x280df0be in ?? () #19 0x8048da8 in ?? () #20 0x8048cd5 in ?? () (kgdb) p *(struct lock*)0xc2e03e00 $6 = {lk_interlock = {lock_data = 0}, lk_flags = 2098176, lk_sharecount = 0, lk_waitcount = 1, lk_exclusivecount = 1, lk_prio = 8, lk_wmesg = 0xc01f229b "inode", lk_timo = 0, lk_lockholder = 45676, ^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^ lk_filename = 0xc01eaad7 "../../kern/vfs_subr.c", lk_lockername = 0xc01ea7e3 "vop_stdlock", lk_lineno = 1275} (kgdb) p *(char**)0xd5493f94 $7 = 0x809c250 "msg" (kgdb) -------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 3: 7:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id F017D14F66 for ; Wed, 27 Oct 1999 03:07:27 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id LAA05458 Wed, 27 Oct 1999 11:07:26 +0100 (BST) Message-ID: <3816CEDD.446B@cs.strath.ac.uk> Date: Wed, 27 Oct 1999 11:07:25 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Is there anything like #ifdef BSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm working with someone porting linux code to FreeBSD. Actually, they want to port it to all BSDs. So, rather than having #if defined (FreeBSD) || defined (NetBSD) || defined (OpenBSD || defined (bsdi) I am looking for a #if defined (BSD) or #ifdef BSD Is there such a beast, and do the other BSDs have it too? If not, I'll just go for the nice and simple #if defined (FreeBSD) || defined (NetBSD) || defined (OpenBSD || defined (bsdi) #define BSD #endif in a global header file. Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 4: 1:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from anon.lcs.mit.edu (anon.lcs.mit.edu [18.26.0.254]) by hub.freebsd.org (Postfix) with SMTP id 6DD5414EE5 for ; Wed, 27 Oct 1999 04:01:29 -0700 (PDT) (envelope-from serge69@nym.alias.net) Date: 27 Oct 1999 11:01:25 -0000 Message-ID: <19991027110125.17132.qmail@nym.alias.net> From: Sergey Subject: Re: fxp related kernel panic To: "Joe McGuckin" , Cc: , References: <199910261818.LAA42698@monk.via.net> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a 3.3-stable machine that I use as a news router (running diablo). The > fxp0 interface averages 10-15 Mbps bandwidth continously. > > About once a week the machine crashes & reboots. We enabled the debugger this time > and captured the following debug output: > Hi! I have similar problem with xl0(3c905B card). This problem happens randomly and doesn't depend on system load. I've found that problem happens in MCLGET macros (mbuf.h) called from xl_newbuf (if_xl.c) on recieving packet. ...... #15 0xc01ecdc6 in trap () #16 0xc01af320 in xl_newbuf () #17 0xc01af479 in xl_rxeof () #18 0xc01afb0b in xl_intr () #19 0xc013fdea in intr_mux () (kgdb) And it is not "out of mbuf" problem: 513/1824 mbufs in use: 317 mbufs allocated to data 196 mbufs allocated to packet headers 257/558/8512 mbuf clusters in use (current/peak/max) 1344 Kbytes allocated to network (43% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines With best regards, Sergey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 4:36:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from babelbrox.axion.bt.co.uk (babelbrox.axion.bt.co.uk [132.146.16.6]) by hub.freebsd.org (Postfix) with ESMTP id 8DBE914F56; Wed, 27 Oct 1999 04:36:32 -0700 (PDT) (envelope-from paul.marquess@bt.com) Received: from cbtlipnt01.btlabs.bt.co.uk by babelbrox.axion.bt.co.uk (local) with ESMTP; Wed, 27 Oct 1999 12:35:28 +0100 Received: by cbtlipnt01.btlabs.bt.co.uk with Internet Mail Service (5.5.2448.0) id ; Wed, 27 Oct 1999 12:35:28 +0100 Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB202D49CA4@mbtlipnt02.btlabs.bt.co.uk> From: paul.marquess@bt.com To: steveb@veriohosting.com, freebsd-database@freebsd.org, freebsd-hackers@freebsd.org Cc: Paul.Marquess@btinternet.com Subject: RE: mbuf problem (panic)--possibly related to Berkeley DB 2.7.7 Date: Wed, 27 Oct 1999 12:35:11 +0100 X-Mailer: Internet Mail Service (5.5.2448.0) MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: steveb@veriohosting.com [mailto:steveb@veriohosting.com] > I am using FreeBSD 3.3-RELEASE, and it is running on a single processor PII 400. > > At first, I thought the problem was due to the network driver, so I swapped network > cards. But, the problem still continues to occur. At first, I used a DEC (de0) NIC. > Then, I switched to an Intel EtherExpress Pro 10/100B Ethernet (fxp0). > > My machine dies when it runs out of mbufs. Normally, one only associates mbufs with > network usage, and network (NIC) drivers. I have tried to investigate this possibility, > as mentioned, but to no avail. > > The problem is either a kernel problem, or is related to the Berkeley DB, and/or > perl module - BerkeleyDB-0.07.pm. I have written to Paul Marquess who is the > author of this perl module. He did not respond, and may not have any idea. I got your original message, but haven't had the time to investigate your problem. After reviewing it and the messages in this thread, as you suspected, I don't have any idea. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 4:52:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from black.nik.gov.pl (black.nik.gov.pl [212.160.156.114]) by hub.freebsd.org (Postfix) with SMTP id 0B6BD14F56; Wed, 27 Oct 1999 04:51:43 -0700 (PDT) (envelope-from dakuc@nik.gov.pl) Received: from green.nik.gov.pl (green.nik.gov.pl [212.160.156.122]) by black.nik.gov.pl (8.9.3+Sun/8.9.1) with ESMTP id NAA22724; Wed, 27 Oct 1999 13:51:55 +0200 (MET DST) Received: from nik.gov.pl (damtest.nik.gov.pl [172.20.11.10]) by green.nik.gov.pl with ESMTP id NAA17522; Wed, 27 Oct 1999 13:50:59 +0200 Message-ID: <3816E73A.F60D5D2D@nik.gov.pl> Date: Wed, 27 Oct 1999 13:51:23 +0200 From: Damian Kuczynski Reply-To: dakuc@nik.gov.pl X-Mailer: Mozilla 4.7 [pl] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: pl, en MIME-Version: 1.0 To: hackers@freebsd.org, ipfw@freebsd.org Subject: Some modifications to natd. proposal Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I use natd + libalias in my test network connected to internet. From my point of view main disadvantage of this program is, that i can't see what' s going on in packet alias engine, (ipfwadm -l -M, or ipfstat -s in ipfilter) so I'm working on patches to natd and libalias which give me that possibility. Can you suggest me, which informations about link should be displayed for links. When I look on alias table, I can see, that some links have non positive expire times calculated as link->expire_time-(timeStamp-link->timestamp) I think, that is a bad idea, and is possible to reinit link, even if it should be deleted from table as expired. For now links a deleted from alias table only as a result of HouseKeeping function called when packet is putted to procesing by alias engine Do links shouldn't be also checked against expirity at least when link is found in. _FindLinkIn Sorry About my Engllsh Best Regards Damian Kuczynski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 6:19:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (oberon.ntu-kpi.kiev.ua [195.178.136.20]) by hub.freebsd.org (Postfix) with ESMTP id 5E8D214BF7 for ; Wed, 27 Oct 1999 06:19:35 -0700 (PDT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (eth0.comsys.ntu-kpi.kiev.ua [10.0.1.184]) by relay1.ntu-kpi.kiev.ua (Postfix) with ESMTP id 471522FA25 for ; Wed, 27 Oct 1999 16:19:32 +0300 (EEST) Received: from comsys.ntu-kpi.kiev.ua (c514-9.comsys.ntu-kpi.kiev.ua [10.18.54.59]) by comsys.ntu-kpi.kiev.ua (8.9.2/8.8.7) with ESMTP id QAA14325 for ; Wed, 27 Oct 1999 16:19:16 +0300 (EEST) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Message-ID: <3816EDD9.6F1FA56C@comsys.ntu-kpi.kiev.ua> Date: Wed, 27 Oct 1999 16:19:38 +0400 From: Andrey Simonenko X-Mailer: Mozilla 4.07 [en] (Win98; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: UNILOAD v.1.2 (boot loader/manager) is ready Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boris Popov wrote: > On Tue, 26 Oct 1999, Andrey Simonenko wrote: > > > I made some days ago UNILOAD v.1.2, the main feature of this version is > > the ability to load system from beyond 1024 cylinder mark. Here it is > Woo, that feature is _very_ useful. Unfortunately I haven't got hard disk where I can install OS on cylinder greater than 1024 and test this feature. _But_ added LBA 'packet' interface works (I think so). I tested UNILOAD on different computers and where IBM/MS INT 13 Extensions are supported, UNILOAD always uses it. > What about incorporating this into FreeBSD's boot code ? FreeBSD boot code (/usr/src/sys/boot/i386/boot0) already uses LBA 'packet' interface and can boot system from beyond 1024 cylinder mark. > Regarding to UNILOAD - it is possible to remove unbootable > partitions from boot menu ? Here it is some lines from file README: -14------------------------------------------------------------------------ Q: I installed UNILOAD and it shows me empty, extended partitions. How to make it don't show such partitions? A: Try to use intellect regime. Press . -15------------------------------------------------------------------------ Q: I used intellect regime and UNILOAD printed 'No bootable entry'. Why? A: UNILOAD forced intellect regime and didn't find any bootable partition. UNILOAD automatically turns off intellect regime and prints all partitions. -16------------------------------------------------------------------------ Q: How does exactly UNILOAD work in intellect regime? A: In intellect regime UNILOAD doesn't show following partitions: partitions with Empty, Extended, Linux swap, BSDI swap fs; partitions without 0xaa55 signature. --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 7:20:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 5E0A814C92 for ; Wed, 27 Oct 1999 07:20:15 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA38990; Wed, 27 Oct 1999 09:19:50 -0500 (CDT) (envelope-from dan) Date: Wed, 27 Oct 1999 09:19:50 -0500 From: Dan Nelson To: Roger Hardiman Cc: hackers@FreeBSD.ORG Subject: Re: Is there anything like #ifdef BSD Message-ID: <19991027091949.A38799@dan.emsphone.com> References: <3816CEDD.446B@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3816CEDD.446B@cs.strath.ac.uk>; from roger@cs.strath.ac.uk on Wed, Oct 27, 1999 at 11:07:25AM +0100 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 27), Roger Hardiman said: > I'm working with someone porting linux code to FreeBSD. Actually, > they want to port it to all BSDs. > > So, rather than having > #if defined (FreeBSD) || defined (NetBSD) > || defined (OpenBSD || defined (bsdi) > > I am looking for a > #if defined (BSD) > or #ifdef BSD Do you know that the code you will be putting inside this #ifdef is BSD-only code (and won't be used by OSF/1, HP-UX, Solaris, etc), or should you rather be using autoconf and checking for specific functions (setproctitle() as an example)? -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 7:34:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D3AB214C92 for ; Wed, 27 Oct 1999 07:34:45 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id KAA13987; Wed, 27 Oct 1999 10:34:06 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 27 Oct 1999 10:34:06 -0400 (EDT) From: Chuck Robey To: Dan Nelson Cc: Roger Hardiman , hackers@FreeBSD.ORG Subject: Re: Is there anything like #ifdef BSD In-Reply-To: <19991027091949.A38799@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Dan Nelson wrote: > In the last episode (Oct 27), Roger Hardiman said: > > I'm working with someone porting linux code to FreeBSD. Actually, > > they want to port it to all BSDs. > > > > So, rather than having > > #if defined (FreeBSD) || defined (NetBSD) > > || defined (OpenBSD || defined (bsdi) > > > > I am looking for a > > #if defined (BSD) > > or #ifdef BSD > > Do you know that the code you will be putting inside this #ifdef is > BSD-only code (and won't be used by OSF/1, HP-UX, Solaris, etc), or > should you rather be using autoconf and checking for specific functions > (setproctitle() as an example)? What make are you using? If it's either a BSD make or a GNU make, then it's smart enough to be able to conditionally set a variable, if a file exists. Look for sys/param.h, and include it if it's there. It has inside it, for all BSD's, the lines: #define BSD 199506 /* System version (year & month). */ #define BSD4_3 1 #define BSD4_4 1 #undef __FreeBSD_version #define __FreeBSD_version 400011 /* Master, propagated to newvers */ The above is from a FreeBSD-current system, but probably, you'd not want to use the __FreeBSD_version. Use the BSD4_3 or BSD4_4, depending on what you're doing. What I'd do is detect the existence of sys/param.h and use it to set HAS_SYS_PARAM_H to 1, and then use that in your files to include sys/param.h. In the sensitive sections of code, condition them against, say, BSD4_4. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 7:35:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id B921015404 for ; Wed, 27 Oct 1999 07:35:30 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11gUAI-0008Kq-00; Wed, 27 Oct 1999 21:35:02 +0700 Date: Wed, 27 Oct 1999 21:35:02 +0700 (ALMST) From: Boris Popov To: Andrey Simonenko Cc: hackers@FreeBSD.ORG Subject: Re: UNILOAD v.1.2 (boot loader/manager) is ready In-Reply-To: <3816EDD9.6F1FA56C@comsys.ntu-kpi.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Andrey Simonenko wrote: > > What about incorporating this into FreeBSD's boot code ? > > FreeBSD boot code (/usr/src/sys/boot/i386/boot0) already uses LBA > 'packet' interface and can boot system from beyond 1024 cylinder mark. Hm, I was not able to do so on the IBM's 13,5Gb drive. BIOS reports that it uses CHS mode, but boot loader was unable to reach FreeBSD partition above 1023 cylinder. Unfortunately I've had only two hours to play with new hardware and can't investigate problem now. > Here it is some lines from file README: > -14------------------------------------------------------------------------ > > Q: I installed UNILOAD and it shows me empty, extended partitions. > How to make it don't show such partitions? > A: Try to use intellect regime. Press . > -15------------------------------------------------------------------------ Why not to made an 'intellect' mode as default ? It would be much less confusing :). In any way, thanks for a good program. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 8:30:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 098C514FFE for ; Wed, 27 Oct 1999 08:30:16 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id LAA01867 for ; Wed, 27 Oct 1999 11:28:41 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Wed, 27 Oct 1999 11:28:41 -0400 (EDT) From: Chuck Youse To: freebsd-hackers@freebsd.org Subject: UFS ACLs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I admittedly haven't done much homework on this topic, but I was wondering if anyone has played with the idea of implementing ACLs on top of UFS. One of the weakest areas in UNIX is its lack of fine-grained access control for resources - the biggest resource being, of course, the filesystem. Chuck Youse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 8:51:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 813FE1515B for ; Wed, 27 Oct 1999 08:51:17 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id LAA98056; Wed, 27 Oct 1999 11:51:12 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <199910271551.LAA98056@blackhelicopters.org> Subject: Re: UFS ACLs In-Reply-To: from Chuck Youse at "Oct 27, 1999 11:28:41 am" To: cyouse@paradox.nexuslabs.com (Chuck Youse) Date: Wed, 27 Oct 1999 11:51:12 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I admittedly haven't done much homework on this topic, but I was wondering > if anyone has played with the idea of implementing ACLs on top of UFS. > > One of the weakest areas in UNIX is its lack of fine-grained access > control for resources - the biggest resource being, of course, the > filesystem. > > Chuck Youse Chuck -- Go do your homework. :) Check the freebsd-security archive for copious, endless discussions on this subject, requirements therefore, etc. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 8:56: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mobil.surnet.ru (mobil.surnet.ru [195.54.2.7]) by hub.freebsd.org (Postfix) with ESMTP id A5F00153FF; Wed, 27 Oct 1999 08:55:21 -0700 (PDT) (envelope-from ilia@cgilh.chel.su) Received: (from uucgilh@localhost) by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id VAA03509; Wed, 27 Oct 1999 21:50:24 +0600 (ESS) Received: (from uucp@localhost) by cgilh.chel.su (8.8.7/8.8.7) with UUCP id VAA00802; Wed, 27 Oct 1999 21:46:58 +0600 Received: from localhost (ilia@localhost) by localhost.cgu.chel.su (8.9.3/8.9.2) with ESMTP id VAA00405; Wed, 27 Oct 1999 21:33:23 +0600 (ESS) (envelope-from ilia@cgilh.chel.su) X-Authentication-Warning: localhost.cgu.chel.su: ilia owned process doing -bs Date: Wed, 27 Oct 1999 21:33:20 +0600 (ESS) From: Ilia Chipitsine X-Sender: ilia@localhost.cgu.chel.su To: questions@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: why FFS is THAT slower than EXT2 ? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1024619076-941038400=:390" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1024619076-941038400=:390 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT -----BEGIN PGP SIGNED MESSAGE----- Well, guys, listen :-) I and my friends mentioned that "FreeBSD + ffs" is often slower (THAT slower) than "Linux + ext2" for number of tasks: rm, find, tar ... for IDE & SCSI disks. I didn't try things like "FreeBSD + ext2" or "Linux + ffs". I attached here results of the test I performed. For test I "gunzip"ped FreeBSD ports collection, in attachment You can find "scripted" output of "# time sh install.sh" for both systems. Also there are "dmesg" outputs. machine was THE SAME: read "dmesg", FreeBSD-3.3 + softupdates + "# tunefs -o time" + "flags 0xb0ffb0ff" (kernel was compiled with "-O2") Linux - RedHat-6.0 with out_of_box_kernel, just "# hdparm -d 1 -c 3 -m 16 /dev/hda", read "hdparm" output... even as non-native English speaker I know few other other words which begin with "f" :-) is "fast" the propriate one for "ffs" ? Regards, (îÁÉÌÕÞÛÉÅ ÐÏÖÅÌÁÎÉÑ) Ilia Chipitsine (éÌØÑ ûÉÐÉÃÉÎ) -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQB1AwUBOBcbQuRxlWKN2EXhAQHHqgL+K+2O8gkv1kYs8AhsqbMsIFTG5u7gfzcT oqqhKlTUlTtaKtAl6g/CnKsPpxfh0CaMEmQC+5bzqSa4MnZcyHwiAWlrNLRlU08A DfYJQRGa/6S5OiaJVYnsAuKnbr6tLZGZ =YWer -----END PGP SIGNATURE----- --0-1024619076-941038400=:390 Content-Type: APPLICATION/octet-stream; name="wtf.tar.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="wtf.tar.gz" H4sICIMXFzgCA3d0Zi50YXIA7Vl9b9vI0c+/JZDvMMjhUAuRqF2+SsQleGRJ TvQkslVLTlMUB2NFLiWeKJLHJW3rPv0zs6RkO73eAQVyRfuEgCi+zM7Ozs7r j9Feqo35Mcnqhxdf6+CMeY4DL4AO9sU/gONxC8BnzPW47XAOwLntey+AvfgD jlpVogR4UeZ59Vt091sp0xf/dYfeebiTpUryDCzTMt0ed+GM1PE/RV7uDmYk 72RqljLaisoM830HzjZheBojN6HqWeaQm54HfDgcMps7/YbvmX7JTW5aUMpU CiU7HfiOwxwHjooS6cGyAosHbAjTyUqPNyaykmElI+C2bfmW6zrw/hcoyjyU SuWlaYzzTOWpDCDM07wu4dO70WsYsAfLNcYiTdalqJJsA5FMxQHSPC9M0wTX NpkD5/kmn88WS2Mu93l5CIA7jm/t+tyzB84OxJ1IUrFOJZwNh94OdrLMZIrz RLILDrd2uAwlyzsZ4a2DAyJRiS54bAdJllQd49PFMoBJonY/13kl1ElLEd3f eqZjMk2ZoJy/yMgYL24CmGUVTrKQWZXUe/Bd6IHFGKhKFgUthHnGeCvDHV3b A69vD3wUqS5SfEBLu/rQhYvFDdSKKORDKIuKJuUeyLLMSxQat5J0Yj4y+vM2 rf6MsqiqrEMibziZxnNp7pNqCxcM2AWs6w1Kdo9GIcq8ziKQGakqMo3F1XL2 GUXK4rzciyyUUEml92B9gJvL2cXss7EYzwLAE5zPrpYo0V3SmhxnyKgqDyAq YA/x2vZZQ3yjl0Nck01Ne4rk1aGQwFtmZb4mCmK6FWV0L0ppNIZ3OV2RplEc aB6gZRvnaH4R1AWyWd6LTEkBN1mid6g6wDjfF3UlS1jmYSLxAfJAk7GHBjEL iPQBonwvkgxUHu5kpYA/m6OZ1Gzpm2er8aI/W5wIGxIDn6DwVY72q3D7x/NF F24meELyLszezRe4C62R0AqvV5DJCrd7105tLDFqaQXv1L0oIrjDKVx4dJ3F sm+hl9VKwgK33jSWskR2EJW04JNZOqblN1s8H13+7XZxdb1awvzm42pGl7B8 P7qe3s6u/3LcaqOqDks0Tb1VzI4HcJaUP8MbcDqQKBBocq7LRg0Zb8msRzL7 OVlRoQdarqeVOxwA3qvThuNsotgHjb0cBaZIcpGKjSLGPpxNnq+Hm8OOcS1x oatkL2GcorbgSIObMDSuR3OI0D+PmnjijAGQxxwJFOQxOGzofQCFb43FbPbZ xs2aTEnCqszTFIfjnGR+6xoFYhhx7gANpiXN8gow930PGdrunYQ9RpEAtZ2m FMzWElAnClKBRmdQIkwiyXC5895kPmqdgTHW039+t9GDkhVtO1rNNhJBkeRd vFjTxZEF/wcWg4ZF/CsswiOLSLMgnvCXm9Hl6maOxO8urq5W3BqwURdGqxFM ZssPjd4MmhTOxxOwnM9zGE9611dzTbSY4R3etHS0pkYQHtNSeOx32YMde6Q5 sgnu/Nas3LK8+Tnc9wf+7hzGItxiHB6/X77xLLvvOX3PbiRpJkZZWlGa2Wn8 4DjOQBuj8PRUvBKu2ziEZmi6jnGR5kVxaF6eqU4AccTIYrnpOHPjYjIG1hhw kauqh9mKw8Bivm/soyNHZg4Zevt89Pl2PrmdTD8t36CFd/WD6+no4xtuGaVI IjeAPSbEutRBjqKyqvd7ulGFRNvH3RyUEg2dDjRNzIYD02Y2zM/7Sob03raO BPq9hdZvseP7JhnEQlEohrjOdJAPWqZnz7l1DBWqBNkw2OLKlHm8j44BpcJ0 lpq4TjMMtEPk8dk+Km5VXcjytupQDEBnMRYUl3So1msKDG2odOJ0suAH+nPp 5MFbQ9RV3syh49xoNgFRluKg9JuyzgDTkkGp6Xg/ubqcmk2exfiWkWxUrGCt 8VBZECepVAdcM5YppRRRnqUH07gopST+dVZTCmiz+r4tASh7xyXpfBRFRIbZ oUCDsLiDbyi+9lQhMKmdFWWSl5QsevxJqseVimwjH3VF+R7tCkeQ+Z/ZXc/p GLPlFQw9j8H0oZIZ2Rx64PX1bHFLZjQy/j313zYqRLn/ug3A79T/4Fh2W//7 loc1Gtb/ru1/q///iMPoo6X2yUUN2NdpFZJL0aa8oS06y+O4Y8CsfwXo51RD 6hc2nNlWb51UGJjVIcPogZ61F2pHAf2LsToM3UZ70b7g+CLD5zspi2MmejYg y++xaG1N4+mLozv/6guxxVP7YtBOsZH5XlJh2Tw/pYwupsAQgwnNa7mcD20M z2QGFT5gxov/T0eFZdJXbv9/1/9dfvJ/x/d0/2/Z7Jv//xHHMiyTomqsv8lc f8W/q7ACbAz4IGB2gNFZt+V/15gAVtQipRoBqn3x43dABgRqqxtJkaam2r40 MMOVosnoFDMUIPc1vkSiKod+rcqXBrdN38VsXGIFaLrDJmfjzgecm/4AO/eC MrXzPTbIcMbE3abC/P6aLqjlBrYXD9iKY37Nqs7upcGSDLs39ZrldUUXcGY5 HhL9lJevXXeIdVVedgqxkbHAKIfFOqV19fKfLEo+JNVLozkbrYow9sh/1A/3 A4s3+vmP3P9I439UH50vJ1/d/7nv8qf/Lf7n2o/4H7PI/31m/cH+n6SJ+G06 bDH/+/x/nBeHMtlssX4OO2THFnU1Q2gtAmZZSHjbc6KB1aWzp89DOg+5PtvG n1ZbiU3VBt1SN9AV3j4BWfAJIXTYh2WJMGGEMUEzVidcrSnWaWrbtHvX04/T 0XIK3zkBLLGN1I5nAxsGjhXYDN7NW8yQDEm78k9SqSQUZripTexAMCDVAUWc vipDLFZUP8z3BTYJ/f+dLpez8cggoEBXPRiKXiUDy3VeAbUDP9cyCw9A5QEf WPD+l+eUq+X4OZ1tW97Q8jlRalSvRdD6C9cZU79lm5bfm7//BdyB1wtToRQg HdYpcIU6SDIsPl69k1mdZFJDcMh+FlFF8uBaHsDyiAZiJYNjLqSoalTaG+yp 1/EPF4ub7qf5tDuZdhfLaRel686X1935eNodfx68NUrCRJqGh2oh7vm+b3EP 5SLg8wOsD9gmdgyNfx7pkMyxeEtmD56QLUqZ5iLCSCjT+NhOvWr+XzXtfsgs F32amcYRpiP8q2mL1DPYJDDCbVKwAH5okMeB5dj+p8+aIKTO/SjPI+zylvBD DS0RpyJMsOM2mebDn/Cxfb4813ww7cyWI1iXSbSRp9H8NNrH0ZhLbunmxEDD OHBeq96euujyC+znxIY9YcONu40gFksbVtgtwqYUxTYJFYgwlDhKYOF5HIlB ETMiiAYIeZQGcyMzZERLuZxaqES9hin6EioYnZAArpXcwYBZw84TMZ4we5SJ u0dmIorQYAioCkIWRHEgB4FvBzH6sYZV27nQJABr+w4827lFtjjuXmCMl5dY yH+SWZSTVgIYrz4y5jP4O3ugTR+ETP4ILeTIHuL20Birpl9cLtbMioneitcs Yg7/8Z8ZCoUQvXk1zqxCvbJECboMCPrXXwFK+AHFvkvKqhaE1+sPBKoLMWGF 6CPsLeqAaUgu1ti1NlJrwAxR7dZR2IJUHmFUXkxT7HPS9zoXZdTQsEazx+kL tX/Cz8CGvuVhxwS42bhconcaEQgAe5QcaYMWym6AUHzSoqWWHm21o+0nQ/jz IfFJaFsja3bs6yEeRHi2jgOJLICL2cXVEcPtYoOk/Rg1i/awzdMIqZBIg1zn GHfdJDPuT+xPwF2L150WtGZxTL/jVPd6qjrDvhCt6D5iHTTgX8P13nbh4/mo C5M5nppOsqu7z6S3JsS2N0BeJFCD/p21Tdqxbet0qZeD8JDiBnsOUOtHVzYs +6suthMWnPeXT8XBphOLxiIhgb4ALfufptf0dQBlKjHM3JGKuo2zdgHb1i4k eRkdDBGSRBrjawA6LGI49OijkPtBY2gabfxw3sSslr7tmgmjov6U9k8FNPNk 1FKM6ijJAyhScehiN+rCXZ7WWFKn9NVNtURzSRBTovYByJ9QCfoLFdbYh9P7 CDMNIc79dSqyHQHYIZXkCX23qjNSqoxII/xLF8BSyyiKkyn5A73L/mmTnZPV ElUAmKHQrUOgWKsoGF3Ozs8/TnvUmXdwShhfzRej1QyfacDbSIuK4uGmHVeU CSXQtzo+FToBtCQUdMuyLqqe1nKmewecNXk2XJTYSGBwTvr5Mx4Udts1rLU7 RDHsKeLhE8Eoru0JtcQ8zZl/8o6seGBfOjs9Q2kuV/Q1QAsbi1B+8VnsiPV1 j40PBa4nn8Yohl2w5qOZofFBItBAZQsNYkpCI1eWMP46ur6cXb4LoA/3QukN Ksq8kGV6oI3cNyjn1+kvdP//dcv/36v/wXYfv//bju7/XW5/q///Pf3/qpZN me1Rf+taAW/7/7/lNWwFfcfCGtF8afzrvb+FHX8Nw4HpK5wmcJnpDMA3ve+x qfZfc8b9HVYwQ4u95tgKDjwso7hbxK/ZPc3atOXH/y/b86fiDwOLYaPwH9ye fzu+Hd+Ob8dXO/4POfDfCgAoAAA= --0-1024619076-941038400=:390-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9: 7:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 2DE4F15061; Wed, 27 Oct 1999 09:07:38 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id MAA01924; Wed, 27 Oct 1999 12:05:50 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Wed, 27 Oct 1999 12:05:50 -0400 (EDT) From: Chuck Youse To: Ilia Chipitsine Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the biggest reasons for the difference: FreeBSD, by default, performs _synchronous_ metadata updates, and Linux performs asynchronous metadata updates. =20 It's definitely a bit slower, but the payoff is in reliability. I have seen more than one [production!] Linux machine completely trash its filesystems because the implementors decided that their "NT-killer" must have good performance at the expense of serious, production-quality reliability. Chuck On Wed, 27 Oct 1999, Ilia Chipitsine wrote: > -----BEGIN PGP SIGNED MESSAGE----- >=20 > Well, guys, listen :-) >=20 > I and my friends mentioned that "FreeBSD + ffs" is often slower > (THAT slower) than "Linux + ext2" for number of tasks: > rm, find, tar ... for IDE & SCSI disks. >=20 > I didn't try things like "FreeBSD + ext2" or "Linux + ffs". >=20 > I attached here results of the test I performed. For test I "gunzip"ped > FreeBSD ports collection, in attachment You can find "scripted" output of= =20 > "# time sh install.sh" for both systems. Also there are "dmesg" outputs. >=20 > machine was THE SAME: read "dmesg", >=20 > FreeBSD-3.3 + softupdates + "# tunefs -o time" + "flags 0xb0ffb0ff" > (kernel was compiled with "-O2") > Linux - RedHat-6.0 with out_of_box_kernel, just=20 > "# hdparm -d 1 -c 3 -m 16 /dev/hda", read "hdparm" output... >=20 > even as non-native English speaker I know few other other words which > begin with "f" :-)=20 > is "fast" the propriate one for "ffs" ? >=20 > Regards, (=EE=C1=C9=CC=D5=DE=DB=C9=C5 =D0=CF=D6=C5=CC=C1=CE=C9=D1) >=20 > Ilia Chipitsine (=E9=CC=D8=D1 =FB=C9=D0=C9=C3=C9=CE) >=20 > -----BEGIN PGP SIGNATURE----- > Version: 2.6.3ia > Charset: noconv >=20 > iQB1AwUBOBcbQuRxlWKN2EXhAQHHqgL+K+2O8gkv1kYs8AhsqbMsIFTG5u7gfzcT > oqqhKlTUlTtaKtAl6g/CnKsPpxfh0CaMEmQC+5bzqSa4MnZcyHwiAWlrNLRlU08A > DfYJQRGa/6S5OiaJVYnsAuKnbr6tLZGZ > =3DYWer > -----END PGP SIGNATURE----- >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:11:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 3A0AE15407; Wed, 27 Oct 1999 09:11:28 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id MAA95118; Wed, 27 Oct 1999 12:16:37 -0400 (EDT) Date: Wed, 27 Oct 1999 12:16:37 -0400 (EDT) From: Ben Rosengart To: Chuck Youse Cc: Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Chuck Youse wrote: > One of the biggest reasons for the difference: FreeBSD, by default, > performs _synchronous_ metadata updates, and Linux performs asynchronous > metadata updates. > > It's definitely a bit slower, but the payoff is in reliability. I have > seen more than one [production!] Linux machine completely trash its > filesystems because the implementors decided that their "NT-killer" must > have good performance at the expense of serious, production-quality > reliability. Read the post again -- they were using soft updates. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:30:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E03A15401; Wed, 27 Oct 1999 09:30:16 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id KAA677849; Wed, 27 Oct 1999 10:29:54 -0600 (MDT) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 27 Oct 1999 10:29:54 -0600 From: "Ronald G. Minnich" To: Chuck Youse Cc: Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Chuck Youse wrote: > One of the biggest reasons for the difference: FreeBSD, by default, > performs _synchronous_ metadata updates, and Linux performs asynchronous > metadata updates. > > It's definitely a bit slower, but the payoff is in reliability. I have > seen more than one [production!] Linux machine completely trash its > filesystems because the implementors decided that their "NT-killer" must > have good performance at the expense of serious, production-quality > reliability. To put it slightly more strongly: as far as I'm concerned ext2 is not a serious fs if you really care about handling power failures and other such fun things. In clusters as small as 64 machines I've measured a 5% probability that after a power failure one of the 64 ext2 file systems will have a trashed root file system. With freebsd, over a four-year span, running through lots of power outages, I didn't lose an FFS file system even *once* (except for the disk that burned up, but not even FFS can fix that one). ext2 needs a lot of help. Evidently it will be getting it soon, though. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:32: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A582D15401; Wed, 27 Oct 1999 09:31:56 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA15358; Wed, 27 Oct 1999 12:30:52 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 27 Oct 1999 12:30:52 -0400 (EDT) From: Chuck Robey To: Ben Rosengart Cc: Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Ben Rosengart wrote: > On Wed, 27 Oct 1999, Chuck Youse wrote: > > > One of the biggest reasons for the difference: FreeBSD, by default, > > performs _synchronous_ metadata updates, and Linux performs asynchronous > > metadata updates. > > > > It's definitely a bit slower, but the payoff is in reliability. I have > > seen more than one [production!] Linux machine completely trash its > > filesystems because the implementors decided that their "NT-killer" must > > have good performance at the expense of serious, production-quality > > reliability. > > Read the post again -- they were using soft updates. Why is that important? Soft updates is still far better than an async filesystem. Have you lost files in panics? I haven't. > > -- > Ben Rosengart > > UNIX Systems Engineer, Skunk Group > StarMedia Network, Inc. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:33:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id EF6161547D; Wed, 27 Oct 1999 09:33:49 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id MAA35323; Wed, 27 Oct 1999 12:35:17 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Wed, 27 Oct 1999 12:35:17 -0400 (EDT) From: Don To: Ben Rosengart Cc: Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is actually a discussion beginning on freebsd-fs about the possibilty to starting a journaled file system project. Perhaps the speed issues (as well as the ACL's issues) could be discussed there? -don On Wed, 27 Oct 1999, Ben Rosengart wrote: > On Wed, 27 Oct 1999, Chuck Youse wrote: > > > One of the biggest reasons for the difference: FreeBSD, by default, > > performs _synchronous_ metadata updates, and Linux performs asynchronous > > metadata updates. > > > > It's definitely a bit slower, but the payoff is in reliability. I have > > seen more than one [production!] Linux machine completely trash its > > filesystems because the implementors decided that their "NT-killer" must > > have good performance at the expense of serious, production-quality > > reliability. > > Read the post again -- they were using soft updates. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:40:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 7A67E15563; Wed, 27 Oct 1999 09:39:59 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id MAA95328; Wed, 27 Oct 1999 12:44:42 -0400 (EDT) Date: Wed, 27 Oct 1999 12:44:42 -0400 (EDT) From: Ben Rosengart To: Chuck Robey Cc: Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Chuck Robey wrote: > On Wed, 27 Oct 1999, Ben Rosengart wrote: > > > On Wed, 27 Oct 1999, Chuck Youse wrote: > > > > > One of the biggest reasons for the difference: FreeBSD, by default, > > > performs _synchronous_ metadata updates, and Linux performs asynchronous > > > metadata updates. > > > > > > It's definitely a bit slower, but the payoff is in reliability. I have > > > seen more than one [production!] Linux machine completely trash its > > > filesystems because the implementors decided that their "NT-killer" must > > > have good performance at the expense of serious, production-quality > > > reliability. > > > > Read the post again -- they were using soft updates. > > Why is that important? Soft updates is still far better than an async > filesystem. Have you lost files in panics? I haven't. What panics? I've been running -stable and it's been living up to the name. I was pointing out to Chuck Youse that BSD metadata writes are also (mostly) asynchronous now, so if FFS is truly slower than ext2fs, there must be some other reason. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:44:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 44CDC14CD4; Wed, 27 Oct 1999 09:44:38 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id MAA15407; Wed, 27 Oct 1999 12:43:53 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 27 Oct 1999 12:43:52 -0400 (EDT) From: Chuck Robey To: Ben Rosengart Cc: Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Ben Rosengart wrote: > On Wed, 27 Oct 1999, Chuck Robey wrote: > > > On Wed, 27 Oct 1999, Ben Rosengart wrote: > > > > > On Wed, 27 Oct 1999, Chuck Youse wrote: > > > > > > > One of the biggest reasons for the difference: FreeBSD, by default, > > > > performs _synchronous_ metadata updates, and Linux performs asynchronous > > > > metadata updates. > > > > > > > > It's definitely a bit slower, but the payoff is in reliability. I have > > > > seen more than one [production!] Linux machine completely trash its > > > > filesystems because the implementors decided that their "NT-killer" must > > > > have good performance at the expense of serious, production-quality > > > > reliability. > > > > > > Read the post again -- they were using soft updates. > > > > Why is that important? Soft updates is still far better than an async > > filesystem. Have you lost files in panics? I haven't. > > What panics? I've been running -stable and it's been living up to the > name. > > I was pointing out to Chuck Youse that BSD metadata writes are also > (mostly) asynchronous now, so if FFS is truly slower than ext2fs, there > must be some other reason. It felt like it was a comment on the filesystem reliability (the subject of the immediately preceding paragraph). I didn't see how softupdates hurt that reliability. > > -- > Ben Rosengart > > UNIX Systems Engineer, Skunk Group > StarMedia Network, Inc. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:45:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 0EF001542A; Wed, 27 Oct 1999 09:45:20 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id RAA99444; Wed, 27 Oct 1999 17:44:54 +0100 (BST) (envelope-from geoffb) Date: Wed, 27 Oct 1999 17:44:54 +0100 From: Geoff Buckingham To: Ben Rosengart Cc: Chuck Robey , Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991027174454.A99169@chuggalug.clues.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Ben Rosengart on Wed, Oct 27, 1999 at 12:44:42PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 27, 1999 at 12:44:42PM -0400, Ben Rosengart wrote: > On Wed, 27 Oct 1999, Chuck Robey wrote: > > > On Wed, 27 Oct 1999, Ben Rosengart wrote: > > > > > On Wed, 27 Oct 1999, Chuck Youse wrote: > > > > > > > One of the biggest reasons for the difference: FreeBSD, by default, > > > > performs _synchronous_ metadata updates, and Linux performs asynchronous > > > > metadata updates. > > > > > > > > It's definitely a bit slower, but the payoff is in reliability. I have > > > > seen more than one [production!] Linux machine completely trash its > > > > filesystems because the implementors decided that their "NT-killer" must > > > > have good performance at the expense of serious, production-quality > > > > reliability. > > > > > > Read the post again -- they were using soft updates. > > > > Why is that important? Soft updates is still far better than an async > > filesystem. Have you lost files in panics? I haven't. > > What panics? I've been running -stable and it's been living up to the > name. > > I was pointing out to Chuck Youse that BSD metadata writes are also > (mostly) asynchronous now, so if FFS is truly slower than ext2fs, there > must be some other reason. > I heard talk the linux folks where using btrees to better handle large directories. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 9:51:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 7B87A14EAD; Wed, 27 Oct 1999 09:51:17 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id LAA89564; Wed, 27 Oct 1999 11:50:56 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 27 Oct 1999 11:50:56 -0500 (CDT) From: David Scheidt To: Chuck Robey Cc: Ben Rosengart , Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Chuck Robey wrote: > > > > Read the post again -- they were using soft updates. > > Why is that important? Soft updates is still far better than an async > filesystem. Have you lost files in panics? I haven't. > Soft updates should get you most of the speed that async updates do. I have lost cylinder groups in panics on systems with soft-updates. (I was using a very buggy kernel module, so things were *hosed*). The original poster hasn't really provided enough information to know what is going on, and what the performance problem is. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 10: 2:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id CEE2014A15; Wed, 27 Oct 1999 10:02:34 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Oct 1999 18:02:33 +0100 (BST) Date: Wed, 27 Oct 1999 18:02:33 +0100 From: David Malone To: Ilia Chipitsine Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991027180233.A20602@gosset.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 27, 1999 at 09:33:20PM +0600, Ilia Chipitsine wrote: I did a similar test ages ago, only I was extracting a version of the Linux kernel. The FreeBSD machine came out about 10% faster, despite the fact it was running squid and had an older, slower disk. FreeBSD: 112.95 109.00 112.14 109.71 111.68 111.41 111.88 Linux: 122.99 122.11 123.35 121.88 121.70 123.47 124.94 I think what you're seeing is the fact that ports is an extream case. If you want to put a system which tries to keep metadata consistant through hell then create lots of small files! You could try and see how working without soft updates and working async changes the timings. (Also - make sure you've set up softupdates correctly - it is quite easy to think you've turned softupdates on and actually have them off!) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 10: 9:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6CC4814A15; Wed, 27 Oct 1999 10:09:05 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA02104; Wed, 27 Oct 1999 19:08:47 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910271708.TAA02104@freebsd.dk> Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: from Ilia Chipitsine at "Oct 27, 1999 09:33:20 pm" To: ilia@cgilh.chel.su (Ilia Chipitsine) Date: Wed, 27 Oct 1999 19:08:47 +0200 (CEST) Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Ilia Chipitsine wrote: > > FreeBSD-3.3 + softupdates + "# tunefs -o time" + "flags 0xb0ffb0ff" > (kernel was compiled with "-O2") Hmm, if you didn't do a "tunefs -n enable" you are not using softupdates and there is your reason why FreeBSD is slower.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 10:27:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 096F914F5B for ; Wed, 27 Oct 1999 10:27:51 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA27499; Wed, 27 Oct 1999 10:27:42 -0700 (PDT) (envelope-from dillon) Date: Wed, 27 Oct 1999 10:27:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199910271727.KAA27499@apollo.backplane.com> To: Alexander Bezroutchko Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: lookup() deadlock in 3.3-stable ? References: <3817008F.4779686C@zenon.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi : :I have box running 3.3-STABLE which locks up several times per day. :After system hangs, ps command in DDB displays a lot of processes :in "inode" state. I suspect deadlock occurs: : : process 45676 unlink("msg/..") : holds lock to "msg" : tries to acquire lock to "msg/..", i.e. "." : : process 45678 stat("msg") : holds lock to "." : tries to acquire lock to "msg" : :How-To-Repeat: : 1. create test directory: : mkdir t : 2. run first process : perl -e 'for(;;) { stat("t") || die }' : 3. run second process : perl -e 'for(;;) { unlink("t/..") || die }' : 4. run disk-bound process (one or move) : find / > /dev/null : :I have kernel core and ready to provide additional information. Well, the system isn't supposed to lockup so this is a bug. It's because ufs_lookup isn't expecting someone to try to delete (or rename for that matter) ".." and so is not doing the normal lock fixups required when traversing "..". Please try the following untested patch. If it works for you I'll commit it into both -current and -stable. -Matt Index: ufs_lookup.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_lookup.c,v retrieving revision 1.26.2.1 diff -u -r1.26.2.1 ufs_lookup.c --- ufs_lookup.c 1999/08/29 16:33:22 1.26.2.1 +++ ufs_lookup.c 1999/10/27 17:25:27 @@ -452,7 +452,11 @@ *vpp = vdp; return (0); } + if (flags & ISDOTDOT) + VOP_UNLOCK(vdp, 0, p); /* race to get the inode */ error = VFS_VGET(vdp->v_mount, dp->i_ino, &tdp); + if (flags & ISDOTDOT) + vn_lock(vdp, LK_EXCLUSIVE | LK_RETRY, p); if (error) return (error); /* @@ -481,7 +485,7 @@ * regular file, or empty directory. */ if (nameiop == RENAME && wantparent && (flags & ISLASTCN)) { - if (error = VOP_ACCESS(vdp, VWRITE, cred, cnp->cn_proc)) + if ((error = VOP_ACCESS(vdp, VWRITE, cred, cnp->cn_proc)) != 0) return (error); /* * Careful about locking second inode. @@ -489,7 +493,11 @@ */ if (dp->i_number == dp->i_ino) return (EISDIR); + if (flags & ISDOTDOT) + VOP_UNLOCK(vdp, 0, p); /* race to get the inode */ error = VFS_VGET(vdp->v_mount, dp->i_ino, &tdp); + if (flags & ISDOTDOT) + vn_lock(vdp, LK_EXCLUSIVE | LK_RETRY, p); if (error) return (error); *vpp = tdp; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 10:33:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id BD48614FB3 for ; Wed, 27 Oct 1999 10:33:08 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id NAA24646; Wed, 27 Oct 1999 13:32:59 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Wed, 27 Oct 1999 13:32:58 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Chuck Youse Cc: freebsd-hackers@freebsd.org Subject: Re: UFS ACLs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As pointed out already, there has been *extensive* discussion of this in *numrous* forums. To guide your research into the topic, I recommend looking at the ACL implementations in Solaris and IRIX, as well as the POSIX.1e ACL specification. Take a look at http://www.watson.org/fbsd-hardening/posix1e/ for links to information on POSIX.1e. You may also want to search the UCLA tech report archive for references to file system layers, extended attribute services, and Access Control Lists, which should turn up a few papers on layered file systems, and specifically on implementing an ACLfs based on an extended attribute service based on layering (lots of bases here). For FreeBSD-specific information, I can recommend no better than searching the archives of -hackers, -security, -fs, and -arch. If you're interested in fine-grained access control on objects other than files, there has been lots of discussion of that also, in many forums. In fact, it's realistic to say that there's a whole field of research on hardening UNIX, writing trusted UNIX implementations, etc. On Wed, 27 Oct 1999, Chuck Youse wrote: > > I admittedly haven't done much homework on this topic, but I was wondering > if anyone has played with the idea of implementing ACLs on top of UFS. > > One of the weakest areas in UNIX is its lack of fine-grained access > control for resources - the biggest resource being, of course, the > filesystem. > > Chuck Youse > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 10:38: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id C616314FA6 for ; Wed, 27 Oct 1999 10:37:50 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id TAA74470 for ; Wed, 27 Oct 1999 19:39:31 +0200 (CEST) Message-Id: <199910271739.TAA74470@gw0.boostworks.com> Date: Wed, 27 Oct 1999 19:37:11 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Running unattended (ifo FFS thread) To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In followup of the FFS thread, I would like to know if there are some recommendations for running unattended machines. For exemple, avoiding the 'run fsck manually' (for exemple, when co-locating a machine far away where it is not possible to get a console login). Hints appreciated on other points that may lead to human intervention and how to avoid it. Thanks, RN. ItM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 10:56:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mobil.surnet.ru (mobil.surnet.ru [195.54.2.7]) by hub.freebsd.org (Postfix) with ESMTP id DCDEF15319; Wed, 27 Oct 1999 10:56:18 -0700 (PDT) (envelope-from ilia@cgilh.chel.su) Received: (from uucgilh@localhost) by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id XAA07114; Wed, 27 Oct 1999 23:50:28 +0600 (ESS) Received: (from uucp@localhost) by cgilh.chel.su (8.8.7/8.8.7) with UUCP id XAA01035; Wed, 27 Oct 1999 23:40:14 +0600 Received: from localhost (ilia@localhost) by localhost.cgu.chel.su (8.9.3/8.9.2) with ESMTP id XAA00957; Wed, 27 Oct 1999 23:40:07 +0600 (ESS) (envelope-from ilia@cgilh.chel.su) X-Authentication-Warning: localhost.cgu.chel.su: ilia owned process doing -bs Date: Wed, 27 Oct 1999 23:40:05 +0600 (ESS) From: Ilia Chipitsine X-Sender: ilia@localhost.cgu.chel.su To: "Ronald G. Minnich" Cc: Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On Wed, 27 Oct 1999, Ronald G. Minnich wrote: > On Wed, 27 Oct 1999, Chuck Youse wrote: > > > One of the biggest reasons for the difference: FreeBSD, by default, > > performs _synchronous_ metadata updates, and Linux performs asynchronous > > metadata updates. > > > > It's definitely a bit slower, but the payoff is in reliability. I have > > seen more than one [production!] Linux machine completely trash its > > filesystems because the implementors decided that their "NT-killer" must > > have good performance at the expense of serious, production-quality > > reliability. > > > To put it slightly more strongly: as far as I'm concerned ext2 is not a as far as I remember ext2 has some "counter". I used to use Linux and it performed 'fsck' from time to time (even if fs was clearly unmounted). that is a very good thing to have. I do not recall that FreeBSD did such thing. > serious fs if you really care about handling power failures and other such > fun things. In clusters as small as 64 machines I've measured a 5% what is standard deviation equal to ? "lanl" means Los-Alamos National Laboratory ? > probability that after a power failure one of the 64 ext2 file systems > will have a trashed root file system. With freebsd, over a four-year span, > running through lots of power outages, I didn't lose an FFS file system I DID lose FFS even it was mounted "sync", not async. > even *once* (except for the disk that burned up, but not even FFS can fix > that one). > > ext2 needs a lot of help. Evidently it will be getting it soon, though. > > ron > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQB1AwUBOBc49+RxlWKN2EXhAQGu5QL/REghsBodptbhMMnvDdKW5rkjaG7v9Mvh u9YWqQjPTlcbjKzrlncsHjDGp3uVJFhOaAdCehH//lhfzGUz7BOOMz9QJhhHEPdA UoghImMubxscz76Yc+qS3rTVGE/PqnOy =kZOJ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 11:55:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mobil.surnet.ru (mobil.surnet.ru [195.54.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 3CF7014CBF; Wed, 27 Oct 1999 11:55:06 -0700 (PDT) (envelope-from ilia@cgilh.chel.su) Received: (from uucgilh@localhost) by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id AAA08646; Thu, 28 Oct 1999 00:50:27 +0600 (ESS) Received: (from uucp@localhost) by cgilh.chel.su (8.8.7/8.8.7) with UUCP id AAA01129; Thu, 28 Oct 1999 00:01:53 +0600 Received: from localhost (ilia@localhost) by localhost.cgu.chel.su (8.9.3/8.9.2) with ESMTP id AAA01079; Thu, 28 Oct 1999 00:01:12 +0600 (ESS) (envelope-from ilia@cgilh.chel.su) X-Authentication-Warning: localhost.cgu.chel.su: ilia owned process doing -bs Date: Thu, 28 Oct 1999 00:01:10 +0600 (ESS) From: Ilia Chipitsine X-Sender: ilia@localhost.cgu.chel.su To: Soren Schmidt Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: <199910271708.TAA02104@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On Wed, 27 Oct 1999, Soren Schmidt wrote: > It seems Ilia Chipitsine wrote: > > > > FreeBSD-3.3 + softupdates + "# tunefs -o time" + "flags 0xb0ffb0ff" > > (kernel was compiled with "-O2") > > Hmm, if you didn't do a "tunefs -n enable" you are not using softupdates > and there is your reason why FreeBSD is slower.. 'mount' without any arguments confirmed that softupdates were enabled. I cannot prove it right now, just because I reformatted the hard drive and installed Linux on it. there must be _another_ reason. try to do the same test. > > -Søren > -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQB1AwUBOBc96ORxlWKN2EXhAQFq+AMA4LWv5wz35CCLR+XSRhKtkDfiQL/8ATvL eoxOKB19iInIBPuypbXNudJBTQf/6L4oZUqpBxoWc/oqjMTuw8ExlvhVn2xzX40f EdSb4VutlrCTwv55tCw3SLd/CZG57ye7 =uTbw -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 11:56:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mobil.surnet.ru (mobil.surnet.ru [195.54.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 023BF14E36; Wed, 27 Oct 1999 11:56:14 -0700 (PDT) (envelope-from ilia@cgilh.chel.su) Received: (from uucgilh@localhost) by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id AAA08645; Thu, 28 Oct 1999 00:50:24 +0600 (ESS) Received: (from uucp@localhost) by cgilh.chel.su (8.8.7/8.8.7) with UUCP id AAA01126; Thu, 28 Oct 1999 00:01:53 +0600 Received: from localhost (ilia@localhost) by localhost.cgu.chel.su (8.9.3/8.9.2) with ESMTP id XAA01062; Wed, 27 Oct 1999 23:59:09 +0600 (ESS) (envelope-from ilia@cgilh.chel.su) X-Authentication-Warning: localhost.cgu.chel.su: ilia owned process doing -bs Date: Wed, 27 Oct 1999 23:59:07 +0600 (ESS) From: Ilia Chipitsine X-Sender: ilia@localhost.cgu.chel.su To: David Scheidt Cc: Chuck Robey , Ben Rosengart , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On Wed, 27 Oct 1999, David Scheidt wrote: > On Wed, 27 Oct 1999, Chuck Robey wrote: > > > > > > > Read the post again -- they were using soft updates. > > > > Why is that important? Soft updates is still far better than an async > > filesystem. Have you lost files in panics? I haven't. > > > > Soft updates should get you most of the speed that async updates do. I have > lost cylinder groups in panics on systems with soft-updates. (I was using a > very buggy kernel module, so things were *hosed*). The original poster > hasn't really provided enough information to know what is going on, and what > the performance problem is. in order to save space I gzip'ped output of my tests. ungzipping ports tarball on FreeBSD took 28 min on Linux --- about 2.5 times faster. there's output of "time sh install.sh". > > > David Scheidt > -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQB1AwUBOBc9bORxlWKN2EXhAQGrxgL+PBNSU1hMNRh3mA/zvQQ/OqvlsGfrr5Bc octa9cLZ3acWrZ3WXtd4CZVy75d/mKtEophUAmKWVsmvRPj0cUjvI6iZmq5EOpK4 dRxBkFFl6jyjns1SSOxBQ8tfdTby0MyZ =upZS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 12: 5: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id C42C814D54; Wed, 27 Oct 1999 12:04:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00409; Wed, 27 Oct 1999 11:53:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910271853.LAA00409@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ilia Chipitsine Cc: David Scheidt , Chuck Robey , Ben Rosengart , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-reply-to: Your message of "Wed, 27 Oct 1999 23:59:07 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Oct 1999 11:53:35 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > in order to save space I gzip'ped output of my tests. > ungzipping ports tarball on FreeBSD took 28 min > on Linux --- about 2.5 times faster. This is something we already know, and it's not the sort of test that you should ever headline as "why is FFS so much slower"? Creation of massive directory tree hierarchies under FFS is more expensive because of the way that FFS tries to keep directories spread out, in order to later have a better chance of putting files close to their parent directories. When you create a massive and mostly empty tree like the ports tree, you pay for this optimisation. The justification for this behaviour is that you only create the tree once, but you may use it for years afterwards. Thus, claiming that "FFS is slower" is both short-sighted and incorrect. If you're going to bother to publicise the results of your tests, you could try actually conducting some meaningful tests first. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 12:28: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id F37ED14A0D; Wed, 27 Oct 1999 12:28:02 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id NAA685938; Wed, 27 Oct 1999 13:27:50 -0600 (MDT) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 27 Oct 1999 13:27:50 -0600 From: "Ronald G. Minnich" To: Ilia Chipitsine Cc: Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Ilia Chipitsine wrote: > as far as I remember ext2 has some "counter". I used to use Linux and > it performed 'fsck' from time to time (even if fs was clearly unmounted). > that is a very good thing to have. And it's a good thing because ... well, maybe because it's not that reliable an FS. I actually can't see it as a good thing if you have a file system that doesn't need it. > I do not recall that FreeBSD did such thing. It might not have needed to. It never has in five years for me. The numbers are from my old job at sarnoff, see my web page ... for a while in 1997-99 we had "things go wrong" about once a month. Over the space of 18 months as "things went wrong" we found ourselves having to fix at least one Linux box each time. On average it was four. > I DID lose FFS even it was mounted "sync", not async. I guess I was lucky :-) anyway, I'll drop this thread, just trying to fill in some info. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 12:38:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 464CD14F0F; Wed, 27 Oct 1999 12:38:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA35962; Wed, 27 Oct 1999 12:38:04 -0700 (PDT) (envelope-from dillon) Date: Wed, 27 Oct 1999 12:38:04 -0700 (PDT) From: Matthew Dillon Message-Id: <199910271938.MAA35962@apollo.backplane.com> To: "Ronald G. Minnich" Cc: Ilia Chipitsine , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, 27 Oct 1999, Ilia Chipitsine wrote: :> as far as I remember ext2 has some "counter". I used to use Linux and :> it performed 'fsck' from time to time (even if fs was clearly unmounted). :> that is a very good thing to have. : :And it's a good thing because ... well, maybe because it's not that :reliable an FS. I actually can't see it as a good thing if you have a file :system that doesn't need it. : :> I do not recall that FreeBSD did such thing. : :It might not have needed to. It never has in five years for me. : :The numbers are from my old job at sarnoff, see my web page ... for a :while in 1997-99 we had "things go wrong" about once a month. Over the :space of 18 months as "things went wrong" we found ourselves having to fix :at least one Linux box each time. On average it was four. : :> I DID lose FFS even it was mounted "sync", not async. : :I guess I was lucky :-) : :anyway, I'll drop this thread, just trying to fill in some info. : :ron To be fair, the counter gizmo for ext2fs was from a time many years ago when ext2fs was not all that reliable. I believe ext2fs has gotten quite a bit more reliable in the last year though. Also it is no longer as simple as it was originally. It turns out there's a reason for UFS/FFS's complexity. The linux crowd has similar problems with their 'simpler' swap and VM subsystems. But before people start smirking keep in mind that linux is quite a bit farther ahead of us in the SMP department. When Kirk gets his softupdates/filesystem-checkmarking code working we are going to be a step up from anything linux could hope to accomplish in the filesystem arena because we will then be able to reliably dump, checkmark, AND sanity-check the filesystem on a live (and busy) system. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 12:41:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id A470114D9A; Wed, 27 Oct 1999 12:41:03 -0700 (PDT) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 11gYwN-0000Wf-00; Wed, 27 Oct 1999 20:40:59 +0100 Received: from localhost (jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with SMTP id UAA91444; Wed, 27 Oct 1999 20:40:58 +0100 (BST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Date: Wed, 27 Oct 1999 20:40:58 +0100 (BST) From: J McKitrick To: "Ronald G. Minnich" Cc: Ilia Chipitsine , Chuck Youse , questions@freebsd.org, hackers@freebsd.org Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a nightmare problem with Linux filesystems. Yes, i'm just a newbie recreational linux user. But i had installed mandrake 6.0, which apparently had serious filesystem bugs that would corrupt data if the cdrom was mounted during shutdown. I had to reinstall because of that, and even after DL'ing the patch, since the RPM had to be forced and never did seem to work right, i never trusted it. -jm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 12:48:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 5D46B14D9A; Wed, 27 Oct 1999 12:48:25 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA23837; Wed, 27 Oct 1999 14:48:04 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 27 Oct 1999 14:48:04 -0500 (CDT) From: David Scheidt To: "Ronald G. Minnich" Cc: Ilia Chipitsine , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Ronald G. Minnich wrote: > On Wed, 27 Oct 1999, Ilia Chipitsine wrote: > > as far as I remember ext2 has some "counter". I used to use Linux and > > it performed 'fsck' from time to time (even if fs was clearly unmounted). > > that is a very good thing to have. > > And it's a good thing because ... well, maybe because it's not that > reliable an FS. I actually can't see it as a good thing if you have a file > system that doesn't need it. I seem to recall that ULTRIX had such a mechanism. There must have been other things that decremented the counter though, because my /home filesystem got fscked nearly every reboot. /usr would only be if the machine was up a really long time. DAvid Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 12:54:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.50]) by hub.freebsd.org (Postfix) with ESMTP id 21BAD1523A; Wed, 27 Oct 1999 12:54:12 -0700 (PDT) (envelope-from plm@smtp7.xs4all.nl) Received: from localhost. (dc2-isdn1780.dial.xs4all.nl [194.109.154.244]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA01607; Wed, 27 Oct 1999 21:54:05 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id VAA03855; Wed, 27 Oct 1999 21:25:08 +0200 (MET DST) (envelope-from plm) To: Ilia Chipitsine Cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: why FFS is THAT slower than EXT2 ? References: From: Peter Mutsaers Date: 27 Oct 1999 21:25:07 +0200 In-Reply-To: Ilia Chipitsine's message of "Wed, 27 Oct 1999 23:59:07 +0600 (ESS)" Message-ID: <87n1t4r4h8.fsf@muon.xs4all.nl> Lines: 28 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "IC" == Ilia Chipitsine writes: >> very buggy kernel module, so things were *hosed*). The >> original poster hasn't really provided enough information to >> know what is going on, and what the performance problem is. IC> in order to save space I gzip'ped output of my tests. IC> ungzipping ports tarball on FreeBSD took 28 min on Linux --- IC> about 2.5 times faster. I've measured ext2fs vs. FFS+softupdates many times (both with optimal hdparam settings and flags), and I've found the opposite (both with UDMA and with fast-SCSI2 disks). Benchmark programs (bonnie, iozone) show FFS is faster in almost all areas. Also creating directories with 1000s of emtpy files and deleting these is faster. The only exception might be untarring large tarballs. Linux makes more aggressive use of the filesystem buffer; it even swaps out quite active processes to be able to cache large amounts. The drawback is that the system as a whole tends to become quite sluggish, while BSD has a better balance between keeping active processes and filesystem-cache. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know peter@mutsaers.com | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 13:49:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id BEA4914A17 for ; Wed, 27 Oct 1999 13:48:59 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id GAA12887 for ; Thu, 28 Oct 1999 06:48:57 +1000 (EST) X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id GAA01859 for ; Thu, 28 Oct 1999 06:48:56 +1000 (EST) Received: (qmail 87339 invoked by uid 1000); 27 Oct 1999 20:48:55 -0000 From: "Andrew Reilly" Date: Thu, 28 Oct 1999 06:48:55 +1000 To: Ilia Chipitsine Cc: Soren Schmidt , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991028064855.A85894@gurney.reilly.home> References: <199910271708.TAA02104@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 12:01:10AM +0600, Ilia Chipitsine wrote: > there must be _another_ reason. try to do the same test. You didn't see Mike Smith's explanation? It seemed pretty convincing to me. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 13:53:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from norad.inetu.net (norad.inetu.net [206.245.188.72]) by hub.freebsd.org (Postfix) with ESMTP id 2795F14E0E for ; Wed, 27 Oct 1999 13:53:28 -0700 (PDT) (envelope-from maxiter@inetu.net) Received: from localhost (maxiter@localhost) by norad.inetu.net (8.9.3/8.9.3) with ESMTP id QAA28216 for ; Wed, 27 Oct 1999 16:55:31 -0400 (EDT) Date: Wed, 27 Oct 1999 16:55:30 -0400 (EDT) From: Mark To: freebsd-hackers@freebsd.org Subject: su-ing a user remotely Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for a tool which I think I'll have to end up making myself. What I'm looking for.... Let's say there are two logins on a FreeBSD machine. On ttyp0 is root, and user fred is logged in on ttyp1. Fred can't su to root because he's not in wheel, and he doesn't/won't know the root pass. Assuming I'm logged in a root, I'd like to be able to "bless" fred from my ttyp0 and 'upgrade' his login to root. Is this feasible or programatically realistic? Is there such a tool? What would need to get changed to make this happen? Thx. --------------------------------------------------- Mark Rekai - INetU, Inc.(tm) - http://www.INetU.net Electronic commerce - Web development - Web hosting Mark@INetU.net - Phone: (610) 266-7441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 13:59:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 306E314E42; Wed, 27 Oct 1999 13:59:19 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id JAA20443; Thu, 28 Oct 1999 09:58:40 +1300 (NZDT) Date: Thu, 28 Oct 1999 09:58:40 +1300 From: Joe Abley To: "Ronald G. Minnich" Cc: Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991028095839.A26635@patho.gen.nz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from rminnich@lanl.gov on Wed, Oct 27, 1999 at 10:29:54AM -0600 X-Files: the Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 27, 1999 at 10:29:54AM -0600, Ronald G. Minnich wrote: > To put it slightly more strongly: as far as I'm concerned ext2 is not a > serious fs if you really care about handling power failures and other such > fun things. I'm not sure I've ever really understood this position. In cases where data integrity is vital to retain, there is no excuse for not using machines with multiple power supplies, each fed from independent, clean power sources, with multiple fans, running a stable, tested OS release. Of course, double-point failures _do_ occur. But really, not very often. Paranoia with FS writes can seem extreme considering that the network which attaches that machine to the outside world is probably not engineered to the same degree of fault protection. Just my $0.02. I'm not saying that FFS should throw caution to the wind (especially not in the default configuration) but to argue that async writes are only ever used by stupid people is a little unfair :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:22:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 185C614E0E; Wed, 27 Oct 1999 14:22:40 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id RAA35700; Wed, 27 Oct 1999 17:24:16 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Wed, 27 Oct 1999 17:24:16 -0400 (EDT) From: Don To: "Ronald G. Minnich" Cc: Ilia Chipitsine , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > as far as I remember ext2 has some "counter". I used to use Linux and > > it performed 'fsck' from time to time (even if fs was clearly unmounted). > > that is a very good thing to have. linux performed a fsck on every 16th boot afaik. This may have been changed but that is how often it occurred when I used linux. This had more to do with the file system becoming fragmented than with it becoming inconsistent. (dont quote me on that.) -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:23: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 288F315016; Wed, 27 Oct 1999 14:22:58 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA41638; Wed, 27 Oct 1999 16:22:20 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 27 Oct 1999 16:22:20 -0500 (CDT) From: David Scheidt To: Joe Abley Cc: "Ronald G. Minnich" , Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: <19991028095839.A26635@patho.gen.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Joe Abley wrote: > On Wed, Oct 27, 1999 at 10:29:54AM -0600, Ronald G. Minnich wrote: > > To put it slightly more strongly: as far as I'm concerned ext2 is not a > > serious fs if you really care about handling power failures and other such > > fun things. > > I'm not sure I've ever really understood this position. In cases where > data integrity is vital to retain, there is no excuse for not using > machines with multiple power supplies, each fed from independent, clean > power sources, with multiple fans, running a stable, tested OS release. > I take it you never have had anyone hit the Big Red Button, a fire, a flood, or a random panic, a clueless tech, or a hardware failure? I see one of my machines go down along these lines every six weeks or so. A hosed filesystem would (really!) ruin my day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:25:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 44ECC14E9C; Wed, 27 Oct 1999 14:25:28 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id RAA35715; Wed, 27 Oct 1999 17:26:57 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Wed, 27 Oct 1999 17:26:57 -0400 (EDT) From: Don To: Matthew Dillon Cc: "Ronald G. Minnich" , Ilia Chipitsine , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: <199910271938.MAA35962@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When Kirk gets his softupdates/filesystem-checkmarking code working we > are going to be a step up from anything linux could hope to accomplish > in the filesystem arena because we will then be able to reliably dump, > checkmark, AND sanity-check the filesystem on a live (and busy) system. I would really like to see the finished product from Kirk especially given all of the work he has already done. However, what will xfs mean to linux? -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:31: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 6DF3F14E0E; Wed, 27 Oct 1999 14:30:54 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id KAA08835; Thu, 28 Oct 1999 10:30:19 +1300 (NZDT) Date: Thu, 28 Oct 1999 10:30:17 +1300 From: Joe Abley To: David Scheidt Cc: "Ronald G. Minnich" , Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991028103016.B8012@patho.gen.nz> References: <19991028095839.A26635@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dscheidt@enteract.com on Wed, Oct 27, 1999 at 04:22:20PM -0500 X-Files: the Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 27, 1999 at 04:22:20PM -0500, David Scheidt wrote: > On Thu, 28 Oct 1999, Joe Abley wrote: > > > On Wed, Oct 27, 1999 at 10:29:54AM -0600, Ronald G. Minnich wrote: > > > To put it slightly more strongly: as far as I'm concerned ext2 is not a > > > serious fs if you really care about handling power failures and other such > > > fun things. > > > > I'm not sure I've ever really understood this position. In cases where > > data integrity is vital to retain, there is no excuse for not using > > machines with multiple power supplies, each fed from independent, clean > > power sources, with multiple fans, running a stable, tested OS release. > > I take it you never have had anyone hit the Big Red Button, a fire, > a flood, or a random panic, a clueless tech, or a hardware failure? > I see one of my machines go down along these lines every six weeks or so. A > hosed filesystem would (really!) ruin my day. Actually, no, at least not in the past six years I've been working with carriers and high-spec datacentres. But I take your point :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:43:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 6FF6414F1E for ; Wed, 27 Oct 1999 14:43:40 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id OAA32608; Wed, 27 Oct 1999 14:43:36 -0700 (PDT) Date: Wed, 27 Oct 1999 14:43:36 -0700 (PDT) From: David Wolfskill Message-Id: <199910272143.OAA32608@pau-amma.whistle.com> To: freebsd-hackers@FreeBSD.ORG, maxiter@inetu.net Subject: Re: su-ing a user remotely In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 27 Oct 1999 16:55:30 -0400 (EDT) >From: Mark >What I'm looking for.... Let's say there are two logins on a FreeBSD >machine. On ttyp0 is root, and user fred is logged in on ttyp1. Fred >can't su to root because he's not in wheel, and he doesn't/won't know the >root pass. Assuming I'm logged in a root, I'd like to be able to "bless" >fred from my ttyp0 and 'upgrade' his login to root. >Is this feasible or programatically realistic? Is there such a tool? >What would need to get changed to make this happen? Why not (temporarily) update the "sudoers" file to permit "fred" the level of access (to the requisite command(s))? Assuming, of course, that "sudo" had been set up in the first place. [Probably not really -hackers material....] Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:49:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 191FB14E0E; Wed, 27 Oct 1999 14:49:12 -0700 (PDT) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id QAA10727; Wed, 27 Oct 1999 16:48:52 -0500 (CDT) Message-Id: <199910272148.QAA10727@chiba.3jane.net> To: Joe Abley Cc: "Ronald G. Minnich" , Chuck Youse , Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-reply-to: Your message of "Thu, 28 Oct 1999 09:58:40 +1300." <19991028095839.A26635@patho.gen.nz> Date: Wed, 27 Oct 1999 16:48:52 -0500 From: "Damon M. Conway" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > On Wed, Oct 27, 1999 at 10:29:54AM -0600, Ronald G. Minnich wrote: > > To put it slightly more strongly: as far as I'm concerned ext2 is not a > > serious fs if you really care about handling power failures and other such > > fun things. > > I'm not sure I've ever really understood this position. In cases where > data integrity is vital to retain, there is no excuse for not using > machines with multiple power supplies, each fed from independent, clean > power sources, with multiple fans, running a stable, tested OS release. all that and a nice stable fs. if you're going to do it, do it all the way. > Of course, double-point failures _do_ occur. But really, not very often. > Paranoia with FS writes can seem extreme considering that the network > which attaches that machine to the outside world is probably not > engineered to the same degree of fault protection. however, network issues don't cause nearly as much headache as fs crashes. > Just my $0.02. I'm not saying that FFS should throw caution to the > wind (especially not in the default configuration) but to argue that > async writes are only ever used by stupid people is a little unfair :) i never saw an argument that people who use async writes were stupid. i saw a statement that said async writes do not recover from power failures as well, and if you are concerned about that, you shouldn't use an async fs. this thread is chatty enough without misquoting people. damon -- Damon Conway Black Rock City Ranger...Riding the edge of chaos "Ana Ng and I are getting old, but we still haven't walked in the glow of each other's majestic presence." -- TMBG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:52:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C894A15545; Wed, 27 Oct 1999 14:52:37 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA10061; Wed, 27 Oct 1999 14:51:55 -0700 (PDT) Date: Wed, 27 Oct 1999 14:51:55 -0700 (PDT) From: Julian Elischer To: Mike Smith Cc: Ilia Chipitsine , David Scheidt , Chuck Robey , Ben Rosengart , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: <199910271853.LAA00409@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Mike Smith wrote: > > in order to save space I gzip'ped output of my tests. > > ungzipping ports tarball on FreeBSD took 28 min > > on Linux --- about 2.5 times faster. > > This is something we already know, and it's not the sort of test that > you should ever headline as "why is FFS so much slower"? Kirk has said that it would be possible for the FFS to modify its behaviour if it notices this usage pattern. > > Creation of massive directory tree hierarchies under FFS is more > expensive because of the way that FFS tries to keep directories spread > out, in order to later have a better chance of putting files close to > their parent directories. When you create a massive and mostly empty > tree like the ports tree, you pay for this optimisation. The > justification for this behaviour is that you only create the tree once, > but you may use it for years afterwards. > > Thus, claiming that "FFS is slower" is both short-sighted and > incorrect. If you're going to bother to publicise the results of your > tests, you could try actually conducting some meaningful tests first. > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:54:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 3DAF514FE6 for ; Wed, 27 Oct 1999 14:54:41 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id XAA10417; Wed, 27 Oct 1999 23:54:42 +0200 (CEST) Message-ID: <19991027235442.A10352@foobar.franken.de> Date: Wed, 27 Oct 1999 23:54:42 +0200 From: Harold Gutch To: Mark , freebsd-hackers@FreeBSD.ORG Subject: Re: su-ing a user remotely References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Mark on Wed, Oct 27, 1999 at 04:55:30PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 27, 1999 at 04:55:30PM -0400, Mark wrote: > > I'm looking for a tool which I think I'll have to end up making myself. > > What I'm looking for.... Let's say there are two logins on a FreeBSD > machine. On ttyp0 is root, and user fred is logged in on ttyp1. Fred > can't su to root because he's not in wheel, and he doesn't/won't know the > root pass. Assuming I'm logged in a root, I'd like to be able to "bless" > fred from my ttyp0 and 'upgrade' his login to root. > > Is this feasible or programatically realistic? Is there such a tool? > What would need to get changed to make this happen? > A friend of mine shortly ago mentioned a tool he wrote some time ago that would scan /dev/kmem for a process with a specific PID and change the UID of this process to whatever value you wanted it to be. You can get it from: ftp://ftp.42.org/pub/FreeBSD/presto-1.1.tar.gz Using it you should be able to change this the UID of fred's loginshell, which should accomplish what you are looking for. bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 14:59:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id DC97D14F8E for ; Wed, 27 Oct 1999 14:59:04 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (ida-89-77.Reshall.Berkeley.EDU [169.229.89.77]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id OAA10983 for ; Wed, 27 Oct 1999 14:59:02 -0700 (PDT) env-from (brian@CSUA.Berkeley.EDU) Date: Wed, 27 Oct 1999 14:59:03 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: freebsd-hackers@freebsd.org Subject: cdd produces only noise from CD-AUDIO tracks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Under -current built from Oct 22 soucrces, and cdd built today, ripping CD-AUDIO tracks just produces output files which are just a loud hiss. I've tried this with both of my CD-ROM drives to no avail, and it used to work for both of them under -current several months ago. wcd0: drive speed 5512KB/sec, 256KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wcd1: drive speed 344 - 1034KB/sec, 768KB cache wcd1: supported read types: CD-R, CD-RW, CD-DA, packet track wcd1: supported write types: CD-R, CD-RW, test write wcd1: Audio: play, 128 volume levels wcd1: Mechanism: ejectable tray wcd1: Medium: no/blank disc inside, unlocked, lock protected Anyone have some insight on this? I think I remember seeing a thread along these lines some time ago, but didn't take notice at the time and can't find it in the list archives. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 15:28:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id A46EA14EF2 for ; Wed, 27 Oct 1999 15:28:22 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id SAA57886; Wed, 27 Oct 1999 18:28:07 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-Id: <199910272228.SAA57886@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 27 Oct 1999 18:28:06 -0400 (EDT) From: John Baldwin To: Mark Subject: RE: su-ing a user remotely Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-99 Mark wrote: > > I'm looking for a tool which I think I'll have to end up making > myself. > > What I'm looking for.... Let's say there are two logins on a FreeBSD > machine. On ttyp0 is root, and user fred is logged in on ttyp1. > Fred > can't su to root because he's not in wheel, and he doesn't/won't know > the > root pass. Assuming I'm logged in a root, I'd like to be able to > "bless" > fred from my ttyp0 and 'upgrade' his login to root. > > Is this feasible or programatically realistic? Is there such a tool? > What would need to get changed to make this happen? Take a look at the sudo, super, and su2 ports and see if any of those can do what you need. > Thx. --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 16: 9:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 255DA14E08 for ; Wed, 27 Oct 1999 16:09:43 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id QAA16358; Wed, 27 Oct 1999 16:07:53 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA21472; Wed, 27 Oct 1999 16:07:53 -0700 Received: from softweyr.com (dyn7.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA23915; Wed, 27 Oct 99 16:07:42 PDT Message-Id: <381785C6.C0000EF1@softweyr.com> Date: Wed, 27 Oct 1999 17:07:50 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Chuck Robey Cc: tbuswell@acadia.net, Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Tue, 26 Oct 1999 tbuswell@acadia.net wrote: > > > > > Thomas David Rivers writes: > > > If you mean Xt (and possibly Motif) - the answer is "very carefully." > > [...] > > > > You're approach would probably work, but there's an easier way. > > See topic 28 in the Xt FAQ. > > > > ftp://ftp.x.org/contrib/faqs/FAQ-Xt > > > > It's not name mangling causing problems, it's lack of "this" when the > > method is invoked as a callback from Xt. > > Yes! This is the method! I like it, or at least, it's as close (in C++ > code) to something I do like. I assume they're using a static member function for the callback and storing the this pointer for the object somewhere handy? This is the canonical way to re-enter C++ code from C land, and can even be used for C++ interrupt handlers if you're very careful. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 16:42: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 4918614D74 for ; Wed, 27 Oct 1999 16:41:57 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id SAA62441; Wed, 27 Oct 1999 18:41:55 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 27 Oct 1999 18:41:55 -0500 (CDT) From: David Scheidt To: Mark Cc: freebsd-hackers@freebsd.org Subject: Re: su-ing a user remotely In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Mark wrote: > > I'm looking for a tool which I think I'll have to end up making myself. > > What I'm looking for.... Let's say there are two logins on a FreeBSD > machine. On ttyp0 is root, and user fred is logged in on ttyp1. Fred > can't su to root because he's not in wheel, and he doesn't/won't know the > root pass. Assuming I'm logged in a root, I'd like to be able to "bless" > fred from my ttyp0 and 'upgrade' his login to root. > > Is this feasible or programatically realistic? Is there such a tool? > What would need to get changed to make this happen? I do this on sparc boxes occaisonally using the nifty forth interperter in the boot ROM to change the UID of some process. Handy for recovering random lost passwords. I suspect that you could do the same with a debugger on FreeBSD, but haven't really thought about it. David scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 16:43:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 9CEA514D74 for ; Wed, 27 Oct 1999 16:43:22 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id TAA16487; Wed, 27 Oct 1999 19:42:16 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 27 Oct 1999 19:42:16 -0400 (EDT) From: Chuck Robey To: Wes Peters Cc: tbuswell@acadia.net, Thomas David Rivers , freebsd-hackers@FreeBSD.ORG Subject: Re: X11/C++ question In-Reply-To: <381785C6.C0000EF1@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Wes Peters wrote: > Chuck Robey wrote: > > > > On Tue, 26 Oct 1999 tbuswell@acadia.net wrote: > > > > > > > > Thomas David Rivers writes: > > > > If you mean Xt (and possibly Motif) - the answer is "very carefully." > > > [...] > > > > > > You're approach would probably work, but there's an easier way. > > > See topic 28 in the Xt FAQ. > > > > > > ftp://ftp.x.org/contrib/faqs/FAQ-Xt > > > > > > It's not name mangling causing problems, it's lack of "this" when the > > > method is invoked as a callback from Xt. > > > > Yes! This is the method! I like it, or at least, it's as close (in C++ > > code) to something I do like. > > I assume they're using a static member function for the callback and storing > the this pointer for the object somewhere handy? This is the canonical way > to re-enter C++ code from C land, and can even be used for C++ interrupt > handlers if you're very careful. Yes, you store the address of the object you want the callback vectored to in the UserData Xt pointer, and when the callback comes into the static func, it just takes the offered object address and reflects the call back out to the right function in the right object. Neat, the user never sees any complication at all. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 17: 2: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 71DA614E19; Wed, 27 Oct 1999 17:01:40 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA05933; Wed, 27 Oct 1999 17:00:46 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id RAA02929; Wed, 27 Oct 1999 17:00:44 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA11954; Wed, 27 Oct 1999 17:00:43 -0700 (PDT) From: Don Lewis Message-Id: <199910280000.RAA11954@salsa.gv.tsc.tdk.com> Date: Wed, 27 Oct 1999 17:00:43 -0700 In-Reply-To: Julian Elischer "Re: why FFS is THAT slower than EXT2 ?" (Oct 27, 2:51pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Julian Elischer , Mike Smith Subject: Re: why FFS is THAT slower than EXT2 ? Cc: Ilia Chipitsine , David Scheidt , Chuck Robey , Ben Rosengart , Chuck Youse , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Oct 27, 2:51pm, Julian Elischer wrote: } Subject: Re: why FFS is THAT slower than EXT2 ? } } } On Wed, 27 Oct 1999, Mike Smith wrote: } } > > in order to save space I gzip'ped output of my tests. } > > ungzipping ports tarball on FreeBSD took 28 min } > > on Linux --- about 2.5 times faster. } > } > This is something we already know, and it's not the sort of test that } > you should ever headline as "why is FFS so much slower"? } } Kirk has said that it would be possible for the FFS to modify its } behaviour if it notices this usage pattern. The basic problem is that the directory layout policy that FFS uses is very non-optimal in this case. This was discussed extensively on freebsd-hackers last year, search the list archive for Reading/writing /usr/ports VERY slow Carl Mascott noticed nearly a 3x speedup when he untarred /usr/ports on FFS filesystem that was generated with only one cylinder group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 17:12: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 0EDA514E2D for ; Wed, 27 Oct 1999 17:11:50 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-41.bellatlantic.net [151.198.135.41]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA17351; Wed, 27 Oct 1999 20:11:32 -0400 (EDT) Message-ID: <381795EA.AD384579@bellatlantic.net> Date: Wed, 27 Oct 1999 20:16:42 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Chuck Youse Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UFS ACLs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Youse wrote: > > I admittedly haven't done much homework on this topic, but I was wondering > if anyone has played with the idea of implementing ACLs on top of UFS. > > One of the weakest areas in UNIX is its lack of fine-grained access > control for resources - the biggest resource being, of course, the > filesystem. As my personal experience with Novell Netware shows most of the time the presence of the fine-grained access control is a great temptation to create a complete mess in the filesystem. The thing I personally feel neccessary is being able to assign access rights to a file to two separate groups because it's cheap and resolves most of the problems. I have implemented it as a small patch that works with both FFS and EXT2FS in FreeBSD. Let me know if you are interested in looking at it. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 17:14:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (police.varesearch.com [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 466AC14EAB for ; Wed, 27 Oct 1999 17:14:21 -0700 (PDT) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id RAA14087; Wed, 27 Oct 1999 17:12:59 -0700 Date: Wed, 27 Oct 1999 17:12:59 -0700 Message-Id: <199910280012.RAA14087@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: timer interrupts From: "Manju Radhakrishnan" Reply-To: "Manju Radhakrishnan" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Manju Radhakrishnan" Be sure to reply to that address. Hi, I am trying to modify IP code in FreeBSD so that the packets from IP layer are not immediately sent to the interface output but they are buffered and sent at a certain rate. So I need to set an interrupt such that a function is called after some time interval. Is using timeout the only way? since timeouts are at a priority lower than network priority, is there anything else that I can use. thanks for the help, Manju Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 18:22:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9235014E08 for ; Wed, 27 Oct 1999 18:22:25 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA19696; Thu, 28 Oct 1999 10:51:51 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910271739.TAA74470@gw0.boostworks.com> Date: Thu, 28 Oct 1999 10:51:51 +0930 (CST) From: "Daniel O'Connor" To: Remy Nonnenmacher Subject: RE: Running unattended (ifo FFS thread) Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-99 Remy Nonnenmacher wrote: > In followup of the FFS thread, I would like to know if there are some > recommendations for running unattended machines. For exemple, avoiding > the 'run fsck manually' (for exemple, when co-locating a machine far > away where it is not possible to get a console login). Well.. (and I know lots of people would say this is stupid) If you are going to run it in isolation, then you can change the inital fsck so that it just assumes yes for all user input in an error condition.. This means that it generally always gets through the fsck.. Of course if fsck had to delete files then they're gone, but if you value its ability to stay up without human intervention its handy. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 18:23:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 3298614CE9; Wed, 27 Oct 1999 18:23:39 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA19704; Thu, 28 Oct 1999 10:53:15 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <87n1t4r4h8.fsf@muon.xs4all.nl> Date: Thu, 28 Oct 1999 10:53:15 +0930 (CST) From: "Daniel O'Connor" To: Peter Mutsaers Subject: Re: why FFS is THAT slower than EXT2 ? Cc: hackers@freebsd.org, questions@freebsd.org, Ilia Chipitsine Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Oct-99 Peter Mutsaers wrote: > The only exception might be untarring large tarballs. Linux makes more > aggressive use of the filesystem buffer; it even swaps out quite > active processes to be able to cache large amounts. The drawback is > that the system as a whole tends to become quite sluggish, while BSD > has a better balance between keeping active processes and > filesystem-cache. Is there anyway to tune this behaviour under FreeBSD? I know the argument is that 'FreeBSD is self tuning' but some of us are unable to resist fiddling =) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 18:25:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id A6CEA14E08 for ; Wed, 27 Oct 1999 18:25:19 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id UAA81599; Wed, 27 Oct 1999 20:25:07 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910280125.UAA81599@celery.dragondata.com> Subject: Re: Running unattended (ifo FFS thread) To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 27 Oct 1999 20:25:06 -0500 (CDT) Cc: remy@synx.com (Remy Nonnenmacher), hackers@FreeBSD.ORG In-Reply-To: from "Daniel O'Connor" at Oct 28, 1999 10:51:51 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locating a machine far > > away where it is not possible to get a console login). > > Well.. (and I know lots of people would say this is stupid) If you are going to > run it in isolation, then you can change the inital fsck so that it just > assumes yes for all user input in an error condition.. > > This means that it generally always gets through the fsck.. Of course if fsck > had to delete files then they're gone, but if you value its ability to stay up > without human intervention its handy. > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, even if it's unneeded. This takes ages for me. I believe I submitted a PR with a 'fix' to fsck. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 18:35:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D1EBA14D6E for ; Wed, 27 Oct 1999 18:35:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA19827; Thu, 28 Oct 1999 11:05:01 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910280125.UAA81599@celery.dragondata.com> Date: Thu, 28 Oct 1999 11:05:00 +0930 (CST) From: "Daniel O'Connor" To: Kevin Day Subject: Re: Running unattended (ifo FFS thread) Cc: hackers@FreeBSD.ORG, (Remy Nonnenmacher) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-99 Kevin Day wrote: > > This means that it generally always gets through the fsck.. Of course if > > had to delete files then they're gone, but if you value its ability to stay > > without human intervention its handy. > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, > even if it's unneeded. This takes ages for me. I believe I submitted a PR > with a 'fix' to fsck. Yeah, the machines we have don't get shutdown except for a power failure so that wasn't a problem :) I'll have a look for your PR tho. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 18:37:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id F29FF14D0D for ; Wed, 27 Oct 1999 18:37:35 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id SAA16563; Wed, 27 Oct 1999 18:37:26 -0700 (PDT) Date: Wed, 27 Oct 1999 18:37:25 -0700 (PDT) From: Julian Elischer To: "Daniel O'Connor" Cc: Remy Nonnenmacher , hackers@FreeBSD.ORG Subject: RE: Running unattended (ifo FFS thread) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Daniel O'Connor wrote: > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locating a machine far > > away where it is not possible to get a console login). > > Well.. (and I know lots of people would say this is stupid) If you are going to > run it in isolation, then you can change the inital fsck so that it just > assumes yes for all user input in an error condition.. we do fsck -p || fsck -y > > This means that it generally always gets through the fsck.. Of course if fsck > had to delete files then they're gone, but if you value its ability to stay up > without human intervention its handy. > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 19:40:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D14714CD0; Wed, 27 Oct 1999 19:40:32 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA12294; Wed, 27 Oct 1999 22:40:31 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA30300; Wed, 27 Oct 1999 22:40:00 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 27 Oct 1999 22:40:00 -0400 (EDT) To: freebsd-hackers@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: ip forwarding broken on alpha X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14359.43410.495963.975277@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an older AlphaStation 600 5/266 running -current (cvsupped last week) which is setup as a router between 2 100mb networks. When the machine is pushed fairly hard (like running a netperf -tUDP_STREAM -- -m 100 across the router, eg about 10-20k 100byte packets/sec ) the alpha falls over almost instantly. I have not enabled any NAT or firewall functionality, just ip forwarding. It generally crashes in MCLGET down in the ethernet driver's receiver interrupt handler. The driver doesn't seem to matter -- I've tried Intel Etherexpress Pro 100Bs and 3Com 3c905C-TX Fast Etherlink XLs. A typical stack trace looks like this: fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x826417b78f222 a1 = 0x1 a2 = 0x0 pc = 0xfffffc00004b31bc ra = 0xfffffc00004b315c curproc = 0 ddbprinttrap from 0xfffffc00004b31bc ddbprinttrap(0x826417b78f222, 0x1, 0x0, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe0005ab57d0> db> tr Debugger() at Debugger+0x2c panic() at panic+0xf4 trap() at trap+0x5cc xl_newbuf() at xl_newbuf+0x15c (null)() at 0x4 db> c this maps to pci/if_xl.c:1654. But the if_xl driver is probably not at fault, as I can crash just as easily in fxp_add_rfabuf() when using intel nics. Before trying the 3com cards, I had been working under the assumption that it was a problem with the fxp driver. I instrumented the mbuf routines somewhat (i hate debugging macros) and it seems the bad access is due to mclfree getting trashed & replaced by a "random" bad value (0x826417b78f222 in this panic). This might be a red herring, but I've found that if I run the entire ip_input path under splnet() (added splnet() around the call to ip_input() in ipintr().), things get a hell of a lot more stable. Rather than crashing in a few seconds, it sometimes takes minutes. And rather than an illegal access, I tend to run out of kernel stack space ( either a panic("possible stack overflow\n"); in alpha/alpha/interrupt.c, or I end up in the SRM console after calling halt from a PC which isn't in the kernel, which smells like an overrun stack to me). I'm not sure if this is related, or if it is a separate problem entirely. Since an x86 (PII@300MHz, 440lx motherboard, kernel built from same sources) is rock solid under the same workload, I suspect there's something wrong that is alpha specific, but I'll be damned if I can figure it out. My best guess is that it has something to do with the different interrupt structure on i386 & alpha. As I understand it, the i386 can mask off particular interrupt sources, but the alpha simply raises & lowers the ipl with the following levels available (from alpha/include/alpha_cpu.h): #define ALPHA_PSL_IPL_0 0x0000 /* all interrupts enabled */ #define ALPHA_PSL_IPL_SOFT 0x0001 /* software ints disabled */ #define ALPHA_PSL_IPL_IO 0x0004 /* I/O dev ints disabled */ #define ALPHA_PSL_IPL_CLOCK 0x0005 /* clock ints disabled */ #define ALPHA_PSL_IPL_HIGH 0x0006 /* all but mchecks disabled */ Can anybody hazard a guess as to what's going on? I've appended dmesg output & my config file for completeness. BTW, as long as the load is light, ip forwarding seems to work. I can't seem to make this happen using 2 100Mb tulips in this box (which must copy on the input path due to DMA alignment problems, this slows things down quite a bit, due to the low memory bandwidth of this machine) Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Wed Oct 27 11:35:25 EDT 1999 gallatin@torrent.cs.duke.edu:/usr/project/ari_scratch2/gallatin/src/sys/comp ile/ALPHA AlphaStation 500 or 600 (KN20AA) Digital AlphaStation 600 5/266, 266MHz 8192 byte page size, 1 processor. CPU: EV5 (21164) major=5 minor=0 OSF PAL rev: 0x1000000020116 real memory = 131940352 (128848K bytes) avail memory = 122200064 (119336K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000674000. cia0: ALCOR/ALCOR2, pass 2 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 xl0: <3Com 3c905C-TX Fast Etherlink XL> irq 8 at device 7.0 on pci0 xl0: interrupting at CIA irq 8 xl0: Ethernet address: 00:50:da:09:3e:41 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: at device 8.0 on pci0 pci1: on pcib1 de0: irq 16 at device 0.0 on pci1 de0: interrupting at CIA irq 16 de0: DEC 21040 [10Mb/s] pass 2.3 de0: address 08:00:2b:e7:e6:d6 isp0: irq 17 at device 1.0 on pci1 isp0: interrupting at CIA irq 17 isp0: invalid NVRAM header (aa,aa,aa,aa) isp0: isp_mboxcmd sees mailbox int with 0x0 in mbox0 isp0: isp_mboxcmd sees mailbox int with 0x0 in mbox0 <..> isp1: irq 18 at device 2.0 on pci1 isp1: interrupting at CIA irq 18 isp1: isp_mboxcmd sees mailbox int with 0x0 in mbox0 isp1: invalid NVRAM header (55,55,55,55) isp1: isp_mboxcmd sees mailbox int with 0x0 in mbox0 isp1: isp_mboxcmd sees mailbox int with 0x0 in mbox0 de1: irq 12 at device 9.0 on pci0 de1: interrupting at CIA irq 12 de1: DEC DE500-XA 21140 [10-100Mb/s] pass 1.1 de1: address 00:00:f8:00:99:ba de1: enabling Full Duplex 100baseTX port isab0: at device 10.0 on pci0 isa0: on isab0 xl1: <3Com 3c905C-TX Fast Etherlink XL> irq 0 at device 11.0 on pci0 xl1: interrupting at CIA irq 0 xl1: Ethernet address: 00:50:da:09:42:41 miibus1: on xl1 xlphy1: <3c905C 10/100 internal PHY> on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl2: <3Com 3c905C-TX Fast Etherlink XL> irq 4 at device 12.0 on pci0 xl2: interrupting at CIA irq 4 xl2: Ethernet address: 00:50:da:09:3f:e8 miibus2: on xl2 xlphy2: <3c905C 10/100 internal PHY> on miibus2 xlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x80 on isa0 sio1: type 16550A sio1: interrupting at ISA irq 3 fdc0: interrupting at ISA irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 struct nfssvc_sock bloated (> 256bytes) Try reducing NFS_UIDHASHSIZ struct nfsuid bloated (> 128bytes) Try unionizing the nu_nickname and nu_flag fields Timecounter "alpha" frequency 266671691 Hz Waiting 3 seconds for SCSI devices to settle isp0: driver initiated bus reset of bus 0 isp1: driver initiated bus reset of bus 0 de0: autosense failed: cable problem? Creating DISK da0 Creating DISK da1 Creating DISK cd0 da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 12, 16bit), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da1 at isp0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 12, 16bit), Tagged Queueing Enabled da1: 2062MB (4223444 512 byte sectors: 255H 63S/T 262C) cd0 at isp0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 12) cd0: Attempt to query device size failed: NOT READY, Medium not present # machine alpha cpu EV4 cpu EV5 ident ALPHA maxusers 32 # Platforms supported options DEC_AXPPCI_33 # UDB, Multia, AXPpci33, Noname options DEC_EB164 # EB164, PC164, PC164LX, PC164SX options DEC_EB64PLUS # EB64+, Aspen Alpine, etc options DEC_2100_A50 # AlphaStation 200, 250, 255, 400 options DEC_KN20AA # AlphaStation 500, 600 options DEC_ST550 # Personal Workstation 433, 500, 600 options DEC_ST6600 # xp1000, dp264, ds20, ds10, family #options DEC_3000_300 # DEC3000/300* Pelic* family #options DEC_3000_500 # DEC3000/[4-9]00 Flamingo/Sandpiper family options INET #InterNETworking `options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MFS #Memory Filesystem options MFS_ROOT #Memory Filesystem as rootfs options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options SOFTUPDATES # Standard busses controller pci0 controller isa0 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 controller isp0 controller ahc0 #controller esp0 controller scbus0 device da0 device sa0 device pass0 device cd0 # # ATA and ATAPI devices # This is work in progress, use at your own risk. # It currently reuses the majors of wd.c and friends. # It cannot co-exist with the old system in one kernel. # You only need one "controller ata0" for it to find all # PCI devices on modern machines. controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives device atapist0 # ATAPI tape drives # real time clock device mcclock0 at isa0 port 0x70 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? device sio0 at isa0 port IO_COM1 irq 4 device sio1 at isa0 port IO_COM2 irq 3 flags 0x80 # MII bus support, required for some 10/100 NICs. controller miibus0 # Operational PCI Ethernet drivers. device al0 device ax0 device de0 device dm0 device fxp0 device le0 device mx0 device pn0 device rl0 device sf0 device sis0 device ste0 device tl0 device vr0 device wb0 device xl0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun pseudo-device pty pseudo-device bpf 4 # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # # everything above is essentially GENERIC. customizations below. # options DDB options BREAK_TO_DEBUGGER To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 20:39:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id AEC2314F32 for ; Wed, 27 Oct 1999 20:39:51 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id WAA85270; Wed, 27 Oct 1999 22:39:42 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 27 Oct 1999 22:39:42 -0500 (CDT) From: David Scheidt To: "Daniel O'Connor" Cc: Remy Nonnenmacher , hackers@freebsd.org Subject: RE: Running unattended (ifo FFS thread) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Daniel O'Connor wrote: > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locating a machine far > > away where it is not possible to get a console login). > > Well.. (and I know lots of people would say this is stupid) If you are going to > run it in isolation, then you can change the inital fsck so that it just > assumes yes for all user input in an error condition.. It isn't really clear what else you would do, though. Most people don't know enough to fix things that fsck can't. If it hoses the box, restore from backup. It is what they are for! David scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 21: 0:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tabby.kudra.com (gw.kudra.com [199.6.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 4573814C85 for ; Wed, 27 Oct 1999 21:00:11 -0700 (PDT) (envelope-from robert@kudra.com) Received: (from robert@localhost) by tabby.kudra.com (8.9.3/8.6.12) id XAA39187; Wed, 27 Oct 1999 23:59:30 -0400 (EDT) Date: Wed, 27 Oct 1999 23:59:29 -0400 From: Robert Sexton To: Ilia Chipitsine Cc: freebsd-hackers@freebsd.org Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991027235929.C39061@tabby.kudra.com> References: <19991027155930.A36190@tabby.kudra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Ilia Chipitsine on Thu, Oct 28, 1999 at 07:08:19AM +0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know waht really happened, but the originally quoted numbers sound fishy to me. There may well be some other problem. I ran two tests on my rather modest machine (P166, 64mb, UW Scsi Drives, 3.3-Stable). I have soft updates turned on. (correctly, I might add :-) Unpacking the ports file from a tarball: 6:30 Creating a ports dir tarfile: 4:30 The filesystems in question were about 800 megs, created with default settings. I'd say thats pretty acceptable performance. -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA Getting to Know your friends, Part VIII: "Jerry is a little too Cerebral for me. But then again, he likes Twinkies." Read the Newton FAQ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 22:45:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id 7EB6E14C89 for ; Wed, 27 Oct 1999 22:45:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01295; Wed, 27 Oct 1999 22:36:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910280536.WAA01295@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Boris Popov Cc: Andrey Simonenko , hackers@FreeBSD.ORG Subject: Re: UNILOAD v.1.2 (boot loader/manager) is ready In-reply-to: Your message of "Wed, 27 Oct 1999 16:34:57 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Oct 1999 22:36:49 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 26 Oct 1999, Andrey Simonenko wrote: > > > I made some days ago UNILOAD v.1.2, the main feature of this version is > > the ability to load system from beyond 1024 cylinder mark. Here it is > > Woo, that feature is _very_ useful. What about incorporating this > into FreeBSD's boot code ? We already support it, but it's turned off by default because a number of the systems we tested didn't like it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 27 22:50:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id 8602E14E44 for ; Wed, 27 Oct 1999 22:50:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01326; Wed, 27 Oct 1999 22:41:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910280541.WAA01326@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: eT@post.com Cc: hackers@freebsd.org Subject: Re: PCI bus Latency In-reply-to: Your message of "Wed, 27 Oct 1999 01:35:57 PDT." <19991027083557.22017.rocketmail@web1402.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Oct 1999 22:41:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please try wrapping your messages to a sane width; try 72 columns. > When doing a pci_read_config(dev, PCI_LATENCY_TIMER, 4) I get varying > values on different hardware configurations. > > On Machine A the value is 32 and my device driver (using DMA) works fine. > > On Machine B the value is 64 and my device driver doesn't work fine - > there seem s to be these hickups in which the Chip writing to the PCI > controller says it has finished transferring data but the write > counters are still > 0. My card works closely with two network cards in > the system. Since you don't make it clear what "the Chip" and "the PCI controller" are, it's kinda hard to be very helpful here. > Actually, I reckon I just need some pointers and things to remember when it > comes to dealing with latency. Any help? I'd start by buying and reading the PCI specification document end to end. You can probably skip the section on physical dimensions, but just about all of the rest of it is relevant. You can save a little time and a lot of money by getting a copy of the Shanley book "PCI System Architecture". Most online bookstores have it; it's cheap. Without meaning to be insulting, it's probably not worthwhile pursuing this further until you've read one or both of the above, since we'd just be regurgitating large portions of the books. Buy, read, and if you're still having trouble then come back and try again. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 0:48:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from omnix.net (omnix.net [195.154.168.66]) by hub.freebsd.org (Postfix) with SMTP id E926014CDE for ; Thu, 28 Oct 1999 00:48:22 -0700 (PDT) (envelope-from didier@omnix.net) Received: (qmail 19162 invoked by uid 200); 28 Oct 1999 07:48:20 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Oct 1999 07:48:20 -0000 Date: Thu, 28 Oct 1999 07:48:20 +0000 (GMT) From: Didier Derny To: Ilia Chipitsine Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've never had a crashed file system with Freebsd (I started with FreeBSD 1.1) On Wed, 27 Oct 1999, Ilia Chipitsine wrote: > -----BEGIN PGP SIGNED MESSAGE----- >=20 > Well, guys, listen :-) >=20 > I and my friends mentioned that "FreeBSD + ffs" is often slower > (THAT slower) than "Linux + ext2" for number of tasks: > rm, find, tar ... for IDE & SCSI disks. >=20 > I didn't try things like "FreeBSD + ext2" or "Linux + ffs". >=20 > I attached here results of the test I performed. For test I "gunzip"ped > FreeBSD ports collection, in attachment You can find "scripted" output of= =20 > "# time sh install.sh" for both systems. Also there are "dmesg" outputs. >=20 > machine was THE SAME: read "dmesg", >=20 > FreeBSD-3.3 + softupdates + "# tunefs -o time" + "flags 0xb0ffb0ff" > (kernel was compiled with "-O2") > Linux - RedHat-6.0 with out_of_box_kernel, just=20 > "# hdparm -d 1 -c 3 -m 16 /dev/hda", read "hdparm" output... >=20 > even as non-native English speaker I know few other other words which > begin with "f" :-)=20 > is "fast" the propriate one for "ffs" ? >=20 > Regards, (=EE=C1=C9=CC=D5=DE=DB=C9=C5 =D0=CF=D6=C5=CC=C1=CE=C9=D1) >=20 > Ilia Chipitsine (=E9=CC=D8=D1 =FB=C9=D0=C9=C3=C9=CE) >=20 > -----BEGIN PGP SIGNATURE----- > Version: 2.6.3ia > Charset: noconv >=20 > iQB1AwUBOBcbQuRxlWKN2EXhAQHHqgL+K+2O8gkv1kYs8AhsqbMsIFTG5u7gfzcT > oqqhKlTUlTtaKtAl6g/CnKsPpxfh0CaMEmQC+5bzqSa4MnZcyHwiAWlrNLRlU08A > DfYJQRGa/6S5OiaJVYnsAuKnbr6tLZGZ > =3DYWer > -----END PGP SIGNATURE----- >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 2:12:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id A808514DA0 for ; Thu, 28 Oct 1999 02:12:11 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id LAA24024 for ; Thu, 28 Oct 1999 11:12:09 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 23952; Thu Oct 28 11:11:16 1999 From: Graham Wheeler To: hackers@freebsd.org Subject: Weird /tmp behaviour Date: Thu, 28 Oct 1999 11:06:14 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99102811072904.03657@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all We've just noticed something strange here, that probably has a mundane explanation but we can't figure it out. On a 2.2.8 FreeBSD system, if anyone creates a file in /tmp, the group gets set to `bin'. The SGID bit is not set, so that doesn't explain it. Does anyone know why this happens? Unfortunately I don't have immediate access to any other releases to see if it is release-specific. -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 2:24: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id A9CFD14EED for ; Thu, 28 Oct 1999 02:23:59 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id LAA11418; Thu, 28 Oct 1999 11:23:31 +0200 (CEST) Message-ID: <19991028112331.A11345@foobar.franken.de> Date: Thu, 28 Oct 1999 11:23:31 +0200 From: Harold Gutch To: Graham Wheeler , hackers@FreeBSD.ORG Subject: Re: Weird /tmp behaviour References: <99102811072904.03657@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <99102811072904.03657@cequrux.com>; from Graham Wheeler on Thu, Oct 28, 1999 at 11:06:14AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 11:06:14AM +0200, Graham Wheeler wrote: > Hi all > > We've just noticed something strange here, that probably has a mundane > explanation but we can't figure it out. On a 2.2.8 FreeBSD system, if anyone > creates a file in /tmp, the group gets set to `bin'. The SGID bit is not set, > so that doesn't explain it. Does anyone know why this happens? Unfortunately > I don't have immediate access to any other releases to see if it is > release-specific. > That's what BSD just does - see open(2): When a new file is created it is given the group of the directory which contains it. The sticky bit on /tmp ensures that only the owner can delete and rename his files in this directory. bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 2:28: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wit401310.student.utwente.nl (wit401310.student.utwente.nl [130.89.236.150]) by hub.freebsd.org (Postfix) with ESMTP id 164C714ED3; Thu, 28 Oct 1999 02:28:05 -0700 (PDT) (envelope-from dalroi@wit401310.student.utwente.nl) Received: from wit401310.student.utwente.nl (localhost [127.0.0.1]) by wit401310.student.utwente.nl (Postfix) with ESMTP id 453091DC9; Thu, 28 Oct 1999 11:28:21 +0200 (CEST) Date: Thu, 28 Oct 1999 11:28:20 +0200 (CEST) From: Alban Hertroys Subject: Re: why FFS is THAT slower than EXT2 ? To: Didier Derny Cc: Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <19991028092821.453091DC9@wit401310.student.utwente.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Oct, Didier Derny wrote: > > I've never had a crashed file system with Freebsd (I started with FreeBSD > 1.1) I've seen it happen once. Eventually it turned out that the drive had become too hot, and FreeBSD wasn't able to synchronize it's data. No miracle the root file system was broken after that... -- Alban Hertroys. http://wit401310.student.utwente.nl --- If I had a sig it would be fun. The quest for the Holy Sig has begun. I have not yet a clue, What will you see next issue? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 3:30:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id AB15314CF1 for ; Thu, 28 Oct 1999 03:30:02 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id MAA29829 for ; Thu, 28 Oct 1999 12:30:00 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 29823; Thu Oct 28 12:29:51 1999 From: Graham Wheeler To: hackers@freebsd.org Subject: Re: Weird /tmp behaviour Date: Thu, 28 Oct 1999 12:23:35 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <99102811072904.03657@cequrux.com> <19991028112331.A11345@cequrux.com> In-Reply-To: <19991028112331.A11345@cequrux.com> MIME-Version: 1.0 Message-Id: <99102812260305.03657@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, you wrote: > On Thu, Oct 28, 1999 at 11:06:14AM +0200, Graham Wheeler wrote: > > Hi all > > > > We've just noticed something strange here, that probably has a mundane > > explanation but we can't figure it out. On a 2.2.8 FreeBSD system, if anyone > > creates a file in /tmp, the group gets set to `bin'. The SGID bit is not set, > > so that doesn't explain it. Does anyone know why this happens? Unfortunately > > I don't have immediate access to any other releases to see if it is > > release-specific. > > > That's what BSD just does - see open(2): > > When a new file is created it is given the group of the directory which > contains it. That's pretty weird (but quite correct). Just checked on NetBSD and found the same. I would have expected this behaviour only if the SGID bit was set, not by default. Ah, well, live and learn (and use chown()); -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 3:45:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 106A814CF1 for ; Thu, 28 Oct 1999 03:45:42 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 53287 invoked by uid 1001); 28 Oct 1999 10:45:38 +0000 (GMT) To: gram@cequrux.com Cc: hackers@freebsd.org Subject: Re: Weird /tmp behaviour From: sthaug@nethelp.no In-Reply-To: Your message of "Thu, 28 Oct 1999 12:23:35 +0200" References: <99102812260305.03657@cequrux.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 28 Oct 1999 12:45:38 +0200 Message-ID: <53285.941107538@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's what BSD just does - see open(2): > > > > When a new file is created it is given the group of the directory which > > contains it. > > That's pretty weird (but quite correct). Just checked on NetBSD and found > the same. I would have expected this behaviour only if the SGID bit was set, > not by default. It's always been the BSD behavior. Solaris and and some other SVR4 systems do the sgid thing in order to make the BSD behavior possible. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 4:52: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 48EEA14E19 for ; Thu, 28 Oct 1999 04:51:52 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id MAA12598 Thu, 28 Oct 1999 12:51:39 +0100 (BST) Message-ID: <381838CB.167E@cs.strath.ac.uk> Date: Thu, 28 Oct 1999 12:51:39 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Bill Paul Cc: hackers@freebsd.org Subject: 2 problems with the linksys mx driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bill, I'm having quite a few problems with my linksys cards. I think most are caused because I'm connected to a switch rather than a simple hub. The cards are the new Version 2 cards (with Wake On Lan) and use the MX driver. 1) On 3.3-stable, the linksys mx driver detects my network connection to a 3COM switch as 100BaseT4. However, the kernel then panics because if_media cannot support media type 0x28. My workarond was to hack the kernel source for if_mx.c and stop it detecting 100BaseT4. It now detects 100Base Full duplex and works ok. 2) On 4.x-current, the linksys mx driver is connected to a Kingston 10/100 Switch. It does not detect a carrier on the network. If I do ifconfig mx0 media auto I see the 'link in use' and '100 Megs in use' LED on my switch go on for 2 seconds, then go off for 2 seconds, then go on for 2 seconds, then go off for 2 seconds. When the link is up, I can ping and use the network etc. When the link is down, I have no network connection. If I type in ifconfig mx0 media 100basetx it all works OK. Do you have any ideas on these. I'm willing to test patches on both -stable and -current and can swap switches too (swap the 3COM and the Kingston) Thanks Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 5:51:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C9B3115125 for ; Thu, 28 Oct 1999 05:51:44 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id HAA19055; Thu, 28 Oct 1999 07:51:18 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 28 Oct 1999 07:51:18 -0500 (CDT) From: David Scheidt To: sthaug@nethelp.no Cc: gram@cequrux.com, hackers@freebsd.org Subject: Re: Weird /tmp behaviour In-Reply-To: <53285.941107538@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999 sthaug@nethelp.no wrote: > > > That's what BSD just does - see open(2): > > > > > > When a new file is created it is given the group of the directory which > > > contains it. > > > > That's pretty weird (but quite correct). Just checked on NetBSD and found > > the same. I would have expected this behaviour only if the SGID bit was set, > > not by default. > > It's always been the BSD behavior. Solaris and and some other SVR4 > systems do the sgid thing in order to make the BSD behavior possible. There is US government regulation requiring this behavior in certain government systems. The Missed 'em V behavior was created for this. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 6:27:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cielo.eece.unm.edu (cielo.eece.unm.edu [129.24.24.11]) by hub.freebsd.org (Postfix) with ESMTP id ECC5A14C91 for ; Thu, 28 Oct 1999 06:27:11 -0700 (PDT) (envelope-from dbader@eece.unm.edu) Received: from jalapeno.eece.unm.edu ([129.24.24.88] helo=eece.unm.edu) by cielo.eece.unm.edu with esmtp (Exim 2.12 #1) id 11gpaB-00068k-00 for freebsd-hackers@freebsd.org; Thu, 28 Oct 1999 07:27:11 -0600 Received: (from dbader@localhost) by eece.unm.edu (8.9.3+Sun/8.9.1) id HAA04687; Thu, 28 Oct 1999 07:27:10 -0600 (MDT) Date: Thu, 28 Oct 1999 07:27:10 -0600 (MDT) Message-Id: <199910281327.HAA04687@eece.unm.edu> X-Authentication-Warning: jalapeno.eece.unm.edu: dbader set sender to dbader@eece.unm.edu using -f From: "David A. Bader" To: freebsd-hackers@freebsd.org Subject: POSIX threads Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an application that uses SIGUSR1, but also POSIX threads. It appears (?) that the user-level POSIX threads now incorporated into FreeBSD 3.x use SIGUSR1 and SIGUSR2. Is this correct? If so, and I have a threaded application, what signals are still available for use? Please reply directly to me, since I do not regularly read this list. dbader@eece.unm.edu Thanks! david -- David A. Bader, Ph.D. Office: 505-277-6724 Dept of Electrical and Computer Engineering FAX: 505-277-1439 EECE Building University of New Mexico dbader@eece.unm.edu Albuquerque, NM 87131 http://www.eece.unm.edu/~dbader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 7:11:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-1.sti.com.br (smtp-1.sti.com.br [200.212.48.202]) by hub.freebsd.org (Postfix) with ESMTP id 0686D15048; Thu, 28 Oct 1999 07:11:11 -0700 (PDT) (envelope-from Casa_do_Pensamento@mail.com) Received: from carlos ([200.188.66.109]) by smtp-1.sti.com.br (8.9.3/8.9.3) with SMTP id LAA27354; Thu, 28 Oct 1999 11:04:56 -0200 Message-Id: <199910281304.LAA27354@smtp-1.sti.com.br> X-Sender: From: To: Date: Thu, 28 Oct 1999 09:32:50 -0300 Subject: Solidão MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Solidão "Você não pode estar só se gostar da pessoa com quem fica quando esta sozinho." - Wayne Dyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 8:29: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id AC69214DAB for ; Thu, 28 Oct 1999 08:28:51 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA04413; Thu, 28 Oct 1999 11:25:47 -0400 (EDT) Message-Id: <199910281525.LAA04413@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 28 Oct 1999 10:27:53 -0400 To: eT@post.com, hackers@FreeBSD.ORG From: Dennis Subject: Re: PCI bus Latency In-Reply-To: <19991027083557.22017.rocketmail@web1402.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:35 AM 10/27/99 -0700, eT wrote: >Greetings .. > >When doing a pci_read_config(dev, PCI_LATENCY_TIMER, 4) I get varying values on >different hardware configurations. > >On Machine A the value is 32 and my device driver (using DMA) works fine. > >On Machine B the value is 64 and my device driver doesn't work fine - there >seem >s to be these hickups in which the Chip writing to the PCI controller says it >ha >s finished transferring data but the write counters are still > 0. My card >works closely with two network cards in the system. > >Actually, I reckon I just need some pointers and things to remember when it >come >s to dealing with latency. Any help? It seems unlikely that the latency timer will cause a controller to "not work" The latency timer settings allow a master to tell the system how long it needs to complete a burst cycle...however a controller is allowed to complete the current cycle when another master grants the bus so you shouldnt have failures unless the controller is defective. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 8:32:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2C3F115125 for ; Thu, 28 Oct 1999 08:32:29 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA14271; Thu, 28 Oct 1999 11:31:07 -0400 (EDT) Date: Thu, 28 Oct 1999 11:31:07 -0400 (EDT) From: Daniel Eischen Message-Id: <199910281531.LAA14271@pcnet1.pcnet.com> To: dbader@eece.unm.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: POSIX threads Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have an application that uses SIGUSR1, but also POSIX threads. It > appears (?) that the user-level POSIX threads now incorporated into > FreeBSD 3.x use SIGUSR1 and SIGUSR2. Is this correct? If so, and I > have a threaded application, what signals are still available for use? No, the threads library that comes with 3.x/4.x does not use SIGUSR1 or SIGUSR2 for anything. It does use SIGPROF via setitimer for its internal scheduling mechanism, and SIGINFO to dump thread information (to aid debugging), but the other signals are available. Perhaps you're confusing libc_r with LinuxThreads which also runs under FreeBSD. I believe LinuxThreads uses SIGUSR1 and/or SIGUSR2. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 8:37: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cielo.eece.unm.edu (cielo.eece.unm.edu [129.24.24.11]) by hub.freebsd.org (Postfix) with ESMTP id 6EAA814DAB for ; Thu, 28 Oct 1999 08:36:58 -0700 (PDT) (envelope-from dbader@eece.unm.edu) Received: from jalapeno.eece.unm.edu ([129.24.24.88] helo=eece.unm.edu) by cielo.eece.unm.edu with esmtp (Exim 2.12 #1) id 11grbl-0006VP-00; Thu, 28 Oct 1999 09:36:57 -0600 Received: (from dbader@localhost) by eece.unm.edu (8.9.3+Sun/8.9.1) id JAA05245; Thu, 28 Oct 1999 09:36:52 -0600 (MDT) Date: Thu, 28 Oct 1999 09:36:52 -0600 (MDT) Message-Id: <199910281536.JAA05245@eece.unm.edu> X-Authentication-Warning: jalapeno.eece.unm.edu: dbader set sender to dbader@eece.unm.edu using -f From: "David A. Bader" To: eischen@vigrid.com Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: <199910281531.LAA14271@pcnet1.pcnet.com> (message from Daniel Eischen on Thu, 28 Oct 1999 11:31:07 -0400 (EDT)) Subject: Re: POSIX threads References: <199910281531.LAA14271@pcnet1.pcnet.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and SIGUSR2. I recently took code that used to work with FSU's implementation of threads under FreeBSD; and instead recompiled with the new FreeBSD 3.x threads; however, it crashes now when creating threads. The FSU threads (that used to work with FreeBSD 2.x no longer compile under 3.x); so I'm not sure if there's another implementation I can try. Thanks, -david > Envelope-to: dbader@eece.unm.edu > Delivery-date: Thu, 28 Oct 1999 09:32:28 -0600 > Date: Thu, 28 Oct 1999 11:31:07 -0400 (EDT) > From: Daniel Eischen > > > I have an application that uses SIGUSR1, but also POSIX threads. It > > appears (?) that the user-level POSIX threads now incorporated into > > FreeBSD 3.x use SIGUSR1 and SIGUSR2. Is this correct? If so, and I > > have a threaded application, what signals are still available for use? > > No, the threads library that comes with 3.x/4.x does not use SIGUSR1 > or SIGUSR2 for anything. It does use SIGPROF via setitimer for its > internal scheduling mechanism, and SIGINFO to dump thread information > (to aid debugging), but the other signals are available. > > Perhaps you're confusing libc_r with LinuxThreads which also runs > under FreeBSD. I believe LinuxThreads uses SIGUSR1 and/or SIGUSR2. > > Dan Eischen > eischen@vigrid.com > -- David A. Bader, Ph.D. Office: 505-277-6724 Dept of Electrical and Computer Engineering FAX: 505-277-1439 EECE Building University of New Mexico dbader@eece.unm.edu Albuquerque, NM 87131 http://www.eece.unm.edu/~dbader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 8:48:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id CEB2B14CA6 for ; Thu, 28 Oct 1999 08:48:22 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA16923; Thu, 28 Oct 1999 11:47:06 -0400 (EDT) Date: Thu, 28 Oct 1999 11:47:06 -0400 (EDT) From: Daniel Eischen Message-Id: <199910281547.LAA16923@pcnet1.pcnet.com> To: dbader@eece.unm.edu, eischen@vigrid.com Subject: Re: POSIX threads Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and > SIGUSR2. I recently took code that used to work with FSU's > implementation of threads under FreeBSD; and instead recompiled with > the new FreeBSD 3.x threads; however, it crashes now when creating > threads. When you say the "new FreeBSD 3.x threads", you mean FreeBSDs default libc_r library, not the LinuxThreads library, right? In what way does your program crash? Have you debugged it? And what version of FreeBSD 3.x are you talking about? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 8:58:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 3DFF314CA6 for ; Thu, 28 Oct 1999 08:58:24 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id IAA12831; Thu, 28 Oct 1999 08:57:52 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 28 Oct 1999 08:57:52 -0700 Date: Thu, 28 Oct 1999 08:57:52 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Ilia Chipitsine Cc: hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: ilia@cgilh.chel.su,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't like to be the shoot the messenger type - but I have several FreeBSD systems and several Linux systems. Twice I have had my Linux filesystem corrupted beyond recovery - I have never had that problem=20 on FreeBSD. The file system may be marginally slower for certain activities, however, I doubt that the time you save will make up for=20 the time spent reinstalling. =09=09=09=09=09-Kip On Wed, 27 Oct 1999, Ilia Chipitsine wrote: > -----BEGIN PGP SIGNED MESSAGE----- >=20 > Well, guys, listen :-) >=20 > I and my friends mentioned that "FreeBSD + ffs" is often slower > (THAT slower) than "Linux + ext2" for number of tasks: > rm, find, tar ... for IDE & SCSI disks. >=20 > I didn't try things like "FreeBSD + ext2" or "Linux + ffs". >=20 > I attached here results of the test I performed. For test I "gunzip"ped > FreeBSD ports collection, in attachment You can find "scripted" output of= =20 > "# time sh install.sh" for both systems. Also there are "dmesg" outputs. >=20 > machine was THE SAME: read "dmesg", >=20 > FreeBSD-3.3 + softupdates + "# tunefs -o time" + "flags 0xb0ffb0ff" > (kernel was compiled with "-O2") > Linux - RedHat-6.0 with out_of_box_kernel, just=20 > "# hdparm -d 1 -c 3 -m 16 /dev/hda", read "hdparm" output... >=20 > even as non-native English speaker I know few other other words which > begin with "f" :-)=20 > is "fast" the propriate one for "ffs" ? >=20 > Regards, (=EE=C1=C9=CC=D5=DE=DB=C9=C5 =D0=CF=D6=C5=CC=C1=CE=C9=D1) >=20 > Ilia Chipitsine (=E9=CC=D8=D1 =FB=C9=D0=C9=C3=C9=CE) >=20 > -----BEGIN PGP SIGNATURE----- > Version: 2.6.3ia > Charset: noconv >=20 > iQB1AwUBOBcbQuRxlWKN2EXhAQHHqgL+K+2O8gkv1kYs8AhsqbMsIFTG5u7gfzcT > oqqhKlTUlTtaKtAl6g/CnKsPpxfh0CaMEmQC+5bzqSa4MnZcyHwiAWlrNLRlU08A > DfYJQRGa/6S5OiaJVYnsAuKnbr6tLZGZ > =3DYWer > -----END PGP SIGNATURE----- >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 9:19:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EA9BA14CA6 for ; Thu, 28 Oct 1999 09:19:01 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id JAA13887; Thu, 28 Oct 1999 09:41:39 -0700 (PDT) Date: Thu, 28 Oct 1999 09:41:39 -0700 (PDT) From: Alfred Perlstein To: "David A. Bader" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: POSIX threads In-Reply-To: <199910281536.JAA05245@eece.unm.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, David A. Bader wrote: > > I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and > SIGUSR2. I recently took code that used to work with FSU's > implementation of threads under FreeBSD; and instead recompiled with > the new FreeBSD 3.x threads; however, it crashes now when creating > threads. A traceback would be much more useful, can you possibly provide one? Even better a specific set of code that causes the crash would be even better. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 9:48:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cielo.eece.unm.edu (cielo.eece.unm.edu [129.24.24.11]) by hub.freebsd.org (Postfix) with ESMTP id C99AA14BC7 for ; Thu, 28 Oct 1999 09:48:52 -0700 (PDT) (envelope-from dbader@eece.unm.edu) Received: from jalapeno.eece.unm.edu ([129.24.24.88] helo=eece.unm.edu) by cielo.eece.unm.edu with esmtp (Exim 2.12 #1) id 11gsjL-00070w-00; Thu, 28 Oct 1999 10:48:51 -0600 Received: (from dbader@localhost) by eece.unm.edu (8.9.3+Sun/8.9.1) id KAA05941; Thu, 28 Oct 1999 10:48:51 -0600 (MDT) Date: Thu, 28 Oct 1999 10:48:51 -0600 (MDT) Message-Id: <199910281648.KAA05941@eece.unm.edu> X-Authentication-Warning: jalapeno.eece.unm.edu: dbader set sender to dbader@eece.unm.edu using -f From: "David A. Bader" To: eischen@vigrid.com Cc: eischen@vigrid.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <199910281547.LAA16923@pcnet1.pcnet.com> (message from Daniel Eischen on Thu, 28 Oct 1999 11:47:06 -0400 (EDT)) Subject: Re: POSIX threads References: <199910281547.LAA16923@pcnet1.pcnet.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you say the "new FreeBSD 3.x threads", you mean FreeBSDs default > libc_r library, not the LinuxThreads library, right? Correct. > In what way does your program crash? Have you debugged it? And > what version of FreeBSD 3.x are you talking about? I'm running FreeBSD-3.3R, and I'll try to provide more debugging information ASAP. Thanks, -david -- David A. Bader, Ph.D. Office: 505-277-6724 Dept of Electrical and Computer Engineering FAX: 505-277-1439 EECE Building University of New Mexico dbader@eece.unm.edu Albuquerque, NM 87131 http://www.eece.unm.edu/~dbader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 10:13:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 358F014C34 for ; Thu, 28 Oct 1999 10:13:26 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA27382; Thu, 28 Oct 1999 10:13:26 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA04537; Thu, 28 Oct 1999 10:13:25 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 28 Oct 1999 10:13:25 -0700 (PDT) Message-Id: <199910281713.KAA04537@vashon.polstra.com> To: gallatin@cs.duke.edu Subject: Re: ip forwarding broken on alpha In-Reply-To: <14359.43410.495963.975277@grasshopper.cs.duke.edu> References: <14359.43410.495963.975277@grasshopper.cs.duke.edu> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <14359.43410.495963.975277@grasshopper.cs.duke.edu>, Andrew Gallatin wrote: > I have an older AlphaStation 600 5/266 running -current (cvsupped > last week) which is setup as a router between 2 100mb networks. > When the machine is pushed fairly hard (like running a netperf > -tUDP_STREAM -- -m 100 across the router, eg about 10-20k 100byte > packets/sec ) the alpha falls over almost instantly. I have not > enabled any NAT or firewall functionality, just ip forwarding. > > It generally crashes in MCLGET down in the ethernet driver's > receiver interrupt handler. I'm probably way off the mark, but I have to ask. Are you sure you're not simply running out of mbufs? I noticed your maxusers is only 32 and I didn't see an options line to raise NMBCLUSTERS. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 10:30: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 465D414D1C for ; Thu, 28 Oct 1999 10:30:00 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id KAA28440; Thu, 28 Oct 1999 10:29:20 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id KAA27796; Thu, 28 Oct 1999 10:29:20 -0700 Received: from softweyr.com (dyn7.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17584; Thu, 28 Oct 99 10:29:00 PDT Message-Id: <381887E4.FFAA00BB@softweyr.com> Date: Thu, 28 Oct 1999 11:29:08 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Roger Hardiman Cc: hackers@FreeBSD.ORG Subject: Re: 2 problems with the linksys mx driver References: <381838CB.167E@cs.strath.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roger Hardiman wrote: > > If I type in ifconfig mx0 media 100basetx > it all works OK. > > Do you have any ideas on these. Autonegotiation is failing. That happens in the Fast Ethernet world. Buying better quality switches *may* help. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 10:46:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id A7DD614EBA for ; Thu, 28 Oct 1999 10:46:41 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA96980; Thu, 28 Oct 1999 10:46:34 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 28 Oct 1999 10:46:33 -0700 (PDT) From: Doug White To: Mike Pritchard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: xntpd & xcdplayer In-Reply-To: <19991027043807.A13608@mpp.pro-ns.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Mike Pritchard wrote: > I've noticed something peculiar over the past week or so with > xntpd and I think xcdplayer (from ports). I am running xntpd > to keep my clock right. I have an always on DSL connection, > so I almost never see any output from xntpd. > > However, I've noticed that the past few times I've started > playing a CD with xcdplayer, I get the following out of xntpd: > > Oct 27 04:10:44 mpp xntpd[153]: Previous time adjustment didn't complete These are pretty normal on busy systems o rsystems with seriously screwed clocks. > Which is somewhat odd, because the last message from xntpd about > adjusting the time was over 13 hours ago (and it was a 0.129016 s > adjustment). xntpd only logs time steps, not the fractional clock slewing it does constantly. The full steps shouldn't really happen once you're synched, but we all know that PC clocks leave something to be desired. > Normally I ignore whatever xntpd tells me, unless it reports > a large time difference. But, tonight when I was checking my mail > and decided to listen to a CD while doing so, I got the > "Previous time adjustment..." message right away after starting to > play the CD. And after thinking back, it seems to me that I see > more of around the time when I'm playing CDs, so it seems like the two > might be related. (IDE) CD activity tends to suspend interrupts for an excessive amount of time. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 10:48:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id EAD92151C6; Thu, 28 Oct 1999 10:48:28 -0700 (PDT) (envelope-from steveb@veriohosting.com) Received: by gatekeeper.veriohosting.com; Thu, 28 Oct 1999 11:48:25 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma012904; Thu, 28 Oct 99 11:48:07 -0600 Received: from iserver.com (glacier.orem.iserver.com [192.168.1.111]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id LAA59123; Thu, 28 Oct 1999 11:49:20 -0600 (MDT) Message-ID: <38188BEC.75ABC44D@iserver.com> Date: Thu, 28 Oct 1999 11:46:21 -0600 From: Steve Bishop X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-database@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Cc: "Paul.Marquess@btinternet.com" Subject: Re: mbuf problem (panic) SOLVED --possibly related to Berkeley DB 2.7.7 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've increased maxusers to 512, and NMBCLUSTERS to 16384, and I haven't been able to reproduce the kernel panic problem anymore. So, my conclusion is that increasing maxusers solved the problem. I don't believe that raising NMBCLUSTERS by itself, or it indirectly being raised by maxusers, fixed the problem. The reason I think this is because I raised NMBCLUSTERS to 8192 before, and it had no effect whatsover in delaying or preventing the kernel panics I was experiencing. As I described before, right before the panic occurred, the OS began to exponentially use up all of the mbufs, and even if I had set NBMCLUSTERS to 30000 it would have used them up in short order. The typical mbuf usage for this system while running all of its software (scripts) is about 100 mbufs, and it has been running over a day now, and not exceeded 962. I've not seen anywhere near the kind of mbuf usage, that occurred when the machine panicked before. This leads me to the conclusion that maxusers, affects many other kernel parameters (which of course it does), and indirectly eliminated the mbuf problem by providing enough resources for the database in all situations, and most especially in cases when Berkeley DB wasn't shut down clean, or in its proper fashion. Although I don't know all of the kernel parameters affected by increasing maxusers, it seems to have solved my problem, and in a roundabout way prevented the machine going into its "spiral-of-death" mbuf problem. -Steve Developer Verio, Inc. verio.com -- the new world of business To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 10:49:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B4D16152B2 for ; Thu, 28 Oct 1999 10:49:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA98079; Thu, 28 Oct 1999 10:49:00 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 28 Oct 1999 10:49:00 -0700 (PDT) From: Doug White To: Damian Kuczynski Cc: hackers@FreeBSD.ORG Subject: Re: Some modifications to natd. proposal In-Reply-To: <3816E73A.F60D5D2D@nik.gov.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Damian Kuczynski wrote: > Hello > > I use natd + libalias in my test network connected to internet. > >From my point of view main disadvantage of this program is, that i can't > see what' s > going on in packet alias engine, I'm not sure what you're looknig for here... do you want more than what 'natd -l' or strategically located ipfw log rules provide? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 12:23: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 5D79414CF7 for ; Thu, 28 Oct 1999 12:23:01 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from bfg (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id UAA00044 Thu, 28 Oct 1999 20:22:49 +0100 (BST) Message-ID: <005901bf2179$e5bb9ae0$0200000a@bfg> From: "Roger Hardiman" To: "Wes Peters" Cc: Subject: Re: 2 problems with the linksys mx driver Date: Thu, 28 Oct 1999 20:22:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >>>> Problems with linksys (mx driver) cards in -stable and - current >> If I type in ifconfig mx0 media 100basetx >> it all works OK. >> >> Do you have any ideas on these. > >Autonegotiation is failing. That happens in the Fast Ethernet world. >Buying better quality switches *may* help. ;^) Can you get any better than 3COM's top of the range stacks? Seriously though, in -stable there are 2 bugs with the linksys (mx driver) cards. 1) In if_mx, (and a few other drivers too for that mater) the driver probes the link and then selects the most suitable speed and mode (half or full duplex) The code picks 100BaseT4 as its first chose, then 100 Meg Full Duplex second, then 100 Meg Half duplex, then 10 Full Duplex, then 10 Half duplex. The Ethernet specs I have read say the official order should be 100 Meg Full Duplex FIRST, then 100base T4, then 100 Meg Half duplex, then 10 Full D then 10 Half D. 2) Even if my line was 100BaseT4, the if_mx driver should not be passing an invalid paremter to if_media, causeing if_media to panic with something along the lines of "invalid media type 0x28/0xffffff" if_mx should not select 100BaseT4 if the rest of the kernel cannot handle it. _OR_ it should be passing the right parameter to if_media. Then there are issues in -current, but lets fix -stable first. This is all a bit different to the Bt848 driver, so I could do with some help kernel hacking. Cheers Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 13:14:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id E399E15399 for ; Thu, 28 Oct 1999 13:13:55 -0700 (PDT) (envelope-from charnier@xp11.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA26966 for freebsd-hackers@FreeBSD.org; Thu, 28 Oct 1999 22:13:54 +0200 (CEST) (envelope-from charnier@xp11.frmug.org) Received: from xp11.frmug.org (xp11.frmug.org [127.0.0.1]) by xp11.frmug.org (8.9.3/8.9.2/xp11-uucp-1.1) with ESMTP id WAA04112 for ; Thu, 28 Oct 1999 22:04:20 +0200 (CEST) (envelope-from charnier@xp11.frmug.org) Message-Id: <199910282004.WAA04112@xp11.frmug.org> To: freebsd-hackers@FreeBSD.org Subject: Re: Running unattended (ifo FFS thread) Date: Thu, 28 Oct 1999 22:04:20 +0200 From: "Philippe Charnier" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The problem is that 'fsck -py' ignores the 'p' and will fsck every time, >even if it's unneeded. This takes ages for me. I believe I submitted a PR >with a 'fix' to fsck. >Kevin According to the man page, fsck -y and fsck -p are two distincts commands. ------ ------ Philippe Charnier charnier@{lirmm.fr,xp11.frmug.org,FreeBSD.org} ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 13:20:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 4C0D014EAE for ; Thu, 28 Oct 1999 13:20:22 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id WAA17457 for freebsd-hackers@freebsd.org; Thu, 28 Oct 1999 22:20:21 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id WAA01594; Thu, 28 Oct 1999 22:15:46 +0200 (MET DST) (envelope-from j) Date: Thu, 28 Oct 1999 22:15:46 +0200 (MET DST) Message-Id: <199910282015.WAA01594@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <01ca01bf09bf$642e9080$2e00a8c0@nt46daniel> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: The sppp driver X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (It would be nice if you formatted your message with line breaks.) "Daniel Hilevich" wrote: > But, in the later case, the control messages are = queued to the > control queue=20 (sp->pp_cpq) which the if_start functions doesn't > have access to. Should = I implement the access? Nothing you gotta worry about. The control queue is only there in order to get higher priority for control packets than for data packets, in an attempt to speedup control negotiations for interfaces that are `dial on demand' (i. e., have LINK1 set). This is opaque to the `customer' of sppp. > - How do you recommend connecting my ioctrl functions to the sppp ioctrl = > function Have a look at the current `customers' for sppp, which are sys/i4b/driver/i4b_sppp.c (for a driver that uses dialup connections), and sys/i386/isa/if_{ar,cx,sr}.c for drivers that use hardware links (like HDLC lines) without dialling. > - Is there any resource about using the sppp driver. The sppp man page = > isn't satisfying at all. See above. > ------=_NextPart_000_01C7_01BF09C7.C5ECB6F0 > Content-Type: text/html; > charset="windows-1255" > Content-Transfer-Encoding: quoted-printable Please don't do this. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 13:20:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id A5D3B1537E for ; Thu, 28 Oct 1999 13:20:21 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id WAA17454 for freebsd-hackers@freebsd.org; Thu, 28 Oct 1999 22:20:21 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id WAA01576; Thu, 28 Oct 1999 22:07:02 +0200 (MET DST) (envelope-from j) Date: Thu, 28 Oct 1999 22:07:02 +0200 (MET DST) Message-Id: <199910282007.WAA01576@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199910021904.VAA16526@dorifer.heim3.tu-clausthal.de> <199910071914.NAA60735@harmony.village.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: 2.88Mb floppies X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > The BIOS will report a different value for the 2.88MB drives to the > probe routines... Actually one out of two possible different values (forgot the actual once), depending on what BIOS you've got... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 13:20:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 9B08015485 for ; Thu, 28 Oct 1999 13:20:29 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id WAA17465 for freebsd-hackers@freebsd.org; Thu, 28 Oct 1999 22:20:28 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id WAA01559; Thu, 28 Oct 1999 22:02:55 +0200 (MET DST) (envelope-from j) Date: Thu, 28 Oct 1999 22:02:55 +0200 (MET DST) Message-Id: <199910282002.WAA01559@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199909272039.WAA04128@yedi.iaf.nl> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: 2.88Mb floppies X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > Just having installed a 2.88Mb floppy drive in one of my axp boxes > I wonder if FreeBSD can do 2.88Mb floppy disks. From the looks > of the contents of /sys/i386/isa/fd.c: .... > it appears it cannot. It cannot. I once tried to hack support for 2.88 MB into the existing driver, but eventually gave up. The driver needs a complete rewrite in order to do this (or some royally painful hackups in order to accomodate for the differing FDC clock frequencies, wrt. seek timing etc.). Once i'm retired, i promise to rewrite that driver. :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 13:20:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 16F7014C08 for ; Thu, 28 Oct 1999 13:20:34 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id WAA17466 for freebsd-hackers@freebsd.org; Thu, 28 Oct 1999 22:20:30 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id WAA01569; Thu, 28 Oct 1999 22:06:10 +0200 (MET DST) (envelope-from j) Date: Thu, 28 Oct 1999 22:06:10 +0200 (MET DST) Message-Id: <199910282006.WAA01569@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199909292346.BAA03499@dorifer.heim3.tu-clausthal.de> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: 2.88Mb floppies X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > I once programmed low-level FDC stuff under DOS, so I'm a bit I under CP/M, that's why i wrote the floppy formatter for 386BSD. ;-) > familiar with this... The difference between 1.44 and 2.88 Mb > floppies is that the latter use 36 sectors per track and twice > the data rate (1 MBit/s). So the entry should look like this: Alas, there's way more of differences than this when it comes to 2.88 MB. The higher data rate makes it now painfully obvious that the entire timing is misdesigned in the driver, or actually rather that the entire FDC design is crippled. :) Seeks will no longer work reliably on a number of drives then (if you double the FDC clock rate once again) since the stepper gets overclocked. Also, there's something called `perpendicular mode' (which i never fully groked what it's really for) you need to enable for 2.88 MB. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 13:50:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 808B314BF4 for ; Thu, 28 Oct 1999 13:50:26 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id WAA17916 for freebsd-hackers@freebsd.org; Thu, 28 Oct 1999 22:50:26 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id WAA01672; Thu, 28 Oct 1999 22:26:25 +0200 (MET DST) (envelope-from j) Date: Thu, 28 Oct 1999 22:26:25 +0200 (MET DST) Message-Id: <199910282026.WAA01672@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199909300941.LAA77105@zibbi.mikom.csir.co.za> <050001bf0b3a$13e078b0$2e00a8c0@nt46daniel> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: A bug in the sppp driver? X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel Hilevich" wrote: > In my case, although, I want to use the IFF_AUTO (dial on demand) > option and this is where ifconfig can not help me. In the auto mode, > the sppp driver should initialize the lcp machine when it gets a new > message to send. Did you ever look how the ISDN `customer' driver handles it? At least for me, it used to work for something like two years now there (and i'm using it daily). Without a massive code review, i can't however tell you the exact chain of events that happens once the callout is triggered, that's nothing one can remember for more than a week. :-) I could however offer you a log from "ifconfig ... debug" for a callout dial-on-demand connection, that should demonstrate the state transitions for normal (i. e. no packet loss) negotiations. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:26: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.apfel.de (mail.apfel.de [195.252.143.26]) by hub.freebsd.org (Postfix) with ESMTP id CE8CA14C18 for ; Thu, 28 Oct 1999 14:25:59 -0700 (PDT) (envelope-from petzi@mail.apfel.de) Received: (from petzi@localhost) by mail.apfel.de (8.9.3/8.9.3) id XAA02557 for hackers@freebsd.org; Thu, 28 Oct 1999 23:52:26 +0200 (MEST) Date: Thu, 28 Oct 1999 23:52:26 +0200 From: Michael Beckmann To: hackers@freebsd.org Subject: Limitations in FreeBSD Message-ID: <19991028235225.A2535@apfel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! 1. What is the maximum size of a file on a filesystem ? 2. What is the maximum size of a filesystem ? 3. What is the maximum amount of RAM that FreeBSD can handle ? 4. What is the maximum size of a file that can be mmap´ed ? Furthermore, I understand that FreeBSD can´t mmap a block device. Is it planned to change that ? Thanks ! :-) Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:30:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id B40A915396 for ; Thu, 28 Oct 1999 14:30:39 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id AA1BA9B22; Thu, 28 Oct 1999 17:30:38 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 9BAB5BA1C; Thu, 28 Oct 1999 17:30:38 -0400 (EDT) Date: Thu, 28 Oct 1999 17:30:38 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Michael Beckmann Cc: hackers@freebsd.org Subject: Re: Limitations in FreeBSD In-Reply-To: <19991028235225.A2535@apfel.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Michael Beckmann wrote: > Hi ! > > 1. What is the maximum size of a file on a filesystem ? > 2. What is the maximum size of a filesystem ? http://www.freebsd.org/FAQ/install.html#AEN704 ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:35:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DBEDD14C18 for ; Thu, 28 Oct 1999 14:35:19 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA10010; Thu, 28 Oct 1999 14:35:11 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 14:35:11 -0700 (PDT) From: Matthew Dillon Message-Id: <199910282135.OAA10010@apollo.backplane.com> To: "Chris D. Faulhaber" Cc: Michael Beckmann , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, 28 Oct 1999, Michael Beckmann wrote: : :> Hi ! :> :> 1. What is the maximum size of a file on a filesystem ? :> 2. What is the maximum size of a filesystem ? : :http://www.freebsd.org/FAQ/install.html#AEN704 : :----- :Chris D. Faulhaber | All the true gurus I've met never :System/Network Administrator, | claimed they were one, and always The document is not quite right. The maximum size is limited to 8 Terrabytes due to block-size conversions done in the kernel which are independant of the filesystem block size. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:42: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 5AFFF153EF for ; Thu, 28 Oct 1999 14:42:00 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA48420; Thu, 28 Oct 1999 14:41:57 -0700 (PDT) Date: Thu, 28 Oct 1999 14:41:57 -0700 (PDT) From: Julian Elischer To: Joerg Wunsch Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: The sppp driver In-Reply-To: <199910282015.WAA01594@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG of course if you want to be really generic, we've just added the netgraph code to -current which implements a lot more than the rather specialised sppp code. On Thu, 28 Oct 1999, J Wunsch wrote: > (It would be nice if you formatted your message with line breaks.) > > "Daniel Hilevich" wrote: > > > But, in the later case, the control messages are = queued to the > > control queue=20 (sp->pp_cpq) which the if_start functions doesn't > > have access to. Should = I implement the access? > > Nothing you gotta worry about. The control queue is only there in > order to get higher priority for control packets than for data > packets, in an attempt to speedup control negotiations for interfaces > that are `dial on demand' (i. e., have LINK1 set). This is opaque to > the `customer' of sppp. > > > - How do you recommend connecting my ioctrl functions to the sppp ioctrl = > > function > > Have a look at the current `customers' for sppp, which are > sys/i4b/driver/i4b_sppp.c (for a driver that uses dialup connections), > and sys/i386/isa/if_{ar,cx,sr}.c for drivers that use hardware links > (like HDLC lines) without dialling. > > > - Is there any resource about using the sppp driver. The sppp man page = > > isn't satisfying at all. > > See above. > > > ------=_NextPart_000_01C7_01BF09C7.C5ECB6F0 > > Content-Type: text/html; > > charset="windows-1255" > > Content-Transfer-Encoding: quoted-printable > > Please don't do this. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:42:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9DFE515436 for ; Thu, 28 Oct 1999 14:42:19 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA02267; Thu, 28 Oct 1999 14:42:00 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: "Chris D. Faulhaber" , Michael Beckmann , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "Thu, 28 Oct 1999 14:35:11 PDT." <199910282135.OAA10010@apollo.backplane.com> Date: Thu, 28 Oct 1999 14:42:00 -0700 Message-ID: <2264.941146920@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The document is not quite right. The maximum size is limited to > 8 Terrabytes due to block-size conversions done in the kernel which are > independant of the filesystem block size. The table in it is also completely hosed. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:43:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 435251543E for ; Thu, 28 Oct 1999 14:43:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA10601; Thu, 28 Oct 1999 14:43:20 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 14:43:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199910282143.OAA10601@apollo.backplane.com> To: Michael Beckmann Cc: hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: <19991028235225.A2535@apfel.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi ! : :1. What is the maximum size of a file on a filesystem ? :2. What is the maximum size of a filesystem ? :3. What is the maximum amount of RAM that FreeBSD can handle ? :4. What is the maximum size of a file that can be mmap´ed ? : :Furthermore, I understand that FreeBSD can´t mmap a block device. :Is it planned to change that ? : :Thanks ! :-) : :Michael The maximum size of a standard filesystem is 8 Terrabytes. The maximum size of a file depends on the filesystem. It is 8 Terrabytes on the standard UFS filesystem. FreeBSD boxes can handle up to 4 Gigabytes of main memory. Block devices are being removed from the system so the answer is no at the moment. If people have a need, we will probably introduce a block device overlay of some sort that would theoretically be mmapable. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 14:56: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D99C14C49 for ; Thu, 28 Oct 1999 14:56:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA48933; Thu, 28 Oct 1999 14:56:00 -0700 (PDT) Date: Thu, 28 Oct 1999 14:56:00 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Michael Beckmann , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-Reply-To: <199910282143.OAA10601@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Matthew Dillon wrote: > :Hi ! > : > :1. What is the maximum size of a file on a filesystem ? > :2. What is the maximum size of a filesystem ? > :3. What is the maximum amount of RAM that FreeBSD can handle ? > :4. What is the maximum size of a file that can be mmap´ed ? > : > :Furthermore, I understand that FreeBSD can´t mmap a block device. > :Is it planned to change that ? > : > :Thanks ! :-) > : > :Michael > > The maximum size of a standard filesystem is 8 Terrabytes. > > The maximum size of a file depends on the filesystem. It is 8 Terrabytes > on the standard UFS filesystem. > > FreeBSD boxes can handle up to 4 Gigabytes of main memory. > > Block devices are being removed from the system so the answer is > no at the moment. If people have a need, we will probably introduce > a block device overlay of some sort that would theoretically be mmapable. I think he means block device as in 'disk' not as in 'brwxrwxrwx" > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 15:22:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id DD7FE152F8 for ; Thu, 28 Oct 1999 15:22:47 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA02885 for hackers@freebsd.org; Fri, 29 Oct 1999 00:22:43 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9ECCA878D; Thu, 28 Oct 1999 23:43:03 +0200 (CEST) Date: Thu, 28 Oct 1999 23:43:03 +0200 From: Ollivier Robert To: hackers@freebsd.org Subject: Re: Limitations in FreeBSD Message-ID: <19991028234303.A87664@keltia.freenix.fr> Reply-To: FreeBSD Chat Mailing List Mail-Followup-To: hackers@freebsd.org References: <19991028235225.A2535@apfel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.0pre2i In-Reply-To: <19991028235225.A2535@apfel.de> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Michael Beckmann: > Furthermore, I understand that FreeBSD can´t mmap a block device. > Is it planned to change that ? What is a block device ? /me hides and runs :-) for the humour impaired... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 15:28:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.apfel.de (mail.apfel.de [195.252.143.26]) by hub.freebsd.org (Postfix) with ESMTP id 08D0F15360 for ; Thu, 28 Oct 1999 15:28:27 -0700 (PDT) (envelope-from petzi@mail.apfel.de) Received: (from petzi@localhost) by mail.apfel.de (8.9.3/8.9.3) id AAA02830; Fri, 29 Oct 1999 00:54:50 +0200 (MEST) Date: Fri, 29 Oct 1999 00:54:50 +0200 From: Michael Beckmann To: Julian Elischer Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD Message-ID: <19991029005450.A2757@apfel.de> References: <199910282143.OAA10601@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Julian Elischer on Thu, Oct 28, 1999 at 02:56:00PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 02:56:00PM -0700, Julian Elischer wrote: > > Block devices are being removed from the system so the answer is > > no at the moment. If people have a need, we will probably introduce > > a block device overlay of some sort that would theoretically be mmapable. > > I think he means block device as in 'disk' not as in 'brwxrwxrwx" I was thinking of using a disk without a filesystem, for example for the CNFS storage method in INN. This requires that the device is mmapable. OK, so I know now that I can have pretty large files in the Terabyte range. Very nice. But I assume I cannot mmap anything like a 100 GB file ? Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 15:35:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C00D154AD for ; Thu, 28 Oct 1999 15:34:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA12655; Thu, 28 Oct 1999 15:34:53 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 15:34:53 -0700 (PDT) From: Matthew Dillon Message-Id: <199910282234.PAA12655@apollo.backplane.com> To: Michael Beckmann Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: <199910282143.OAA10601@apollo.backplane.com> <19991029005450.A2757@apfel.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, Oct 28, 1999 at 02:56:00PM -0700, Julian Elischer wrote: :> > Block devices are being removed from the system so the answer is :> > no at the moment. If people have a need, we will probably introduce :> > a block device overlay of some sort that would theoretically be mmapable. :> :> I think he means block device as in 'disk' not as in 'brwxrwxrwx" : :I was thinking of using a disk without a filesystem, for example for the CNFS :storage method in INN. This requires that the device is mmapable. : :OK, so I know now that I can have pretty large files in the Terabyte range. :Very nice. But I assume I cannot mmap anything like a 100 GB file ? : :Michael Intel cpu's only have a 4G address space. Your are limited to around a 2G mmap()ing. You can mmap() any portion of a larger file but you cannot mmap() the whole file at once. The easiest thing to do is to simply create a number of fixed-sized files and tell CNFS to use them. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 15:49:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.apfel.de (mail.apfel.de [195.252.143.26]) by hub.freebsd.org (Postfix) with ESMTP id A5E5814DA5 for ; Thu, 28 Oct 1999 15:47:34 -0700 (PDT) (envelope-from petzi@mail.apfel.de) Received: (from petzi@localhost) by mail.apfel.de (8.9.3/8.9.3) id BAA02891; Fri, 29 Oct 1999 01:13:48 +0200 (MEST) Date: Fri, 29 Oct 1999 01:13:48 +0200 From: Michael Beckmann To: Matthew Dillon Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD Message-ID: <19991029011348.B2757@apfel.de> References: <199910282143.OAA10601@apollo.backplane.com> <19991029005450.A2757@apfel.de> <199910282234.PAA12655@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <199910282234.PAA12655@apollo.backplane.com>; from Matthew Dillon on Thu, Oct 28, 1999 at 03:34:53PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 03:34:53PM -0700, Matthew Dillon wrote: > :OK, so I know now that I can have pretty large files in the Terabyte range. > :Very nice. But I assume I cannot mmap anything like a 100 GB file ? > : > :Michael > > Intel cpu's only have a 4G address space. Your are limited to around > a 2G mmap()ing. You can mmap() any portion of a larger file but you > cannot mmap() the whole file at once. > > The easiest thing to do is to simply create a number of fixed-sized files > and tell CNFS to use them. Here is the problem: When you want to have 500 GB of storage, you will need 250 files. In the current implementation of nnrpd, this will need 250 file descriptors per nnrpd. This will limit the number of readers that can be supported on a system, because a nnrpd is spawned for each reader. I was told that nnrpd can be hacked to only consume file descriptors when really needed, but it´s supposed to have a performance penalty. That´s why I´m looking for a way of having large mmap´able files. Are you saying that ALL Intel CPUs, including PIII, can only address 4 GB? I probably need to look at other architectures or solve this fd problem. Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 16: 2:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id CFFE414DA5 for ; Thu, 28 Oct 1999 16:02:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA02302; Thu, 28 Oct 1999 15:53:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910282253.PAA02302@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Beckmann Cc: Matthew Dillon , Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "Fri, 29 Oct 1999 01:13:48 +0200." <19991029011348.B2757@apfel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Oct 1999 15:53:20 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That=B4s why I=B4m looking for a way of having large mmap=B4able = > files. Are you saying that ALL Intel CPUs, including PIII, can only = > address 4 GB? = That's correct; it's why the ia32 architecture has a '32' in its name. > I probably need to look at other architectures or solve this fd problem= =2E How many fd's do you plan to have open? How severe is the performance = penalty (have you actually measured it yet, or are you just going on = word of mouth)? -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 16:36:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.apfel.de (mail.apfel.de [195.252.143.26]) by hub.freebsd.org (Postfix) with ESMTP id AC693151B5 for ; Thu, 28 Oct 1999 16:36:33 -0700 (PDT) (envelope-from petzi@mail.apfel.de) Received: (from root@localhost) by mail.apfel.de (8.9.3/8.9.3) id CAA03203; Fri, 29 Oct 1999 02:02:54 +0200 (MEST) Date: Fri, 29 Oct 1999 02:02:53 +0200 From: Michael Beckmann To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD Message-ID: <19991029020253.A3005@apfel.de> References: <19991029011348.B2757@apfel.de> <199910282253.PAA02302@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <199910282253.PAA02302@dingo.cdrom.com>; from Mike Smith on Thu, Oct 28, 1999 at 03:53:20PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 03:53:20PM -0700, Mike Smith wrote: > How many fd's do you plan to have open? This would be 2^17 to 2^19. Would that be advisable ? I have never seen anything like that. > How severe is the performance > penalty (have you actually measured it yet, or are you just going on > word of mouth)? The latter. Measuring would be difficult due to lack of tools, and I´d rather not make life tests in production machines. Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 16:41:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 484D7151B5 for ; Thu, 28 Oct 1999 16:41:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA02494; Thu, 28 Oct 1999 16:32:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910282332.QAA02494@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Beckmann Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "Fri, 29 Oct 1999 02:02:53 +0200." <19991029020253.A3005@apfel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Oct 1999 16:32:03 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Oct 28, 1999 at 03:53:20PM -0700, Mike Smith wrote: > > How many fd's do you plan to have open? > = > This would be 2^17 to 2^19. Would that be advisable ? I have never > seen anything like that. That would be difficult. > > How severe is the performance = > > penalty (have you actually measured it yet, or are you just going on = > > word of mouth)? > = > The latter. Measuring would be difficult due to lack of tools, and I=B4= d > rather not make life tests in production machines. This is a failure of your approach, I think. You are trying to make a = decision without adequate information, which is never a good idea. = Craft the tools and make an informed choice. TBH, it sounds like you need to look at a different reader architecture. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 16:43:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 979C8151B5 for ; Thu, 28 Oct 1999 16:43:30 -0700 (PDT) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 125; Thu, 28 Oct 1999 16:38:24 -0700 Message-ID: <15f901bf219e$20df55c0$1e80000a@avantgo.com> From: "Scott Hess" To: "Michael Beckmann" , "Mike Smith" Cc: References: <19991029011348.B2757@apfel.de> <199910282253.PAA02302@dingo.cdrom.com> <19991029020253.A3005@apfel.de> Subject: Re: Limitations in FreeBSD Date: Thu, 28 Oct 1999 16:42:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Beckmann wrote: > On Thu, Oct 28, 1999 at 03:53:20PM -0700, Mike Smith wrote: > > How severe is the performance > > penalty (have you actually measured it yet, or are you just going on > > word of mouth)? > > The latter. Measuring would be difficult due to lack of tools, and I´d > rather not make life tests in production machines. Urk! I don't mean to be insulting, but the notion that you would roll _any_ solution out for a problem of this size based on word of mouth freaks the crap out of me. If you have a genuine need for 500Gig of news spool, and enough users that mmap'ed I/O in nntp is needed and the number of file descriptors is going to be a problem, and you're willing to change architectures if need be, then if you don't have tools - I'd suggest you write some! [And better to start early, because once you roll into production it's too late to write the tools :-),] scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 17:21:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.apfel.de (mail.apfel.de [195.252.143.26]) by hub.freebsd.org (Postfix) with ESMTP id 4A5D7154E8 for ; Thu, 28 Oct 1999 17:21:14 -0700 (PDT) (envelope-from petzi@mail.apfel.de) Received: (from root@localhost) by mail.apfel.de (8.9.3/8.9.3) id CAA03481; Fri, 29 Oct 1999 02:47:42 +0200 (MEST) Date: Fri, 29 Oct 1999 02:47:42 +0200 From: Michael Beckmann To: Scott Hess Cc: hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD Message-ID: <19991029024742.B3005@apfel.de> References: <19991029011348.B2757@apfel.de> <199910282253.PAA02302@dingo.cdrom.com> <19991029020253.A3005@apfel.de> <15f901bf219e$20df55c0$1e80000a@avantgo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <15f901bf219e$20df55c0$1e80000a@avantgo.com>; from Scott Hess on Thu, Oct 28, 1999 at 04:42:42PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 04:42:42PM -0700, Scott Hess wrote: > Urk! I don't mean to be insulting, but the notion that you would roll > _any_ solution out for a problem of this size based on word of mouth freaks > the crap out of me. Hey ! You guys seem to have pretty strict opinions about how to solve problems. Right now I am just investigating the options and asking for the properties of this FreeBSD OS (where news is not the only reason for finding out about them). > If you have a genuine need for 500Gig of news spool, This is roughly 10 days of newsfeed, btw. > and enough users that mmap'ed I/O in nntp is needed and the number of file > descriptors is going to be a problem, and you're willing to change I would like to know if that number of file descriptors is going to be a problem, could someone tell me please ? It appears that 2^17 are settable through sysctl, but will I actually be able to use that many ? (Yes, I could write a tool to find it out, but I am willing to rely on word of mouth here). Thanks, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 17:36:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 82519154AD for ; Thu, 28 Oct 1999 17:36:26 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-213.bellatlantic.net [151.198.117.213]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA28411; Thu, 28 Oct 1999 20:36:06 -0400 (EDT) Message-ID: <3818ED2D.8DE2F050@bellatlantic.net> Date: Thu, 28 Oct 1999 20:41:17 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Michael Beckmann Cc: Matthew Dillon , Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: <199910282143.OAA10601@apollo.backplane.com> <19991029005450.A2757@apfel.de> <199910282234.PAA12655@apollo.backplane.com> <19991029011348.B2757@apfel.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Beckmann wrote: > > On Thu, Oct 28, 1999 at 03:34:53PM -0700, Matthew Dillon wrote: > > :OK, so I know now that I can have pretty large files in the Terabyte range. > > :Very nice. But I assume I cannot mmap anything like a 100 GB file ? > > : > > :Michael > > > > Intel cpu's only have a 4G address space. Your are limited to around > > a 2G mmap()ing. You can mmap() any portion of a larger file but you > > cannot mmap() the whole file at once. > > > > The easiest thing to do is to simply create a number of fixed-sized files > > and tell CNFS to use them. > > Here is the problem: > When you want to have 500 GB of storage, you will need 250 files. In the current > implementation of nnrpd, this will need 250 file descriptors per nnrpd. This will I think this situation will bring you where you started: you will be able to map a whole one file, but only one file at a time, not 250 files at once. So it would be simpler and more efficient to have only one big file and map the pieces of it as needed. I would also suggest to make these pieces much smaller than 2G: then you will be able to map a number of them at once and when you decide to substitute one mapped piece for another you won't have to re-create the page tables for the whole 2G of the address space. I guess the best size of these pieces depends on the typical request size of your application. > limit the number of readers that can be supported on a system, because a nnrpd is > spawned for each reader. I was told that nnrpd can be hacked to only consume file > descriptors when really needed, but it´s supposed to have a performance penalty. Mapping and unmapping frequently the whole 2G files would impose much higher performance penalty. Also if you plan to have many processes doing mmaps don't forget that each of them would consume some kernel address space for its page tables. With big mmaps you would exhaust your kernel address space very quickly (an example of this is that Oracle on UnixWare uses special calls using 4MB physical pages to map its SGA, otherwise the kernel virtual memory on a large-physical-memory machine gets exhausted very quickly and with terrible consequences). The page tables for such amounts of memory would consume the kernel virtual memory much faster than 250 file descriptors per process. > That´s why I´m looking for a way of having large mmap´able files. Are you saying > that ALL Intel CPUs, including PIII, can only address 4 GB? I probably need to > look at other architectures or solve this fd problem. Pentiums can address more physical memory (again, UnixWare supports up to 16GB of physical memory) - at the price of some performance penalty, but not virtual memory. A 64-bit architecture such as Alpha, UltraSPARC or HP PA-8000 may help you. But I guess what you really need is to split your very big file into a number of pages of some reasonable size and map/unmap them as needed. Although the RISC architectures (at least PA-RISC and RS/6000 but I think the others too) use different organisation of the page tables and for them mapping the big memory areas in many processes should not be a big problem. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 17:55: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5231814E61 for ; Thu, 28 Oct 1999 17:54:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA13725; Thu, 28 Oct 1999 17:54:46 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 17:54:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199910290054.RAA13725@apollo.backplane.com> To: Michael Beckmann Cc: Scott Hess , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: <19991029011348.B2757@apfel.de> <199910282253.PAA02302@dingo.cdrom.com> <19991029020253.A3005@apfel.de> <15f901bf219e$20df55c0$1e80000a@avantgo.com> <19991029024742.B3005@apfel.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Urk! I don't mean to be insulting, but the notion that you would roll :> _any_ solution out for a problem of this size based on word of mouth freaks :> the crap out of me. : :Hey ! You guys seem to have pretty strict opinions about how to solve problems. :Right now I am just investigating the options and asking for the properties of :this FreeBSD OS (where news is not the only reason for finding out about them). : :> If you have a genuine need for 500Gig of news spool, : :This is roughly 10 days of newsfeed, btw. This is roughly 20 days of newsfeed if one take the porn, warez, and binaries groups, which contain mostly junk, and try to hold onto them for the full expiration time. If the person setting up the system were to spend a little time filtering out the junk and/or adjusting the expiration it is fairly easy to get away with much smaller spools and an order of magnitude cheaper system. At BEST I wound up using around a 40G spool. If the person isn't willing to filter he pretty much deserves all the pain he creates for himself :-(. Roughly speaking, less then 1% of a typical userbase even bothers to read usenet news. In anycase... I don't know what INN is doing these days, but I do know that lots of people run large spools with it on 32 bit machines just fine. Most of the assumptions I've heard so far are absurd for *any* UNIX box, not just an intel box. INN is a heavy-weight system but it doesn't eat hundreds of file descriptors per nnrpd process. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 18:33:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 51CC314EE8; Thu, 28 Oct 1999 18:33:24 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id VAA09459; Thu, 28 Oct 1999 21:33:21 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA33215; Thu, 28 Oct 1999 21:32:51 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 Oct 1999 21:32:51 -0400 (EDT) To: dfr@nlsystems.com Cc: freebsd-hackers@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: ip forwarding broken on alpha In-Reply-To: <14359.43410.495963.975277@grasshopper.cs.duke.edu> References: <14359.43410.495963.975277@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14360.62787.116526.830259@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin writes: > > I have an older AlphaStation 600 5/266 running -current (cvsupped > last week) which is setup as a router between 2 100mb networks. When > the machine is pushed fairly hard (like running a netperf -tUDP_STREAM > -- -m 100 across the router, eg about 10-20k 100byte packets/sec ) the > alpha falls over almost instantly. I have not enabled any NAT or > firewall functionality, just ip forwarding. <...> > > This might be a red herring, but I've found that if I run the entire > ip_input path under splnet() (added splnet() around the call to > ip_input() in ipintr().), things get a hell of a lot more stable. > Rather than crashing in a few seconds, it sometimes takes minutes. > And rather than an illegal access, I tend to run out of kernel stack > space ( either a panic("possible stack overflow\n"); in > alpha/alpha/interrupt.c, or I end up in the SRM console after calling > halt from a PC which isn't in the kernel, which smells like an overrun > stack to me). I'm not sure if this is related, or if it is a separate > problem entirely. That was it. The problem is that the interrupt handler returns through exception_return, like the trap handler does. Exception_return checks to see if the last ipl the system was at was 0. If it was, it eventually lowers the ipl to zero and checks for a pending ast. This was the problem. If you're getting interrupts quickly enough, there's large window when you're still running on the interrupt stack where you're sitting at ipl0 and you can get another interrupt & build onto that stack. If you're getting 40,000 interrupts per second (forwarding 20,000 packets/sec), this can build up & rapidly run you out of stack space. I've found the system can forward 70,000 packets per second & remain perfectly stable with the appended patch. I'm not terribly good at assembler, so rather than try to be tricky & check to see if the current ipl is >= 4 (handling a device interrupt), I simply copied exception_return & skipped the ipl lowering & the check for an ast since I don't think you're ever going to need to check for an ast after an interrupt. I have NFC why mclfree was getting trashed, but it must have been caused by running out of stack space as the appended patch seems to take care of everything. Doug -- should I commit this as-is, or do you want to take a more refined approach? Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Index: exception.s =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/exception.s,v retrieving revision 1.3 diff -u -r1.3 exception.s --- exception.s 1999/08/28 00:38:26 1.3 +++ exception.s 1999/10/28 19:17:26 @@ -76,7 +76,7 @@ /* a0, a1, & a2 already set up */ mov sp, a3 ; .loc 1 __LINE__ CALL(interrupt) - jmp zero, exception_return + jmp zero, interrupt_return END(XentInt) /**************************************************************************/ Index: swtch.s =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/swtch.s,v retrieving revision 1.11 diff -u -r1.11 swtch.s --- swtch.s 1999/08/28 00:38:32 1.11 +++ swtch.s 1999/10/28 20:08:24 @@ -308,6 +308,61 @@ .set at END(exception_return) + + +LEAF(interrupt_return, 1) /* XXX should be NESTED */ + br pv, Lintr_er1 +Lintr_er1: LDGP(pv) + + ldq s1, (FRAME_PS * 8)(sp) /* get the saved PS */ + and s1, ALPHA_PSL_IPL_MASK, t0 /* look at the saved IPL */ + bne t0, Lintr_restoreregs /* != 0: can't do AST or SIR */ + + /* see if we can do an SIR */ + ldl t1, ipending /* SIR pending? */ + beq t1, Lintr_chkast /* no, try an AST*/ + + /* We've got a SIR. */ + CALL(do_sir) /* do the SIR; lowers IPL */ + +Lintr_chkast: + + and s1, ALPHA_PSL_USERMODE, t0 /* are we returning to user? */ + beq t0, Lintr_restoreregs /* no: just return */ + +Lintr_setfpenable: + /* enable FPU based on whether the current proc is fpcurproc */ + ldq t0, curproc + ldq t1, fpcurproc + cmpeq t0, t1, t0 + mov zero, a0 + cmovne t0, 1, a0 + call_pal PAL_OSF1_wrfen + +Lintr_restoreregs: + /* set the hae register if this process has specified a value */ + ldq t0, curproc + beq t0, Lintr_nohae + ldq t1, P_MD_FLAGS(t0) + and t1, MDP_HAEUSED + beq t1, Lintr_nohae + ldq a0, P_MD_HAE(t0) + ldq pv, chipset + CHIPSET_WRITE_HAE + CALL((pv)) +Lintr_nohae: + + /* restore the registers, and return */ + bsr ra, exception_restore_regs /* jmp/CALL trashes pv/t12 */ + ldq ra,(FRAME_RA*8)(sp) + .set noat + ldq at_reg,(FRAME_AT*8)(sp) + + lda sp,(FRAME_SW_SIZE*8)(sp) + call_pal PAL_OSF1_rti + .set at + END(interrupt_return) + + LEAF(exception_save_regs, 0) stq v0,(FRAME_V0*8)(sp) stq a3,(FRAME_A3*8)(sp) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 18:49: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 2AB3615545 for ; Thu, 28 Oct 1999 18:48:51 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id VAA28249; Thu, 28 Oct 1999 21:48:38 -0400 (EDT) Date: Thu, 28 Oct 1999 20:45:39 -0400 (EDT) From: Zhihui Zhang To: Matthew Dillon Cc: "Chris D. Faulhaber" , Michael Beckmann , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-Reply-To: <199910282135.OAA10010@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Matthew Dillon wrote: > :On Thu, 28 Oct 1999, Michael Beckmann wrote: > : > :> Hi ! > :> > :> 1. What is the maximum size of a file on a filesystem ? > :> 2. What is the maximum size of a filesystem ? > : > :http://www.freebsd.org/FAQ/install.html#AEN704 > : > :----- > :Chris D. Faulhaber | All the true gurus I've met never > :System/Network Administrator, | claimed they were one, and always > > The document is not quite right. The maximum size is limited to > 8 Terrabytes due to block-size conversions done in the kernel which are > independant of the filesystem block size. Can you tell me how to get the 8TB value? I know all the things about indirect blocks and I know that we use negative numbers for those indirect blocks. Thanks. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 18:56:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D35B14EAE for ; Thu, 28 Oct 1999 18:56:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA14208; Thu, 28 Oct 1999 18:55:53 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 18:55:53 -0700 (PDT) From: Matthew Dillon Message-Id: <199910290155.SAA14208@apollo.backplane.com> To: Zhihui Zhang Cc: "Chris D. Faulhaber" , Michael Beckmann , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> The document is not quite right. The maximum size is limited to :> 8 Terrabytes due to block-size conversions done in the kernel which are :> independant of the filesystem block size. : :Can you tell me how to get the 8TB value? I know all the things about :indirect blocks and I know that we use negative numbers for those indirect :blocks. Thanks. : :-Zhihui The kernel uses 512 byte blocks internally. 32 bit block number quantities are used. To avoid sign problems we only allow 31 bits to be used within the kernel (negative block number quantities are also used within the kernel to identify meta-data). So: 2^31 = 2 billion x 512 = 1 TB. Hmm. That isn't 8 TB. I think we might have a problem over 1 TB with mmap() and the VM system. Grr. Maybe the I/O subsystem too. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 19:29:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from usc.edu (usc.edu [128.125.253.136]) by hub.freebsd.org (Postfix) with ESMTP id 079A314EFF for ; Thu, 28 Oct 1999 19:29:05 -0700 (PDT) (envelope-from walker@usc.edu) Received: from skat.usc.edu (root@skat.usc.edu [128.125.253.131]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id TAA20855; Thu, 28 Oct 1999 19:29:02 -0700 (PDT) Received: from cohiba.usc.edu (cohiba.usc.edu [128.125.29.205]) by skat.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id TAA20264; Thu, 28 Oct 1999 19:29:01 -0700 (PDT) Date: Thu, 28 Oct 1999 19:28:58 -0700 (Pacific Daylight Time) From: Michael Walker To: hackers@FreeBSD.ORG Cc: Michael Beckmann Subject: Re: Limitations in FreeBSD In-Reply-To: <19991029011348.B2757@apfel.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here is the problem: > When you want to have 500 GB of storage, you will need 250 files. In the = current > implementation of nnrpd, this will need 250 file descriptors per nnrpd. T= his will > limit the number of readers that can be supported on a system, because a = nnrpd is > spawned for each reader. I was told that nnrpd can be hacked to only cons= ume file > descriptors when really needed, but it=B4s supposed to have a performance= penalty. > That=B4s why I=B4m looking for a way of having large mmap=B4able files. A= re you saying > that ALL Intel CPUs, including PIII, can only address 4 GB? I probably ne= ed to > look at other architectures or solve this fd problem. >=20 > Michael Is FreeBSD available for Alpha's 64 bit arch (1.8e19)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 19:30:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id DA19714D96 for ; Thu, 28 Oct 1999 19:30:55 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-105.bellatlantic.net [151.198.135.105]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id WAA21887; Thu, 28 Oct 1999 22:30:45 -0400 (EDT) Message-ID: <38190808.7B403D4E@bellatlantic.net> Date: Thu, 28 Oct 1999 22:35:52 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-980222-SNAP i386) MIME-Version: 1.0 To: Matthew Dillon Cc: Michael Beckmann , Scott Hess , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD References: <19991029011348.B2757@apfel.de> <199910282253.PAA02302@dingo.cdrom.com> <19991029020253.A3005@apfel.de> <15f901bf219e$20df55c0$1e80000a@avantgo.com> <19991029024742.B3005@apfel.de> <199910290054.RAA13725@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :> If you have a genuine need for 500Gig of news spool, > : > :This is roughly 10 days of newsfeed, btw. > > This is roughly 20 days of newsfeed if one take the porn, warez, and > binaries groups, which contain mostly junk, and try to hold onto them > for the full expiration time. If the person setting up the system > were to spend a little time filtering out the junk and/or adjusting the > expiration it is fairly easy to get away with much smaller spools and an > order of magnitude cheaper system. At BEST I wound up using around a > 40G spool. If the person isn't willing to filter he pretty much deserves > all the pain he creates for himself :-(. Roughly speaking, less then 1% > of a typical userbase even bothers to read usenet news. I think if such a high amount of space with such a high number of parallel users is a must then a lot simpler approach would be to divide the news spool (say, by newsgroups) among multiple machines and set up one machine as a kind of proxy, to accept requests from the users and forward them to a machine which really has this particular newsgroup on it. That would also solve the problem with the CPU load and memory size. For further scalability there may be multiple proxy machines and a load balancing appliance of the same kind as the ones used for the web servers. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 20:26:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 730DB14E95 for ; Thu, 28 Oct 1999 20:26:20 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id XAA04715; Thu, 28 Oct 1999 23:24:21 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Thu, 28 Oct 1999 23:24:20 -0400 (EDT) From: Chuck Youse To: Mike Smith Cc: Michael Beckmann , Matthew Dillon , Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-Reply-To: <199910282253.PAA02302@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That=B4s why I=B4m looking for a way of having large mmap=B4able=20 > > files. Are you saying that ALL Intel CPUs, including PIII, can only=20 > > address 4 GB?=20 >=20 > That's correct; it's why the ia32 architecture has a '32' in its name. I don't believe that's true. I don't have any hard evidence within easy reach, but with the introduction of the Pentium, the address space was increased. A user process, of course, can only have 4G of addressible space (32-bit addresses) but the OS can map pages of the 4G space into a larger area. Something to do with 4MB pages instead of 4K pages. =20 Again, I could be wrong on this one. Chuck Youse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 20:41:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc158233-a.catv1.md.home.com (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 29B9014F4F for ; Thu, 28 Oct 1999 20:41:20 -0700 (PDT) (envelope-from sjr@home.net) Received: from istari.home.net (localhost.home.net [127.0.0.1]) by cc158233-a.catv1.md.home.com (8.9.3/8.9.3) with ESMTP id XAA38860 for ; Thu, 28 Oct 1999 23:41:16 -0400 (EDT) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <199910290341.XAA38860@cc158233-a.catv1.md.home.com> Date: Thu, 28 Oct 1999 23:41:15 -0400 (EDT) From: "Stephen J. Roznowski" Subject: CCD questions To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking at the tutorial on building CCDs at http://www.freebsd.org/tutorials/formatting-media/x205.html It seems that this page needs to be updated to include the FAQ entry between the ccdconfig and newfs. [I don't remember the error I had before I did the disklabel...] # ccdconfig ccd0 32 0 /dev/sd0c /dev/sd1c /dev/sd2c >> # disklabel ccd0 > /tmp/ccd.label >> # disklabel -Rr ccd0 /tmp/ccd.label # newfs /dev/rccd0c Is this really the case? [If so, I'll send-pr a correction] Also, "newfs -v /dev/ccd0c" yields newfs: /dev/rccd0c: `c' partition is unavailable but "newfs /dev/ccd0c" works. Why is this? Finally, the CCD homepage at http://stampede.cs.berkeley.edu/ccd/ seems unavailable. Is this temporary or permanent? Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 20:41:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 3EE8215513 for ; Thu, 28 Oct 1999 20:41:38 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA00720; Thu, 28 Oct 1999 23:41:15 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-Id: <199910290341.XAA00720@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910282253.PAA02302@dingo.cdrom.com> Date: Thu, 28 Oct 1999 23:41:14 -0400 (EDT) From: John Baldwin To: Mike Smith Subject: Re: Limitations in FreeBSD Cc: hackers@FreeBSD.ORG, Julian Elischer , Matthew Dillon , Michael Beckmann Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-99 Mike Smith wrote: > >> That´s why I´m looking for a way of having large mmap´able >> files. Are you saying that ALL Intel CPUs, including PIII, can only >> address 4 GB? > > That's correct; it's why the ia32 architecture has a '32' in its > name. Note quite. With PAE (Page Address Extensions available on PPro's and some later chips) you can get an extra 4 bits, for a total of 36 bits of addressable space, or 64 Gig. That still won't help out very much, however, for this problem. --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 20:41:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 0DF0115512 for ; Thu, 28 Oct 1999 20:41:46 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA00750; Thu, 28 Oct 1999 23:41:28 -0400 (EDT) (envelope-from jobaldwi@vt.edu) Message-Id: <199910290341.XAA00750@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 28 Oct 1999 23:41:28 -0400 (EDT) From: John Baldwin To: Chuck Youse Subject: Re: Limitations in FreeBSD Cc: hackers@FreeBSD.ORG, Julian Elischer , Matthew Dillon , Michael Beckmann , Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Oct-99 Chuck Youse wrote: > >> > That´s why I´m looking for a way of having large mmap´able >> > files. Are you saying that ALL Intel CPUs, including PIII, can >> > only >> > address 4 GB? >> >> That's correct; it's why the ia32 architecture has a '32' in its >> name. > > I don't believe that's true. I don't have any hard evidence within > easy > reach, but with the introduction of the Pentium, the address space > was > increased. A user process, of course, can only have 4G of > addressible > space (32-bit addresses) but the OS can map pages of the 4G space > into a > larger area. It was the PPro, not the Pentium, and it is called Page Address Extensions.. it does some funky stuff with the page tables to gain an extra 4 bits for a total of 64 gig of addressable space. It ends up using 4k and 2mb pages. > Something to do with 4MB pages instead of 4K pages. This is a seperate issue known as Page Size Extensions and actually was present in some i486dx4/100's. Basically, it allows you to directly map 4mb with a single page entry by leaving out the bottommost layer of the page tables. > Again, I could be wrong on this one. > > Chuck Youse --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 20:50: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.aye.net (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (Postfix) with SMTP id 535231504D for ; Thu, 28 Oct 1999 20:49:56 -0700 (PDT) (envelope-from barrett@phoenix.aye.net) Received: (qmail 13941 invoked by uid 1000); 29 Oct 1999 03:52:20 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Oct 1999 03:52:20 -0000 Date: Thu, 28 Oct 1999 23:52:20 -0400 (EDT) From: Barrett Richardson To: Michael Beckmann Cc: Matthew Dillon , Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-Reply-To: <19991029011348.B2757@apfel.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Michael Beckmann wrote: > Here is the problem: > When you want to have 500 GB of storage, you will need 250 files. In the = current > implementation of nnrpd, this will need 250 file descriptors per nnrpd. T= his will > limit the number of readers that can be supported on a system, because a = nnrpd is > spawned for each reader. I was told that nnrpd can be hacked to only cons= ume file > descriptors when really needed, but it=B4s supposed to have a performance= penalty. > That=B4s why I=B4m looking for a way of having large mmap=B4able files. A= re you saying > that ALL Intel CPUs, including PIII, can only address 4 GB? I probably ne= ed to > look at other architectures or solve this fd problem. >=20 > Michael >=20 Have a look in news.software.nntp. Some of the folks there have built some monster news systems on intel boxes (including FreeBSD). They surely have encountered some of the hurdles you forsee. There was an excellent thread last summer about building a distributed scalable news system that would scale to a million users with a FreeBSD/Diablo combination. A search for Joe Greco and Diablo at deja should turn up some gems. - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 20:50: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9EFC8154F3 for ; Thu, 28 Oct 1999 20:50:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA16929; Thu, 28 Oct 1999 20:49:46 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 20:49:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199910290349.UAA16929@apollo.backplane.com> To: John Baldwin Cc: Chuck Youse , hackers@FreeBSD.ORG, Julian Elischer , Michael Beckmann , Mike Smith Subject: Re: Limitations in FreeBSD References: <199910290341.XAA00750@server.baldwin.cx> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yuch. The page address extension junk is just that... junk. Besides, as was mentioned it wouldn't help mmap() at all. Registers are 32 bits and nobody is going to revisit the segmentation (retch) stuff. Ugh, two icky things in one paragraph, excuse me please while I take a trip to the bathroom! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 21:56:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 51ED214C20; Thu, 28 Oct 1999 21:56:20 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id VAA10430; Thu, 28 Oct 1999 21:56:05 -0700 (PDT) Message-Id: <199910290456.VAA10430@lestat.nas.nasa.gov> To: Andrew Gallatin Cc: dfr@nlsystems.com, freebsd-hackers@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ip forwarding broken on alpha Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 28 Oct 1999 21:56:04 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999 21:32:51 -0400 (EDT) Andrew Gallatin wrote: > exception_return & skipped the ipl lowering & the check for an ast > since I don't think you're ever going to need to check for an ast > after an interrupt. Nonsense. ASTs are a key part of process scheduling, and I'd bet that you run into strange scheduling behaviour if you don't deal with ASTs after e.g. clock interrupts. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 22:11:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 8E6BD15605 for ; Thu, 28 Oct 1999 22:11:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA03970; Thu, 28 Oct 1999 22:02:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910290502.WAA03970@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Youse Cc: hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "Thu, 28 Oct 1999 23:24:20 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Oct 1999 22:02:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's correct; it's why the ia32 architecture has a '32' in its name= =2E > = > I don't believe that's true. I don't have any hard evidence within eas= y > reach, but with the introduction of the Pentium, the address space was > increased. A user process, of course, can only have 4G of addressible > space (32-bit addresses) but the OS can map pages of the 4G space into = a > larger area. > = > Something to do with 4MB pages instead of 4K pages. = > = > Again, I could be wrong on this one. Think about it for a second. How big is a pointer? -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 22:23:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 46A9014FDF for ; Thu, 28 Oct 1999 22:23:30 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11h4Vd-0001Zu-00; Thu, 28 Oct 1999 23:23:30 -0600 Message-ID: <38192F50.CCDC0B51@softweyr.com> Date: Thu, 28 Oct 1999 23:23:28 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Stephen J. Roznowski" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CCD questions References: <199910290341.XAA38860@cc158233-a.catv1.md.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Stephen J. Roznowski" wrote: > > I'm looking at the tutorial on building CCDs at Why? Do you have a compelling reason not to use Vinum volume manager? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 22:55:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id B20B814D1B for ; Thu, 28 Oct 1999 22:55:30 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA37270 for ; Fri, 29 Oct 1999 12:55:16 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 29 Oct 1999 12:55:15 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: RTLD_GLOBAL/RTLD_LOCAL dlopen mode flags Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! Are there any plans to implement RTLD_GLOBAL/RTLD_LOCAL mode flags for dlopen? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 23:15:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a13b146.neo.rr.com [204.210.197.146]) by hub.freebsd.org (Postfix) with ESMTP id 48A1914E7E for ; Thu, 28 Oct 1999 23:15:10 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA22947; Fri, 29 Oct 1999 02:14:28 -0400 Date: Fri, 29 Oct 1999 02:14:28 -0400 (EDT) From: Mike Nowlin To: Roger Hardiman Cc: Wes Peters , hackers@FreeBSD.ORG Subject: Re: 2 problems with the linksys mx driver In-Reply-To: <005901bf2179$e5bb9ae0$0200000a@bfg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Autonegotiation is failing. That happens in the Fast Ethernet world. > >Buying better quality switches *may* help. ;^) > > Can you get any better than 3COM's top of the range stacks? I ran into a similar problem with a couple Linksys cards under both FBSD & (ugh) Win95 -- telling the HP ProCurve 2424M to force 100BTX half-duplex (didn't try full) fixed the problem.... Still seeing this autoneg problem with my cheapy Linksys 100-only hub and my wife's Linksys card on '95... You'd figure that autoneg would work when everything's by the same manufacturer.... :) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 28 23:50:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id A6350154CE for ; Thu, 28 Oct 1999 23:50:51 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA25033 for freebsd-hackers@FreeBSD.ORG; Fri, 29 Oct 1999 08:50:50 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id IAA03867; Fri, 29 Oct 1999 08:36:33 +0200 (MET DST) (envelope-from j) Message-ID: <19991029083633.54208@uriah.heep.sax.de> Date: Fri, 29 Oct 1999 08:36:33 +0200 From: J Wunsch To: freebsd-hackers@FreeBSD.ORG Subject: Re: The sppp driver Reply-To: Joerg Wunsch References: <199910282015.WAA01594@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Julian Elischer on Thu, Oct 28, 1999 at 02:41:57PM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Julian Elischer wrote: > of course if you want to be really generic, we've just added the > netgraph code to -current which implements a lot more than the > rather specialised sppp code. Sure, i was only answering a question. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 0:22: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from omnix.net (omnix.net [195.154.168.66]) by hub.freebsd.org (Postfix) with SMTP id 0E8A714FDE for ; Fri, 29 Oct 1999 00:21:54 -0700 (PDT) (envelope-from didier@omnix.net) Received: (qmail 5037 invoked by uid 200); 29 Oct 1999 07:21:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Oct 1999 07:21:53 -0000 Date: Fri, 29 Oct 1999 07:21:53 +0000 (GMT) From: Didier Derny To: Alban Hertroys Cc: Ilia Chipitsine , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? In-Reply-To: <19991028092821.453091DC9@wit401310.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I saw it once too but it came from a defective adaptec 2940 board On Thu, 28 Oct 1999, Alban Hertroys wrote: > On 28 Oct, Didier Derny wrote: > > > > I've never had a crashed file system with Freebsd (I started with FreeBSD > > 1.1) > > I've seen it happen once. Eventually it turned out that the drive had > become too hot, and FreeBSD wasn't able to synchronize it's data. No > miracle the root file system was broken after that... > that's why I'm selling computers in industial rack mount boxes with a correct cooling system (standard boxes are often has hot as hell with 10000rpm disks). > -- > Alban Hertroys. > http://wit401310.student.utwente.nl > --- > If I had a sig it would be fun. > The quest for the Holy Sig has begun. > I have not yet a clue, > What will you see next issue? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 2:53:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8F84E14D0B; Fri, 29 Oct 1999 02:53:06 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA72539; Fri, 29 Oct 1999 10:53:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 29 Oct 1999 10:53:29 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: freebsd-hackers@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: ip forwarding broken on alpha In-Reply-To: <14360.62787.116526.830259@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Andrew Gallatin wrote: > > Andrew Gallatin writes: > > > > I have an older AlphaStation 600 5/266 running -current (cvsupped > > last week) which is setup as a router between 2 100mb networks. When > > the machine is pushed fairly hard (like running a netperf -tUDP_STREAM > > -- -m 100 across the router, eg about 10-20k 100byte packets/sec ) the > > alpha falls over almost instantly. I have not enabled any NAT or > > firewall functionality, just ip forwarding. > > <...> > > > > > This might be a red herring, but I've found that if I run the entire > > ip_input path under splnet() (added splnet() around the call to > > ip_input() in ipintr().), things get a hell of a lot more stable. > > Rather than crashing in a few seconds, it sometimes takes minutes. > > And rather than an illegal access, I tend to run out of kernel stack > > space ( either a panic("possible stack overflow\n"); in > > alpha/alpha/interrupt.c, or I end up in the SRM console after calling > > halt from a PC which isn't in the kernel, which smells like an overrun > > stack to me). I'm not sure if this is related, or if it is a separate > > problem entirely. > > That was it. > > The problem is that the interrupt handler returns through > exception_return, like the trap handler does. Exception_return checks > to see if the last ipl the system was at was 0. If it was, it > eventually lowers the ipl to zero and checks for a pending ast. This > was the problem. If you're getting interrupts quickly enough, there's > large window when you're still running on the interrupt stack where > you're sitting at ipl0 and you can get another interrupt & build onto > that stack. If you're getting 40,000 interrupts per second > (forwarding 20,000 packets/sec), this can build up & rapidly run you > out of stack space. > > I've found the system can forward 70,000 packets per second & remain > perfectly stable with the appended patch. I'm not terribly good at > assembler, so rather than try to be tricky & check to see if the > current ipl is >= 4 (handling a device interrupt), I simply copied > exception_return & skipped the ipl lowering & the check for an ast > since I don't think you're ever going to need to check for an ast > after an interrupt. > > I have NFC why mclfree was getting trashed, but it must have been > caused by running out of stack space as the appended patch seems to > take care of everything. > > Doug -- should I commit this as-is, or do you want to take a more > refined approach? I think the intention of ASTs is that they are generated whenever you are returning to user mode. This patch will essentially defer the AST until the next system call which might be unacceptable. I can see the window and its a serious problem but I'm worried about fixing it in this way. What I really want is some way to generate a 'real' AST after the PALcode has dropped the exception frame for the interrupt. Without changing to use the VMS palcode, we aren't going to get that though :-). (ASTs and SWIs are derived from the way VAXen work and the VMS palcode emulates the old vax behaviour). The main problem as I see it is that we are dropping the IPL to zero before calling the ast. I don't see why we are doing this at all. We should be able to just call the ast without changing the ipl at all. This still leaves a window in do_sir (which lowers the IPL to 1) though. Perhaps, SWIs should be handled by using another kernel thread which can be switched to instead of calling do_sir. I have to think about that some more. Could you test just removing the swpipl(0) code and see if it improves things, thanks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 2:57:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id DF46E15094 for ; Fri, 29 Oct 1999 02:57:10 -0700 (PDT) (envelope-from gena@NetVision.net.il) Received: from Burka.NetVision.net.il (burka.netvision.net.il [194.90.1.23]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id LAA26871 for ; Fri, 29 Oct 1999 11:57:08 +0200 (IST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-XFMail-Comment: Experimental version - for developers only Date: Fri, 29 Oct 1999 11:52:58 +0200 (IST) X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: freebsd-hackers@freebsd.org Subject: incoming ISDN connections (isdnd+iijppp) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I want to set up an ISDN dialin on my FreeBSD box (AVI Fritz ISDN card + i4= b configured and work fine). The client probably will be Windoze (or something similar). Does anyone has a working configuration (isdnd.rc + ppp.conf) for such a se= tup? The sample files supplied with iijppp are for dialout only. Specifically i = need to know where (and how) ppp -direct should be launched. Is it from connectproc =3D = ... in isdnd.rc or something else? Also i'd like to know how to set up ISDN callback in conjunction with 128K = mode (multilink). Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud PGP public key is available through PGP keyserver. This message was sent at 29-Oct-99 11:52:58 by XFMail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 2:59:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 33FDF14A0B; Fri, 29 Oct 1999 02:59:35 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA76319; Fri, 29 Oct 1999 11:00:07 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 29 Oct 1999 11:00:07 +0100 (BST) From: Doug Rabson To: Jason Thorpe Cc: Andrew Gallatin , freebsd-hackers@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ip forwarding broken on alpha In-Reply-To: <199910290456.VAA10430@lestat.nas.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Jason Thorpe wrote: > On Thu, 28 Oct 1999 21:32:51 -0400 (EDT) > Andrew Gallatin wrote: > > > exception_return & skipped the ipl lowering & the check for an ast > > since I don't think you're ever going to need to check for an ast > > after an interrupt. > > Nonsense. ASTs are a key part of process scheduling, and I'd bet that > you run into strange scheduling behaviour if you don't deal with ASTs > after e.g. clock interrupts. Thats correct. The problem is that we are calling the AST with interrupts enabled which allows unbounded interrupt recursion. This is true in NetBSD (at least in version 1.60 of locore.s) as well. The whole idea of ASTs and SWIs is an awful hangover from the VAX; there must be a better way. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 3:14:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wombat.is.fh-hamburg.de (wombat.is.fh-hamburg.de [141.22.192.33]) by hub.freebsd.org (Postfix) with ESMTP id C2F5714CF7 for ; Fri, 29 Oct 1999 03:14:18 -0700 (PDT) (envelope-from kuehl@lgk.de) Received: from issus.susan.fh-hamburg.de (issus.susan.fh-hamburg.de [141.22.100.39]) by wombat.is.fh-hamburg.de (8.9.3/8.9.3) with SMTP id MAA20649; Fri, 29 Oct 1999 12:13:59 +0200 (MET DST) Received: from pisces.susan.fh-hamburg.de by issus.susan.fh-hamburg.de (5.65v4.0/1.1.10.5/19Aug97-1156AM) id AA25481; Fri, 29 Oct 1999 12:10:40 +0200 Message-Id: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 In-Reply-To: <199910290502.WAA03970@dingo.cdrom.com> Date: Fri, 29 Oct 1999 12:05:55 +0200 (CEST) Reply-To: kuehl@lgk.de From: Lars Gerhard Kuehl To: Mike Smith Subject: Re: Limitations in FreeBSD Cc: hackers@FreeBSD.ORG, Chuck Youse Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Oct-99 Mike Smith wrote: >> > That's correct; it's why the ia32 architecture has a '32' in its name. >> >> I don't believe that's true. I don't have any hard evidence within easy >> reach, but with the introduction of the Pentium, the address space was >> increased. A user process, of course, can only have 4G of addressible >> space (32-bit addresses) but the OS can map pages of the 4G space into a >> larger area. The Pentium and successors can address more than 4G _physical_ memory, 32 or 64GB, I need to look into the manual. But that feature needs to be explicitely enabled. >> >> Something to do with 4MB pages instead of 4K pages. >> >> Again, I could be wrong on this one. With extended physical addressing enabled the bigger page size is 2MB instead of 4 MB. > Think about it for a second. How big is a pointer? The Intel architecture still supports segmented memory, so the effective maximum pointer size is 48 bit. Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 3:19:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from router.ems.chel.su (router.ems.chel.su [195.54.2.222]) by hub.freebsd.org (Postfix) with ESMTP id 04DE315538 for ; Fri, 29 Oct 1999 03:17:56 -0700 (PDT) (envelope-from villain@villain.home.ems.chel.su) Received: (from uucp@localhost) by router.ems.chel.su (8.9.3/8.9.3/Debian/GNU) with UUCP id QAA31328 for hackers@FreeBSD.ORG; Fri, 29 Oct 1999 16:08:05 +0600 Received: by villain.home.ems.chel.su (Postfix, from userid 1000) id 78B92AA9F; Fri, 29 Oct 1999 12:24:07 +0600 (YEKST) Date: Fri, 29 Oct 1999 12:24:06 +0600 From: Aleksey I Zavilohin To: hackers@FreeBSD.ORG Subject: Re: why FFS is THAT slower than EXT2 ? Message-ID: <19991029122406.A367@villain.home.ems.chel.su> Mail-Followup-To: hackers@FreeBSD.ORG References: <19991027174454.A99169@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991027174454.A99169@chuggalug.clues.com> Organization: villain X-Operation-System: Linux 2.3.24 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geoff Buckingham wrote: > > I was pointing out to Chuck Youse that BSD metadata writes are also > > (mostly) asynchronous now, so if FFS is truly slower than ext2fs, there > > must be some other reason. > > > I heard talk the linux folks where using btrees to better handle large > directories. No, current implementation ext2 (and, i think, pre-ext3 too) don`t use btree for handle large directories. Btree associated with Hash Reiser in LinuxWorld 8-) and resierfs. -- "Let's show this prehistoric bitch how we do things downtown!" -- The Ghostbusters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 5:12:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc158233-a.catv1.md.home.com (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id D2A8F155A7 for ; Fri, 29 Oct 1999 05:12:44 -0700 (PDT) (envelope-from sjr@home.net) Received: from istari.home.net (localhost.home.net [127.0.0.1]) by cc158233-a.catv1.md.home.com (8.9.3/8.9.3) with ESMTP id IAA40158; Fri, 29 Oct 1999 08:12:05 -0400 (EDT) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <199910291212.IAA40158@cc158233-a.catv1.md.home.com> Date: Fri, 29 Oct 1999 08:12:04 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: CCD questions To: wes@softweyr.com Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <38192F50.CCDC0B51@softweyr.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Oct, Wes Peters wrote: > "Stephen J. Roznowski" wrote: >> >> I'm looking at the tutorial on building CCDs at > > Why? Do you have a compelling reason not to use Vinum volume manager? No, but why should I use Vinum over CCD? (All I want to do is create some larger disks). I just did a search on www.freebsd.org, and all I could find about Vinum seems to imply that the software isn't ready for prime time. Also, a quick scan of the vinum(4) man page doesn't lead to a lot of confidence since a large portion of the page is devoted to "DEBUGGING PROBLEMS WITH VINUM" including kernel panics.... Is Vinum ready for prime time? Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 5:28:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from explorer.tip.CSIRO.AU (explorer.tip.CSIRO.AU [130.155.191.10]) by hub.freebsd.org (Postfix) with ESMTP id 3D9AD14DB0 for ; Fri, 29 Oct 1999 05:28:09 -0700 (PDT) (envelope-from amy@explorer.tip.CSIRO.AU) Received: from explorer.tip.CSIRO.AU (localhost [127.0.0.1]) by explorer.tip.CSIRO.AU (8.9.3/8.9.1) with ESMTP id WAA47341; Fri, 29 Oct 1999 22:28:01 +1000 (EST) (envelope-from amy@explorer.tip.CSIRO.AU) Message-Id: <199910291228.WAA47341@explorer.tip.CSIRO.AU> To: "Stephen J. Roznowski" Cc: hackers@freebsd.org Subject: Re: CCD questions In-reply-to: Your message of "Fri, 29 Oct 1999 08:12:04 -0400." <199910291212.IAA40158@cc158233-a.catv1.md.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <47337.941200079.1@explorer.tip.CSIRO.AU> Date: Fri, 29 Oct 1999 22:28:00 +1000 From: "Shaun Amy, CSIRO TIP/ATNF" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910291212.IAA40158@cc158233-a.catv1.md.home.com> you write: >On 28 Oct, Wes Peters wrote: >> "Stephen J. Roznowski" wrote: >>> >>> I'm looking at the tutorial on building CCDs at >> >> Why? Do you have a compelling reason not to use Vinum volume manager? > >No, but why should I use Vinum over CCD? (All I want to do is create >some larger disks). > >I just did a search on www.freebsd.org, and all I could find about Vinum >seems to imply that the software isn't ready for prime time. Also, a >quick scan of the vinum(4) man page doesn't lead to a lot of confidence >since a large portion of the page is devoted to "DEBUGGING PROBLEMS WITH >VINUM" including kernel panics.... > >Is Vinum ready for prime time? Vinum is included in the 3.3-RELEASE which suggests there must be a very high level of confidence in its stability and functionality. I would guess that while Vinum is being actively maintained by Greg et al., ccd is showing its age and is probably not being as actively maintained. Vinum has been around for q good amount of time - I heard Greg talk about is in September 1998 at a conference. For some fun, I recently (four weeks ago) decided to stripe and concatenate a couple of filesystems across two 4GB SCSI disks. I was so confident I moved my home directory off my older 2.2.8-STABLE box onto one of these vinum devices and whilst one user probably doesn't hit things hard I have seen no problems. Having had considerable experience with Sun's DiskSuite on Solaris boxes I didn't have much of a problem in getting things going (it was even easier than I thought). There is some excellent info on Greg's WWW site: http://www.lemis.com/vinum.html which may help you get going. Note that the RAID-5 functionality is now also present. Regards, Shaun. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 6:16: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tiscalinet.it (fornax.tiscalinet.it [195.130.224.67]) by hub.freebsd.org (Postfix) with SMTP id 5BD47155A7 for ; Fri, 29 Oct 1999 06:15:14 -0700 (PDT) (envelope-from eventsport@yahoo.com) Received: (qmail 5573 invoked by uid 7770); 29 Oct 1999 13:01:01 -0000 Received: from ca2-966.tiscalinet.it (HELO yahoo.com) (212.123.92.70) by fornax.tiscalinet.it with SMTP; 29 Oct 1999 13:01:01 -0000 Message-ID: <38199A86.94C7A33F@yahoo.com> Date: Fri, 29 Oct 1999 15:00:57 +0200 From: Vincenzo Girau Reply-To: eventsport@tiscalinet.it Organization: Eventsport - International Soccer Tournaments X-Mailer: Mozilla 4.5 [it] (Win95; I) X-Accept-Language: it MIME-Version: 1.0 Subject: Sardinia Cup 2000 - International Soccer Tournament Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear sporting friends, We want to inform you that we will organize international football tournaments in Sardinia, of which you will find more greater reports in the enclosed news. We like invite yours teams to these tournaments. When your team had interested to the participation in one or more of these foregoing events, contact us. We invite you to visit our site Internet to the address http://www.geocities.com/eventsport In the 1999 at Sardinia Cup we have had two teams from Peru, three teams from Romania. See results at http://www.geocities.com/eventsport/sardinia_cup_gb_1999.html Sardinia Cup 2000 5 - 9 July 2000 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/sardinia_cup_gb_2000.html CATEGORIES ADMITTED Categories admitted Limit of age Times of play Boys born A - Debuttanti * 1.1.1991 or 2 x 20' later B - Pulcini * Boys born 2 x 20' 1.1.1989 or later C - Esordienti Boys born 2 x 20' 1.1.1987 or later D - Giovanissimi Boys born 2 x 25' 1.1.1985 or later Boys born E - Allievi 1.1.1983 or 2 x 25' later F - Juniores Boys born 2 x 25' 1.1.1981 or later G - Womens without limit of 2 x 30' age H - Mens without limit of 2 x 30' age I - Futsal - without limit of Mens** age 2 x 25' L - Futsal - without limit of Womens** age 2 x 25' * The categories A - B played with 7-a side. ** The categories I - L played with 5-a side Dates of the tournament: 5 - 9 July 2000 Start of the Tournament: 5 July 2000 End of the Tournament: 8 July 2000 Number of matches for team: minimum 4, maximum 6. First meal: supper of the 5 July 2000 Last meal: breakfast of the 9 July 2000 Fields of play: in beat earth, in natural grass and in synthetic grass for the futsal. PROGRAMME OF THE TOURNAMENT WEDNESDAY 5 July 2000 Hours 9.00 Arrival. Meeting of all clubs. Parade at the Stadium. Hours 9.30 Opening of the Tournament at the Stadium. Official Welcome to all the participants. Hours 10.00 Start of the Tournament. Hours 16.00 Qualifying games. THURSDAY 6 July 2000 Hours 9.00 Qualifying games. Hours 16.00 Qualifying games. FRIDAY 7 July 2000 Hours 9.00 Qualifying games. Hours 16.00 Qualifying games. SATURDAY 8 July 2000 Hours 9.00 Semi-finals. Hours 16.00 Finals. Hours 20.00 Ceremony of prize-winners. SUNDAY 9 July 2000 Hours 9.00 Preparation for the departure. Departure. Maybe technical changes. INDIVIDUAL FEE OF PARTICIPATION (From the dinner of 5 July 2000 at the breakfast of 9 July 2000) EXTRA ARRANGEMENT 4 NIGHTS 4 NIGHTS 4 NIGHTS EXTRA EXTRA NIGHT B/B H/B F/B NIGHT B/B NIGHT H/B F/B Schools - players and £. £. 2 ====== ====== 200.000 ====== ====== 60.000 teamleaders 104 EURO 32 EURO Hotel*** - Boys £. £. £. £. 70.000 £. 80.000 £. (0 - 10 old 240.000 280.000 320.000 90.000 years) 125 EURO 146 EURO 166 EURO 37 EURO 42 EURO 47 EURO Hotel*** - £. £. £. £. 75.000 £. 85.000 £. adults 280.000 320.000 360.000 95.000 146 EURO 166 EURO 187 EURO 40 EURO 45 EURO 50 EURO Arrangement in room double, triple or multiple for the players. All rooms with with private bathroom. Fee of participation for every team: £. 350.000 (181 EURO)**. Fee of participation for team. that don't exploite accomodation of the Tournament (without transfers) £. 1.200.000 (620 EURO)** ** (not repayable on case of renouncement). THE INDIVIDUAL FEE OF PARTICIPATION INCLUDES: Participation at the chosen Tournament and arrangement in accomodation of your chose. THE FEE DOESN'T INCLUDE: transfers from and from the airports or the harbors, excursions, drinks, entrances and another and everything as not specified expressly to the voice "The individual fee of participation includes". SUPPLEMENT FOR SINGLE ROOM AT HOTEL***: £. 30.000 (16 EURO) italian Lires for night. TRANSPORT: Fee of transport for team. from the harbor or from the airport of Cagliari: CAGLIARI - ASSEMINI and return £. 750.000 (388 EURO) for team. FINAL DATE OF INSCRIPTION: 06 May 2000 (after this data will be accepted only inscriptions at complete places). PAYMENT: Fee of participation for team: within of the 06 May 2000. Individual fee of participation: 40% within of the 20 May 2000. Balance: within of the 06 June 2000. NOTE: the inscription will be valid only to total happened sale and if the form of inscription will have compiled in each your part. Otherwise the bookings for the hotels, the adhesion of the teams to the manifestation won't be guaranteed. Into positive case, your adhesion will have confirmed quickly from the Eventsport. For adesion or further informations about the International Football Tournaments signed in this pages contact us by fax (please with text in english, french or italian) at the number: +39 070 9459282 or send us a E-Mail: eventsport@yahoo.com Eventsport organize also: 4th Assemini Cup 2000 27 - 30 December 2000 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/assemini_cup_gb_2000.html 2st Epiphany Cup 2001 2 - 6 January 2001 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/epiphany_cup_gb_2001.html and more other tournaments http://www.geocities.com/eventsport/tournaments.html Hoping to have you like participant at one of our events and awaiting a your quick response, we offers you, Best regards, Eventsport Vincenzo Girau ================================================================================ If you don't want to receive ours messages please send a e-mail at: eventsport@yahoo.com with in the subject line "unsubscribe Eventsport" ================================================================================ Eventsport International Football Tournaments Vincenzo Girau via Po, 22 09032 Assemini (CAGLIARI) Sardinia - Italy - Europe Tel.: +39 070 9459074 Fax: +39 070 9459282 Cell.: +39 (0)338 5226170 http://www.geocities.com/eventsport http://web.tiscalinet.it/eventsport E-mail: eventsport@yahoo.com ================================================================================ Cari amici sportivi, Intendiamo informarVi che organizziamo e promuoviamo Tornei Internazionali di Calcio, dei quali troverete maggiori notizie di seguito. Ci fa piacere invitare la Vostra squadra a questi tornei. Qualora la Vostra squadra fosse interessata alla partecipazione ad una o più di queste manifestazioni suddette, Vi preghiamo di metterVi subito in contatto con noi. Vi invitiamo a visitare il nostro sito Internet all'indirizzo http://www.geocities.com/eventsport Nel 1999 al Sardinia Cup abbiamo avuto come partecipanti anche due squadre provenienti dal Perù e tre squadre dalla Romania. Vedi i risultati all'indirizzo http://www.geocities.com/eventsport/sardinia_cup_1999.html Sardinia Cup 2000 5 - 9 Luglio 2000 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/sardinia_cup_2000.html CATEGORIE PARTECIPANTI Categorie Limit of age Durata gare A - Debuttanti * nati dal 1.1.1991 2 x 20' in poi B - Pulcini * nati dal 1.1.1989 2 x 20' in poi C - Esordienti nati dal 1.1.1987 2 x 20' in poi D - Giovanissimi nati dal 1.1.1985 2 x 25' in poi E - Allievi nati dal 1.1.1983 2 x 25' in poi F - Juniores nati dal 1.1.1981 2 x 25' in poi G - Donne senza limite 2 x 30' d'età H - Uomini senza limite 2 x 30' d'età I - Calcio a 5 - senza limite Maschile** d'età 2 x 25' L - Calcio a 5 - senza limite Femminile** d'età 2 x 25' * Le categorie A - B giocano con 7 giocatori in campo. ** Le categorie I - L giocano con 5 giocatori in campo. Date di svolgimento: 5 - 9 Luglio 2000 Inizio del Torneo: 5 Luglio 2000 Fine del Torneo: 8 Luglio 2000 Numero di partite per squadra: minimo 4, massimo 6. Primo Pasto: pranzo del 5 Luglio 2000 Ultimo Pasto: colazione del 9 Luglio 2000 Campi di gioco: in terra battuta, in erba naturale e in erba sintetica per il calcio a 5. PROGRAMMA DEL TORNEO MERCOLEDI' 5 Luglio 2000: Arrivo delle squadre. Ore 9.00 Raduno di tutti i club partecipanti. Ore 9.30 Cerimonia di apertura del Torneo e benvenuto ufficiale a tutti i partecipanti. Ore 10.00 Inizio del Torneo. Ore 16.00 Qualificazioni. GIOVEDI' 6 Luglio 2000: Ore 9.00 Qualificazioni. Ore 16.00 Qualificazioni. VENERDI' 7 Luglio 2000: Ore 9.00 Qualificazioni. Ore 16.00 Qualificazioni. SABATO 8 Luglio 2000: Ore 9.00 Semifinali. Ore 16.00 Finali. Ore 20.00 Cerimonia di premiazione. DOMENICA 9 Luglio 2000: Ore 9.00 Preparativi per viaggio di ritorno. Partenza e inizio del viaggio di ritorno. Sono possibili variazioni di carattere tecnico. COSTI INDIVIDUALI DI ALLOGGIO (Dal pranzo del 5 luglio 2000 alla colazione del 9 luglio 2000) TIPO DI 4 NOTTI 4 NOTTI 4 NOTTI NOTTE NOTTE NOTTE ALLOGGIO B/B H/B F/B EXTRA B/B EXTRA H/B EXTRA F/B Scuole - atleti + £. £. 60.000 2 adulti ====== ====== 200.000 ====== ====== 32 EURO a squadra 104 EURO Hotel*** - ragazzi £. £. £. £. 70.000 £. 80.000 240.000 280.000 320.000 £. 90.000 (0 - 10 125 EURO 146 EURO 166 EURO 37 EURO 42 EURO 47 EURO anni) Hotel*** £. £. £. £. 75.000 £. 85.000 £. 95.000 - adulti 280.000 320.000 360.000 50 EURO 146 EURO 166 EURO 187 EURO 40 EURO 45 EURO B/B = Programma con pernottamento e prima colazione. H/B = Programma con mezza pensione. F/B = Programma con pensione completa. Camere doppie, triple o quadruple per gli atleti. Tutte le camere con servizi. Camere doppie per allenatori, dirigenti ed accompagnatori. Tutte le camere con servizi. Quota di partecipazione a squadra: £. 350.000 (181 EURO)**. Quota di partecipazione per squadra che non utilizza alloggi del Torneo (senza trasporti) £. 1.200.000 (620 EURO)**. ** (non rimborsabile in caso di rinuncia). LA QUOTA DI PARTECIPAZIONE COMPRENDE: Partecipazione al Torneo prescelto e pernottamenti negli alloggi di vostra scelta LA QUOTA NON COMPRENDE: trasferimenti da e per l'aeroporto o il porto di Cagliari, escursioni, bevande, ingressi, extra in genere e tutto quanto non specificato espressamente alla voce "LA QUOTA DI PARTECIPAZIONE COMPRENDE". SUPPLEMENTO CAMERA SINGOLA : £. 30.000 (16 EURO) al giorno per persona. TRASPORTO Quote di trasporto per squadre che arrivano al porto o all'aeroporto di Cagliari: CAGLIARI - ASSEMINI e ritorno £. 750.000 (388 EURO) a squadra. SCADENZA ISCRIZIONI: 6 Maggio 2000 (dopo tale data saranno accettate iscrizioni solo ad esaurimento posti). PAGAMENTO: Quota di iscrizione delle squadre: entro il 6 Maggio 2000. Pagamento quote di partecipazione per persona: 40% entro il 21 Maggio 2000. Saldo finale: entro il 6 Giugno 2000. NOTA BENE: non sarà accettata partecipazione di squadre che non abbiano regolato per tempo i loro impegni di pagamento. L'iscrizione sarà valida solo a saldo totale avvenuto e se il modulo d'iscrizione verrà compilato in ogni sua parte. Diversamente non si potranno garantire gli alloggi e quindi l'adesione della squadra al Torneo. In caso positivo, la vostra adesione vi verrà confermata al più presto da Eventsport. Per adesioni o ulteriori informazioni sui Tornei Internazionali di Calcio riportati in queste pagine contattateci tramite fax (in lingua italiana, francese o inglese) al numero: 070 9459282 o inviateci una E-Mail: eventsport@yahoo.com Eventsport organizza anche: 4° Assemini Cup 2000 27 - 30 Dicembre 2000 Assemini (CAGLIARI) - Sardegna - Italia http://www.geocities.com/eventsport/assemini_cup_2000.html 2° Epiphany Cup 2001 2 - 6 Gennaio 2001 Assemini (CAGLIARI) - Sardegna - Italia http://www.geocities.com/eventsport/epiphany_cup_2000.html e tanti altri tornei: http://www.geocities.com/eventsport/tornei.html Sperando di avere la Vostra squadra partecipante ad uno dei nostri eventi, e restando in attesa di una vostra veloce risposta, Vi porgiamo Distinti Saluti Eventsport Vincenzo Girau ================================================================================ Se tu non vuoi più ricevere nostre E-mail manda una E-mail a: eventsport@yahoo.com con soggetto "unsubscribe Eventsport" ================================================================================ Eventsport International Football Tournaments Vincenzo Girau via Po, 22 09032 Assemini (CAGLIARI) Sardinia - Italy - Europe Tel.: +39 070 9459074 Fax: +39 070 9459282 Cell.: +39 (0)338 5226170 http://www.geocities.com/eventsport http://web.tiscalinet.it/eventsport E-mail: eventsport@yahoo.com ================================================================================ Cher ami sportif, Nous voulons vous informer qui nous organizons tournois internationales de football en Sardaigne, desquelles vous trouverez plus de notices dans les pages allegués. Nous invitons votre club à la participation a ces tournois. Lorsque votre club est interessé à la participation dans une ou plus événements, s'il vous plait contactez nous. Nous vous invitons à visité nos pages in Internet à l'adresse http://www.geocities.com/eventsport Dans le 1999 au Sardinia Cup ont participé deux équipes du Peru et trois équipes de la Romanie. Les résultes sont à l'adresse http://www.geocities.com/eventsport/sardinia_cup_fr_1999.html 4éme Sardinia Cup 2000 5 - 9 Juillet 2000 Assemini (CAGLIARI) - Sardaigne - Italie http://www.geocities.com/eventsport/sardinia_cup_fr_2000.html CATÉGORIES D'ÂGE Catégories d'âge Limite d'âge Temps de jeu A - Debuttanti * Nè à partir du 2 x 20' 1.1.1991 ou après B - Pulcini * Nè à partir du 2 x 20' 1.1.1989 ou après C - Esordienti Nè à partir du 2 x 20' 1.1.1987 ou après D - Giovanissimi Nè à partir du 2 x 25' 1.1.1985 ou après E - Allievi Nè à partir du 2 x 25' 1.1.1983 ou après F - Juniores Nè à partir du 2 x 25' 1.1.1981 ou après G - Femmes sans limite d'âge 2 x 30' H - Hommes sans limite d'âge 2 x 30' I - Futsal - Hommes** sans limite d'âge 2 x 25' L - Futsal - Femmes** sans limite d'âge 2 x 25' * Les catégories A - B jouent avec sept joueurs pour équipe. ** Les catégories I - L jouent avec cinq joueurs pour équipe. Date du Tournoi: 5 - 9 Juillet 2000 Début du Tournoi: 5 Juillet 2000 Fin du Tournoi: 8 Juillet 2000 Nombre de matches par équipe: minimum 4, maximum 6. Premier repas: déjeuner du 5 Juillet 2000 Dernier repas: petit déjeuner du 9 Juillet 2000 Champs de jeu: herbeuse et en terre, synthétique pour le futsal. PROGRAMME DU TOURNOI MERCREDI 5 Juillet 2000 Heures 9.00 Arrivée. Rassemblement de toute les équipes. Défilé de toute les équipes à le stade. Heures 9.30 Ouverture du Tournoi. Bienvenue a toute les équipes participants. Heures 10.00 Début du Tournoi. JEUDI 6 Juillet 2000 Heures 9.00 Matches éliminatoires. Heures 16.00 Matches éliminatoires. VENDREDI 7 Juillet 2000 Heures 9.00 Matches éliminatoires. Heures 16.00 Matches éliminatoires. SAMEDI 8 Juillet 2000 Heures 9.00 Démi-finals. Heures 16.00 Finals. Heures 20.00 Distribution des prix. DIMANCHE 9 Juillet 2000 Heures 9.00 Préparatifs du départ. Départ. On peut vérifier changes du programme. FRAIS INDIVIDUEL DE PARTICIPATION (Du déjeuner du 5 Juillet 2000 au petit déjeuner du 9 Juillet 2000) HÉBERGEMENT 4 NUITS 4 NUITS 4 NUITS EXTRA EXTRA EXTRA B/B H/B F/B NUIT B/B NUIT H/B NUIT F/B Écoles - Joueurs + 2 £. £. dirigeants ====== ====== 200.000 ====== ====== 60.000 par équipe 104 EURO 32 EURO Hotel*** - jeunes £. £. £. £. 70.000 £. 80.000 £. (0 - 10 240.000 280.000 320.000 90.000 ans) 125 EURO 146 EURO 166 EURO 37 EURO 42 EURO 47 EURO Hotel*** - £. £. £. £. 75.000 £. 85.000 £. adults 280.000 320.000 360.000 95.000 146 EURO 166 EURO 187 EURO 40 EURO 45 EURO 50 EURO Frais de participation por chaque équipe: £. 350.000 (181 EURO)** par équipe . Frais de participation por chaque équipe qui ne utilise pas les hébergements du Tournoi (sans transferements) £. 1.200.000 (620 EURO)** par équipe. ** (ne pas remboursable dans le cas de forfait). Hébergement en chambres doubles ou multiples avec bains privés pour les joueurs. LE FRAIS INDIVIDUEL DE PARTICIPATION COMPREND: Participation au Tournoi choisi et hébergement avec traitement choisi. LE FRAIS NE COMPREND PAS: transferements de et pour les aéroports ou les ports, excursiones, boissons, entrées et extras de tout sorte et tout entier pas specifié expressément à la voix "Le frais individuel de participation comprend". SUPPLÉMENT POUR CHAMBRE INDIVIDUELLE EN HOTEL: £. 30.000 (16 EURO) par jour. TRANSPORT: Frais de transport pour équipe du port ou du airport de Cagliari: CAGLIARI - ASSEMINI et retour £. 750.000 (388 EURO) par équipe. EXPIRATION POUR L'INSCRIPTION: 06 Mai 2000 (après cette date on accepteront seulement inscriptiones jusque à la fin des places). PAYEMENT: Frais de participation por chaque équipe: entre le 06 Mai 2000. Frais individuel de participation: 40% entre le 21 Mai 2000. Solde: entre le 06 Juin 2000. NOTE: l'inscription sera valide seulement à solde total effectué et si le module d'inscription sera compilé de toutes parts. Autrement les inscriptions préalables pour les hôtels, l'inscription de l'équipe au tournoi ne seront pas garantis. Dans le cas positif, vôtre inscription sera confirmée le plus tôt possible par Eventsport. Pour adhésions ou ultérieures informations sur les Tournois Internationales de Football signés dans ces pages on peut se mettre en contact avec nous par fax (en langue anglaise, francaise ou italienne) : +39 070 9459282 ou envoyez une E-mail: eventsport@yahoo.com Eventsport organise aussi: 4éme Assemini Cup 2000 27 - 30 Decembre 2000 Assemini (CAGLIARI) - Sardaigne - Italie http://www.geocities.com/eventsport/assemini_cup_fr_2000.html 2éme Epiphany Cup 2001 2 - 6 Janvier 2001 Assemini (CAGLIARI) - Sardaigne - Italie http://www.geocities.com/eventsport/epiphany_cup_fr_2001.html et autres tournois: http://www.geocities.com/eventsport/tournois.html En espérant de voir vous comme participants à une de nos événements en Sardaigne et en attendant rapidement votre réponse, Vous veuillez agréer nos meilleures salutations. Eventsport Vincenzo Girau ================================================================================ Si tu ne veut pas recevoir our mail envoye e une E-mail: eventsport@yahoo.com avec le subject "unsubscribe Eventsport" ================================================================================ Eventsport International Football Tournaments Vincenzo Girau via Po, 22 09032 Assemini (CAGLIARI) Sardaigne - Italie - Europe Tel.: +39 070 9459074 Fax: +39 070 9459282 Cell.: +39 (0)338 5226170 http://www.geocities.com/eventsport http://web.tiscalinet.it/eventsport E-mail: eventsport@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 7:20:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DD99E14EBB; Fri, 29 Oct 1999 07:20:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA21656; Fri, 29 Oct 1999 10:20:14 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA34233; Fri, 29 Oct 1999 10:19:44 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 Oct 1999 10:19:44 -0400 (EDT) To: Doug Rabson Cc: Andrew Gallatin , freebsd-hackers@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: ip forwarding broken on alpha In-Reply-To: References: <14360.62787.116526.830259@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14361.41684.912860.445771@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson writes: > > I think the intention of ASTs is that they are generated whenever you are > returning to user mode. This patch will essentially defer the AST until > the next system call which might be unacceptable. Whoops! I hadn't realized this. > I can see the window and its a serious problem but I'm worried about > fixing it in this way. What I really want is some way to generate a 'real' > AST after the PALcode has dropped the exception frame for the interrupt. > Without changing to use the VMS palcode, we aren't going to get that > though :-). (ASTs and SWIs are derived from the way VAXen work and the VMS > palcode emulates the old vax behaviour). > > The main problem as I see it is that we are dropping the IPL to zero > before calling the ast. I don't see why we are doing this at all. We > should be able to just call the ast without changing the ipl at all. This > still leaves a window in do_sir (which lowers the IPL to 1) though. I think this is safe because if we don't lower the ipl to 0, then we cannot get recursion because of this check: ldq s1, (FRAME_PS * 8)(sp) /* get the saved PS */ and s1, ALPHA_PSL_IPL_MASK, t0 /* look at the saved IPL */ bne t0, Lrestoreregs /* != 0: can't do AST or SIR */ I think the worst that can happen is 0: ?: ipl0, interrupted 1: device interrupt : ipl4 prev. ipl == 0 --> calls do_sir, lowers ipl to 1, interrupted 2: device interrupt : ipl4, previous ipl != 0, returns > Perhaps, SWIs should be handled by using another kernel thread which can > be switched to instead of calling do_sir. I have to think about that some > more. Could you test just removing the swpipl(0) code and see if it > improves things, thanks. Yes, it improves things. Removing the swpipl(0) appears to make an alpha stable under extreme interrupt load. I'm most of the way through a cvs checkout of -current while forwarding about 15,000 packets/sec. If I can get through a buildworld under this load, I'll call it stable. I am also curious as to why the swpipl(0) was there in the first place. I was initially concerned that it was required for some reason I did not understand (like something higher up was expecting exception_return to clean up the ipl state). I did know that the PALcode puts the ipl back where it was after a hardware interrupt. This is another reason I previously thought that special casing hardware interrupts might be the right thing to do. I looked at NetBSD's CVS web, and it looks like it has been there since day one. It will be nice to loose it, as it should reduce overhead quite a bit. For clarity, I'm running with just the following now: Index: swtch.s =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/swtch.s,v retrieving revision 1.11 diff -u -c -r1.11 swtch.s cvs diff: conflicting specifications of output style *** swtch.s 1999/08/28 00:38:32 1.11 --- swtch.s 1999/10/29 13:39:46 *************** *** 263,271 **** CALL(do_sir) /* do the SIR; lowers IPL */ Lchkast: - ldiq a0, ALPHA_PSL_IPL_0 /* drop IPL to zero*/ - call_pal PAL_OSF1_swpipl - and s1, ALPHA_PSL_USERMODE, t0 /* are we returning to user? */ beq t0, Lrestoreregs /* no: just return */ --- 263,268 ---- Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 7:30:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 5C78514FAD for ; Fri, 29 Oct 1999 07:30:26 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 29 Oct 1999 15:30:23 +0100 (BST) To: freebsd-hackers@freebsd.org Subject: Procfs' pointers to files. X-Request-Do: Date: Fri, 29 Oct 1999 15:30:23 +0100 From: David Malone Message-ID: <199910291530.aa28972@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sure this has been discussed before, but I couldn't find anything doing a quick search of the lists. I've thought about trying to add a /proc/nnn/fd to allow access to a running processes file discriptors from other processes. The fdescfs only supports access to a processes own file discriptors. One complication is who to give to allow to open the file discriptors. A safe answer would seem to be only allow root to access them, as you don't want to allow unprivilegde programs to be able to steal file discriptors (say from other programs which have inhereted a file dircriptor from some privilaged program). However, procfs currently allows people to do this with an executables file. You can make hard links to and run /proc/nnn/file as it is essentially another hard link to the executable file. This could be a problem if you have suid executables protected by nonexecutable directories, as people can steal copies of the file while it is running. Is this a real problem, or is it a "well don't protect suid executables that way" problem? The permissions used in Linux's /proc seem to be more conservative and seem to prevent this. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 7:56:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 041E21553C for ; Fri, 29 Oct 1999 07:56:47 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA50220; Fri, 29 Oct 1999 09:56:29 -0500 (CDT) (envelope-from dan) Date: Fri, 29 Oct 1999 09:56:29 -0500 From: Dan Nelson To: Lars Gerhard Kuehl Cc: Mike Smith , hackers@FreeBSD.ORG, Chuck Youse Subject: Re: Limitations in FreeBSD Message-ID: <19991029095629.D48778@dan.emsphone.com> References: <199910290502.WAA03970@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kuehl@lgk.de on Fri, Oct 29, 1999 at 12:05:55PM +0200 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 29), Lars Gerhard Kuehl said: > > Think about it for a second. How big is a pointer? > > The Intel architecture still supports segmented memory, > so the effective maximum pointer size is 48 bit. gcc doesn't handle segmented memory architectures, though, so you'll have to write your own low-level memory copying operations if you want to access other segments. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 8:51:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id B8A9314A2D; Fri, 29 Oct 1999 08:51:45 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id LAA09528; Fri, 29 Oct 1999 11:51:33 -0400 (EDT) Received: from njb140bh3.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id LAA16625; Fri, 29 Oct 1999 11:51:01 -0400 (EDT) Received: by njb140bh3.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Fri, 29 Oct 1999 11:51:26 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'hackers@FreeBSD.org'" Cc: "'announce@FreeBSD.org'" Subject: TTY driver for SBNI-12x cards Date: Fri, 29 Oct 1999 11:51:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I have released beta version of the TTY driver for SBNI-12x cards for FreeBSD 3.2, 3.3 The SBNI-12x card is a short range modem. It is allow to get up to 2MB speed over plain couple of wires. Great for ISP and as "last mile" solution. For more information about the card, please visit http://www.granch.ru. ( russian only :( ) It seems to me it is working just fine. I have tested it using both FreeBSD to FreeBSD, and FreeBSD to Linux modes. The driver can be found at http://gs.inettech.com.my/gs-1.0.1a-freebsd.tar.gz The GS drivers home page is http://gs.inettech.com.my Thanks, eMax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 8:56:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 133F514CFB for ; Fri, 29 Oct 1999 08:56:03 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA05888; Fri, 29 Oct 1999 08:56:01 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 29 Oct 1999 08:56:01 -0700 (PDT) From: Doug White To: "Stephen J. Roznowski" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CCD questions In-Reply-To: <199910290341.XAA38860@cc158233-a.catv1.md.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Stephen J. Roznowski wrote: > I'm looking at the tutorial on building CCDs at > > http://www.freebsd.org/tutorials/formatting-media/x205.html I am the author of said document ;) > It seems that this page needs to be updated to include the FAQ > entry between the ccdconfig and newfs. [I don't remember the > error I had before I did the disklabel...] > > # ccdconfig ccd0 32 0 /dev/sd0c /dev/sd1c /dev/sd2c > > >> # disklabel ccd0 > /tmp/ccd.label > >> # disklabel -Rr ccd0 /tmp/ccd.label > > # newfs /dev/rccd0c > > Is this really the case? [If so, I'll send-pr a correction] ccdconfig manufactures a disklabel when you create the stripe, so you don't need to adjust the disklabel. The subdisks must have disklabels, and you can't use the C partition since ccd only uses partitions of type 4.2BSD. > Also, "newfs -v /dev/ccd0c" yields > > newfs: /dev/rccd0c: `c' partition is unavailable > > but "newfs /dev/ccd0c" works. Why is this? ccds are goofy. They're not real devices. If the tutorial says to newfs rccd then that is a problem. My tutorial needs rewriting anyway, I'm not sure it works on 3.X anymore. It completely ignores the existence of fdisk -e, for starters, and the sysinstall options have moved. fdisk -e is _too_ useful. > Finally, the CCD homepage at http://stampede.cs.berkeley.edu/ccd/ > seems unavailable. Is this temporary or permanent? CCD is deprecated by vinum. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 9:20:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id 44967155F0 for ; Fri, 29 Oct 1999 09:20:38 -0700 (PDT) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id SAA14366 for freebsd-hackers@freebsd.org; Fri, 29 Oct 1999 18:20:31 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199910291620.SAA14366@oskar.dev.nanoteq.co.za> Subject: TCP delay ack question To: freebsd-hackers@freebsd.org Date: Fri, 29 Oct 1999 18:20:30 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... We have two machines that are experiencing some interesting behaviour. The one is running a 2.1.5 FreeBSD kernel (yes old) and the other a 2.2.6-STABLE kernel (also a bit old :) ) The problem is that when transfering mail to the 2.1.5 machine it happens quite quickly, but on the 2.2.6 machine it is a lot slower. When sending from another client it is fast through both machines. After examining the packets with tcpdump, I saw that when a transfer is slow ... there are no tos flags set on the packets, when the transfer is fast .. the client sets tos 0x10 (priority) on the all the packets. I then read through TCP/IP Illustrated Vol 2 .. and came accros the TF_DELACK option which delays ACKs up to 0.5 sec with a 200ms timer interval. This seems to correlate with the slow transfers as the client would send two packets (the last with the PUSH flag set) and then the FreeBSD machine would only send the ack after 0.2 seconds. Is this correct behaviour ? The question .. Should the client always set 0x10 in the tos field ... (we don't have control over the clients) or is it possible to ignore this on the FreeBSD server (we do not yet have the sysctl option to disable the delay on acks) Thanks Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 9:48:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-6.cpinternet.com [208.149.16.6]) by hub.freebsd.org (Postfix) with ESMTP id 61B8D14DB0 for ; Fri, 29 Oct 1999 09:48:41 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id LAA03899; Fri, 29 Oct 1999 11:48:06 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 Oct 1999 11:48:06 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: charnier@xp11.frmug.org Cc: hackers@freebsd.org Subject: Re: Running unattended (ifo FFS thread) X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14361.52780.321311.23524@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth charnier@xp11.frmug.org: : : >The problem is that 'fsck -py' ignores the 'p' and will fsck every time, : >even if it's unneeded. This takes ages for me. I believe I submitted a PR : >with a 'fix' to fsck. : : According to the man page, fsck -y and fsck -p are two distincts commands. Here's a patch to fix the man page as well then: *** fsck.8.~1~ Fri Oct 29 11:42:04 1999 --- fsck.8 Fri Oct 29 11:43:30 1999 *************** *** 109,115 **** .Nm with the .Fl p ! option will correct; if it encounters other inconsistencies, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected inconsistency one or more lines will be printed identifying the filesystem on which the correction will take place, --- 109,117 ---- .Nm with the .Fl p ! option will correct, in the absence of the ! .Fl y ! option; if it encounters other inconsistencies, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected inconsistency one or more lines will be printed identifying the filesystem on which the correction will take place, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 10:39:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5DE9C15485 for ; Fri, 29 Oct 1999 10:39:35 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id KAA17842; Fri, 29 Oct 1999 10:34:41 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id KAA12433; Fri, 29 Oct 1999 10:34:37 -0700 Received: from softweyr.com (dyn7.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA12854; Fri, 29 Oct 99 10:33:13 PDT Message-Id: <3819DA63.E3B68AC1@softweyr.com> Date: Fri, 29 Oct 1999 11:33:23 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Mike Nowlin Cc: Roger Hardiman , hackers@FreeBSD.ORG Subject: Re: 2 problems with the linksys mx driver References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nowlin wrote: > > > >Autonegotiation is failing. That happens in the Fast Ethernet world. > > >Buying better quality switches *may* help. ;^) > > > > Can you get any better than 3COM's top of the range stacks? > > I ran into a similar problem with a couple Linksys cards under both FBSD & > (ugh) Win95 -- telling the HP ProCurve 2424M to force 100BTX half-duplex > (didn't try full) fixed the problem.... Still seeing this autoneg problem > with my cheapy Linksys 100-only hub and my wife's Linksys card on '95... > > You'd figure that autoneg would work when everything's by the same > manufacturer.... :) But it's not, is just all from the same assembler. The cards and boxes are assembled from a bewildering supply of chips, all from different vendors. Ethernet is so nice, because it just works, except when it doesn't. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 11: 1: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id 326221502E for ; Fri, 29 Oct 1999 11:00:57 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id LAA07280 for freebsd-hackers@freebsd.org; Fri, 29 Oct 1999 11:00:56 -0700 (MST) Date: Fri, 29 Oct 1999 11:00:56 -0700 (MST) From: "Russell L. Carter" Message-Id: <199910291800.LAA07280@vip.consys.com> To: freebsd-hackers@freebsd.org Subject: /usr/include/posix4/semaphore.h Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, The stuff defined in /usr/include/posix4/semaphore.h, is not implemented in -current, right? If I missed it, I'd appreciate a pointer... Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 11: 5:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 8BE5114FF2 for ; Fri, 29 Oct 1999 11:05:56 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (ind.alcatel.com 2.3 [OUT])) id LAA18734; Fri, 29 Oct 1999 11:05:46 -0700 (PDT) Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA14376; Fri, 29 Oct 1999 11:05:42 -0700 Received: from softweyr.com (dyn7.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA14540; Fri, 29 Oct 99 11:05:21 PDT Message-Id: <3819E1EA.83DD04B7@softweyr.com> Date: Fri, 29 Oct 1999 12:05:30 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: "Stephen J. Roznowski" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CCD questions References: <199910291212.IAA40158@cc158233-a.catv1.md.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Stephen J. Roznowski" wrote: > > On 28 Oct, Wes Peters wrote: > > "Stephen J. Roznowski" wrote: > >> > >> I'm looking at the tutorial on building CCDs at > > > > Why? Do you have a compelling reason not to use Vinum volume manager? > > No, but why should I use Vinum over CCD? (All I want to do is create > some larger disks). Because Vinum is being maintained, and because Vinum will allow you to stripe your disks instead of simple concatenate them, which will probably result in better I/O rates. > I just did a search on www.freebsd.org, and all I could find about Vinum > seems to imply that the software isn't ready for prime time. Also, a > quick scan of the vinum(4) man page doesn't lead to a lot of confidence > since a large portion of the page is devoted to "DEBUGGING PROBLEMS WITH > VINUM" including kernel panics.... And what do you do if ccd panics your system? ;^) This is just another facet of Grog's professionalism showing through. > Is Vinum ready for prime time? It had better be, since I've been using it to stripe 4 17 GB UWSCSI disks into a single 65 GB volume for about 3 months now. This is on a production server that churns 8-10 GB of new data every day - a web spider/filter machine. Vinum is much more actively maintained than ccd is, and has pretty much deprecated ccd. Vinum accomplishes all that ccd does, is simpler to use, and does much more as well. Try it, you'll like it. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 11:19:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id 8665014FF2 for ; Fri, 29 Oct 1999 11:19:14 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id OAA07695; Fri, 29 Oct 1999 14:13:03 -0400 (EDT) From: Peter Dufault Message-Id: <199910291813.OAA07695@hda.hda.com> Subject: Re: /usr/include/posix4/semaphore.h In-Reply-To: <199910291800.LAA07280@vip.consys.com> from "Russell L. Carter" at "Oct 29, 99 11:00:56 am" To: rcarter@pinyon.org (Russell L. Carter) Date: Fri, 29 Oct 1999 14:13:03 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The stuff defined in /usr/include/posix4/semaphore.h, is > not implemented in -current, right? If I missed it, I'd > appreciate a pointer... Right, not implemented. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 11:36:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id EEE29154E5 for ; Fri, 29 Oct 1999 11:36:29 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA12446; Fri, 29 Oct 1999 20:25:42 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA24249; Fri, 29 Oct 1999 20:15:18 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910291815.UAA24249@yedi.iaf.nl> Subject: Re: 2.88Mb floppies In-Reply-To: <199910282002.WAA01559@uriah.heep.sax.de> from J Wunsch at "Oct 28, 1999 10: 2:55 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 29 Oct 1999 20:15:18 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As J Wunsch wrote ... > Wilko Bulte wrote: > > > Just having installed a 2.88Mb floppy drive in one of my axp boxes > > I wonder if FreeBSD can do 2.88Mb floppy disks. From the looks > > of the contents of /sys/i386/isa/fd.c: > .... > > it appears it cannot. > > It cannot. I once tried to hack support for 2.88 MB into the existing > driver, but eventually gave up. The driver needs a complete rewrite > in order to do this (or some royally painful hackups in order to > accomodate for the differing FDC clock frequencies, wrt. seek timing > etc.). > > Once i'm retired, i promise to rewrite that driver. :-) Point taken. Project shelved ;-) It was triggered by the size of boot.flp for Alpha and the availability of a couple of 2.88Mb drives. Never mind :) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 12: 8:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bezeqint.net (mail-a.bezeqint.net [192.115.106.23]) by hub.freebsd.org (Postfix) with ESMTP id DD31715571 for ; Fri, 29 Oct 1999 12:08:31 -0700 (PDT) (envelope-from sarig@bezeqint.net) Received: from default (pt119-75.nas.bezeqint.net) by mail.bezeqint.net (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with SMTP id <0FKD0044CP5FMX@mail.bezeqint.net> for hackers@FreeBSD.ORG; Fri, 29 Oct 1999 21:08:03 +0200 (IST) Date: Fri, 29 Oct 1999 21:07:44 +0200 From: Oren Sarig Subject: Re: Limitations in FreeBSD In-reply-to: <19991029095629.D48778@dan.emsphone.com> X-Sender: sarig@mail.bezeqint.net To: hackers@FreeBSD.ORG Message-id: <3.0.6.32.19991029210744.007da290@mail.bezeqint.net> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Content-type: text/plain; charset="us-ascii" References: <199910290502.WAA03970@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:56 29/10/99 -0500, Dan Nelson wrote: >In the last episode (Oct 29), Lars Gerhard Kuehl said: >> > Think about it for a second. How big is a pointer? >> >> The Intel architecture still supports segmented memory, >> so the effective maximum pointer size is 48 bit. > >gcc doesn't handle segmented memory architectures, though, so you'll >have to write your own low-level memory copying operations if you want >to access other segments. OK, I haven't messed with this stuff in a long time, but here goes. In the Intel 32Bit architecture (IA32), when you enter protected mode you may also turn on a feature called paging (I assume fbsd uses that...). Basically, it lets you map addresses programs use (linear addresses) to actual physical addresses, by using paging tables. Most of the addresses are mapped outside of the actual memory, and so whenever somebody wants to access them, a general protection fault occurs. The kernel taps the GPF, gets the page from the swap, loads it into memory, remaps the linear address, and gives the program back the control, but now the program has the data in memory. IA32 supports up to 4Gb of physical memory with protected mode, and a whole lot more virtual memory than that with paging. For more info go to http://developer.intel.com/ and go into the Literature Center and get Intel Architecture Developer's Guide: Volume III: System Programmer's Guide (Or something along those lines). About the segments, you need to understand the differences between a flat memory model and a segmented memory model first. In a flat memory model, all the program's data, code, the stack, the TSS, the LDT, and anything else are all the same linear memory area. A program may use any of the segment registers to access any of it's data... it can use ES:BP to access the stack, or DS:BX to access some code. In a segmented memory model, the data, code, stack, TSS, and LDT are in different segments: the stack is accessed via SS:(E)SP/(E)BP, data via DS:SI or ES:DI, and code via CS:IP. (G)CC is a compiler for the flat memory model. A flat memory model is easy to acheive using paging. Basically, a proccess always has a 4Gb address space available. Some of it is for his code/data/stack... and some may be used for pipes or kernel message areas. A proccess is not aware of other proccesses, and thinks he has complete control of the system. The actual memory the proccess uses is determined through paging. Segments have nothing to do here. Hope this answers some of the questions on the memory limits, etc. :) I haven't messed with this stuff in some time, so don't take my word for it. Go read Intel's docs if this interests you. -- Oren Sarig sarig@isdn.net.il To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 13:21:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9C6E11557D for ; Fri, 29 Oct 1999 13:21:13 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA16847 for FreeBSD-hackers@freebsd.org; Fri, 29 Oct 1999 22:04:03 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA31440 for FreeBSD-hackers@freebsd.org; Fri, 29 Oct 1999 22:14:01 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910292014.WAA31440@yedi.iaf.nl> Subject: bootpd on Alpha / alignment problems To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Fri, 29 Oct 1999 22:14:01 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Alpha the bootpd does not work, it assert-fails on the size of the struct bootp being != to BP_MINPKTSZ. A bit of debugging reveals: alpine#./bootpd -d9 sizeof struct bootp=312, BP_MINPKTSZ=300 bootpd: info(6): bootptab mtime: Fri Oct 29 20:10:09 1999 bootpd: info(6): reading "/etc/bootptab" bootpd: info(6): read 1 entries (1 hosts) from "/etc/bootptab" My best bet is that the Alpha alignment inside the struct results in a bigger bootp struct. I am, however, not sure on what the right way is to fix this. Comments appreciated, Wilko ======= #define BP_MINPKTSZ 300 /* to check sizeof(struct bootp) */ struct bootp { unsigned char bp_op; /* packet opcode type */ unsigned char bp_htype; /* hardware addr type */ unsigned char bp_hlen; /* hardware addr length */ unsigned char bp_hops; /* gateway hops */ unsigned int32 bp_xid; /* transaction ID */ unsigned short bp_secs; /* seconds since boot began */ unsigned short bp_flags; /* RFC1532 broadcast, etc. */ struct in_addr bp_ciaddr; /* client IP address */ struct in_addr bp_yiaddr; /* 'your' IP address */ struct in_addr bp_siaddr; /* server IP address */ struct in_addr bp_giaddr; /* gateway IP address */ unsigned char bp_chaddr[BP_CHADDR_LEN]; /* client hardware address */ char bp_sname[BP_SNAME_LEN]; /* server host name */ char bp_file[BP_FILE_LEN]; /* boot file name */ unsigned char bp_vend[BP_VEND_LEN]; /* vendor-specific area */ /* note that bp_vend can be longer, extending to end of packet. */ }; /* -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 15:12: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 9DF4215019 for ; Fri, 29 Oct 1999 15:11:55 -0700 (PDT) (envelope-from patrykz@mycenae.ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id IAA27730; Sat, 30 Oct 1999 08:11:12 +1000 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <199910292211.IAA27730@mycenae.ilion.eu.org> To: Dan Nelson Cc: Lars Gerhard Kuehl , Mike Smith , hackers@FreeBSD.ORG, Chuck Youse Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "Fri, 29 Oct 1999 09:56:29 EST." <19991029095629.D48778@dan.emsphone.com> Date: Sat, 30 Oct 1999 08:11:12 +1000 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the last episode (Oct 29), Lars Gerhard Kuehl said: > > > Think about it for a second. How big is a pointer? > > > > The Intel architecture still supports segmented memory, > > so the effective maximum pointer size is 48 bit. The extra 16 bits of the segment don't actually contribute to the address space size on IA32, as Intel decided to do segment translation before virtual address translation (ie, all segments have to fit in the same 32bit vaddr space). PPC, on the other hand.... ;) If you want a trully gigantic address space, try a 64 bit PPC, it's got 80 bit addresses, even if they're totally and utterly useless unless you're writing a SASOS. Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 15:34:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id 6D74115126 for ; Fri, 29 Oct 1999 15:34:30 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from bone.nectar.com (bone.nectar.com [10.0.0.105]) by gw.nectar.com (Postfix) with ESMTP id 69497C008; Fri, 29 Oct 1999 17:33:14 -0500 (CDT) Received: from bone.nectar.com (localhost [127.0.0.1]) by bone.nectar.com (Postfix) with ESMTP id 568FA1DA4; Fri, 29 Oct 1999 17:34:29 -0500 (CDT) X-Mailer: exmh version 2.1.0 09/18/1999 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.com/nectar-dh-dss.txt From: Jacques Vidrine To: Wes Peters Cc: freebsd-hackers@freebsd.org, sjr@home.net In-reply-to: <3819E1EA.83DD04B7@softweyr.com> References: <199910291212.IAA40158@cc158233-a.catv1.md.home.com> <3819E1EA.83DD04B7@softweyr.com> Subject: Re: CCD questions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Oct 1999 17:34:29 -0500 Message-Id: <19991029223429.568FA1DA4@bone.nectar.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 October 1999 at 12:05, Wes Peters wrote: > and because Vinum will allow you to stripe your disks instead of > simple concatenate them, which will probably result in better I/O > rates. To be fair, ccd also allows you to stripe your disks. I find vinum far easier to use than ccd, while providing more flexibility. -- Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 18:31:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (dynamic-23.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.23]) by hub.freebsd.org (Postfix) with ESMTP id 5CD6514F26 for ; Fri, 29 Oct 1999 18:30:10 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA00682; Sat, 30 Oct 1999 01:44:04 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA00675; Fri, 29 Oct 1999 15:09:45 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910291409.PAA00675@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Julian Elischer Cc: Joerg Wunsch , freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: The sppp driver In-Reply-To: Message from Julian Elischer of "Thu, 28 Oct 1999 14:41:57 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Oct 1999 15:09:45 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Indeed :-) Watch this space ! > of course if you want to be really generic, > we've just added the netgraph code to -current which implements a lot more > than the rather specialised sppp code. > > > > On Thu, 28 Oct 1999, J Wunsch wrote: > > > (It would be nice if you formatted your message with line breaks.) > > > > "Daniel Hilevich" wrote: > > > > > But, in the later case, the control messages are = queued to the > > > control queue=20 (sp->pp_cpq) which the if_start functions doesn't > > > have access to. Should = I implement the access? > > > > Nothing you gotta worry about. The control queue is only there in > > order to get higher priority for control packets than for data > > packets, in an attempt to speedup control negotiations for interfaces > > that are `dial on demand' (i. e., have LINK1 set). This is opaque to > > the `customer' of sppp. > > > > > - How do you recommend connecting my ioctrl functions to the sppp ioctrl = > > > function > > > > Have a look at the current `customers' for sppp, which are > > sys/i4b/driver/i4b_sppp.c (for a driver that uses dialup connections), > > and sys/i386/isa/if_{ar,cx,sr}.c for drivers that use hardware links > > (like HDLC lines) without dialling. > > > > > - Is there any resource about using the sppp driver. The sppp man page = > > > isn't satisfying at all. > > > > See above. > > > > > ------=_NextPart_000_01C7_01BF09C7.C5ECB6F0 > > > Content-Type: text/html; > > > charset="windows-1255" > > > Content-Transfer-Encoding: quoted-printable > > > > Please don't do this. > > > > -- > > cheers, J"org > > > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > > Never trust an operating system you don't have sources for. ;-) -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 18:51:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc158233-a.catv1.md.home.com (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 9B61714CA8; Fri, 29 Oct 1999 18:51:27 -0700 (PDT) (envelope-from sjr@home.net) Received: from istari.home.net (localhost.home.net [127.0.0.1]) by cc158233-a.catv1.md.home.com (8.9.3/8.9.3) with ESMTP id VAA42524; Fri, 29 Oct 1999 21:46:12 -0400 (EDT) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <199910300146.VAA42524@cc158233-a.catv1.md.home.com> Date: Fri, 29 Oct 1999 21:46:11 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: Vinum (was: CCD questions) To: grog@lemis.com Cc: amy@explorer.tip.CSIRO.AU, dwhite@resnet.uoregon.edu, hackers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19991029141001.20435@mojave.worldwide.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks everyone for all the good information.... On 29 Oct, Greg Lehey wrote: > The point here is that Stepen used the -v option for newfs, which > tells newfs to ignore partition information. This is needed for > Vinum, and hasn't been used for anything else. Stephen, what does > 'newfs /dev/rccd0c' do? To be honest, I don't remember... I jotted down these notes as I was building the system, but needed to get it back in production and didn't have a lot of time to try different options. I do remember that when I followed the tutorial instructions *exactly*, it failed.. I think that the error message was something about "can't rewrite disk label". I believe that I needed to do the disklabel trick to get the newfs to complete. >>> Finally, the CCD homepage at http://stampede.cs.berkeley.edu/ccd/ >>> seems unavailable. Is this temporary or permanent? >> >> CCD is deprecated by vinum. > > I think that, as long as ccd is still available (and I don't see it > going away soon), the docco should be available too. Perhaps the tutorial should be updated to point folks towards vinum? Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 18:51:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc158233-a.catv1.md.home.com (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 9B61714CA8; Fri, 29 Oct 1999 18:51:27 -0700 (PDT) (envelope-from sjr@home.net) Received: from istari.home.net (localhost.home.net [127.0.0.1]) by cc158233-a.catv1.md.home.com (8.9.3/8.9.3) with ESMTP id VAA42524; Fri, 29 Oct 1999 21:46:12 -0400 (EDT) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <199910300146.VAA42524@cc158233-a.catv1.md.home.com> Date: Fri, 29 Oct 1999 21:46:11 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: Vinum (was: CCD questions) To: grog@lemis.com Cc: amy@explorer.tip.CSIRO.AU, dwhite@resnet.uoregon.edu, hackers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19991029141001.20435@mojave.worldwide.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks everyone for all the good information.... On 29 Oct, Greg Lehey wrote: > The point here is that Stepen used the -v option for newfs, which > tells newfs to ignore partition information. This is needed for > Vinum, and hasn't been used for anything else. Stephen, what does > 'newfs /dev/rccd0c' do? To be honest, I don't remember... I jotted down these notes as I was building the system, but needed to get it back in production and didn't have a lot of time to try different options. I do remember that when I followed the tutorial instructions *exactly*, it failed.. I think that the error message was something about "can't rewrite disk label". I believe that I needed to do the disklabel trick to get the newfs to complete. >>> Finally, the CCD homepage at http://stampede.cs.berkeley.edu/ccd/ >>> seems unavailable. Is this temporary or permanent? >> >> CCD is deprecated by vinum. > > I think that, as long as ccd is still available (and I don't see it > going away soon), the docco should be available too. Perhaps the tutorial should be updated to point folks towards vinum? Thanks, -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 21:14:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 14D5E14C8C for ; Fri, 29 Oct 1999 21:14:44 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id GAA22428; Sat, 30 Oct 1999 06:14:32 +0200 (CEST) Message-Id: <199910300414.GAA22428@midten.fast.no> To: wes@softweyr.com Cc: sjr@home.net, freebsd-hackers@FreeBSD.ORG Subject: Re: CCD questions From: Tor.Egge@fast.no In-Reply-To: Your message of "Fri, 29 Oct 1999 12:05:30 -0600" References: <3819E1EA.83DD04B7@softweyr.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 30 Oct 1999 06:14:32 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Because Vinum is being maintained, and because Vinum will allow you to > stripe your disks instead of simple concatenate them, which will probably > result in better I/O rates. Some simple measurements shows ccd to be slightly faster when striping 11 disks, then running 130 threads reading 1MB blocks from random sector-aligned positions in a 10 GB file. with Vinum: 70 MB/s (2 of the 11 subdisks shown in iostat output) tty da5 da6 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 94 171.82 36 5.96 174.53 38 6.48 0 0 16 3 80 0 35 173.90 36 6.13 174.79 36 6.10 0 0 9 3 88 1 47 175.33 35 6.01 173.96 38 6.44 0 0 9 3 88 1 378 175.69 38 6.53 170.85 38 6.28 0 0 9 3 88 1 37 176.47 37 6.42 173.21 35 5.87 0 0 9 3 88 0 36 176.05 39 6.72 172.27 35 5.87 0 0 9 3 87 0 36 168.95 40 6.60 172.89 36 6.14 0 0 9 4 87 0 36 169.44 39 6.42 171.73 38 6.30 0 0 8 4 88 0 36 172.64 37 6.24 174.79 38 6.44 0 0 9 3 88 With ccd: 80 MB/s tty ccd1 cpu tin tout KB/t tps MB/s us ni sy in id 0 39 204.46 408 81.56 0 0 5 1 94 0 39 205.28 413 82.75 0 0 5 1 94 0 39 204.91 438 87.72 0 0 7 1 92 0 39 204.96 429 85.96 0 0 6 1 93 0 39 205.13 439 87.85 0 0 6 1 93 0 39 204.80 448 89.61 0 0 5 1 94 0 39 204.77 428 85.66 0 0 5 1 94 0 39 204.66 440 87.95 0 0 6 1 93 0 39 205.58 421 84.61 0 0 5 1 94 ccd is also capable of striping disks with different sizes. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 23:43:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59]) by hub.freebsd.org (Postfix) with ESMTP id 587A814F66; Fri, 29 Oct 1999 23:43:16 -0700 (PDT) (envelope-from minwei@Exchange.Microsoft.com) Received: by dfssl with Internet Mail Service (5.5.2650.21) id ; Fri, 29 Oct 1999 23:43:11 -0700 Message-ID: <01D6C7224936D211BA450000F805D5380F8D04B4@TOTO> From: "Min Wei (Exchange)" To: freebsd-net@FreeBSD.ORG, "'hackers@freebsd.org'" Subject: FreeBSD reboots every 45 minutes Date: Fri, 29 Oct 1999 23:41:31 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF22A1.CA8731C0" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF22A1.CA8731C0 Content-Type: text/plain Hi. I am confused at the following strange FreeBSD reboot case. I have a Dell PowerEdge 2300 dual proc machine with Intel 100/10 netcard. I put 3.2 SMP kernel with options MAXUSERS=256 and NMBCLUSTERS=32768. Otherwise kernel is almost the same as the stock FreeBSD kernel. When I started some live Web tests with my custom Apache module, I found that the FreeBSD panics every 45 minutes. First, I thought it was some FIN_WAIT_2 problem. So I applied julian(@whistle.com)'s patch. But it still reboots after 45 minutes of testing. Then I thought it might be running out of mbufs due to load. However, the number of allocated mbufs is no where near 32768 just seconds before the reboot. One additional piece of data is that in my simluated environment, I was able to pound the machine with FreeBSD 3.2 SMP for more than 12 hours straight with 600 running Apache child processes. I haven't tried to dump kernel core to see the call stack since the machine is actually far away at a hosting site. I wonder if anyone is aware of SMP kernel issues with Dell PowerEdge machines. I will try single processor mode when I could arrange more live time. However I am kind of suspect somewhere in net driver or TCP/IP stack is screwed up. Any help on the possible reboot cause is greatly appreciated. Otherwise I might have to try BSDI which is something I would rather not to do. Thanks, --min ------_=_NextPart_001_01BF22A1.CA8731C0 Content-Type: text/html FreeBSD reboots every 45 minutes

Hi. I am confused at the following strange FreeBSD reboot case.
I have a Dell PowerEdge 2300 dual proc machine with Intel 100/10 netcard.
I put 3.2 SMP kernel with options MAXUSERS=256 and NMBCLUSTERS=32768.
Otherwise kernel is almost the same as the stock FreeBSD kernel.

When I started some live Web tests with my custom Apache module,
I found that the FreeBSD panics every 45 minutes. First, I thought
it was some FIN_WAIT_2 problem. So I applied julian(@whistle.com)'s
patch. But it still reboots after 45 minutes of testing. Then
I thought it might be running out of mbufs due to load. However, the
number of allocated mbufs is no where near 32768 just seconds before the reboot.

One additional piece of data is that in my simluated environment, I was able
to pound the machine with FreeBSD 3.2 SMP for more than 12 hours straight
with 600 running Apache child processes.

I haven't tried to dump kernel core to see the call stack since the machine
is actually far away at a hosting site.

I wonder if anyone is aware of SMP kernel issues with Dell PowerEdge machines.
I will try single processor mode when I could arrange more live time.
However I am kind of suspect somewhere in net driver or TCP/IP stack
is screwed up.

Any help on the possible reboot cause is greatly appreciated. Otherwise I might
have to try BSDI which is something I would rather not to do.

        Thanks,
        --min

------_=_NextPart_001_01BF22A1.CA8731C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 29 23:50:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5AA2E14C93 for ; Fri, 29 Oct 1999 23:50:25 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p03-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.132]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA28241; Sat, 30 Oct 1999 15:50:19 +0900 (JST) Message-ID: <381A94AF.9DEB1710@newsguy.com> Date: Sat, 30 Oct 1999 15:48:15 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Min Wei (Exchange)" Cc: "'hackers@freebsd.org'" Subject: Re: FreeBSD reboots every 45 minutes References: <01D6C7224936D211BA450000F805D5380F8D04B4@TOTO> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Min Wei (Exchange)" wrote: > > Hi. I am confused at the following strange FreeBSD reboot case. > I have a Dell PowerEdge 2300 dual proc machine with Intel 100/10 > netcard. > I put 3.2 SMP kernel with options MAXUSERS=256 and > NMBCLUSTERS=32768. Try some rational numbers. Get that NMBCLUSTERS down to 8192, for instance. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "People call him Neutron Star, 'cuz he's so dense lights bends around him." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 3:54:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 11C0514CBA for ; Sat, 30 Oct 1999 03:54:47 -0700 (PDT) (envelope-from freebsd-hackers@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA92328 for hackers@FreeBSD.org; Sat, 30 Oct 1999 12:36:50 +0200 (CEST) (envelope-from freebsd-hackers@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for hackers@FreeBSD.org (hackers@FreeBSD.org) To: hackers@FreeBSD.org Date: Sat, 30 Oct 1999 12:36:43 +0200 From: Marcel Moolenaar Message-ID: <381ACA3B.F8D71A57@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199910292014.WAA31440@yedi.iaf.nl> Subject: Re: bootpd on Alpha / alignment problems Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Alpha the bootpd does not work, it assert-fails on the > size of the struct bootp being != to BP_MINPKTSZ. > > My best bet is that the Alpha alignment inside the struct results > in a bigger bootp struct. I am, however, not sure on what the right > way is to fix this. Make sure int32 is not defined in terms of long. If it is, then bp_xid is aligned on a 8 byte boundary adding 4 bytes to the size of the struct. Since long if 64-bits on the Alpha, the total increase will be 8. Any alignment at the end of the structure shouldn't cause you troubles. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 7:24:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 397B614E48 for ; Sat, 30 Oct 1999 07:24:30 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id KAA00290; Sat, 30 Oct 1999 10:22:49 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Sat, 30 Oct 1999 10:22:48 -0400 (EDT) From: Chuck Youse To: Oren Sarig Cc: hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-Reply-To: <3.0.6.32.19991029210744.007da290@mail.bezeqint.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Oren Sarig wrote: > actual physical addresses, by using paging tables. Most of the addresses > are mapped outside of the actual memory, and so whenever somebody wants to > access them, a general protection fault occurs. The kernel taps the GPF, > gets the page from the swap, loads it into memory, remaps the linear > address, and gives the program back the control, but now the program has > the data in memory. IA32 supports up to 4Gb of physical memory with > protected mode, and a whole lot more virtual memory than that with paging. Well, just a minor technicality: when a non-present page is referenced, a page fault is generated, not a general protection fault. GPFs are the catch-all fault that is primarily used to flag security violations. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 8:31:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id 4FEAA1507D for ; Sat, 30 Oct 1999 08:19:29 -0700 (PDT) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id KAA02421 for ; Sun, 24 Oct 1999 10:30:41 +0200 Received: (qmail 14076 invoked from network); 24 Oct 1999 08:30:30 -0000 Received: from piano.innominate.local (192.168.0.213) by lingo01.innominate.local with SMTP; 24 Oct 1999 08:30:30 -0000 Received: from localhost (graichen@localhost) by piano.innominate.local (8.9.3/8.9.3) with ESMTP id KAA05434; Sun, 24 Oct 1999 10:30:30 +0200 (CEST) (envelope-from graichen@innominate.de) X-Authentication-Warning: piano.innominate.local: graichen owned process doing -bs Date: Sun, 24 Oct 1999 10:30:30 +0200 (CEST) From: Thomas Graichen X-Sender: graichen@piano.innominate.local To: freebsd-fs@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org Subject: journaling UFS and LFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is anybody working on adding journaling to the (Free)BSD ufs - or are there any docs in that direction avalibale - any papers or so ? how much harder this is getting due to the complex FreeBSD vm/buffercache and soft updates ? - is anybody intereseted in starting to work on this ? and the next question: now that LFS starts to get usable in NetBSD - has anybody started to look at getting it working again in FreeBSD too (maybe matt ?) or has it on the TODO list for the next months or anything similar ? - anybody with some skills willing to to start working on this ? - just some words about the state in NetBSD (according to my experiments :-): they have it working so far - mostly stable with some minor problems still and also the fsck_lfs is at least able to check the lfs filesystem read only. i think it is a very important point to get this working in FreeBSD due to too long fsck times at bootup getting more and more a killer argument against FreeBSD in serious use with growing filesystem sizes - linux now has somekind of beta quality journaling for ext2 working now btw. t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 9:16: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id DE4951507D; Sat, 30 Oct 1999 09:15:56 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id MAA43646; Sat, 30 Oct 1999 12:17:44 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sat, 30 Oct 1999 12:17:44 -0400 (EDT) From: Don To: Thomas Graichen Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: journaling UFS and LFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > is anybody working on adding journaling to the (Free)BSD ufs - or > are there any docs in that direction avalibale - any papers or > so ? how much harder this is getting due to the complex > FreeBSD vm/buffercache and soft updates ? - is > anybody intereseted in starting to work on > this ? This is exactly the project which was just starting to be discussed on freebsd-fs. There are several people who would love to work on this and as long as the FreeBSD community is going to support. If this project is going to be supported then it will be done. Softupdates is definitely a viable solution however it does not address several issues and the license is not a BSD license so it makes me uncomfortable. > and the next question: now that LFS starts to get usable in NetBSD > - has anybody started to look at getting it working again in > FreeBSD too (maybe matt ?) or has it on the TODO list LFS is being considered as a starting point for this project. The goal is to build an extensible file system with features such as the ability to grow and shrink partitions, acl's journaling etc. XFS is also being considered as a feature reference. > i think it is a very important point to get this working in FreeBSD > due to too long fsck times at bootup getting more and more a > killer argument against FreeBSD in serious use with > growing filesystem sizes Absolutely. >- linux now has somekind > of beta quality journaling for ext2 working now > btw. No comment :) -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 10: 3:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 3C6D214FF7 for ; Sat, 30 Oct 1999 10:03:10 -0700 (PDT) (envelope-from rene@canyon.demon.nl) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11hbuG-000214-00 for freebsd-hackers@freebsd.org; Sat, 30 Oct 1999 17:03:08 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id RAA01051 for freebsd-hackers@freebsd.org; Sat, 30 Oct 1999 17:13:09 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <199910301513.RAA01051@canyon.demon.nl> Subject: Natd+PKT_ALIAS_PUNCH_FW missing something? To: FreeBSD hackers Date: Sat, 30 Oct 1999 17:13:09 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Am I missing something? I modified natd.c so an extra option was available to turn on punch firewall (see diff below). When I activated this option it did not seem to work (ftp-data is still blocked by my firewall). When I add a general allow line for any traffic from 20 to 1023- it (of course) works. But the whole idea was to get rid of this line... Rene -- BEGIN -- *** natd.c.orig Sat Oct 30 17:01:40 1999 --- natd.c Sat Oct 30 17:09:49 1999 *************** *** 852,857 **** --- 852,858 ---- enum Option { PacketAliasOption, + PunchFW, Verbose, InPort, OutPort, *************** *** 955,960 **** --- 956,969 ---- "same_ports", "m" }, + { PunchFW, + PKT_ALIAS_PUNCH_FW, + String, + "basenumber:count", + "punch holes in the firewall for incomming ftp data connections", + "punch_fw", + NULL }, + { Verbose, 0, YesNo, *************** *** 1168,1173 **** --- 1177,1189 ---- aliasValue = yesNoValue ? info->packetAliasOpt : 0; PacketAliasSetMode (aliasValue, info->packetAliasOpt); + break; + + case PunchFW: + if (sscanf(strValue, "%u:%u", &basefw, &count) != 2) + errx(1, "%s needs basefw:count", info->name); + PacketAliasSetFWBase(basefw, count); + PacketAliasSetMode(PKT_ALIAS_PUNCH_FW, PKT_ALIAS_PUNCH_FW); break; case Verbose: -- END -- -- Rene de Vries http://www.tcja.nl/~rene; mailto:rene@tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 15:32:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 0A69B15195 for ; Sat, 30 Oct 1999 15:32:35 -0700 (PDT) (envelope-from borjam@we.lc.ehu.es) Received: from sirius.we.lc.ehu.es (sirius [158.227.6.30]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA21306 for ; Sun, 31 Oct 1999 00:32:33 +0200 (MET DST) From: Borja Marcos Received: (from borjam@localhost) by sirius.we.lc.ehu.es (8.9.1/8.9.1) id AAA16912 for hackers@freebsd.org; Sun, 31 Oct 1999 00:32:32 +0200 (MET DST) Message-Id: <199910302232.AAA16912@sirius.we.lc.ehu.es> Subject: exec() security enhancement To: hackers@freebsd.org Date: Sun, 31 Oct 1999 00:32:32 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Many security exploits create files in the /tmp directory and execute them. I think it would be a good idea to add logging to the to exec_check_permissions() in kern.exec.c so that attempts to run files from a filesystem mounted as "noexec" can be detected. With this measeure, and mounting /tmp as "noexec" some generic hostile acts (wow, how does it sound! :-) ) could be detected. Regards, Borja. -- *********************************************************************** Borja Marcos * Internet: borjam@we.lc.ehu.es Alangoeta, 11 1 izq * borjamar@sarenet.es 48990 - Algorta (Vizcaya) * borjam@well.com SPAIN * CompuServe: 100015,3502 *********************************************************************** --- FreeBSD, turning PCs into workstations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 15:45:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id D644F14D7D for ; Sat, 30 Oct 1999 15:45:09 -0700 (PDT) (envelope-from usenet@erix.ericsson.se) Received: from super.du.uab.ericsson.se (root@super.du.uab.ericsson.se [134.138.176.16]) by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id AAA12032 for ; Sun, 31 Oct 1999 00:45:07 +0200 (MET DST) Received: from news.du.uab.ericsson.se (news [134.138.176.24]) by super.du.uab.ericsson.se (8.9.3/8.9.3/erix-1.7) with ESMTP id AAA08862 for ; Sun, 31 Oct 1999 00:45:06 +0200 (MET DST) Received: (from news@localhost) by news.du.uab.ericsson.se (8.9.1b+Sun/8.9.1/news-1.1) id AAA20873 for freebsd-hackers@freebsd.org; Sun, 31 Oct 1999 00:45:05 +0200 (MET DST) Received: from GATEWAY by news with netnews for freebsd-hackers@freebsd.org (freebsd-hackers@freebsd.org) To: freebsd-hackers@freebsd.org Date: 31 Oct 1999 00:26:11 +0200 From: Kent Boortz Message-ID: Organization: Ericsson Telecom AB, Stockholm, Sweden Content-Type: text/plain; charset=us-ascii Subject: semaphores/semget problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to port the Linux sound program GramoFile but failed. The source was found at http://cardit.et.tudelft.nl/~card06/ It was easy to make it compile and link, mostly changing to , and -lcurses to -lncurses. But creating the System V semaphores fails when trying to play some sound. A call to semget(IPC_PRIVATE, SEMMSL, IPC_EXCL | IPC_CREAT | 0600)) fails with the error "No space left on device". I tried to use a smaller value for SEMMSL but it did not help. Any hints about what can be the cause of this problem? I have set options SYSVSHM # System V Interface options SYSVMSG options SYSVSEM in the kernel config and I run FreeBSD 3.3-STABLE #0: Sun Oct 10 00:45:08 CEST 1999 kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 15:46:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id AFA40151AE for ; Sat, 30 Oct 1999 15:46:27 -0700 (PDT) (envelope-from borjam@we.lc.ehu.es) Received: from sirius.we.lc.ehu.es (sirius [158.227.6.30]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA21324 for ; Sun, 31 Oct 1999 00:46:25 +0200 (MET DST) From: Borja Marcos Received: (from borjam@localhost) by sirius.we.lc.ehu.es (8.9.1/8.9.1) id AAA17006 for hackers@freebsd.org; Sun, 31 Oct 1999 00:46:24 +0200 (MET DST) Message-Id: <199910302246.AAA17006@sirius.we.lc.ehu.es> Subject: Re: exec() security enhancement To: hackers@freebsd.org Date: Sun, 31 Oct 1999 00:46:24 +0200 (MET DST) In-Reply-To: <199910302232.AAA16912@sirius.we.lc.ehu.es> from "Borja Marcos" at Oct 31, 99 00:32:32 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I forgot, the same could be applied to filesystems mounted as "nosuid". Borja. -- *********************************************************************** Borja Marcos * Internet: borjam@we.lc.ehu.es Alangoeta, 11 1 izq * borjamar@sarenet.es 48990 - Algorta (Vizcaya) * borjam@well.com SPAIN * CompuServe: 100015,3502 *********************************************************************** --- FreeBSD, turning PCs into workstations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 18: 3:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 892EF14C10 for ; Sat, 30 Oct 1999 18:03:21 -0700 (PDT) (envelope-from borjam@we.lc.ehu.es) Received: from sirius.we.lc.ehu.es (sirius [158.227.6.30]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id CAA21479 for ; Sun, 31 Oct 1999 02:03:19 +0100 (MET) From: Borja Marcos Received: (from borjam@localhost) by sirius.we.lc.ehu.es (8.9.1/8.9.1) id CAA17338 for hackers@freebsd.org; Sun, 31 Oct 1999 02:03:18 +0100 (MET) Message-Id: <199910310103.CAA17338@sirius.we.lc.ehu.es> Subject: Obtaining the filename for a vnode To: hackers@freebsd.org Date: Sun, 31 Oct 1999 02:03:18 +0100 (MET) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm modifying execve() so that it will log attempts to execute a program from a filesystem mounted as noexec. I think it is interesting to log the UID, the filename of the program which called execve() and the program it tried to executed. I see (kern_exec.c) I have the vnode of the process text, but, how can I obtain the filename for the vnode? Is there a routine in the kernel to do that? Thanks, Borja. -- *********************************************************************** Borja Marcos * Internet: borjam@we.lc.ehu.es Alangoeta, 11 1 izq * borjamar@sarenet.es 48990 - Algorta (Vizcaya) * borjam@well.com SPAIN * CompuServe: 100015,3502 *********************************************************************** --- FreeBSD, turning PCs into workstations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 30 20:20:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id A57E814CC2 for ; Sat, 30 Oct 1999 20:20:49 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id XAA00592; Sat, 30 Oct 1999 23:19:06 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Sat, 30 Oct 1999 23:19:06 -0400 (EDT) From: Chuck Youse To: Borja Marcos Cc: hackers@FreeBSD.ORG Subject: Re: Obtaining the filename for a vnode In-Reply-To: <199910310103.CAA17338@sirius.we.lc.ehu.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Borja Marcos wrote: > I see (kern_exec.c) I have the vnode of the process > text, but, how can I obtain the filename for the vnode? Is there a > routine in the kernel to do that? Careful here: the UNIX filesystem separates vnodes from directory entries. One can easily map a name in the filesystem to a v-node (via namei() et al.) but was never designed to work the other way around. Unlike most other operating systems (Windows NT, VMS, etc.) there is no one-to-one correspondence between a file on disk and its associated names in the filesystem. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message