From owner-freebsd-hackers Sun Aug 20 5: 0:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.nildram.co.uk (mercury.nildram.co.uk [195.112.4.37]) by hub.freebsd.org (Postfix) with ESMTP id 11DE837B422 for ; Sun, 20 Aug 2000 05:00:12 -0700 (PDT) Received: from nermal.unix-consult.com (tgeusch.dial.nildram.co.uk [195.149.29.39]) by mercury.nildram.co.uk (8.10.0/8.10.0.Beta10) with ESMTP id e7KB8Ra26885 for ; Sun, 20 Aug 2000 12:08:28 +0100 Received: (qmail 480 invoked by uid 1002); 20 Aug 2000 11:53:25 -0000 Date: Sun, 20 Aug 2000 12:53:24 +0100 From: Timo Geusch To: hackers@freebsd.org Subject: USR I-modem problems on 4.1-stable and 5.0-current Message-ID: <20000820125324.A443@nermal.unix-consult.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="LZvS9be/3tNcYl/X" X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii All, I've written to the list earlier about this but was not able to provide all the info needed thanks to the usual lack of time. So here we go again: I've got two different systems, one running 5.0, the other 4.1-stable as of yesterday evening UK time. All info, i.e. dmesg etc are provided by the latter system but the output and the results are the same. On both systems, this ISDN modem card (which supposedly masks as a PnP serial port) is recognized and PnP configured by the BIOS. It also shows up on the dmesg but is listed as 'unknown'. As it will only ever be configured as one of the standard serial ports, I added it to my config so it would be probed. The result is ALWAYS the error message 'configured irq x is not in bitmap of probed irqs' - see attached dmesg. As this card is a PnP card and gets recognized as such, I also added the PnP id to the list of PnP ids in sio.c, recompiled the whole kernel (make clean depend all) but it still does not get picked up. It shows up as 'unknown' instead. Please find attached the dmesg of the system, pnpinfo output (the ISDN modem is currently the only PnP card in this system) and the entry I put into the sio pnp table. For reference I appended the whole pnp id table from sio.c; please search for '>>>' to find the entry I added. Any help re what i am missing here greatly appreciated - my soon to be ex-employer want their ISDN router back so I'd like to get this card going as the alternative is too ugly to mention (i.e. a 33.6 modem) TIA, Timo --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="pnpinfo.out" Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID USR0410 (0x10047256), Serial Number 0x3642324e PnP Version 1.0, Vendor Version 0 Device Description: USRobotics Courier I-Modem with ISDN/V.34 Logical Device ID: USR0000 0x00007256 #0 TAG Start DF Good Configuration FIXED I/O base address 0x2f8 length 0x8 IRQ: 3 - only one type (true/edge) TAG Start DF Acceptable Configuration FIXED I/O base address 0x3f8 length 0x8 IRQ: 4 - only one type (true/edge) TAG Start DF Acceptable Configuration FIXED I/O base address 0x3e8 length 0x8 IRQ: 4 - only one type (true/edge) TAG Start DF Acceptable Configuration FIXED I/O base address 0x2e8 length 0x8 IRQ: 3 - only one type (true/edge) TAG Start DF Sub-optimal Configuration FIXED I/O base address 0x3e8 length 0x8 IRQ: 3 5 7 - only one type (true/edge) TAG Start DF Sub-optimal Configuration FIXED I/O base address 0x2e8 length 0x8 IRQ: 4 5 7 - only one type (true/edge) TAG End DF End Tag Successfully got 22 resources, 1 logical fdevs -- card select # 0x0001 CSN USR0410 (0x10047256), Serial Number 0x3642324e Logical device #0 IO: 0x02f8 0x02f8 0x02f8 0x02f8 0x02f8 0x02f8 0x02f8 0x02f8 IRQ 3 0 DMA 4 4 IO range check 0x00 activate 0x01 --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sio.c" static struct isa_pnp_id sio_ids[] = { {0x0005d041, "Standard PC COM port"}, /* PNP0500 */ {0x0105d041, "16550A-compatible COM port"}, /* PNP0501 */ {0x0205d041, "Multiport serial device (non-intelligent 16550)"}, /* PNP0502 */ {0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */ {0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */ /* Devices that do not have a compatid */ {0x12206804, NULL}, /* ACH2012 - 5634BTS 56K Video Ready Modem */ {0x7602a904, NULL}, /* AEI0276 - 56K v.90 Fax Modem (LKT) */ {0x00007905, NULL}, /* AKY0000 - 56K Plug&Play Modem */ {0x01405407, NULL}, /* AZT4001 - AZT3000 PnP SOUND DEVICE, MODEM */ {0x56039008, NULL}, /* BDP0356 - Best Data 56x2 */ {0x36339008, NULL}, /* BDP3336 - Best Data Prods. 336F */ {0x0014490a, NULL}, /* BRI1400 - Boca 33.6 PnP */ {0x0015490a, NULL}, /* BRI1500 - Internal Fax Data */ {0x0034490a, NULL}, /* BRI3400 - Internal ACF Modem */ {0x00b4490a, NULL}, /* BRIB400 - Boca 56k PnP */ {0x0030320d, NULL}, /* CIR3000 - Cirrus Logic V43 */ {0x0100440e, NULL}, /* CRD0001 - Cardinal MVP288IV ? */ {0x36033610, NULL}, /* DAV0336 - DAVICOM 336PNP MODEM */ {0x0000aa1a, NULL}, /* FUJ0000 - FUJITSU Modem 33600 PNP/I2 */ {0x1200c31e, NULL}, /* GVC0012 - VF1128HV-R9 (win modem?) */ {0x0303c31e, NULL}, /* GVC0303 - MaxTech 33.6 PnP D/F/V */ {0x0505c31e, NULL}, /* GVC0505 - GVC 56k Faxmodem */ {0x0050c31e, NULL}, /* GVC5000 - some GVC modem */ {0x3800f91e, NULL}, /* GWY0038 - Telepath with v.90 */ {0x9062f91e, NULL}, /* GWY6290 - Telepath with x2 Technology */ {0x0000f435, NULL}, /* MOT0000 - Motorola ModemSURFR 33.6 Intern */ {0x5015f435, NULL}, /* MOT1550 - Motorola ModemSURFR 56K Modem */ {0xf015f435, NULL}, /* MOT15F0 - Motorola VoiceSURFR 56K Modem */ {0x6045f435, NULL}, /* MOT4560 - Motorola ? */ {0x61e7a338, NULL}, /* NECE761 - 33.6Modem */ {0x0f804f3f, NULL}, /* OZO800f - Zoom 2812 (56k Modem) */ {0x39804f3f, NULL}, /* OZO8039 - Zoom 56k flex */ {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ {0x1000eb49, NULL}, /* ROK0010 - Rockwell ? */ {0x5002734a, NULL}, /* RSS0250 - 5614Jx3(G) Internal Modem */ {0x6202734a, NULL}, /* RSS0262 - 5614Jx3[G] V90+K56Flex Modem */ {0xc100ad4d, NULL}, /* SMM00C1 - Leopard 56k PnP */ {0x9012b04e, NULL}, /* SUP1290 - Supra ? */ {0x1013b04e, NULL}, /* SUP1310 - SupraExpress 336i PnP */ {0x8013b04e, NULL}, /* SUP1380 - SupraExpress 288i PnP Voice */ {0x8113b04e, NULL}, /* SUP1381 - SupraExpress 336i PnP Voice */ {0x5016b04e, NULL}, /* SUP1650 - Supra 336i Sp Intl */ {0x7016b04e, NULL}, /* SUP1670 - Supra 336i V+ Intl */ {0x7420b04e, NULL}, /* SUP2070 - Supra ? */ {0x8020b04e, NULL}, /* SUP2080 - Supra ? */ {0x8420b04e, NULL}, /* SUP2084 - SupraExpress 56i PnP */ {0x7121b04e, NULL}, /* SUP2171 - SupraExpress 56i Sp? */ {0x8024b04e, NULL}, /* SUP2480 - Supra ? */ {0x01007256, NULL}, /* USR0001 - U.S. Robotics Inc., Sportster W */ {0x02007256, NULL}, /* USR0002 - U.S. Robotics Inc. Sportster 33. */ {0x04007256, NULL}, /* USR0004 - USR Sportster 14.4k */ {0x06007256, NULL}, /* USR0006 - USR Sportster 33.6k */ {0x11007256, NULL}, /* USR0011 - USR ? */ {0x01017256, NULL}, /* USR0101 - USR ? */ >>> This entry was added {0x10047256, NULL}, /* USR0410 - USR I-modem */ <<< {0x30207256, NULL}, /* USR2030 - U.S.Robotics Inc. Sportster 560 */ {0x50207256, NULL}, /* USR2050 - U.S.Robotics Inc. Sportster 33. */ {0x70207256, NULL}, /* USR2070 - U.S.Robotics Inc. Sportster 560 */ {0x30307256, NULL}, /* USR3030 - U.S. Robotics 56K FAX INT */ {0x31307256, NULL}, /* USR3031 - U.S. Robotics 56K FAX INT */ {0x50307256, NULL}, /* USR3050 - U.S. Robotics 56K FAX INT */ {0x70307256, NULL}, /* USR3070 - U.S. Robotics 56K Voice INT */ {0x90307256, NULL}, /* USR3090 - USR ? */ {0x70917256, NULL}, /* USR9170 - U.S. Robotics 56K FAX INT */ {0x90917256, NULL}, /* USR9190 - USR 56k Voice INT */ {0x0300695c, NULL}, /* WCI0003 - Fax/Voice/Modem/Speakphone/Asvd */ {0x61f7896a, NULL}, /* ZTIF761 - Zoom ComStar 33.6 */ {0} }; --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.out" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-STABLE #1: Sun Aug 20 09:11:56 BST 2000 root@nermal.unix-consult.com:/usr/src/sys/compile/NERMAL.SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (232.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 268435456 (262144K bytes) avail memory = 258490368 (252432K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 10 IOAPIC #0 intpin 18 -> irq 12 IOAPIC #0 intpin 19 -> irq 11 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02de000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 11 pci0: at 11.0 irq 11 sym0: <875> port 0x9400-0x94ff mem 0xe2100000-0xe2100fff,0xe2102000-0xe21020ff irq 12 at device 12.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. fxp0: port 0x9800-0x981f mem 0xe2000000-0xe20fffff,0xe2101000-0xe2101fff irq 10 at device 14.0 on pci0 fxp0: Ethernet address 00:08:c7:8c:40:03 isa0: too many memory ranges fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: parallel port not found. unknown0: at port 0x2f8-0x2ff irq 3 on isa0 unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown2: at port 0x40-0x43 irq 0 on isa0 unknown3: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown4: at port 0x61 on isa0 unknown5: at port 0xf0-0xff irq 13 on isa0 unknown6: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xcc800-0xcffff,0-0x9ffff,0xfffe0000-0xffffffff,0xfec00000-0xfec0ffff,0xfee00000-0xfee0ffff on isa0 unknown7: at port 0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f on isa0 unknown8: at port 0x208-0x20f on isa0 unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! acd0: CDROM at ata1-master using PIO4 Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2006MB (4110000 512 byte sectors: 255H 63S/T 255C) Mounting root from ufs:/dev/da0s1a da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15) da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) vinum: loaded vinum: reading configuration from /dev/da2s1e vinum: updating configuration from /dev/da1s1e vinum: updating configuration from /dev/da0s1h --LZvS9be/3tNcYl/X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 21 3: 7:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id E87C237B424; Mon, 21 Aug 2000 03:07:22 -0700 (PDT) Received: by snafu.adept.org (Postfix, from userid 1000) id 960C79EE01; Mon, 21 Aug 2000 03:07:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 9114C9B001; Mon, 21 Aug 2000 03:07:21 -0700 (PDT) Date: Mon, 21 Aug 2000 03:07:21 -0700 (PDT) From: Mike Hoskins To: Mike Smith Cc: Josh Paetzel , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Installation Problems on Dell PowerEdge 6100/200 In-Reply-To: <200008090315.UAA15544@mass.osd.bsdi.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, 8 Aug 2000, Mike Smith wrote: > > If it is worth anything, I tried installing on a poweredge 2450 once and to > > make a long story short couldn't get the onboard RAID to work or the SMP to > > work. I hear it got sent back for something else (that wasn't a dell!) > > Onboard RAID will be working shortly (waiting for someome to lend me > hardware), SMP works as of 4.1-RELEASE. I'm psyched. I just finished an order for a dual p3/866 2450 with 1GB RAM and 4x36GB (Perc 2/DC). Thanks to amr, the West Coast is getting another cvsup server (at least, that's my plan ;). -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 21 9:37:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 5926637B424; Mon, 21 Aug 2000 09:37:06 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.9.3/1.13) id TAA15453; Mon, 21 Aug 2000 19:37:03 +0300 (EEST) Date: Mon, 21 Aug 2000 19:37:03 +0300 From: Ruslan Ermilov To: Kazukata Yokota Cc: hackers@FreeBSD.org Subject: [PATCH] 3-button microsoft-type serial mouse Message-ID: <20000821193703.A15158@sunbay.com> Mail-Followup-To: Kazukata Yokota , hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="8t9RHnE3ZwKMSgU+" X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Hi! I have a 3-button microsoft-type serial mouse (I do not know the vendor, only FCC ID if needed) which generates the `middle button down' event as previous `button down/up' event (any). Attached are: 1. the script(1) output of unmodified moused(8) with comments on events. 2. the patch that makes my mouse's 3rd button work. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="moused.script" Script started on Mon Aug 21 18:55:26 2000 perl# moused -d -f -p /dev/cuaa1 moused: PnP COM device rev 1.0 probe... moused: modem status 03 moused: alternate probe... moused: pnpwakeup2(): valid response. moused: M 4d moused: non-PnP mouse 'M' moused: PnP serial mouse: 'PNP0F01' '' '' moused: proto params: 40 40 40 00 3 dc 00 moused: port: /dev/cuaa1 interface: serial type: microsoft model: generic Left button pressed: moused: received char 0x60 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 60,0,0,0,0,0,0,0 moused: tv: 966873379 603859 moused: : 966873377 3320 moused: flags:00000001 buttons:00000001 obuttons:00000000 moused: activity : buttons 0x00000001 dx 0 dy 0 dz 0 moused: mstate[0]->count:1 moused: button 1 count 1 Left button released: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 moused: tv: 966873380 693550 moused: flags:00000001 buttons:00000000 obuttons:00000001 moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 moused: mstate[0]->count:1 moused: button 1 count 0 Right button pressed: moused: received char 0x50 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 50,0,0,0,0,0,0,0 moused: tv: 966873382 523875 moused: : 966873377 3320 moused: flags:00000004 buttons:00000004 obuttons:00000000 moused: activity : buttons 0x00000004 dx 0 dy 0 dz 0 moused: mstate[2]->count:1 moused: button 3 count 1 Right button released: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 moused: tv: 966873383 493579 moused: flags:00000004 buttons:00000000 obuttons:00000004 moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 moused: mstate[2]->count:1 moused: button 3 count 0 Middle button pressed: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 Middle button released: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 perl# exit Script done on Mon Aug 21 18:56:28 2000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="moused.c.patch" Index: moused.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/moused/moused.c,v retrieving revision 1.45 diff -u -p -r1.45 moused.c --- moused.c 2000/04/21 14:20:25 1.45 +++ moused.c 2000/08/21 16:09:44 @@ -1660,8 +1660,7 @@ r_protocol(u_char rBuf, mousestatus_t *a ? MOUSE_BUTTON2DOWN : butmapmss[(pBuf[0] & MOUSE_MSS_BUTTONS) >> 4]; else - act->button |= (act->obutton & MOUSE_BUTTON2DOWN) - | butmapmss[(pBuf[0] & MOUSE_MSS_BUTTONS) >> 4]; + act->button |= butmapmss[(pBuf[0] & MOUSE_MSS_BUTTONS) >> 4]; /* Send X10 btn events to remote client (ensure -128-+127 range) */ if ((rodent.rtype == MOUSE_PROTO_X10MOUSEREM) && @@ -1676,6 +1675,10 @@ r_protocol(u_char rBuf, mousestatus_t *a act->dx = (char)(((pBuf[0] & 0x03) << 6) | (pBuf[1] & 0x3F)); act->dy = (char)(((pBuf[0] & 0x0C) << 4) | (pBuf[2] & 0x3F)); + + if (act->button == act->obutton && !act->dx && !act->dy) + act->button |= MOUSE_BUTTON2DOWN; + break; case MOUSE_PROTO_GLIDEPOINT: /* GlidePoint */ --8t9RHnE3ZwKMSgU+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 21 14:25:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id C062937B423; Mon, 21 Aug 2000 14:25:15 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA14744; Mon, 21 Aug 2000 14:38:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008212138.OAA14744@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Cc: hardware@freebsd.org Subject: Updated driver for Mylex 160/170/352/2000/3000 controllers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Aug 2000 14:38:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The next BETA version of the 'mly' driver for Mylex's current family of PCI SCSI RAID controllers is now available from http://people.freebsd.org/~msmith/RAID/index.html#mylex. The major change in this version is the addition of status monitoring; the driver is now aware of the array status and will report drive status at attach time in the SCSI INQUIRY data, as well as logging status events. I don't have a 4.x system to test on at this stage, so I'm not trying to make the driver work on 4.x. Having said that, the issues involved in fixing it for 4.x are probably small, and if an interested user can provide me with a little assistance, I'm sure I can sort it out. Thanks as usual to Mylex for the hardware and data, and BSDi for funding this work. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 21 14:37:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc27.worldnet.att.net (mtiwmhc27.worldnet.att.net [204.127.131.52]) by hub.freebsd.org (Postfix) with ESMTP id E66BA37B506 for ; Mon, 21 Aug 2000 14:36:06 -0700 (PDT) Received: from default ([12.77.203.143]) by mtiwmhc27.worldnet.att.net (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20000821213537.JDJN14052.mtiwmhc27.worldnet.att.net@default> for ; Mon, 21 Aug 2000 21:35:37 +0000 From: hspio@worldnet.att.net To: hackers@FreeBSD.ORG Date: Mon, 21 Aug 2000 17:28:29 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: UNSUBSCRIBE Message-ID: <39A166BD.9240.3C492FD@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Aug 2000, at 2:58, freebsd-hackers-digest wrote: > > freebsd-hackers-digest Saturday, August 19 2000 Volume 04 : Number= 925 > > > > In this issue: > Re: Critical (or equivalent) section in Userland? > Re: Critical (or equivalent) section in Userland? > Re: 'group' in ioctl() > RE: Bootable CD... > Re: Critical (or equivalent) section in Userland? > Loading font with libvgl > Date: Fri, 18 Aug 2000 14:18:38 +0200 > Fellow Writer > Re: Fellow Writer > Re: Anyone try the new dual-head G-400 drivers? > Re: Anyone try the new dual-head G-400 drivers? > Re: Fellow Writer > Re: RE: what to do about /tmp > Re: Bootable CD... > Re: Mosix in FreeBSD. > Re: Mosix in FreeBSD. > Re: Bootable CD... > Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > 64bit Ethernet Controllers > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > RE: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: Critical (or equivalent) section in Userland? > Re: Cheap 1000Gbyte machine > Re: Critical (or equivalent) section in Userland? > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: Cheap 1000Gbyte machine > Re: 64bit Ethernet Controllers > Re: Bootable CD... > IEEE1394 driver system for -current > > ---------------------------------------------------------------------- > > Date: Fri, 18 Aug 2000 07:49:32 +0100 > From: Karl Pielorz > Subject: Re: Critical (or equivalent) section in Userland? > > Warner Losh wrote: > > > Kill sendmail's root process. That's the best you can do. It won't > > impact anything, it will prevent the reading of the queue files (and > > the config files) and the children will just run with the old copies. > > then you wait for all the children to die (with a reasonable > > timeout). Then you do your change, then restart sendmail. That's the > > best you can hope for. > > Unforuntately this doesn't work, as sendmails numerous children live for= too > long (the machine is a busy MX, and people increasingly mail 5Mb+ files > around) > > Also adding to the children's lives is the fact that sendmail uses cache= d > connections to delivery multiple messages to the same destination MX, wh= ich > leads to even longer 'death' times, and can also result in Sendmail's ki= ds > looking up domains etc. in the config files :( [At least, that's what ap= pears > to be happening after a lot of observation]... > > However, 'killall -SIGSTOP sendmail' - appears to work very nicely... Wi= th a > 'killall -SIGCONT sendmail' putting things back to normal. I'm also doin= g the > stop twice for good measure incase anything was forking at the time. > > I guess only time will tell, but the signal idea seems the best so far, > considering the other restrictions :) > > Regards, > > Karl > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 00:51:53 -0600 > From: Warner Losh > Subject: Re: Critical (or equivalent) section in Userland? > > In message <399CDC7C.F68E634@tdx.co.uk> Karl Pielorz writes: > : However, 'killall -SIGSTOP sendmail' - appears to work very nicely... = With a > : 'killall -SIGCONT sendmail' putting things back to normal. I'm also do= ing the > : stop twice for good measure incase anything was forking at the time. > > No need to stop twice. > > : I guess only time will tell, but the signal idea seems the best so far= , > : considering the other restrictions :) > > Well, you still have the same problem as before, you've just made it > harder to exploit. Namely, if sendmail fires up and reads one of the > set of files, then you stop it, and start it again and reads the rest > it is little different than the problem you had before. > > I would suspect it is much less likely to happen, however. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 00:53:59 -0600 > From: Warner Losh > Subject: Re: 'group' in ioctl() > > In message <20000818142650A.fujita@soum.co.jp> FUJITA Kazutoshi writes: > : What 'group' should I use ? > > Pick one, it will not likely matter. Traditionally, certain groups > have been reserved for the TTY layer, but unless you are trying to > coexist with these sorts of interfaces, it really doesn't matter much. > > I would avoid the 'f' group, however, because those IOCTLs need to > work on all file descriptors and you wouldn't want a collision. > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 09:58:09 +0200 (SAST) > From: Johan Kruger > Subject: RE: Bootable CD... > > Might be that you need to disklabel the image of the filesystem on > which you copy this files, ( not talking about the mfs filesystem that > is crunced into the kernel ) > So, try the following. > Mount this image by doing 'vnconfig /dev/vn0 /pathtobootimage/myimage.im= g' > where myimgae.img is the 2.88 M boot image. > Now do a 'mount /dev/vn0 /mnt' > now do a 'disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > Something like above, try and see if it works. > If it doesn't create a new filesystem, do newfs and disklabel, then copy= all > those files of yours onto the filesystem. > You actually don't need all those files. > Anyways, i think it's the bootloader itself thats not loading the kernel= on the > CD ( inside the 2.88 M) image. And to correct that you need to reinstall= the > bootloader, and the bootblocks. > That is boot0 to boot2 > > > On 17-Aug-00 Patrick Bihan-Faou wrote: > > Hi, > > > > > > I am trying to build a bootable CD... Now this sounds like something t= rivial > > enough to do when you know what you are doing. In my case I must admit= that > > I am somewhat confused. > > > > Until now, I think that the trick was to make the CD look like a flopp= y and > > boot it as such. I have created some bootable CDs in the past and they > > seemed to work OK. > > > > However it looks like things have changed recently in the way CD-Roms = are > > booted, and I am not able to create a working CD anymore. > > > > What I would like to clarify is what needs to be in the "2.88 M" boota= ble > > image ? > > > > Here is what I have: > > > > /boot > > /boot0 > > /boot1 > > /boot2 > > /loader > > /cdboot > > /pxeboot > > /loader.config > > /loader.rc > > /boot.config > > /kernel.config > > /kernel.gz > > /modules > > ... > > /usr/sbin > > ibcs2 > > linux > > svr4 > > > > > > Now whenever I boot this image, the loader dies displaying a all whack= hex > > values and saying "BTX Halted". > > > > > > I am a bit confused as to what to do next, and I would really apprecia= te any > > help. > > > > BTW I am working on a fresh copy of FreeBSD 4.1-STABLE (checked-out Au= gust > > 15). > > > > > > Patrick. > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > - ---------------------------------- > E-Mail: Johan Kruger > Date: 18-Aug-00 > Time: 09:49:10 > > This message was sent by XFMail > - ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 07:52:17 +0000 > From: Tony Finch > Subject: Re: Critical (or equivalent) section in Userland? > > Karl Pielorz wrote: > > > >I don't think advisory locks will work - the other process is sendmail.= .. I > >have to keep it from opening any of it's config files, whilst I 'rename= ' out > >of place the old ones (keeping any fd's to them intact) and rename in t= he new > >ones... > > Why not append a serial number to the end of the filenames of the > subsidiary configuration files, and modify sendmail.cf accordingly? > Then the update procedure could be: > (1) write all the new files as $filename.`date +%Y%d%m%H%M%S` > (2) mv sendmail.cf.date sendmail.cf (or use `ln -sf` if you want to > keep old files) > (3) every day or so delete configuration files that are older than > your maximum queue run time. > > This gives you atomic configuration updates. > > You don't need to rename the old sendmail.cf to another because > existing fds will remain attached to the old file which isn't being > altered, just unlinked. > > Tony. > - -- > en oeccget g mtcaa f.a.n.finch > v spdlkishrhtewe y dot@dotat.at > eatp o v eiti i d. fanf@covalent.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 10:43:24 +0200 (SAST) > From: Johan Kruger > Subject: Loading font with libvgl > > Hmm, a few days back on the mailing list i saw there was > problem with specifying a different font when using libvgl. > Allthough this is not critical to my application, it would > shurely enhance the look and feel of my app. > > So i am wondering ... is somebody working on this ? > And nope , i cant work on it right now. *;-) > > Just curios > - ---------------------------------- > Unix Software Developer/Engineer > E-Mail: Johan Kruger > Date: 18-Aug-00 > Time: 10:37:54 > > This message was sent by XFMail > - ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 14:18:38 +0200 > From: rudy.gheysens@gemeenschapsonderwijs.be > Subject: Date: Fri, 18 Aug 2000 14:18:38 +0200 > > Dear Sir, > Madam, > > For the thirteenth time already our association is organi-zing a cartoon > contest. Firstly, we would like to thank all parti-cipants of the 1999 > contest. The large number of entries proves their confidence in our > orga-nisation and this is a real incen-tive for us to do even better in > 2001. > We hope we can count on your collaboration and wish you a lot of success= ! > > > The President > Rudy Gheysens > ________________________________________ > RULES > > 1. Theme: " THE SUPERMARKET ". > > 2. The number of entries is limited until 5. > They shall not have been exhibited or publis-hed before. > > 3. The works have to be sent to the following address: > > EURO-KARTOENALE > WAREGEMSESTEENWEG 113 > B- 9770 KRUISHOUTEM - BELGIUM > > 4. The drawings shall have the following dimen-sions: 210 x 297 mm. The > works shall not be provided by a passe-partout, neit-her be stuck on to = a > larger paper. > The drawing must bear, on the reverse side, the surna-me, christian > name and address of the participant. The drawings shall not bear subtitl= es. > > 5. By virtue of their participation, the partici-pants > autho-rize the organizers to publish some of their works that they have > received. > > 6. The following prizes are foreseen: > > 1.GOLDEN EGG 50.000 BEF (1.239,46 euro) > 2.SILVER EGG 30.000 BEF (743,68 euro) > 3.BRONZE EGG 25.000 BEF (619,73 euro) > 4.PRIZE OF THE E.U. 15.000 BEF (371,84 euro) > 5.BEST BELGIUM CARTOON 10.000 BEF (247,89 euro) > > 7. By participating the participant lends his works to the organizers > for exhibitions. > The works received will remain at the dispo-sal of the organizers > du-ring one year (until 01.11.2002). > > 8. The entries will only be sent back by the organizers on receiving a > written request. The awarded works will become the property of the > organi-zers. > > 9. EXTREME DATE OF ENTRY: 15.01.2001 !! > Opening of the exhibition: Friday 15/4/2001 at 8 pm. > _________________________________________ > > DEADLINE 15.01.2001 _______________________________ > Note concerning the catalogue > > In order to receive the free catalogu-e, please attach FIVE (5) coupons = " > international reply " to cover the postage. > These coupons ar available in your local post office. > ______________________________________________ > > E.C.C. - EUROPEAN CARTOON CENTRE > __________________________________________ > > Dear cartoonist > > Kruishoutem has the honnour to open the European cartoon Centre. > > The centre aims at: > * displaying cartoons and caricatures of both national and international > artists > * extending the largest documentation centre regarding cartoons and > caricatures in Europe. This documentation will be the disposal of every > cartoonist in the world > * keeping the available documentation and cartoons at the disposal of > advertising agencies and designers in order to offer the cartoonists a > forum. > > In order to accomplish this mission, the "Euro-kartoenale" will use its > private collection of cartoon books, publications, magazines and origina= l > cartoons to start up the centre. However, this will not suffice. > We also count on the support and cooperation of the cartoonists themselv= es. > This is why we make an urgent appeal to provide us with cartoon books an= d > catalogues (personal work or copies from your private collection), magaz= ines > (please send them regulary), dissertations and other suitable material. > > Much to our regrets we do not have the budget to reimburse you. > > We are looking forward to any support and will keep you informed of the > European Cartoon centre. > > Rudy Gheysens > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 06:27:08 -0700 (PDT) > From: juliangabrielcolado@overtimemail.com > Subject: Fellow Writer > > - --=3D200008180907=3D > Content-Type: text/plain;charset=3DUS-ASCII > > Dear fellow writer: > > I have come across a great new website for writers. They are a > on-demand publisher, and are currently looking for new authors. > They pay the best royalties in the industry, and the people there > are writers like us. If you think you might be interested, email me > and I can send you the link. I already have two titles up with > them, and they have been very helpful. > > PS- if you're not interested, don't reply, and you won't hear from > me again. I'm not a robot, and your name isn't on some list I > bought. I'm just kind of a fanatic for writer's rights, and thought > this might help out some of my fellow writers. > > Good luck with your writing, > Julian Gabriel Colado > > > - --=3D200008180907=3D-- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 23:47:22 +1000 > From: Andrew Kenneth Milton > Subject: Re: Fellow Writer > > +-------[ juliangabrielcolado@overtimemail.com ]---------------------- > | Dear fellow writer: > | > > | They pay the best royalties in the industry, and the people there > | are writers like us. > > The writers there are completely crap? Doesn't sound too good. > > - -- > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Mil= ton > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daem= on > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 10:14:38 -0400 > From: "Jeroen C. van Gelderen" > Subject: Re: Anyone try the new dual-head G-400 drivers? > > "Alexander N. Kabaev" wrote: > > > > This driver will not run on FreeBSD most likely. It seems like the dri= ver needs > > Linux framebuffer device to run. > > Fortunately this doesn't seem to be the case. Works like a charm... > > Cheers, > Jeroen > - -- > Jeroen C. van Gelderen o _ _ _ > jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) > _< \_ _>(_) (_)/<_ \_| \ _|/' \/ > (_)>(_) (_) (_) (_) (_)' _\o_ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 10:19:14 -0400 (EDT) > From: "Alexander N. Kabaev" > Subject: Re: Anyone try the new dual-head G-400 drivers? > > This is the case when I am certainly glad I was mistaken. The sentence f= rom > README about driver working only with framebuffer fooled me. Thanks for > clearing my confusion. > > > On 18-Aug-00 Jeroen C. van Gelderen wrote: > > "Alexander N. Kabaev" wrote: > >> > >> This driver will not run on FreeBSD most likely. It seems like the dr= iver > >> needs > >> Linux framebuffer device to run. > > > > Fortunately this doesn't seem to be the case. Works like a charm... > > > > Cheers, > > Jeroen > > -- > > Jeroen C. van Gelderen o _ _ _ > > jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) > > _< \_ _>(_) (_)/<_ \_| \ _|/' \/ > > (_)>(_) (_) (_) (_) (_)' _\o_ > > - ---------------------------------- > E-Mail: Alexander N. Kabaev > Date: 18-Aug-00 > Time: 10:15:16 > - ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 08:07:02 -0700 > From: Chameleon > Subject: Re: Fellow Writer > > At 11:47 PM 8/18/00 +1000, Andrew Kenneth Milton wrote: > >+-------[ juliangabrielcolado@overtimemail.com ]---------------------- > >| Dear fellow writer: > >| > > > >| They pay the best royalties in the industry, and the people there > >| are writers like us. > > > >The writers there are completely crap? Doesn't sound too good. > > LOL > thats a good one > > >-- > >Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Mi= lton > >The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > >ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Dae= mon > >PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-hackers" in the body of the message > > > - ----------------------------------------------------------------------= ------------------------ > > The human mind ordinarily operates at only ten percent of its capacity > - -- the rest is overhead for the operating system. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 08:47:06 -0700 (PDT) > From: Matt Dillon > Subject: Re: RE: what to do about /tmp > > : > :Matt, > : > :I noticed /tmp and /var/tmp are used slightly differently, for example,= the > :contents of /tmp are not expected to survive a reboot, while /var/tmp i= s > :used for files you might need after a crash, like vi recovery files. > > This may have been true at one time in the past, but these days > /tmp and /var/tmp tend to be used interchangeably. You can't make > those sorts of assumptions. > > :One advantage of mounting /tmp with MFS is that you don't have use up a= nother > :disk partition. Performance-wise, I would think data moves something > :like this: > : > :/tmp on MFS: > : application data --> kernel VM --> paged to disk > : > :/tmp on FFS: > : application data --> kernel file buffer --> flushed to disk > : > :Is that basically correct? What makes MFS less efficient than FFS? > :What would be the implications of creating a 512 MB swap partition > :and mounting an MFS /tmp? > : > :Thanks, > : > :Allen > > There are several problems with MFS: > > * The active data set is cached in memory TWICE rather then just > once. That is, for each page of file data two pages is taken up > of memory. > > * While it is true that MFS will swap unused data, performance under > heavy load will go to pot because MFS does not in any way attempt > to sequence the data to swap. > > MFS may appear fast under light loads, but performance degrades > drastically (to much worse then what you get with FFS) under > heavy memory loads. > > * MFS eats a 'random' amount of swap, up to the size of the MFS > disk. Under medium loads where paging is taking place, the > swap backing store for MFS becomes fragmented and performance > goes to pot. > > There are two solutions: > > * First, you can use vnconfig to create a swap-backed filesystem > and you can reserve the necessary swap wspace contiguously, > resulting in performance which will be as good or better then > a normal FFS filesystem (because your swap space may be striped > across several disks). > > * Second, you can use a normal FFS partition. > > In either case enabling softupdates on the vnconfig or normal > FFS partition should result in good overall peformance without > the load penalty. > > With both solutions it is a good idea to make /var/tmp the partition > and make /tmp a softlink to /var/tmp. > > Using MD instead of MFS is typically not a great choice. While it i= s > true that MD only caches data once, the data is not swap-backed so > what data MD does allocate is allocated permanently. This is useful > in certain system configurations but not useful in the general case. > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 11:48:21 -0400 > From: "Patrick Bihan-Faou" > Subject: Re: Bootable CD... > > Hi, > > > > > Might be that you need to disklabel the image of the filesystem on > > which you copy this files, ( not talking about the mfs filesystem that > > is crunced into the kernel ) > > So, try the following. > > Mount this image by doing 'vnconfig /dev/vn0 /pathtobootimage/myimage.= img' > > where myimgae.img is the 2.88 M boot image. > > Now do a 'mount /dev/vn0 /mnt' > > now do a 'disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > Actually I am using the doFS.sh script from /usr/src/release. The diskla= bel > is done (without the -b and -s options though) by that script. Also I us= ed > to be able to build bootable CDs from the same procedure a few weeks ago > (before the code in /usr/src/sys/boot was updated). > > The CD is recognized as bootable and starts to boot. I can stop the boot= at > the first "spinning bar" (I think that's boot0 or boot1) before the cont= rol > is passed to "loader". > > From there I am sort of stuck: the only thing I can boot is loader which= in > turn crashes immediately. I tried to load "kernel.gz" but its format is = not > recognized at this stage of the boot (probably because it is compressed)= . > > > > BTW I tried you procedure above, and I get: > > su-2.03# vnconfig /dev/vn0 boot.cdrom.img > su-2.03# mount /dev/vn0 /mnt > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > disklabel: /dev/vn0: Device busy > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /mnt > disklabel: /mnt: Is a directory > su-2.03# umount /mnt > su-2.03# disklabel -B -b mindbox/boot/boot1 -s mindbox/boot/boot2 /dev/v= n0 > disklabel: ioctl DIOCWLABEL: Operation not supported by device > su-2.03# > > > > > I'd rather fix the problem with the current version of the boot code, bu= t > time is pressing and I am tempted to revert to the code tagged with the > FreeBSD-4.0 release. Is this something that I should do ? > > > > Patrick. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 09:31:50 -0700 > From: Marco Molteni > Subject: Re: Mosix in FreeBSD. > > On Thu, 17 Aug 2000, Jes=3DFAs Arn=3DE1iz wrote: > > > I have read some information about MOSIX which is some patch for the l= inux > > kernel created to build super-computers from a net of PCs. > >=3D20 > > I want to know if is there some similar project (mosix or even cluster= ing) > > but for FreeBSD, if someone know some about it please let me know. > > Mosix started on BSD/OS, and was then rewritten for Linux. I think the B= SD/=3D > OS > version has died, but you may ask the Mosix people, now that the *BSD ar= e > getting more attention... > > Marco > - --=3D20 > Marco Molteni "rough consensus and running code" > SRI International, System Design Laboratory > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 12:41:54 +0000 > From: Alan Clegg > Subject: Re: Mosix in FreeBSD. > > Out of the ether, Marco Molteni spewed forth the following bitstream: > > > Mosix started on BSD/OS, and was then rewritten for Linux. I think the= BSD/OS > > version has died, but you may ask the Mosix people, now that the *BSD = are > > getting more attention... > > I spoke to the author (one of the authors?) of Mosix at LinuxWorld this > last week, and he was sorry to say that it was *NOT* available on *BSD* > to the public any longer. > > However, the code is still up and running on BSD/OS at the University. > > AlanC > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 18:46:10 +0200 (SAST) > From: Johan Kruger > Subject: Re: Bootable CD... > > Ok, here's what i did ( busy building a custom CD installation ) > After the 'make release' , i took the boot.flp image 2.88 Meg and > mounted it. I deleted everything except for /boot/boot0-2 an the > bootforth loader. Then i made my own kernel allowing a MFS of 2048 x 512 > blocks, giving me 1.44 Meg in the filesystem. > In this i crunched 72 Megs of binary's , one of them 'chroot' > I compiled init as not to look for 'rc' ( check the Makefile, define par= t > that's specifically for a release ) > After this i use the write_mfs_in_kernel script and umount it ( remember= to > compress the kernel after the mfs write > > sh -e doFS.sh -s mfsroot ./ /mnt 2880 johan's_mfsfd_root_dir/ 8000 minim= um2 > ./write_mfs_in_kernel kernel mfsroot > gzip -9vc kernel > kernel.gz > vnconfig /dev/vn0 boot.flp > mount /dev/vn0 /mnt > rm /mnt/kernel.gz > cp kernel.gz /mnt/kernel.gz > umount /mnt > vnconfig -u /dev/vn0 > > Now your boot.flp is ready for mkisofs > > Basically what happens now , i copy my complete live filesystem with > installed apps to the CD's root dir, and when i do mkisofs, i use my new > bootimage. After boot , since it can not find rc, it executes .profile i= n > the MFS filesystem in the kernel- BUT ONLY if you compiled init for the > crunch with in /usr/src/sbin/init/Makefile > > #CFLAGS+=3D-DDEBUGSHELL -DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > CFLAGS+=3D-DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > > In .profile i put 'mount_cd9660 /dev/acd0a /cdrom' ( /cdrom an extra dir= i put > in my filesystem ) and 'chroot /cdrom /setup' , where setup is my prog, = and > this works perfectly , i even load my own modules before the chroot and = so on. > > The release i built is 5.0-CURRRENT , and if you want the boot.flp i can > attach it for you. Just mail me. Right now i'm going home - it's Friday = - at > last > GOOD LUCK > *;-) > > On 18-Aug-00 Patrick Bihan-Faou wrote: > > Hi, > > > > > > Actually I am using the doFS.sh script from /usr/src/release. The disk= label > > is done (without the -b and -s options though) by that script. Also I = used > > to be able to build bootable CDs from the same procedure a few weeks a= go > > (before the code in /usr/src/sys/boot was updated). > > > > The CD is recognized as bootable and starts to boot. I can stop the bo= ot at > > the first "spinning bar" (I think that's boot0 or boot1) before the co= ntrol > > is passed to "loader". > > > >>From there I am sort of stuck: the only thing I can boot is loader whi= ch in > > turn crashes immediately. I tried to load "kernel.gz" but its format i= s not > > recognized at this stage of the boot (probably because it is compresse= d). > > > > > > > > BTW I tried you procedure above, and I get: > > > > su-2.03# vnconfig /dev/vn0 boot.cdrom.img > > su-2.03# mount /dev/vn0 /mnt > > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > disklabel: /dev/vn0: Device busy > > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /mnt > > > > Patrick. > > > > > > - ---------------------------------- > Unix Software Developer/Engineer > E-Mail: Johan Kruger > Date: 18-Aug-00 > Time: 18:28:20 > > All good things come to those who ... runs FreeBSD > - ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 18:16:09 +0100 > From: Jonathan Laventhol > Subject: Cheap 1000Gbyte machine > > Hello Folks -- > > Anybody built a file server with approx 1000 Gbyte or more? > Or even 200 Gbyte? > > I'm looking for a cheap simple way of doing this. Lots of > IDE drives? (How many can you have?) Or SCSI? (Again, > how many can you have?). > > It's for lots of 1 Mbyte files: no huge files. > > Thanks for any tips. > > Regards, > Jonathan. > - -- > ____________________________________________________________________ > Imagination 25 Store Street South Crescent London WC1E 7BL England | > Tel +44 20 7323 3300 Fax +44 20 7323 5801 | > _______________________________________________________| > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 19:20:31 +0200 > From: Wilko Bulte > Subject: Re: Cheap 1000Gbyte machine > > On Fri, Aug 18, 2000 at 06:16:09PM +0100, Jonathan Laventhol wrote: > > > Anybody built a file server with approx 1000 Gbyte or more? > > Done routinely in the commercial world. But cheap.. > > > I'm looking for a cheap simple way of doing this. Lots of > > What is cheap? > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > how many can you have?). > > SCSI, behind RAID array controllers. Connected to the host via SCSI > or Fibrechannel. > > - -- > Wilko Bulte wilko@freebsd.org > Arnhem, the Netherlands > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 13:52:39 -0400 > From: Dennis > Subject: 64bit Ethernet Controllers > > Have any 64bit PCI ethernet controllers been tested in 4.x yet? Preferab= ly > quad port..I've seen a few around (adaptec has one) but no mention on th= e > list of specific experience. > > Dennis > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 19:45:43 +0200 (CEST) > From: Soren Schmidt > Subject: Re: Cheap 1000Gbyte machine > > It seems Jonathan Laventhol wrote: > > Hello Folks -- > > > > Anybody built a file server with approx 1000 Gbyte or more? > > Not yet :) > > > Or even 200 Gbyte? > > Yup, 300G's standing here right next to me... > > > I'm looking for a cheap simple way of doing this. Lots of > > IDE drives? (How many can you have?) Or SCSI? (Again, > > how many can you have?). > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > drives and you should be in business, for a very resonable > pricetag. > > - -S=F8ren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 10:44:21 -0700 (PDT) > From: Matthew Jacob > Subject: Re: Cheap 1000Gbyte machine > > On Fri, 18 Aug 2000, Soren Schmidt wrote: > > > It seems Jonathan Laventhol wrote: > > > Hello Folks -- > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > Not yet :) > > That's not quite true. We had ~900GB on a NetBSD/Alpha machine at NASA/A= mes. > > > > > > Or even 200 Gbyte? > > > > Yup, 300G's standing here right next to me... > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > how many can you have?). > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > drives and you should be in business, for a very resonable > > pricetag. > > > > You know, I used to say ixnay on that, but, Soren, I've been looking at = a lot > of the features of the newer ATA drives, and now that they have bad bloc= k > replacement, I'd have to say that what you're proposing is not unreasona= ble, > although I'd suggest that Vinum/RAID5 be used. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 19:52:42 +0200 (CEST) > From: Soren Schmidt > Subject: Re: Cheap 1000Gbyte machine > > It seems Matthew Jacob wrote: > > On Fri, 18 Aug 2000, Soren Schmidt wrote: > > > > > It seems Jonathan Laventhol wrote: > > > > Hello Folks -- > > > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > > > Not yet :) > > > > That's not quite true. We had ~900GB on a NetBSD/Alpha machine at NASA= /Ames. > > Oh, I mean I havn't build one yet :) > > > > > Or even 200 Gbyte? > > > > > > Yup, 300G's standing here right next to me... > > > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > > how many can you have?). > > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > drives and you should be in business, for a very resonable > > > pricetag. > > > > You know, I used to say ixnay on that, but, Soren, I've been looking a= t a lot > > of the features of the newer ATA drives, and now that they have bad bl= ock > > replacement, I'd have to say that what you're proposing is not unreaso= nable, > > although I'd suggest that Vinum/RAID5 be used. > > Nice to hear, and yes vinum is the way to go for redundancy, who is > going to backup THAT amount of data, and on what :) > > - -S=F8ren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 13:53:05 -0400 > From: Nathan Vidican > Subject: Re: Cheap 1000Gbyte machine > > Soren Schmidt wrote: > > > > It seems Jonathan Laventhol wrote: > > > Hello Folks -- > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > Not yet :) > > > > > Or even 200 Gbyte? > > > > Yup, 300G's standing here right next to me... > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > how many can you have?). > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > drives and you should be in business, for a very resonable > > pricetag. > > > > -S=F8ren > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > Try AreaSYS electronics, they make an external ATA to SCSI RAID system > that operates independant of the O/S. I don't know how it would be in > terms of performance, but you might be able to put a few of these > devices on to a system, and use vinum/raid of the raid systems, (seeing > as how FreeBSD would just see them as giant scsi drives). > I believe they do a setup which houses 8 ATA disks, in which case you > could get away with more than what you're looking for with just two > units. > > - -- > Nathan Vidican > webmaster@wmptl.com > Windsor Match Plate & Tool Ltd. > http://www.wmptl.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 14:09:42 -0400 > From: "Allen Pulsifer" > Subject: RE: Cheap 1000Gbyte machine > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > drives and you should be in business, for a very resonable > > pricetag. > > Might be doable, but it would probably take a custom cabinet to accomoda= te > the ATA/66 cabling limitations (2 drives per cable with an 18 inch maxim= um > length). And don't forget about heat and vibration... > > Allen > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 11:17:10 -0700 (PDT) > From: Matthew Jacob > Subject: Re: Cheap 1000Gbyte machine > > > > > Nice to hear, and yes vinum is the way to go for redundancy, who is > > going to backup THAT amount of data, and on what :) > > Oh, you really still have to backups. But you hope you never have to > restore... > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 12:06:57 -0700 > From: Mike Smith > Subject: Re: Cheap 1000Gbyte machine > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > > how many can you have?). > > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > drives and you should be in business, for a very resonable > > > pricetag. > > > > You know, I used to say ixnay on that, but, Soren, I've been looking a= t a lot > > of the features of the newer ATA drives, and now that they have bad bl= ock > > replacement, I'd have to say that what you're proposing is not unreaso= nable, > > although I'd suggest that Vinum/RAID5 be used. > > Personally, I'd do it like this: > > 16 x IBM DTLA-307075 @ $550ea (approx) > 2 x 3ware Escalade 6800 @ $500ea (approx) > > You can get 24" ATA-66 cables from 3ware (or get them custom cut), which= > will greatly simplify cable routing. Presto; a terabyte for under $10k. > > Since you need to use something to stripe the two arrays together anyway= , > it's really a matter of preference between the 3ware controllers at 8 > drives each or your average addin ATA card at 4 drives a pop. > > - -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 12:31:49 -0700 (PDT) > From: Mikko Tyolajarvi > Subject: Re: Critical (or equivalent) section in Userland? > > Karl Pielorz wrote: > > >Warner Losh wrote: > > >> If advisory locks won't work (and they almost always will for things > >> like this), then you could walk the process tree. For all processes > >> that aren't suspended or yourself, send a SIGSTOP, keep a list. > > >I don't think advisory locks will work - the other process is sendmail.= .. I > >have to keep it from opening any of it's config files, whilst I 'rename= ' out > >of place the old ones (keeping any fd's to them intact) and rename in t= he new > >ones... > > Warning, here be dragons... > > You could try replacing sendmail (using mailer.conf) with a script > that sets LD_PRELOAD and then execs sendmail. Then you have to write > a little shared lib to wrap some system calls. If you are lucky, > wrapping open() will be sufficient. In your wrapper function, you > should have the opportunity to use any of a number of mutual exclusion > schemes, including advisory locking. > > Some sessions with truss/ktrace and some studying of the sendmail > source may be necessary to get it right, but this is something I'd > definitely check out. > > A wrapper for open could look like: > > #define open __hide_open_prototype > #include > #include > #include > #undef open > > int > open(const char *path, int flags, mode_t mode) > { > if (/* path is a file to be protected */) { > /* do something */ > /* and beware of calling open() recursively */ > } > return _open(path, flags, mode); > } > > Compile with "cc -shared -o open.so -fpic open.c" > > Of course, this still may not help much when sendmail has opened some > of its files, and you then change all of them, which might lead to > inconsistencies. > > $.02, > /Mikko > > - -- > Mikko Ty=F6l=E4j=E4rvi_______________________________________mikko@rsas= ecurity.com > RSA Security > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 15:57:48 -0400 > From: Robert Sexton > Subject: Re: Cheap 1000Gbyte machine > > On Fri, Aug 18, 2000 at 06:16:09PM +0100, Jonathan Laventhol wrote: > > Hello Folks -- > > > > Anybody built a file server with approx 1000 Gbyte or more? > > Or even 200 Gbyte? > > Joe Greco did this for a news machine last year. He used several wide > SCSI controllers, and a bunch of 36G drives, if I recall correctly. > > > I'm looking for a cheap simple way of doing this. Lots of > > IDE drives? (How many can you have?) Or SCSI? (Again, > > how many can you have?). > > Good, Fast, or Cheap. Pick any two :-) > > I'd suggest two Symbios based LVD SCSI Cards. Up to 14 drives per > chain, with very reasonable cabling limitations. > > Can IDE drives release the bus during seeks? Historically thats been > the big advantage of SCSI: Two IDE drives are no faster than one IDE > drive, while SCSI scales in performance. > > - -- > Robert Sexton - robert@kudra.com, Cincinnati OH, USA > Anarchy: It's not the Law, It's just a good Idea. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 21:45:14 +0100 > From: Karl Pielorz > Subject: Re: Critical (or equivalent) section in Userland? > > Mikko Tyolajarvi wrote: > > > Warning, here be dragons... > > But, they can be tamed! :) > > > You could try replacing sendmail (using mailer.conf) with a script > > that sets LD_PRELOAD and then execs sendmail. Then you have to write > > a little shared lib to wrap some system calls. If you are lucky, > > wrapping open() will be sufficient. In your wrapper function, you > > should have the opportunity to use any of a number of mutual exclusion > > schemes, including advisory locking. > > I have recently been doing a lot of work with LD_PRELOAD and wrapping > syscalls... (a strange co-incidence? :) - but, sending all the sendmail = calls > a SIGSTOP seems to have done the trick... > > > Of course, this still may not help much when sendmail has opened some > > of its files, and you then change all of them, which might lead to > > inconsistencies. > > My original idea of 'mv'ing the files seems to cope admirably with this.= .. If > sendmail open()'s one of the original files, it's FD is still valid _aft= er_ > the mv operations. > > The question has never been 'pulling the rug' from under sendmail, it's = more > been of keeping sendmail from talking to the rug, while I do the dirty..= . > > SIGSTOP and SIGCONT seem to do the trick nicely... Yes, It's not ideal, = but it > seems to work perfectly well (which maybe, makes it as ideal as you can = get in > the real world... ? :) > > - -Kp > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 14:04:57 -0700 > From: Parag Patel > Subject: Re: Cheap 1000Gbyte machine > > On Fri, 18 Aug 2000 15:57:48 EDT, Robert Sexton wrote: > > > >Can IDE drives release the bus during seeks? Historically thats been > >the big advantage of SCSI: Two IDE drives are no faster than one IDE > >drive, while SCSI scales in performance. > > How about a single IDE (master) drive per controller, that is, no slave > drives at all? This would halve the number of available drives per card > (or require twice the number of cards) but essentially would use the PCI > bus as a multiplex bus between drives instead of SCSI. > > You're still pretty much stuck waiting for one command to finish before > another can be sent to a drive though, unlike SCSI drives. Still a lot > cheaper tho'. > > I suppose another trick would be to arrange your vinum partitions and > drive layout so that master and slave drives are never accessed > simultaneously so one won't block access to the other. > > > -- Parag Patel > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 17:18:38 -0400 (EDT) > From: Mike Wade > Subject: Re: Cheap 1000Gbyte machine > > On Fri, 18 Aug 2000, Jonathan Laventhol wrote: > > > Hello Folks -- > > > > Anybody built a file server with approx 1000 Gbyte or more? > > Or even 200 Gbyte? > > > > I'm looking for a cheap simple way of doing this. Lots of > > IDE drives? (How many can you have?) Or SCSI? (Again, > > how many can you have?). > > > > It's for lots of 1 Mbyte files: no huge files. > > > > Thanks for any tips. > > You might want to check out the Arena Industrial II Rackmount RAID syste= m > from "www.raidweb.com". It has 8 x UDMA controllers that connect to the > host via Ultra2 SCSI (platform independant). Buy two (or more) of those > and 16 x (60/80 gb Maxtor UMDA Drives or 75 gb IBM UMDA Drives). > > 2 x Arena Industrial II Rackmount RAID $3,975 > 16 x Maxtor UDMA 60 gb Hard Drives $3,680 > > Total Cost $7,655 > > That comes out to about $7.98 / gb... > > - --- > Mike Wade (mwade@cdc.net) > Chief Technical Officer > CDC Internet, Inc. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 23:23:22 +0200 (CEST) > From: Soren Schmidt > Subject: Re: Cheap 1000Gbyte machine > > It seems Parag Patel wrote: > > On Fri, 18 Aug 2000 15:57:48 EDT, Robert Sexton wrote: > > > > > >Can IDE drives release the bus during seeks? Historically thats been > > >the big advantage of SCSI: Two IDE drives are no faster than one IDE > > >drive, while SCSI scales in performance. > > > > How about a single IDE (master) drive per controller, that is, no slav= e > > drives at all? This would halve the number of available drives per ca= rd > > (or require twice the number of cards) but essentially would use the P= CI > > bus as a multiplex bus between drives instead of SCSI. > > > > You're still pretty much stuck waiting for one command to finish befor= e > > another can be sent to a drive though, unlike SCSI drives. Still a lo= t > > cheaper tho'. > > Not really, if the ATA drives are configured as single masters, they can= > run simultaniously, but you will still have the PCI bus speed limit :) > Which BTW is around 120MB/s as some overhead goes to keep the system > running (yes I have measured that :) ) > > And if you have modern ATA disks, they support tagged queuing as well, > have had that running in my lab too... > > > I suppose another trick would be to arrange your vinum partitions and > > drive layout so that master and slave drives are never accessed > > simultaneously so one won't block access to the other. > > Endeed, that would be the easiest solution... > > - -S=F8ren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 14:33:58 -0700 (PDT) > From: Matthew Jacob > Subject: Re: Cheap 1000Gbyte machine > > On Fri, 18 Aug 2000, Soren Schmidt wrote: > > > It seems Parag Patel wrote: > > > On Fri, 18 Aug 2000 15:57:48 EDT, Robert Sexton wrote: > > > > > > > >Can IDE drives release the bus during seeks? Historically thats be= en > > > >the big advantage of SCSI: Two IDE drives are no faster than one ID= E > > > >drive, while SCSI scales in performance. > > > > > > How about a single IDE (master) drive per controller, that is, no sl= ave > > > drives at all? This would halve the number of available drives per = card > > > (or require twice the number of cards) but essentially would use the= PCI > > > bus as a multiplex bus between drives instead of SCSI. > > > > > > You're still pretty much stuck waiting for one command to finish bef= ore > > > another can be sent to a drive though, unlike SCSI drives. Still a = lot > > > cheaper tho'. > > > > Not really, if the ATA drives are configured as single masters, they c= an > > run simultaniously, but you will still have the PCI bus speed limit :) > > Which BTW is around 120MB/s as some overhead goes to keep the system > > running (yes I have measured that :) ) > > > > And if you have modern ATA disks, they support tagged queuing as well, > > have had that running in my lab too... > > Yes. I've seen tag depths of 32. Still not as much as SCSI, but 32 will > saturate most spindles still (I've been having to work on some non-FBSD = ATA > and S.M.A.R.T. stuff lately....) > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 17:52:28 -0400 > From: "Louis A. Mamakos" > Subject: Re: 64bit Ethernet Controllers > > > Have any 64bit PCI ethernet controllers been tested in 4.x yet? Prefer= ably > > quad port..I've seen a few around (adaptec has one) but no mention on = the > > list of specific experience. > > This may not be exactly what you meant, but the Alteon Gigabit ethernet > controllers (the ti device) are 64 bit PCI cards. The ones I'm using ha= ve > optical connections, but they do have a twisted pair version with suppor= t > for a 10/100-Base-T phy in addition to the gigabit phy. > > louie > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 18 Aug 2000 18:13:20 -0400 > From: "Patrick Bihan-Faou" > Subject: Re: Bootable CD... > > Hi, > > > Now I am trying to use the boot.flp image that comes with the 4.1-Releas= e > CD. > My alteration on that boot.flp is to replace the kernel.gz with my own (= it > contains a different set of binaries in the mfsroot. > > Now when my CD boots, the PC just goes into an endless reboot cycle. If = I > stop the boot process when "loader" is loaded and try to load my kernel > manually (load kernel.gz) the loader answers with a "don't know how to l= oad > module /kernel.gz" error. > > If I do a lsmod, there is nothing loaded. > > I am getting really confused and frustrated... Good thing that I have a > rewritable CD available :) > > > > Also on a side note, I think that it would be a great feature to have > "mount_cd9660" as part of the binaries compiled in the fixit and/or inst= all > floppies. At least this way I could mount my CD after booting from a > floppy... ohwell... > > > > Patrick. > > > "Johan Kruger" wrote in message > news:XFMail.000818184610.jkruger@oskar.dev.nanoteq.co.za... > > Ok, here's what i did ( busy building a custom CD installation ) > > After the 'make release' , i took the boot.flp image 2.88 Meg and > > mounted it. I deleted everything except for /boot/boot0-2 an the > > bootforth loader. Then i made my own kernel allowing a MFS of 2048 x 5= 12 > > blocks, giving me 1.44 Meg in the filesystem. > > In this i crunched 72 Megs of binary's , one of them 'chroot' > > I compiled init as not to look for 'rc' ( check the Makefile, define p= art > > that's specifically for a release ) > > After this i use the write_mfs_in_kernel script and umount it ( rememb= er > to > > compress the kernel after the mfs write > > > > sh -e doFS.sh -s mfsroot ./ /mnt 2880 johan's_mfsfd_root_dir/ 8000 > minimum2 > > ./write_mfs_in_kernel kernel mfsroot > > gzip -9vc kernel > kernel.gz > > vnconfig /dev/vn0 boot.flp > > mount /dev/vn0 /mnt > > rm /mnt/kernel.gz > > cp kernel.gz /mnt/kernel.gz > > umount /mnt > > vnconfig -u /dev/vn0 > > > > Now your boot.flp is ready for mkisofs > > > > Basically what happens now , i copy my complete live filesystem with > > installed apps to the CD's root dir, and when i do mkisofs, i use my n= ew > > bootimage. After boot , since it can not find rc, it executes .profile= in > > the MFS filesystem in the kernel- BUT ONLY if you compiled init for th= e > > crunch with in /usr/src/sbin/init/Makefile > > > > #CFLAGS+=3D-DDEBUGSHELL -DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > CFLAGS+=3D-DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > > > > > In .profile i put 'mount_cd9660 /dev/acd0a /cdrom' ( /cdrom an extra d= ir i > put > > in my filesystem ) and 'chroot /cdrom /setup' , where setup is my prog= , > and > > this works perfectly , i even load my own modules before the chroot an= d so > on. > > > > The release i built is 5.0-CURRRENT , and if you want the boot.flp i c= an > > attach it for you. Just mail me. Right now i'm going home - it's Frida= y - > at > > last > > GOOD LUCK > > *;-) > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 19 Aug 2000 19:00:26 +0900 > From: Katsushi Kobayashi > Subject: IEEE1394 driver system for -current > > Hello, > > I announced IEEE1394 device driver on FREENIX'99 (sorry not > on '00). I have caught up -current version at this time. > > The latest -current driver patch can be found at: > > ftp://ftp.uec.ac.jp/pub/firewire/beta/ > > I hope you success to make a kernel on your source tree. > > The driver function is still limited and may include many > bugs since the driver has been used for specific purrposes, > e.g., the driver have not supported SCSI (CAM) storage on > IEEE1394 and not been complient to loadable kernel module. > However, I think it is better to merge -current on this time and > maintain on it compared with taking a effort in independent. > > Let me know what shall I do to merge my code. > > - -- > > ikob@koganei= .wide.ad.jp > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > End of freebsd-hackers-digest V4 #925 > ************************************* > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 21 16: 4:55 2000 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 7B43537B424 for ; Mon, 21 Aug 2000 16:04:53 -0700 (PDT) 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 TAA95077; Mon, 21 Aug 2000 19:04:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 21 Aug 2000 19:04:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Damian Kuczynski Cc: freebsd-hackers@freebsd.org Subject: Re: quotas and file creditentials In-Reply-To: <3992A8C7.1B5CC765@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 Thu, 10 Aug 2000, Damian Kuczynski wrote: > When I tried to analizee problem with mail.local writing messages to > user mailmox over quota limit I saw, that once root open a file which > belongs to nonprivileged user ex. test1, and after that drops his > privlegees to this user then user test1 is able to write to this file as > many data an he want and qverquota his disk limits mail.local works in > this maneer so it is able to overquota user mailbox. > > Is this normal, or maybe file should be writen under permissions > effective user (euid=test1) Damian, Cached credentials for file descriptor (socket, file) access are a fairly widely used phenomena under UNIX, and probably not something that should be used; the defined semantics indicate that access checks can occur only on open(), not necessarily on individual read()/write() calls. However, what you could do is move the open() in mail.local to after the revocation of privilege, although you'd want to create the mailbox first with privilege if it doesn't already exist. This would probably give the correct semantics from the perspective of quotas. At one point patches to do this were floating around -- from your message, I think it's safe to assume that they were not committed. Might be worth checking the archives of -hackers and -isp. 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 Mon Aug 21 16: 6: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nantai.utsunomiya-u.ac.jp (nantai.utsunomiya-u.ac.jp [160.12.195.11]) by hub.freebsd.org (Postfix) with ESMTP id 12BEF37B5AF; Mon, 21 Aug 2000 16:05:55 -0700 (PDT) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:FMyngiPgGfNI1j/ZGBgYV3kK4cKFuIwO@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1] (may be forged)) by nantai.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id IAA20157; Tue, 22 Aug 2000 08:05:48 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:geOglOLMDw6vgnFMI7C+3aYBgqtuxtsO@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id IAA06561; Tue, 22 Aug 2000 08:12:40 +0900 (JST) Message-Id: <200008212312.IAA06561@zodiac.mech.utsunomiya-u.ac.jp> To: Ruslan Ermilov Cc: hackers@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: [PATCH] 3-button microsoft-type serial mouse In-reply-to: Your message of "Mon, 21 Aug 2000 19:37:03 +0300." <20000821193703.A15158@sunbay.com> References: <20000821193703.A15158@sunbay.com> Date: Tue, 22 Aug 2000 08:12:39 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi! > >I have a 3-button microsoft-type serial mouse (I do not know the vendor, >only FCC ID if needed) which generates the `middle button down' event as >previous `button down/up' event (any). Attached are: I have heard about this tipe of mouse. It's one of old serial mice, isn't it? >1. the script(1) output of unmodified moused(8) with comments on events. >2. the patch that makes my mouse's 3rd button work. Thank you for the patch. However, this modification should best be implemented as an option (or a special kludge for this mouse). It is perfectly valid the same data packet is sent from the mouse twice (or three time or more), and there may be some 3-button mice which stop working if this kludge is invoked for all mice as a standard feature. Kazu >Cheers, >-- >Ruslan Ermilov Oracle Developer/DBA, >ru@sunbay.com Sunbay Software AG, >ru@FreeBSD.org FreeBSD committer, >+380.652.512.251 Simferopol, Ukraine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 21 16:16:20 2000 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 61FF837B423 for ; Mon, 21 Aug 2000 16:16:13 -0700 (PDT) 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 TAA95190; Mon, 21 Aug 2000 19:15:57 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 21 Aug 2000 19:15:57 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: David Kirchner Cc: freebsd-hackers@freebsd.org Subject: Re: quotacheck on a live filesystem; safe? (fwd) 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 Due to the locking involved in ufs_quota.c's management of the quota files, I believe it may be possible to get a deadlock when modifying the quota from userland. I haven't thought through all the details yet, and am not familiar with the quotacheck.c code, but there are some related deadlock conditions in the extended attribute code as it uses backing files in much the same way. In essence, the UFS code holds onto an extra reference to the quota record file as part of the file system mount structure. When it needs to commit quota updates to disk, it acquires a vnode lock for the record file. However, this is not done using the locking protocol -- i.e., the locking order may not be maintained. The caller to ufs_readwrite() may already hold the lock on another file; I'm not sure how rigorously the quota code checks for this type of situation, but if you are getting either hangs during direct quota file modification, or lock manager panics, that could be the source. I believe quotacheck.c attempts to directly access the backing file, in which case such a deadlock could arise. The quotactl interface appears to support a call to set/get quota settings/usage, which should be used to manipulate quotas -- never direct quota backing file access. I make no promise about the accuracy of my claims about the existing quotacheck implementation, but that might be a place to start looking, and you can certainly imagine problems coming about as a result. You might also be able to imagine that direct user access to the quota backing files could be used to bottleneck or entirely block write access to the file system, due to locking requirements. In the extended attribute implementation, I generally recommend that backing files be stored in a directory inaccessible to non-administrative users, as the ability to hold vnode locks for the file (i.e., long vop_read/write calls) could impact performance substantially, or allow a deadlock to arise/be engineered. Robert Watson On Thu, 10 Aug 2000, David Kirchner wrote: > I've searched the archives and I've seen this question asked a few other > times, but I did not see any response. Does anyone know the answer? > > ---------- Forwarded message ---------- > Date: Wed, 9 Aug 2000 14:15:17 -0700 (PDT) > From: David Kirchner > To: freebsd-questions@FreeBSD.ORG > Subject: quotacheck on a live filesystem; safe? > > > Hi, > > I've been reading over source for quotacheck and ufs_quota.c and so far I > have not found a reason why running quotacheck on a live filesystem would > cause anything but inconsistencies in the quota.user file. Is this an > incorrect belief? > > >From what I understand: > > the quota.user file is used as a storage for quota information between > boots and by the various userland quota reporting utilities. The kernel > maintains an idea of the quota in memory, and commits it to disk when > necessary. > > If this is correct, then I could expect, at worst, someone's quota to be > invalid if the machine crashes while quotacheck is running and their files > are being modified? > > Thanks, > David Kirchner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > > > 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 Mon Aug 21 18: 1:33 2000 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 D860037B507 for ; Mon, 21 Aug 2000 18:01:27 -0700 (PDT) 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 VAA96232; Mon, 21 Aug 2000 21:01:13 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 21 Aug 2000 21:01:13 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jonas Bulow Cc: hackers@freebsd.org Subject: Re: freebsd and non-preemtive threads In-Reply-To: <3997C2C5.83AFE056@servicefactory.se> 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 Both Coda and Arla make use of an LWP implementation originating at CMU. I believe that the implementation can make use of timers to add preemption, but know that in Coda preemption is not supported: LWPs are used to represent in-process (potentially blocking) RPCs on both the client and server, and are quite light weight, meaning low context-switch overhead with minimal kernel involvement. As a result, AFS and Coda servers tend to run with hundreds, if not thousands of threads: a feat not possible in many 1:1 userland thread/kernel mappings (Linux kernel threads, for example), and often not all that scalable in m:n models. However, as with other library-based thread mechanisms, you have to be careful to direct potentially blocking calls through the thread-aware versions of the calls so as not to block all other threads. As the LWP code used in AFS/Coda/Arla uses select() for blocking/timeout management, there are some scalability issues with lots of blocked threads--these might be improved through use of poll() or kqueue(). For reference, my recollection is that peemption-aware userland thread libraries tend to make alot of timer syscalls, losing some of the advantage of being a userland thread library (low context switch cost, few transistions between user/kerneland). The AFS LWP code included a fasttime() mechanism that took advantage of the ability to mmap kernel memory under SunOS, allowing direct access to the timer variable in kernel, without a context switch. I do not believe that native ports to Linux/FreeBSD/et al have retained this capability, especially given its requirements for privilege. However, it would be easy to imagine a kernel module exporting a /dev/time, which had the singular ability of allowing the mmaping of a page containing only the kernel's timer variables, permitting syscall-free precise time access from userland using atomic memory access calls. 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 Mon Aug 21 18:13:20 2000 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 4CE7537B423; Mon, 21 Aug 2000 18:13:18 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7M1DGJ12836; Mon, 21 Aug 2000 18:13:16 -0700 (PDT) Date: Mon, 21 Aug 2000 18:13:16 -0700 From: Alfred Perlstein To: Robert Watson Cc: Jonas Bulow , hackers@FreeBSD.ORG Subject: Re: freebsd and non-preemtive threads Message-ID: <20000821181316.J4854@fw.wintelcom.net> References: <3997C2C5.83AFE056@servicefactory.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from rwatson@FreeBSD.ORG on Mon, Aug 21, 2000 at 09:01:13PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Robert Watson [000821 18:01] wrote: > > For reference, my recollection is that peemption-aware userland thread > libraries tend to make alot of timer syscalls, losing some of the > advantage of being a userland thread library (low context switch cost, few > transistions between user/kerneland). The AFS LWP code included a > fasttime() mechanism that took advantage of the ability to mmap kernel > memory under SunOS, allowing direct access to the timer variable in > kernel, without a context switch. I do not believe that native ports to > Linux/FreeBSD/et al have retained this capability, especially given its > requirements for privilege. However, it would be easy to imagine a kernel > module exporting a /dev/time, which had the singular ability of allowing > the mmaping of a page containing only the kernel's timer variables, > permitting syscall-free precise time access from userland using atomic > memory access calls. I think phk and I discussed this about a year ago, our idea was to automatically map the segment in for each process (also allowing things like getpid and such to be accessable). It would be nice to see happen either way (mmap'able /dev/time or automatically) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 4:35:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from procsys.com (PPP-180-142.bng.vsnl.net.in [203.197.180.142]) by hub.freebsd.org (Postfix) with SMTP id EF29437B43C for ; Tue, 22 Aug 2000 04:35:27 -0700 (PDT) Received: from procsys.com ([192.168.1.115]) by procsys.com with SMTP; Tue, 22 Aug 2000 17:08:10 +0800 Message-ID: <39A2664F.3337A741@procsys.com> Date: Tue, 22 Aug 2000 17:08:55 +0530 From: Pran Joseph Reply-To: pran@procsys.com Organization: Processor Systems (India) Pvt. Ltd X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Memory Mapping 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 am trying to write a PCI ethernet driver for FreeBSD 3.4 release . I am new to the driver stuff. I want to allocate some memory for device buffer using malloc function. I also want the physical address of allocated memory block so that I can initialize the device registers. Can any one of you please explain me how I can convert address returned by malloc to Physical address. Thanks -Pran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 4:44:35 2000 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 57E5937B424 for ; Tue, 22 Aug 2000 04:44:32 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7MBiLD27083; Tue, 22 Aug 2000 04:44:21 -0700 (PDT) Date: Tue, 22 Aug 2000 04:44:21 -0700 From: Alfred Perlstein To: Pran Joseph Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Memory Mapping Message-ID: <20000822044421.Q4854@fw.wintelcom.net> References: <39A2664F.3337A741@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39A2664F.3337A741@procsys.com>; from pran@procsys.com on Tue, Aug 22, 2000 at 05:08:55PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Pran Joseph [000822 04:36] wrote: > Hi, > > I am trying to write a PCI ethernet driver for FreeBSD 3.4 release . I > am new to the driver stuff. > > I want to allocate some memory for device buffer using malloc > function. I also want the physical address of allocated memory block > so that I can initialize the device registers. > > Can any one of you please explain me how I can convert address > returned by > malloc to Physical address. VTOPHYS or vtophys. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 6:29:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kuku.excite.com (kuku-rwcmta.excite.com [198.3.99.63]) by hub.freebsd.org (Postfix) with ESMTP id 74E3E37B424 for ; Tue, 22 Aug 2000 06:29:35 -0700 (PDT) Received: from magic.excite.com ([199.172.148.161]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20000822132935.EDPD8172.kuku.excite.com@magic.excite.com> for ; Tue, 22 Aug 2000 06:29:35 -0700 Message-ID: <5061190.966950975267.JavaMail.imail@magic.excite.com> Date: Tue, 22 Aug 2000 06:29:34 -0700 (PDT) From: bliss-s@excite.com To: hackers@freebsd.org Subject: Advanced OS Questions only you can answer... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 192.45.228.88 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am stuck between a rock and a hard place. I've been to your website, I've logged in under deja.news and posted questions, I've emailed several people, and my Dad even called the BSD 800 number for me and paid a fee to find out that all my questions are too advanced for their services. The representative at the 800 number told my Dad that my only hope was to send this email to you. I am researching OS's and chose FreeBSD because it was open source. I know nothing about OS's. I thought open source would mean that I could review the documentation and find all my answers. However, open source means nothing to me because I reviewed the documentation, and it doesn't help me out because I know no terms good enough to understand the documentation. I've been doing this now for 4 weeks...what is sad is that I need answers to these questions in 2 weeks. I have a highschool paper that is due in 3 weeks, and the teacher is unable to help me out...my Dad doesn't have the knowledge...so, as you can tell by now, I suck at getting this paper completed in time. I am very green on this, so please keep this in mind if you are able to answer the questions below. I understand that there might be a fee for this....if so, please let me know. Again, you are my only hope. I thank you VERY much With most SINCERE thanks! David Igo ========================================= 1. How does this OS manage process scheduling, interprocess communication, process synchronization, and of handling deadlocks. 2. How does the OS manage main memory and does it manage secondary storage to back up main memory. I need on algorithm and one structure to show this management...along with how they relate to the management. 3. I need the key characteristics of the OS supporting file structures and access methods in regards to types of access methods, directory structures, data protection, and file consistency. 4. How does the OS control peripheral devices and the input/output need for applications regarding input/output design, interfaces, internal system structures. 5. how does the OS provide for a collection of processors including: a. processors that do not share a memory b. processor that do not share a clock c. storage devices dispersed among various sites d. distributed file system e. process synchoronization f. process communication g. failures recovery 6. And finally, how does the OS ensure the protection and security of files, memory, segments, and CPU for data and code in the following situations: a. Unauthorized access b. mailicious destruction, c. alteration d. accidental introduction of inconsistency I CAN'T THANK YOU ENOUGH FOR TAKING THE TIME TO HELP ME OUT. _______________________________________________________ Say Bye to Slow Internet! http://www.home.com/xinbox/signup.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 7:10:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from diskfarm.firehouse.net (rdu25-12-043.nc.rr.com [24.25.12.43]) by hub.freebsd.org (Postfix) with ESMTP id 51B9F37B43E for ; Tue, 22 Aug 2000 07:10:46 -0700 (PDT) Received: (from abc@localhost) by diskfarm.firehouse.net (8.9.3/8.9.3) id OAA89368; Tue, 22 Aug 2000 14:10:37 GMT (envelope-from abc) Date: Tue, 22 Aug 2000 14:10:37 +0000 From: Alan Clegg To: bliss-s@excite.com Cc: hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... Message-ID: <20000822141037.B89195@diskfarm.firehouse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bliss-s@excite.com on Tue, Aug 22, 2000 at 06:29:34AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of the ether, bliss-s@excite.com spewed forth the following bitstream: > I am stuck between a rock and a hard place. I've been to your website, I've > logged in under deja.news and posted questions, I've emailed several people, > and my Dad even called the BSD 800 number for me and paid a fee to find out > that all my questions are too advanced for their services. The > representative at the 800 number told my Dad that my only hope was to send > this email to you. My guess is that the answer was more along the lines of "Can't your son do his own homework/research?" AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 7:24:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 4A8F537B43E for ; Tue, 22 Aug 2000 07:24:36 -0700 (PDT) Received: (qmail 60618 invoked by uid 1001); 22 Aug 2000 14:19:13 -0000 Date: Tue, 22 Aug 2000 17:19:13 +0300 From: Peter Pentchev To: bliss-s@excite.com Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... Message-ID: <20000822171913.D58183@ringwraith.office1.bg> References: <5061190.966950975267.JavaMail.imail@magic.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5061190.966950975267.JavaMail.imail@magic.excite.com>; from bliss-s@excite.com on Tue, Aug 22, 2000 at 06:29:34AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The short answer: none of your questions has a short answer. A recommendation: get Kirk McKusick's "Design and Implementation of 4.4BSD", it has a lot of the information you need, and a quick skim through the relevant chapters should be enough to give you an idea of the answers you need. I think that for most people, the ability to really answer even half of your questions would come after several university-level courses in computer science and OS design, and/or after several years' worth of work in the field. (alright, so there may be exceptions.. if you happen to be one of them, or if you've had those several years of programming experience, then McKusick's book should give you the answers you need :) G'luck, Peter -- The rest of this sentence is written in Thailand, on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 7:27:21 2000 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 F1D7037B424 for ; Tue, 22 Aug 2000 07:27:18 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id AE9709B05; Tue, 22 Aug 2000 10:27:17 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id A1F61BA03; Tue, 22 Aug 2000 10:27:17 -0400 (EDT) Date: Tue, 22 Aug 2000 10:27:17 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: bliss-s@excite.com Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... In-Reply-To: <5061190.966950975267.JavaMail.imail@magic.excite.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, 22 Aug 2000 bliss-s@excite.com wrote: *snip* > > I am researching OS's and chose FreeBSD because it was open source. I know > nothing about OS's. I thought open source would mean that I could review > the documentation and find all my answers. However, open source means > nothing to me because I reviewed the documentation, and it doesn't help me > out because I know no terms good enough to understand the documentation. > I've been doing this now for 4 weeks...what is sad is that I need answers to > these questions in 2 weeks. I have a highschool paper that is due in 3 > weeks, and the teacher is unable to help me out...my Dad doesn't have the > knowledge...so, as you can tell by now, I suck at getting this paper > completed in time. > If you know nothing about OS's, perhaps you should start with an easier topic than BSD internals. Also, Open Source means that the source is available, not that everything you have questions on is documented. And since FreeBSD is done almost completely by volunteers, what information you do find has been contributed by those with the time and interest, not because they get paid for it. However, you are welcome to contribute your answers back to the project for future reference. Many of your questions can be answered by reading a copy of Design and Implementation of 4.4BSD, available at most fine bookstores. In addition, you are welcome to UTSL (Use The Source, Luke). ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 7:35: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 9245937B424 for ; Tue, 22 Aug 2000 07:34:56 -0700 (PDT) Received: from localhost (lists@localhost) by security.za.net (8.9.3/8.9.3) with ESMTP id QAA26329 for ; Tue, 22 Aug 2000 16:34:49 +0200 (SAST) (envelope-from lists@security.za.net) Date: Tue, 22 Aug 2000 16:34:49 +0200 (SAST) From: Lists Account To: hackers@freebsd.org Subject: IBM ServerRaid 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 All, does anyone know if there are any IBM Server raid drivers for FreeBSD out there? If So can anyone tell me where I can get one Thanks Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 8:42:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id E892F37B42C for ; Tue, 22 Aug 2000 08:42:07 -0700 (PDT) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id 06F2C3A6; Tue, 22 Aug 2000 11:42:02 -0400 (EDT) Received: (from jon@localhost) by fury.csh.rit.edu (8.9.3+Sun/8.9.1) id LAA26801; Tue, 22 Aug 2000 11:41:36 -0400 (EDT) Date: Tue, 22 Aug 2000 11:41:36 -0400 From: Jon Parise To: bliss-s@excite.com Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... Message-ID: <20000822114135.D25556@csh.rit.edu> References: <5061190.966950975267.JavaMail.imail@magic.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <5061190.966950975267.JavaMail.imail@magic.excite.com>; from bliss-s@excite.com on Tue, Aug 22, 2000 at 06:29:34AM -0700 X-Operating-System: SunOS 5.7 (sun4u) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 22, 2000 at 06:29:34AM -0700, bliss-s@excite.com wrote: > I am very green on this, so please keep this in mind if you are able to > answer the questions below. I understand that there might be a fee for > this....if so, please let me know. Looks like you bit off a lot more than you could chew. =) Have a look here for some seminar information on 4.4BSD internals: http://www.csh.rit.edu/seminars/os/19962/week4/ -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 9:47:35 2000 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 8235037B423 for ; Tue, 22 Aug 2000 09:47:26 -0700 (PDT) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id MAA00344 for ; Tue, 22 Aug 2000 12:47:26 -0400 (EDT) Date: Tue, 22 Aug 2000 12:44:14 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: kernel debugging on 4.1-release 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 try to trace some system call using remote debugging and find something that I can not explain myself (the related source is ffs_write()): case 1: ------- 443 if (object) (gdb) break 430 Breakpoint 6 at 0xc0289cea: file ../../ufs/ufs/ufs_readwrite.c, line 430. (gdb) c Continuing. Breakpoint 6, ffs_write (ap=0xc64f5e70) at ../../ufs/ufs/ufs_readwrite.c:438 438 p = uio->uio_procp; In the above case, even if I set breakpoint 6 at line 430, it insists on line 438. case 2: ------- (gdb) print p->p_limit $1 = (struct plimit *) 0xffffffff In the above case, the statement has just used p->p_limit to do some comparison and yet gdb says its value is -1. The statement using it is: if (vp->v_type == VREG && p && uio->uio_offset + uio->uio_resid > p->p_rlimit[RLIMIT_FSIZE].rlim_cur) { Are these bugs of gdb or am I doing something wrong? I notice that 4.1-release install KLD files at the same time you install kernel. In the past, I only copy the file kernel.debug to the target machine. Do I have to copy those .ko files to the target machine as well? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 9:54: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from herd.plethora.net (herd.plethora.net [205.166.146.1]) by hub.freebsd.org (Postfix) with ESMTP id 47E6F37B422 for ; Tue, 22 Aug 2000 09:54:01 -0700 (PDT) Received: from guild.plethora.net (root@guild.plethora.net [205.166.146.8]) by herd.plethora.net (8.9.0/8.9.0) with ESMTP id LAA09193; Tue, 22 Aug 2000 11:53:55 -0500 (CDT) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.9.3/8.9.0) with ESMTP id LAA11615; Tue, 22 Aug 2000 11:53:53 -0500 (CDT) Message-Id: <200008221653.LAA11615@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: bliss-s@excite.com Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... Date: Tue, 22 Aug 2000 11:53:53 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >1. How does this OS manage process scheduling, interprocess communication, >process synchronization, and of handling deadlocks. These are four totally unrelated questions. For most OS's, I'd suggest you start with the same question, without the "how", because most don't really do much with this. BSD-derived systems have a variety of IPC mechanisms, and at least a couple of algorithms that control scheduling. As to "handling deadlocks", the OS may not handle them at all; you're welcome to write a pair of programs that deadlock and just sit there forever. >2. How does the OS manage main memory and does it manage secondary storage >to back up main memory. I need on algorithm and one structure to show this >management...along with how they relate to the management. The OS manages main memory by breaking it up into 8 1/2 by 11 sections of bits called "pages". (The 1/2 is used for parity.) Secondary storage is not generally used to back up main memory; instead, the OS uses tertiary storage to back up main memory, since this is generally more reliable. An algorithm might be while (no-free-memory) { kill(rand(), 9); } A structure could be struct { int yes; char *no; }; >3. I need the key characteristics of the OS supporting file structures and >access methods in regards to types of access methods, directory structures, >data protection, and file consistency. It's very good at all of these, across the board. File loss is less than 300ppm, directory structures are roughly half the size of typical files, and most common access methods are supported. >4. How does the OS control peripheral devices and the input/output need for >applications regarding input/output design, interfaces, internal system >structures. If the peripheral devices misbehave, the OS stops providing power to them. Your question implies that applications are "designed"; this is incorrect. Applications are thrown together over a weekend before the release date. The time before that is spent getting wildly drunk. Internal system structures: They're internal, you don't need to know. >5. how does the OS provide for a collection of processors including: > a. processors that do not share a memory It doesn't. > b. processor that do not share a clock It doesn't. > c. storage devices dispersed among various sites It doesn't. > d. distributed file system NFS. > e. process synchoronization It doesn't. > f. process communication It doesn't. > g. failures recovery It doesn't. >6. And finally, how does the OS ensure the protection and security of >files, memory, segments, and CPU for data and code in the following >situations: > a. Unauthorized access It says "ERROR ERROR ERROR" in a monotone. > b. mailicious destruction, It doesn't. No OS does. If your data is destroyed, *it is destroyed*. > c. alteration Ditto. If you want to make backups, go ahead. > d. accidental introduction of inconsistency Mostly this is left to hardware. >I CAN'T THANK YOU ENOUGH FOR TAKING THE TIME TO HELP ME OUT. But you can't be bothered to take the time to learn *ANYTHING* about the field. There is no way you can be experienced enough for it to make sense for you to be assigned to research these questions, yet so inexperienced as to make the obvious gaffes you did throughout this procedure. The answers above, if you have any business seeking the real answers, will help you on your way. If they don't seem helpful, *you are not ready to understand these questions*. Your questions came out like someone coming to an AIDS conference and asking why letting blood isn't helping, and whether anyone knows which humors are affected by AIDS. You need to learn the basics before you can get into OS internals. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 10: 8:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id AC2D437B422 for ; Tue, 22 Aug 2000 10:08:34 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id e7MHEbL05793; Tue, 22 Aug 2000 12:14:37 -0500 (CDT) (envelope-from jlemon) Date: Tue, 22 Aug 2000 12:14:37 -0500 (CDT) From: Jonathan Lemon Message-Id: <200008221714.e7MHEbL05793@prism.flugsvamp.com> To: seebs@plethora.net, hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >>2. How does the OS manage main memory and does it manage secondary storage >>to back up main memory. I need on algorithm and one structure to show this >>management...along with how they relate to the management. > >The OS manages main memory by breaking it up into 8 1/2 by 11 sections of bits >called "pages". (The 1/2 is used for parity.) Yes, but this is not portable. For a better fit, the OS should strive to maintain ISO 216 compliance as well, if possible. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 10: 9:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 05EC337B424 for ; Tue, 22 Aug 2000 10:09:39 -0700 (PDT) Received: from localhost (IDENT:QpdpJlBNhLcj5Y2Po3scTz343lD6QBGb0iAgZh1rmJ/Wb+m2KiIOmUQTRKqWTaeg@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/8.11.0/peace) with ESMTP/inet6 id e7MH93v84262; Wed, 23 Aug 2000 02:09:03 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 23 Aug 2000 02:08:59 +0900 (JST) Message-Id: <20000823.020859.74674005.ume@mahoroba.org> To: n@nectar.com Cc: freebsd-hackers@freebsd.org Subject: Re: Testers wanted: nsswitch From: Hajimu UMEMOTO In-Reply-To: <20000819163017.A30595@hamlet.nectar.com> References: <20000819163017.A30595@hamlet.nectar.com> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 Sat, 19 Aug 2000 16:30:17 -0500 >>>>> "Jacques A. Vidrine" said: n> I've made a port of NetBSD's nsswitch code. This allows one to n> configure various databases such as passwd(5) to use files, NIS, n> or Hesiod. I like bringing nsswitch into FreeBSD. It will reduce maintainance cost around resolver related routins. When I merged KAME effort around fixing DNS query order problem from NetBSD, I was forced to work with nsswitch -> host.conf issue. Your nsswith support in getaddrinfo.c is quite different from NetBSD's one. (maybe name6.c, too?) Why don't you simply bring the code from NetBSD? The origin of getadrinfo.c and name6.c is KAME, and basically these files are same between NetBSD and FreeBSD except some OS depend part such as reading host.conf. We should keep close these files to NetBSD as possible. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 10:10:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from herd.plethora.net (herd.plethora.net [205.166.146.1]) by hub.freebsd.org (Postfix) with ESMTP id 02EFB37B446 for ; Tue, 22 Aug 2000 10:10:40 -0700 (PDT) Received: from guild.plethora.net (root@guild.plethora.net [205.166.146.8]) by herd.plethora.net (8.9.0/8.9.0) with ESMTP id MAA09270; Tue, 22 Aug 2000 12:10:38 -0500 (CDT) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.9.3/8.9.0) with ESMTP id MAA12340; Tue, 22 Aug 2000 12:10:37 -0500 (CDT) Message-Id: <200008221710.MAA12340@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: Jonathan Lemon Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... In-reply-to: Your message of "Tue, 22 Aug 2000 12:14:37 CDT." <200008221714.e7MHEbL05793@prism.flugsvamp.com> Date: Tue, 22 Aug 2000 12:10:37 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008221714.e7MHEbL05793@prism.flugsvamp.com>, Jonathan Lemon writ es: >In article t> you write: >>>2. How does the OS manage main memory and does it manage secondary storage >>>to back up main memory. I need on algorithm and one structure to show this >>>management...along with how they relate to the management. >> >>The OS manages main memory by breaking it up into 8 1/2 by 11 sections of bit >s >>called "pages". (The 1/2 is used for parity.) > >Yes, but this is not portable. For a better fit, the OS should strive >to maintain ISO 216 compliance as well, if possible. Look, I don't think we want to confuse the kid. It's bad enough that the crossways "8 inches" just refers to a standard octet, but the vertical 11 inches is a 2^N thing. It's worse still that, on most platforms, the page is really 12 or 13 inches. I wanted to start him with the easy case. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 10:12:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id A3FB937B423 for ; Tue, 22 Aug 2000 10:12:44 -0700 (PDT) Received: (qmail 61495 invoked by uid 1001); 22 Aug 2000 17:07:18 -0000 Date: Tue, 22 Aug 2000 20:07:18 +0300 From: Peter Pentchev To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: kernel debugging on 4.1-release Message-ID: <20000822200718.F58183@ringwraith.office1.bg> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zzhang@cs.binghamton.edu on Tue, Aug 22, 2000 at 12:44:14PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 22, 2000 at 12:44:14PM -0400, Zhihui Zhang wrote: > > I try to trace some system call using remote debugging and find something > that I can not explain myself (the related source is ffs_write()): > > case 1: > ------- > > 443 if (object) > (gdb) break 430 > Breakpoint 6 at 0xc0289cea: file ../../ufs/ufs/ufs_readwrite.c, line 430. > (gdb) c > Continuing. > > Breakpoint 6, ffs_write (ap=0xc64f5e70) at > ../../ufs/ufs/ufs_readwrite.c:438 > 438 p = uio->uio_procp; > > In the above case, even if I set breakpoint 6 at line 430, it insists on > line 438. This is caused by compiler optimization - gcc notices lines 430 and 438 are the same (actually not the lines themselves, but the relevant blocks of code, which may have nothing to do with source organization in lines), and only generates the code once. For debugging purposes, it stores debug information that it has done so - and gdb knows that a breakpoint on line 430 should actually be placed at the code fragment corresponding to line 438. > > case 2: > ------- > > (gdb) print p->p_limit > $1 = (struct plimit *) 0xffffffff > > In the above case, the statement has just used p->p_limit to do some > comparison and yet gdb says its value is -1. The statement using it is: > > if (vp->v_type == VREG && p && > uio->uio_offset + uio->uio_resid > > p->p_rlimit[RLIMIT_FSIZE].rlim_cur) { I'm not quite sure about this one, but it might very well be also related to gcc optimizing something out; I've cursed it more than once, trying to debug things compiled with -O -g, and finding some of my local vars totally gone, common subexpressions eliminated or only calculated once, whole dead code branches gone, and the like :) For debugging without tearing more than half of your hair out, compile the kernel with no -O options and with some kind of -g options; I personally use -ggdb -g3 for more gdb-targeted output (though I would be the first to admit I know nothing about just what does gcc do that is gdb-targeted :) G'luck, Peter -- The rest of this sentence is written in Thailand, on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 10:17:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by hub.freebsd.org (Postfix) with ESMTP id 2CC5D37B423 for ; Tue, 22 Aug 2000 10:17:29 -0700 (PDT) Received: from boostworks.com (root@oldrn.luxdev.boostworks.com [192.168.1.99]) by luxren2.boostworks.com (8.9.1/8.9.1) with ESMTP id TAA23213; Tue, 22 Aug 2000 19:17:03 +0200 (CEST) Message-Id: <200008221717.TAA23213@luxren2.boostworks.com> Date: Tue, 22 Aug 2000 19:16:59 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@boostworks.com Subject: Re: Advanced OS Questions only you can answer... To: seebs@plethora.net Cc: jlemon@flugsvamp.com, hackers@FreeBSD.ORG In-Reply-To: <200008221710.MAA12340@guild.plethora.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Aug, Peter Seebach wrote: > In message <200008221714.e7MHEbL05793@prism.flugsvamp.com>, Jonathan Lemon writ > es: >>In article >t> you write: >>>>2. How does the OS manage main memory and does it manage secondary storage >>>>to back up main memory. I need on algorithm and one structure to show this >>>>management...along with how they relate to the management. >>> >>>The OS manages main memory by breaking it up into 8 1/2 by 11 sections of bit >>s >>>called "pages". (The 1/2 is used for parity.) >> >>Yes, but this is not portable. For a better fit, the OS should strive >>to maintain ISO 216 compliance as well, if possible. > > Look, I don't think we want to confuse the kid. It's bad enough that the > crossways "8 inches" just refers to a standard octet, but the vertical 11 > inches is a 2^N thing. It's worse still that, on most platforms, the page > is really 12 or 13 inches. > > I wanted to start him with the easy case. > Rigth. 0.33 meter in processors running in Europe countries. (Using Metric RAM, or MRAM). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 10:19:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bw150zhb.bluewin.ch (bw150zhb.bluewin.ch [195.186.1.68]) by hub.freebsd.org (Postfix) with ESMTP id 1A19C37B42C for ; Tue, 22 Aug 2000 10:19:46 -0700 (PDT) Received: from aleph (bw1-41pub70.bluewin.ch [195.186.41.70]) by bw150zhb.bluewin.ch (8.9.3/8.9.3) with SMTP id TAA05226; Tue, 22 Aug 2000 19:19:39 +0200 (MET DST) From: "Oliver Fehr" To: , Subject: RE: Advanced OS Questions only you can answer... Date: Tue, 22 Aug 2000 19:19:12 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 In-Reply-To: <5061190.966950975267.JavaMail.imail@magic.excite.com> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recommend reading "Modern Operating Systems" by Andrew S. Tannenbaum (Prentice Hall). Though a bit old (1992, I think) it will give you most of the information you want. Hope that helps Kind Regards Oliver Fehr E-Mail:oliver.fehr@ofehr.com -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of bliss-s@excite.com Sent: Tuesday, August 22, 2000 3:30 PM To: hackers@freebsd.org Subject: Advanced OS Questions only you can answer... I am stuck between a rock and a hard place. I've been to your website, I've logged in under deja.news and posted questions, I've emailed several people, and my Dad even called the BSD 800 number for me and paid a fee to find out that all my questions are too advanced for their services. The representative at the 800 number told my Dad that my only hope was to send this email to you. I am researching OS's and chose FreeBSD because it was open source. I know nothing about OS's. I thought open source would mean that I could review the documentation and find all my answers. However, open source means nothing to me because I reviewed the documentation, and it doesn't help me out because I know no terms good enough to understand the documentation. I've been doing this now for 4 weeks...what is sad is that I need answers to these questions in 2 weeks. I have a highschool paper that is due in 3 weeks, and the teacher is unable to help me out...my Dad doesn't have the knowledge...so, as you can tell by now, I suck at getting this paper completed in time. I am very green on this, so please keep this in mind if you are able to answer the questions below. I understand that there might be a fee for this....if so, please let me know. Again, you are my only hope. I thank you VERY much With most SINCERE thanks! David Igo ========================================= 1. How does this OS manage process scheduling, interprocess communication, process synchronization, and of handling deadlocks. 2. How does the OS manage main memory and does it manage secondary storage to back up main memory. I need on algorithm and one structure to show this management...along with how they relate to the management. 3. I need the key characteristics of the OS supporting file structures and access methods in regards to types of access methods, directory structures, data protection, and file consistency. 4. How does the OS control peripheral devices and the input/output need for applications regarding input/output design, interfaces, internal system structures. 5. how does the OS provide for a collection of processors including: a. processors that do not share a memory b. processor that do not share a clock c. storage devices dispersed among various sites d. distributed file system e. process synchoronization f. process communication g. failures recovery 6. And finally, how does the OS ensure the protection and security of files, memory, segments, and CPU for data and code in the following situations: a. Unauthorized access b. mailicious destruction, c. alteration d. accidental introduction of inconsistency I CAN'T THANK YOU ENOUGH FOR TAKING THE TIME TO HELP ME OUT. _______________________________________________________ Say Bye to Slow Internet! http://www.home.com/xinbox/signup.html 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 Tue Aug 22 10:20: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from herd.plethora.net (herd.plethora.net [205.166.146.1]) by hub.freebsd.org (Postfix) with ESMTP id 947E937B43E for ; Tue, 22 Aug 2000 10:20:00 -0700 (PDT) Received: from guild.plethora.net (root@guild.plethora.net [205.166.146.8]) by herd.plethora.net (8.9.0/8.9.0) with ESMTP id MAA09347; Tue, 22 Aug 2000 12:20:00 -0500 (CDT) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.9.3/8.9.0) with ESMTP id MAA12743; Tue, 22 Aug 2000 12:19:59 -0500 (CDT) Message-Id: <200008221719.MAA12743@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: remy@boostworks.com Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... In-reply-to: Your message of "Tue, 22 Aug 2000 19:16:59 +0200." <200008221717.TAA23213@luxren2.boostworks.com> Date: Tue, 22 Aug 2000 12:19:58 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008221717.TAA23213@luxren2.boostworks.com>, Remy Nonnenmacher wr ites: >On 22 Aug, Peter Seebach wrote: >> Look, I don't think we want to confuse the kid. It's bad enough that the >> crossways "8 inches" just refers to a standard octet, but the vertical 11 >> inches is a 2^N thing. It's worse still that, on most platforms, the page >> is really 12 or 13 inches. >> I wanted to start him with the easy case. >Rigth. 0.33 meter in processors running in Europe countries. >(Using Metric RAM, or MRAM). Sheesh! The sad thing is, after all the other crap in this thread, he'll think you're joking. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 11:20:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 281EF37B43C for ; Tue, 22 Aug 2000 11:20:41 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA20982; Tue, 22 Aug 2000 11:32:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008221832.LAA20982@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lists Account Cc: hackers@freebsd.org Subject: Re: IBM ServerRaid In-reply-to: Your message of "Tue, 22 Aug 2000 16:34:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Aug 2000 11:32:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi All, > > does anyone know if there are any IBM Server raid drivers for FreeBSD out > there? If So can anyone tell me where I can get one Not at this point in time. There's been some noise about it, and I've been promised one to work on, but nothing's happening just yet. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 11:31:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 4029837B423 for ; Tue, 22 Aug 2000 11:31:13 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 9A1321925E; Tue, 22 Aug 2000 13:31:12 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id NAA41788; Tue, 22 Aug 2000 13:31:12 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Tue, 22 Aug 2000 13:31:12 -0500 From: "Jacques A. Vidrine" To: Hajimu UMEMOTO Cc: freebsd-hackers@freebsd.org Subject: Re: Testers wanted: nsswitch Message-ID: <20000822133112.A41773@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Hajimu UMEMOTO , freebsd-hackers@freebsd.org References: <20000819163017.A30595@hamlet.nectar.com> <20000823.020859.74674005.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000823.020859.74674005.ume@mahoroba.org>; from ume@mahoroba.org on Wed, Aug 23, 2000 at 02:08:59AM +0900 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 23, 2000 at 02:08:59AM +0900, Hajimu UMEMOTO wrote: [snip] > Your nsswith support in getaddrinfo.c is quite different from NetBSD's > one. (maybe name6.c, too?) Why don't you simply bring the code from > NetBSD? > The origin of getadrinfo.c and name6.c is KAME, and basically these > files are same between NetBSD and FreeBSD except some OS depend part > such as reading host.conf. We should keep close these files to NetBSD > as possible. I intended to inquire about this: I wasn't sure if there were many FreeBSDisms in the resolver, and because I have a healthy fear of breaking the resolver, I tried not to change its behavior significantly. Now that I understand the source of getadrinfo.c and name6.c, I will indeed sync them with NetBSD inasmuch as is possible. Thanks for bringing this up! -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / 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 Tue Aug 22 11:42:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fobos.marketsite.ru (fobos.marketsite.ru [194.226.198.36]) by hub.freebsd.org (Postfix) with ESMTP id A6A8737B43C; Tue, 22 Aug 2000 11:42:27 -0700 (PDT) Received: from bb.marketsite.ru ([194.226.198.1] helo=runnet-gw.marketsite.ru) by fobos.marketsite.ru with esmtp (Exim 3.14 #40) id 13RJ04-0004sp-00; Tue, 22 Aug 2000 22:42:17 +0400 Content-Length: 28940 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.4.0.FreeBSD:000822224421:1773=_" Date: Tue, 22 Aug 2000 22:44:21 +0400 (MSD) Reply-To: diwil@dataart.com From: dimmy the wild To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Subject: fm 801 sound Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.0.FreeBSD:000822224421:1773=_ Content-Type: text/plain; charset=KOI8-R Fellows, Ok, this is a working edition of the fm801 chip driver attached. It tested with play, rvplayer, x11amp. I've found no probs so far. Can anyone put it on the cvs tree? Put it to /usr/src/sys/dev/sound/pci/fms.c To add it to the kernel you have to add the line dev/sound/pci/fms.c optional pcm to the file /usr/src/sys/conf/files and rebuild the kernel... Also the driver is designed to be compiled as a module. Note, that the current edition works only with latest snapshot of the system. To make it working with 4.1 you'll have to apply the following path: ---------------------------------------------------- --- fms.c Tue Aug 22 22:37:07 2000 +++ fms-4.1.c Tue Aug 22 22:39:28 2000 @@ -115,19 +115,10 @@ static int fm801ch_setup(pcm_channel *c); */ -static u_int32_t fmts[] = { - AFMT_U8, - AFMT_STEREO | AFMT_U8, - AFMT_S16_LE, - AFMT_STEREO | AFMT_S16_LE, /* - AFMT_STEREO | (AFMT_S16_LE | AFMT_S16_BE | AFMT_U16_LE | AFMT_U16_BE), - (AFMT_S16_LE | AFMT_S16_BE | AFMT_U16_LE | AFMT_U16_BE), */ - 0 -}; - static pcmchan_caps fm801ch_caps = { 4000, 48000, - fmts, 0 + AFMT_STEREO | AFMT_U8 | AFMT_S16_LE, + AFMT_STEREO | AFMT_U8 | AFMT_S16_LE }; static pcm_channel fm801_chantemplate = { ----------------------------------------------------- Thanks, Dmitry. -- ********************************************************************** ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ `6_ 6 ) `-. ( ).`-.__.`) DataArt Enterprises, Inc. (_Y_.)' ._ ) `._ `. ``-..-' Serpukhovskaja street, 10 _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia (il),-'' (li),' ((!.-' +7 (812) 3261780, 5552490 ********************************************************************** --_=XFMail.1.4.0.FreeBSD:000822224421:1773=_ Content-Disposition: attachment; filename="fms.c" Content-Transfer-Encoding: base64 Content-Type: application/octet-stream; name=fms.c; SizeOnDisk=19735 LyoKICogQ29weXJpZ2h0IChjKSAyMDAwIERtaXRyeSBEaWNreSBkaXdpbEBkYXRhYXJ0LmNvbQog KiBBbGwgcmlnaHRzIHJlc2VydmVkLgogKgogKiBSZWRpc3RyaWJ1dGlvbiBhbmQgdXNlIGluIHNv dXJjZSBhbmQgYmluYXJ5IGZvcm1zLCB3aXRoIG9yIHdpdGhvdXQKICogbW9kaWZpY2F0aW9uLCBh cmUgcGVybWl0dGVkIHByb3ZpZGVkIHRoYXQgdGhlIGZvbGxvd2luZyBjb25kaXRpb25zCiAqIGFy ZSBtZXQ6CiAqIDEuIFJlZGlzdHJpYnV0aW9ucyBvZiBzb3VyY2UgY29kZSBtdXN0IHJldGFpbiB0 aGUgYWJvdmUgY29weXJpZ2h0CiAqICAgIG5vdGljZSwgdGhpcyBsaXN0IG9mIGNvbmRpdGlvbnMg YW5kIHRoZSBmb2xsb3dpbmcgZGlzY2xhaW1lci4KICogMi4gUmVkaXN0cmlidXRpb25zIGluIGJp bmFyeSBmb3JtIG11c3QgcmVwcm9kdWNlIHRoZSBhYm92ZSBjb3B5cmlnaHQKICogICAgbm90aWNl LCB0aGlzIGxpc3Qgb2YgY29uZGl0aW9ucyBhbmQgdGhlIGZvbGxvd2luZyBkaXNjbGFpbWVyIGlu IHRoZQogKiAgICBkb2N1bWVudGF0aW9uIGFuZC9vciBvdGhlciBtYXRlcmlhbHMgcHJvdmlkZWQg d2l0aCB0aGUgZGlzdHJpYnV0aW9uLgogKgogKiBUSElTIFNPRlRXQVJFIElTIFBST1ZJREVEIEJZ IFRIRSBBVVRIT1IgQU5EIENPTlRSSUJVVE9SUyBgQVMgSVMnJyBBTkQKICogQU5ZIEVYUFJFU1Mg T1IgSU1QTElFRCBXQVJSQU5USUVTLCBJTkNMVURJTkcsIEJVVCBOT1QgTElNSVRFRCBUTywgVEhF CiAqIElNUExJRUQgV0FSUkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkgQU5EIEZJVE5FU1MgRk9S IEEgUEFSVElDVUxBUiBQVVJQT1NFCiAqIEFSRSBESVNDTEFJTUVELiAgSU4gTk8gRVZFTlQgU0hB TEwgVEhFIEFVVEhPUiBPUiBDT05UUklCVVRPUlMgQkUgTElBQkxFCiAqIEZPUiBBTlkgRElSRUNU LCBJTkRJUkVDVCwgSU5DSURFTlRBTCwgU1BFQ0lBTCwgRVhFTVBMQVJZLCBPUiBDT05TRVFVRU5U SUFMCiAqIERBTUFHRVMgKElOQ0xVRElORywgQlVUIE5PVCBMSU1JVEVEIFRPLCBQUk9DVVJFTUVO VCBPRiBTVUJTVElUVVRFIEdPT0RTCiAqIE9SIFNFUlZJQ0VTOyBMT1NTIE9GIFVTRSwgREFUQSwg T1IgUFJPRklUUzsgT1IgQlVTSU5FU1MgSU5URVJSVVBUSU9OKQogKiBIT1dFVkVSIENBVVNFRCBB TkQgT04gQU5ZIFRIRU9SWSBPRiBMSUFCSUxJVFksIFdIRVRIRVIgSU4gQ09OVFJBQ1QsIFNUUklD VAogKiBMSUFCSUxJVFksIE9SIFRPUlQgKElOQ0xVRElORyBORUdMSUdFTkNFIE9SIE9USEVSV0lT RSkgQVJJU0lORyBJTiBBTlkgV0FZCiAqIE9VVCBPRiBUSEUgVVNFIE9GIFRISVMgU09GVFdBUkUs IEVWRU4gSUYgQURWSVNFRCBPRiBUSEUgUE9TU0lCSUxJVFkgT0YKICogU1VDSCBEQU1BR0UuCiAq CiAqICRJZCQKICovCgojaW5jbHVkZSA8ZGV2L3NvdW5kL3BjbS9zb3VuZC5oPgojaW5jbHVkZSA8 ZGV2L3NvdW5kL3BjbS9hYzk3Lmg+CiNpbmNsdWRlIDxwY2kvcGNpcmVnLmg+CiNpbmNsdWRlIDxw Y2kvcGNpdmFyLmg+CgojZGVmaW5lIFBDSV9WRU5ET1JfRk9SVEVNRURJQQkweDEzMTkKI2RlZmlu ZSBQQ0lfREVWSUNFX0ZPUlRFTUVESUExCTB4MDgwMTEzMTkKI2RlZmluZSBQQ0lfREVWSUNFX0ZP UlRFTUVESUEyCTB4MDgwMjEzMTkJLyogPz8/IGhhdmUgbm8gaWRlYSB3aGF0J3MgdGhpcy4uLiAq LwoKI2RlZmluZSBGTV9QQ01fVk9MVU1FICAgICAgICAgICAweDAwCiNkZWZpbmUgRk1fRk1fVk9M VU1FICAgICAgICAgICAgMHgwMgojZGVmaW5lIEZNX0kyU19WT0xVTUUgICAgICAgICAgIDB4MDQK I2RlZmluZSBGTV9SRUNPUkRfU09VUkNFICAgICAgICAweDA2CgojZGVmaW5lIEZNX1BMQVlfQ1RM ICAgICAgICAgICAgIDB4MDgKI2RlZmluZSAgRk1fUExBWV9SQVRFX01BU0sgICAgICAgICAgICAg IDB4MGYwMAojZGVmaW5lICBGTV9QTEFZX0JVRjFfTEFTVCAgICAgICAgICAgICAgMHgwMDAxCiNk ZWZpbmUgIEZNX1BMQVlfQlVGMl9MQVNUICAgICAgICAgICAgICAweDAwMDIKI2RlZmluZSAgRk1f UExBWV9TVEFSVCAgICAgICAgICAgICAgICAgIDB4MDAyMAojZGVmaW5lICBGTV9QTEFZX1BBVVNF ICAgICAgICAgICAgICAgICAgMHgwMDQwCiNkZWZpbmUgIEZNX1BMQVlfU1RPUE5PVyAgICAgICAg ICAgICAgICAweDAwODAKI2RlZmluZSAgRk1fUExBWV8xNkJJVCAgICAgICAgICAgICAgICAgIDB4 NDAwMAojZGVmaW5lICBGTV9QTEFZX1NURVJFTyAgICAgICAgICAgICAgICAgMHg4MDAwCgojZGVm aW5lIEZNX1BMQVlfRE1BTEVOICAgICAgICAgIDB4MGEKI2RlZmluZSBGTV9QTEFZX0RNQUJVRjEg ICAgICAgICAweDBjCiNkZWZpbmUgRk1fUExBWV9ETUFCVUYyICAgICAgICAgMHgxMAoKCiNkZWZp bmUgRk1fUkVDX0NUTCAgICAgICAgICAgICAgMHgxNAojZGVmaW5lICBGTV9SRUNfUkFURV9NQVNL ICAgICAgICAgICAgICAgMHgwZjAwCiNkZWZpbmUgIEZNX1JFQ19CVUYxX0xBU1QgICAgICAgICAg ICAgICAweDAwMDEKI2RlZmluZSAgRk1fUkVDX0JVRjJfTEFTVCAgICAgICAgICAgICAgIDB4MDAw MgojZGVmaW5lICBGTV9SRUNfU1RBUlQgICAgICAgICAgICAgICAgICAgMHgwMDIwCiNkZWZpbmUg IEZNX1JFQ19QQVVTRSAgICAgICAgICAgICAgICAgICAweDAwNDAKI2RlZmluZSAgRk1fUkVDX1NU T1BOT1cgICAgICAgICAgICAgICAgIDB4MDA4MAojZGVmaW5lICBGTV9SRUNfMTZCSVQgICAgICAg ICAgICAgICAgICAgMHg0MDAwCiNkZWZpbmUgIEZNX1JFQ19TVEVSRU8gICAgICAgICAgICAgICAg ICAweDgwMDAKCgojZGVmaW5lIEZNX1JFQ19ETUFMRU4gICAgICAgICAgIDB4MTYKI2RlZmluZSBG TV9SRUNfRE1BQlVGMSAgICAgICAgICAweDE4CiNkZWZpbmUgRk1fUkVDX0RNQUJVRjIgICAgICAg ICAgMHgxYwoKI2RlZmluZSBGTV9DT0RFQ19DVEwgICAgICAgICAgICAweDIyCiNkZWZpbmUgRk1f Vk9MVU1FICAgICAgICAgICAgICAgMHgyNgojZGVmaW5lICBGTV9WT0xVTUVfTVVURSAgICAgICAg ICAgICAgICAgMHg4MDAwCgojZGVmaW5lIEZNX0NPREVDX0NNRCAgICAgICAgICAgIDB4MmEKI2Rl ZmluZSAgRk1fQ09ERUNfQ01EX1JFQUQgICAgICAgICAgICAgIDB4MDA4MAojZGVmaW5lICBGTV9D T0RFQ19DTURfVkFMSUQgICAgICAgICAgICAgMHgwMTAwCiNkZWZpbmUgIEZNX0NPREVDX0NNRF9C VVNZICAgICAgICAgICAgICAweDAyMDAKCiNkZWZpbmUgRk1fQ09ERUNfREFUQSAgICAgICAgICAg MHgyYwoKI2RlZmluZSBGTV9JT19DVEwgICAgICAgICAgICAgICAweDUyCiNkZWZpbmUgRk1fQ0FS RF9DVEwgICAgICAgICAgICAgMHg1NAoKI2RlZmluZSBGTV9JTlRNQVNLICAgICAgICAgICAgICAw eDU2CiNkZWZpbmUgIEZNX0lOVE1BU0tfUExBWSAgICAgICAgICAgICAgICAweDAwMDEKI2RlZmlu ZSAgRk1fSU5UTUFTS19SRUMgICAgICAgICAgICAgICAgIDB4MDAwMgojZGVmaW5lICBGTV9JTlRN QVNLX1ZPTCAgICAgICAgICAgICAgICAgMHgwMDQwCiNkZWZpbmUgIEZNX0lOVE1BU0tfTVBVICAg ICAgICAgICAgICAgICAweDAwODAKCiNkZWZpbmUgRk1fSU5UU1RBVFVTICAgICAgICAgICAgMHg1 YQojZGVmaW5lICBGTV9JTlRTVEFUVVNfUExBWSAgICAgICAgICAgICAgMHgwMTAwCiNkZWZpbmUg IEZNX0lOVFNUQVRVU19SRUMgICAgICAgICAgICAgICAweDAyMDAKI2RlZmluZSAgRk1fSU5UU1RB VFVTX1ZPTCAgICAgICAgICAgICAgIDB4NDAwMAojZGVmaW5lICBGTV9JTlRTVEFUVVNfTVBVICAg ICAgICAgICAgICAgMHg4MDAwCgojZGVmaW5lIEZNODAxX0JVRkZTSVpFIDEwMjQqNAkvKiBPdGhl ciB2YWx1ZXMgZG8gbm90IHdvcmshISEgKi8KCi8qIGRlYnVnIHB1cnBvc2VzICovCiNkZWZpbmUg RFBSSU5UCSBpZigwKSBwcmludGYKCgovKiBjaGFubmVsIGludGVyZmFjZSAqLwpzdGF0aWMgdm9p ZCAqZm04MDFjaF9pbml0KHZvaWQgKmRldmluZm8sIHNuZF9kYnVmICpiLCBwY21fY2hhbm5lbCAq YywgaW50IGRpcik7CnN0YXRpYyBpbnQgZm04MDFjaF9zZXRkaXIodm9pZCAqZGF0YSwgaW50IGRp cik7CnN0YXRpYyBpbnQgZm04MDFjaF9zZXRmb3JtYXQodm9pZCAqZGF0YSwgdV9pbnQzMl90IGZv cm1hdCk7CnN0YXRpYyBpbnQgZm04MDFjaF9zZXRzcGVlZCh2b2lkICpkYXRhLCB1X2ludDMyX3Qg c3BlZWQpOwpzdGF0aWMgaW50IGZtODAxY2hfc2V0YmxvY2tzaXplKHZvaWQgKmRhdGEsIHVfaW50 MzJfdCBibG9ja3NpemUpOwpzdGF0aWMgaW50IGZtODAxY2hfdHJpZ2dlcih2b2lkICpkYXRhLCBp bnQgZ28pOwpzdGF0aWMgaW50IGZtODAxY2hfZ2V0cHRyKHZvaWQgKmRhdGEpOwpzdGF0aWMgcGNt Y2hhbl9jYXBzICpmbTgwMWNoX2dldGNhcHModm9pZCAqZGF0YSk7Ci8qCnN0YXRpYyBpbnQgZm04 MDFjaF9zZXR1cChwY21fY2hhbm5lbCAqYyk7CiovCgpzdGF0aWMgdV9pbnQzMl90IGZtdHNbXSA9 IHsKCUFGTVRfVTgsCglBRk1UX1NURVJFTyB8IEFGTVRfVTgsCglBRk1UX1MxNl9MRSwKCUFGTVRf U1RFUkVPIHwgQUZNVF9TMTZfTEUsIC8qCglBRk1UX1NURVJFTyB8IChBRk1UX1MxNl9MRSB8IEFG TVRfUzE2X0JFIHwgQUZNVF9VMTZfTEUgfCBBRk1UX1UxNl9CRSksCgkoQUZNVF9TMTZfTEUgfCBB Rk1UX1MxNl9CRSB8IEFGTVRfVTE2X0xFIHwgQUZNVF9VMTZfQkUpLCAqLwoJMAp9OwoKc3RhdGlj IHBjbWNoYW5fY2FwcyBmbTgwMWNoX2NhcHMgPSB7Cgk0MDAwLCA0ODAwMCwKCWZtdHMsIDAKfTsK ICAgICAgICAgICAgICAgIApzdGF0aWMgcGNtX2NoYW5uZWwgZm04MDFfY2hhbnRlbXBsYXRlID0g ewoJZm04MDFjaF9pbml0LAoJZm04MDFjaF9zZXRkaXIsCglmbTgwMWNoX3NldGZvcm1hdCwKCWZt ODAxY2hfc2V0c3BlZWQsCglmbTgwMWNoX3NldGJsb2Nrc2l6ZSwKCWZtODAxY2hfdHJpZ2dlciwK CWZtODAxY2hfZ2V0cHRyLAoJZm04MDFjaF9nZXRjYXBzLAp9OwoKc3RydWN0IGZtODAxX2luZm87 CgpzdHJ1Y3QgZm04MDFfY2hpbmZvIHsKCXN0cnVjdCBmbTgwMV9pbmZvIAkqcGFyZW50OwoJcGNt X2NoYW5uZWwgCQkqY2hhbm5lbDsKCXNuZF9kYnVmIAkJKmJ1ZmZlcjsKCXVfaW50MzJfdCAJCXNw ZCwgZGlyLCBmbXQ7CS8qIHNwZWVkLCBkaXJlY3Rpb24sIGZvcm1hdCAqLwoJdV9pbnQzMl90CQlz aGlmdDsKfTsKCnN0cnVjdCBmbTgwMV9pbmZvIHsKCWludCAJCQl0eXBlOwoJYnVzX3NwYWNlX3Rh Z190IAlzdDsKCWJ1c19zcGFjZV9oYW5kbGVfdCAJc2g7CglidXNfZG1hX3RhZ190ICAgCXBhcmVu dF9kbWF0OwoJCglkZXZpY2VfdCAJCWRldjsKCWludCAJCQludW07Cgl1X2ludDMyX3QgCQl1bml0 OwoJCglzdHJ1Y3QgcmVzb3VyY2UgCSpyZWcsICppcnE7CglpbnQgICAgICAgICAgICAgCXJlZ3R5 cGUsIHJlZ2lkLCBpcnFpZDsKCXZvaWQgICAgICAgICAgICAJKmloOwoKCXVfaW50MzJfdAkJcGxh eV9mbGlwLAoJCQkJcGxheV9uZXh0YmxrLAoJCQkJcGxheV9zdGFydCwKCQkJCXBsYXlfYmxrc2l6 ZSwKCQkJCXBsYXlfZm10LAoJCQkJcGxheV9zaGlmdCwKCQkJCXBsYXlfc2l6ZTsKCQoJdV9pbnQz Ml90CQlyZWNfZmxpcCwKCQkJCXJlY19uZXh0YmxrLAoJCQkJcmVjX3N0YXJ0LAoJCQkJcmVjX2Js a3NpemUsCgkJCQlyZWNfZm10LAoJCQkJcmVjX3NoaWZ0LAoJCQkJcmVjX3NpemU7CgkKCXN0cnVj dCBmbTgwMV9jaGluZm8gCXBjaCwgcmNoOwp9OwoKCi8qIHNldmVyYWwgcHJvY2VkdXJlcyB0byBy ZWxlYXNlIHRoZSB0aGluZyBwcm9wZXJseSBpZiBjb21waWxlZCBhcyBtb2R1bGUgKi8Kc3RhdGlj IHN0cnVjdCBmbTgwMV9pbmZvICpzYXZlODAxOwpzdHJ1Y3QgZm04MDFfaW5mbyAqZm04MDFfZ2V0 IF9fUCgodm9pZCApKTsKCnN0YXRpYyB2b2lkCmZtODAxX3NhdmUoc3RydWN0IGZtODAxX2luZm8g KmZtODAxKQp7CglzYXZlODAxID0gZm04MDE7Cn0KCnN0cnVjdCBmbTgwMV9pbmZvICoKZm04MDFf Z2V0KHZvaWQgKQp7CglyZXR1cm4gc2F2ZTgwMTsKfQoKLyogQnVzIFJlYWQgLyBXcml0ZSByb3V0 aW5lcyAqLwpzdGF0aWMgdV9pbnQzMl90CmZtODAxX3JkKHN0cnVjdCBmbTgwMV9pbmZvICpmbTgw MSwgaW50IHJlZ25vLCBpbnQgc2l6ZSkKewoJc3dpdGNoKHNpemUpIHsKCWNhc2UgMToKCQlyZXR1 cm4gKGJ1c19zcGFjZV9yZWFkXzEoZm04MDEtPnN0LCBmbTgwMS0+c2gsIHJlZ25vKSk7CgljYXNl IDI6CgkJcmV0dXJuIChidXNfc3BhY2VfcmVhZF8yKGZtODAxLT5zdCwgZm04MDEtPnNoLCByZWdu bykpOwoJY2FzZSA0OgoJCXJldHVybiAoYnVzX3NwYWNlX3JlYWRfNChmbTgwMS0+c3QsIGZtODAx LT5zaCwgcmVnbm8pKTsKCWRlZmF1bHQ6CgkJcmV0dXJuIDB4ZmZmZmZmZmY7Cgl9Cn0KCnN0YXRp YyB2b2lkCmZtODAxX3dyKHN0cnVjdCBmbTgwMV9pbmZvICpmbTgwMSwgaW50IHJlZ25vLCB1X2lu dDMyX3QgZGF0YSwgaW50IHNpemUpCnsKCXN3aXRjaChzaXplKSB7CgljYXNlIDE6CgkJcmV0dXJu IGJ1c19zcGFjZV93cml0ZV8xKGZtODAxLT5zdCwgZm04MDEtPnNoLCByZWdubywgZGF0YSk7Cglj YXNlIDI6CgkJcmV0dXJuIGJ1c19zcGFjZV93cml0ZV8yKGZtODAxLT5zdCwgZm04MDEtPnNoLCBy ZWdubywgZGF0YSk7CgljYXNlIDQ6CgkJcmV0dXJuIGJ1c19zcGFjZV93cml0ZV80KGZtODAxLT5z dCwgZm04MDEtPnNoLCByZWdubywgZGF0YSk7CglkZWZhdWx0OgoJCXJldHVybjsKCX0KfQoKLyoK ICogIGFjOTcgY29kZWMgcm91dGluZXMKICovCiNkZWZpbmUgVElNTyA1MApzdGF0aWMgdV9pbnQz Ml90CmZtODAxX3JkY2Qodm9pZCAqZGV2aW5mbywgaW50IHJlZ25vKQp7CglzdHJ1Y3QgZm04MDFf aW5mbyAqZm04MDEgPSAoc3RydWN0IGZtODAxX2luZm8gKilkZXZpbmZvOwoJaW50IGk7CgkKCWZv ciAoaSA9IDA7IGkgPCBUSU1PICYmIGZtODAxX3JkKGZtODAxLEZNX0NPREVDX0NNRCwyKSAmIEZN X0NPREVDX0NNRF9CVVNZOyBpKyspIHsKCQlERUxBWSgxMDAwMCk7CgkJRFBSSU5UKCJmbTgwMSBy ZGNkOiAxIC0gREVMQVlcbiIpOwoJfQoJaWYgKGkgPj0gVElNTykgewoJCXByaW50ZigiZm04MDEg cmRjZDogY29kZWMgYnVzeVxuIik7CgkJcmV0dXJuIDA7Cgl9CgkKCWZtODAxX3dyKGZtODAxLEZN X0NPREVDX0NNRCwgcmVnbm98Rk1fQ09ERUNfQ01EX1JFQUQsMik7CgoJZm9yIChpID0gMDsgaSA8 IFRJTU8gJiYgIShmbTgwMV9yZChmbTgwMSxGTV9DT0RFQ19DTUQsMikgJiBGTV9DT0RFQ19DTURf VkFMSUQpOyBpKyspCgl7CgkJREVMQVkoMTAwMDApOwoJCURQUklOVCgiZm04MDEgcmRjZDogMiAt IERFTEFZXG4iKTsKCX0KCWlmIChpID49IFRJTU8pIHsKCQlwcmludGYoImZtODAxIHJkY2Q6IHdy aXRlIGNvZGVjIGludmFsaWRcbiIpOwoJCXJldHVybiAwOwoJfQoJCQoJcmV0dXJuIGZtODAxX3Jk KGZtODAxLEZNX0NPREVDX0RBVEEsMik7Cn0KCnN0YXRpYyB2b2lkCmZtODAxX3dyY2Qodm9pZCAq ZGV2aW5mbywgaW50IHJlZ25vLCB1X2ludDMyX3QgZGF0YSkKewoJc3RydWN0IGZtODAxX2luZm8g KmZtODAxID0gKHN0cnVjdCBmbTgwMV9pbmZvICopZGV2aW5mbzsKCWludCBpOwoJCglEUFJJTlQo ImZtODAxX3dyY2QgcmVnIDB4JXggdmFsIDB4JXhcbiIscmVnbm8sIGRhdGEpOwovKgkKCWlmKHJl Z25vID09IEFDOTdfUkVHX1JFQ1NFTCkJcmV0dXJuOwoqLwkKCS8qIFBvbGwgdW50aWwgY29kZWMg aXMgcmVhZHkgKi8KCWZvciAoaSA9IDA7IGkgPCBUSU1PICYmIGZtODAxX3JkKGZtODAxLEZNX0NP REVDX0NNRCwyKSAmIEZNX0NPREVDX0NNRF9CVVNZOyBpKyspIHsKCQlERUxBWSgxMDAwMCk7CgkJ RFBSSU5UKCJmbTgwMSByZGNkOiAxIC0gREVMQVlcbiIpOwoJfQoJaWYgKGkgPj0gVElNTykgewoJ CXByaW50ZigiZm04MDEgd3JjZDogcmVhZCBjb2RlYyBidXN5XG4iKTsKCQlyZXR1cm47Cgl9CgkK CWZtODAxX3dyKGZtODAxLEZNX0NPREVDX0RBVEEsZGF0YSwgMik7CglmbTgwMV93cihmbTgwMSxG TV9DT0RFQ19DTUQsIHJlZ25vLDIpOwoJCgkvKiB3YWl0IHVudGlsIGNvZGVjIGlzIHJlYWR5ICov Cglmb3IgKGkgPSAwOyBpIDwgVElNTyAmJiBmbTgwMV9yZChmbTgwMSxGTV9DT0RFQ19DTUQsMikg JiBGTV9DT0RFQ19DTURfQlVTWTsgaSsrKSB7CgkJREVMQVkoMTAwMDApOwoJCURQUklOVCgiZm04 MDEgd3JjZDogMiAtIERFTEFZXG4iKTsKCX0KCWlmIChpID49IFRJTU8pIHsKCQlwcmludGYoImZt ODAxIHdyY2Q6IHJlYWQgY29kZWMgYnVzeVxuIik7CgkJcmV0dXJuOwoJfQoJRFBSSU5UKCJmbTgw MSB3cmNkIHJlbGVhc2UgcmVnIDB4JXggdmFsIDB4JXhcbiIscmVnbm8sIGRhdGEpOwoJcmV0dXJu Owp9CgovKiAKICogVGhlIGludGVycnVwdCBoYW5kbGVyIAogKi8Kc3RhdGljIHZvaWQKZm04MDFf aW50cih2b2lkICpwKQp7CglzdHJ1Y3QgZm04MDFfaW5mbyAJKmZtODAxID0gKHN0cnVjdCBmbTgw MV9pbmZvICopcDsKCXVfaW50MzJfdCAgICAgICAJaW50c3JjID0gZm04MDFfcmQoZm04MDEsIEZN X0lOVFNUQVRVUywgMik7CglzdHJ1Y3QgZm04MDFfY2hpbmZvCSpjaCA9ICYoZm04MDEtPnBjaCk7 CglzbmRfZGJ1ZiAJCSpiID0gY2gtPmJ1ZmZlcjsKCQoJRFBSSU5UKCJcbmZtODAxX2ludHIgaW50 c3JjIDB4JXggIiwgaW50c3JjKTsKCURQUklOVCgicnAgJWQsIHJsICVkLCBmcCAlZCBmbCAlZCwg c2l6ZT0lZFxuIiwKCQliLT5ycCxiLT5ybCwgYi0+ZnAsYi0+ZmwsIGItPmJsa3N6KTsKCQkKCWlm KGludHNyYyAmIEZNX0lOVFNUQVRVU19QTEFZKSB7CgkJZm04MDEtPnBsYXlfZmxpcCsrOwoJCWlm KGZtODAxLT5wbGF5X2ZsaXAgJiAxKSB7CgkJCWZtODAxX3dyKGZtODAxLCBGTV9QTEFZX0RNQUJV RjEsIGZtODAxLT5wbGF5X3N0YXJ0LDQpOwoJCX0gZWxzZQoJCQlmbTgwMV93cihmbTgwMSwgRk1f UExBWV9ETUFCVUYyLCBmbTgwMS0+cGxheV9uZXh0YmxrLDQpOwoJCWNobl9pbnRyKGZtODAxLT5w Y2guY2hhbm5lbCk7Cgl9CgkKCWlmKGludHNyYyAmIEZNX0lOVFNUQVRVU19SRUMpIHsKCQlmbTgw MS0+cmVjX2ZsaXArKzsKCQlpZihmbTgwMS0+cmVjX2ZsaXAgJiAxKSB7CgkJCWZtODAxX3dyKGZt ODAxLCBGTV9SRUNfRE1BQlVGMSwgZm04MDEtPnJlY19zdGFydCw0KTsKCQl9IGVsc2UKCQkJZm04 MDFfd3IoZm04MDEsIEZNX1JFQ19ETUFCVUYyLCBmbTgwMS0+cmVjX25leHRibGssNCk7CgkJY2hu X2ludHIoZm04MDEtPnJjaC5jaGFubmVsKTsKCX0KCQoJaWYgKCBpbnRzcmMgJiBGTV9JTlRTVEFU VVNfTVBVICkgewoJCS8qIFRoaXMgaXMgYSBUT0RPaXNoIHRoaW5nLi4uICovCgkJZm04MDFfd3Io Zm04MDEsIEZNX0lOVFNUQVRVUywgaW50c3JjICYgRk1fSU5UU1RBVFVTX01QVSwyKTsKCX0KCQoJ aWYgKCBpbnRzcmMgJiBGTV9JTlRTVEFUVVNfVk9MICkgewoJCS8qIFRoaXMgaXMgYSBUT0RPaXNo IHRoaW5nLi4uICovCgkJZm04MDFfd3IoZm04MDEsIEZNX0lOVFNUQVRVUywgaW50c3JjICYgRk1f SU5UU1RBVFVTX1ZPTCwyKTsKCX0KCQoJRFBSSU5UKCJmbTgwMV9pbnRyIGNsZWFyXG5cbiIpOwoJ Zm04MDFfd3IoZm04MDEsIEZNX0lOVFNUQVRVUywgaW50c3JjICYgKEZNX0lOVFNUQVRVU19QTEFZ IHwgRk1fSU5UU1RBVFVTX1JFQyksIDIpOwp9CgovKgogKiAgSW5pdCByb3V0aW5lIGlzIHRha2Vu IGZyb20gYW4gb3JpZ2luYWwgTmV0QlNEIGRyaXZlcgogKi8Kc3RhdGljIGludApmbTgwMV9pbml0 KHN0cnVjdCBmbTgwMV9pbmZvICpmbTgwMSkKewoJdV9pbnQzMl90IGsxOwoJCgkvKiByZXNldCBj b2RlYyAqLwoJZm04MDFfd3IoZm04MDEsIEZNX0NPREVDX0NUTCwgMHgwMDIwLDIpOwoJREVMQVko MTAwMDAwKTsKCWZtODAxX3dyKGZtODAxLCBGTV9DT0RFQ19DVEwsIDB4MDAwMCwyKTsKCURFTEFZ KDEwMDAwMCk7CgkKCWZtODAxX3dyKGZtODAxLCBGTV9QQ01fVk9MVU1FLCAweDA4MDgsMik7Cglm bTgwMV93cihmbTgwMSwgRk1fRk1fVk9MVU1FLCAweDA4MDgsMik7CglmbTgwMV93cihmbTgwMSwg Rk1fSTJTX1ZPTFVNRSwgMHgwODA4LDIpOwoJCglmbTgwMV93cigodm9pZCAqKWZtODAxLCBGTV9S RUNPUkRfU09VUkNFLCAweDAwMDAsMik7CgkKCS8qIFVubWFzayBwbGF5YmFjaywgcmVjb3JkIGFu ZCBtcHUgaW50ZXJydXB0cywgbWFzayB0aGUgcmVzdCAqLwoJazEgPSBmbTgwMV9yZCgodm9pZCAq KWZtODAxLCBGTV9JTlRNQVNLLDIpOwoJZm04MDFfd3IoZm04MDEsIEZNX0lOVE1BU0ssCgkJKGsx ICYgfihGTV9JTlRNQVNLX1BMQVkgfCBGTV9JTlRNQVNLX1JFQyB8IEZNX0lOVE1BU0tfTVBVKSkg fAoJCUZNX0lOVE1BU0tfVk9MLDIpOwoJZm04MDFfd3IoZm04MDEsIEZNX0lOVFNUQVRVUywKCQlG TV9JTlRTVEFUVVNfUExBWSB8IEZNX0lOVFNUQVRVU19SRUMgfCBGTV9JTlRTVEFUVVNfTVBVIHwK CQlGTV9JTlRTVEFUVVNfVk9MLDIpOwoJCglEUFJJTlQoIkZNODAxIGluaXQgT2tcbiIpOwoJcmV0 dXJuIDA7Cn0KCnN0YXRpYyBpbnQKZm04MDFfcGNpX2F0dGFjaChkZXZpY2VfdCBkZXYpCnsKCXNu ZGRldl9pbmZvIAkJKmQ7Cgl1X2ludDMyX3QgCQlkYXRhOwoJc3RydWN0IGFjOTdfaW5mbyAJKmNv ZGVjOwoJc3RydWN0IGZtODAxX2luZm8gCSpmbTgwMTsKCWludCAJCQlpOwoJaW50IAkJCW1hcHBl ZCA9IDA7CgljaGFyIAkJCXN0YXR1c1tTTkRfU1RBVFVTTEVOXTsKCQoJZCA9IGRldmljZV9nZXRf c29mdGMoZGV2KTsKCWlmICgoZm04MDEgPSAoc3RydWN0IGZtODAxX2luZm8gKiltYWxsb2Moc2l6 ZW9mKCpmbTgwMSksTV9ERVZCVUYsIE1fTk9XQUlUKSkgPT0gTlVMTCkgewoJCWRldmljZV9wcmlu dGYoZGV2LCAiY2Fubm90IGFsbG9jYXRlIHNvZnRjXG4iKTsKCQlyZXR1cm4gRU5YSU87Cgl9CgkK CWJ6ZXJvKGZtODAxLCBzaXplb2YoKmZtODAxKSk7CglmbTgwMS0+dHlwZSA9IHBjaV9nZXRfZGV2 aWQoZGV2KTsKCQoJZGF0YSA9IHBjaV9yZWFkX2NvbmZpZyhkZXYsIFBDSVJfQ09NTUFORCwgMik7 CglkYXRhIHw9IChQQ0lNX0NNRF9QT1JURU58UENJTV9DTURfTUVNRU58UENJTV9DTURfQlVTTUFT VEVSRU4pOwoJcGNpX3dyaXRlX2NvbmZpZyhkZXYsIFBDSVJfQ09NTUFORCwgZGF0YSwgMik7Cglk YXRhID0gcGNpX3JlYWRfY29uZmlnKGRldiwgUENJUl9DT01NQU5ELCAyKTsKCQoJZm9yIChpID0g MDsgKG1hcHBlZCA9PSAwKSAmJiAoaSA8IFBDSV9NQVhNQVBTXzApOyBpKyspIHsKCQlmbTgwMS0+ cmVnaWQgPSBQQ0lSX01BUFMgKyBpKjQ7CgkJZm04MDEtPnJlZ3R5cGUgPSBTWVNfUkVTX01FTU9S WTsKCQlmbTgwMS0+cmVnID0gYnVzX2FsbG9jX3Jlc291cmNlKGRldiwgZm04MDEtPnJlZ3R5cGUs ICZmbTgwMS0+cmVnaWQsCgkJCQkJCTAsIH4wLCAxLCBSRl9BQ1RJVkUpOwoJCWlmKCFmbTgwMS0+ cmVnKQoJCXsKCQkJZm04MDEtPnJlZ3R5cGUgPSBTWVNfUkVTX0lPUE9SVDsKCQkJZm04MDEtPnJl ZyA9IGJ1c19hbGxvY19yZXNvdXJjZShkZXYsIGZtODAxLT5yZWd0eXBlLCAmZm04MDEtPnJlZ2lk LAoJCQkJCQkwLCB+MCwgMSwgUkZfQUNUSVZFKTsKCQl9CgkJCgkJaWYoZm04MDEtPnJlZykgewoJ CQlmbTgwMS0+c3QgPSBybWFuX2dldF9idXN0YWcoZm04MDEtPnJlZyk7CgkJCWZtODAxLT5zaCA9 IHJtYW5fZ2V0X2J1c2hhbmRsZShmbTgwMS0+cmVnKTsKCQkJbWFwcGVkKys7CgkJfQoJfQoKCWlm IChtYXBwZWQgPT0gMCkgewoJCWRldmljZV9wcmludGYoZGV2LCAidW5hYmxlIHRvIG1hcCByZWdp c3RlciBzcGFjZVxuIik7CgkJZ290byBvb3BzOwoJfQoJCglmbTgwMV9pbml0KGZtODAxKTsKCQoJ Y29kZWMgPSBhYzk3X2NyZWF0ZShkZXYsICh2b2lkICopZm04MDEsIE5VTEwsIGZtODAxX3JkY2Qs IGZtODAxX3dyY2QpOwoJaWYgKGNvZGVjID09IE5VTEwpIGdvdG8gb29wczsKCglpZiAobWl4ZXJf aW5pdChkLCAmYWM5N19taXhlciwgY29kZWMpID09IC0xKSBnb3RvIG9vcHM7CgoJZm04MDEtPmly cWlkID0gMDsKCWZtODAxLT5pcnEgPSBidXNfYWxsb2NfcmVzb3VyY2UoZGV2LCBTWVNfUkVTX0lS USwgJmZtODAxLT5pcnFpZCwKCQkJCTAsIH4wLCAxLCBSRl9BQ1RJVkUgfCBSRl9TSEFSRUFCTEUp OwoJaWYgKCFmbTgwMS0+aXJxIHx8CgkJYnVzX3NldHVwX2ludHIoZGV2LCBmbTgwMS0+aXJxLCBJ TlRSX1RZUEVfVFRZLAoJCQkJCWZtODAxX2ludHIsIGZtODAxLCAmZm04MDEtPmloKSkgewoJCWRl dmljZV9wcmludGYoZGV2LCAidW5hYmxlIHRvIG1hcCBpbnRlcnJ1cHRcbiIpOwoJCWdvdG8gb29w czsKCX0KCQoJaWYgKGJ1c19kbWFfdGFnX2NyZWF0ZSgvKnBhcmVudCovTlVMTCwgLyphbGlnbm1l bnQqLzIsIC8qYm91bmRhcnkqLzAsCgkJLypsb3dhZGRyKi9CVVNfU1BBQ0VfTUFYQUREUl8zMkJJ VCwKCQkvKmhpZ2hhZGRyKi9CVVNfU1BBQ0VfTUFYQUREUiwKCQkvKmZpbHRlciovTlVMTCwgLypm aWx0ZXJhcmcqL05VTEwsCgkJLyptYXhzaXplKi9GTTgwMV9CVUZGU0laRSwgLypuc2VnbWVudHMq LzEsIC8qbWF4c2VneiovMHgzZmZmZiwKCQkvKmZsYWdzKi8wLCAmZm04MDEtPnBhcmVudF9kbWF0 KSAhPSAwKSB7CgkJZGV2aWNlX3ByaW50ZihkZXYsICJ1bmFibGUgdG8gY3JlYXRlIGRtYSB0YWdc biIpOwoJCWdvdG8gb29wczsKCX0KCQoJc25wcmludGYoc3RhdHVzLCA2NCwgImF0ICVzIDB4JWx4 IGlycSAlbGQiLAoJCShmbTgwMS0+cmVndHlwZSA9PSBTWVNfUkVTX0lPUE9SVCk/ICJpbyIgOiAi bWVtb3J5IiwKCQlybWFuX2dldF9zdGFydChmbTgwMS0+cmVnKSwgcm1hbl9nZXRfc3RhcnQoZm04 MDEtPmlycSkpOwoKI2RlZmluZSBGTTgwMV9NQVhQTEFZQ0gJMQoJaWYgKHBjbV9yZWdpc3Rlcihk ZXYsIGZtODAxLCBGTTgwMV9NQVhQTEFZQ0gsIDEpKSBnb3RvIG9vcHM7CglwY21fYWRkY2hhbihk ZXYsIFBDTURJUl9QTEFZLCAmZm04MDFfY2hhbnRlbXBsYXRlLCBmbTgwMSk7CglwY21fYWRkY2hh bihkZXYsIFBDTURJUl9SRUMsICZmbTgwMV9jaGFudGVtcGxhdGUsIGZtODAxKTsKCXBjbV9zZXRz dGF0dXMoZGV2LCBzdGF0dXMpOwoKCWZtODAxX3NhdmUoZm04MDEpOwoJcmV0dXJuIDA7CgkKb29w czoJCglwcmludGYoIkZvcnRlIE1lZGlhIEZNODAxIGluaXRpYWxpemF0aW9uIGZhaWxlZFxuIik7 CglpZiAoZm04MDEtPnJlZykgYnVzX3JlbGVhc2VfcmVzb3VyY2UoZGV2LCBmbTgwMS0+cmVndHlw ZSwgZm04MDEtPnJlZ2lkLCBmbTgwMS0+cmVnKTsKCWlmIChmbTgwMS0+aWgpIGJ1c190ZWFyZG93 bl9pbnRyKGRldiwgZm04MDEtPmlycSwgZm04MDEtPmloKTsKCWlmIChmbTgwMS0+aXJxKSBidXNf cmVsZWFzZV9yZXNvdXJjZShkZXYsIFNZU19SRVNfSVJRLCBmbTgwMS0+aXJxaWQsIGZtODAxLT5p cnEpOwoJZnJlZShmbTgwMSwgTV9ERVZCVUYpOwoJcmV0dXJuIEVOWElPOwp9CgpzdGF0aWMgaW50 CmZtODAxX3BjaV9wcm9iZSggZGV2aWNlX3QgZGV2ICkKewoJaW50IGlkOwoJaWYgKChpZCA9IHBj aV9nZXRfZGV2aWQoZGV2KSkgPT0gUENJX0RFVklDRV9GT1JURU1FRElBMSApIHsKCQlkZXZpY2Vf c2V0X2Rlc2MoZGV2LCAiRm9ydGUgTWVkaWEgRk04MDEgQXVkaW8gQ29udHJvbGxlciIpOwoJCXJl dHVybiAwOwoJfQovKgoJaWYgKChpZCA9IHBjaV9nZXRfZGV2aWQoZGV2KSkgPT0gUENJX0RFVklD RV9GT1JURU1FRElBMiApIHsKCQlkZXZpY2Vfc2V0X2Rlc2MoZGV2LCAiRm9ydGUgTWVkaWEgRk04 MDEgSm95c3RpY2sgKE5vdCBTdXBwb3J0ZWQpIik7CgkJcmV0dXJuIEVOWElPOwoJfQoqLwoJcmV0 dXJuIEVOWElPOwp9CgoKCi8qIGNoYW5uZWwgaW50ZXJmYWNlICovCnN0YXRpYyB2b2lkICoKZm04 MDFjaF9pbml0KHZvaWQgKmRldmluZm8sIHNuZF9kYnVmICpiLCBwY21fY2hhbm5lbCAqYywgaW50 IGRpcikKewoJc3RydWN0IGZtODAxX2luZm8gKmZtODAxID0gKHN0cnVjdCBmbTgwMV9pbmZvICop ZGV2aW5mbzsKCXN0cnVjdCBmbTgwMV9jaGluZm8gKmNoID0gKGRpciA9PSBQQ01ESVJfUExBWSk/ ICZmbTgwMS0+cGNoIDogJmZtODAxLT5yY2g7CgkKCURQUklOVCgiZm04MDFjaF9pbml0LCBkaXJl Y3Rpb24gPSAlZFxuIiwgZGlyKTsKCWNoLT5wYXJlbnQgPSBmbTgwMTsKCWNoLT5jaGFubmVsID0g YzsKCWNoLT5idWZmZXIgPSBiOwoJY2gtPmJ1ZmZlci0+YnVmc2l6ZSA9IEZNODAxX0JVRkZTSVpF OwoJY2gtPmRpciA9IGRpcjsKCWlmKCBjaG5fYWxsb2NidWYoY2gtPmJ1ZmZlciwgZm04MDEtPnBh cmVudF9kbWF0KSA9PSAtMSkgcmV0dXJuIE5VTEw7CglyZXR1cm4gKHZvaWQgKiljaDsKfQoKc3Rh dGljIGludApmbTgwMWNoX3NldGRpcih2b2lkICpkYXRhLCBpbnQgZGlyKQp7CglzdHJ1Y3QgZm04 MDFfY2hpbmZvICpjaCA9IGRhdGE7CgljaC0+ZGlyID0gZGlyOwoJcmV0dXJuIDA7Cn0KCnN0YXRp YyBpbnQKZm04MDFjaF9zZXRmb3JtYXQodm9pZCAqZGF0YSwgdV9pbnQzMl90IGZvcm1hdCkKewoJ c3RydWN0IGZtODAxX2NoaW5mbyAqY2ggPSBkYXRhOwoJc3RydWN0IGZtODAxX2luZm8gKmZtODAx ID0gY2gtPnBhcmVudDsKCQoJRFBSSU5UKCJmbTgwMWNoX3NldGZvcm1hdCAweCV4IDogJXMsICVz LCAlcywgJXNcbiIsIGZvcm1hdCwKCQkoZm9ybWF0ICYgQUZNVF9TVEVSRU8pPyJzdGVyZW8iOiJt b25vIiwKCQkoZm9ybWF0ICYgKEFGTVRfUzE2X0xFIHwgQUZNVF9TMTZfQkUgfCBBRk1UX1UxNl9M RSB8IEFGTVRfVTE2X0JFKSkgPyAiMTZiaXQiOiI4Yml0IiwKCQkoZm9ybWF0ICYgQUZNVF9TSUdO RUQpPyAic2lnbmVkIjoidW5zaWduZWQiLAoJCShmb3JtYXQgJiBBRk1UX0JJR0VORElBTik/ImJp Z2VuZGlhaCI6ImxpdHRsZWVuZGlhbiIgKTsKCQoJaWYoY2gtPmRpciA9PSBQQ01ESVJfUExBWSkg ewoJCWZtODAxLT5wbGF5X2ZtdCA9ICAoZm9ybWF0ICYgQUZNVF9TVEVSRU8pPyBGTV9QTEFZX1NU RVJFTyA6IDA7CgkJZm04MDEtPnBsYXlfZm10IHw9IChmb3JtYXQgJiBBRk1UXzE2QklUKSA/IEZN X1BMQVlfMTZCSVQgOiAwOwoJCXJldHVybiAwOwoJfQoJCglpZihjaC0+ZGlyID09IFBDTURJUl9S RUMgKSB7CgkJZm04MDEtPnJlY19mbXQgPSAoZm9ybWF0ICYgQUZNVF9TVEVSRU8pPyBGTV9SRUNf U1RFUkVPOjA7CgkJZm04MDEtPnJlY19mbXQgfD0gKGZvcm1hdCAmIEFGTVRfMTZCSVQpID8gRk1f UExBWV8xNkJJVCA6IDA7CgkJcmV0dXJuIDA7Cgl9CgkKCXJldHVybiAwOwp9CgpzdHJ1Y3QgewoJ aW50IGxpbWl0OwoJaW50IHJhdGU7Cn0gZm04MDFfcmF0ZXNbMTFdID0gewoJeyAgNjYwMCwgIDU1 MDAgfSwgICAgICAgICAKCXsgIDg3NTAsICA4MDAwIH0sICAgICAgICAgCgl7IDEwMjUwLCAgOTYw MCB9LCAgICAgICAgIAoJeyAxMzIwMCwgMTEwMjUgfSwgICAgICAgICAKCXsgMTc1MDAsIDE2MDAw IH0sICAgICAgICAgCgl7IDIwNTAwLCAxOTIwMCB9LCAgICAgICAgIAoJeyAyNjUwMCwgMjIwNTAg fSwgICAgICAgICAKCXsgMzUwMDAsIDMyMDAwIH0sICAgICAgICAgCgl7IDQxMDAwLCAzODQwMCB9 LCAgICAgICAgIAoJeyA0NjAwMCwgNDQxMDAgfSwgICAgICAgICAKCXsgNDgwMDAsIDQ4MDAwIH0s ICAgICAgICAgCi8qIGFueXRoaW5nIGFib3ZlIC0+IDQ4MDAwICovCn07CgpzdGF0aWMgaW50CmZt ODAxY2hfc2V0c3BlZWQodm9pZCAqZGF0YSwgdV9pbnQzMl90IHNwZWVkKQp7CglzdHJ1Y3QgZm04 MDFfY2hpbmZvICpjaCA9IGRhdGE7CglzdHJ1Y3QgZm04MDFfaW5mbyAqZm04MDEgPSBjaC0+cGFy ZW50OwoJcmVnaXN0ZXIgaW50IGk7CgkKCQoJZm9yIChpID0gMDsgaSA8IDEwICYmIGZtODAxX3Jh dGVzW2ldLmxpbWl0IDw9IHNwZWVkOyBpKyspIDsKCQoJaWYoY2gtPmRpciA9PSBQQ01ESVJfUExB WSkgewoJCWZtODAxLT5wY2guc3BkID0gZm04MDFfcmF0ZXNbaV0ucmF0ZTsKCQlmbTgwMS0+cGxh eV9zaGlmdCA9IChpPDw4KTsKCQlmbTgwMS0+cGxheV9zaGlmdCAmPSBGTV9QTEFZX1JBVEVfTUFT SzsKCX0KCQoJaWYoY2gtPmRpciA9PSBQQ01ESVJfUkVDICkgewoJCWZtODAxLT5yY2guc3BkID0g Zm04MDFfcmF0ZXNbaV0ucmF0ZTsKCQlmbTgwMS0+cmVjX3NoaWZ0ID0gKGk8PDgpOwoJCWZtODAx LT5yZWNfc2hpZnQgJj0gRk1fUkVDX1JBVEVfTUFTSzsKCX0KCQoJY2gtPnNwZCA9IGZtODAxX3Jh dGVzW2ldLnJhdGU7CgkKCXJldHVybiBmbTgwMV9yYXRlc1tpXS5yYXRlOwp9CgpzdGF0aWMgaW50 CmZtODAxY2hfc2V0YmxvY2tzaXplKHZvaWQgKmRhdGEsIHVfaW50MzJfdCBibG9ja3NpemUpCnsK CXN0cnVjdCBmbTgwMV9jaGluZm8gKmNoID0gZGF0YTsKCXN0cnVjdCBmbTgwMV9pbmZvICpmbTgw MSA9IGNoLT5wYXJlbnQ7CgkKCWlmKGNoLT5kaXIgPT0gUENNRElSX1BMQVkpIHsKCQlpZihmbTgw MS0+cGxheV9mbGlwKSByZXR1cm4gZm04MDEtPnBsYXlfYmxrc2l6ZTsKCQlmbTgwMS0+cGxheV9i bGtzaXplID0gYmxvY2tzaXplOwoJfQoJCglpZihjaC0+ZGlyID09IFBDTURJUl9SRUMpIHsKCQlp ZihmbTgwMS0+cmVjX2ZsaXApIHJldHVybiBmbTgwMS0+cmVjX2Jsa3NpemU7CgkJZm04MDEtPnJl Y19ibGtzaXplID0gYmxvY2tzaXplOwoJfQoJCglEUFJJTlQoImZtODAxY2hfc2V0YmxvY2tzaXpl ICVkIChkaXIgJWQpXG4iLGJsb2Nrc2l6ZSwgY2gtPmRpcik7CgoJcmV0dXJuIGJsb2Nrc2l6ZTsK fQoKc3RhdGljIGludApmbTgwMWNoX3RyaWdnZXIodm9pZCAqZGF0YSwgaW50IGdvKQp7CglzdHJ1 Y3QgZm04MDFfY2hpbmZvICpjaCA9IGRhdGE7CglzdHJ1Y3QgZm04MDFfaW5mbyAqZm04MDEgPSBj aC0+cGFyZW50OwoJdV9pbnQzMl90IGJhc2VhZGRyID0gdnRvcGh5cyhjaC0+YnVmZmVyLT5idWYp OwoJc25kX2RidWYgKmIgPSBjaC0+YnVmZmVyOwoJdV9pbnQzMl90IGsxOwoJCglEUFJJTlQoImZt ODAxY2hfdHJpZ2dlciBnbyAlZCAsICIsIGdvKTsKCURQUklOVCgicnAgJWQsIHJsICVkLCBmcCAl ZCBmbCAlZCwgZGwgJWQsIGJsa3NpemU9JWRcbiIsCgkJYi0+cnAsYi0+cmwsIGItPmZwLGItPmZs LCBiLT5kbCwgYi0+Ymxrc3opOwoJCglpZiAoZ28gPT0gUENNVFJJR19FTUxETUFXUiB8fCBnbyA9 PSBQQ01UUklHX0VNTERNQVJEKSB7CgkJcmV0dXJuIDA7Cgl9CgkKCWlmIChjaC0+ZGlyID09IFBD TURJUl9QTEFZKSB7CgkJaWYgKGdvID09IFBDTVRSSUdfU1RBUlQpIHsKCQkJCQoJCQlmbTgwMS0+ cGxheV9zdGFydCA9IGJhc2VhZGRyOwoJCQlmbTgwMS0+cGxheV9uZXh0YmxrID0gZm04MDEtPnBs YXlfc3RhcnQgKyBmbTgwMS0+cGxheV9ibGtzaXplOwoJCQlmbTgwMS0+cGxheV9mbGlwID0gMDsK CQkJZm04MDFfd3IoZm04MDEsIEZNX1BMQVlfRE1BTEVOLCBmbTgwMS0+cGxheV9ibGtzaXplIC0g MSwgMik7CgkJCWZtODAxX3dyKGZtODAxLCBGTV9QTEFZX0RNQUJVRjEsZm04MDEtPnBsYXlfc3Rh cnQsNCk7CgkJCWZtODAxX3dyKGZtODAxLCBGTV9QTEFZX0RNQUJVRjIsZm04MDEtPnBsYXlfbmV4 dGJsayw0KTsKCQkJZm04MDFfd3IoZm04MDEsIEZNX1BMQVlfQ1RMLAoJCQkJCUZNX1BMQVlfU1RB UlQgfCBGTV9QTEFZX1NUT1BOT1cgfCBmbTgwMS0+cGxheV9mbXQgfCBmbTgwMS0+cGxheV9zaGlm dCwgCgkJCQkJMiApOwoJCQl9IGVsc2UgewoJCQlmbTgwMS0+cGxheV9mbGlwID0gMDsKCQkJazEg PSBmbTgwMV9yZChmbTgwMSwgRk1fUExBWV9DVEwsMik7CgkJCWZtODAxX3dyKGZtODAxLCBGTV9Q TEFZX0NUTCwKCQkJCShrMSAmIH4oRk1fUExBWV9TVE9QTk9XIHwgRk1fUExBWV9TVEFSVCkpIHwK CQkJCUZNX1BMQVlfQlVGMV9MQVNUIHwgRk1fUExBWV9CVUYyX0xBU1QsIDIgKTsKCQl9Cgl9IGVs c2UgaWYoY2gtPmRpciA9PSBQQ01ESVJfUkVDKSB7CgkJaWYgKGdvID09IFBDTVRSSUdfU1RBUlQp IHsKCQkJZm04MDEtPnJlY19zdGFydCA9IGJhc2VhZGRyOwoJCQlmbTgwMS0+cmVjX25leHRibGsg PSBmbTgwMS0+cmVjX3N0YXJ0ICsgZm04MDEtPnJlY19ibGtzaXplOwoJCQlmbTgwMS0+cmVjX2Zs aXAgPSAwOwoJCQlmbTgwMV93cihmbTgwMSwgRk1fUkVDX0RNQUxFTiwgZm04MDEtPnJlY19ibGtz aXplIC0gMSwgMik7CgkJCWZtODAxX3dyKGZtODAxLCBGTV9SRUNfRE1BQlVGMSxmbTgwMS0+cmVj X3N0YXJ0LDQpOwoJCQlmbTgwMV93cihmbTgwMSwgRk1fUkVDX0RNQUJVRjIsZm04MDEtPnJlY19u ZXh0YmxrLDQpOwoJCQlmbTgwMV93cihmbTgwMSwgRk1fUkVDX0NUTCwgCgkJCQkJRk1fUkVDX1NU QVJUIHwgRk1fUkVDX1NUT1BOT1cgfCBmbTgwMS0+cmVjX2ZtdCB8IGZtODAxLT5yZWNfc2hpZnQs IAoJCQkJCTIgKTsKCQkJfSBlbHNlIHsKCQkJZm04MDEtPnJlY19mbGlwID0gMDsKCQkJazEgPSBm bTgwMV9yZChmbTgwMSwgRk1fUkVDX0NUTCwyKTsKCQkJZm04MDFfd3IoZm04MDEsIEZNX1JFQ19D VEwsCgkJCQkoazEgJiB+KEZNX1JFQ19TVE9QTk9XIHwgRk1fUkVDX1NUQVJUKSkgfAoJCQkJRk1f UkVDX0JVRjFfTEFTVCB8IEZNX1JFQ19CVUYyX0xBU1QsIDIpOwoJCX0KCX0KCQoJcmV0dXJuIDA7 Cn0KCi8qIEFsbW9zdCBBTFNBIGNvcHkgKi8Kc3RhdGljIGludApmbTgwMWNoX2dldHB0cih2b2lk ICpkYXRhKQp7CglzdHJ1Y3QgZm04MDFfY2hpbmZvICpjaCA9IGRhdGE7CglzdHJ1Y3QgZm04MDFf aW5mbyAqZm04MDEgPSBjaC0+cGFyZW50OwoJaW50IHJlc3VsdCA9IDA7CglzbmRfZGJ1ZiAqYiA9 IGNoLT5idWZmZXI7CgkKCWlmIChjaC0+ZGlyID09IFBDTURJUl9QTEFZKSB7CgkJcmVzdWx0ID0g Zm04MDFfcmQoZm04MDEsIAoJCQkoZm04MDEtPnBsYXlfZmxpcCYxKSA/IAoJCQlGTV9QTEFZX0RN QUJVRjI6Rk1fUExBWV9ETUFCVUYxLCA0KSAtIGZtODAxLT5wbGF5X3N0YXJ0OwoJfQoJCglpZiAo Y2gtPmRpciA9PSBQQ01ESVJfUkVDKSB7CgkJcmVzdWx0ID0gZm04MDFfcmQoZm04MDEsCgkJCShm bTgwMS0+cmVjX2ZsaXAmMSkgPwoJCQlGTV9SRUNfRE1BQlVGMjpGTV9SRUNfRE1BQlVGMSwgNCkg LSBmbTgwMS0+cmVjX3N0YXJ0OwoJfSAKCQoJRFBSSU5UKCJmbTgwMWNoX2dldHB0cjolZCwgIHJw ICVkLCBybCAlZCwgZnAgJWQgZmwgJWRcbiIsCgkgICAgICAgICAgICAgICAgcmVzdWx0LCBiLT5y cCxiLT5ybCwgYi0+ZnAsYi0+ZmwpOyAgICAgICAgICAgICAgICAKCglyZXR1cm4gcmVzdWx0Owp9 CgpzdGF0aWMgcGNtY2hhbl9jYXBzICoKZm04MDFjaF9nZXRjYXBzKHZvaWQgKmRhdGEpCnsKCXJl dHVybiAmZm04MDFjaF9jYXBzOwp9CgpzdGF0aWMgaW50CmZtODAxX3BjaV9kZXRhY2goZGV2aWNl X3QgZGV2KQp7CglzdHJ1Y3QgZm04MDFfaW5mbyAqZm04MDEgPSBmbTgwMV9nZXQoKTsKCQoJRFBS SU5UKCJGb3J0ZSBNZWRpYSBGTTgwMSBkZXRhY2hcbiIpOwoKCWlmIChmbTgwMS0+cmVnKSBidXNf cmVsZWFzZV9yZXNvdXJjZShkZXYsIGZtODAxLT5yZWd0eXBlLCBmbTgwMS0+cmVnaWQsIGZtODAx LT5yZWcpOwoJaWYgKGZtODAxLT5paCkgYnVzX3RlYXJkb3duX2ludHIoZGV2LCBmbTgwMS0+aXJx LCBmbTgwMS0+aWgpOwoJaWYgKGZtODAxLT5pcnEpIGJ1c19yZWxlYXNlX3Jlc291cmNlKGRldiwg U1lTX1JFU19JUlEsIGZtODAxLT5pcnFpZCwgZm04MDEtPmlycSk7CglmcmVlKGZtODAxLCBNX0RF VkJVRik7CglyZXR1cm4gMDsJCn0KCnN0YXRpYyBkZXZpY2VfbWV0aG9kX3QgZm04MDFfbWV0aG9k c1tdID0gewoJLyogRGV2aWNlIGludGVyZmFjZSAqLwoJREVWTUVUSE9EKGRldmljZV9wcm9iZSwJ CWZtODAxX3BjaV9wcm9iZSksCglERVZNRVRIT0QoZGV2aWNlX2F0dGFjaCwJZm04MDFfcGNpX2F0 dGFjaCksCglERVZNRVRIT0QoZGV2aWNlX2RldGFjaCwJZm04MDFfcGNpX2RldGFjaCksCgl7IDAs IDB9Cn07CgpzdGF0aWMgZHJpdmVyX3QgZm04MDFfZHJpdmVyID0gewoJInBjbSIsCglmbTgwMV9t ZXRob2RzLAoJc2l6ZW9mKHNuZGRldl9pbmZvKSwKfTsKCnN0YXRpYyBkZXZjbGFzc190IHBjbV9k ZXZjbGFzczsKCkRSSVZFUl9NT0RVTEUoZm04MDEsIHBjaSwgZm04MDFfZHJpdmVyLCBwY21fZGV2 Y2xhc3MsMCwgMCk7Cg== --_=XFMail.1.4.0.FreeBSD:000822224421:1773=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 12:13:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 92AB237B424 for ; Tue, 22 Aug 2000 12:13:52 -0700 (PDT) Received: from softweyr.com ([208.187.122.225]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id NAA17583; Tue, 22 Aug 2000 13:13:19 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39A2D25D.4CC11C6D@softweyr.com> Date: Tue, 22 Aug 2000 13:19:57 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Lemon Cc: seebs@plethora.net, hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... References: <200008221714.e7MHEbL05793@prism.flugsvamp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon wrote: > > In article you write: > >>2. How does the OS manage main memory and does it manage secondary storage > >>to back up main memory. I need on algorithm and one structure to show this > >>management...along with how they relate to the management. > > > >The OS manages main memory by breaking it up into 8 1/2 by 11 sections of bits > >called "pages". (The 1/2 is used for parity.) > > Yes, but this is not portable. For a better fit, the OS should strive > to maintain ISO 216 compliance as well, if possible. There is a kernel option to use A4 pages, IIRC. -- "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 Tue Aug 22 12:16:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 2371437B423 for ; Tue, 22 Aug 2000 12:16:10 -0700 (PDT) Received: from softweyr.com ([208.187.122.225]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id NAA17603; Tue, 22 Aug 2000 13:15:59 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39A2D2FA.46CCCA52@softweyr.com> Date: Tue, 22 Aug 2000 13:22:34 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Oliver Fehr Cc: bliss-s@excite.com, hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fehr wrote: > > I recommend reading "Modern Operating Systems" by Andrew S. Tannenbaum > (Prentice Hall). Though a bit old (1992, I think) it will give you most of > the information you want. The problem with Tannenbaum's book is that it doesn't cover any modern operating systems. Mr. Bliss, once you've finished your research, please write a replacement text that covers Mach (as a starting point), Chorus, Plan9, Spring, and Flux. -- "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 Tue Aug 22 13: 7:22 2000 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 D6F2737B42C for ; Tue, 22 Aug 2000 13:07:14 -0700 (PDT) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13RKKH-0004R1-00 for hackers@freebsd.org; Tue, 22 Aug 2000 20:07:13 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id WAA00503 for hackers@freebsd.org; Tue, 22 Aug 2000 22:07:13 +0200 (CEST) (envelope-from rene) Date: Tue, 22 Aug 2000 22:07:13 +0200 From: Rene de Vries To: hackers@freebsd.org Subject: Panic from within jail Message-ID: <20000822220712.A433@canyon.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hackers, I was playing arnound with jail (mostly to see how/if it worked). After setting up a environment a la jail(8) I started jail. Everything worked fine. When I tried to mount an filesystem via nfs the system paniced. The filesystems physical location is on the same machine as the jail is on. So, in short: telnet river <--- river is the "jail" on my machine "grand" ...login.... $su ... #mount -t nfs grand:/usr/src /usr/src .... ... panic: page fault If there is anything I can do, please let me know. Rene BTW: does this have anything to do with kern/4021, or should I submit a bug? -- Rene de Vries http://www.tcja.nl 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 Tue Aug 22 13:52:13 2000 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 79ACD37B423 for ; Tue, 22 Aug 2000 13:52:07 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13RL1i-0005HM-00; Tue, 22 Aug 2000 20:52:06 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id WAA00671; Tue, 22 Aug 2000 22:52:14 +0200 (CEST) (envelope-from wkb) Date: Tue, 22 Aug 2000 22:52:14 +0200 From: Wilko Bulte To: Rene de Vries Cc: hackers@freebsd.org Subject: Re: Panic from within jail Message-ID: <20000822225214.B616@freebie.demon.nl> References: <20000822220712.A433@canyon.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000822220712.A433@canyon.demon.nl>; from rene@canyon.demon.nl on Tue, Aug 22, 2000 at 10:07:13PM +0200 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 22, 2000 at 10:07:13PM +0200, Rene de Vries wrote: > I was playing arnound with jail (mostly to see how/if it worked). After > setting up a environment a la jail(8) I started jail. Everything worked fine. > > When I tried to mount an filesystem via nfs the system paniced. The > filesystems physical location is on the same machine as the jail is on. > > So, in short: > > telnet river <--- river is the "jail" on my machine "grand" > ...login.... > $su > ... > #mount -t nfs grand:/usr/src /usr/src > .... > ... > panic: page fault > > If there is anything I can do, please let me know. Post the traceback as displayed on the console I guess? And the version of FreeBSD would also help. W/ -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 14:40:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id E9E2637B422 for ; Tue, 22 Aug 2000 14:40:53 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7MLeaT45194; Tue, 22 Aug 2000 14:40:37 -0700 (PDT) Date: Tue, 22 Aug 2000 14:40:36 -0700 (PDT) From: Doug White To: Hajimu UMEMOTO Cc: n@nectar.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Testers wanted: nsswitch In-Reply-To: <20000823.020859.74674005.ume@mahoroba.org> 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, 23 Aug 2000, Hajimu UMEMOTO wrote: > >>>>> On Sat, 19 Aug 2000 16:30:17 -0500 > >>>>> "Jacques A. Vidrine" said: > > n> I've made a port of NetBSD's nsswitch code. This allows one to > n> configure various databases such as passwd(5) to use files, NIS, > n> or Hesiod. > > I like bringing nsswitch into FreeBSD. It will reduce maintainance > cost around resolver related routins. > When I merged KAME effort around fixing DNS query order problem from > NetBSD, I was forced to work with nsswitch -> host.conf issue. I think we all like the semantics, but I recall a large discussion about a year ago that NetBSD's nsswitch is serializing, which for heavy DNS use is a major performance hit. I don't recall if a design ever came out of it. 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 Tue Aug 22 15: 2:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 2A4DB37B43C; Tue, 22 Aug 2000 15:02:15 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA22251; Tue, 22 Aug 2000 15:15:20 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008222215.PAA22251@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Cc: hardware@freebsd.org Subject: Mylex driver, re-update Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Aug 2000 15:15:20 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a pile more testing last night, I've updated the driver for the new Mylex controllers again. This code should now work correctly when loaded at boot time or statically compiled into the kernel, and as a bonus, it ought to work with 4.x systems as well. http://people.freebsd.org/~msmith/RAID/index.html#mylex As usual, success/failure reports would be greatly appreciated. Thanks! -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 15: 6:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 7114D37B43F for ; Tue, 22 Aug 2000 15:06:49 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA22281; Tue, 22 Aug 2000 15:19:27 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008222219.PAA22281@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Katsushi Kobayashi Cc: freebsd-hackers@freebsd.org Subject: Re: IEEE1394 driver system for -current In-reply-to: Your message of "Sat, 19 Aug 2000 19:00:26 +0900." <399E5A33.B552E780@koganei.wide.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Aug 2000 15:19:27 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I announced IEEE1394 device driver on FREENIX'99 (sorry not > on '00). I have caught up -current version at this time. > > The latest -current driver patch can be found at: > > ftp://ftp.uec.ac.jp/pub/firewire/beta/ > > I hope you success to make a kernel on your source tree. Building it was fine. I got a card from CompUSA (yuck!) which uses a slightly different version of the Lynx chipset (TSB12LV23), so I may need a few tiny changes. > The driver function is still limited and may include many > bugs since the driver has been used for specific purrposes, > e.g., the driver have not supported SCSI (CAM) storage on > IEEE1394 and not been complient to loadable kernel module. > However, I think it is better to merge -current on this time and > maintain on it compared with taking a effort in independent. I think that's an excellent idea. > Let me know what shall I do to merge my code. I'd be happy to help you get the code merged and also help with testing etc. To begin with, can you recommend (or warn against) any particular DV hardware? I need at least one working peripheral (I have a 1394 disk device for later, right now I just want something that can show me the adapter working). Once I have the necessary hardware, I can spend a little time looking over your code and then we can get things resolved. I'm terribly sorry it's taken me so long to get to this point. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 17:44:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kwanon.research.canon.com.au (kwanon.research.canon.com.au [203.12.172.254]) by hub.freebsd.org (Postfix) with ESMTP id 4FC2237B43F for ; Tue, 22 Aug 2000 17:44:20 -0700 (PDT) Received: from bellmann.research.canon.com.au (bellmann.research.canon.com.au [10.5.0.3]) by kwanon.research.canon.com.au (Postfix) with ESMTP id 584208A893; Wed, 23 Aug 2000 00:48:34 +0000 (UTC) Received: from elph.research.canon.com.au (elph.research.canon.com.au [203.12.174.253]) by bellmann.research.canon.com.au (Postfix) with ESMTP id 057968B19; Wed, 23 Aug 2000 10:39:24 +1000 (EST) Received: from elph.research.canon.com.au (elph.research.canon.com.au [203.12.174.253]) by elph.research.canon.com.au (Postfix) with ESMTP id 5D433278; Wed, 23 Aug 2000 10:43:44 +1000 (EST) Date: Wed, 23 Aug 2000 10:43:44 +1000 (EST) From: Iain Templeton To: Ustimenko Semen Cc: freebsd-hackers@FreeBSD.org Subject: Re: nullfs patch 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 Sun, 6 Aug 2000, Ustimenko Semen wrote: > Hi! > > Here is a patch, it seems it fix some bugs in nullfs. > At least i was able to make kernel on nullfs mounted > filesystem. > > All results are welcome! > This is pretty good. I have been doing all my port building on a nullfs mounted filesystem for that last week (about 10-20 ports so far I think), and I haven't noticed any problems as yet. It certainly doesn't panic() on mmap() anymore. Patched against null_vnops.c 1.38 (from -stable) cleanly, and works for me so far. I have yet to try fancy things with jail (using say nullfs to mount a ro filesystem that can be shared between different jails for /usr for example). Iain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 19:12: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from reddog.yi.org (ls-tc01-21.nothinbut.net [207.44.35.35]) by hub.freebsd.org (Postfix) with ESMTP id DF61B37B43E for ; Tue, 22 Aug 2000 19:11:52 -0700 (PDT) Received: from reddog.yi.org (localhost [127.0.0.1]) by reddog.yi.org (Postfix) with SMTP id C31F15FA; Tue, 22 Aug 2000 22:18:50 -0500 (EST) Date: Tue, 22 Aug 2000 17:29:45 -0500 From: spectre To: bliss-s@excite.com Cc: hackers@freebsd.org Subject: Re: Advanced OS Questions only you can answer... Message-ID: <20000822172945.A17560@reddog.yi.org> References: <5061190.966950975267.JavaMail.imail@magic.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <5061190.966950975267.JavaMail.imail@magic.excite.com>; from bliss-s@excite.com on Tue, Aug 22, 2000 at 06:29:34AM -0700 Content-Length: 626 Lines: 12 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 22, 2000 at 06:29:34AM -0700, bliss-s@excite.com wrote: > I am stuck between a rock and a hard place. I've been to your website, I've > logged in under deja.news and posted questions, I've emailed several people, > and my Dad even called the BSD 800 number for me and paid a fee to find out > that all my questions are too advanced for their services. The > representative at the 800 number told my Dad that my only hope was to send > this email to you. [...] If you want something with tons of documentation, and something that's a little bit smaller and perhaps easier to understand than FreeBSD, try Minix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 19:16:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.bsdhome.com (unknown [24.25.2.13]) by hub.freebsd.org (Postfix) with ESMTP id E3DC737B423 for ; Tue, 22 Aug 2000 19:16:43 -0700 (PDT) Received: from vger.bsdhome.com (vger [192.168.220.2]) by smtp.bsdhome.com (8.9.3/8.9.3) with ESMTP id WAA12588; Tue, 22 Aug 2000 22:16:37 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: from localhost (bsd@localhost) by vger.bsdhome.com (8.9.3/8.9.3) with ESMTP id WAA10880; Tue, 22 Aug 2000 22:16:36 -0400 (EDT) (envelope-from bsd@vger.bsdhome.com) Date: Tue, 22 Aug 2000 22:16:35 -0400 (EDT) From: Brian Dean To: Wes Peters Cc: Jonathan Lemon , seebs@plethora.net, hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... In-Reply-To: <39A2D25D.4CC11C6D@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 Tue, 22 Aug 2000, Wes Peters wrote: > There is a kernel option to use A4 pages, IIRC. Yes, that's right next DUPLEX option to put data on both sides of the page, thus doubling the capacity. Didn't IBM come up with that just recently? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 22 22:13: 4 2000 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 3FB1637B422 for ; Tue, 22 Aug 2000 22:13:00 -0700 (PDT) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13RSqP-0002Go-00; Wed, 23 Aug 2000 05:12:58 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id HAA01544; Wed, 23 Aug 2000 07:12:25 +0200 (CEST) (envelope-from rene) Date: Wed, 23 Aug 2000 07:12:25 +0200 From: Rene de Vries To: Wilko Bulte Cc: hackers@freebsd.org Subject: Re: Panic from within jail Message-ID: <20000823071225.A1507@canyon.demon.nl> References: <20000822220712.A433@canyon.demon.nl> <20000822225214.B616@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000822225214.B616@freebie.demon.nl>; from wkb@freebie.demon.nl on Tue, Aug 22, 2000 at 10:52:14PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The first time it crashed, it didn't say anything (not even panic) it just rebooted. The second time it said "panic:page fault" and synced the disks but that was it. The version of FreeBSD is 4.1-S as of monday. This morning I tried to reproduce it, but I was not able to. At first I thought it had anything to do with the "route add -host 192.168.1.100 192.168.1.2" (where the .100 is the jail) that I did because I wass clueless why a connection to the jail didn't work. But when I tried to reproduce this this morning the mount command simply returned with "nfs: /usr/src: Operation not permitted", which is ok. I'll try to reproduce this the evening, if I find a way, you'll be the first to know. Rene On Tue, Aug 22, 2000 at 10:52:14PM +0200, Wilko Bulte wrote: > On Tue, Aug 22, 2000 at 10:07:13PM +0200, Rene de Vries wrote: > > > I was playing arnound with jail (mostly to see how/if it worked). After > > setting up a environment a la jail(8) I started jail. Everything worked fine. > > > > When I tried to mount an filesystem via nfs the system paniced. The > > filesystems physical location is on the same machine as the jail is on. > > > > So, in short: > > > > telnet river <--- river is the "jail" on my machine "grand" > > ...login.... > > $su > > ... > > #mount -t nfs grand:/usr/src /usr/src > > .... > > ... > > panic: page fault > > > > If there is anything I can do, please let me know. > > Post the traceback as displayed on the console I guess? And the version > of FreeBSD would also help. > > W/ -- Rene de Vries http://www.tcja.nl 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 Tue Aug 22 23: 6:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 4516837B446 for ; Tue, 22 Aug 2000 23:06:28 -0700 (PDT) Received: from softweyr.com (Foolstrustident!@dyn3.softweyr.com [204.68.178.227]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA18813; Wed, 23 Aug 2000 00:06:24 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39A36B78.EAC2192@softweyr.com> Date: Wed, 23 Aug 2000 00:13:12 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Oliver Fehr Cc: hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... References: <39A2D2FA.46CCCA52@softweyr.com> <00082221322801.26000@yalta.ofehr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fehr wrote: > > On Tue, 22 Aug 2000, Wes Peters wrote: > > Oliver Fehr wrote: > > > > > > I recommend reading "Modern Operating Systems" by Andrew S. Tannenbaum > > > (Prentice Hall). Though a bit old (1992, I think) it will give you most of > > > the information you want. > > > > The problem with Tannenbaum's book is that it doesn't cover any modern > > operating systems. Mr. Bliss, once you've finished your research, please > > write a replacement text that covers Mach (as a starting point), Chorus, > > Plan9, Spring, and Flux. > > > Well, the book covers UNIX and DOS, at least on of which can be considered > a modern operating system. You be the judge which on ... Neither. One is not an operating system, but merely a game loader, and the other is over 30 years old and dates to the days of mechanial tele- types and punched paper tape as input/output devices. If you haven't studied at least two of the above, you have no chance of understanding why UNIX isn't a modern operating system. It is the conceptual parent of all of the above, though. -- "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 Tue Aug 22 23:18:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from inconnu.isu.edu (inconnu.isu.edu [134.50.8.55]) by hub.freebsd.org (Postfix) with ESMTP id 587B937B424 for ; Tue, 22 Aug 2000 23:18:55 -0700 (PDT) Received: from localhost (galt@localhost) by inconnu.isu.edu (8.9.3/8.9.3) with ESMTP id AAA22048; Wed, 23 Aug 2000 00:18:19 -0600 Date: Wed, 23 Aug 2000 00:18:19 -0600 (MDT) From: John Galt To: Wes Peters Cc: Jonathan Lemon , seebs@plethora.net, hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... In-Reply-To: <39A2D25D.4CC11C6D@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 I heard that Jon Johansen hacked the kernel to use Legal as part of his DeCSS work... On Tue, 22 Aug 2000, Wes Peters wrote: > Jonathan Lemon wrote: > > > > In article you write: > > >>2. How does the OS manage main memory and does it manage secondary storage > > >>to back up main memory. I need on algorithm and one structure to show this > > >>management...along with how they relate to the management. > > > > > >The OS manages main memory by breaking it up into 8 1/2 by 11 sections of bits > > >called "pages". (The 1/2 is used for parity.) > > > > Yes, but this is not portable. For a better fit, the OS should strive > > to maintain ISO 216 compliance as well, if possible. > > There is a kernel option to use A4 pages, IIRC. > > -- Artificial intelligence is no match for natural stupidity. Who is John Galt? galt@inconnu.isu.edu, that's who! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 5: 7:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 0E57837B423 for ; Wed, 23 Aug 2000 05:07:48 -0700 (PDT) Received: (qmail 64878 invoked by uid 1001); 23 Aug 2000 12:02:07 -0000 Date: Wed, 23 Aug 2000 15:02:07 +0300 From: Peter Pentchev To: freebsd-hackers@freebsd.org Subject: MFC of sed -E Message-ID: <20000823150207.D63286@ringwraith.office1.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey there, Is there any compelling reason not to merge the extended regexp capabilities of /usr/bin/sed? The patches in the following revisions apply cleanly to RELENG_4's sed (except for the $FreeBSD id's, of course ;), and -E works as expected. src/usr.bin/sed/compile.c 1.14 src/usr.bin/sed/extern.h 1.5 src/usr.bin/sed/main.c 1.10 src/usr.bin/sed/sed.1 1.10 G'luck, Peter -- If you think this sentence is confusing, then change one pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 7:40:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [63.147.8.7]) by hub.freebsd.org (Postfix) with ESMTP id 6918337B423 for ; Wed, 23 Aug 2000 07:40:27 -0700 (PDT) Received: from Barricuda.Catonic.NET (1Cust221.tnt1.huntsville.al.da.uu.net [63.10.51.221]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id JAA19910 for ; Wed, 23 Aug 2000 09:12:27 -0400 Received: from localhost (localhost [127.0.0.1]) by Barricuda.Catonic.NET (8.9.3/8.9.3) with ESMTP id JAA59460 for ; Wed, 23 Aug 2000 09:38:18 -0500 (CDT) (envelope-from kris@barricuda.catonic.net) Date: Wed, 23 Aug 2000 09:38:17 -0500 (CDT) From: Kris Kirby To: hackers@freebsd.org Subject: Location of superblock? Message-ID: X-Tech-Support-Email: bofh@catonic.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a filesystem I am trying to recover (Win2K ate the slice table; I accidentally wiped the disklabel) and need to know the correct location of the superblock in relation to the start of the partition (a la disklabel). Please note: I have the correct superblock, and do not need the alternates. I have already found them. (600MB of text from "fsck -b # -n" run by a shell script that incremented # every loop.) ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 8:17:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id 0B0EE37B423 for ; Wed, 23 Aug 2000 08:17:40 -0700 (PDT) Received: (cpmta 27184 invoked from network); 23 Aug 2000 08:17:31 -0700 Received: from m12hRs4n205.midsouth.rr.com (HELO development1) (24.95.125.205) by smtp.valuedata.net with SMTP; 23 Aug 2000 08:17:31 -0700 X-Sent: 23 Aug 2000 15:17:31 GMT Message-ID: <000901c00d15$014ef540$0200000a@development1> From: "Daryl Chance" To: "FreeBSD Hackers" Subject: 4.1 Release....MIIBUS Date: Wed, 23 Aug 2000 10:15:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I know that in 4.0 Release that miibus was required, though not marked. I noticed that 4.1 Release miibus is still not marked as (required), is it no longer required, or is it still not marked? I ahven't tried compiling it with miibus commented out, I'm just assuming it's still required Thanks, -------------------------------------------------------- | Daryl Chance | I have made this letter longer then | | Valuedata, LLC | usual because I lacked the time to | | Memphis, TN | make it shorter. -- Blaise Pascal | -------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 8:20:22 2000 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 969D437B424 for ; Wed, 23 Aug 2000 08:20:13 -0700 (PDT) Received: from sol.we.lc.ehu.es (sol [158.227.6.42]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA24291 for ; Wed, 23 Aug 2000 17:20:03 +0200 (MET DST) From: Borja Marcos Received: (from borjam@localhost) by sol.we.lc.ehu.es (8.9.1/8.9.1) id RAA06321 for hackers@freebsd.org; Wed, 23 Aug 2000 17:20:03 +0200 (MET DST) Message-Id: <200008231520.RAA06321@sol.we.lc.ehu.es> Subject: Re: Advanced OS Questions only you can answer... To: wes@softweyr.com (Wes Peters) Date: Wed, 23 Aug 100 03:02:23 +0200 (MET DST) In-Reply-To: <39A2D2FA.46CCCA52@softweyr.com> from "Wes Peters" at Aug 22, 0 01:22:34 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Oliver Fehr wrote: > > > > I recommend reading "Modern Operating Systems" by Andrew S. Tannenbaum > > (Prentice Hall). Though a bit old (1992, I think) it will give you most of > > the information you want. > > The problem with Tannenbaum's book is that it doesn't cover any modern > operating systems. Mr. Bliss, once you've finished your research, please > write a replacement text that covers Mach (as a starting point), Chorus, > Plan9, Spring, and Flux. Anyway, it is an excellent theory book. And, once you have read it, you can read documents describing other OSs, like, for example, the articles describing Plan 9. "Modern operating Systems" also covers Amoeba, which is indeed a modern operating system. Plan 9 and Amoeba give you an excellent spectrum on the design of distributed operating systems; both are quite different, with different design goals. Borja. -- *********************************************************************** Borja Marcos * Internet: borjam@we.lc.ehu.es Alangoeta, 11 1 izq * borjamar@sarenet.es 48990 - Algorta (Vizcaya) * borjam@well.com SPAIN * borjam@uninet.edu *********************************************************************** --- 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 Wed Aug 23 8:30:11 2000 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 67F0637B43F for ; Wed, 23 Aug 2000 08:30:04 -0700 (PDT) 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 KAA94357; Wed, 23 Aug 2000 10:30:03 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 23 Aug 2000 10:30:02 -0500 (CDT) From: David Scheidt To: Daryl Chance Cc: FreeBSD Hackers Subject: Re: 4.1 Release....MIIBUS In-Reply-To: <000901c00d15$014ef540$0200000a@development1> 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, 23 Aug 2000, Daryl Chance wrote: :Hi, : :I know that in 4.0 Release that miibus was required, though :not marked. I noticed that 4.1 Release miibus is still not :marked as (required), is it no longer required, or is it still :not marked? I ahven't tried compiling it with miibus commented :out, I'm just assuming it's still required : MIIBUS is only required if you have an ethernet adapter that requires it. If you try to include such a device, and not MIIBUS, I'm not at all suprised that the compile fails. It is certainly possible to build a kernel without MIIBUS, though. None of my fxp(4) equipped machines use it, for instance. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 8:45:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c014.sfo.cp.net (c014-h017.c014.sfo.cp.net [209.228.12.81]) by hub.freebsd.org (Postfix) with SMTP id 16E7437B43F for ; Wed, 23 Aug 2000 08:45:30 -0700 (PDT) Received: (cpmta 26738 invoked from network); 23 Aug 2000 08:45:29 -0700 Received: from m12hRs4n205.midsouth.rr.com (HELO development1) (24.95.125.205) by smtp.valuedata.net with SMTP; 23 Aug 2000 08:45:29 -0700 X-Sent: 23 Aug 2000 15:45:29 GMT Message-ID: <001f01c00d18$e9bfa100$0200000a@development1> From: "Daryl Chance" To: "FreeBSD Hackers" References: Subject: Re: 4.1 Release....MIIBUS Date: Wed, 23 Aug 2000 10:43:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, thanks for clearing this up...I haven't tried it with my realtek cards, but I know the Netgear ones need it :). Thanks again, -------------------------------------------------------- | Daryl Chance | I have made this letter longer then | | Valuedata, LLC | usual because I lacked the time to | | Memphis, TN | make it shorter. -- Blaise Pascal | -------------------------------------------------------- ----- Original Message ----- From: "David Scheidt" To: "Daryl Chance" Cc: "FreeBSD Hackers" Sent: Wednesday, August 23, 2000 10:30 AM Subject: Re: 4.1 Release....MIIBUS > On Wed, 23 Aug 2000, Daryl Chance wrote: > > :Hi, > : > :I know that in 4.0 Release that miibus was required, though > :not marked. I noticed that 4.1 Release miibus is still not > :marked as (required), is it no longer required, or is it still > :not marked? I ahven't tried compiling it with miibus commented > :out, I'm just assuming it's still required > : > > MIIBUS is only required if you have an ethernet adapter that requires it. > If you try to include such a device, and not MIIBUS, I'm not at all suprised > that the compile fails. It is certainly possible to build a kernel without > MIIBUS, though. None of my fxp(4) equipped machines use it, for instance. > > > David > > > > 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 Aug 23 9: 7:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id DD66437B43C for ; Wed, 23 Aug 2000 09:07:35 -0700 (PDT) Received: (qmail 66409 invoked by uid 1001); 23 Aug 2000 16:02:23 -0000 Date: Wed, 23 Aug 2000 19:02:23 +0300 From: Peter Pentchev To: freebsd-hackers@freebsd.org Subject: mount_mfs /var on a diskless workstation Message-ID: <20000823190223.H63286@ringwraith.office1.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, so probably I'm missing something again, like in my previous post about mounting different subdirs in a filesystem (btw thanks to those who replied then, all replies have been most helpful). So.. Is there a way to cleanly shutdown (or reboot) a NFS-rooted workstation? rc.diskless2 MFS-mounts /var, and when init(8) tries to kill the running daemons, the /etc and /var mount_mfs's obstinately and rightly refuse to die - /etc has /etc/ttys in use, and /var has.. lots of files, most notably /var/db/mounttab. As a result, mount_mfs lives, init waits quite a while, tries to kill it with SIGKILL, fails again, and complains, advising a ps axl.. I wonder if there might be some kind of race condition here - some processes that received the SIGTERM, but not quite finished yet - but anyway, just how stupid would it be if I tried to teach the kernel to leave mount_mfs alone on a kill(-1, SIGTERM)? Would this break anything but init on shutdown? G'luck, Peter -- This sentence was in the past tense. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 11:29:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id C3EF637B423 for ; Wed, 23 Aug 2000 11:29:24 -0700 (PDT) Received: (qmail 745744 invoked from network); 23 Aug 2000 18:29:18 -0000 Received: from r121m50.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.50]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 23 Aug 2000 18:29:18 -0000 Message-ID: <39A41897.173F00@cybercable.fr> Date: Wed, 23 Aug 2000 20:31:52 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: sysctl from kernel 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 new to the FreeBSD kernel and I wanted to know what are the good methods to read a sysctl value from the kernel. Is it the same interface as in user-space ? Any help or links to some documentation would be greatly appreciated :) Thanks, Maxime Henrion To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 11:34:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.254]) by hub.freebsd.org (Postfix) with ESMTP id 36C3137B422 for ; Wed, 23 Aug 2000 11:34:25 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA04750; Wed, 23 Aug 2000 20:34:22 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Maxime Henrion Cc: hackers@FreeBSD.ORG Subject: Re: sysctl from kernel In-Reply-To: Your message of "Wed, 23 Aug 2000 20:31:52 +0200." <39A41897.173F00@cybercable.fr> Date: Wed, 23 Aug 2000 20:34:22 +0200 Message-ID: <4748.967055662@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A41897.173F00@cybercable.fr>, Maxime Henrion writes: > Hi, > >I'm new to the FreeBSD kernel and I wanted to know what are the good >methods to read a sysctl value from the kernel. Is it the same interface >as in user-space ? > >Any help or links to some documentation would be greatly appreciated :) Look at the kernel_sysctl() function in src/sys/kern/kern_sysctl.c -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 11:56: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A044837B423 for ; Wed, 23 Aug 2000 11:56:02 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA66623; Wed, 23 Aug 2000 12:56:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA51586; Wed, 23 Aug 2000 12:55:48 -0600 (MDT) Message-Id: <200008231855.MAA51586@harmony.village.org> To: "Daryl Chance" Subject: Re: 4.1 Release....MIIBUS Cc: "FreeBSD Hackers" In-reply-to: Your message of "Wed, 23 Aug 2000 10:15:33 CDT." <000901c00d15$014ef540$0200000a@development1> References: <000901c00d15$014ef540$0200000a@development1> Date: Wed, 23 Aug 2000 12:55:48 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000901c00d15$014ef540$0200000a@development1> "Daryl Chance" writes: : I know that in 4.0 Release that miibus was required, though : not marked. I noticed that 4.1 Release miibus is still not : marked as (required), is it no longer required, or is it still : not marked? I ahven't tried compiling it with miibus commented : out, I'm just assuming it's still required miibus is still required for any ethernet card with a mii. Which is basically all of them produced in the last few years. my trusty ne2000 doesn't need it :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 14: 9: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 8DBFE37B424 for ; Wed, 23 Aug 2000 14:09:05 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id OAA09954; Wed, 23 Aug 2000 14:09:05 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA86366; Wed, 23 Aug 2000 14:09:05 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008232109.OAA86366@bubba.whistle.com> Subject: Re: 4.1 Release....MIIBUS In-Reply-To: <200008231855.MAA51586@harmony.village.org> "from Warner Losh at Aug 23, 2000 12:55:48 pm" To: Warner Losh Date: Wed, 23 Aug 2000 14:09:05 -0700 (PDT) Cc: Daryl Chance , FreeBSD Hackers X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > : not marked. I noticed that 4.1 Release miibus is still not > : marked as (required), is it no longer required, or is it still > : not marked? I ahven't tried compiling it with miibus commented > : out, I'm just assuming it's still required > > miibus is still required for any ethernet card with a mii. Which is > basically all of them produced in the last few years. my trusty > ne2000 doesn't need it :-) Would you ever want "miibus" even if you're NOT using any of the cards that require it? I guess you might need it to be able to KLD load one of those drivers.. ? But that's no argument becuse you could just have a miibus.ko that was a dependency of those drivers. So why is it a separate option? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 14:50:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CA79C37B443 for ; Wed, 23 Aug 2000 14:50:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA67358; Wed, 23 Aug 2000 15:50:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA52708; Wed, 23 Aug 2000 15:49:58 -0600 (MDT) Message-Id: <200008232149.PAA52708@harmony.village.org> To: Archie Cobbs Subject: Re: 4.1 Release....MIIBUS Cc: Daryl Chance , FreeBSD Hackers In-reply-to: Your message of "Wed, 23 Aug 2000 14:09:05 PDT." <200008232109.OAA86366@bubba.whistle.com> References: <200008232109.OAA86366@bubba.whistle.com> Date: Wed, 23 Aug 2000 15:49:58 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008232109.OAA86366@bubba.whistle.com> Archie Cobbs writes: : Warner Losh writes: : > : not marked. I noticed that 4.1 Release miibus is still not : > : marked as (required), is it no longer required, or is it still : > : not marked? I ahven't tried compiling it with miibus commented : > : out, I'm just assuming it's still required : > : > miibus is still required for any ethernet card with a mii. Which is : > basically all of them produced in the last few years. my trusty : > ne2000 doesn't need it :-) : : Would you ever want "miibus" even if you're NOT using any of : the cards that require it? No. : I guess you might need it to be able to KLD load one of those : drivers.. ? But that's no argument becuse you could just have : a miibus.ko that was a dependency of those drivers. Already does that. : So why is it a separate option? because it is a driver. Why is pci a separate driver? While most computers have it, not all do. Likewise with miibus. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 15: 9:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id 1E37837B422 for ; Wed, 23 Aug 2000 15:09:48 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id PAA10734; Wed, 23 Aug 2000 15:09:47 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id PAA35866; Wed, 23 Aug 2000 15:09:47 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008232209.PAA35866@bubba.whistle.com> Subject: Re: 4.1 Release....MIIBUS In-Reply-To: <200008232149.PAA52708@harmony.village.org> "from Warner Losh at Aug 23, 2000 03:49:58 pm" To: Warner Losh Date: Wed, 23 Aug 2000 15:09:47 -0700 (PDT) Cc: Archie Cobbs , Daryl Chance , FreeBSD Hackers X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > : So why is it a separate option? > > because it is a driver. Why is pci a separate driver? While most > computers have it, not all do. Likewise with miibus. Ah.. but this analogy is not exact, because (for example) "device ed0" does not require PCI, wheras all of these miibus drivers do.. But you're probably right, since it's a driver maybe that's a good enough reason. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 15:12:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (Postfix) with ESMTP id DE58037B42C for ; Wed, 23 Aug 2000 15:12:06 -0700 (PDT) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by gatekeeper.whistle.com (8.9.3/8.9.3) with ESMTP id PAA10760; Wed, 23 Aug 2000 15:12:06 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id PAA55123; Wed, 23 Aug 2000 15:12:06 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008232212.PAA55123@bubba.whistle.com> Subject: Re: 4.1 Release....MIIBUS In-Reply-To: <200008232209.PAA35866@bubba.whistle.com> "from Archie Cobbs at Aug 23, 2000 03:09:47 pm" To: Archie Cobbs Date: Wed, 23 Aug 2000 15:12:05 -0700 (PDT) Cc: Warner Losh , Daryl Chance , FreeBSD Hackers X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > But you're probably right, since it's a driver maybe that's > a good enough reason. ^^^^^^ Oops, meant "bus" instead of "driver" there.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 15:52:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AA27137B43C for ; Wed, 23 Aug 2000 15:52:16 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA67552; Wed, 23 Aug 2000 16:52:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA52995; Wed, 23 Aug 2000 16:52:02 -0600 (MDT) Message-Id: <200008232252.QAA52995@harmony.village.org> To: Archie Cobbs Subject: Re: 4.1 Release....MIIBUS Cc: Daryl Chance , FreeBSD Hackers In-reply-to: Your message of "Wed, 23 Aug 2000 15:09:47 PDT." <200008232209.PAA35866@bubba.whistle.com> References: <200008232209.PAA35866@bubba.whistle.com> Date: Wed, 23 Aug 2000 16:52:02 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008232209.PAA35866@bubba.whistle.com> Archie Cobbs writes: : Warner Losh writes: : > : So why is it a separate option? : > : > because it is a driver. Why is pci a separate driver? While most : > computers have it, not all do. Likewise with miibus. : : Ah.. but this analogy is not exact, because (for example) : "device ed0" does not require PCI, wheras all of these miibus : drivers do.. "device xe" does require pccard, otherwise it fails. "device wi" requires pccard, but will silently fail if no pccard in kernel. : But you're probably right, since it's a driver maybe that's : a good enough reason. I think that it is a minor flaw in our config system. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 16:13:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 5714A37B446 for ; Wed, 23 Aug 2000 16:13:31 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA00663; Wed, 23 Aug 2000 16:26:49 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008232326.QAA00663@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Archie Cobbs Cc: Warner Losh , Daryl Chance , FreeBSD Hackers Subject: Re: 4.1 Release....MIIBUS In-reply-to: Your message of "Wed, 23 Aug 2000 14:09:05 PDT." <200008232109.OAA86366@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Aug 2000 16:26:49 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would you ever want "miibus" even if you're NOT using any of > the cards that require it? > > I guess you might need it to be able to KLD load one of those > drivers.. ? But that's no argument becuse you could just have > a miibus.ko that was a dependency of those drivers. > > So why is it a separate option? For the same reason that eg. 'pci' is still a separate option. Config isn't smart enough to handle these dependancies. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 17:11: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.chiaro.com (mail.chiaro.com [63.88.196.66]) by hub.freebsd.org (Postfix) with ESMTP id 077B737B631 for ; Wed, 23 Aug 2000 17:11:03 -0700 (PDT) Received: by mail.chiaro.com with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Aug 2000 19:11:06 -0500 Message-ID: <2383E22BDFF6D311BB8400B0D021A507287E22@mail.chiaro.com> From: Charles Anderson To: FreeBSD Hackers Subject: FW: Notification: Inbound Mail Failure Date: Wed, 23 Aug 2000 19:11:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C00D5F.CBD255EC" 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_000_01C00D5F.CBD255EC Content-Type: text/plain; charset="iso-8859-1" -----Original Message----- From: Administrator Sent: Wednesday, August 23, 2000 6:53 PM To: Administrator Subject: Notification: Inbound Mail Failure The following recipients did not receive the attached mail. A NDR was not sent to the originator for the following recipients for one of the following reasons: * The Delivery Status Notification options did not request failure notification, or requested no notification. * The message was of precedence bulk. NDR reasons are listed with each recipient, along with the notification requested for that recipient, or the precedence. alias-chiaro-dbaukus@mail.chiaro.com MSEXCH:IMS:chiaro:da:MAIL 0 (000C05A6) Unknown Recipient Precedence: bulk The message that caused this notification was: <> ------_=_NextPart_000_01C00D5F.CBD255EC Content-Type: message/rfc822 Message-ID: <200008232252.QAA52995@harmony.village.org> From: Warner Losh To: Archie Cobbs Cc: Daryl Chance , FreeBSD Hackers Subject: Re: 4.1 Release....MIIBUS Date: Wed, 23 Aug 2000 17:52:02 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" In message <200008232209.PAA35866@bubba.whistle.com> Archie Cobbs writes: : Warner Losh writes: : > : So why is it a separate option? : > : > because it is a driver. Why is pci a separate driver? While most : > computers have it, not all do. Likewise with miibus. : : Ah.. but this analogy is not exact, because (for example) : "device ed0" does not require PCI, wheras all of these miibus : drivers do.. "device xe" does require pccard, otherwise it fails. "device wi" requires pccard, but will silently fail if no pccard in kernel. : But you're probably right, since it's a driver maybe that's : a good enough reason. I think that it is a minor flaw in our config system. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message ------_=_NextPart_000_01C00D5F.CBD255EC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 17:11:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.chiaro.com (mail.chiaro.com [63.88.196.66]) by hub.freebsd.org (Postfix) with ESMTP id 4ACFC37B64C for ; Wed, 23 Aug 2000 17:11:17 -0700 (PDT) Received: by mail.chiaro.com with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Aug 2000 19:11:16 -0500 Message-ID: <2383E22BDFF6D311BB8400B0D021A507287E23@mail.chiaro.com> From: Charles Anderson To: FreeBSD Hackers Subject: FW: Notification: Inbound Mail Failure Date: Wed, 23 Aug 2000 19:11:16 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C00D5F.D21E0B94" 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_000_01C00D5F.D21E0B94 Content-Type: text/plain; charset="iso-8859-1" -----Original Message----- From: Administrator Sent: Wednesday, August 23, 2000 6:53 PM To: Administrator Subject: Notification: Inbound Mail Failure The following recipients did not receive the attached mail. A NDR was not sent to the originator for the following recipients for one of the following reasons: * The Delivery Status Notification options did not request failure notification, or requested no notification. * The message was of precedence bulk. NDR reasons are listed with each recipient, along with the notification requested for that recipient, or the precedence. alias-chiaro-freebsd-hackers@mail.chiaro.com MSEXCH:IMS:chiaro:da:MAIL 0 (000C05A6) Unknown Recipient Precedence: bulk The message that caused this notification was: <> ------_=_NextPart_000_01C00D5F.D21E0B94 Content-Type: message/rfc822 Message-ID: <200008232252.QAA52995@harmony.village.org> From: Warner Losh To: Archie Cobbs Cc: Daryl Chance , FreeBSD Hackers Subject: Re: 4.1 Release....MIIBUS Date: Wed, 23 Aug 2000 17:52:02 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" In message <200008232209.PAA35866@bubba.whistle.com> Archie Cobbs writes: : Warner Losh writes: : > : So why is it a separate option? : > : > because it is a driver. Why is pci a separate driver? While most : > computers have it, not all do. Likewise with miibus. : : Ah.. but this analogy is not exact, because (for example) : "device ed0" does not require PCI, wheras all of these miibus : drivers do.. "device xe" does require pccard, otherwise it fails. "device wi" requires pccard, but will silently fail if no pccard in kernel. : But you're probably right, since it's a driver maybe that's : a good enough reason. I think that it is a minor flaw in our config system. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message ------_=_NextPart_000_01C00D5F.D21E0B94-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 17:49:12 2000 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 DEE4537B423 for ; Wed, 23 Aug 2000 17:49:08 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-140.nnj.dialup.bellatlantic.net [151.198.117.140]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA12673; Wed, 23 Aug 2000 20:45:41 -0400 (EDT) Message-ID: <39A470BF.B20F9AE5@bellatlantic.net> Date: Wed, 23 Aug 2000 20:47:59 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Wes Peters Cc: Oliver Fehr , hackers@FreeBSD.ORG Subject: Re: Advanced OS Questions only you can answer... References: <39A2D2FA.46CCCA52@softweyr.com> <00082221322801.26000@yalta.ofehr.com> <39A36B78.EAC2192@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > Oliver Fehr wrote: > > Well, the book covers UNIX and DOS, at least on of which can be considered > > a modern operating system. You be the judge which on ... > > Neither. One is not an operating system, but merely a game loader, and > the other is over 30 years old and dates to the days of mechanial tele- > types and punched paper tape as input/output devices. If you haven't > studied at least two of the above, you have no chance of understanding > why UNIX isn't a modern operating system. It is the conceptual parent > of all of the above, though. Acutually I found reading the Lions book (Unix V6 with commentaries) very helpful. The reason is that Unix V6 is small and simple, contains only the basic concepts unobscured yet by decades of features and optimisations. Helps a lot in understanding things. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 18: 8:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (oe52.law10.hotmail.com [64.4.14.41]) by hub.freebsd.org (Postfix) with ESMTP id A3A0A37B422 for ; Wed, 23 Aug 2000 18:08:51 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 23 Aug 2000 18:08:51 -0700 X-Originating-IP: [194.165.167.142] From: "Printf Cout" To: Subject: ld_path_variable Date: Thu, 24 Aug 2000 02:07:59 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C00D70.20087FA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: X-OriginalArrivalTime: 24 Aug 2000 01:08:51.0325 (UTC) FILETIME=[DD606AD0:01C00D67] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0014_01C00D70.20087FA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Installed imlib so that I could install gnome1.2x & Titano. Next = question how do I add LIBDIR to LD_LIBRARY_PATH? & or what must I do = to tell compiler & linker that imlib.19x has been installed? How do I add LLIBDIR to options during execution and linking? Apparently the libraries are in usr/local/lib How do I tell #include statements this? ------=_NextPart_000_0014_01C00D70.20087FA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Installed imlib=20 so that I could install gnome1.2x & Titano.  Next = question  how do=20 I add LIBDIR to LD_LIBRARY_PATH?  & or what must I do to tell = compiler=20 & linker that imlib.19x has been installed?
How do I add LLIBDIR = to=20 options during execution and linking?
Apparently the libraries are=20 in
usr/local/lib
How do I tell #include statements=20 this?
------=_NextPart_000_0014_01C00D70.20087FA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 21:20:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id ECB1737B424 for ; Wed, 23 Aug 2000 21:20:32 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7O4ard23484 for ; Wed, 23 Aug 2000 21:36:53 -0700 (PDT) Date: Wed, 23 Aug 2000 21:36:53 -0700 (PDT) From: FengYue To: freebsd-hackers@FreeBSD.ORG Subject: psmintr 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 Hi, what does "psmintr: out of sync (0000 != 0008)." mean? I got tons of this message on my console and then my X-window went nearly dead. sounds like my PS/2 mouse's problem? Found the source code in isa/psm.c, but have not got any clue what could have caused this. (Have had this mouse for last 2 years). Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 21:41:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 4D95B37B423 for ; Wed, 23 Aug 2000 21:41:35 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7O4vun34616 for ; Wed, 23 Aug 2000 21:57:56 -0700 (PDT) Date: Wed, 23 Aug 2000 21:57:56 -0700 (PDT) From: FengYue To: freebsd-hackers@FreeBSD.ORG Subject: Re: psmintr 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 Forgot to mention, it's a 4.1-stable box (PIII-450, 256MB ram, 1024MB swap) On Wed, 23 Aug 2000, FengYue wrote: > > Hi, what does "psmintr: out of sync (0000 != 0008)." mean? > I got tons of this message on my console and then my X-window went > nearly dead. > > sounds like my PS/2 mouse's problem? Found the source code in isa/psm.c, > but have not got any clue what could have caused this. (Have had this > mouse for last 2 years). > > Thanks! > > > > 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 Aug 23 22:48:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 5715E37B424 for ; Wed, 23 Aug 2000 22:48:10 -0700 (PDT) Received: from vcmr-19.rcs.rpi.edu (vcmr-19.rcs.rpi.edu [128.113.113.12]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA557476 for ; Thu, 24 Aug 2000 01:48:09 -0400 Received: from localhost (gerbal@localhost) by vcmr-19.rcs.rpi.edu (8.8.5/8.8.6) with SMTP id BAA137388 for ; Thu, 24 Aug 2000 01:48:32 -0400 X-Authentication-Warning: vcmr-19.rcs.rpi.edu: gerbal owned process doing -bs Date: Thu, 24 Aug 2000 01:48:32 -0400 (EDT) From: Louis Gerbarg X-Sender: gerbal@vcmr-19.rcs.rpi.edu To: freebsd-hackers@FreeBSD.ORG Subject: A few device questions 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 have been working with the OpenBSD /dev/random driver, and have ported it to Darwin. While I was at I wanted to also port it to FreeBSD, because it is more functional then current one, but I have a few questions: In OpenBSD random has its own major, whereas in FreeBSD it is part of the mem major. I assume that it should be kept part o the mem major? Assuming I do that I basicly was going to make the memdriver calls check for the random minors, and if it was one call the appropriate call from the OpenBSD random driver. The mem driver does not seem to have an attach call. To hack around that on darwin I used a static variable initialized to 0, and then put a test for it in the open call. If it is zero it runs my attach routine and sets the variable to 1. Is there a better way to do this in the FreeBSD mem driver? The OpenBSD driver does not support the poll call, but one of the FreeBSD one does. I prefer the OpenBSD semantics, but is there a reason why poll is available for one of the random devices? I also patched the libkern random routine, so that it calls the same backend as /dev/urandom. This is equivalent to /dev/srandom until it runs out of entropy, then degenerates to /dev/prandom, which is basicly equivalent to the current algorithm. This allows all of the kernel random routines to get better quality random. Do other people think this is a good idea? I also modified theier random driver to use sha1 instead of md5, because it was simpler for a number of reasons. In OpenBSD that is in /usr/src/sys/crypto/, where would it go in FreeBSD? Also there seems to be a vestigial version of seperate random driver kern/kern_random.c (Attic). Is there any reason why the code was moved directly into the architexture specific mem.c. It seems to me that the random code should be platform neutral, and that placing it in the mem driver causes a significant increase in complexity in certain cases. Thanks for your time, it may be that I am just entirely off base, but I think that improved random code could be pretty useful. Louis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 22:53:34 2000 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 4CD7C37B422 for ; Wed, 23 Aug 2000 22:53:33 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7O5rW101014; Wed, 23 Aug 2000 22:53:32 -0700 (PDT) Date: Wed, 23 Aug 2000 22:53:32 -0700 From: Alfred Perlstein To: Louis Gerbarg Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A few device questions Message-ID: <20000823225331.X4854@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from gerbal@rpi.edu on Thu, Aug 24, 2000 at 01:48:32AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Louis Gerbarg [000823 22:48] wrote: > > The mem driver does not seem to have an attach call. To hack around that > on darwin I used a static variable initialized to 0, and then put a test > for it in the open call. If it is zero it runs my attach routine and sets > the variable to 1. Is there a better way to do this in the FreeBSD mem > driver? Yes, have a look at src/sys/netinet/accf_http.c particularly the DECLARE_MODULE macro, this allows one to declare routines to be run at the time when modload or boot happens. Sorry I can't answer your other questions, I try to avoid entropy. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 23:29:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id 70AE637B43C for ; Wed, 23 Aug 2000 23:29:23 -0700 (PDT) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id IAA62216; Thu, 24 Aug 2000 08:30:12 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200008240630.IAA62216@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Louis Gerbarg Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A few device questions In-Reply-To: Your message of "Thu, 24 Aug 2000 01:48:32 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Aug 2000 08:30:12 +0200 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Thu, 24 Aug 2000 01:48:32 EDT, Louis Gerbarg wrote: > I have been working with the OpenBSD /dev/random driver, and have ported > it to Darwin. While I was at I wanted to also port it to FreeBSD, because > it is more functional then current one, but I have a few questions: You should talk to Mark Murray markm@FreeBSD.Org who has done alot of work with the current implementation of our random device. /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 23 23:39:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id D09E137B423 for ; Wed, 23 Aug 2000 23:39:21 -0700 (PDT) Received: from grimreaper.grondar.za ([196.7.18.138] ident=root) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13RqfV-0001PS-00; Thu, 24 Aug 2000 08:39:18 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e7O6e5p14819; Thu, 24 Aug 2000 08:40:05 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008240640.e7O6e5p14819@grimreaper.grondar.za> To: Johan Karlsson Cc: Louis Gerbarg , freebsd-hackers@FreeBSD.ORG Subject: Re: A few device questions References: <200008240630.IAA62216@numeri.campus.luth.se> In-Reply-To: <200008240630.IAA62216@numeri.campus.luth.se> ; from Johan Karlsson "Thu, 24 Aug 2000 08:30:12 +0200." Date: Thu, 24 Aug 2000 08:40:05 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At Thu, 24 Aug 2000 01:48:32 EDT, Louis Gerbarg wrote: > > > I have been working with the OpenBSD /dev/random driver, and have > > ported it to Darwin. While I was at I wanted to also port it to > > FreeBSD, because it is more functional then current one, but I have > > a few questions: > > You should talk to Mark Murray markm@FreeBSD.Org who has done alot of > work with the current implementation of our random device. I am currently rewriting FreeBSD's /dev/random device to use Schneier's Yarrow algorithm. Some of it is in current, and a lot more is uncommitted. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 1:34: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id DA34737B43F; Thu, 24 Aug 2000 01:33:57 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 09:33:39 +0100 Message-ID: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 09:33:37 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: help with restoring sh Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have been upgrading from 3.4 to 4.1 and during the reboot I get a permission denied when it tries to exec the /bin/sh. I am trying to restore the file with one that is functioning properly..however I do not know how I should go about correcting my problem. I would appreciate any help as I am stranded with a server that is down at the moment... Thanks Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 1:46: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 5B09237B423 for ; Thu, 24 Aug 2000 01:46:00 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 09:45:54 +0100 Message-ID: <39A4E0C0.8AF0FC16@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 09:45:52 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: filename too long??? References: <39A4E022.FC7C26D5@cs.ucl.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 Theo PAGTZIS wrote: > Hi, > > I have the following fstab file > > # Device Mountpoint FStype Options Dump > Pass# > /dev/wd0s1b none swap sw 0 > 0 > /dev/wd0s1a / ufs rw 1 > 1 > /dev/wd0s1f /usr ufs rw 2 > 2 > /dev/wd0s1e /var ufs rw 2 > 2 > /dev/wcd0c /mnt/cdrom cd9660 ro,noauto 0 > 0 > /dev/fd0 /mnt/floppy msdos rw,noauto 0 > 0 > proc /proc procfs rw 0 > 0 > > # you want to get the essential ports in one place to do one build and > multi installs - faster > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool > /usr/pool nfs rw 0 0 > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports > /usr/ports/distfiles nfs rw 0 0 > > # this needs a soft link on the mounted folder, on the root dir > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas > /backupETC nfs rw 0 0 > > When I try to mount these stores I get : > > nfs: > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool: > File name too long > nfs: > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports: > File name too long > nfs: > starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas: > File name too long > > This was not the case with Fbsd 3.4 > > Why is this happening? Is it because of the device name change because > the machine boots fine without asking for an ad0 device set > > Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 2:31:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from plum.flirble.org (plum.flirble.org [195.40.6.20]) by hub.freebsd.org (Postfix) with ESMTP id 2656B37B423; Thu, 24 Aug 2000 02:31:27 -0700 (PDT) Received: from scot (helo=localhost) by plum.flirble.org with local-esmtp (Exim 3.12 #5) id 13RtM6-000Mx1-00; Thu, 24 Aug 2000 10:31:26 +0100 Date: Thu, 24 Aug 2000 10:31:26 +0100 (BST) From: scot@poptart.org X-Sender: scot@plum.flirble.org To: Theo PAGTZIS Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: help with restoring sh In-Reply-To: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk> 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 Boot from a fix-it floppy and copy it there from the floppy... (and make sure the permissions are correct)... Scot On Thu, 24 Aug 2000, Theo PAGTZIS wrote: > Hi all, > > I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... > > > Thanks > > Theo > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" 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 Aug 24 5:39:42 2000 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 CE89937B422 for ; Thu, 24 Aug 2000 05:39:38 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id IAA09534; Thu, 24 Aug 2000 08:39:22 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008241239.IAA09534@blackhelicopters.org> Subject: Re: psmintr In-Reply-To: from FengYue at "Aug 23, 2000 9:57:56 pm" To: fengyue@bluerose.windmoon.nu (FengYue) Date: Thu, 24 Aug 2000 08:39:21 -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 There was a bug that caused this not too long ago. Try resupping & rebuilding. > > Forgot to mention, it's a 4.1-stable box (PIII-450, 256MB ram, 1024MB > swap) > > On Wed, 23 Aug 2000, FengYue wrote: > > > > > Hi, what does "psmintr: out of sync (0000 != 0008)." mean? > > I got tons of this message on my console and then my X-window went > > nearly dead. > > > > sounds like my PS/2 mouse's problem? Found the source code in isa/psm.c, > > but have not got any clue what could have caused this. (Have had this > > mouse for last 2 years). > > > > Thanks! > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 9:16:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id C064137B43C for ; Thu, 24 Aug 2000 09:16:31 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 24 Aug 2000 17:16:18 +0100 Message-ID: <39A54A50.1151A1A@cs.ucl.ac.uk> Date: Thu, 24 Aug 2000 17:16:16 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, freebsd-net@freebsd.org Subject: fbsd box acting as a wavelan BS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Has anyone managed to configure a fbsd box as a Wavelan BS ? Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 10:26:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id C2D1A37B424; Thu, 24 Aug 2000 10:26:39 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7OHQXW04754 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 24 Aug 2000 19:26:36 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e7OHQlq82861; Thu, 24 Aug 2000 19:26:48 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id TAA30136; Thu, 24 Aug 2000 19:26:43 +0200 (CEST) (envelope-from ticso) Date: Thu, 24 Aug 2000 19:26:42 +0200 From: Bernd Walter To: Theo PAGTZIS Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: help with restoring sh Message-ID: <20000824192642.B30092@cicely8.cicely.de> References: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39A4DDE1.17DFE7DC@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Thu, Aug 24, 2000 at 09:33:37AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 09:33:37AM +0100, Theo PAGTZIS wrote: > Hi all, > > I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... With boot -s you on the loader prompt you can boot into single user mode. If asked for the shell to start try /bin/csh which is a different shell and then fix your problem. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 10:43:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from unx70.staff.flyingcroc.net (smokey.staff.flyingcroc.net [207.246.150.70]) by hub.freebsd.org (Postfix) with ESMTP id C3B4A37B424 for ; Thu, 24 Aug 2000 10:43:41 -0700 (PDT) Received: from flyingcroc.net (localhost [127.0.0.1]) by unx70.staff.flyingcroc.net (8.9.3/8.9.3) with ESMTP id KAA68418 for ; Thu, 24 Aug 2000 10:43:40 -0700 (PDT) (envelope-from jkraft@flyingcroc.net) Message-ID: <39A55ECC.BEC39349@flyingcroc.net> Date: Thu, 24 Aug 2000 10:43:40 -0700 From: Jason Kraft X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-RC3 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: nfs mount problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am running FreeBSD 4.1. I have made an NFS mount. server:/some/partition /mnt nfs rw 2 2 If I start to bring over files from that mount partition (/mnt) to a local directory, say /some/other/directory, it times out if I open up another terminal and type ls in /some/other/directory. I am not sure if there is something I can put in my fstab to help from this timing out problem. I have read the man pages for mount_nfs and nfsd. Any suggestions? Jason Kraft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 10:43:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 1778537B423; Thu, 24 Aug 2000 10:43:49 -0700 (PDT) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id KAA13920; Thu, 24 Aug 2000 10:43:45 -0700 (PDT) Date: Thu, 24 Aug 2000 10:43:45 -0700 From: Eric Kozowski To: Theo PAGTZIS Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS Message-ID: <20000824104345.G12584@schooner.svjava.com> References: <39A54A50.1151A1A@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <39A54A50.1151A1A@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Thu, Aug 24, 2000 at 05:16:16PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > Hi all, > > Has anyone managed to configure a fbsd box as a Wavelan BS ? yes it's easy. which wavelan card are you using? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 13:25:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.disney.com (mail11.disney.com [208.246.35.55]) by hub.freebsd.org (Postfix) with ESMTP id AB14A37B422 for ; Thu, 24 Aug 2000 13:25:51 -0700 (PDT) Received: from pain.corp.disney.com (pain.corp.disney.com [153.7.231.100]) by mail11.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id e7OKaJ120779 for ; Thu, 24 Aug 2000 13:36:20 -0700 (PDT) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP for freebsd-hackers@freebsd.org; Thu, 24 Aug 2000 13:26:17 -0700 Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id NAA09099 for ; Thu, 24 Aug 2000 13:25:48 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from snoopy.fan.fa.disney.com by mercury.fan.fa.disney.com for freebsd-hackers@freebsd.org; Thu, 24 Aug 2000 13:25:48 -0700 From: Jim Pirzyk Organization: Walt Disney Feature Animation To: freebsd-hackers@freebsd.org Subject: Fwd: kern.ipc.maxsockbuf setting does not work Date: Thu, 24 Aug 2000 13:24:01 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00082413254801.00439@snoopy.fan.fa.disney.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I have tracked down the bug to the fact in /sys/kern/uipc_socket2.c of this code fragment in sbreserver(): if ((u_quad_t)cc > (u_quad_t)sb_max * MCLBYTES / (MSIZE + MCLBYTES)) return (0); So why is the test not just this: if ((u_quad_t)cc > (u_quad_t)sb_max) return (0); - JimP ---------- Forwarded Message ---------- Subject: kern.ipc.maxsockbuf setting does not work Date: Thu, 24 Aug 2000 10:21:02 -0700 From: Jim Pirzyk I am running a 4.1-RELEASE i386 system and I am trying to increase the maxsockbuf size so I set it in /etc/sysctl.conf like this: kern.ipc.maxsockbuf=524288 And on bootup I see kern.ipc.maxsockbuf: 262144 -> 524288 but when I try to use a larger buffer I get: pirzyk@snoopy:/sys/kern 10>ttcp -r -w512 ttcp-r: buflen=65536, nbuf=2048, align=16384/0, port=5001, sockbufsize=524288 tcp ttcp-r: socket ttcp-r: setsockopt: sndbuf: No buffer space available errno=55 But this should work. Seems the kernel is keeping the old value of 262144. Now I can change it in /usr/include/sys/socketvar.h (SB_MAX) and rebuild the kernel but I do not think this is what was designed. - JimP -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) ------------------------------------------------------- -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 24 17:38:37 2000 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 3F85737B424 for ; Thu, 24 Aug 2000 17:38:34 -0700 (PDT) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id UAA08757 for ; Thu, 24 Aug 2000 20:38:30 -0400 (EDT) Date: Thu, 24 Aug 2000 20:35:14 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: delayed write 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 I am wondering what exactly will happen if a delayed write goes wrong. It seems to me that the kernel will just clear the error flag and mark the buffer as delayed write again. This gives the buffer a second chance. But how many chances at most a buffer can get before it is aborted. While this may seem not serious on a local filesystem. Consider the NFS case, if a delayed write to a NFS server fails, how many times will we retry? My understanding is that the user program will not notice these retries or aborts until it closes the file. Am I right? Please clarify this for me. Before 4.0, if we write something to a write-protected floppy, the system will panic. Obviously, this panic does not happen on 4.0+. So I guess that the retries must have a limit. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 0:10:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from procsys.com (PPP-180-143.bng.vsnl.net.in [203.197.180.143]) by hub.freebsd.org (Postfix) with SMTP id CC8C937B42C for ; Fri, 25 Aug 2000 00:10:50 -0700 (PDT) Received: from procsys.com ([192.168.1.115]) by procsys.com with SMTP; Fri, 25 Aug 2000 12:43:29 +0800 Message-ID: <39A61CCA.2DB82AFF@procsys.com> Date: Fri, 25 Aug 2000 12:44:18 +0530 From: Pran Joseph Reply-To: pran@procsys.com Organization: Processor Systems (India) Pvt. Ltd X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Memory Mapping -2 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 am trying to write a PCI ethernet driver for FreeBSD 3.4 release. I have some questions 1. How can I convert physical address to virtual address . What I want is to read the physical address from the device register and to copy it to host memory. From my earlier post I found that I can use vtopys macro to convert virtual to physical address. Now I want to do the reverse. 2. What are things should I do if I want the driver to work on alpha platform also. Thanks -Pran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 0:38: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 5AF6837B424 for ; Fri, 25 Aug 2000 00:37:58 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id AAA16934 for ; Fri, 25 Aug 2000 00:36:51 -0700 (MST) Received: from 207-218-69-66.nas-1.OBT.primenet.com(207.218.69.66), claiming to be "foo.fake.primenet.com" via SMTP by smtp03.primenet.com, id smtpdAAAv4aWcH; Fri Aug 25 00:36:47 2000 Received: from localhost (bkogawa@localhost) by foo.fake.primenet.com (8.9.3/8.8.8) with SMTP id AAA76521 for ; Fri, 25 Aug 2000 00:37:38 -0700 (PDT) (envelope-from bkogawa@primenet.com) X-Authentication-Warning: foo.fake.primenet.com: bkogawa owned process doing -bs Date: Fri, 25 Aug 2000 00:37:38 -0700 (PDT) From: "Bryan K. Ogawa" X-Sender: bkogawa@foo.fake.primenet.com To: hackers@freebsd.org Subject: Document about threads 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 Hey all, I have been trying to port some code to FreeBSD which currently runs under Linux (and to some degree, Solaris). Since I'm a longtime FreeBSD user, I'm pretty excited to get a chance to port to FreeBSD. The program I'm working on uses both POSIX threads and ISO C++ (including templates, exceptions, etc.), so I needed information about the current state of such things under FreeBSD. However, there wasn't any "one-stop" documentation I could find about the current state of everything. As a result, I ended up writing a brief text document which describes what I found out about threads (C++ and threads is only mentioned briefly). If anyone who knows about the state of the FreeBSD threads implementation could go through it and check it for factual errors, missing bits, etc. then that would be great. Included at the end of the document is a little bit about the planned implementation using scheduler activations for -CURRENT, but that section is almost totally just posts copied from the mailing list archives. I would be happy to contribute this information to the Documentation project if that would be preferable. The URL for the document is http://www.idiom.com/~bko/bsd/freebsd-threads.txt A few quick questions: 1. I had seen an email in the mailing list archives which asserted that C++ exceptions have been broken since August 1999 in the multithread case -- does anyone know what the status in 4.1-STABLE and -CURRENT are? I've managed to get the code to compile under FreeBSD, but it crashes quite rapidly after this, and I'm wondering if it's because of an exception being thrown. This is under 4.1-RELEASE. 2. Sometimes, the programs crash at startup, but not always. I seem to recall a recent discussion about the loader not being multi-thread safe -- was this fixed in time for 4.1-RELEASE ? Thanks, -- bryan k ogawa http://www.primenet.com/~bkogawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 1:15:37 2000 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 6A40937B424 for ; Fri, 25 Aug 2000 01:15:25 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id PAA92576; Fri, 25 Aug 2000 15:10:46 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 25 Aug 2000 15:10:46 +0700 (NSS) From: Max Khon To: "Bryan K. Ogawa" Cc: hackers@FreeBSD.ORG Subject: Re: Document about threads 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 hi, there! On Fri, 25 Aug 2000, Bryan K. Ogawa wrote: > 1. I had seen an email in the mailing list archives which asserted that > C++ exceptions have been broken since August 1999 in the multithread case > -- does anyone know what the status in 4.1-STABLE and -CURRENT are? I've > managed to get the code to compile under FreeBSD, but it crashes quite > rapidly after this, and I'm wondering if it's because of an exception > being thrown. This is under 4.1-RELEASE. this issue is unrelated to threads. FreeBSD stock g++ 2.95.2 compiler uses -fsjlj-exceptions mechanism for exception handling which is broken (g++ sometimes generates incorrect code even without any optimization options given). It is not FreeBSD-specific behaviour. gcc GNATS has bug report with similar gcc behaviour under OS/390. uou can still use /usr/ports/lang/egcs -- this is the same 2.95.2 but it uses DWARF2 unwinding info for exception handling -- the same mechanism that is used by default under Linux and (IIRC) Solaris. I believe that FreeBSD g++ will switch to this scheme in near future. I have initial set of patches that adds support to FreeBSD CRT startups for loading info from .eh_frame ELF sections needed for DWARF2 unwinding info mechanism to work. David O'Brien has all the information. I think he can shed some light on this issue (he is gcc/binutils maintainer) but he seems to be busy with other tasks -- I still haven't got any replies from him except "go ahead, it would be nice to have this feature" :) > 2. Sometimes, the programs crash at startup, but not always. I seem to > recall a recent discussion about the loader not being multi-thread safe -- > was this fixed in time for 4.1-RELEASE ? yes, I beleive /fjoe PS you will also have problems with shared libraries debugging (see PR/20373). I have solution for this problem too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 1:52:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 523C337B43C for ; Fri, 25 Aug 2000 01:52:46 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id KAA69212 for hackers@freebsd.org; Fri, 25 Aug 2000 10:52:49 +0200 (CEST) (envelope-from kuku) Date: Fri, 25 Aug 2000 10:52:49 +0200 (CEST) From: Christoph Kukulies Message-Id: <200008250852.KAA69212@gilberto.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: tape buffer size - scsi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I posted this already in 'questions' but since it is very urgent to my tape read back withing the next couple of hours I'm posting my plea here also: I'm trying to read a DAT tape with important backup data. The device is a DEC TLZ04. sa0 at ncr0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers When trying to read it (tar tvf /dev/rsa0) I'm getting a kernel message: (sa0:ncr0:0:4:0): 132497-byte tape record bigger than suplied buffer Any ideas? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 2:24: 2 2000 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 39EEC37B42C for ; Fri, 25 Aug 2000 02:23:59 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7P9Njo11283; Fri, 25 Aug 2000 02:23:45 -0700 (PDT) Date: Fri, 25 Aug 2000 02:23:44 -0700 From: Alfred Perlstein To: Pran Joseph Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Memory Mapping -2 Message-ID: <20000825022344.K1209@fw.wintelcom.net> References: <39A61CCA.2DB82AFF@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39A61CCA.2DB82AFF@procsys.com>; from pran@procsys.com on Fri, Aug 25, 2000 at 12:44:18PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Pran Joseph [000825 00:11] wrote: > Hi, > > I am trying to write a PCI ethernet driver for FreeBSD 3.4 release. > > I have some questions > > 1. How can I convert physical address to virtual address . What I want > is to read the physical address from the device register and to copy it > to host memory. From my earlier post I found that I can use vtopys > macro to convert virtual to physical address. Now I want to do the > reverse. Um, I'm not sure what you mean here, a physical memory location can be mapped vitually anywhere :), you have to keep track of the virtual address somehow in your driver. > 2. What are things should I do if I want the driver to work on alpha > platform also. Don't use i386 assumptions? example: use PAGE_SIZE rather than hardcoding 4096, make sure you're using busdma rather than hardcoding all your stuff. Lastly buy and alpha. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 2:45:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.dev.nanoteq.co.za (ockle.dev.nanoteq.co.za [196.7.114.28]) by hub.freebsd.org (Postfix) with ESMTP id BD7AB37B423; Fri, 25 Aug 2000 02:45:03 -0700 (PDT) Received: (from johan@localhost) by ockle.dev.nanoteq.co.za (8.9.3/8.9.3) id LAA97652; Fri, 25 Aug 2000 11:56:12 +0200 (SAST) (envelope-from johan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 25 Aug 2000 11:56:12 +0200 (SAST) Organization: Nanoteq From: Johan Kruger To: FreeBSD Current , freebsd-hackers@FreeBSD.ORG Subject: perlcc in current - xs_init and boot_DynaLoader Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If i do a perlcc test.pl i get the folllowing , in CURRENT ? Must i define something beforehand, or is it broken ? -Wl,-E -lperl -lm -L/usr/libdata/perl/5.6.0/mach/CORE -lperl -lm -lc -lcrypt /usr/libdata/perl/5.6.0/mach/auto/IO/IO.so /usr/libdata/perl/5.6.0/mach/auto/Fcntl/Fcntl.so /tmp/ccJ97508.o: In function `xs_init': /tmp/ccJ97508.o(.text+0x33a4): undefined reference to `boot_DynaLoader' ERROR: In compiling code for test.pl.c ! ---------------------------------- Unix Software Developer/Engineer E-Mail: Johan Kruger Date: 25-Aug-00 Time: 11:53:40 All good things come to those who ... runs FreeBSD ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 3:14: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from user2.hushmail.com (user2.hushmail.com [216.18.8.74]) by hub.freebsd.org (Postfix) with ESMTP id C42C537B424 for ; Fri, 25 Aug 2000 03:13:58 -0700 (PDT) Received: (from root@localhost) by user2.hushmail.com (8.9.3/8.9.3) id DAA14106; Fri, 25 Aug 2000 03:12:41 -0700 From: core-ix@hushmail.com Message-Id: <200008251012.DAA14106@user2.hushmail.com> Date: ×ò, 25 VIII 2000 13:12:13 +0200 (EEDT) Cc: To: freebsd-hackers@FreeBSD.ORG Mime-version: 1.0 Content-type: multipart/mixed; boundary="Hushpart_boundary_XVfBISCSfQomtkHiyjTkbtSNezCOjdha" Subject: Preventing zombies to occure Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Hushpart_boundary_XVfBISCSfQomtkHiyjTkbtSNezCOjdha Content-type: text/plain Hello, I have some ideas to improve fork()-ing and getting rid of zombie processes. This things mentioned here are proposed of a man that do not know very well (author means 'the depths' of) BSD kernel source although he have some ex- pirience with it (mainly in reading it :-). By definition zombie is a process entry in proc table that wasn't released by wait*() called form the parent's code. So all we need to do is to ensure that parent will call wait*() as many times as it called fork(). This meth- od have some advantages but it has some disadvantages too. First of all, we provide programmers & all users with full out-of-zombies enviroment where everything created will be destroyed in the right way. Second, proposed me- thod is easy to include in current source with minnor modifications. What I exactly mean is: 1) Adding 'int childs' field in 'struct proc' in /usr/src/sys/sys/proc.h That field will store current numbers of childs for the process entry. After creation of process it is initialized to zero and incremented by one after each fork(). The real incrementation may be done by *fork() or fork1() from /usr/src/sys/kern/kern_fork.c - it doesn't matter. In this way we may keep track of number of childs; how many times process fork()s; to limit number of fork()s per process and etc. 2) Setting up an 'at-exit()' function that will call wait*() as many ti- mes as needed. It could probably look something like that: void release_childs(p) struct proc *p; { int rc; while(p->childs != 0) /* Release all childs in a loop by { * wait()-ing each of them to exit rc = wait(NULL);*/ if(rc == -1) { printf(" Can NOT release all childs \n"); /* * Any other steps to proceed here */ return; } p->childs--; /* Decreasing the number of childs left*/ } return; } And the code to call the above somewhere in fork1() (probably): . . . at_exit(release_childs()); . . . 3) Of course, any program may still use wait*() functions to ensure right exiting of each childs, but the new wait*() functions should include some bits of code like this (probably the right place for it is /usr/src/sys/kern/kern_ exit.c --> wait1()): . . . q->childs--; . . . By doing this, the code will take care only for childs that wasn't wait()- ed or 'forgotten' by the parent process due to programmer's mistake or bad algorithm. This code probably may be improved a lot but for now it is still in 0.1 version :-) so please excuse my "kernel-C". (All mentioned-bug comments are wellcome). That's all by now. If you think there is something usefull in the ideas menti- oned above please drop me a letter to encourage me. I am unix new programmer with little experience but I'd like to help anyone that develops BSD and espe- cially FreeBSD by introdusing ideas that I found worthable in my works. Please excuse my code if it isn't as tight as it should be but I am only 18-years- old high-school student with interests in OS development and almost any information about it. (If you can, send me any kind of programming resources oriented to BSD and other Unices). Thanks for reading this long borring letter. Looking forward to hearing from you. ix core-ix@hushmail.com --Hushpart_boundary_XVfBISCSfQomtkHiyjTkbtSNezCOjdha-- IMPORTANT NOTICE: If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages. Get your FREE, totally secure email address at http://www.hushmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 3:40:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1350037B422 for ; Fri, 25 Aug 2000 03:40:33 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id DAA74998; Fri, 25 Aug 2000 03:39:50 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200008251039.DAA74998@pike.osd.bsdi.com> Subject: Re: Preventing zombies to occure In-Reply-To: <200008251012.DAA14106@user2.hushmail.com> from "core-ix@hushmail.com" at "Aug 25, 2000 03:13:52 am" To: core-ix@hushmail.com Date: Fri, 25 Aug 2000 03:39:50 -0700 (PDT) Cc: hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (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 core-ix@hushmail.com wrote: > Hello, > > I have some ideas to improve fork()-ing and getting rid of zombie processes. > This things mentioned here are proposed of a man that do not know very well > (author means 'the depths' of) BSD kernel source although he have some ex- > pirience with it (mainly in reading it :-). I'll betray some of my own ignorance here, but what about processes where the parent exits before the child? For example, when starting a server, it is customary for the foreground process to fork a background child to be the actual server process and then exit. You might be able to work around that problem and the one you are tackling by adding some smarts to exit(2) so that when a process exits, it checks to see if any of its children are zombies and clears them if so, and for a process to not become a zombie upon exit(2) unless it's parent is still around. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 3:47:37 2000 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 E972537B424 for ; Fri, 25 Aug 2000 03:47:34 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7PAl3413151; Fri, 25 Aug 2000 03:47:03 -0700 (PDT) Date: Fri, 25 Aug 2000 03:47:03 -0700 From: Alfred Perlstein To: core-ix@hushmail.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Preventing zombies to occure Message-ID: <20000825034703.L1209@fw.wintelcom.net> References: <200008251012.DAA14106@user2.hushmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008251012.DAA14106@user2.hushmail.com>; from core-ix@hushmail.com on Fri, Aug 25, 2000 at 10:14:18AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * core-ix@hushmail.com [000825 03:14] wrote: > Hello, > > I have some ideas to improve fork()-ing and getting rid of zombie processes. > This things mentioned here are proposed of a man that do not know very well > (author means 'the depths' of) BSD kernel source although he have some ex- > pirience with it (mainly in reading it :-). > > By definition zombie is a process entry in proc table that wasn't released > by wait*() called form the parent's code. So all we need to do is to ensure > that parent will call wait*() as many times as it called fork(). This meth- > od have some advantages but it has some disadvantages too. First of all, > we > provide programmers & all users with full out-of-zombies enviroment where > everything created will be destroyed in the right way. Second, proposed > me- > thod is easy to include in current source with minnor modifications. > [snip] If a parent that has zombie children exits the kernel will attach them to init (I haven't checked, but this is the common unix solution). init will be calling waitpid to clear zombies automagically. So this sorta already happens. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 4:11:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sample.bt.ru (sample.bt.ru [195.170.35.9]) by hub.freebsd.org (Postfix) with ESMTP id 584CD37B424 for ; Fri, 25 Aug 2000 04:11:48 -0700 (PDT) Received: from igor (igor.bt.ru [195.170.35.38]) by sample.bt.ru (8.9.3/8.9.3) with SMTP id OAA01522 for ; Fri, 25 Aug 2000 14:41:23 +0400 Message-ID: <012901c00e7f$0c0c9300$2623aac3@igor> From: "Igor Rumyntsev" To: Subject: Date: Fri, 25 Aug 2000 14:27:16 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0126_01C00EA0.91A96D50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0126_01C00EA0.91A96D50 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0126_01C00EA0.91A96D50 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0126_01C00EA0.91A96D50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 4:21:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id D5DFD37B424 for ; Fri, 25 Aug 2000 04:21:44 -0700 (PDT) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id UAA50540; Fri, 25 Aug 2000 20:20:49 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200008251120.UAA50540@shidahara1.planet.sci.kobe-u.ac.jp> To: acpi-jp@jp.freebsd.org, hackers@freebsd.org Cc: iwasaki@jp.freebsd.org Subject: Merging ACPI related code is on the way. Date: Fri, 25 Aug 2000 20:20:49 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have committed orthognal part of ACPI driver. The rest part will be committed after a few days. I put the part at . This can be applied for HEAD. Please test and report about it if there is serious problem,such as breaking build. Thanks. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 5:58:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by hub.freebsd.org (Postfix) with ESMTP id 9610437B423 for ; Fri, 25 Aug 2000 05:58:32 -0700 (PDT) Received: from gab200r1.ems.att.com ([135.37.94.32]) by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id IAA10921; Fri, 25 Aug 2000 08:58:31 -0400 (EDT) Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id JAA01545; Fri, 25 Aug 2000 09:00:21 -0400 (EDT) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2652.35) id ; Fri, 25 Aug 2000 08:58:30 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Alfred Perlstein'" , core-ix@hushmail.com Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Preventing zombies to occure Date: Fri, 25 Aug 2000 08:58:28 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have some ideas to improve fork()-ing and getting rid of > zombie processes. > > This things mentioned here are proposed of a man that do > not know very well > > (author means 'the depths' of) BSD kernel source although > he have some ex- > > pirience with it (mainly in reading it :-). > > > > By definition zombie is a process entry in proc table that > wasn't released > > by wait*() called form the parent's code. So all we need to > do is to ensure > > that parent will call wait*() as many times as it called > fork(). This meth- > > od have some advantages but it has some disadvantages too. > First of all, > > we > > provide programmers & all users with full out-of-zombies > enviroment where > > everything created will be destroyed in the right way. > Second, proposed > > me- > > thod is easy to include in current source with minnor modifications. > > > > [snip] > > If a parent that has zombie children exits the kernel will attach them > to init (I haven't checked, but this is the common unix solution). > init will be calling waitpid to clear zombies automagically. > > So this sorta already happens. :) two ways: first: something like SIGCHLD_handler(int) { while (waitpid(-1, NULL, 0)) ; } you need to handle SIGCHLD, otherwise you will have zombies. second: use SA_NOCLDWAID flag in sigaction(2) in this case ``init'' will be responsible for zombie process 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 Aug 25 6:24:44 2000 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 40D2337B43C for ; Fri, 25 Aug 2000 06:24:42 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7PDO9t16755; Fri, 25 Aug 2000 06:24:09 -0700 (PDT) Date: Fri, 25 Aug 2000 06:24:09 -0700 From: "'Alfred Perlstein'" To: "Yevmenkin, Maksim N, CSCIO" Cc: core-ix@hushmail.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Preventing zombies to occure Message-ID: <20000825062409.O1209@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from myevmenkin@att.com on Fri, Aug 25, 2000 at 08:58:28AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Yevmenkin, Maksim N, CSCIO [000825 05:59] wrote: > > > > [snip] > > > > If a parent that has zombie children exits the kernel will attach them > > to init (I haven't checked, but this is the common unix solution). > > init will be calling waitpid to clear zombies automagically. > > > > So this sorta already happens. :) > > two ways: > > first: > > something like > > SIGCHLD_handler(int) > { > while (waitpid(-1, NULL, 0)) > ; > } This could be wrong if: [EINTR] The call was interrupted by a caught signal, or the signal did not have the SA_RESTART flag set. more proper (paraniod) would be: int sigchld_handler(int) { while (waitpid(-1, NULL, 0) || errno == EINTR) ; } > you need to handle SIGCHLD, otherwise you will have zombies. > > second: > > use SA_NOCLDWAID flag in sigaction(2) > in this case ``init'' will be responsible for zombie process typo: should be 'SA_NOCLDWAIT'. Sorry to pick, but one must be careful. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 7: 5:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 992A837B423 for ; Fri, 25 Aug 2000 07:05:10 -0700 (PDT) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.0/8.11.0) id e7PE2KG06553; Fri, 25 Aug 2000 10:02:20 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 25 Aug 2000 10:02:20 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Max Khon Subject: Re: Document about threads Cc: freebsd-hackers@FreeBSD.ORG, "Bryan K. Ogawa" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > this issue is unrelated to threads. FreeBSD stock g++ 2.95.2 compiler > uses -fsjlj-exceptions mechanism for exception handling which is broken > (g++ sometimes generates incorrect code even without any optimization > options given). It is not FreeBSD-specific behaviour. gcc GNATS has > bug report with similar gcc behaviour under OS/390. There was a bug in -fsjlj-exceptions code generation related to shared libraries and to best of my knowledge the correct fix has been imported into the official gcc CVS tree and was merged into FreeBSD some time ago. Are there any other errors you know about? If there are any simple code snippets which can demonstrate the problem, I am willing to investigate it further and see if it can be fixed. -fsjls-exceptions errors should be fixed regardless of whether FreeBSD is going to switch to DWARF scheme or not. 4.x-STABLE is here to stay for quite some time and I doubt that it will ever be changed to use DWARF unwinding. ------------------------------------------ E-Mail: Alexander N. Kabaev Date: 25-Aug-00 Time: 09:45:59 ------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 7:53:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D89537B440 for ; Fri, 25 Aug 2000 07:53:50 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id QAA71242; Fri, 25 Aug 2000 16:53:55 +0200 (CEST) (envelope-from kuku) Date: Fri, 25 Aug 2000 16:53:55 +0200 From: Christoph Kukulies To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: tape buffer size - scsi Message-ID: <20000825165355.B71087@gil.physik.rwth-aachen.de> References: <200008250852.KAA69212@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008250852.KAA69212@gilberto.physik.rwth-aachen.de>; from kuku@gilberto.physik.RWTH-Aachen.DE on Fri, Aug 25, 2000 at 10:52:49AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 10:52:49AM +0200, Christoph Kukulies wrote: > > Sorry, I posted this already in 'questions' but since it is very urgent to > my tape read back withing the next couple of hours I'm posting my plea > here also: Ooops. I must have been very nervous about getting my tape read back that I made so many typos. I finally solved it. The tape was written a bit weird at then. dd if=/dev/rsa0 ibs=256k | tar zxvf - solved the problem. > -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 7:55: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cyfari.com (www.cyfari.com [63.70.68.50]) by hub.freebsd.org (Postfix) with SMTP id 1D57737B423 for ; Fri, 25 Aug 2000 07:55:03 -0700 (PDT) Received: (qmail 81842 invoked by uid 1000); 25 Aug 2000 15:00:21 -0000 Date: Fri, 25 Aug 2000 11:00:21 -0400 From: Naief BinTalal To: core-ix@hushmail.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Preventing zombies to occure Message-ID: <20000825110021.A81738@www.cyfari.com> References: <200008251012.DAA14106@user2.hushmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200008251012.DAA14106@user2.hushmail.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 02:19:28PM +0000, core-ix@hushmail.com wrote: > Hello, > Hi ix > By definition zombie is a process entry in proc table that wasn't released > by wait*() called form the parent's code. So all we need to do is to ensure A zombie can only occur with a *live* parent. If the parent exits, it's orphaned children are automatically inherited by init (Pid 1) which is a very well written program that will wait on any exiting child ( or even a bunch of zombies inherited from a dysfunctional parent ). So your solution is already there in the system. The solution (if one is even desired :) should be along these line: Instead of discarding SIGCHLD which is issued when the child exits, it should have a default handler which would check if indeed that is the case and wait on that child (in other words what a good programmer should do for himself :) .... Naief To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 8:26:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 25E4337B42C; Fri, 25 Aug 2000 08:26:06 -0700 (PDT) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.0/8.11.0) with ESMTP id e7PFQ3631621; Fri, 25 Aug 2000 11:26:03 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200008251526.e7PFQ3631621@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: Robert Watson , Jonas Bulow , hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: freebsd and non-preemtive threads References: <3997C2C5.83AFE056@servicefactory.se> <20000821181316.J4854@fw.wintelcom.net> In-reply-to: Your message of "Mon, 21 Aug 2000 18:13:16 PDT." <20000821181316.J4854@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Aug 2000 11:26:03 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Robert Watson [000821 18:01] wrote: > > > > For reference, my recollection is that peemption-aware userland thread > > libraries tend to make alot of timer syscalls, losing some of the > > advantage of being a userland thread library (low context switch cost, few > > transistions between user/kerneland). The AFS LWP code included a > > fasttime() mechanism that took advantage of the ability to mmap kernel > > memory under SunOS, allowing direct access to the timer variable in > > kernel, without a context switch. I do not believe that native ports to > > Linux/FreeBSD/et al have retained this capability, especially given its > > requirements for privilege. However, it would be easy to imagine a kernel > > module exporting a /dev/time, which had the singular ability of allowing > > the mmaping of a page containing only the kernel's timer variables, > > permitting syscall-free precise time access from userland using atomic > > memory access calls. > > I think phk and I discussed this about a year ago, our idea was to > automatically map the segment in for each process (also allowing > things like getpid and such to be accessable). > > It would be nice to see happen either way (mmap'able /dev/time or > automatically) If it's a uni-processor machine, could you use the cycle counter register? I wrote a driver under FreeBSD 3.0 for the Datum bc635PCI which allowed a process to mmap() the device registers of this board. With two memory references, you'd get a timestamp with 100ns resolution, which was handy for a bunch of tasks. I don't know that a /dev/time would give you sufficient resolution, as convienient memory-based stuff would only be updated everytime hardclock() ran, at HZ times per second. The gettimeofday(), etc., routines do some other fiddling (like the TSC register, or reading other programmable timer devices). louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 8:36:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f233.law7.hotmail.com [216.33.237.233]) by hub.freebsd.org (Postfix) with ESMTP id CDB2937B42C for ; Fri, 25 Aug 2000 08:36:15 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 25 Aug 2000 08:36:15 -0700 Received: from 209.249.186.215 by lw7fd.law7.hotmail.msn.com with HTTP; Fri, 25 Aug 2000 GMT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: hackers@freebsd.org Subject: Re: Document about threads Date: Fri, 25 Aug 2000 11:36:15 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 25 Aug 2000 15:36:15.0728 (UTC) FILETIME=[34ABD700:01C00EAA] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Bryan K. Ogawa" > >If anyone who knows about the state of the FreeBSD threads implementation >could go through it and check it for factual errors, missing bits, etc. >then that would be great. in your section about common reentrant extensions, you mention the IPv6 apis. these are currently _not_ a viable alternative to the missing traditional gethostby{name,addr}_r entrypoints due to a bug in KAME. they are not threadsafe. your process will deadlock if multiple threads call getipnodeby{addr,name}. see http://orange.kame.net/dev/query-pr.cgi?pr=277. -- -greg ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 8:55: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from irvmail2.bdi.gte.com (irvmail2.bdi.gte.com [192.76.80.130]) by hub.freebsd.org (Postfix) with ESMTP id 7266637B43F for ; Fri, 25 Aug 2000 08:54:59 -0700 (PDT) Received: from irvmail2.bdi.gte.com (localhost [127.0.0.1]) by irvmail2.bdi.gte.com (8.9.3/8.9.3) with ESMTP id KAA05521; Fri, 25 Aug 2000 10:54:51 -0500 (EST) Received: from mail1.irngtx.tel.gte.com ([143.91.100.195]) by irvmail2.bdi.gte.com (8.9.3/8.9.3) with ESMTP id KAA05396; Fri, 25 Aug 2000 10:54:45 -0500 (EST) Received: from calender.tmtrfl.tel.gte.com (calender.tmtrfl.tel.gte.com [136.151.235.242]) by mail1.irngtx.tel.gte.com (8.9.3/8.9.3) with ESMTP id KAA29308; Fri, 25 Aug 2000 10:54:42 -0500 (CDT) Received: from aais.bdi.gte.com (michigan.tmtrfl.tel.gte.com [136.151.196.186]) by calender.tmtrfl.tel.gte.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id Q0GZC552; Fri, 25 Aug 2000 12:04:58 -0400 Message-ID: <39A69632.BD821EA@aais.bdi.gte.com> Date: Fri, 25 Aug 2000 11:52:18 -0400 From: Tim Grzechowski Organization: GTE Data Services X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: thomas r stromberg Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Anyone try the new dual-head G-400 drivers? References: <20000817111335.B714@rtci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I am a SysAdmin at GTE, 'er Verizon, and we are doing something simular. We tried using the freebie stuff with Xfree86 4.0.1 but found it to be extreamly buggy... both on Linux and FreeBSD. The solution we found works best is paying the 129 bucks and getting the drivers from AcceleratedX (I think it supports up to eight monitors). We are using the Matrox DUAL Head AGP card. It's been about three weeks and I have had no problems at all... in fact, I will defend to the death anyone that comes in and tries to take eight one of my two 21" monitors! I'm telling you, once you use it for a few hours you will never want to go back. ...no the task of talking the wife into a second 21" monitor for the house :) AcceleratedX has demo drivers, but be warned that they only work ten minutes before it dumps you back at the command prompt-- it doesn't care what you are doing. Hope this helps a bit. /tg thomas r stromberg wrote: > > We're looking at buying some workstations for our network admins > here, and dual head is a plus. We were looking at buying them from > hardware.bsdi.com, and then today on Slashdot I saw: > > ----------------- > Matrox has released a beta driver for their G200/G400/G450 which > includes support for DualHead and QuadHead (up to 4 monitors), Flat > Panel and TV out. This driver is a beta. You can get it here and I > mirrored it here. You'll need XFree 4.0.1 in order to use this > driver. Please follow the readme file carefully! (the readme file > from Matrox's FTP needs to be converted dos2unix). Note: you cannot > use the 3D hardware acceleration on the 2nd monitor (yet). > ----------------- > > And of course, I was instantly happy when I saw this.. > > Has anyone tried these drivers yet in FreeBSD? They look to be the > OS-independant XFree86 4.0.1 modules (nothing funky like the NVIDIA > ones). They come with some source code, but it appears to be > wrappers around a missing HAL (?) library, though I could be wrong. > > Please forward any successes/failures to the list. > > -- > thomas r. stromberg : tstromberg@rtci.com > senior systems administrator : http://www.afterthought.org/ > research triangle commerce, inc. : 1.919.657.1317 -- --------------------------------------------------------------- Timothy Grzechowski tim.grzechowski@aais.bdi.gte.com --------------------------------------------------------------- GTE Data Services AAIS Engineering, Sys. Admin. --------------------------------------------------------------- Office: 813/978-4327 Office FAX: 813/978-6812 --------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 9: 5: 4 2000 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 79D5B37B43E for ; Fri, 25 Aug 2000 09:04:48 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id XAA06934; Fri, 25 Aug 2000 23:04:29 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 25 Aug 2000 23:04:28 +0700 (NSS) From: Max Khon To: "Alexander N. Kabaev" Cc: freebsd-hackers@FreeBSD.ORG, "Bryan K. Ogawa" Subject: Re: Document about threads 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 hi, there! On Fri, 25 Aug 2000, Alexander N. Kabaev wrote: > There was a bug in -fsjlj-exceptions code generation related to shared > libraries and to best of my knowledge the correct fix has been imported into > the official gcc CVS tree and was merged into FreeBSD some time ago. Are there > any other errors you know about? If there are any simple code snippets which can > demonstrate the problem, I am willing to investigate it further and see if > it can be fixed. -fsjls-exceptions errors should be fixed regardless of whether > FreeBSD is going to switch to DWARF scheme or not. 4.x-STABLE is here to stay > for quite some time and I doubt that it will ever be changed to use DWARF > unwinding. this is definitely not the case with shared libraries -- I know about that bug and the fix was merged to FreeBSD CVS source tree somewhere around beginning of this year. unfortunately I have no simple code snippets and have no time to investigate it further. but I have an application that demonstrates this bug: Reactor_Exceptions_Test from ACE wrappers (you can get ACE wrappers from http://www.cs.wustl.edu/~schmidt/). the test itself is quite simple snippet but you will need to build ACE to run it. please look at #413 and #258 in gcc GNATS. all that I found is that emitted setjmp got optimized during flow analysis stage in such way that when exception is raised execution continues in try { } block (yes, again) instead of place where decision is taken in which catch { } block the execution should be continued. I do not know about any other 2.95.2 bugs. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 9:50: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 733A737B422 for ; Fri, 25 Aug 2000 09:49:56 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA75934; Fri, 25 Aug 2000 10:49:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA17846; Fri, 25 Aug 2000 10:49:46 -0600 (MDT) Message-Id: <200008251649.KAA17846@harmony.village.org> To: pran@procsys.com Subject: Re: Memory Mapping -2 Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 25 Aug 2000 12:44:18 +0530." <39A61CCA.2DB82AFF@procsys.com> References: <39A61CCA.2DB82AFF@procsys.com> Date: Fri, 25 Aug 2000 10:49:46 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A61CCA.2DB82AFF@procsys.com> Pran Joseph writes: : 1. How can I convert physical address to virtual address . What I want : is to read the physical address from the device register and to copy it : to host memory. From my earlier post I found that I can use vtopys : macro to convert virtual to physical address. Now I want to do the : reverse. : : 2. What are things should I do if I want the driver to work on alpha : platform also. Use the bus space macros. These will generally obviate the need to to the vtophys and ptovirt sorts of things. I don't think FreeBSD has a ptovirt these days. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 10:15:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id B704837B42C for ; Fri, 25 Aug 2000 10:15:36 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13SMka-000Lbe-00; Fri, 25 Aug 2000 17:54:40 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id RAA96635; Fri, 25 Aug 2000 17:54:39 +0100 (BST) (envelope-from ben) Date: Fri, 25 Aug 2000 17:54:39 +0100 From: Ben Smithurst To: "'Alfred Perlstein'" Cc: "Yevmenkin, Maksim N, CSCIO" , core-ix@hushmail.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Preventing zombies to occure Message-ID: <20000825175439.C30144@strontium.scientia.demon.co.uk> References: <20000825062409.O1209@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000825062409.O1209@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 'Alfred Perlstein' wrote: > int > sigchld_handler(int) > { > > while (waitpid(-1, NULL, 0) || errno == EINTR) > ; > } Even more paranoid would be int sigchld_handler(int) { int e = errno; while (waitpid(-1, NULL, 0) || errno == EINTR) ; errno = e; } otherwise you could get bogus errors reported, I think. if ((fp = fopen(foo, "r")) == NULL) /* SIGCHLD arrives here */ warn("can't open foo"); -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 11:28:59 2000 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 27B0937B443; Fri, 25 Aug 2000 11:28:48 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7PISlV25020; Fri, 25 Aug 2000 11:28:47 -0700 (PDT) Date: Fri, 25 Aug 2000 11:28:47 -0700 From: "'Alfred Perlstein'" To: Ben Smithurst Cc: "Yevmenkin, Maksim N, CSCIO" , core-ix@hushmail.com, freebsd-hackers@FreeBSD.org Subject: Re: Preventing zombies to occure Message-ID: <20000825112847.Z1209@fw.wintelcom.net> References: <20000825062409.O1209@fw.wintelcom.net> <20000825175439.C30144@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000825175439.C30144@strontium.scientia.demon.co.uk>; from ben@FreeBSD.org on Fri, Aug 25, 2000 at 05:54:39PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Ben Smithurst [000825 10:15] wrote: > 'Alfred Perlstein' wrote: > > > int > > sigchld_handler(int) > > { > > > > while (waitpid(-1, NULL, 0) || errno == EINTR) > > ; > > } > > Even more paranoid would be > > int > sigchld_handler(int) > { > int e = errno; > > while (waitpid(-1, NULL, 0) || errno == EINTR) > ; > > errno = e; > } > > otherwise you could get bogus errors reported, I think. > > if ((fp = fopen(foo, "r")) == NULL) > /* SIGCHLD arrives here */ > warn("can't open foo"); The code I presented is flawed as a result of an allnighter dealing with postresql. I'll enjoy thinking about this over the weekend. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 11:31:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 274D137B422 for ; Fri, 25 Aug 2000 11:31:52 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13SNlG-000LkM-00; Fri, 25 Aug 2000 18:59:26 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id SAA21641; Fri, 25 Aug 2000 18:59:26 +0100 (BST) (envelope-from ben) Date: Fri, 25 Aug 2000 18:59:26 +0100 From: Ben Smithurst To: "'Alfred Perlstein'" Cc: "Yevmenkin, Maksim N, CSCIO" , core-ix@hushmail.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Preventing zombies to occure Message-ID: <20000825185926.D30144@strontium.scientia.demon.co.uk> References: <20000825062409.O1209@fw.wintelcom.net> <20000825175439.C30144@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000825175439.C30144@strontium.scientia.demon.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 'Alfred Perlstein' wrote: > >> int >> sigchld_handler(int) >> { >> >> while (waitpid(-1, NULL, 0) || errno == EINTR) >> ; >> } actually, shouldn't you use WNOHANG when calling waitpid() there? What I normally do is int e = errno; while (waitpid(-1, NULL, WNOHANG) > 0) ; errno = e; But I think I'm drifting from the original point. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 11:57:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 62D7A37B422 for ; Fri, 25 Aug 2000 11:57:43 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13SOfa-000D8C-00; Fri, 25 Aug 2000 18:57:39 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id UAA01509; Fri, 25 Aug 2000 20:57:54 +0200 (CEST) (envelope-from wkb) Date: Fri, 25 Aug 2000 20:57:54 +0200 From: Wilko Bulte To: Christoph Kukulies Cc: hackers@freebsd.org Subject: Re: tape buffer size - scsi Message-ID: <20000825205754.E605@freebie.demon.nl> References: <200008250852.KAA69212@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008250852.KAA69212@gilberto.physik.rwth-aachen.de>; from kuku@gilberto.physik.rwth-aachen.de on Fri, Aug 25, 2000 at 10:52:49AM +0200 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 10:52:49AM +0200, Christoph Kukulies wrote: > Sorry, I posted this already in 'questions' but since it is very urgent to > my tape read back withing the next couple of hours I'm posting my plea > here also: > > > I'm trying to read a DAT tape with important backup data. > The device is a DEC TLZ04. > sa0 at ncr0 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > > When trying to read it (tar tvf /dev/rsa0) I'm getting a kernel message: > > (sa0:ncr0:0:4:0): 132497-byte tape record bigger than suplied buffer > > Any ideas? The tape has probably been written by a non-FreeBSD machine. Like an SGI or something like that. They can do much larger blocksizes. I think FreeBSD is limited to 64k (??). W/ -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 12:10: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 1DA5F37B422 for ; Fri, 25 Aug 2000 12:10:02 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id F2F391925D; Fri, 25 Aug 2000 14:10:00 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id OAA22236; Fri, 25 Aug 2000 14:10:00 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Fri, 25 Aug 2000 14:10:00 -0500 From: "Jacques A. Vidrine" To: Tim Grzechowski Cc: thomas r stromberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Anyone try the new dual-head G-400 drivers? Message-ID: <20000825141000.A22129@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Tim Grzechowski , thomas r stromberg , freebsd-hackers@FreeBSD.ORG References: <20000817111335.B714@rtci.com> <39A69632.BD821EA@aais.bdi.gte.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39A69632.BD821EA@aais.bdi.gte.com>; from tim.grzechowski@aais.bdi.gte.com on Fri, Aug 25, 2000 at 11:52:18AM -0400 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 25, 2000 at 11:52:18AM -0400, Tim Grzechowski wrote: > We tried using the freebie stuff with Xfree86 4.0.1 but found > it to be extreamly buggy... both on Linux and FreeBSD. Could you describe `extremely buggy'? Did you open any problem reports with the XFree86 guys? I have been using the Matrox G400 Dual-Head AGP card with XFree86 4.0.1 + Matrox's Linux driver since August 18 with zero problems. Works perfectly. I was previously using a Matrox Millenium II AGP + Matrox Millenium II PCI since the XFree86 3.9 days. Like you, I will kill anyone who attempts to make off with one of my monitors :-) -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / 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 Aug 25 12:33: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id C1F0B37B423 for ; Fri, 25 Aug 2000 12:32:58 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e7PJWtr36485; Sat, 26 Aug 2000 04:32:55 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: takawata@shidahara1.planet.sci.kobe-u.ac.jp Cc: acpi-jp@jp.freebsd.org, hackers@freebsd.org, iwasaki@jp.freebsd.org Subject: Re: Merging ACPI related code is on the way. In-Reply-To: <200008251120.UAA50540@shidahara1.planet.sci.kobe-u.ac.jp> References: <200008251120.UAA50540@shidahara1.planet.sci.kobe-u.ac.jp> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000826043254B.iwasaki@jp.FreeBSD.org> Date: Sat, 26 Aug 2000 04:32:54 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have committed orthognal part of ACPI driver. > The rest part will be committed after a few days. > I put the part at . > > This can be applied for HEAD. Please test and report about it if there > is serious problem,such as breaking build. It seems OK for me. BTW, I've just added new file in CVS; sys/dev/acpi/acpi_powerres.c. You need to have the following line in sys/conf/files. dev/acpi/acpi_powerres.c optional acpi Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 13:24: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 8499337B423; Fri, 25 Aug 2000 13:24:02 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13SQ17-0007ZL-00; Fri, 25 Aug 2000 22:23:57 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e7PKOep20703; Fri, 25 Aug 2000 22:24:40 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008252024.e7PKOep20703@grimreaper.grondar.za> To: Johan Kruger Cc: FreeBSD Current , freebsd-hackers@FreeBSD.ORG Subject: Re: perlcc in current - xs_init and boot_DynaLoader References: In-Reply-To: ; from Johan Kruger "Fri, 25 Aug 2000 11:56:12 +0200." Date: Fri, 25 Aug 2000 22:24:40 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If i do a perlcc test.pl i get the folllowing , in CURRENT ? > Must i define something beforehand, or is it broken ? I'll take a look... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 18:29:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fishtank.hermans.ab.ca (fishtank.hermans.ab.ca [209.115.211.177]) by hub.freebsd.org (Postfix) with ESMTP id 8F54837B43F for ; Fri, 25 Aug 2000 18:29:39 -0700 (PDT) Received: from desktopnt (desktop-nt [192.168.27.100]) by fishtank.hermans.ab.ca (8.9.3/8.9.3) with SMTP id TAA28466 for ; Fri, 25 Aug 2000 19:29:39 -0600 (MDT) (envelope-from freebsd@hermans.ab.ca) From: "Jamie Hermans" To: Subject: Auto DMA vs. Manual DMA Settings... FBSD 3.51 Date: Fri, 25 Aug 2000 19:29:38 -0600 Message-ID: <001001c00efd$1a5840c0$641ba8c0@hermans.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reposted to -HACKERS Hiya... I am having an issue with the wd driver (from FBSD 3.51). Once a customer kernel (having the flags 0xa0ffa0ff for wd) is booted, I get screen-full's of this error message when there is any hard drive access: DMA failure, DMA status 5 I can "slow down" or degrade my DMA settings in the BIOS to avoid this message, but I'm sure I am taking a performance penalty in doing this. For more history, please refer to: http://www.freebsd.org/cgi/mid.cgi?db=mid&id=19991220124638.B37447@web.net ... where this was covered back in December 1999 - I had hoped that this would have been resolved by now. System hardware - Maxtor UDMA66 drive, motherboard only supports UDMA33 however, so that's not really an issue. My question ... can I use the ad driver from 4.x with 3.51-RELEASE? This problem doesn't occur under 4.0 or 4.1-RELEASE/STABLE. If this is possible ... how? Thanks for any thoughts (or even solutions) :) Regards ... Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 21: 2:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id 4A1DC37B424 for ; Fri, 25 Aug 2000 21:02:25 -0700 (PDT) Received: from bsdevil.meta.net.ob.kamp.net (port-50.d.kamp.de [195.62.120.242]) by mail-ob.kamp.net (8.10.1/8.10.1) with ESMTP id e7Q42FV29123 for ; Sat, 26 Aug 2000 06:02:17 +0200 Date: Sat, 26 Aug 2000 06:02:15 +0200 Message-Id: <200008260402.e7Q42FV29123@mail-ob.kamp.net> From: Farid Hajji To: hackers@freebsd.org Subject: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) X-Mailer: Emacs-20.6.1/FreeBSD-5.0-CURRENT Reply-To: farid.hajji@ob.kamp.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, [please Cc: to me, since I'm not subscribed to this list. Thanks] are there plans to replace FreeBSD's libc with GNU glibc in the near or medium future? Linux moved also from it's own libc5 to glibc (=libc6) some time ago and it may be useful to do the same in FreeBSD too. The reason I'm asking this is to investigate further, wether the Hurd can be dropped into a FreeBSD system as an alternative to the current FreeBSD kernel. As you probably know, Keio University and NTT provide a RT-Mach/Lites package that can be installed into a FreeBSD 2.2.8 system and which, when booted, provides binary compatibility with the means of the system call redirection feature of Mach. Such a system feels like an original FreeBSD system and is a good development platform for Mach programming. The Lites server used by RT-Mach is a user-land single OS-Server that contains most of the 4.4 BSD-Lite code to emulate a *BSD kernel. It is still monolithic in the sense that it is a single task with multiple threads. As opposed to the single-OS Server Lites, the Hurd is a set of OS-Servers that run on top of Mach and that seek to replace Unix. They actually provide Unix API compatibility through the current version of glibc which translates Unix calls into (mainly) RPCs to the appropriate Hurd servers. The Hurd is still under development but is already working reasonably well for development purposes. Actually, people at Debian are trying to put up a debian-style distribution of GNU/Hurd, that will resemble Debian/Linux. Once such a systems is ready, Hurd-0.3 will be released. As FreeBSD user, I strongly dislike the debian style currently favorized but there is not much that can be done against it. What I'm trying to do, is to figure out how to add binary compatibility to the Hurd in the same way than is done with RT-Mach/Lites, so that ultimatly, the Hurd/Mach can be added as an alternative kernel to a current FreeBSD distribution. This is one way how the Hurd can be installed in a FreeBSD distribution: 1. Replace libc with glibc and create a glibc-based FreeBSD distribution. The Hurd/Glibc/Mach can now be compiled like a regular FreeBSD port and installed in a subdirectory somewhere (say: /usr/local/hurd). Rebooting the Mach kernel would load the Hurd servers first and would then invoke the regular FreeBSD rc scripts. Each FreeBSD binary that is linked against FreeBSD glibc would now be transparently relinked against the Hurd's glibc, which would call the servers and Mach in appropriate ways. Other libs [that don't contain traps] can be used unchanged. 2. Statically linked binaries and other binaries (like Linux etc...) would need more work to be supported. There, the syscall redirection mechanism of Mach would still be needed. Should this mechanism be implemented in the Hurd, providing binary compatibility to FreeBSD could be possible, even without having to move FreeBSD to glibc in the first place. An easier and probably faster way would be to provide specially compiled versions of those static programs that would be used instead of the FreeBSD ones while running the Hurd. Yet having the possibility to transparently link FreeBSD binaries against the Hurd's glibc instead of the hypothetical FreeBSD glibc would have the enormous advantage to reduce the syscall overhead that is induced by the syscall redirection facility. What would you suggest? -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 21: 6:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D076337B42C; Fri, 25 Aug 2000 21:06:13 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA58490; Fri, 25 Aug 2000 21:06:13 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Aug 2000 21:06:13 -0700 (PDT) From: Kris Kennaway To: Farid Hajji Cc: hackers@freebsd.org Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) In-Reply-To: <200008260402.e7Q42FV29123@mail-ob.kamp.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 Sat, 26 Aug 2000, Farid Hajji wrote: > Hello, > > [please Cc: to me, since I'm not subscribed to this list. Thanks] > > are there plans to replace FreeBSD's libc with GNU glibc in the near > or medium future? I think I can safely say: "No." Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 21:16:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7F04A37B42C; Fri, 25 Aug 2000 21:16:20 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA59197; Fri, 25 Aug 2000 21:16:20 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 25 Aug 2000 21:16:20 -0700 (PDT) From: Kris Kennaway To: Farid Hajji Cc: hackers@freebsd.org Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) 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 Fri, 25 Aug 2000, Kris Kennaway wrote: > On Sat, 26 Aug 2000, Farid Hajji wrote: > > > Hello, > > > > [please Cc: to me, since I'm not subscribed to this list. Thanks] > > > > are there plans to replace FreeBSD's libc with GNU glibc in the near > > or medium future? > > I think I can safely say: > > "No." To be slightly less glib[c]: Linking a FreeBSD system against glibc would cause every userland binary on such a system to become "infected" by the GPL, resulting in obvious chaos and pandemonium :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 21:16:30 2000 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 AA4C537B440 for ; Fri, 25 Aug 2000 21:16:25 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id VAA28112; Fri, 25 Aug 2000 21:15:33 -0700 (PDT) Message-Id: <200008260415.VAA28112@implode.root.com> To: farid.hajji@ob.kamp.net Cc: hackers@FreeBSD.ORG Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) In-reply-to: Your message of "Sat, 26 Aug 2000 06:02:15 +0200." <200008260402.e7Q42FV29123@mail-ob.kamp.net> From: David Greenman Reply-To: dg@root.com Date: Fri, 25 Aug 2000 21:15:33 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >[please Cc: to me, since I'm not subscribed to this list. Thanks] > >are there plans to replace FreeBSD's libc with GNU glibc in the near >or medium future? Linux moved also from it's own libc5 to glibc (=libc6) >some time ago and it may be useful to do the same in FreeBSD too. No, that is not going to happen. >The reason I'm asking this is to investigate further, wether the Hurd >can be dropped into a FreeBSD system as an alternative to the current >FreeBSD kernel. Using a non-FreeBSD kernel with GNU libc would pretty much make it not FreeBSD anymore. FreeBSD is what it is; if you don't like most of it, then may I suggest that you use one of the alternatives that better suits your needs. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - 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 Fri Aug 25 21:17:35 2000 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 4151637B422 for ; Fri, 25 Aug 2000 21:17:33 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7Q4HTt10671; Fri, 25 Aug 2000 21:17:29 -0700 (PDT) Date: Fri, 25 Aug 2000 21:17:29 -0700 From: Alfred Perlstein To: Farid Hajji Cc: hackers@FreeBSD.ORG Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) Message-ID: <20000825211728.G1209@fw.wintelcom.net> References: <200008260402.e7Q42FV29123@mail-ob.kamp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008260402.e7Q42FV29123@mail-ob.kamp.net>; from farid.hajji@ob.kamp.net on Sat, Aug 26, 2000 at 06:02:15AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Farid Hajji [000825 21:03] wrote: > Hello, > > [please Cc: to me, since I'm not subscribed to this list. Thanks] > > are there plans to replace FreeBSD's libc with GNU glibc in the near > or medium future? Linux moved also from it's own libc5 to glibc (=libc6) > some time ago and it may be useful to do the same in FreeBSD too. hahahaha no. > The reason I'm asking this is to investigate further, wether the Hurd > can be dropped into a FreeBSD system as an alternative to the current > FreeBSD kernel. I'm going to have to cut you short here, what's them point of this? I read the rest of your message and basically what you seem to want to do is port the FreeBSD userland to Hurd, that's what you need to do. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 21:22: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 9E1D437B43E; Fri, 25 Aug 2000 21:21:59 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13SXaN-00009E-00; Fri, 25 Aug 2000 22:28:51 -0600 Message-ID: <39A74783.FF8CF3AF@softweyr.com> Date: Fri, 25 Aug 2000 22:28:51 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Farid Hajji , hackers@freebsd.org Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 26 Aug 2000, Farid Hajji wrote: > > > Hello, > > > > [please Cc: to me, since I'm not subscribed to this list. Thanks] > > > > are there plans to replace FreeBSD's libc with GNU glibc in the near > > or medium future? > > I think I can safely say: > > "No." Not only "No" but "Hell No". Why would we want to replace our functional, proven libc code with the GPL virus? -- "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 Aug 25 21:24:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id 4CD1237B43E for ; Fri, 25 Aug 2000 21:24:54 -0700 (PDT) Received: from holly.dyndns.org ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZV00HANSZ8TF@mta5.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Fri, 25 Aug 2000 23:11:32 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id XAA74481; Fri, 25 Aug 2000 23:11:13 -0500 (CDT envelope-from chris) Date: Fri, 25 Aug 2000 23:11:12 -0500 From: Chris Costello Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) In-reply-to: <200008260402.e7Q42FV29123@mail-ob.kamp.net> To: Farid Hajji Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000825231112.K60058@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <200008260402.e7Q42FV29123@mail-ob.kamp.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, August 26, 2000, Farid Hajji wrote: > are there plans to replace FreeBSD's libc with GNU glibc in the near > or medium future? Linux moved also from it's own libc5 to glibc (=libc6) > some time ago and it may be useful to do the same in FreeBSD too. There are no such plans for that type of downgrade. If the software you need to use externally calls nonstandard C library functions consider porting the library and linking it manually, or fixing the software: cc -o my-hurd-program -nostdlib -lglibc ... or something along those lines. -- |Chris Costello |You can't make a program without broken egos. `--------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 21:57: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id BC71E37B43C for ; Fri, 25 Aug 2000 21:56:58 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7Q4uuK14033; Fri, 25 Aug 2000 21:56:56 -0700 (PDT) Date: Fri, 25 Aug 2000 21:56:56 -0700 (PDT) From: Doug White To: Jamie Hermans Cc: hackers@FreeBSD.ORG Subject: Re: Auto DMA vs. Manual DMA Settings... FBSD 3.51 In-Reply-To: <001001c00efd$1a5840c0$641ba8c0@hermans.ab.ca> 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, 25 Aug 2000, Jamie Hermans wrote: > I am having an issue with the wd driver (from FBSD 3.51). Once a customer > kernel (having the flags 0xa0ffa0ff for wd) is booted, I get screen-full's > of this error message when there is any hard drive access: > > DMA failure, DMA status 5 > > I can "slow down" or degrade my DMA settings in the BIOS to avoid this > message, but I'm sure I am taking a performance penalty in doing this. It may be that: a) your cable is damaged; b) your system is too noisy; c) your disks proclaim UDMA capability but can't actually deliver it. > http://www.freebsd.org/cgi/mid.cgi?db=mid&id=19991220124638.B37447@web.net > > ... where this was covered back in December 1999 - I had hoped that this > would have been resolved by now. > > System hardware - Maxtor UDMA66 drive, motherboard only supports UDMA33 > however, so that's not really an issue. I'd suggest upgrading to a proper DMA66 cable and see if that helps. > My question ... can I use the ad driver from 4.x with 3.51-RELEASE? This > problem doesn't occur under 4.0 or 4.1-RELEASE/STABLE. If this is possible > ... how? No, the ata driver is not available on 3.X. 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 Aug 25 22:23: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id 1243437B422 for ; Fri, 25 Aug 2000 22:23:06 -0700 (PDT) Received: (qmail 6468406 invoked from network); 26 Aug 2000 05:23:04 -0000 Received: from r121m50.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.50]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 26 Aug 2000 05:23:04 -0000 Message-ID: <39A754D0.834409BE@cybercable.fr> Date: Sat, 26 Aug 2000 07:25:36 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: hackers@freebsd.org Subject: Re: sysctl from kernel References: <4748.967055662@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your help ! If someone would be kind enough to answer them, I have a few other questions. I'm currently trying to modify sysctl_kern_proc() function in src/sys/kern/kern_proc.c But, to modify it, I must understand it first ;-) First, this sysctl is supposed to give the list of the running processes, but where this information is stored ? The function returns an int so it's probably not this :-) Second, what is an "oib" ? There are a lot of oib related stuff with sysctl and I can't understand what it is. Thanks for all future help. Maxime Henrion Poul-Henning Kamp wrote: > In message <39A41897.173F00@cybercable.fr>, Maxime Henrion writes: > > Hi, > > > >I'm new to the FreeBSD kernel and I wanted to know what are the good > >methods to read a sysctl value from the kernel. Is it the same interface > >as in user-space ? > > > >Any help or links to some documentation would be greatly appreciated :) > > Look at the kernel_sysctl() function in src/sys/kern/kern_sysctl.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 23:59:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 8DC2D37B424 for ; Fri, 25 Aug 2000 23:59:15 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id AAA04702; Fri, 25 Aug 2000 00:29:59 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008250729.AAA04702@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: pran@procsys.com Cc: freebsd-hackers@freebsd.org Subject: Re: Memory Mapping -2 In-reply-to: Your message of "Fri, 25 Aug 2000 12:44:18 +0530." <39A61CCA.2DB82AFF@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Aug 2000 00:29:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I am trying to write a PCI ethernet driver for FreeBSD 3.4 release. Will you folks please give up and move to 4.x? 3.x is *dead*. 8) > I have some questions > > 1. How can I convert physical address to virtual address . What I want > is to read the physical address from the device register and to copy it > to host memory. From my earlier post I found that I can use vtopys > macro to convert virtual to physical address. Now I want to do the > reverse. You don't do it like this. Firstly, you shouldn't use vtophys, you should be using busdma. Secondly, a physical page can appear in more than one virtual location. Typically your ethernet hardware will have a descriptor associated with each buffer, and you need to use the descriptor to backtrack to your control structure which references the actual virtual address you care about. > 2. What are things should I do if I want the driver to work on alpha > platform also. a) Move to 4.x b) Use the busspace and busdma interfaces -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 23:59:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id D754E37B440 for ; Fri, 25 Aug 2000 23:59:17 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA00847; Thu, 24 Aug 2000 19:32:56 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008250232.TAA00847@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Isaac Waldron" Cc: freebsd-hackers@freebsd.org Subject: Re: Size limits for kld's? In-reply-to: Your message of "Sun, 13 Aug 2000 12:10:23 EDT." <003e01c00540$fecf05c0$0100000a@waldron.house> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Aug 2000 19:32:56 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Unfortunately, while the open and close functions I wrote are called > correctly, the ioctl function is never called. A call to ioctl(filehdl, > PLEX86_IOCTL, int) returns an error, and a perror("ioctl") prints > "ioctl: Bad Address." I know that the ioctl number is correct, and it > was defined with the proper _IO* macro. The file handle also opens just > fine, as the printf's in my open function are executed and show on the > console. AFAIK, that error would be caused by an EFAULT being returned > somewhere in the chain. > > What I'm asking is, what would cause some of the functions referenced by > my driver's cdevsw to not be able to be called? Are there size limits > on functions in a kld? Or a limit on the total size of a kld? Nope. But the third argument to ioctl() is typically the *address* of your integer parameter. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 25 23:59:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 31FE537B422 for ; Fri, 25 Aug 2000 23:59:20 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA00857; Thu, 24 Aug 2000 19:33:02 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008250233.TAA00857@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Katsushi Kobayashi Cc: freebsd-hackers@freebsd.org Subject: Re: IEEE1394 driver system for -current In-reply-to: Your message of "Sat, 19 Aug 2000 19:00:26 +0900." <399E5A33.B552E780@koganei.wide.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Aug 2000 19:33:02 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I announced IEEE1394 device driver on FREENIX'99 (sorry not > on '00). I have caught up -current version at this time. > > The latest -current driver patch can be found at: > > ftp://ftp.uec.ac.jp/pub/firewire/beta/ > > I hope you success to make a kernel on your source tree. Thanks again for the reminder about this. I've taken some time to play a little with the code and some hardware, and I have some comments on the code and what needs to be changed before it would be suitable for committing. > The driver function is still limited and may include many > bugs since the driver has been used for specific purrposes, > e.g., the driver have not supported SCSI (CAM) storage on > IEEE1394 and not been complient to loadable kernel module. > However, I think it is better to merge -current on this time and > maintain on it compared with taking a effort in independent. > > Let me know what shall I do to merge my code. There are several things that need to be fixed. I'm not going to be nice about the code, because it needs some major work before it is ready, but I do think that it is worth using your code (and your skills) in some form. 1) The code is very messy. This makes it hard to read. It needs to be reformatted before committing to reduce whitespace/style changes afterwards. 2) There are a lot of "magic numbers" (numeric values for registers and so forth) rather than defined constants. This makes it hard to work out what parts of the code are doing. 3) The code lacks structure. There are some very clear divisions that should be made between the various components in the 1394 stack, and these are not being made. Fixing this will involve moving a lot of code around, and should be done before the code is committed. 1394 can be looked at as being quite similar to USB (the predominant interface model is OHCI, also used for USB). The obvious software components are: a) Host adapter driver (eg. TI Lynx, NEC, Adaptec, etc.) b) Generic 1394 layer c) Peripheral/protocol driver layer (eg. DV, CAM shim, etc) c') Layered peripheral/protocol driver layer The interface between layers a) and b), and between layers b) and c) and between layers c) and c') should all be clearly defined. Using newbus and defining these interactions in terms of parent-child relationships and bus methods will make this very easy. Having said so many cruel things about your code, it's clear that you've spent a lot of time making your stack work, and during that time you must have accumulated a lot of experience with these peripherals. I understand that Warner has proposed you be granted CVS commit access in order to work on your code in the FreeBSD CVS repository, and I'm in favour of this. I would, however, like to see the above issues addressed before the initial import. One option that you might want to consider is working with Bill Paul on the cleanup and restructuring process. Bill has a lot of experience with network-like peripherals, and with the way in which we like things to be done. In combination with your experience with 1394 in general, I think this would result in some very good and useful code. I've already spoken to Bill about this, and he seemed interested. (Apologies if I'm dumping you in it here, pal. 8) In summary, then, I would encourage you to consider the points above, and engage in some discussion (either on the -arch list or on a new freebsd-1394 list) about how to go about reorganising and cleaning up your code ready for committing as soon as practical. Regards, -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 0:13:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id 06D3B37B423 for ; Sat, 26 Aug 2000 00:13:43 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA83100; Sat, 26 Aug 2000 09:13:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: farid.hajji@ob.kamp.net Cc: hackers@FreeBSD.ORG Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) In-Reply-To: Your message of "Sat, 26 Aug 2000 06:02:15 +0200." <200008260402.e7Q42FV29123@mail-ob.kamp.net> Date: Sat, 26 Aug 2000 09:13:40 +0200 Message-ID: <83098.967274020@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008260402.e7Q42FV29123@mail-ob.kamp.net>, Farid Hajji writes: >Hello, > >[please Cc: to me, since I'm not subscribed to this list. Thanks] > >are there plans to replace FreeBSD's libc with GNU glibc in the near >or medium future? Linux moved also from it's own libc5 to glibc (=libc6) >some time ago and it may be useful to do the same in FreeBSD too. Only if glibc is released under a BSD license *could* this happen, and in that case it would still be up to an actual comparison of the code. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 0:18:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id 1BAED37B423 for ; Sat, 26 Aug 2000 00:18:13 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA83250; Sat, 26 Aug 2000 09:18:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Maxime Henrion Cc: hackers@FreeBSD.ORG Subject: Re: sysctl from kernel In-Reply-To: Your message of "Sat, 26 Aug 2000 07:25:36 +0200." <39A754D0.834409BE@cybercable.fr> Date: Sat, 26 Aug 2000 09:18:10 +0200 Message-ID: <83248.967274290@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A754D0.834409BE@cybercable.fr>, Maxime Henrion writes: >Thanks for your help ! > >If someone would be kind enough to answer them, I have a few other questions. >I'm currently trying to modify sysctl_kern_proc() function in >src/sys/kern/kern_proc.c First: look at sysctl(3) sysctl can read and set variables, so you pass it the "new" value and a buffer for the "old" value. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 0:26:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 6408C37B422; Sat, 26 Aug 2000 00:26:27 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id AAA00732; Sat, 26 Aug 2000 00:40:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008260740.AAA00732@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: pran@procsys.com, freebsd-hackers@freebsd.org Subject: Re: Memory Mapping -2 In-reply-to: Your message of "Fri, 25 Aug 2000 00:29:59 PDT." <200008250729.AAA04702@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Aug 2000 00:40:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, > > > > I am trying to write a PCI ethernet driver for FreeBSD 3.4 release. BTW, just checking out the Procsys website I assume that you're working on driver(s) for your 'Nakajima' PCI NICs. If that's the case, and also assuming that these are based on off-the-shelf MAC parts, have you checked to make sure there isn't already a driver? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 2:14:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id EB1F037B422; Sat, 26 Aug 2000 02:14:24 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13Sc2f-000GZe-00; Sat, 26 Aug 2000 11:14:21 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e7Q9F9p25033; Sat, 26 Aug 2000 11:15:09 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200008260915.e7Q9F9p25033@grimreaper.grondar.za> To: Mark Murray Cc: Johan Kruger , FreeBSD Current , freebsd-hackers@FreeBSD.ORG Subject: Re: perlcc in current - xs_init and boot_DynaLoader References: <200008252024.e7PKOep20703@grimreaper.grondar.za> In-Reply-To: <200008252024.e7PKOep20703@grimreaper.grondar.za> ; from Mark Murray "Fri, 25 Aug 2000 22:24:40 +0200." Date: Sat, 26 Aug 2000 11:15:09 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If i do a perlcc test.pl i get the folllowing , in CURRENT ? > > Must i define something beforehand, or is it broken ? > > I'll take a look... Looks like perl brokenness. The missing boot_DynaLoader is in DynaLoader.a, but there is no way of linking it in. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 8:20:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 50BFA37B423 for ; Sat, 26 Aug 2000 08:20:53 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7QFJaC09611 for ; Sat, 26 Aug 2000 08:19:36 -0700 (PDT) Date: Sat, 26 Aug 2000 08:19:36 -0700 (PDT) From: FengYue To: freebsd-hackers@freebsd.org Subject: SYN flood prevention methods 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 know this is an old topic but I don't seem to find answers to my questions in the mailing list archives. I'm wondering why FreeBSD did not implement the SYN cookies method that is currently implemented in Linux? To my best understanding, SYN cookie seems to be a better method against SYS flood than the random drop method. It seems both OpenBSD and FreeBSD have implemented the random drop method. I guess there are must be some "bad things" about SYN cookies that I don't know about. Also, I was looking at the netinet/ code this morning but was not able to find how the seq backlog queue is created/defined. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 9:26:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 8E12D37B423 for ; Sat, 26 Aug 2000 09:26:51 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13Sitz-0000ER-00; Sat, 26 Aug 2000 10:33:51 -0600 Message-ID: <39A7F16F.3E073F17@softweyr.com> Date: Sat, 26 Aug 2000 10:33:51 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: FengYue Cc: freebsd-hackers@freebsd.org Subject: Re: SYN flood prevention methods References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FengYue wrote: > > Hi, I know this is an old topic but I don't seem to find answers > to my questions in the mailing list archives. > > I'm wondering why FreeBSD did not implement the SYN cookies method > that is currently implemented in Linux? To my best understanding, > SYN cookie seems to be a better method against SYS flood than > the random drop method. It seems both OpenBSD and FreeBSD have > implemented the random drop method. I guess there are must be some > "bad things" about SYN cookies that I don't know about. A quick search of the net, hackers, and security mail lists turned up a number of hits for "syn cookie", including several with URL references to weaknesses in the scheme. http://www.FreeBSD.org/cgi/search.cgi?words=syn+cookie&max=50&sort=score&source=freebsd-security&source=freebsd-hackers&source=freebsd-net -- "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 Sat Aug 26 10:21:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id 7A75A37B43E for ; Sat, 26 Aug 2000 10:21:12 -0700 (PDT) Received: from bsdevil.meta.net.ob.kamp.net (port-43.d.kamp.de [195.62.120.235]) by mail-ob.kamp.net (8.10.1/8.10.1) with ESMTP id e7QHL8V15403 for ; Sat, 26 Aug 2000 19:21:09 +0200 Date: Sat, 26 Aug 2000 19:21:08 +0200 Message-Id: <200008261721.e7QHL8V15403@mail-ob.kamp.net> From: Farid Hajji To: hackers@FreeBSD.org In-reply-to: <39A74783.FF8CF3AF@softweyr.com> (message from Wes Peters on Fri, 25 Aug 2000 22:28:51 -0600) Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) X-Mailer: Emacs-20.6.1/FreeBSD-5.0-CURRENT Reply-To: farid.hajji@ob.kamp.net References: <39A74783.FF8CF3AF@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > are there plans to replace FreeBSD's libc with GNU glibc in the near > > > or medium future? Thanks for all your replies. I perfectly understand the reasons for avoiding GNU copylefted code like glibc in FreeBSD. Using the Hurd/Mach as kernel replacement for FreeBSD would indeed require adding the syscall emulation feature like in Lites/RT-Mach, linking against FreeBSD's libc and adding missing functionality as stubs. I just hoped it would be a bit easier ;-) BTW, I don't have any problems with the FreeBSD kernel itself or its libc. They are excellent and I'm using them both at home and exclusively for mission critical applications. Keep up the good work! -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 10:39: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 235E737B42C for ; Sat, 26 Aug 2000 10:39:04 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id KAA44502; Sat, 26 Aug 2000 10:38:55 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: farid.hajji@ob.kamp.net Cc: hackers@FreeBSD.ORG Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) In-Reply-To: Message from Farid Hajji of "Sat, 26 Aug 2000 06:02:15 +0200." <200008260402.e7Q42FV29123@mail-ob.kamp.net> Date: Sat, 26 Aug 2000 10:38:55 -0700 Message-ID: <44497.967311535@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > are there plans to replace FreeBSD's libc with GNU glibc in the near > or medium future? Linux moved also from it's own libc5 to glibc (=libc6) > some time ago and it may be useful to do the same in FreeBSD too. Nope. The license for glibc is not one we'd want to use for such a core component (which is less optional than, say, grep) nor does our libc lack for the kinds of features which would make switching necessary. Those wishing to play with the HURD under FreeBSD can simply add glibc to the list of components they need to bring over; they needs of the few do not outweigh the needs of the many in this case. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 11: 1:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id F036C37B42C; Sat, 26 Aug 2000 11:01:08 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Sat, 26 Aug 2000 19:00:58 +0100 Message-ID: <39A805D7.95A813AF@cs.ucl.ac.uk> Date: Sat, 26 Aug 2000 19:00:55 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Eric Kozowski Cc: Theo PAGTZIS , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: <39A54A50.1151A1A@cs.ucl.ac.uk> <20000824104345.G12584@schooner.svjava.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Kozowski wrote: > On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > > Hi all, > > > > Has anyone managed to configure a fbsd box as a Wavelan BS ? > > yes it's easy. which wavelan card are you using? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Wavelan Orinoco...Silver (with the ISA bridge) I would like to know how but ...do you really mean that the fbsd box is acting a base station with the wavelan card in *infrastructure* mode or do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc mode is very easy...what I want is to have the fbsd base station act as an access point where _many_ clients can associate....not just one.... so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to peer connection ) or infrastructure mode...??? If it works in ad-hoc mode the PCF and DCF functions are not really happening...which is what a BS is all about... Don't you agree? (or anyone else) Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 11: 3:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fishtank.hermans.ab.ca (fishtank.hermans.ab.ca [209.115.211.177]) by hub.freebsd.org (Postfix) with ESMTP id B411D37B422 for ; Sat, 26 Aug 2000 11:03:23 -0700 (PDT) Received: from desktopnt (desktop-nt [192.168.27.100]) by fishtank.hermans.ab.ca (8.9.3/8.9.3) with SMTP id MAA64294; Sat, 26 Aug 2000 12:03:20 -0600 (MDT) (envelope-from freebsd@hermans.ab.ca) From: "Jamie Hermans" To: "'Doug White'" Cc: Subject: RE: Auto DMA vs. Manual DMA Settings... FBSD 3.51 Date: Sat, 26 Aug 2000 12:03:20 -0600 Message-ID: <000801c00f87$ebb84ea0$641ba8c0@hermans.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Doug... Actually, it is a proper UDMA66 cable (so agrees the Promise UDMA66 controller I was playing with a while back). But ... I'm not looking for UDMA66 speeds, like I mentioned - the motherboard only supports UDMA33 anyways. With a tip from another reply, I found this on Maxtor's website: (although my ASUS board is much newer than Oct 98, it's a start) Overview: Some older Ultra DMA 33 motherboards with older BIOS' (revision date 10/28/98 and older) have exhibited compatibility issues with Ultra DMA/66/100 drives. The symptom manifests itself as a system hangs at boot, and performance problems. On some motherboards the system does not properly check the UDMA setting returned by the drive. The end result is that the motherboard attempts to set itself up in an unsupported mode. These issues arise because of a bug in the system's BIOS, NOT a problem with the Maxtor hard drive. Some System's will also have performance problems due to the controller chipset. To eliminate this problem, Maxtor has developed the UDMAUPDT.EXE ... Jamie -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Doug White Sent: Friday, August 25, 2000 10:57 pm To: Jamie Hermans Cc: hackers@FreeBSD.ORG Subject: Re: Auto DMA vs. Manual DMA Settings... FBSD 3.51 It may be that: a) your cable is damaged; b) your system is too noisy; c) your disks proclaim UDMA capability but can't actually deliver it. I'd suggest upgrading to a proper DMA66 cable and see if that helps. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 11:14:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 954B137B423; Sat, 26 Aug 2000 11:14:25 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7QIdja02282; Sat, 26 Aug 2000 14:39:45 -0400 (EDT) Date: Sat, 26 Aug 2000 14:39:45 -0400 (EDT) From: Jim Flowers To: Theo PAGTZIS Cc: Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS In-Reply-To: <39A805D7.95A813AF@cs.ucl.ac.uk> 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 Last I checked the wi driver will not do IBSS and says so in the documentation. I also tried it and couldn't get anywhere. Would be nice. Even better would be to use the algos in their office router stuff. We're looking at that now. We currently use a fbsd box to connect the Internet to a WavePointII on one frequency and then on a second frequency we connect multipoint users with fbsd boxes. Works very well although the WavePointII has to be monitored continuously. Bandwidth varies from 600 kbps to about 3000 kbps. Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Sat, 26 Aug 2000, Theo PAGTZIS wrote: > Eric Kozowski wrote: > > > On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > > > Hi all, > > > > > > Has anyone managed to configure a fbsd box as a Wavelan BS ? > > > > yes it's easy. which wavelan card are you using? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > Wavelan Orinoco...Silver (with the ISA bridge) > > I would like to know how but ...do you really mean that the fbsd box is > acting a base station with the wavelan card in *infrastructure* mode or > do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc > mode is very easy...what I want is to have the fbsd base station act as > an access point where _many_ clients can associate....not just one.... > > so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to > peer connection ) or infrastructure mode...??? > > If it works in ad-hoc mode the PCF and DCF functions are not really > happening...which is what a BS is all about... > > Don't you agree? (or anyone else) > > > Theo > > > > 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 Sat Aug 26 11:28:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 6E74837B43C; Sat, 26 Aug 2000 11:28:09 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Sat, 26 Aug 2000 19:28:04 +0100 Message-ID: <39A80C31.2FB487D5@cs.ucl.ac.uk> Date: Sat, 26 Aug 2000 19:28:01 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Jim Flowers Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Flowers wrote: > Last I checked the wi driver will not do IBSS and says so in the > documentation. I also tried it and couldn't get anywhere. Would be nice. > Jim, do you mean Bill's driver doesn't do adhoc mode...? IBSS is independent BSS which is adhoc mode...did you mean to say BSS ?? > > Even better would be to use the algos in their office router stuff. We're > looking at that now. > Couldn't agree more... > > We currently use a fbsd box to connect the Internet to a WavePointII on > one frequency and then on a second frequency we connect multipoint users > with fbsd boxes. > wait a minute...a single WPII bridge is connected behind a fbsd router box.....fine...now one freq is to act as a portal for the ...Internet?? and the other is to act as an AP for the nodes... but the BS can operate in a single freq...cannot switch between different frequencies (unless you set it manually but this is a different cell altogether...from the portal cell to Inet..) something is not quite right here...could you explain a little? > > Works very well although the WavePointII has to be monitored > continuously. Bandwidth varies from 600 kbps to about 3000 kbps. why does the WPII have to be monitored? In any case the AP function is not effected in the fbsd box but on lucent's bridge...well that is what I am doing....for the moment... Do you have any code that is checking out the office router algos? I would appreciate a peek.... :) Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 18:23:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 8C29D37B43E; Sat, 26 Aug 2000 18:23:04 -0700 (PDT) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id SAA06785; Sat, 26 Aug 2000 18:23:01 -0700 (PDT) Date: Sat, 26 Aug 2000 18:23:01 -0700 From: Eric Kozowski To: Theo PAGTZIS Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS Message-ID: <20000826182301.C6587@schooner.svjava.com> References: <39A54A50.1151A1A@cs.ucl.ac.uk> <20000824104345.G12584@schooner.svjava.com> <39A805D7.95A813AF@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <39A805D7.95A813AF@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Sat, Aug 26, 2000 at 07:00:55PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 26, 2000 at 07:00:55PM +0100, Theo PAGTZIS wrote: > Eric Kozowski wrote: > > > On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: > > > Hi all, > > > > > > Has anyone managed to configure a fbsd box as a Wavelan BS ? > > > > yes it's easy. which wavelan card are you using? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > Wavelan Orinoco...Silver (with the ISA bridge) > > I would like to know how but ...do you really mean that the fbsd box is > acting a base station with the wavelan card in *infrastructure* mode or > do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc > mode is very easy...what I want is to have the fbsd base station act as > an access point where _many_ clients can associate....not just one.... > > so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to > peer connection ) or infrastructure mode...??? a wavelan accesspoint operates in infrastructe mode, which means that the client can only talk to the base station/accesspoint. ad-hoc means clients can contact each other directly. the wi driver supports both modes. i'm running my wavelan gold card in BSS mode to an apple airport base station. > If it works in ad-hoc mode the PCF and DCF functions are not really > happening...which is what a BS is all about... not sure what you mean by pcf and dcf. i do know that power saving mode will not work in ad-hoc mode. > Don't you agree? (or anyone else) with what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 20: 1:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc26.worldnet.att.net (mtiwmhc26.worldnet.att.net [204.127.131.51]) by hub.freebsd.org (Postfix) with ESMTP id BEFDF37B422; Sat, 26 Aug 2000 19:58:57 -0700 (PDT) Received: from default ([12.70.5.164]) by mtiwmhc26.worldnet.att.net (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20000827025834.CNMU9297.mtiwmhc26.worldnet.att.net@default>; Sun, 27 Aug 2000 02:58:34 +0000 From: hspio@worldnet.att.net To: hackers@FreeBSD.ORG, owner-freebsd-hackers-digest@FreeBSD.ORG Date: Sat, 26 Aug 2000 22:53:00 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: UNSUBSCRIBE REMOVE Message-ID: <39A84A4C.20198.175588@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Aug 2000, at 9:47, freebsd-hackers-digest wrote: > > freebsd-hackers-digest Tuesday, August 22 2000 Volume 04 : Number 927 > > > > In this issue: > [PATCH] 3-button microsoft-type serial mouse > Updated driver for Mylex 160/170/352/2000/3000 controllers > UNSUBSCRIBE > Re: quotas and file creditentials > Re: [PATCH] 3-button microsoft-type serial mouse > Re: quotacheck on a live filesystem; safe? (fwd) > Re: freebsd and non-preemtive threads > Re: freebsd and non-preemtive threads > Memory Mapping > Re: Memory Mapping > Advanced OS Questions only you can answer... > Re: Advanced OS Questions only you can answer... > Re: Advanced OS Questions only you can answer... > Re: Advanced OS Questions only you can answer... > IBM ServerRaid > Re: Advanced OS Questions only you can answer... > kernel debugging on 4.1-release > > ---------------------------------------------------------------------- > > Date: Mon, 21 Aug 2000 19:37:03 +0300 > From: Ruslan Ermilov > Subject: [PATCH] 3-button microsoft-type serial mouse > > - --8t9RHnE3ZwKMSgU+ > Content-Type: text/plain; charset=us-ascii > > Hi! > > I have a 3-button microsoft-type serial mouse (I do not know the vendor, > only FCC ID if needed) which generates the `middle button down' event as > previous `button down/up' event (any). Attached are: > > 1. the script(1) output of unmodified moused(8) with comments on events. > 2. the patch that makes my mouse's 3rd button work. > > > Cheers, > - -- > Ruslan Ermilov Oracle Developer/DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > - --8t9RHnE3ZwKMSgU+ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: attachment; filename="moused.script" > > Script started on Mon Aug 21 18:55:26 2000 > perl# moused -d -f -p /dev/cuaa1 > moused: PnP COM device rev 1.0 probe... > moused: modem status 03 > moused: alternate probe... > moused: pnpwakeup2(): valid response. > moused: M 4d > moused: non-PnP mouse 'M' > moused: PnP serial mouse: 'PNP0F01' '' '' > moused: proto params: 40 40 40 00 3 dc 00 > moused: port: /dev/cuaa1 interface: serial type: microsoft model: generic > > Left button pressed: > > moused: received char 0x60 > moused: received char 0x0 > moused: received char 0x0 > moused: assembled full packet (len 3) 60,0,0,0,0,0,0,0 > moused: tv: 966873379 603859 > moused: : 966873377 3320 > moused: flags:00000001 buttons:00000001 obuttons:00000000 > moused: activity : buttons 0x00000001 dx 0 dy 0 dz 0 > moused: mstate[0]->count:1 > moused: button 1 count 1 > > Left button released: > > moused: received char 0x40 > moused: received char 0x0 > moused: received char 0x0 > moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 > moused: tv: 966873380 693550 > moused: flags:00000001 buttons:00000000 obuttons:00000001 > moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 > moused: mstate[0]->count:1 > moused: button 1 count 0 > > Right button pressed: > > moused: received char 0x50 > moused: received char 0x0 > moused: received char 0x0 > moused: assembled full packet (len 3) 50,0,0,0,0,0,0,0 > moused: tv: 966873382 523875 > moused: : 966873377 3320 > moused: flags:00000004 buttons:00000004 obuttons:00000000 > moused: activity : buttons 0x00000004 dx 0 dy 0 dz 0 > moused: mstate[2]->count:1 > moused: button 3 count 1 > > Right button released: > > moused: received char 0x40 > moused: received char 0x0 > moused: received char 0x0 > moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 > moused: tv: 966873383 493579 > moused: flags:00000004 buttons:00000000 obuttons:00000004 > moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 > moused: mstate[2]->count:1 > moused: button 3 count 0 > > Middle button pressed: > > moused: received char 0x40 > moused: received char 0x0 > moused: received char 0x0 > moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 > > Middle button released: > > moused: received char 0x40 > moused: received char 0x0 > moused: received char 0x0 > moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 > perl# exit > > Script done on Mon Aug 21 18:56:28 2000 > > - --8t9RHnE3ZwKMSgU+ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: attachment; filename="moused.c.patch" > > Index: moused.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/moused/moused.c,v > retrieving revision 1.45 > diff -u -p -r1.45 moused.c > - --- moused.c 2000/04/21 14:20:25 1.45 > +++ moused.c 2000/08/21 16:09:44 > @@ -1660,8 +1660,7 @@ r_protocol(u_char rBuf, mousestatus_t *a > ? MOUSE_BUTTON2DOWN > : butmapmss[(pBuf[0] & MOUSE_MSS_BUTTONS) >> 4]; > else > - - act->button |= (act->obutton & MOUSE_BUTTON2DOWN) > - - | butmapmss[(pBuf[0] & MOUSE_MSS_BUTTONS) >> 4]; > + act->button |= butmapmss[(pBuf[0] & MOUSE_MSS_BUTTONS) >> 4]; > > /* Send X10 btn events to remote client (ensure -128-+127 range) */ > if ((rodent.rtype == MOUSE_PROTO_X10MOUSEREM) && > @@ -1676,6 +1675,10 @@ r_protocol(u_char rBuf, mousestatus_t *a > > act->dx = (char)(((pBuf[0] & 0x03) << 6) | (pBuf[1] & 0x3F)); > act->dy = (char)(((pBuf[0] & 0x0C) << 4) | (pBuf[2] & 0x3F)); > + > + if (act->button == act->obutton && !act->dx && !act->dy) > + act->button |= MOUSE_BUTTON2DOWN; > + > break; > > case MOUSE_PROTO_GLIDEPOINT: /* GlidePoint */ > > - --8t9RHnE3ZwKMSgU+-- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Mon, 21 Aug 2000 14:38:17 -0700 > From: Mike Smith > Subject: Updated driver for Mylex 160/170/352/2000/3000 controllers > > The next BETA version of the 'mly' driver for Mylex's current family of > PCI SCSI RAID controllers is now available from > http://people.freebsd.org/~msmith/RAID/index.html#mylex. > > The major change in this version is the addition of status monitoring; the > driver is now aware of the array status and will report drive status at > attach time in the SCSI INQUIRY data, as well as logging status events. > > I don't have a 4.x system to test on at this stage, so I'm not trying to > make the driver work on 4.x. Having said that, the issues involved in > fixing it for 4.x are probably small, and if an interested user can > provide me with a little assistance, I'm sure I can sort it out. > > Thanks as usual to Mylex for the hardware and data, and BSDi for funding > this work. > > - -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Mon, 21 Aug 2000 17:28:29 -0400 > From: hspio@worldnet.att.net > Subject: UNSUBSCRIBE > > On 19 Aug 2000, at 2:58, freebsd-hackers-digest wrote: > > > > > freebsd-hackers-digest Saturday, August 19 2000 Volume 04 : Number= > 925 > > > > > > > > In this issue: > > Re: Critical (or equivalent) section in Userland? > > Re: Critical (or equivalent) section in Userland? > > Re: 'group' in ioctl() > > RE: Bootable CD... > > Re: Critical (or equivalent) section in Userland? > > Loading font with libvgl > > Date: Fri, 18 Aug 2000 14:18:38 +0200 > > Fellow Writer > > Re: Fellow Writer > > Re: Anyone try the new dual-head G-400 drivers? > > Re: Anyone try the new dual-head G-400 drivers? > > Re: Fellow Writer > > Re: RE: what to do about /tmp > > Re: Bootable CD... > > Re: Mosix in FreeBSD. > > Re: Mosix in FreeBSD. > > Re: Bootable CD... > > Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > 64bit Ethernet Controllers > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > RE: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: Critical (or equivalent) section in Userland? > > Re: Cheap 1000Gbyte machine > > Re: Critical (or equivalent) section in Userland? > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: Cheap 1000Gbyte machine > > Re: 64bit Ethernet Controllers > > Re: Bootable CD... > > IEEE1394 driver system for -current > > > > ---------------------------------------------------------------------- > > > > Date: Fri, 18 Aug 2000 07:49:32 +0100 > > From: Karl Pielorz > > Subject: Re: Critical (or equivalent) section in Userland? > > > > Warner Losh wrote: > > > > > Kill sendmail's root process. That's the best you can do. It won't > > > impact anything, it will prevent the reading of the queue files (and > > > the config files) and the children will just run with the old copies. > > > then you wait for all the children to die (with a reasonable > > > timeout). Then you do your change, then restart sendmail. That's the > > > best you can hope for. > > > > Unforuntately this doesn't work, as sendmails numerous children live for= > too > > long (the machine is a busy MX, and people increasingly mail 5Mb+ files > > around) > > > > Also adding to the children's lives is the fact that sendmail uses cache= > d > > connections to delivery multiple messages to the same destination MX, wh= > ich > > leads to even longer 'death' times, and can also result in Sendmail's ki= > ds > > looking up domains etc. in the config files :( [At least, that's what ap= > pears > > to be happening after a lot of observation]... > > > > However, 'killall -SIGSTOP sendmail' - appears to work very nicely... Wi= > th a > > 'killall -SIGCONT sendmail' putting things back to normal. I'm also doin= > g the > > stop twice for good measure incase anything was forking at the time. > > > > I guess only time will tell, but the signal idea seems the best so far, > > considering the other restrictions :) > > > > Regards, > > > > Karl > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 00:51:53 -0600 > > From: Warner Losh > > Subject: Re: Critical (or equivalent) section in Userland? > > > > In message <399CDC7C.F68E634@tdx.co.uk> Karl Pielorz writes: > > : However, 'killall -SIGSTOP sendmail' - appears to work very nicely... = > With a > > : 'killall -SIGCONT sendmail' putting things back to normal. I'm also do= > ing the > > : stop twice for good measure incase anything was forking at the time. > > > > No need to stop twice. > > > > : I guess only time will tell, but the signal idea seems the best so far= > , > > : considering the other restrictions :) > > > > Well, you still have the same problem as before, you've just made it > > harder to exploit. Namely, if sendmail fires up and reads one of the > > set of files, then you stop it, and start it again and reads the rest > > it is little different than the problem you had before. > > > > I would suspect it is much less likely to happen, however. > > > > Warner > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 00:53:59 -0600 > > From: Warner Losh > > Subject: Re: 'group' in ioctl() > > > > In message <20000818142650A.fujita@soum.co.jp> FUJITA Kazutoshi writes: > > : What 'group' should I use ? > > > > Pick one, it will not likely matter. Traditionally, certain groups > > have been reserved for the TTY layer, but unless you are trying to > > coexist with these sorts of interfaces, it really doesn't matter much. > > > > I would avoid the 'f' group, however, because those IOCTLs need to > > work on all file descriptors and you wouldn't want a collision. > > > > Warner > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 09:58:09 +0200 (SAST) > > From: Johan Kruger > > Subject: RE: Bootable CD... > > > > Might be that you need to disklabel the image of the filesystem on > > which you copy this files, ( not talking about the mfs filesystem that > > is crunced into the kernel ) > > So, try the following. > > Mount this image by doing 'vnconfig /dev/vn0 /pathtobootimage/myimage.im= > g' > > where myimgae.img is the 2.88 M boot image. > > Now do a 'mount /dev/vn0 /mnt' > > now do a 'disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > > > Something like above, try and see if it works. > > If it doesn't create a new filesystem, do newfs and disklabel, then copy= > all > > those files of yours onto the filesystem. > > You actually don't need all those files. > > Anyways, i think it's the bootloader itself thats not loading the kernel= > on the > > CD ( inside the 2.88 M) image. And to correct that you need to reinstall= > the > > bootloader, and the bootblocks. > > That is boot0 to boot2 > > > > > > On 17-Aug-00 Patrick Bihan-Faou wrote: > > > Hi, > > > > > > > > > I am trying to build a bootable CD... Now this sounds like something t= > rivial > > > enough to do when you know what you are doing. In my case I must admit= > that > > > I am somewhat confused. > > > > > > Until now, I think that the trick was to make the CD look like a flopp= > y and > > > boot it as such. I have created some bootable CDs in the past and they > > > seemed to work OK. > > > > > > However it looks like things have changed recently in the way CD-Roms = > are > > > booted, and I am not able to create a working CD anymore. > > > > > > What I would like to clarify is what needs to be in the "2.88 M" boota= > ble > > > image ? > > > > > > Here is what I have: > > > > > > /boot > > > /boot0 > > > /boot1 > > > /boot2 > > > /loader > > > /cdboot > > > /pxeboot > > > /loader.config > > > /loader.rc > > > /boot.config > > > /kernel.config > > > /kernel.gz > > > /modules > > > ... > > > /usr/sbin > > > ibcs2 > > > linux > > > svr4 > > > > > > > > > Now whenever I boot this image, the loader dies displaying a all whack= > hex > > > values and saying "BTX Halted". > > > > > > > > > I am a bit confused as to what to do next, and I would really apprecia= > te any > > > help. > > > > > > BTW I am working on a fresh copy of FreeBSD 4.1-STABLE (checked-out Au= > gust > > > 15). > > > > > > > > > Patrick. > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > - ---------------------------------- > > E-Mail: Johan Kruger > > Date: 18-Aug-00 > > Time: 09:49:10 > > > > This message was sent by XFMail > > - ---------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 07:52:17 +0000 > > From: Tony Finch > > Subject: Re: Critical (or equivalent) section in Userland? > > > > Karl Pielorz wrote: > > > > > >I don't think advisory locks will work - the other process is sendmail.= > .. I > > >have to keep it from opening any of it's config files, whilst I 'rename= > ' out > > >of place the old ones (keeping any fd's to them intact) and rename in t= > he new > > >ones... > > > > Why not append a serial number to the end of the filenames of the > > subsidiary configuration files, and modify sendmail.cf accordingly? > > Then the update procedure could be: > > (1) write all the new files as $filename.`date +%Y%d%m%H%M%S` > > (2) mv sendmail.cf.date sendmail.cf (or use `ln -sf` if you want to > > keep old files) > > (3) every day or so delete configuration files that are older than > > your maximum queue run time. > > > > This gives you atomic configuration updates. > > > > You don't need to rename the old sendmail.cf to another because > > existing fds will remain attached to the old file which isn't being > > altered, just unlinked. > > > > Tony. > > - -- > > en oeccget g mtcaa f.a.n.finch > > v spdlkishrhtewe y dot@dotat.at > > eatp o v eiti i d. fanf@covalent.net > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 10:43:24 +0200 (SAST) > > From: Johan Kruger > > Subject: Loading font with libvgl > > > > Hmm, a few days back on the mailing list i saw there was > > problem with specifying a different font when using libvgl. > > Allthough this is not critical to my application, it would > > shurely enhance the look and feel of my app. > > > > So i am wondering ... is somebody working on this ? > > And nope , i cant work on it right now. *;-) > > > > Just curios > > - ---------------------------------- > > Unix Software Developer/Engineer > > E-Mail: Johan Kruger > > Date: 18-Aug-00 > > Time: 10:37:54 > > > > This message was sent by XFMail > > - ---------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 14:18:38 +0200 > > From: rudy.gheysens@gemeenschapsonderwijs.be > > Subject: Date: Fri, 18 Aug 2000 14:18:38 +0200 > > > > Dear Sir, > > Madam, > > > > For the thirteenth time already our association is organi-zing a cartoon > > contest. Firstly, we would like to thank all parti-cipants of the 1999 > > contest. The large number of entries proves their confidence in our > > orga-nisation and this is a real incen-tive for us to do even better in > > 2001. > > We hope we can count on your collaboration and wish you a lot of success= > ! > > > > > > The President > > Rudy Gheysens > > ________________________________________ > > RULES > > > > 1. Theme: " THE SUPERMARKET ". > > > > 2. The number of entries is limited until 5. > > They shall not have been exhibited or publis-hed before. > > > > 3. The works have to be sent to the following address: > > > > EURO-KARTOENALE > > WAREGEMSESTEENWEG 113 > > B- 9770 KRUISHOUTEM - BELGIUM > > > > 4. The drawings shall have the following dimen-sions: 210 x 297 mm. The > > works shall not be provided by a passe-partout, neit-her be stuck on to = > a > > larger paper. > > The drawing must bear, on the reverse side, the surna-me, christian > > name and address of the participant. The drawings shall not bear subtitl= > es. > > > > 5. By virtue of their participation, the partici-pants > > autho-rize the organizers to publish some of their works that they have > > received. > > > > 6. The following prizes are foreseen: > > > > 1.GOLDEN EGG 50.000 BEF (1.239,46 euro) > > 2.SILVER EGG 30.000 BEF (743,68 euro) > > 3.BRONZE EGG 25.000 BEF (619,73 euro) > > 4.PRIZE OF THE E.U. 15.000 BEF (371,84 euro) > > 5.BEST BELGIUM CARTOON 10.000 BEF (247,89 euro) > > > > 7. By participating the participant lends his works to the organizers > > for exhibitions. > > The works received will remain at the dispo-sal of the organizers > > du-ring one year (until 01.11.2002). > > > > 8. The entries will only be sent back by the organizers on receiving a > > written request. The awarded works will become the property of the > > organi-zers. > > > > 9. EXTREME DATE OF ENTRY: 15.01.2001 !! > > Opening of the exhibition: Friday 15/4/2001 at 8 pm. > > _________________________________________ > > > > DEADLINE 15.01.2001 _______________________________ > > Note concerning the catalogue > > > > In order to receive the free catalogu-e, please attach FIVE (5) coupons = > " > > international reply " to cover the postage. > > These coupons ar available in your local post office. > > ______________________________________________ > > > > E.C.C. - EUROPEAN CARTOON CENTRE > > __________________________________________ > > > > Dear cartoonist > > > > Kruishoutem has the honnour to open the European cartoon Centre. > > > > The centre aims at: > > * displaying cartoons and caricatures of both national and international > > artists > > * extending the largest documentation centre regarding cartoons and > > caricatures in Europe. This documentation will be the disposal of every > > cartoonist in the world > > * keeping the available documentation and cartoons at the disposal of > > advertising agencies and designers in order to offer the cartoonists a > > forum. > > > > In order to accomplish this mission, the "Euro-kartoenale" will use its > > private collection of cartoon books, publications, magazines and origina= > l > > cartoons to start up the centre. However, this will not suffice. > > We also count on the support and cooperation of the cartoonists themselv= > es. > > This is why we make an urgent appeal to provide us with cartoon books an= > d > > catalogues (personal work or copies from your private collection), magaz= > ines > > (please send them regulary), dissertations and other suitable material. > > > > Much to our regrets we do not have the budget to reimburse you. > > > > We are looking forward to any support and will keep you informed of the > > European Cartoon centre. > > > > Rudy Gheysens > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 06:27:08 -0700 (PDT) > > From: juliangabrielcolado@overtimemail.com > > Subject: Fellow Writer > > > > - --=3D200008180907=3D > > Content-Type: text/plain;charset=3DUS-ASCII > > > > Dear fellow writer: > > > > I have come across a great new website for writers. They are a > > on-demand publisher, and are currently looking for new authors. > > They pay the best royalties in the industry, and the people there > > are writers like us. If you think you might be interested, email me > > and I can send you the link. I already have two titles up with > > them, and they have been very helpful. > > > > PS- if you're not interested, don't reply, and you won't hear from > > me again. I'm not a robot, and your name isn't on some list I > > bought. I'm just kind of a fanatic for writer's rights, and thought > > this might help out some of my fellow writers. > > > > Good luck with your writing, > > Julian Gabriel Colado > > > > > > - --=3D200008180907=3D-- > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 23:47:22 +1000 > > From: Andrew Kenneth Milton > > Subject: Re: Fellow Writer > > > > +-------[ juliangabrielcolado@overtimemail.com ]---------------------- > > | Dear fellow writer: > > | > > > > | They pay the best royalties in the industry, and the people there > > | are writers like us. > > > > The writers there are completely crap? Doesn't sound too good. > > > > - -- > > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Mil= > ton > > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > > ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daem= > on > > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 10:14:38 -0400 > > From: "Jeroen C. van Gelderen" > > Subject: Re: Anyone try the new dual-head G-400 drivers? > > > > "Alexander N. Kabaev" wrote: > > > > > > This driver will not run on FreeBSD most likely. It seems like the dri= > ver needs > > > Linux framebuffer device to run. > > > > Fortunately this doesn't seem to be the case. Works like a charm... > > > > Cheers, > > Jeroen > > - -- > > Jeroen C. van Gelderen o _ _ _ > > jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) > > _< \_ _>(_) (_)/<_ \_| \ _|/' \/ > > (_)>(_) (_) (_) (_) (_)' _\o_ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 10:19:14 -0400 (EDT) > > From: "Alexander N. Kabaev" > > Subject: Re: Anyone try the new dual-head G-400 drivers? > > > > This is the case when I am certainly glad I was mistaken. The sentence f= > rom > > README about driver working only with framebuffer fooled me. Thanks for > > clearing my confusion. > > > > > > On 18-Aug-00 Jeroen C. van Gelderen wrote: > > > "Alexander N. Kabaev" wrote: > > >> > > >> This driver will not run on FreeBSD most likely. It seems like the dr= > iver > > >> needs > > >> Linux framebuffer device to run. > > > > > > Fortunately this doesn't seem to be the case. Works like a charm... > > > > > > Cheers, > > > Jeroen > > > -- > > > Jeroen C. van Gelderen o _ _ _ > > > jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) > > > _< \_ _>(_) (_)/<_ \_| \ _|/' \/ > > > (_)>(_) (_) (_) (_) (_)' _\o_ > > > > - ---------------------------------- > > E-Mail: Alexander N. Kabaev > > Date: 18-Aug-00 > > Time: 10:15:16 > > - ---------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 08:07:02 -0700 > > From: Chameleon > > Subject: Re: Fellow Writer > > > > At 11:47 PM 8/18/00 +1000, Andrew Kenneth Milton wrote: > > >+-------[ juliangabrielcolado@overtimemail.com ]---------------------- > > >| Dear fellow writer: > > >| > > > > > >| They pay the best royalties in the industry, and the people there > > >| are writers like us. > > > > > >The writers there are completely crap? Doesn't sound too good. > > > > LOL > > thats a good one > > > > >-- > > >Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Mi= > lton > > >The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > > >ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Dae= > mon > > >PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > >with "unsubscribe freebsd-hackers" in the body of the message > > > > > > - ----------------------------------------------------------------------= > - ------------------------ > > > > > The human mind ordinarily operates at only ten percent of its capacity > > - -- the rest is overhead for the operating system. > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 08:47:06 -0700 (PDT) > > From: Matt Dillon > > Subject: Re: RE: what to do about /tmp > > > > : > > :Matt, > > : > > :I noticed /tmp and /var/tmp are used slightly differently, for example,= > the > > :contents of /tmp are not expected to survive a reboot, while /var/tmp i= > s > > :used for files you might need after a crash, like vi recovery files. > > > > This may have been true at one time in the past, but these days > > /tmp and /var/tmp tend to be used interchangeably. You can't make > > those sorts of assumptions. > > > > :One advantage of mounting /tmp with MFS is that you don't have use up a= > nother > > :disk partition. Performance-wise, I would think data moves something > > :like this: > > : > > :/tmp on MFS: > > : application data --> kernel VM --> paged to disk > > : > > :/tmp on FFS: > > : application data --> kernel file buffer --> flushed to disk > > : > > :Is that basically correct? What makes MFS less efficient than FFS? > > :What would be the implications of creating a 512 MB swap partition > > :and mounting an MFS /tmp? > > : > > :Thanks, > > : > > :Allen > > > > There are several problems with MFS: > > > > * The active data set is cached in memory TWICE rather then just > > once. That is, for each page of file data two pages is taken up > > of memory. > > > > * While it is true that MFS will swap unused data, performance under > > heavy load will go to pot because MFS does not in any way attempt > > to sequence the data to swap. > > > > MFS may appear fast under light loads, but performance degrades > > drastically (to much worse then what you get with FFS) under > > heavy memory loads. > > > > * MFS eats a 'random' amount of swap, up to the size of the MFS > > disk. Under medium loads where paging is taking place, the > > swap backing store for MFS becomes fragmented and performance > > goes to pot. > > > > There are two solutions: > > > > * First, you can use vnconfig to create a swap-backed filesystem > > and you can reserve the necessary swap wspace contiguously, > > resulting in performance which will be as good or better then > > a normal FFS filesystem (because your swap space may be striped > > across several disks). > > > > * Second, you can use a normal FFS partition. > > > > In either case enabling softupdates on the vnconfig or normal > > FFS partition should result in good overall peformance without > > the load penalty. > > > > With both solutions it is a good idea to make /var/tmp the partition > > and make /tmp a softlink to /var/tmp. > > > > Using MD instead of MFS is typically not a great choice. While it i= > s > > true that MD only caches data once, the data is not swap-backed so > > what data MD does allocate is allocated permanently. This is useful > > in certain system configurations but not useful in the general case. > > > > -Matt > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 11:48:21 -0400 > > From: "Patrick Bihan-Faou" > > Subject: Re: Bootable CD... > > > > Hi, > > > > > > > > > Might be that you need to disklabel the image of the filesystem on > > > which you copy this files, ( not talking about the mfs filesystem that > > > is crunced into the kernel ) > > > So, try the following. > > > Mount this image by doing 'vnconfig /dev/vn0 /pathtobootimage/myimage.= > img' > > > where myimgae.img is the 2.88 M boot image. > > > Now do a 'mount /dev/vn0 /mnt' > > > now do a 'disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > > > Actually I am using the doFS.sh script from /usr/src/release. The diskla= > bel > > is done (without the -b and -s options though) by that script. Also I us= > ed > > to be able to build bootable CDs from the same procedure a few weeks ago > > (before the code in /usr/src/sys/boot was updated). > > > > The CD is recognized as bootable and starts to boot. I can stop the boot= > at > > the first "spinning bar" (I think that's boot0 or boot1) before the cont= > rol > > is passed to "loader". > > > > From there I am sort of stuck: the only thing I can boot is loader which= > in > > turn crashes immediately. I tried to load "kernel.gz" but its format is = > not > > recognized at this stage of the boot (probably because it is compressed)= > . > > > > > > > > BTW I tried you procedure above, and I get: > > > > su-2.03# vnconfig /dev/vn0 boot.cdrom.img > > su-2.03# mount /dev/vn0 /mnt > > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > disklabel: /dev/vn0: Device busy > > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /mnt > > disklabel: /mnt: Is a directory > > su-2.03# umount /mnt > > su-2.03# disklabel -B -b mindbox/boot/boot1 -s mindbox/boot/boot2 /dev/v= > n0 > > disklabel: ioctl DIOCWLABEL: Operation not supported by device > > su-2.03# > > > > > > > > > > I'd rather fix the problem with the current version of the boot code, bu= > t > > time is pressing and I am tempted to revert to the code tagged with the > > FreeBSD-4.0 release. Is this something that I should do ? > > > > > > > > Patrick. > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 09:31:50 -0700 > > From: Marco Molteni > > Subject: Re: Mosix in FreeBSD. > > > > On Thu, 17 Aug 2000, Jes=3DFAs Arn=3DE1iz wrote: > > > > > I have read some information about MOSIX which is some patch for the l= > inux > > > kernel created to build super-computers from a net of PCs. > > >=3D20 > > > I want to know if is there some similar project (mosix or even cluster= > ing) > > > but for FreeBSD, if someone know some about it please let me know. > > > > Mosix started on BSD/OS, and was then rewritten for Linux. I think the B= > SD/=3D > > OS > > version has died, but you may ask the Mosix people, now that the *BSD ar= > e > > getting more attention... > > > > Marco > > - --=3D20 > > Marco Molteni "rough consensus and running code" > > SRI International, System Design Laboratory > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 12:41:54 +0000 > > From: Alan Clegg > > Subject: Re: Mosix in FreeBSD. > > > > Out of the ether, Marco Molteni spewed forth the following bitstream: > > > > > Mosix started on BSD/OS, and was then rewritten for Linux. I think the= > BSD/OS > > > version has died, but you may ask the Mosix people, now that the *BSD = > are > > > getting more attention... > > > > I spoke to the author (one of the authors?) of Mosix at LinuxWorld this > > last week, and he was sorry to say that it was *NOT* available on *BSD* > > to the public any longer. > > > > However, the code is still up and running on BSD/OS at the University. > > > > AlanC > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 18:46:10 +0200 (SAST) > > From: Johan Kruger > > Subject: Re: Bootable CD... > > > > Ok, here's what i did ( busy building a custom CD installation ) > > After the 'make release' , i took the boot.flp image 2.88 Meg and > > mounted it. I deleted everything except for /boot/boot0-2 an the > > bootforth loader. Then i made my own kernel allowing a MFS of 2048 x 512 > > blocks, giving me 1.44 Meg in the filesystem. > > In this i crunched 72 Megs of binary's , one of them 'chroot' > > I compiled init as not to look for 'rc' ( check the Makefile, define par= > t > > that's specifically for a release ) > > After this i use the write_mfs_in_kernel script and umount it ( remember= > to > > compress the kernel after the mfs write > > > > sh -e doFS.sh -s mfsroot ./ /mnt 2880 johan's_mfsfd_root_dir/ 8000 minim= > um2 > > ./write_mfs_in_kernel kernel mfsroot > > gzip -9vc kernel > kernel.gz > > vnconfig /dev/vn0 boot.flp > > mount /dev/vn0 /mnt > > rm /mnt/kernel.gz > > cp kernel.gz /mnt/kernel.gz > > umount /mnt > > vnconfig -u /dev/vn0 > > > > Now your boot.flp is ready for mkisofs > > > > Basically what happens now , i copy my complete live filesystem with > > installed apps to the CD's root dir, and when i do mkisofs, i use my new > > bootimage. After boot , since it can not find rc, it executes .profile i= > n > > the MFS filesystem in the kernel- BUT ONLY if you compiled init for the > > crunch with in /usr/src/sbin/init/Makefile > > > > #CFLAGS+=3D-DDEBUGSHELL -DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > CFLAGS+=3D-DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > > > > > In .profile i put 'mount_cd9660 /dev/acd0a /cdrom' ( /cdrom an extra dir= > i put > > in my filesystem ) and 'chroot /cdrom /setup' , where setup is my prog, = > and > > this works perfectly , i even load my own modules before the chroot and = > so on. > > > > The release i built is 5.0-CURRRENT , and if you want the boot.flp i can > > attach it for you. Just mail me. Right now i'm going home - it's Friday = > - - at > > last > > GOOD LUCK > > *;-) > > > > On 18-Aug-00 Patrick Bihan-Faou wrote: > > > Hi, > > > > > > > > > Actually I am using the doFS.sh script from /usr/src/release. The disk= > label > > > is done (without the -b and -s options though) by that script. Also I = > used > > > to be able to build bootable CDs from the same procedure a few weeks a= > go > > > (before the code in /usr/src/sys/boot was updated). > > > > > > The CD is recognized as bootable and starts to boot. I can stop the bo= > ot at > > > the first "spinning bar" (I think that's boot0 or boot1) before the co= > ntrol > > > is passed to "loader". > > > > > >>From there I am sort of stuck: the only thing I can boot is loader whi= > ch in > > > turn crashes immediately. I tried to load "kernel.gz" but its format i= > s not > > > recognized at this stage of the boot (probably because it is compresse= > d). > > > > > > > > > > > > BTW I tried you procedure above, and I get: > > > > > > su-2.03# vnconfig /dev/vn0 boot.cdrom.img > > > su-2.03# mount /dev/vn0 /mnt > > > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/vn0 > > > disklabel: /dev/vn0: Device busy > > > su-2.03# disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /mnt > > > > > > Patrick. > > > > > > > > > > - ---------------------------------- > > Unix Software Developer/Engineer > > E-Mail: Johan Kruger > > Date: 18-Aug-00 > > Time: 18:28:20 > > > > All good things come to those who ... runs FreeBSD > > - ---------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 18:16:09 +0100 > > From: Jonathan Laventhol > > Subject: Cheap 1000Gbyte machine > > > > Hello Folks -- > > > > Anybody built a file server with approx 1000 Gbyte or more? > > Or even 200 Gbyte? > > > > I'm looking for a cheap simple way of doing this. Lots of > > IDE drives? (How many can you have?) Or SCSI? (Again, > > how many can you have?). > > > > It's for lots of 1 Mbyte files: no huge files. > > > > Thanks for any tips. > > > > Regards, > > Jonathan. > > - -- > > ____________________________________________________________________ > > Imagination 25 Store Street South Crescent London WC1E 7BL England | > > Tel +44 20 7323 3300 Fax +44 20 7323 5801 | > > _______________________________________________________| > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 19:20:31 +0200 > > From: Wilko Bulte > > Subject: Re: Cheap 1000Gbyte machine > > > > On Fri, Aug 18, 2000 at 06:16:09PM +0100, Jonathan Laventhol wrote: > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > Done routinely in the commercial world. But cheap.. > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > What is cheap? > > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > how many can you have?). > > > > SCSI, behind RAID array controllers. Connected to the host via SCSI > > or Fibrechannel. > > > > - -- > > Wilko Bulte wilko@freebsd.org > > Arnhem, the Netherlands > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 13:52:39 -0400 > > From: Dennis > > Subject: 64bit Ethernet Controllers > > > > Have any 64bit PCI ethernet controllers been tested in 4.x yet? Preferab= > ly > > quad port..I've seen a few around (adaptec has one) but no mention on th= > e > > list of specific experience. > > > > Dennis > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 19:45:43 +0200 (CEST) > > From: Soren Schmidt > > Subject: Re: Cheap 1000Gbyte machine > > > > It seems Jonathan Laventhol wrote: > > > Hello Folks -- > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > Not yet :) > > > > > Or even 200 Gbyte? > > > > Yup, 300G's standing here right next to me... > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > how many can you have?). > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > drives and you should be in business, for a very resonable > > pricetag. > > > > - -S=F8ren > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 10:44:21 -0700 (PDT) > > From: Matthew Jacob > > Subject: Re: Cheap 1000Gbyte machine > > > > On Fri, 18 Aug 2000, Soren Schmidt wrote: > > > > > It seems Jonathan Laventhol wrote: > > > > Hello Folks -- > > > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > > > Not yet :) > > > > That's not quite true. We had ~900GB on a NetBSD/Alpha machine at NASA/A= > mes. > > > > > > > > > Or even 200 Gbyte? > > > > > > Yup, 300G's standing here right next to me... > > > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > > how many can you have?). > > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > drives and you should be in business, for a very resonable > > > pricetag. > > > > > > > You know, I used to say ixnay on that, but, Soren, I've been looking at = > a lot > > of the features of the newer ATA drives, and now that they have bad bloc= > k > > replacement, I'd have to say that what you're proposing is not unreasona= > ble, > > although I'd suggest that Vinum/RAID5 be used. > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 19:52:42 +0200 (CEST) > > From: Soren Schmidt > > Subject: Re: Cheap 1000Gbyte machine > > > > It seems Matthew Jacob wrote: > > > On Fri, 18 Aug 2000, Soren Schmidt wrote: > > > > > > > It seems Jonathan Laventhol wrote: > > > > > Hello Folks -- > > > > > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > > > > > Not yet :) > > > > > > That's not quite true. We had ~900GB on a NetBSD/Alpha machine at NASA= > /Ames. > > > > Oh, I mean I havn't build one yet :) > > > > > > > Or even 200 Gbyte? > > > > > > > > Yup, 300G's standing here right next to me... > > > > > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > > > how many can you have?). > > > > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > > drives and you should be in business, for a very resonable > > > > pricetag. > > > > > > You know, I used to say ixnay on that, but, Soren, I've been looking a= > t a lot > > > of the features of the newer ATA drives, and now that they have bad bl= > ock > > > replacement, I'd have to say that what you're proposing is not unreaso= > nable, > > > although I'd suggest that Vinum/RAID5 be used. > > > > Nice to hear, and yes vinum is the way to go for redundancy, who is > > going to backup THAT amount of data, and on what :) > > > > - -S=F8ren > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 13:53:05 -0400 > > From: Nathan Vidican > > Subject: Re: Cheap 1000Gbyte machine > > > > Soren Schmidt wrote: > > > > > > It seems Jonathan Laventhol wrote: > > > > Hello Folks -- > > > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > > > Not yet :) > > > > > > > Or even 200 Gbyte? > > > > > > Yup, 300G's standing here right next to me... > > > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > > how many can you have?). > > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > drives and you should be in business, for a very resonable > > > pricetag. > > > > > > -S=F8ren > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > Try AreaSYS electronics, they make an external ATA to SCSI RAID system > > that operates independant of the O/S. I don't know how it would be in > > terms of performance, but you might be able to put a few of these > > devices on to a system, and use vinum/raid of the raid systems, (seeing > > as how FreeBSD would just see them as giant scsi drives). > > I believe they do a setup which houses 8 ATA disks, in which case you > > could get away with more than what you're looking for with just two > > units. > > > > - -- > > Nathan Vidican > > webmaster@wmptl.com > > Windsor Match Plate & Tool Ltd. > > http://www.wmptl.com/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 14:09:42 -0400 > > From: "Allen Pulsifer" > > Subject: RE: Cheap 1000Gbyte machine > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > drives and you should be in business, for a very resonable > > > pricetag. > > > > Might be doable, but it would probably take a custom cabinet to accomoda= > te > > the ATA/66 cabling limitations (2 drives per cable with an 18 inch maxim= > um > > length). And don't forget about heat and vibration... > > > > Allen > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 11:17:10 -0700 (PDT) > > From: Matthew Jacob > > Subject: Re: Cheap 1000Gbyte machine > > > > > > > > Nice to hear, and yes vinum is the way to go for redundancy, who is > > > going to backup THAT amount of data, and on what :) > > > > Oh, you really still have to backups. But you hope you never have to > > restore... > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 12:06:57 -0700 > > From: Mike Smith > > Subject: Re: Cheap 1000Gbyte machine > > > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > > > how many can you have?). > > > > > > > > Take 3 or 4 Promise Ultra66/100's and 14 IBM 75G DTLA 307075 > > > > drives and you should be in business, for a very resonable > > > > pricetag. > > > > > > You know, I used to say ixnay on that, but, Soren, I've been looking a= > t a lot > > > of the features of the newer ATA drives, and now that they have bad bl= > ock > > > replacement, I'd have to say that what you're proposing is not unreaso= > nable, > > > although I'd suggest that Vinum/RAID5 be used. > > > > Personally, I'd do it like this: > > > > 16 x IBM DTLA-307075 @ $550ea (approx) > > 2 x 3ware Escalade 6800 @ $500ea (approx) > > > > You can get 24" ATA-66 cables from 3ware (or get them custom cut), which= > > > will greatly simplify cable routing. Presto; a terabyte for under $10k. > > > > Since you need to use something to stripe the two arrays together anyway= > , > > it's really a matter of preference between the 3ware controllers at 8 > > drives each or your average addin ATA card at 4 drives a pop. > > > > - -- > > ... every activity meets with opposition, everyone who acts has his > > rivals and unfortunately opponents also. But not because people want > > to be opponents, rather because the tasks and relationships force > > people to take different points of view. [Dr. Fritz Todt] > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 12:31:49 -0700 (PDT) > > From: Mikko Tyolajarvi > > Subject: Re: Critical (or equivalent) section in Userland? > > > > Karl Pielorz wrote: > > > > >Warner Losh wrote: > > > > >> If advisory locks won't work (and they almost always will for things > > >> like this), then you could walk the process tree. For all processes > > >> that aren't suspended or yourself, send a SIGSTOP, keep a list. > > > > >I don't think advisory locks will work - the other process is sendmail.= > .. I > > >have to keep it from opening any of it's config files, whilst I 'rename= > ' out > > >of place the old ones (keeping any fd's to them intact) and rename in t= > he new > > >ones... > > > > Warning, here be dragons... > > > > You could try replacing sendmail (using mailer.conf) with a script > > that sets LD_PRELOAD and then execs sendmail. Then you have to write > > a little shared lib to wrap some system calls. If you are lucky, > > wrapping open() will be sufficient. In your wrapper function, you > > should have the opportunity to use any of a number of mutual exclusion > > schemes, including advisory locking. > > > > Some sessions with truss/ktrace and some studying of the sendmail > > source may be necessary to get it right, but this is something I'd > > definitely check out. > > > > A wrapper for open could look like: > > > > #define open __hide_open_prototype > > #include > > #include > > #include > > #undef open > > > > int > > open(const char *path, int flags, mode_t mode) > > { > > if (/* path is a file to be protected */) { > > /* do something */ > > /* and beware of calling open() recursively */ > > } > > return _open(path, flags, mode); > > } > > > > Compile with "cc -shared -o open.so -fpic open.c" > > > > Of course, this still may not help much when sendmail has opened some > > of its files, and you then change all of them, which might lead to > > inconsistencies. > > > > $.02, > > /Mikko > > > > - -- > > Mikko Ty=F6l=E4j=E4rvi_______________________________________mikko@rsas= > ecurity.com > > RSA Security > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 15:57:48 -0400 > > From: Robert Sexton > > Subject: Re: Cheap 1000Gbyte machine > > > > On Fri, Aug 18, 2000 at 06:16:09PM +0100, Jonathan Laventhol wrote: > > > Hello Folks -- > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > Or even 200 Gbyte? > > > > Joe Greco did this for a news machine last year. He used several wide > > SCSI controllers, and a bunch of 36G drives, if I recall correctly. > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > how many can you have?). > > > > Good, Fast, or Cheap. Pick any two :-) > > > > I'd suggest two Symbios based LVD SCSI Cards. Up to 14 drives per > > chain, with very reasonable cabling limitations. > > > > Can IDE drives release the bus during seeks? Historically thats been > > the big advantage of SCSI: Two IDE drives are no faster than one IDE > > drive, while SCSI scales in performance. > > > > - -- > > Robert Sexton - robert@kudra.com, Cincinnati OH, USA > > Anarchy: It's not the Law, It's just a good Idea. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 21:45:14 +0100 > > From: Karl Pielorz > > Subject: Re: Critical (or equivalent) section in Userland? > > > > Mikko Tyolajarvi wrote: > > > > > Warning, here be dragons... > > > > But, they can be tamed! :) > > > > > You could try replacing sendmail (using mailer.conf) with a script > > > that sets LD_PRELOAD and then execs sendmail. Then you have to write > > > a little shared lib to wrap some system calls. If you are lucky, > > > wrapping open() will be sufficient. In your wrapper function, you > > > should have the opportunity to use any of a number of mutual exclusion > > > schemes, including advisory locking. > > > > I have recently been doing a lot of work with LD_PRELOAD and wrapping > > syscalls... (a strange co-incidence? :) - but, sending all the sendmail = > calls > > a SIGSTOP seems to have done the trick... > > > > > Of course, this still may not help much when sendmail has opened some > > > of its files, and you then change all of them, which might lead to > > > inconsistencies. > > > > My original idea of 'mv'ing the files seems to cope admirably with this.= > .. If > > sendmail open()'s one of the original files, it's FD is still valid _aft= > er_ > > the mv operations. > > > > The question has never been 'pulling the rug' from under sendmail, it's = > more > > been of keeping sendmail from talking to the rug, while I do the dirty..= > . > > > > SIGSTOP and SIGCONT seem to do the trick nicely... Yes, It's not ideal, = > but it > > seems to work perfectly well (which maybe, makes it as ideal as you can = > get in > > the real world... ? :) > > > > - -Kp > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 14:04:57 -0700 > > From: Parag Patel > > Subject: Re: Cheap 1000Gbyte machine > > > > On Fri, 18 Aug 2000 15:57:48 EDT, Robert Sexton wrote: > > > > > >Can IDE drives release the bus during seeks? Historically thats been > > >the big advantage of SCSI: Two IDE drives are no faster than one IDE > > >drive, while SCSI scales in performance. > > > > How about a single IDE (master) drive per controller, that is, no slave > > drives at all? This would halve the number of available drives per card > > (or require twice the number of cards) but essentially would use the PCI > > bus as a multiplex bus between drives instead of SCSI. > > > > You're still pretty much stuck waiting for one command to finish before > > another can be sent to a drive though, unlike SCSI drives. Still a lot > > cheaper tho'. > > > > I suppose another trick would be to arrange your vinum partitions and > > drive layout so that master and slave drives are never accessed > > simultaneously so one won't block access to the other. > > > > > > -- Parag Patel > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 17:18:38 -0400 (EDT) > > From: Mike Wade > > Subject: Re: Cheap 1000Gbyte machine > > > > On Fri, 18 Aug 2000, Jonathan Laventhol wrote: > > > > > Hello Folks -- > > > > > > Anybody built a file server with approx 1000 Gbyte or more? > > > Or even 200 Gbyte? > > > > > > I'm looking for a cheap simple way of doing this. Lots of > > > IDE drives? (How many can you have?) Or SCSI? (Again, > > > how many can you have?). > > > > > > It's for lots of 1 Mbyte files: no huge files. > > > > > > Thanks for any tips. > > > > You might want to check out the Arena Industrial II Rackmount RAID syste= > m > > from "www.raidweb.com". It has 8 x UDMA controllers that connect to the > > host via Ultra2 SCSI (platform independant). Buy two (or more) of those > > and 16 x (60/80 gb Maxtor UMDA Drives or 75 gb IBM UMDA Drives). > > > > 2 x Arena Industrial II Rackmount RAID $3,975 > > 16 x Maxtor UDMA 60 gb Hard Drives $3,680 > > > > Total Cost $7,655 > > > > That comes out to about $7.98 / gb... > > > > - --- > > Mike Wade (mwade@cdc.net) > > Chief Technical Officer > > CDC Internet, Inc. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 23:23:22 +0200 (CEST) > > From: Soren Schmidt > > Subject: Re: Cheap 1000Gbyte machine > > > > It seems Parag Patel wrote: > > > On Fri, 18 Aug 2000 15:57:48 EDT, Robert Sexton wrote: > > > > > > > >Can IDE drives release the bus during seeks? Historically thats been > > > >the big advantage of SCSI: Two IDE drives are no faster than one IDE > > > >drive, while SCSI scales in performance. > > > > > > How about a single IDE (master) drive per controller, that is, no slav= > e > > > drives at all? This would halve the number of available drives per ca= > rd > > > (or require twice the number of cards) but essentially would use the P= > CI > > > bus as a multiplex bus between drives instead of SCSI. > > > > > > You're still pretty much stuck waiting for one command to finish befor= > e > > > another can be sent to a drive though, unlike SCSI drives. Still a lo= > t > > > cheaper tho'. > > > > Not really, if the ATA drives are configured as single masters, they can= > > > run simultaniously, but you will still have the PCI bus speed limit :) > > Which BTW is around 120MB/s as some overhead goes to keep the system > > running (yes I have measured that :) ) > > > > And if you have modern ATA disks, they support tagged queuing as well, > > have had that running in my lab too... > > > > > I suppose another trick would be to arrange your vinum partitions and > > > drive layout so that master and slave drives are never accessed > > > simultaneously so one won't block access to the other. > > > > Endeed, that would be the easiest solution... > > > > - -S=F8ren > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 14:33:58 -0700 (PDT) > > From: Matthew Jacob > > Subject: Re: Cheap 1000Gbyte machine > > > > On Fri, 18 Aug 2000, Soren Schmidt wrote: > > > > > It seems Parag Patel wrote: > > > > On Fri, 18 Aug 2000 15:57:48 EDT, Robert Sexton wrote: > > > > > > > > > >Can IDE drives release the bus during seeks? Historically thats be= > en > > > > >the big advantage of SCSI: Two IDE drives are no faster than one ID= > E > > > > >drive, while SCSI scales in performance. > > > > > > > > How about a single IDE (master) drive per controller, that is, no sl= > ave > > > > drives at all? This would halve the number of available drives per = > card > > > > (or require twice the number of cards) but essentially would use the= > PCI > > > > bus as a multiplex bus between drives instead of SCSI. > > > > > > > > You're still pretty much stuck waiting for one command to finish bef= > ore > > > > another can be sent to a drive though, unlike SCSI drives. Still a = > lot > > > > cheaper tho'. > > > > > > Not really, if the ATA drives are configured as single masters, they c= > an > > > run simultaniously, but you will still have the PCI bus speed limit :) > > > Which BTW is around 120MB/s as some overhead goes to keep the system > > > running (yes I have measured that :) ) > > > > > > And if you have modern ATA disks, they support tagged queuing as well, > > > have had that running in my lab too... > > > > Yes. I've seen tag depths of 32. Still not as much as SCSI, but 32 will > > saturate most spindles still (I've been having to work on some non-FBSD = > ATA > > and S.M.A.R.T. stuff lately....) > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 17:52:28 -0400 > > From: "Louis A. Mamakos" > > Subject: Re: 64bit Ethernet Controllers > > > > > Have any 64bit PCI ethernet controllers been tested in 4.x yet? Prefer= > ably > > > quad port..I've seen a few around (adaptec has one) but no mention on = > the > > > list of specific experience. > > > > This may not be exactly what you meant, but the Alteon Gigabit ethernet > > controllers (the ti device) are 64 bit PCI cards. The ones I'm using ha= > ve > > optical connections, but they do have a twisted pair version with suppor= > t > > for a 10/100-Base-T phy in addition to the gigabit phy. > > > > louie > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Fri, 18 Aug 2000 18:13:20 -0400 > > From: "Patrick Bihan-Faou" > > Subject: Re: Bootable CD... > > > > Hi, > > > > > > Now I am trying to use the boot.flp image that comes with the 4.1-Releas= > e > > CD. > > My alteration on that boot.flp is to replace the kernel.gz with my own (= > it > > contains a different set of binaries in the mfsroot. > > > > Now when my CD boots, the PC just goes into an endless reboot cycle. If = > I > > stop the boot process when "loader" is loaded and try to load my kernel > > manually (load kernel.gz) the loader answers with a "don't know how to l= > oad > > module /kernel.gz" error. > > > > If I do a lsmod, there is nothing loaded. > > > > I am getting really confused and frustrated... Good thing that I have a > > rewritable CD available :) > > > > > > > > Also on a side note, I think that it would be a great feature to have > > "mount_cd9660" as part of the binaries compiled in the fixit and/or inst= > all > > floppies. At least this way I could mount my CD after booting from a > > floppy... ohwell... > > > > > > > > Patrick. > > > > > > "Johan Kruger" wrote in message > > news:XFMail.000818184610.jkruger@oskar.dev.nanoteq.co.za... > > > Ok, here's what i did ( busy building a custom CD installation ) > > > After the 'make release' , i took the boot.flp image 2.88 Meg and > > > mounted it. I deleted everything except for /boot/boot0-2 an the > > > bootforth loader. Then i made my own kernel allowing a MFS of 2048 x 5= > 12 > > > blocks, giving me 1.44 Meg in the filesystem. > > > In this i crunched 72 Megs of binary's , one of them 'chroot' > > > I compiled init as not to look for 'rc' ( check the Makefile, define p= > art > > > that's specifically for a release ) > > > After this i use the write_mfs_in_kernel script and umount it ( rememb= > er > > to > > > compress the kernel after the mfs write > > > > > > sh -e doFS.sh -s mfsroot ./ /mnt 2880 johan's_mfsfd_root_dir/ 8000 > > minimum2 > > > ./write_mfs_in_kernel kernel mfsroot > > > gzip -9vc kernel > kernel.gz > > > vnconfig /dev/vn0 boot.flp > > > mount /dev/vn0 /mnt > > > rm /mnt/kernel.gz > > > cp kernel.gz /mnt/kernel.gz > > > umount /mnt > > > vnconfig -u /dev/vn0 > > > > > > Now your boot.flp is ready for mkisofs > > > > > > Basically what happens now , i copy my complete live filesystem with > > > installed apps to the CD's root dir, and when i do mkisofs, i use my n= > ew > > > bootimage. After boot , since it can not find rc, it executes .profile= > in > > > the MFS filesystem in the kernel- BUT ONLY if you compiled init for th= > e > > > crunch with in /usr/src/sbin/init/Makefile > > > > > > #CFLAGS+=3D-DDEBUGSHELL -DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > > CFLAGS+=3D-DSECURE -DLOGIN_CAP -DCOMPAT_SYSV_INIT > > > > > > > > > In .profile i put 'mount_cd9660 /dev/acd0a /cdrom' ( /cdrom an extra d= > ir i > > put > > > in my filesystem ) and 'chroot /cdrom /setup' , where setup is my prog= > , > > and > > > this works perfectly , i even load my own modules before the chroot an= > d so > > on. > > > > > > The release i built is 5.0-CURRRENT , and if you want the boot.flp i c= > an > > > attach it for you. Just mail me. Right now i'm going home - it's Frida= > y - > > at > > > last > > > GOOD LUCK > > > *;-) > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > Date: Sat, 19 Aug 2000 19:00:26 +0900 > > From: Katsushi Kobayashi > > Subject: IEEE1394 driver system for -current > > > > Hello, > > > > I announced IEEE1394 device driver on FREENIX'99 (sorry not > > on '00). I have caught up -current version at this time. > > > > The latest -current driver patch can be found at: > > > > ftp://ftp.uec.ac.jp/pub/firewire/beta/ > > > > I hope you success to make a kernel on your source tree. > > > > The driver function is still limited and may include many > > bugs since the driver has been used for specific purrposes, > > e.g., the driver have not supported SCSI (CAM) storage on > > IEEE1394 and not been complient to loadable kernel module. > > However, I think it is better to merge -current on this time and > > maintain on it compared with taking a effort in independent. > > > > Let me know what shall I do to merge my code. > > > > - -- > > > > ikob@koganei= > .wide.ad.jp > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ------------------------------ > > > > End of freebsd-hackers-digest V4 #925 > > ************************************* > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Mon, 21 Aug 2000 19:04:34 -0400 (EDT) > From: Robert Watson > Subject: Re: quotas and file creditentials > > On Thu, 10 Aug 2000, Damian Kuczynski wrote: > > > When I tried to analizee problem with mail.local writing messages to > > user mailmox over quota limit I saw, that once root open a file which > > belongs to nonprivileged user ex. test1, and after that drops his > > privlegees to this user then user test1 is able to write to this file as > > many data an he want and qverquota his disk limits mail.local works in > > this maneer so it is able to overquota user mailbox. > > > > Is this normal, or maybe file should be writen under permissions > > effective user (euid=test1) > > Damian, > > Cached credentials for file descriptor (socket, file) access are a fairly > widely used phenomena under UNIX, and probably not something that should > be used; the defined semantics indicate that access checks can occur only > on open(), not necessarily on individual read()/write() calls. However, > what you could do is move the open() in mail.local to after the revocation > of privilege, although you'd want to create the mailbox first with > privilege if it doesn't already exist. This would probably give the > correct semantics from the perspective of quotas. At one point patches to > do this were floating around -- from your message, I think it's safe to > assume that they were not committed. Might be worth checking the archives > of -hackers and -isp. > > 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 > > ------------------------------ > > Date: Tue, 22 Aug 2000 08:12:39 +0900 > From: Kazutaka YOKOTA > Subject: Re: [PATCH] 3-button microsoft-type serial mouse > > >Hi! > > > >I have a 3-button microsoft-type serial mouse (I do not know the vendor, > >only FCC ID if needed) which generates the `middle button down' event as > >previous `button down/up' event (any). Attached are: > > I have heard about this tipe of mouse. It's one of old serial mice, > isn't it? > > >1. the script(1) output of unmodified moused(8) with comments on events. > >2. the patch that makes my mouse's 3rd button work. > > Thank you for the patch. > > However, this modification should best be implemented as an option (or > a special kludge for this mouse). > > It is perfectly valid the same data packet is sent from the mouse > twice (or three time or more), and there may be some 3-button mice > which stop working if this kludge is invoked for all mice as a > standard feature. > > Kazu > > >Cheers, > >-- > >Ruslan Ermilov Oracle Developer/DBA, > >ru@sunbay.com Sunbay Software AG, > >ru@FreeBSD.org FreeBSD committer, > >+380.652.512.251 Simferopol, Ukraine > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Mon, 21 Aug 2000 19:15:57 -0400 (EDT) > From: Robert Watson > Subject: Re: quotacheck on a live filesystem; safe? (fwd) > > Due to the locking involved in ufs_quota.c's management of the quota > files, I believe it may be possible to get a deadlock when modifying the > quota from userland. I haven't thought through all the details yet, and > am not familiar with the quotacheck.c code, but there are some related > deadlock conditions in the extended attribute code as it uses backing > files in much the same way. In essence, the UFS code holds onto an extra > reference to the quota record file as part of the file system mount > structure. When it needs to commit quota updates to disk, it acquires a > vnode lock for the record file. However, this is not done using the > locking protocol -- i.e., the locking order may not be maintained. The > caller to ufs_readwrite() may already hold the lock on another file; I'm > not sure how rigorously the quota code checks for this type of situation, > but if you are getting either hangs during direct quota file modification, > or lock manager panics, that could be the source. I believe quotacheck.c > attempts to directly access the backing file, in which case such a > deadlock could arise. The quotactl interface appears to support a > call to set/get quota settings/usage, which should be used to manipulate > quotas -- never direct quota backing file access. > > I make no promise about the accuracy of my claims about the existing > quotacheck implementation, but that might be a place to start looking, and > you can certainly imagine problems coming about as a result. You might > also be able to imagine that direct user access to the quota backing files > could be used to bottleneck or entirely block write access to the file > system, due to locking requirements. In the extended attribute > implementation, I generally recommend that backing files be stored in a > directory inaccessible to non-administrative users, as the ability to hold > vnode locks for the file (i.e., long vop_read/write calls) could impact > performance substantially, or allow a deadlock to arise/be engineered. > > Robert Watson > > On Thu, 10 Aug 2000, David Kirchner wrote: > > > I've searched the archives and I've seen this question asked a few other > > times, but I did not see any response. Does anyone know the answer? > > > > ---------- Forwarded message ---------- > > Date: Wed, 9 Aug 2000 14:15:17 -0700 (PDT) > > From: David Kirchner > > To: freebsd-questions@FreeBSD.ORG > > Subject: quotacheck on a live filesystem; safe? > > > > > > Hi, > > > > I've been reading over source for quotacheck and ufs_quota.c and so far I > > have not found a reason why running quotacheck on a live filesystem would > > cause anything but inconsistencies in the quota.user file. Is this an > > incorrect belief? > > > > >From what I understand: > > > > the quota.user file is used as a storage for quota information between > > boots and by the various userland quota reporting utilities. The kernel > > maintains an idea of the quota in memory, and commits it to disk when > > necessary. > > > > If this is correct, then I could expect, at worst, someone's quota to be > > invalid if the machine crashes while quotacheck is running and their files > > are being modified? > > > > Thanks, > > David Kirchner > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > 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 > > ------------------------------ > > Date: Mon, 21 Aug 2000 21:01:13 -0400 (EDT) > From: Robert Watson > Subject: Re: freebsd and non-preemtive threads > > Both Coda and Arla make use of an LWP implementation originating at CMU. > I believe that the implementation can make use of timers to add > preemption, but know that in Coda preemption is not supported: LWPs are > used to represent in-process (potentially blocking) RPCs on both the > client and server, and are quite light weight, meaning low context-switch > overhead with minimal kernel involvement. As a result, AFS and Coda > servers tend to run with hundreds, if not thousands of threads: a feat not > possible in many 1:1 userland thread/kernel mappings (Linux kernel > threads, for example), and often not all that scalable in m:n models. > However, as with other library-based thread mechanisms, you have to be > careful to direct potentially blocking calls through the thread-aware > versions of the calls so as not to block all other threads. As the LWP > code used in AFS/Coda/Arla uses select() for blocking/timeout management, > there are some scalability issues with lots of blocked threads--these > might be improved through use of poll() or kqueue(). > > For reference, my recollection is that peemption-aware userland thread > libraries tend to make alot of timer syscalls, losing some of the > advantage of being a userland thread library (low context switch cost, few > transistions between user/kerneland). The AFS LWP code included a > fasttime() mechanism that took advantage of the ability to mmap kernel > memory under SunOS, allowing direct access to the timer variable in > kernel, without a context switch. I do not believe that native ports to > Linux/FreeBSD/et al have retained this capability, especially given its > requirements for privilege. However, it would be easy to imagine a kernel > module exporting a /dev/time, which had the singular ability of allowing > the mmaping of a page containing only the kernel's timer variables, > permitting syscall-free precise time access from userland using atomic > memory access calls. > > 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 > > ------------------------------ > > Date: Mon, 21 Aug 2000 18:13:16 -0700 > From: Alfred Perlstein > Subject: Re: freebsd and non-preemtive threads > > * Robert Watson [000821 18:01] wrote: > > > > For reference, my recollection is that peemption-aware userland thread > > libraries tend to make alot of timer syscalls, losing some of the > > advantage of being a userland thread library (low context switch cost, few > > transistions between user/kerneland). The AFS LWP code included a > > fasttime() mechanism that took advantage of the ability to mmap kernel > > memory under SunOS, allowing direct access to the timer variable in > > kernel, without a context switch. I do not believe that native ports to > > Linux/FreeBSD/et al have retained this capability, especially given its > > requirements for privilege. However, it would be easy to imagine a kernel > > module exporting a /dev/time, which had the singular ability of allowing > > the mmaping of a page containing only the kernel's timer variables, > > permitting syscall-free precise time access from userland using atomic > > memory access calls. > > I think phk and I discussed this about a year ago, our idea was to > automatically map the segment in for each process (also allowing > things like getpid and such to be accessable). > > It would be nice to see happen either way (mmap'able /dev/time or > automatically) > > - -- > - -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 17:08:55 +0530 > From: Pran Joseph > Subject: Memory Mapping > > Hi, > > I am trying to write a PCI ethernet driver for FreeBSD 3.4 release . I > am new to the driver stuff. > > I want to allocate some memory for device buffer using malloc > function. I also want the physical address of allocated memory block > so that I can initialize the device registers. > > Can any one of you please explain me how I can convert address > returned by > malloc to Physical address. > > Thanks > - -Pran > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 04:44:21 -0700 > From: Alfred Perlstein > Subject: Re: Memory Mapping > > * Pran Joseph [000822 04:36] wrote: > > Hi, > > > > I am trying to write a PCI ethernet driver for FreeBSD 3.4 release . I > > am new to the driver stuff. > > > > I want to allocate some memory for device buffer using malloc > > function. I also want the physical address of allocated memory block > > so that I can initialize the device registers. > > > > Can any one of you please explain me how I can convert address > > returned by > > malloc to Physical address. > > VTOPHYS or vtophys. > > - -Alfred > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 06:29:34 -0700 (PDT) > From: bliss-s@excite.com > Subject: Advanced OS Questions only you can answer... > > I am stuck between a rock and a hard place. I've been to your website, I've > logged in under deja.news and posted questions, I've emailed several people, > and my Dad even called the BSD 800 number for me and paid a fee to find out > that all my questions are too advanced for their services. The > representative at the 800 number told my Dad that my only hope was to send > this email to you. > > I am researching OS's and chose FreeBSD because it was open source. I know > nothing about OS's. I thought open source would mean that I could review > the documentation and find all my answers. However, open source means > nothing to me because I reviewed the documentation, and it doesn't help me > out because I know no terms good enough to understand the documentation. > I've been doing this now for 4 weeks...what is sad is that I need answers to > these questions in 2 weeks. I have a highschool paper that is due in 3 > weeks, and the teacher is unable to help me out...my Dad doesn't have the > knowledge...so, as you can tell by now, I suck at getting this paper > completed in time. > > I am very green on this, so please keep this in mind if you are able to > answer the questions below. I understand that there might be a fee for > this....if so, please let me know. > > Again, you are my only hope. I thank you VERY much > > With most SINCERE thanks! > David Igo > ========================================= > 1. How does this OS manage process scheduling, interprocess communication, > process synchronization, and of handling deadlocks. > > 2. How does the OS manage main memory and does it manage secondary storage > to back up main memory. I need on algorithm and one structure to show this > management...along with how they relate to the management. > > 3. I need the key characteristics of the OS supporting file structures and > access methods in regards to types of access methods, directory structures, > data protection, and file consistency. > > 4. How does the OS control peripheral devices and the input/output need for > applications regarding input/output design, interfaces, internal system > structures. > > 5. how does the OS provide for a collection of processors including: > a. processors that do not share a memory > b. processor that do not share a clock > c. storage devices dispersed among various sites > d. distributed file system > e. process synchoronization > f. process communication > g. failures recovery > > 6. And finally, how does the OS ensure the protection and security of > files, memory, segments, and CPU for data and code in the following > situations: > a. Unauthorized access > b. mailicious destruction, > c. alteration > d. accidental introduction of inconsistency > > I CAN'T THANK YOU ENOUGH FOR TAKING THE TIME TO HELP ME OUT. > > > > > > _______________________________________________________ > Say Bye to Slow Internet! > http://www.home.com/xinbox/signup.html > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 14:10:37 +0000 > From: Alan Clegg > Subject: Re: Advanced OS Questions only you can answer... > > Out of the ether, bliss-s@excite.com spewed forth the following bitstream: > > I am stuck between a rock and a hard place. I've been to your website, I've > > logged in under deja.news and posted questions, I've emailed several people, > > and my Dad even called the BSD 800 number for me and paid a fee to find out > > that all my questions are too advanced for their services. The > > representative at the 800 number told my Dad that my only hope was to send > > this email to you. > > My guess is that the answer was more along the lines of "Can't your son > do his own homework/research?" > > AlanC > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 17:19:13 +0300 > From: Peter Pentchev > Subject: Re: Advanced OS Questions only you can answer... > > The short answer: none of your questions has a short answer. > > A recommendation: get Kirk McKusick's "Design and Implementation of 4.4BSD", > it has a lot of the information you need, and a quick skim through the > relevant chapters should be enough to give you an idea of the answers > you need. I think that for most people, the ability to really answer even > half of your questions would come after several university-level courses > in computer science and OS design, and/or after several years' worth > of work in the field. > > (alright, so there may be exceptions.. if you happen to be one of them, > or if you've had those several years of programming experience, then > McKusick's book should give you the answers you need :) > > G'luck, > Peter > > - -- > The rest of this sentence is written in Thailand, on > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 10:27:17 -0400 (EDT) > From: "Chris D. Faulhaber" > Subject: Re: Advanced OS Questions only you can answer... > > On Tue, 22 Aug 2000 bliss-s@excite.com wrote: > > *snip* > > > > I am researching OS's and chose FreeBSD because it was open source. I know > > nothing about OS's. I thought open source would mean that I could review > > the documentation and find all my answers. However, open source means > > nothing to me because I reviewed the documentation, and it doesn't help me > > out because I know no terms good enough to understand the documentation. > > I've been doing this now for 4 weeks...what is sad is that I need answers to > > these questions in 2 weeks. I have a highschool paper that is due in 3 > > weeks, and the teacher is unable to help me out...my Dad doesn't have the > > knowledge...so, as you can tell by now, I suck at getting this paper > > completed in time. > > > > If you know nothing about OS's, perhaps you should start with an easier > topic than BSD internals. > > Also, Open Source means that the source is available, not that everything > you have questions on is documented. And since FreeBSD is done almost > completely by volunteers, what information you do find has been > contributed by those with the time and interest, not because they get > paid for it. However, you are welcome to contribute your answers back to > the project for future reference. > > Many of your questions can be answered by reading a copy of Design and > Implementation of 4.4BSD, available at most fine bookstores. In addition, > you are welcome to UTSL (Use The Source, Luke). > > - ----- > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > - -------------------------------------------------------- > FreeBSD: The Power To Serve - http://www.FreeBSD.org > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 16:34:49 +0200 (SAST) > From: Lists Account > Subject: IBM ServerRaid > > Hi All, > > does anyone know if there are any IBM Server raid drivers for FreeBSD out > there? If So can anyone tell me where I can get one > > Thanks > > Andrew > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 11:41:36 -0400 > From: Jon Parise > Subject: Re: Advanced OS Questions only you can answer... > > On Tue, Aug 22, 2000 at 06:29:34AM -0700, bliss-s@excite.com wrote: > > > I am very green on this, so please keep this in mind if you are able to > > answer the questions below. I understand that there might be a fee for > > this....if so, please let me know. > > Looks like you bit off a lot more than you could chew. =) > > Have a look here for some seminar information on 4.4BSD internals: > > http://www.csh.rit.edu/seminars/os/19962/week4/ > > - -- > Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology > http://www.csh.rit.edu/~jon/ : Computer Science House Member > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Tue, 22 Aug 2000 12:44:14 -0400 (EDT) > From: Zhihui Zhang > Subject: kernel debugging on 4.1-release > > I try to trace some system call using remote debugging and find something > that I can not explain myself (the related source is ffs_write()): > > case 1: > - ------- > > 443 if (object) > (gdb) break 430 > Breakpoint 6 at 0xc0289cea: file ../../ufs/ufs/ufs_readwrite.c, line 430. > (gdb) c > Continuing. > > Breakpoint 6, ffs_write (ap=0xc64f5e70) at > ../../ufs/ufs/ufs_readwrite.c:438 > 438 p = uio->uio_procp; > > In the above case, even if I set breakpoint 6 at line 430, it insists on > line 438. > > case 2: > - ------- > > (gdb) print p->p_limit > $1 = (struct plimit *) 0xffffffff > > In the above case, the statement has just used p->p_limit to do some > comparison and yet gdb says its value is -1. The statement using it is: > > if (vp->v_type == VREG && p && > uio->uio_offset + uio->uio_resid > > p->p_rlimit[RLIMIT_FSIZE].rlim_cur) { > > Are these bugs of gdb or am I doing something wrong? I notice that > 4.1-release install KLD files at the same time you install kernel. In the > past, I only copy the file kernel.debug to the target machine. Do I have > to copy those .ko files to the target machine as well? > > Any help is appreciated. > > - -Zhihui > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > End of freebsd-hackers-digest V4 #927 > ************************************* > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 26 21: 1:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id ED02837B424 for ; Sat, 26 Aug 2000 21:01:35 -0700 (PDT) Received: from holly.dyndns.org ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZX00F93N0NBU@mta5.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Sat, 26 Aug 2000 22:57:59 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id WAA79015; Sat, 26 Aug 2000 22:57:35 -0500 (CDT envelope-from chris) Date: Sat, 26 Aug 2000 22:57:34 -0500 From: Chris Costello Subject: Re: UNSUBSCRIBE REMOVE In-reply-to: <39A84A4C.20198.175588@localhost> To: hspio@worldnet.att.net Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000826225734.P60058@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <39A84A4C.20198.175588@localhost> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, August 26, 2000, hspio@worldnet.att.net wrote: > [2,640 lines removed] ... and this was at the bottom of the message you quoted: > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message At the very least, don't just mail a whole day's worth of data back to the list with "UNSUBSCRIBE REMOVE" affixed to the subject line. Don't you know how much bandwidth and money you're wasting for people who have to pay for the amount of data they download? I'm sending this to the list because hopefully someone else reading it and wanting to unsubscribe won't make the same mistake. -- |Chris Costello |Justify my text? I'm sorry but it has no excuse. `------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message