From owner-freebsd-hackers Sun Sep 13 04:32:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21749 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 04:32:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from klokan.sh.cvut.cz (klokan.sh.cvut.cz [147.32.127.208] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21701 for ; Sun, 13 Sep 1998 04:31:59 -0700 (PDT) (envelope-from J.Klaus@sh.cvut.cz) Received: from veverka.sh.cvut.cz (veverka.sh.cvut.cz [194.108.141.34]) by klokan.sh.cvut.cz (8.8.8/8.8.8/Silicon Hill/Antispam/29.3.1998) with ESMTP id NAA22723 for ; Sun, 13 Sep 1998 13:31:40 +0200 Received: from hell.sh.cvut.cz (hell.sh.cvut.cz [194.108.141.148]) by veverka.sh.cvut.cz (8.8.8/8.8.8) with SMTP id NAA08154 for ; Sun, 13 Sep 1998 13:32:07 +0200 (CEST) (envelope-from klausik@veverka.sh.cvut.cz) Date: Sun, 13 Sep 1998 13:31:40 +0200 (CEST) From: Jaroslav Klaus X-Sender: klausik@hell.sh.cvut.cz To: freebsd-hackers@FreeBSD.ORG Subject: bdevsw_add, cdevsw_add ? 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 Hello, I'm going to learn how to write lkm. In kern/kern_lkm.c there's: if ( err = bdevsw_add(&descrip, args->lkm_dev.bdev, &(args->lkm_olddev.bdev))) { but I can't find where is definition of bdevsw_add (resp. cdevsw_add). I found only prototype in sys/conf.h: int bdevsw_add __P((dev_t *descrip,struct bdevsw *new,struct bdevsw **old)); Thank you. Jarda Klaus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 05:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28540 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 05:50:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from klokan.sh.cvut.cz (klokan.sh.cvut.cz [147.32.127.208] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28491 for ; Sun, 13 Sep 1998 05:50:03 -0700 (PDT) (envelope-from J.Klaus@sh.cvut.cz) Received: from veverka.sh.cvut.cz (veverka.sh.cvut.cz [194.108.141.34]) by klokan.sh.cvut.cz (8.8.8/8.8.8/Silicon Hill/Antispam/29.3.1998) with ESMTP id OAA23953; Sun, 13 Sep 1998 14:49:48 +0200 Received: from hell.sh.cvut.cz (hell.sh.cvut.cz [194.108.141.148]) by veverka.sh.cvut.cz (8.8.8/8.8.8) with SMTP id OAA08394; Sun, 13 Sep 1998 14:50:18 +0200 (CEST) (envelope-from klausik@veverka.sh.cvut.cz) Date: Sun, 13 Sep 1998 14:49:49 +0200 (CEST) From: Jaroslav Klaus X-Sender: klausik@hell.sh.cvut.cz To: Jaroslav Klaus cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bdevsw_add, cdevsw_add ? 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, 13 Sep 1998, Jaroslav Klaus wrote: > but I can't find where is definition of bdevsw_add (resp. cdevsw_add). I > found only prototype in sys/conf.h: I've already found it in kern_conf.c. Forget my question. Jarda Klaus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 07:58:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08555 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 07:58:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08550 for ; Sun, 13 Sep 1998 07:58:43 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA05840; Sun, 13 Sep 1998 16:58:24 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA03914; Sun, 13 Sep 1998 16:58:14 +0200 (MET DST) Message-ID: <19980913165813.06185@follo.net> Date: Sun, 13 Sep 1998 16:58:13 +0200 From: Eivind Eklund To: Jaroslav Klaus Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bdevsw_add, cdevsw_add ? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Jaroslav Klaus on Sun, Sep 13, 1998 at 02:49:49PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 13, 1998 at 02:49:49PM +0200, Jaroslav Klaus wrote: > On Sun, 13 Sep 1998, Jaroslav Klaus wrote: > > > but I can't find where is definition of bdevsw_add (resp. cdevsw_add). I > > found only prototype in sys/conf.h: > > I've already found it in kern_conf.c. Forget my question. In 3.0, I believe you're now supposed to use cdewsw_add exclusively, after Julian's changes... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 11:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00412 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 11:03:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00388; Sun, 13 Sep 1998 11:03:43 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA05675; Sun, 13 Sep 1998 14:08:56 -0400 From: Bill Paul Message-Id: <199809131808.OAA05675@skynet.ctr.columbia.edu> Subject: STILL looking for testers for ThunderLAN driver To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Date: Sun, 13 Sep 1998 14:08:55 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my _third_ call for testers for the ThunderLAN PCI network driver. So far, response to the first two calls for testers has been totally underwhelming. Look people, this isn't hard: if you have a Compaq PCI Netelligent or NetFlex 3/P card or a Compaq system with a built-in Netelligent or NetFlex 3/P ethernet controller, or an Olicom ThunderLAN=based adapter, download the driver from http://www.freebsd.org/~wpaul/ThunderLAN and give it a try. If works great for you, then tell me. If it doesn't work, then also tell me, and give me lots of information about what doesn't work, what error messages you see, what hardware you have, and anything else that might make it easier for me to debug the problem. Apparently some people are unable to quite grasp this concept so I'm going to spell it out for you in graphic detail. You may wish to escort little children out of the room until I'm finished. This is what I want you to do: - If you have a Compaq system or Compaq network adapter, then establish whether or not it has a PCI ThunderLAN chip. Note that I said PCI. That's PCI: pee-see-eye. _NOT_ EISA. _NOT_ ISA. _NOT_ PCMCIA. Don't send me e-mail asking me what kind of card you have: YOU look in the manual and find out for yourself. Here's a hint: a NetFlex/E is an EISA bus card. A NetFlex/P is a PCI card. I'm not the least bit interested in the NetFlex/E, only the NetFlex/P. PCI ThunderLAN chips are about 1 inch square, have a Texas Instruments logo imprinted on them along with the word TLAN superimposed over a lightning bolt. There should be a part number that looks something like TNETE100A, or TNETE100PCM, or something to that effect. - If you can conclusively determine that you have a PCI ThunderLAN device, download the driver from http://www.freebsd.org/~wpaul/ThunderLAN and compile a new kernel. There are instructions there that explain how to do this. There's driver code for 3.0-current and 2.2.x (where x can be 5, 6 or 7; don't know about 2.2.1 or 2.2.2). - Boot the kernel and see if a tl0 device is detected and properly attached. If the driver complains that it couldn't read the station address from the EEPROM, then the attach will have failed. If you see 'tl0: Ethernet address: xx:xx:xx:xx:xx:xx' then it succeeded. - It's possible you may have a ThunderLAN adapder who's PCI device ID does not appear in the device list in if_tlreg.h. If you think this is the case, try temporarily changing one of the PCI device IDs in if_tlreg.h to match your device's ID and see if the adapter is probed successfully. If so, e-mail me the device ID and the official name of the adapter (if you know it) so that I can update the list. - If the interface is attached correctly, connect the ThunderLAN NIC to a network and run some tests. See if you can get 100Mbps out of it. Beat up on it. Try to induce problems. Report back to me how well it works or fails to work. - Once you are satisfied that the driver works well, or you have found a problem, e-mail me at wpaul@skynet.ctr.columbia.edu and send me the following information: o The type of adapter you have and the type of system in which it is installed o If the adapter is integrated into your machine, provide the model number of the entire system o The version of FreeBSD you're using o An accurate and ___***DETAILED***___ description of any problem(s) you have encountered. Include _ALL_ error messages that you see. Quote the messages exactly: do not make half- hearted attempts to remember or interpret them. Just copy them down exactly and show them to me. o If you report a problem, be prepared to try patches that I might send you to fix the problem. Now here are examples of resports that I do not want to see, and the replies you're likely to get from me if see them: - "Hi, I have a Compaq GrumbleSmurf 2100 machine; does this system have a ThunderLAN adapter in it?" Don't send me questions like this. It's your hardware, you have the manuals for it, you can pop the cover and look inside it. _YOU_ tell _ME_ if it has a ThunderLAN PCI NIC in it. If I had a complete list of all Compaq models with ThunderLAN PCI NICs in them, I would have listed them here, but I don't. - "Hi, I have several Compaq systems with ThunderLAN NICs, but they're all in production running Windows NT and I can't shut them down to test them with FreeBSD." Then why did you bother writing me. - "Hi: I don't run FreeBSD, but do you know if your driver will work with Linux? I have a Compaq machine running Linux version mumble and I'm trying to set up networking on it." No, FreeBSD device drivers don't work with Linux. No, I will not help you set up Linux. If you want help with Linux, go subscribe to a Linux mailing list. If you persist in bothering me, agents of the sooper sekrit FreeBSD Cabal (tinfc) will sneak into your home, send me your machine so that I can do some decent testing, and replace it with a cardboard box with the word 'Compaq' written on it. Chances are you'll never notice the difference. - "Hi, I have a Compaq machine with a Netelligent NIC and I tried your driver, but I encountered some problems. Unfortunately, I'm going out of town for a month and I won't be able to give you any details or do any troubleshooting until then." I'm hoping to get this driver code into FreeBSD 3.0, which is due to ship inside of a couple of months, so I don't have time to wait for people to get back from their vacations/business trips/cruises/etc. Give me a break here people. - "Hi, I tried your driver but I got an error saying that something failed. Can you help me?" No. - "Hi, I have a Compaq machine running Windows 95. How do I install FreeBSD?" I'm sorry, this is device driver testing: brain implants are two doors down on the right. - "unsubscribe" Was it something I said? So come on people, I know there have to be some people out there with Compaq machines who want to use their built-in PCI NIC. If you don't have one, see if your friend has one. Or your friend's friend. If they're running Linux, convince them to try FreeBSD. Now's your big chance to contribute. Soon even you could be a member of the FreeBSD Cabal (tinfc). -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 13:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21875 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 13:00:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21859; Sun, 13 Sep 1998 13:00:24 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA10257; Sun, 13 Sep 1998 12:59:58 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <35FC243D.AC5C026E@dal.net> Date: Sun, 13 Sep 1998 12:59:57 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE-0905 i386) MIME-Version: 1.0 To: Bill Paul CC: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: STILL looking for testers for ThunderLAN driver References: <199809131808.OAA05675@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > > This is my _third_ call for testers for the ThunderLAN PCI network > driver. So far, response to the first two calls for testers has been > totally underwhelming. In case it helps any, I have seen your previous requests, and sympathized with your plight. However, I have none of the equipment you are trying to test. Given compaq's known problems with FreeBSD, I suspect that very few people on either of these lists have it either. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** "Yes, the president should resign. He has lied to the American people, time and time again, and betrayed their trust. He is no longer an effective leader. Since he has admitted guilt, there is no reason to put the American people through an impeachment. He will serve absolutely no purpose in finishing out his term; the only possible solution is for the president to save some dignity and resign." - William Jefferson Clinton, 1974 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 13:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00562 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 13:56:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00551 for ; Sun, 13 Sep 1998 13:56:34 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: (from graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) id PAA01179 for freebsd-hackers@freebsd.org; Sun, 13 Sep 1998 15:56:16 -0500 (CDT) Date: Sun, 13 Sep 1998 15:56:16 -0500 (CDT) From: Kent A Vander Velden Message-Id: <199809132056.PAA01179@isua3.iastate.edu> To: freebsd-hackers@FreeBSD.ORG Subject: Unused functions Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the code associated with unused functions of a used archive ever removed from the executable that uses the archive? After linking I see with 'nm' there are many functions in the executable that are never called. This is making my executable rather large since the archive is huge. Would elf help in anyway with this? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 15:07:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09997 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 15:07:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09978 for ; Sun, 13 Sep 1998 15:07:48 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id QAA11908; Sun, 13 Sep 1998 16:59:51 -0400 (EDT) Date: Sun, 13 Sep 1998 16:59:50 -0400 (EDT) From: Chuck Robey To: Kent A Vander Velden cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions In-Reply-To: <199809132056.PAA01179@isua3.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Sep 1998, Kent A Vander Velden wrote: > > Is the code associated with unused functions of a used archive ever removed > from the executable that uses the archive? After linking I see with 'nm' > there are many functions in the executable that are never called. This is > making my executable rather large since the archive is huge. Would elf > help in anyway with this? Do you realize that many of the libc functions need each other as dependencies? Many functions just don't work alone. At least for shared executeables, they don't exist in your executeable until you actually execute it, anyways, so they don't bloat your executeable at all. They get linked in during the startup task of locating and loading the executeable into memory, before it really starts to work. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 16:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16377 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 16:03:55 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16372; Sun, 13 Sep 1998 16:03:53 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA16686; Sun, 13 Sep 1998 16:03:38 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd016635; Sun Sep 13 16:03:30 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA21895; Sun, 13 Sep 1998 16:03:26 -0700 (MST) From: Terry Lambert Message-Id: <199809132303.QAA21895@usr04.primenet.com> Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets To: sthaug@nethelp.no Date: Sun, 13 Sep 1998 23:03:26 +0000 (GMT) Cc: dwhite@resnet.uoregon.edu, hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <17840.905638663@verdi.nethelp.no> from "sthaug@nethelp.no" at Sep 13, 98 00:17:43 am X-Mailer: ELM [version 2.4 PL25] 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 > static int icmpbmcastecho = 1; > SYSCTL_INT(_net_inet_icmp, OID_AUTO, bmcastecho, CTLFLAG_RW, &icmpbmcastecho, > 0, ""); > > I believe it should be turned *off* by default, and hope this is fixed > before 3.0 is released. Being off by default would break SLP and IPv6 autodetection for address assignment. Certainly, you should be able to turn it off, but the correct place to block DOS broadcast ping attacks is your firewall. Windows 95 also has this assinine behaviour, such that you can't probe a net to see if an address is free, or intermittently to take "snapshots" of active and inactive machines, etc.. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 16:06:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17248 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 16:06:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17226; Sun, 13 Sep 1998 16:06:42 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA17142; Sun, 13 Sep 1998 16:06:27 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd017137; Sun Sep 13 16:06:21 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA22001; Sun, 13 Sep 1998 16:06:18 -0700 (MST) From: Terry Lambert Message-Id: <199809132306.QAA22001@usr04.primenet.com> Subject: Re: STILL looking for testers for ThunderLAN driver To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Sun, 13 Sep 1998 23:06:17 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <199809131808.OAA05675@skynet.ctr.columbia.edu> from "Bill Paul" at Sep 13, 98 02:08:55 pm X-Mailer: ELM [version 2.4 PL25] 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 > This is my _third_ call for testers for the ThunderLAN PCI network > driver. So far, response to the first two calls for testers has been > totally underwhelming. I don't have any of the necessary hardware. However, there were a couple of posts in the comp.os.unix.freebsd.misc with people asking if this hardware is supported. You may wish to look for "compaq" in that news group, and contact them directly via email. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 16:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18891 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 16:15:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18873 for ; Sun, 13 Sep 1998 16:15:05 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA15980; Mon, 14 Sep 1998 00:14:52 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id AAA05075; Mon, 14 Sep 1998 00:14:51 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199809132314.AAA05075@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Studded cc: The Subject: Re: Missing CVS $Id strings In-reply-to: Your message of "Sat, 12 Sep 1998 18:35:46 PDT." <35FB2172.D0F2D90B@dal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Sep 1998 00:14:51 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > During a recent discussion regarding the benefits of various methods of > updating the configuration and other files related to a system upgrade, > the fact that many of those files don't have CVS $Id strings was > mentioned. Subsequent to that discussion Brian Somers was kind enough to > add those strings to most of those files. I volunteered to provide a > list of the other files that don't have $Id's, so here 'tis. [.....] Here's what I did: > /etc/gnats/freefall No source > /etc/mail/Makefile Ok > /etc/namedb/named.root Doesn't belong to FreeBSD > /etc/namedb/make-localhost Ok > /etc/uucp/call.sample Ok > /etc/uucp/config.sample Ok > /etc/uucp/dial.sample Ok > /etc/uucp/dialcode.sample Ok > /etc/uucp/passwd.sample Ok > /etc/uucp/port.sample Ok > /etc/uucp/sys1.sample Ok > /etc/uucp/sys2.sample Ok > /etc/amd.map No documented comment chars > /etc/group Ok > /etc/motd Skipped > /etc/manpath.config Ok > /etc/mail.rc No documented comment chars > /etc/daily Ok (2.2 only) > /etc/monthly Ok (2.2 only) > /etc/master.passwd No source > /etc/sendmail.cf No source > /etc/passwd No documented comment chars > /root/.cshrc Ok > /root/.login Ok > /var/crash/minfree No documented comment chars > /boot.help Skipped > /.cshrc Ok (same as /root/.cshrc) > /COPYRIGHT Ok I suspect the other files shouldn't be changed... comments ? Cheers. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 16:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19141 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 16:17:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19127 for ; Sun, 13 Sep 1998 16:17:47 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA19220; Sun, 13 Sep 1998 16:17:17 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd019211; Sun Sep 13 16:17:12 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA22419; Sun, 13 Sep 1998 16:17:11 -0700 (MST) From: Terry Lambert Message-Id: <199809132317.QAA22419@usr04.primenet.com> Subject: Re: Unused functions To: graphix@iastate.edu (Kent A Vander Velden) Date: Sun, 13 Sep 1998 23:17:10 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809132056.PAA01179@isua3.iastate.edu> from "Kent A Vander Velden" at Sep 13, 98 03:56:16 pm X-Mailer: ELM [version 2.4 PL25] 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 > Is the code associated with unused functions of a used archive ever removed > from the executable that uses the archive? After linking I see with 'nm' > there are many functions in the executable that are never called. This is > making my executable rather large since the archive is huge. Would elf > help in anyway with this? Functions that are called by functions you call will cause code to be drug in, even if you don't call them directly. For shared libraries, the symbols are used to look up the code addresses, and called through a table. Since the pages aren't there unless they are used, this is good enough. For statically linked images, only the functions that are actually used are linked in. For static linkage, the smalled chunk you can pull in during the link is one ".o" file from the archive (library). So if you have one ".o" file that resulted from a ".c" file that implements the functions "bob" and "superbob", you will get both these functions code, even if you only call one of them. If this is a problem for you, then consider breaking the file into two (or more) files to make them seperate compilation units, and therefore seperate ".o" files, and therefore seperately linked from the archive (library) file (".a"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 16:58:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24283 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 16:58:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24235 for ; Sun, 13 Sep 1998 16:58:50 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id BAA28990; Mon, 14 Sep 1998 01:53:30 +0200 (CEST) Message-ID: <19980914015329.18217@foobar.franken.de> Date: Mon, 14 Sep 1998 01:53:29 +0200 From: Harold Gutch To: Brian Somers Cc: The Subject: Re: Missing CVS $Id strings References: <35FB2172.D0F2D90B@dal.net> <199809132314.AAA05075@woof.lan.awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199809132314.AAA05075@woof.lan.awfulhak.org>; from Brian Somers on Mon, Sep 14, 1998 at 12:14:51AM +0100 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 14, 1998 at 12:14:51AM +0100, Brian Somers wrote: > Here's what I did: > [...] > > /etc/passwd No documented comment chars >From the passwd(5) manpage: Lines whose first non-whitespace character is a pound-sign (#) are com- ments, and are ignored. Blank lines which consist only of spaces, tabs or newlines are also ignored. Note that the last I remember is that this is incorrect in -STABLE (see some -stable archive for more on this topic, the subject was "Finger and getpwent"). -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 17:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26687 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 17:09:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isua4.iastate.edu (isua4.iastate.edu [129.186.1.204]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26681 for ; Sun, 13 Sep 1998 17:09:32 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua4.iastate.edu (8.8.5/8.8.5) with SMTP id TAA28013; Sun, 13 Sep 1998 19:09:16 -0500 (CDT) Message-Id: <199809140009.TAA28013@isua4.iastate.edu> To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions In-reply-to: Your message of "Sun, 13 Sep 1998 23:17:10 -0000." <199809132317.QAA22419@usr04.primenet.com> Date: Sun, 13 Sep 1998 19:09:16 CDT From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >For statically linked images, only the functions that are actually >used are linked in. > >For static linkage, the smalled chunk you can pull in during the >link is one ".o" file from the archive (library). So if you have >one ".o" file that resulted from a ".c" file that implements the >functions "bob" and "superbob", you will get both these functions >code, even if you only call one of them. Just so I completely understand, if I truely use only one function in from a .o file and no other function is using anything in this .o file, the entire .o file is still pulled into the executable? So, there are could be a lot of unused, unreachable code in an executable. Nothing can be done to remove the bloat after the executable has been linked? Is this commonly the way its done on other systems as well? I had always assumed that unused functions and data were tosed out. Thanks. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 18:09:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03426 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 18:09:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03420 for ; Sun, 13 Sep 1998 18:08:59 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id SAA08497; Sun, 13 Sep 1998 18:14:33 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809140114.SAA08497@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Kent Vander Velden cc: Terry Lambert , freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions In-reply-to: Your message of "Sun, 13 Sep 1998 19:09:16 CDT." <199809140009.TAA28013@isua4.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Sep 1998 18:14:32 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just so I completely understand, if I truely use only one function in from > a .o file and no other function is using anything in this .o file, the > entire .o file is still pulled into the executable? So, there are could be > a lot of unused, unreachable code in an executable. Nothing can be done to > remove the bloat after the executable has been linked? Is this commonly the > way its done on other systems as well? I had always assumed that unused > functions and data were tosed out. In most object formats, reference information is kept on a per-object basis (ie. per .o file). Keeping this sort of information on any smaller granularity would lead to an insane increase in the complexity and corresponding performance reduction of the link phase. This is why an experienced programmer will group only related items in a given object. It allows the programmer and the C scoping rules to work together to determine what should be associated and what need not. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 13 20:55:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17630 for freebsd-hackers-outgoing; Sun, 13 Sep 1998 20:55:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from banshee.cs.uow.edu.au (banshee.cs.uow.edu.au [130.130.188.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17620 for ; Sun, 13 Sep 1998 20:55:35 -0700 (PDT) (envelope-from ncb05@banshee.cs.uow.edu.au) Received: (from ncb05@localhost) by banshee.cs.uow.edu.au (8.9.1a/8.9.1) id NAA22896; Mon, 14 Sep 1998 13:55:17 +1000 (EST) Date: Mon, 14 Sep 1998 13:55:16 +1000 (EST) From: Nicholas Charles Brawn X-Sender: ncb05@banshee.cs.uow.edu.au To: freebsd-hackers@FreeBSD.ORG Subject: lkm interaction with kernel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to figure out how I can write a drop-in lkm that will interact with the kernel with minimal modification of kernel source. The design i am basing it on is ip_fw, but when looking through ip_fw.c, I can't see how it is called from the kernel when a packet arrives to be processed (if ip_fw has been loaded as an lkm). Could someone give me some help to figure this out? Cheers, Nick -- Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A "When in doubt, ask someone wiser than yourself..." -unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 00:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20131 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 00:23:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20110; Mon, 14 Sep 1998 00:23:39 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id AAA18054; Mon, 14 Sep 1998 00:23:24 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma018050; Mon Sep 14 00:23:13 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id AAA16550; Mon, 14 Sep 1998 00:23:09 -0700 (PDT) From: Archie Cobbs Message-Id: <199809140723.AAA16550@bubba.whistle.com> Subject: Re: Still! what appears to be VM problems. In-Reply-To: <13818.5746.872010.922783@lupo.thebarn.com> from Russell Cattelan at "Sep 12, 98 01:45:51 am" To: cattelan@thebarn.com (Russell Cattelan) Date: Mon, 14 Sep 1998 00:23:09 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Russell Cattelan writes: > Sep 11 17:34:45 lupo /kernel: pid 11035 (sendmail), uid 0: exited on signal 11 > Sep 11 17:49:45 lupo /kernel: pid 11049 (sendmail), uid 0: exited on signal 11 > > perl in free(): warning: junk pointer, too high to make sense. > perl in free(): warning: junk pointer, too high to make sense. > > This is the latest CAM kernel... so it isn't the "most" to date. We've been seeing a similar problem (or problems) literally for years ! Ie, in 2.2, 3.0, ... Could be one bug, could be more than one bug... but the following things seems to crop up all the time (not necessarily at the same time): - some file is being mmap'd - some process is forking - panic because a process on sleep and run queues at the same time - random segfaults in processes (inetd, sendmail -> because they fork alot?) When we try to look at kernel core dumps, it always seems either completely mysterious (eg, impossible CPU register contents) or almost completely mysterious (because no one here understands the VM code). I guess I'm hoping some VM guru will see this list and think "aha!" .. VM gurus, any ideas? Maybe there's some small race condition in the VM system when a process forks and there's a context switch involving a process using mmap and/or shared memory?? Or maybe just a simple mmap/shared memory bug? -Archie References: [DR97] The Dave Rivers memorial panic [INN98] People with news servers (which use mmap) getting random pages written into files. [SEGV97] Numerous inetd/sendmail random segfault reports to this list ___________________________________________________________________________ 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 Mon Sep 14 07:31:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11667 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 07:31:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isua1.iastate.edu (isua1.iastate.edu [129.186.1.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11659 for ; Mon, 14 Sep 1998 07:31:40 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua1.iastate.edu (8.8.5/8.8.5) with SMTP id IAA18774; Mon, 14 Sep 1998 08:15:44 -0500 (CDT) Message-Id: <199809141315.IAA18774@isua1.iastate.edu> To: Chuck Robey cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions In-reply-to: Your message of "Sun, 13 Sep 1998 16:59:50 EDT." Date: Mon, 14 Sep 1998 08:15:44 CDT From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Do you realize that many of the libc functions need each other as >dependencies? Yes, obviously, but I was not referring to libc or shared code per se. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 08:29:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19369 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 08:29:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18563; Mon, 14 Sep 1998 08:25:52 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id SAA06734; Mon, 14 Sep 1998 18:25:10 +0300 (EEST) (envelope-from ru) Date: Mon, 14 Sep 1998 18:25:10 +0300 From: Ruslan Ermilov To: obrien@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: ports/mail/mutt/patches/patch-05: what for? Message-ID: <19980914182510.A6579@relay.ucb.crimea.ua> Mail-Followup-To: obrien@FreeBSD.org, hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.6i X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! What the patch-05 is used for? GETHOSTNAME_DOMAIN is undefined anyway. It has no effect. Right? It was deleted in 1.2, and restored in 1.3, why? By the way, the latest development version 0.94.6i replaces --enable-hidden-host config option with a runtime option. Best regards, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 11:06:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14889 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 11:06:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14871 for ; Mon, 14 Sep 1998 11:06:47 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA20877; Mon, 14 Sep 1998 11:06:31 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd020828; Mon Sep 14 11:06:29 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA18220; Mon, 14 Sep 1998 11:06:24 -0700 (MST) From: Terry Lambert Message-Id: <199809141806.LAA18220@usr05.primenet.com> Subject: Re: Unused functions To: mike@smith.net.au (Mike Smith) Date: Mon, 14 Sep 1998 18:06:24 +0000 (GMT) Cc: graphix@iastate.edu, tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809140114.SAA08497@word.smith.net.au> from "Mike Smith" at Sep 13, 98 06:14:32 pm X-Mailer: ELM [version 2.4 PL25] 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 > In most object formats, reference information is kept on a per-object > basis (ie. per .o file). Keeping this sort of information on any > smaller granularity would lead to an insane increase in the complexity > and corresponding performance reduction of the link phase. ...and corresponding reduction in time for *re*linking, and reduction in size of the resulting binaries. Basically, it's a compiler-write-benchmark-less-work-to-write thing. > This is why an experienced programmer will group only related items in > a given object. Yes. This is why. > It allows the programmer and the C scoping rules to > work together to determine what should be associated and what need not. Instead of the compiler merely calculating hamiltonian cycles in the dependency graph to do dead code elimination. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 11:12:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16260 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 11:12:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16247 for ; Mon, 14 Sep 1998 11:12:16 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA19195; Mon, 14 Sep 1998 19:12:00 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA09904; Mon, 14 Sep 1998 11:33:11 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199809141033.LAA09904@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Harold Gutch cc: Brian Somers , The Subject: Re: Missing CVS $Id strings In-reply-to: Your message of "Mon, 14 Sep 1998 01:53:29 +0200." <19980914015329.18217@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Sep 1998 11:33:09 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Sep 14, 1998 at 12:14:51AM +0100, Brian Somers wrote: > > Here's what I did: > > > [...] > > > /etc/passwd No documented comment chars > > >From the passwd(5) manpage: > Lines whose first non-whitespace character is a pound-sign (#) are com- > ments, and are ignored. Blank lines which consist only of spaces, tabs > or newlines are also ignored. > > Note that the last I remember is that this is incorrect in > -STABLE (see some -stable archive for more on this topic, the > subject was "Finger and getpwent"). This should be submitted as a bug. Try putting a line beginning with ``#'' in your passwd via ``vipw'' on current.... > -- > bye, logix > > Sleep is an abstinence syndrome wich occurs due to lack of caffein. > Wed Mar 4 04:53:33 CET 1998 #unix, ircnet -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 11:15:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17401 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 11:15:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17375 for ; Mon, 14 Sep 1998 11:15:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00296; Mon, 14 Sep 1998 11:19:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809141819.LAA00296@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), graphix@iastate.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions In-reply-to: Your message of "Mon, 14 Sep 1998 18:06:24 -0000." <199809141806.LAA18220@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Sep 1998 11:19:48 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It allows the programmer and the C scoping rules to > > work together to determine what should be associated and what need not. > > Instead of the compiler merely calculating hamiltonian cycles in > the dependency graph to do dead code elimination. And if I happen to *want* all of the items in a given object (eg. I am using a scripting language that supports primitive lookup via the symbol table, or any other form of lazy runtime linking)? The current rules give the best of both worlds. Don't fix what isn't really broken. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 13:19:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08530 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 13:19:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from du248-16.cc.iastate.edu (du248-16.cc.iastate.edu [129.186.248.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08515 for ; Mon, 14 Sep 1998 13:19:41 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by du248-16.cc.iastate.edu (8.8.5/8.8.5) with SMTP id PAA21067; Mon, 14 Sep 1998 15:17:47 -0500 (CDT) Message-Id: <199809142017.PAA21067@du248-16.cc.iastate.edu> To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions In-reply-to: Your message of "Mon, 14 Sep 1998 11:19:48 PDT." <199809141819.LAA00296@dingo.cdrom.com> Date: Mon, 14 Sep 1998 15:17:45 CDT From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199809141819.LAA00296@dingo.cdrom.com>, Mike Smith writes: >> > It allows the programmer and the C scoping rules to >> > work together to determine what should be associated and what need not. >> >> Instead of the compiler merely calculating hamiltonian cycles in >> the dependency graph to do dead code elimination. > >And if I happen to *want* all of the items in a given object (eg. I am >using a scripting language that supports primitive lookup via the >symbol table, or any other form of lazy runtime linking)? > >The current rules give the best of both worlds. Don't fix what isn't >really broken. Is there any tool that can, as a post process following linking, remove any unused code? Strip just removes the debug symbols correct? Perhaps SuperStrip! This would seem to be a nice feature since it could be run by a person that is aware of the problems it may cause and has done the work to be certain no harm will happen. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 13:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09494 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 13:22:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09468 for ; Mon, 14 Sep 1998 13:22:20 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id NAA10302; Mon, 14 Sep 1998 13:21:58 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd010286; Mon Sep 14 13:21:57 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id NAA26933; Mon, 14 Sep 1998 13:21:54 -0700 (MST) From: Terry Lambert Message-Id: <199809142021.NAA26933@usr05.primenet.com> Subject: Re: Unused functions To: graphix@iastate.edu (Kent Vander Velden) Date: Mon, 14 Sep 1998 20:21:54 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809140009.TAA28013@isua4.iastate.edu> from "Kent Vander Velden" at Sep 13, 98 07:09:16 pm X-Mailer: ELM [version 2.4 PL25] 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 > Just so I completely understand, if I truely use only one function in from > a .o file and no other function is using anything in this .o file, the > entire .o file is still pulled into the executable? So, there are could be > a lot of unused, unreachable code in an executable. Yes, if it's statically linked, and you poorly organize your code. This is why software engineers make more money than mere programmers. > Nothing can be done to remove the bloat after the executable has > been linked? Not quite. But nothing *is* done... > Is this commonly the way its done on other systems as well? Yes. This is a compiler/linker technology issue, not a system issue. > I had always assumed that unused functions and data were tosed out. No. Only for compilers and linkers that optimize for image size and execution speed, instead of for compiler benchmarks. Q: Do you buy a compiler that is very fast, or do you buy the compiler that makes very fast code? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 15:17:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04006 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 15:17:33 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03993 for ; Mon, 14 Sep 1998 15:17:30 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA17663; Mon, 14 Sep 1998 15:17:11 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd017629; Mon Sep 14 15:17:06 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA01956; Mon, 14 Sep 1998 15:17:01 -0700 (MST) From: Terry Lambert Message-Id: <199809142217.PAA01956@usr05.primenet.com> Subject: Re: Unused functions To: mike@smith.net.au (Mike Smith) Date: Mon, 14 Sep 1998 22:17:00 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, graphix@iastate.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809141819.LAA00296@dingo.cdrom.com> from "Mike Smith" at Sep 14, 98 11:19:48 am X-Mailer: ELM [version 2.4 PL25] 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 > > > It allows the programmer and the C scoping rules to > > > work together to determine what should be associated and what need not. > > > > Instead of the compiler merely calculating hamiltonian cycles in > > the dependency graph to do dead code elimination. > > And if I happen to *want* all of the items in a given object (eg. I am > using a scripting language that supports primitive lookup via the > symbol table, or any other form of lazy runtime linking)? > > The current rules give the best of both worlds. Don't fix what isn't > really broken. Dynamic linking requires dlopen, requires a name-to-table-offset mapping (*not* your standard symbol table mechanism!), and will work, even on stripped executables. Yes, dead-code elimination would be "bad" if you were loading objects that called otherwise dead code in the program address space (ie: used the program symbol space as a library symbol space). In such cases, I suggest you don't use -O2, since the compiler will do dead code elimination on you within modules if it thinks it can get away with it right now. So I think the dynmaic linking case and the static case are two *very* different cases. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 15:41:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09290 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 15:41:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09281 for ; Mon, 14 Sep 1998 15:41:50 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-30.camalott.com [208.229.74.30]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA15858; Mon, 14 Sep 1998 17:42:51 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA09355; Mon, 14 Sep 1998 17:40:44 -0500 (CDT) (envelope-from joelh) Date: Mon, 14 Sep 1998 17:40:44 -0500 (CDT) Message-Id: <199809142240.RAA09355@detlev.UUCP> To: Terry Lambert CC: graphix@iastate.edu (Kent Vander Velden), tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <199809142021.NAA26933@usr05.primenet.com> Subject: Re: Unused functions From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199809142021.NAA26933@usr05.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Just so I completely understand, if I truely use only one function in from >> a .o file and no other function is using anything in this .o file, the >> entire .o file is still pulled into the executable? So, there are could be >> a lot of unused, unreachable code in an executable. > Yes, if it's statically linked, and you poorly organize your code. > This is why software engineers make more money than mere programmers. This is also why most libraries tend to define one exported function per object file, or sometimes exported functions that are always used together (foodb_open, foodb_close). >> Nothing can be done to remove the bloat after the executable has >> been linked? > Not quite. But nothing *is* done... What can be done in the compiler and linker alone? If an object file contains both foo() and bar(), and foo calls bar, the linker doesn't know that. Neither does it know about static baz(), which only quux() calls. The user program doesn't call quux, and therefore doesn't call baz, but the linker doesn't know that. I don't see any way to resolve the issue without instrumenting the object file (perhaps by extending stabs?). If that were to be done, then something similar to lorder would do the trick. >> I had always assumed that unused functions and data were tosed out. > No. Only for compilers and linkers that optimize for image size > and execution speed, instead of for compiler benchmarks. > Q: Do you buy a compiler that is very fast, or do you buy the > compiler that makes very fast code? I prefer a compiler that has the choice. This isn't hard, particularly since several optimizations-- including the one under discussion-- are handled by passes over intermediate representations of the code. Given no choice, I tend towards the one that makes fast code. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 16:13:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15090 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 16:13:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA15075 for ; Mon, 14 Sep 1998 16:13:35 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 10258 invoked by uid 1001); 14 Sep 1998 23:13:17 +0000 (GMT) To: tlambert@primenet.com Cc: hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets In-Reply-To: Your message of "Sun, 13 Sep 1998 23:03:26 +0000 (GMT)" References: <199809132303.QAA21895@usr04.primenet.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 15 Sep 1998 01:13:17 +0200 Message-ID: <10256.905814797@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > static int icmpbmcastecho = 1; > > SYSCTL_INT(_net_inet_icmp, OID_AUTO, bmcastecho, CTLFLAG_RW, &icmpbmcastecho, > > 0, ""); > > > > I believe it should be turned *off* by default, and hope this is fixed > > before 3.0 is released. > > Being off by default would break SLP and IPv6 autodetection for > address assignment. When you say SLP, I assume you're talking about RFC 2165. From my reading of RFC 2165, multicast is preferred: The Service Location discovery mechanisms typically multicast messages to as many enterprise networks as needed to establish service availability. The protocol will operate in a broadcast environment with limitations detailed in section 3.6.1. It says that Service Agents must listen to the IP broadcast address, but I assume there are considerably fewer Service Agents than User Agents, and explicitly configuring them to listen to the IP broadcast address would not seem to be an undue hardship. As far as I can see, IPv6 autodetection uses multicast, not broadcast. Also, since the FreeBSD TCP/IP stack currently doesn't implement IPv6, I find it hard to use this as a very strong argument. My conclusion is that we probably need separate sysctl variables for "multicast echo" and "broadcast echo", with the former defaulting to on, and the latter to off. Yes, I volunteer to do this if there is any interest. > Certainly, you should be able to turn it off, but the correct place > to block DOS broadcast ping attacks is your firewall. I agree that this is the best place for it - but I'd also like FreeBSD systems to be secure against smurf attacks out of the box, even if the router/firewall/whatever lets IP broadcast through (and translates it to link-level broadcast). Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 18:25:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03989 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 18:25:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03979 for ; Mon, 14 Sep 1998 18:24:59 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA04014; Mon, 14 Sep 1998 18:22:11 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <35FDC142.A242B43E@dal.net> Date: Mon, 14 Sep 1998 18:22:10 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE-0914 i386) MIME-Version: 1.0 To: Brian Somers CC: The Subject: Re: Missing CVS $Id strings References: <199809132314.AAA05075@woof.lan.awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Many many thanks. :) Don't let the below be interpreted as ungratefulness. I also understand Bruce's point about not tagging files on a vendor branch, and I suppose that the same argument can be made for the named.root file. Fortunately none of those files will be changing often for the same reason. Brian Somers wrote: > Here's what I did: > > > /etc/gnats/freefall No source The Makefile in /usr/src/gnu/usr.bin/send-pr copies the categories file in that same directory to /etc/gnats/freefall. My testing indicates that a # comment in that file is harmless, but someone else might want to look it over. Given that this file hardly ever changes putting an $Id string in it isn't a priority. > > /etc/motd Skipped > > /boot.help Skipped Ok, this is fine... probably better for aesthetic reasons anyway. > > /etc/master.passwd No source > > /etc/passwd No documented comment chars > > /var/crash/minfree No documented comment chars > > /.cshrc Ok (same as /root/.cshrc) I meant to delete these files from the list, sorry. Thank you once again, :) Doug -- *** Chief Operations Officer, DALnet IRC network *** "Yes, the president should resign. He has lied to the American people, time and time again, and betrayed their trust. He is no longer an effective leader. Since he has admitted guilt, there is no reason to put the American people through an impeachment. He will serve absolutely no purpose in finishing out his term; the only possible solution is for the president to save some dignity and resign." - William Jefferson Clinton, 1974 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 18:54:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08206 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 18:54:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08196 for ; Mon, 14 Sep 1998 18:54:31 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA24867; Mon, 14 Sep 1998 18:54:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd024842; Mon Sep 14 18:54:07 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA12519; Mon, 14 Sep 1998 18:54:03 -0700 (MST) From: Terry Lambert Message-Id: <199809150154.SAA12519@usr05.primenet.com> Subject: Re: Unused functions To: joelh@gnu.org Date: Tue, 15 Sep 1998 01:54:03 +0000 (GMT) Cc: tlambert@primenet.com, graphix@iastate.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809142240.RAA09355@detlev.UUCP> from "Joel Ray Holveck" at Sep 14, 98 05:40:44 pm X-Mailer: ELM [version 2.4 PL25] 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 > What can be done in the compiler and linker alone? If an object file > contains both foo() and bar(), and foo calls bar, the linker doesn't > know that. What? Then how can my definition of "printf" override the library definition? The object file format certainly knows about intra-object dependencies. > Neither does it know about static baz(), which only quux() > calls. True. > The user program doesn't call quux, and therefore doesn't call > baz, but the linker doesn't know that. False. Libraries are *not* stripped. There is also a difference between strip, strip -d, and strip -x. if -x was used, then the symbol will have been eliminated, and the code dependency will be known (or agregated). If you aim the gun at your foot and pull the trigger, it's UNIX's job to ensure reliable delivery of the bullet to where you aimed the gun (in this case, Mr. Foot). > I don't see any way to resolve the issue without instrumenting the > object file (perhaps by extending stabs?). If that were to be done, > then something similar to lorder would do the trick. That's what symbols are for. There are alread sufficient symbols tro support this (presuing you don't -x anything). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 18:59:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09121 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 18:59:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09113 for ; Mon, 14 Sep 1998 18:59:34 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id DAA02165; Tue, 15 Sep 1998 03:55:23 +0200 (CEST) Message-ID: <19980915035523.35224@foobar.franken.de> Date: Tue, 15 Sep 1998 03:55:23 +0200 From: Harold Gutch To: Brian Somers Cc: The Subject: Re: Missing CVS $Id strings References: <19980914015329.18217@foobar.franken.de> <199809141033.LAA09904@woof.lan.awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199809141033.LAA09904@woof.lan.awfulhak.org>; from Brian Somers on Mon, Sep 14, 1998 at 11:33:09AM +0100 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 14, 1998 at 11:33:09AM +0100, Brian Somers wrote: > > > > /etc/passwd No documented comment chars > > > > >From the passwd(5) manpage: > > Lines whose first non-whitespace character is a pound-sign (#) are com- > > ments, and are ignored. Blank lines which consist only of spaces, tabs > > or newlines are also ignored. > > > > Note that the last I remember is that this is incorrect in > > -STABLE (see some -stable archive for more on this topic, the > > subject was "Finger and getpwent"). > > This should be submitted as a bug. Try putting a line beginning with > ``#'' in your passwd via ``vipw'' on current.... > As I don't run -CURRENT, i can't say anything on this topic, the comment-stuff definitely is somehow broken in -STABLE (at least it can can be called a documentation bug). To fresh up this whole case again, in the end the 2.2-manpage says: [...] updated to properly support netgroups in FreeBSD 2.0.5. Support for com- ments first appeared in FreeBSD 3.0. which doesn't quite fit for a 2.2-manpage (yes, the manpage is correct for 2.2 too, as it says that this behaviour is new in 3.0, still it shouldn't be in a 2.2-manpage IMHO). Due to me not running -CURRENT, I can't say anything on the degree of brokenness of this feature there, but nethertheless IMO it shouldn't be mentioned in the manpage before it's working. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 14 20:51:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19819 for freebsd-hackers-outgoing; Mon, 14 Sep 1998 20:51:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAB19813 for ; Mon, 14 Sep 1998 20:51:36 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-30.camalott.com [208.229.74.30]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA07865; Mon, 14 Sep 1998 22:53:18 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA10597; Mon, 14 Sep 1998 22:51:03 -0500 (CDT) (envelope-from joelh) Date: Mon, 14 Sep 1998 22:51:03 -0500 (CDT) Message-Id: <199809150351.WAA10597@detlev.UUCP> To: Terry Lambert CC: joelh@gnu.org, tlambert@primenet.com, graphix@iastate.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: <199809150154.SAA12519@usr05.primenet.com> Subject: Re: Unused functions From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199809150154.SAA12519@usr05.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What can be done in the compiler and linker alone? If an object file >> contains both foo() and bar(), and foo calls bar, the linker doesn't >> know that. > What? > Then how can my definition of "printf" override the library > definition? Because printf is alone in its object file. (I am referring to the .o, before it goes into libc.a or libc.so.*, of course.) There's nothing else in that object file that calls it, so all calls are bound at link time. Try this simple test: --- hello_lib.h --- extern char* hello_str(void); --- hello_lib.c --- #include "hello_lib.h" char* hello_str1(void) { return "hello world"; } char* hello_str(void) { return hello_str1(); } --- hello_tst.c --- #include #include "hello_lib.h" char* hello_str1(void) { return "Hello, world!"; } void main(void) { puts(hello_str()); } --- Makefile --- LIB=hello SRCS=hello_lib.c SHLIB_MAJOR=1 SHLIB_MINOR=0 hello_tst: gcc -o hello_tst hello_tst.c -L. -lhello .include --- end --- detlev$ make all hello_tst Warning: Object directory not changed from original /home/joelh/src/hello gcc -O -pipe -c hello_lib.c -o hello_lib.o building standard hello library ranlib libhello.a gcc -fpic -DPIC -O -pipe -c hello_lib.c -o hello_lib.so building shared hello library (version 1.0) gcc -o hello_tst hello_tst.c -L. -lhello detlev$ ./hello_tst hello world detlev$ Note that the message originally defined by the library was displayed, implying that the binding of the call was done at hello_lib.o's link time, not at hello_tst's. > The object file format certainly knows about intra-object > dependencies. Where? I couldn't see anything about it in either the stabs info from a .s file or from a ldd -v examination. I don't mind looking for more, but in point of fact, I don't know where to look. >> The user program doesn't call quux, and therefore doesn't call >> baz, but the linker doesn't know that. > False. > Libraries are *not* stripped. There is also a difference between > strip, strip -d, and strip -x. if -x was used, then the symbol > will have been eliminated, and the code dependency will be known > (or agregated). Where are these code dependencies located? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 03:06:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02456 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 03:06:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02447 for ; Tue, 15 Sep 1998 03:06:41 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id MAA07559; Tue, 15 Sep 1998 12:06:22 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA22649; Tue, 15 Sep 1998 12:06:21 +0200 (MET DST) Message-ID: <19980915120620.32623@follo.net> Date: Tue, 15 Sep 1998 12:06:20 +0200 From: Eivind Eklund To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions References: <199809140114.SAA08497@word.smith.net.au> <199809141806.LAA18220@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809141806.LAA18220@usr05.primenet.com>; from Terry Lambert on Mon, Sep 14, 1998 at 06:06:24PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Moved to -chat] On Mon, Sep 14, 1998 at 06:06:24PM +0000, Terry Lambert wrote: [... on dead code elimination at the final code level ...] > > It allows the programmer and the C scoping rules to > > work together to determine what should be associated and what need not. > > Instead of the compiler merely calculating hamiltonian cycles in > the dependency graph to do dead code elimination. I don't get what Hamilton cycles has to do with this. It looks like a simple mark-and-sweep GC to me, and I can't see how looking for Hamilton cycles are going to find. Also, I can't think of a single case where I have written code that is likely to have even a single Hamilton cycle - I usually don't call main() from elsewhere in my program (and I certainly don't call _start). If you can involve Hamilton cycles at all here, it sounds like it must be on a subgraph. How? For those following: A Hamilton cycle touch every node in the graph exactly once, and forms a cycle. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 03:22:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04282 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 03:22:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.10.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04268 for ; Tue, 15 Sep 1998 03:22:36 -0700 (PDT) (envelope-from kheuer@gwdu60.gwdg.de) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.9.0/8.9.0) with SMTP id MAA06006 for ; Tue, 15 Sep 1998 12:22:11 +0200 (CEST) Date: Tue, 15 Sep 1998 12:22:11 +0200 (CEST) From: Konrad Heuer To: freebsd-hackers@FreeBSD.ORG Subject: Catching SIGSEGV 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 May I ask my question here although it's not correlated to FreeBSD development? I write a program which shall run under FreeBSD and want to catch SIGSEGV to count these events. So the program is like this: int nsegv = 0; int *ptr; int zero = 0; void sighdl ( int sig ) { ptr = &zero; nsegv++; } int dowork ( ) { int buf; signal(SIGSEGV, sighdl); ptr = InvalidAddress; buf = *ptr; } Ok, the signal handler gets called, ptr will be reset to a legal address, but nevertheless after returning from the signal handler it will be called again immediately resulting in an infinite loop. Where's my mistake? What can I do to prevent that loop? Thanks for any reply. Regards Konrad Heuer // Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH // Goettingen (GWDG), Am Fassberg, D-37077 Goettingen, Germany // // kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 04:15:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14981 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 04:15:02 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14976 for ; Tue, 15 Sep 1998 04:15:00 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id HAA01989; Tue, 15 Sep 1998 07:16:00 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 15 Sep 1998 07:16:00 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Konrad Heuer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i had to write a short test program, but simply when SIGSEGV is caught it seems that the return address is set to as to try to "retry" the operation that failed. take a look at the output of this program: #include int nsegv = 0; int ptr; int zero = 0; int *inv = 0; void sighdl ( int sig ) { ptr = &zero; printf("%x\n",inv);fflush(0); inv++; /* remove this to see 0 vs behaviour */ nsegv++; } int main( ) { int buf; signal(SIGSEGV, sighdl); ptr = *(++inv); /* note this only happens once, put the ++ after and it starts at 0 rather than 4 */ buf = ptr; return 1; } it compiles with a warning... sue me i'm up 24hrs :P Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 15 Sep 1998, Konrad Heuer wrote: > > May I ask my question here although it's not correlated to FreeBSD > development? > > I write a program which shall run under FreeBSD and want to catch SIGSEGV > to count these events. So the program is like this: > > int nsegv = 0; > int *ptr; > int zero = 0; > > void sighdl ( int sig ) > { > ptr = &zero; > nsegv++; > } > > int dowork ( ) > { > int buf; > > signal(SIGSEGV, sighdl); > > ptr = InvalidAddress; > buf = *ptr; > } > > Ok, the signal handler gets called, ptr will be reset to a legal address, > but nevertheless after returning from the signal handler it will be called > again immediately resulting in an infinite loop. > > Where's my mistake? What can I do to prevent that loop? > Thanks for any reply. > > Regards > Konrad Heuer > > // Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH > // Goettingen (GWDG), Am Fassberg, D-37077 Goettingen, Germany > // > // kheuer@gwdu60.gwdg.de > > > 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 Sep 15 05:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25303 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 05:33:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25277 for ; Tue, 15 Sep 1998 05:33:23 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id QAA07541; Tue, 15 Sep 1998 16:32:52 +0200 (MET DST) Message-ID: <19980915163251.A7518@cons.org> Date: Tue, 15 Sep 1998 16:32:51 +0200 From: Martin Cracauer To: Konrad Heuer , freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Konrad Heuer on Tue, Sep 15, 1998 at 12:22:11PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Konrad Heuer wrote: > > May I ask my question here although it's not correlated to FreeBSD > development? > > I write a program which shall run under FreeBSD and want to catch SIGSEGV > to count these events. You have to longjmp out of your signal handler. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 06:36:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07709 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 06:36:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07693 for ; Tue, 15 Sep 1998 06:36:46 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id PAA00371; Tue, 15 Sep 1998 15:30:57 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199809151330.PAA00371@ocean.campus.luth.se> Subject: Re: Catching SIGSEGV In-Reply-To: from Konrad Heuer at "Sep 15, 98 12:22:11 pm" To: kheuer@gwdu60.gwdg.de (Konrad Heuer) Date: Tue, 15 Sep 1998 15:30:57 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 According to Konrad Heuer: > int nsegv = 0; > int *ptr; > int zero = 0; > > void sighdl ( int sig ) > { > ptr = &zero; > nsegv++; > } > > int dowork ( ) > { > int buf; > > signal(SIGSEGV, sighdl); > > ptr = InvalidAddress; > buf = *ptr; > } My guess is that you would want to declare things like this: volatile int nsegv = 0; volatile int *ptr; int zero = 0; Then the restarted "buf = *ptr;" line will not use a buffered value for ptr but read it from memory. I think. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 08:03:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24622 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 08:03:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA24614 for ; Tue, 15 Sep 1998 08:03:01 -0700 (PDT) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id LAA15244; Tue, 15 Sep 1998 11:01:51 -0400 Date: Tue, 15 Sep 1998 11:01:50 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Mikael Karpberg cc: Konrad Heuer , freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV In-Reply-To: <199809151330.PAA00371@ocean.campus.luth.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 On Tue, 15 Sep 1998, Mikael Karpberg wrote: > My guess is that you would want to declare things like this: > volatile int nsegv = 0; > volatile int *ptr; > int zero = 0; > > Then the restarted "buf = *ptr;" line will not use a buffered value for ptr > but read it from memory. I think. Depends on the instruction and how restart happens. I think it's going to be iffy for portability. But it will be interesting to see how it works out :-) ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 08:55:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02499 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 08:55:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02492 for ; Tue, 15 Sep 1998 08:55:27 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id MAA27445; Tue, 15 Sep 1998 12:06:35 -0400 (EDT) Date: Tue, 15 Sep 1998 12:06:34 -0400 (EDT) From: Charles Youse To: Mikael Karpberg cc: Konrad Heuer , freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV In-Reply-To: <199809151330.PAA00371@ocean.campus.luth.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 On Tue, 15 Sep 1998, Mikael Karpberg wrote: > My guess is that you would want to declare things like this: > > volatile int nsegv = 0; > volatile int *ptr; > int zero = 0; > > Then the restarted "buf = *ptr;" line will not use a buffered value for ptr > but read it from memory. I think. Unfortunately, because the value of ptr is most likely read from a register in the instruction that faults, declaring it volatile does not help. Volatile prevents optimization, but loading a value into a register to perform indirection is not an optimization, and in most cases (and on most architectures) this load is *required*. Restarting the instruction, despite the changed value of ptr, will not change the value in the register, and so the fault will occur again. Chuck Youse cyouse@syncom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 09:41:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11047 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 09:41:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11027 for ; Tue, 15 Sep 1998 09:41:53 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id MAA03417; Tue, 15 Sep 1998 12:43:05 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 15 Sep 1998 12:43:05 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Ron G. Minnich" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV 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 ok, basically what is going on is that there is data being read for where it ain't supposed to be, the OS traps and your signal handler ought to handle it, else when the OS _RESTARTS_ the intruction you'll fault again then then loop. "there is no buffer in memory" it's the reading of the memory that's causing the fault, someone in this thread brought up setjmp, that could also work, another trick would be to change the value of 'ptr' to something valid, (in the handler) then when the instruction is restarted it will access valid memory and proceed as planned. > On Tue, 15 Sep 1998, Mikael Karpberg wrote: > > My guess is that you would want to declare things like this: > > volatile int nsegv = 0; > > volatile int *ptr; > > int zero = 0; > > > > Then the restarted "buf = *ptr;" line will not use a buffered value for ptr > > but read it from memory. I think. that is TOTALLY wrong. no matter what happens the CPU will fault on the fetch from the bad address. > Depends on the instruction and how restart happens. I think it's going to > be iffy for portability. But it will be interesting to see how it works > out :-) there was an OS that did something funky to the first page of memory that allowed programmers to abuse the fact that it was null and accessable. many programs broke when the system was brought to a different archetecture. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 10:01:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15713 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 10:01:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from crap.31337.net (crap.31337.net [194.109.86.254] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15662; Tue, 15 Sep 1998 10:01:26 -0700 (PDT) (envelope-from alexlh@crap.31337.net) Received: (from alexlh@localhost) by crap.31337.net (8.8.8/8.8.8) id SAA17958; Tue, 15 Sep 1998 18:37:45 GMT (envelope-from alexlh) Message-ID: <19980915183742.20167@funk.org> Date: Tue, 15 Sep 1998 18:37:42 +0000 From: Alex Le Heux To: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: 3Com 3c900B-FL? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is anyone working on support for the 3c900B-FL card? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 12:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15187 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 12:39:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15151; Tue, 15 Sep 1998 12:39:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00585; Tue, 15 Sep 1998 12:44:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809151944.MAA00585@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Le Heux cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 3Com 3c900B-FL? In-reply-to: Your message of "Tue, 15 Sep 1998 18:37:42 -0000." <19980915183742.20167@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Sep 1998 12:44:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > Is anyone working on support for the 3c900B-FL card? Is this substantially different from the other members of the 3c900 family? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 14:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03943 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 14:10:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03865; Tue, 15 Sep 1998 14:10:10 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA22910; Tue, 15 Sep 1998 14:09:49 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd022838; Tue Sep 15 14:09:40 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA25292; Tue, 15 Sep 1998 14:09:35 -0700 (MST) From: Terry Lambert Message-Id: <199809152109.OAA25292@usr09.primenet.com> Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets To: sthaug@nethelp.no Date: Tue, 15 Sep 1998 21:09:35 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <10256.905814797@verdi.nethelp.no> from "sthaug@nethelp.no" at Sep 15, 98 01:13:17 am X-Mailer: ELM [version 2.4 PL25] 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 > Also, since the FreeBSD TCP/IP stack currently doesn't implement IPv6, > I find it hard to use this as a very strong argument. Both the WIDE IPv6 and the INRIA IPv6 run under FreeBSD. > My conclusion is that we probably need separate sysctl variables for > "multicast echo" and "broadcast echo", with the former defaulting to > on, and the latter to off. Yes, I volunteer to do this if there is > any interest. I think it should default to "on", since that is historical behaviour, and because I've had more than one MIS problem that came down to not being able to identify the hardware address of a misconfigured machine because the !@#!@$! thing would not reply to broadcast ping, and didn't support any services that you could telnet to to get it in the arp table to look there. At this point, lack of a broadcast ping degrades to a cube-to-cube search for the offending Microsoft box. If FreeBSD also fails to reply to perfectly valid broadcasts, well, then it becomes a cube-to-cube search for the offending Microsoft *or* FreeBSD box (bletch!). If you are worried about DOS attacks, and you are too stupid to set up your firewall correctly, I have little sympathy, since if nothing else, they could hijack your NFS connections (which I presume you were also too dumb to firewall: stupid is as stupid does, after all), and then sysctl the things back on themselves. In other words, either your network is secure by design, or it's broken by design, and there is no "happy medium". > > Certainly, you should be able to turn it off, but the correct place > > to block DOS broadcast ping attacks is your firewall. > > I agree that this is the best place for it - but I'd also like FreeBSD > systems to be secure against smurf attacks out of the box, even if the > router/firewall/whatever lets IP broadcast through (and translates it > to link-level broadcast). And what about NFS hijack, SMB hijack, source routing, IP spoofing, etc.? A firewall is a requirement for a secure network; that's all there is to it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 14:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04117 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 14:11:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04027; Tue, 15 Sep 1998 14:10:54 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA14252; Tue, 15 Sep 1998 14:10:33 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd014225; Tue Sep 15 14:10:27 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA25347; Tue, 15 Sep 1998 14:10:20 -0700 (MST) From: Terry Lambert Message-Id: <199809152110.OAA25347@usr09.primenet.com> Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets To: sthaug@nethelp.no Date: Tue, 15 Sep 1998 21:10:19 +0000 (GMT) Cc: tlambert@primenet.com, hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <10256.905814797@verdi.nethelp.no> from "sthaug@nethelp.no" at Sep 15, 98 01:13:17 am X-Mailer: ELM [version 2.4 PL25] 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 > > Being off by default would break SLP and IPv6 autodetection for > > address assignment. > > When you say SLP, I assume you're talking about RFC 2165. From my > reading of RFC 2165, multicast is preferred: Sorry; I should have said "RLP". SLP uses multicase; RLP use UDP broadcast. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 14:27:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08643 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 14:27:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08636 for ; Tue, 15 Sep 1998 14:27:27 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA02512; Tue, 15 Sep 1998 14:27:09 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd002486; Tue Sep 15 14:27:04 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id OAA25996; Tue, 15 Sep 1998 14:27:00 -0700 (MST) From: Terry Lambert Message-Id: <199809152127.OAA25996@usr09.primenet.com> Subject: Re: Unused functions To: eivind@yes.no (Eivind Eklund) Date: Tue, 15 Sep 1998 21:27:00 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980915120620.32623@follo.net> from "Eivind Eklund" at Sep 15, 98 12:06:20 pm X-Mailer: ELM [version 2.4 PL25] 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 dead code elimination at the final code level ...] > > > It allows the programmer and the C scoping rules to > > > work together to determine what should be associated and what need not. > > > > Instead of the compiler merely calculating hamiltonian cycles in > > the dependency graph to do dead code elimination. > > I don't get what Hamilton cycles has to do with this. It looks like a > simple mark-and-sweep GC to me, and I can't see how looking for > Hamilton cycles are going to find. You are looking for code without cycles through known referenced symbols (if it has a cyle through a known referenced symbol, you add it to the list of symbols). Since you already have the tree in memory, with the edges correctly arranged, this is simpler than trying to run Warshall's across the entrie symbol table from the point of view of each node (and cheaper by an order of magnitude). > Also, I can't think of a single case where I have written code that is > likely to have even a single Hamilton cycle - I usually don't call > main() from elsewhere in my program (and I certainly don't call > _start). If you can involve Hamilton cycles at all here, it sounds > like it must be on a subgraph. How? Consider all top level "known referenced" symbols to be connected by an edge. > For those following: A Hamilton cycle touch every node in the graph > exactly once, and forms a cycle. More importantly, you can tell as DAG from a DCG. Symbols in a DCG, where "known refrenced" forms an edge to the rest of the graph, means that you have to reference increasingly fewer nodes as you go on. Note: this rather dry argument still applies only to dead code elimination in library archives in statically linked images). Consider the user's symbols seperate from other symbols (you have to do this because of Mike Smith's point about the user's symbols vs. library symbols). By definition, these symbols are considered "used". Then you go through the archives (libraries), and examine these symbols. These are second order symbols. You sort these onto either the "used" or the "unknown" list. Then you look for a DCG using the "used" as a list, and traverse only the "unknown" entries. If you find a cycle, you add the "unknown" symbols in the cycle to the "used" list. You repeat this process until, after a pass, no new symbols are added to the "used" list. The remaining symbols on the "unknown" list now represent "dead code"/"dead data". Now you eliminate this code from inclusion in the relocation and image write phase of the link. This works, even in the case of static symbols, since statics must also be relocated, and therefore will have a pseudo-symbol. All code/data between an unused symbol or pseudo-symbol and a used one is dead, and may be eliminated. Actually, you should talk to SEF about this; he's an old compiler guru, and he worked on the Microsoft compiler for SCO. He has an interesting "shaggy dog" story about emission of pseudo-symbols for data on something like: main() { char *str = "Hello World!" + 6; puts( str - 6); puts( "Goodbye "); puts( str); } [ oversimplification; the exact case was the loss of "Hello " through dead-data elimination for the "whoami" program, if I remember correctly... Microsoft failed to emit a correct pseudo-symbol for the start of the str data, emitting only _str for "World!"... ] Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 14:34:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10676 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 14:34:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ms7.hinet.net (ms7.hinet.net [168.95.4.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08571; Tue, 15 Sep 1998 14:26:22 -0700 (PDT) (envelope-from bw006x@ms22.hinet.net) Received: from sen005644 (h252.s2.ts32.hinet.net [163.32.2.252]) by ms7.hinet.net (8.8.8/8.8.8) with SMTP id FAA18024; Wed, 16 Sep 1998 05:25:40 +0800 (CST) Date: Wed, 16 Sep 1998 05:25:40 +0800 (CST) Message-Id: <199809152125.FAA18024@ms7.hinet.net> From: fbv006394@ms7.hinet.net Subject: ²ú²ï¤Ñ¦a¯S»ù³q³ø¡@ dúPþ©ûBûBþ©úP d X-Mailer: Mozilla 4.01 [tw] (Win95; I) Content-Type: TEXT/PLAIN; charset=BIG5 to: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ²ú²ï¤Ñ¦a ¥þ¦~µL¥ðªº¦bºô¸ô¤W¬°±z´£¨Ñ¶®ªÚ²£«~¥þ°ê°e³f¨ì©²ªºªA°È¡@ dúPþ©ûBûBþ©úP d Åý±z±o¥H§K¨ü¶ë¨®¤§­W »´ÃP¨É¨ü ¨ÉÅA¥þ²y 112¦~ªº¶®ªÚª¾¦W²£«~ ¶®ªÚ ¤ñ¤k¤H§ó¤F¸Ñ¤k¤H ¦æ¾P¥þ²y130­Ó°ê®a «~½è­È±o±zªº«H¿à ­Y¥»«H¥ó¹ï±z³y¦¨§xÂZ §Ú­Ì°£¤F¸ÛÀµªº­Pºp¥~ ¤]½Ð³qª¾§Ú­Ì§R°£ ÁÂÁ mailto:avon0916@geocities.com?subject=DeleteMe_-6423 [¥»¶g¯S»ù«~¡@¥»¶g¦³65ºØºô¤Í¯S»ù«~­ò ¥þ­± 3 ~ 7.5§é ½Ð¤Wºô¿ïÁÊ] http://www.geocities.com/FashionAvenue/Catwalk/3625/net13.htm 1.¨k©Ê¿i¬â¬~­±Á÷(¤é¥»Gravis) ¥«»ù 250 ºô¤Í»ù ¢°¢µ¢¯ ¦Û«H»P¾y¤O±q³oùض}©l ¨k¤HªºÁy ¬~Áy§ó»Ý­n¥h¨¤½è 2.Âù¦â®B»I(ºë«~·mGo ¬ü°ê­ì¸Ë) ¥«»ù 350 ºô¤ÍÀu´f»ù ¢°¢´¢¸ §t·LÅnÂA±m²É¤l ªø«OÂA¼í®B¦â¡@¤@¤ä®B±m¥i¯«©_§e²{ ±K±m ¯]¥ú ²V¦â ¥|ºØ®B®Ä 3.¥h¨¤½è¿i¬âÁ÷(°ò¦«O¾i¥[±j ¬ü°ê­ì¸Ë¶i¤f) ¥«»ù 600 ºô¤ÍÀu´f»ù ¢²¢°¢° ¦³®Ä¸Ñ¨M¦]¦Ñ¤Æ¨¤½è ©Î¦Ã«¯°ï¿n¡A³y¦¨¦Ù½§Åf¨H¡B²ÊÁW¡B¯h­Â°ÝÃD 4.¶W¯Å²H´³²Õ¦X(¤é¥»­ì¸Ë¶i¤f) ¥«»ù 3100 ºô¤ÍÀu´f»ù ¢°¢¸¢±¢¯ ÂùºÞ»ô¤U ±Æ°£¶Â¦â¯À §í¨î¦A¥Í ­é°£¦Ñ¼o¨¤½è ¦A³y¤k©Ê¦Û«H 5.Á¥Á¨¦p¶³¯Ý¸n ¥«»ù 850 ºô¤ÍÀu´f»ù ¢µ¢°¢± ¶W²ÓÅÖºû µ·½v¥ú¿A ªA¶KµÎ¾A ¥ßÅé¯BÀJ¨ë¸Á¢µ· µØÄR®öº© ±j¯P§l¤Þ±zªº¥L µL¥i¨ú¥Nªº¥Ø¥úµJÂI Ä_¨©¦Û¤v¡@´N±q¤µ¤Ñ¶}©l­ò ¢ð¢ü¢ü¢ø¡G¡þ¡þ¢ë¢÷¢õ¢í¡D¢ü¢÷¡þ¢ô£B¢û¢û¢é úPþ©ûBûBþ©úP d To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 15:13:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21347 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 15:13:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from crap.31337.net (crap.31337.net [194.109.86.254] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21319; Tue, 15 Sep 1998 15:13:44 -0700 (PDT) (envelope-from alexlh@funk.org) Received: from nose (nose.funk.org [194.109.86.229]) by crap.31337.net (8.8.8/8.8.8) with SMTP id XAA18243; Tue, 15 Sep 1998 23:49:15 GMT (envelope-from alexlh@funk.org) Message-Id: <3.0.5.32.19980916001225.00a0a420@crap.31337.net> X-Sender: alexlh@crap.31337.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 16 Sep 1998 00:12:25 +0200 To: Mike Smith From: Alex Le Heux Subject: Re: 3Com 3c900B-FL? Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199809151944.MAA00585@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:44 15-09-98 -0700, Mike Smith wrote: >> Hi, >> >> Is anyone working on support for the 3c900B-FL card? > >Is this substantially different from the other members of the 3c900 >family? > I have no clue. This is what the probe looks like: Sep 15 18:27:05 cthulu /kernel: pci0:8: vendor=0x10b7, device=0x900a,class=network (ethernet) int a irq 10 [no driver assigned] Alex --- Water water everywhere, and not a drop to drink Lusers lusers everywhere, and not a one can think - alt.sysadmin.recovery 18/08/98 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 16:16:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03353 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 16:16:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03317 for ; Tue, 15 Sep 1998 16:16:51 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-107.camalott.com [208.229.74.107]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA01407; Tue, 15 Sep 1998 17:29:03 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA13470; Tue, 15 Sep 1998 17:26:55 -0500 (CDT) (envelope-from joelh) Date: Tue, 15 Sep 1998 17:26:55 -0500 (CDT) Message-Id: <199809152226.RAA13470@detlev.UUCP> To: Alfred Perlstein CC: "Ron G. Minnich" , freebsd-hackers@FreeBSD.ORG In-reply-to: Subject: Re: Catching SIGSEGV From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > there was an OS that did something funky to the first page of memory that > allowed programmers to abuse the fact that it was null and accessable. > many programs broke when the system was brought to a different > archetecture. You're using it. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 18:58:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03919 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 18:58:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03891 for ; Tue, 15 Sep 1998 18:58:07 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id VAA03889; Tue, 15 Sep 1998 21:59:16 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 15 Sep 1998 21:59:16 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Joel Ray Holveck cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV In-Reply-To: <199809152226.RAA13470@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > there was an OS that did something funky to the first page of memory that > > allowed programmers to abuse the fact that it was null and accessable. > > many programs broke when the system was brought to a different > > archetecture. > > You're using it. (i posted that after 24hours of coding / fighting a bad fbsd install) anyhow, the OS was BSD, and it was the VAX that it was done on? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 15 19:18:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07901 for freebsd-hackers-outgoing; Tue, 15 Sep 1998 19:18:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07856 for ; Tue, 15 Sep 1998 19:18:32 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-120.camalott.com [208.229.74.120]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id VAA20679; Tue, 15 Sep 1998 21:20:16 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id VAA04311; Tue, 15 Sep 1998 21:18:08 -0500 (CDT) (envelope-from joelh) Date: Tue, 15 Sep 1998 21:18:08 -0500 (CDT) Message-Id: <199809160218.VAA04311@detlev.UUCP> To: Alfred Perlstein CC: Joel Ray Holveck , freebsd-hackers@FreeBSD.ORG In-reply-to: Subject: Re: Catching SIGSEGV From: Joel Ray Holveck References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> there was an OS that did something funky to the first page of memory that >>> allowed programmers to abuse the fact that it was null and accessable. >>> many programs broke when the system was brought to a different >>> archetecture. >> You're using it. > (i posted that after 24hours of coding / fighting a bad fbsd install) I understand. > anyhow, the OS was BSD, and it was the VAX that it was done on? Yes. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 01:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26258 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 01:03:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26250 for ; Wed, 16 Sep 1998 01:03:34 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id KAA25076; Wed, 16 Sep 1998 10:03:13 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id KAA27161; Wed, 16 Sep 1998 10:03:12 +0200 (MET DST) Message-ID: <19980916100311.62440@follo.net> Date: Wed, 16 Sep 1998 10:03:11 +0200 From: Eivind Eklund To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions References: <19980915120620.32623@follo.net> <199809152127.OAA25996@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809152127.OAA25996@usr09.primenet.com>; from Terry Lambert on Tue, Sep 15, 1998 at 09:27:00PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 15, 1998 at 09:27:00PM +0000, Terry Lambert wrote: > > [... on dead code elimination at the final code level ...] > > > > It allows the programmer and the C scoping rules to > > > > work together to determine what should be associated and what need not. > > > > > > Instead of the compiler merely calculating hamiltonian cycles in > > > the dependency graph to do dead code elimination. > > > > I don't get what Hamilton cycles has to do with this. It looks like a > > simple mark-and-sweep GC to me, and I can't see how looking for > > Hamilton cycles are going to find. > > You are looking for code without cycles through known referenced > symbols (if it has a cyle through a known referenced symbol, you > add it to the list of symbols). Since you already have the tree > in memory, with the edges correctly arranged, this is simpler than > trying to run Warshall's across the entrie symbol table from the > point of view of each node (and cheaper by an order of magnitude). Hmmm. I can't see any reason why you would want to do a Floyd-Warshall - that calculate the connectivity of the entire graph, which is really producing a lot of data you don't need. I can see two ways of doing this that seem useful. Both of them require (well, prefer) a bit of used/unused for each symbol (partial pseudo-code follows below). (1) Recursive mark'n'sweep void Symbol_MarkAllChildren(struct Symbol *pSymbol) { int iChild; if (!pSymbol->isUsed) { pSymbol->isUsed = 1; for (iChild = 0; iChild < pSymbol->nChildren; iChild++) Symbol_MarkAllChildren(pSymbol->aChildren[iChild]); } } Clear_isUsed_in_all_symbols(); for (pSymbol over each symbol in the initially used set) { Symbol_MarkAllChildren(pSymbol); } /* Symbols marked with 'isUsed' are needed - the rest can be discarded */ (2) Non-recursive mark'n'sweep void Symbol_MarkChildren(struct Symbol *pSymbol) { int iChild; for (iChild = 0; iChild < pSymbol->nChildren; iChild++) { if (!pSymbol->aChildren[iChild]->isUsed) { pSymbol->aChildren[iChild]->isUsed = 1; Symbol_TransferToTempUsedList(pSymbol->aChildren[iChild]); } } } Clear_isUsed_in_all_symbols(); for (pSymbol over each symbol in the initially used set) { Symbol_MarkChildren(pSymbol); Symbol_TransferToFinalUsedList(pSymbol); } do { for (pSymbol over each symbol in the TempUsedList) { if (pSymbol->isUsed) { Symbol_MarkChildren(pSymbol); Symbol_TransferToFinalUsedList(pSymbol); } } } while(!List_isEmpty(TempUsedList)); /* Symbols marked isUsed are needed - the rest can be discarded. The symbols to be used are in the 'FinalUsedList', while the ones that are to be discarded are left in the inital pool */ Both algorithm 1 and 2 are o(N) and O(N) in the number of edges connecting the set of used symbols. The only case you can avoid examining all of these edges is if all symbols are included in the final used set; then you could do a cutoff. I don't think it would be worthwhile, though. The algorithms are sort-of equal - algorithm 1 just use the stack for storing examination order, while algorithm 2 does the same thing using three lists, giving a slightly different order for the marking (basically a depth-first vs a breadth-first walk). > > Also, I can't think of a single case where I have written code that is > > likely to have even a single Hamilton cycle - I usually don't call > > main() from elsewhere in my program (and I certainly don't call > > _start). If you can involve Hamilton cycles at all here, it sounds > > like it must be on a subgraph. How? > > Consider all top level "known referenced" symbols to be connected > by an edge. Connected to _what_ by an edge? > > For those following: A Hamilton cycle touch every node in the graph > > exactly once, and forms a cycle. > > More importantly, you can tell as DAG from a DCG. Symbols in a DCG, > where "known refrenced" forms an edge to the rest of the graph, means > that you have to reference increasingly fewer nodes as you go on. [...] > You sort these onto either the "used" or the "unknown" list. > > Then you look for a DCG using the "used" as a list, and traverse only > the "unknown" entries. If you find a cycle, you add the "unknown" > symbols in the cycle to the "used" list. Why is this easier/faster than the trivial algorithms I present above? And where does hamilton cycles (as opposed to just cycles in the graph) enter into this? I can sort of get a picture of using cycles to separate used/unused symbols, but I can't see any direct advantages to it, and I can't see Hamiltonian cycles in there at all. What am I missing here? (I'm interested due to sometimes needing this type of algorithms, and if something else is more effective than the techniques outlined above - well, then I want that :-) > Actually, you should talk to SEF about this; he's an old compiler > guru, and he worked on the Microsoft compiler for SCO. SEF, this is your call. Speak up. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 01:47:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03959 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 01:47:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03917 for ; Wed, 16 Sep 1998 01:47:05 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id KAA25941; Wed, 16 Sep 1998 10:54:06 +0200 (SAT) Received: by citadel via recvmail id 25939; Wed Sep 16 10:53:59 1998 From: Graham Wheeler Message-Id: <199809160852.KAA02623@cdsec.com> Subject: Re: Catching SIGSEGV To: bright@hotjobs.com (Alfred Perlstein) Date: Wed, 16 Sep 1998 10:52:44 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Sep 15, 98 12:43:05 pm X-Mailer: ELM [version 2.4 PL25-h4.1] 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 is no buffer in memory" it's the reading of the memory that's > causing the fault, someone in this thread brought up setjmp, that could > also work, another trick would be to change the value of 'ptr' to > something valid, (in the handler) then when the instruction is restarted > it will access valid memory and proceed as planned. The handler was already doing that (setting ptr to something valid). The original question was why does it still SEGV after ptr is set to a valid value? > > On Tue, 15 Sep 1998, Mikael Karpberg wrote: > > > My guess is that you would want to declare things like this: > > > volatile int nsegv = 0; > > > volatile int *ptr; > > > int zero = 0; > > > > > > Then the restarted "buf = *ptr;" line will not use a buffered value for ptr > > > but read it from memory. I think. > > that is TOTALLY wrong. no matter what happens the CPU will fault on the > fetch from the bad address. It isn't *totally* wrong, because the handler was setting ptr to a valid value. However, in practice it is insufficient bacuse the instruction that gets restarted is at the m/c level rather than the level of C statements, so the pointer will already be in a register, even though it is (or should be) volatile. So the only solution is to use setjmp/longjmp. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 02:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14904 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 02:58:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.10.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14898 for ; Wed, 16 Sep 1998 02:58:15 -0700 (PDT) (envelope-from kheuer@gwdu60.gwdg.de) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.9.0/8.9.0) with SMTP id LAA09487; Wed, 16 Sep 1998 11:57:34 +0200 (CEST) Date: Wed, 16 Sep 1998 11:57:34 +0200 (CEST) From: Konrad Heuer To: Martin Cracauer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Catching SIGSEGV In-Reply-To: <19980915163251.A7518@cons.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 Tue, 15 Sep 1998, Martin Cracauer wrote: > > May I ask my question here although it's not correlated to FreeBSD > > development? > > > > I write a program which shall run under FreeBSD and want to catch SIGSEGV > > to count these events. > > You have to longjmp out of your signal handler. This works. Thanks for all replies and the whole discussion! Konrad Heuer // Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH // Goettingen (GWDG), Am Fassberg, D-37077 Goettingen, Germany // // kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 05:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02496 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 05:25:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02475 for ; Wed, 16 Sep 1998 05:25:02 -0700 (PDT) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (frankenputer.aussie.org [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id WAA22191 for ; Wed, 16 Sep 1998 22:24:40 +1000 (EST) Message-Id: <199809161224.WAA22191@mail.aussie.org> From: "Hallam Oaks P/L list account" To: "freebsd-hackers@FreeBSD.ORG" Date: Wed, 16 Sep 1998 22:24:39 +1000 Reply-To: "Hallam Oaks P/L list account" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: 'struct isa_device' advice sought Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello; I'm implementing a PCI device interface for an ISDN card. The interface has the normal pci/ dir support code (this is already done so is not an issue). The main driver, however, is the i4b ISDN code, and this is where I'm running into trouble (despite appearances, this is not an ISDN-specific posting). The particular i4b code that I need to deal with assumes that the card it's working with is ISA, and as such makes liberal use of isa_device structs as parameters to functions, etc. To make this work with the PCI card, I'd have to either extensively modify this code (possible but not desirable), or init an isa_device structure and pretend that the PCI card is an ISA device (at least insofar as the i4b code is concerned). The changes necessary to the i4b code to make this work would not be so major - it would be aware of the PCI-ness of the card where it mattered, but otherwise not. My question is this : is the concept of a PCI card masquerading (in a limited sense) as an ISA one a legitimate approach ? Is it likely to cause problems ? I know it's a kludge but the alternative is also not particularly desirable. Any advice appreciated. -- Chris Hallam Oaks P/L To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 06:47:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13170 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 06:47:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13165 for ; Wed, 16 Sep 1998 06:47:55 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA06294; Wed, 16 Sep 1998 15:47:14 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA28293; Wed, 16 Sep 1998 15:47:12 +0200 (MET DST) Message-ID: <19980916154712.01723@follo.net> Date: Wed, 16 Sep 1998 15:47:12 +0200 From: Eivind Eklund To: Hallam Oaks P/L list account , "freebsd-hackers@FreeBSD.ORG" Subject: Re: 'struct isa_device' advice sought References: <199809161224.WAA22191@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809161224.WAA22191@mail.aussie.org>; from Hallam Oaks P/L list account on Wed, Sep 16, 1998 at 10:24:39PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 16, 1998 at 10:24:39PM +1000, Hallam Oaks P/L list account wrote: > My question is this : is the concept of a PCI card masquerading (in > a limited sense) as an ISA one a legitimate approach ? Is it likely > to cause problems ? I know it's a kludge but the alternative is > also not particularly desirable. The alternative is particularly desireable, and I hope to get time to fix it Real Soon Now. It is also necessary to be able to get a clean integration of the PnP code (which I have a hacky intergration of now). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 08:02:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24129 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 08:02:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24122 for ; Wed, 16 Sep 1998 08:02:22 -0700 (PDT) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (frankenputer.aussie.org [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id BAA22369 for ; Thu, 17 Sep 1998 01:02:00 +1000 (EST) Message-Id: <199809161502.BAA22369@mail.aussie.org> From: "Hallam Oaks P/L list account" To: "freebsd-hackers@FreeBSD.ORG" Date: Thu, 17 Sep 1998 01:01:39 +1000 Reply-To: "Hallam Oaks P/L list account" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: 'struct isa_device' advice sought Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Sep 1998 15:47:12 +0200, Eivind Eklund wrote: >On Wed, Sep 16, 1998 at 10:24:39PM +1000, Hallam Oaks P/L list account wrote: >> My question is this : is the concept of a PCI card masquerading (in >> a limited sense) as an ISA one a legitimate approach ? Is it likely >> to cause problems ? I know it's a kludge but the alternative is >> also not particularly desirable. > >The alternative is particularly desireable, and I hope to get time to >fix it Real Soon Now. It is also necessary to be able to get a clean >integration of the PnP code (which I have a hacky intergration of >now). ok, from an architecture point of view it's desirable, but recoding all of that section to suit PCI (in a consistent manner such that it integrates cleanly with the rest of i4b) is probably too much for me to bite off right now. I simply don't have a good enough grasp of the i4b package as a whole to do it intelligently :) Nevertheless ... I have a card I need to get going. What do you suggest ? Is the isa masquerading going to be more trouble than it's worth ? -- Chris Hallam Oaks P/L To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 10:00:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14187 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 10:00:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from icsnet.com (icsnet.com [204.194.104.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14161 for ; Wed, 16 Sep 1998 09:59:57 -0700 (PDT) (envelope-from jeffrey@meltzer.org) Received: HReceived: from xu90.villagenet.com (xu90 [205.136.35.9]) by icsnet.com (ics mailserver) with SMTP id NAA07862 for ; Wed, 16 Sep 1998 13:01:23 -0400 (EDT) Message-ID: <35FFEBD3.66EA91D4@meltzer.org> Received: from sparc.icsnet.com by xu90.villagenet.com via smtpd (for icsnet.com [204.194.104.2]) with SMTP; 16 Sep 1998 17:28:55 UT Date: Wed, 16 Sep 1998 12:48:19 -0400 From: Jeffrey Meltzer Organization: ICS Network Operations Center X-Mailer: Mozilla 4.5b1 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD on Libretto Content-Type: multipart/alternative; boundary="------------BE0EA0BC0689479632FC445F" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------BE0EA0BC0689479632FC445F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm having some problems setting up FreeBSD on the Libretto 50CT with a Linksys Ethercard Combo, which is supposedly supported by FreeBSD. I run through the PAO install disk, and when it gets to the nic part, it finds the card as a Linksys Ethercard Combo, but says it is unsupported, and then aborts. Anybody have any idea what to try next? -- Jeffrey Meltzer http://www.meltzer.org ICS Network Operations Center Support Manager Phone 516-218-0700/Fax 516-218-0769 620 Johnson Ave. Bohemia, NY 11716 --------------BE0EA0BC0689479632FC445F Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit I'm having some problems setting up FreeBSD on the Libretto 50CT with a
 Linksys Ethercard Combo, which is supposedly supported by FreeBSD.  I
 run through the PAO install disk, and when it gets to the nic part, it
 finds the card as a Linksys Ethercard Combo, but says it is unsupported,
 and then aborts. Anybody have any idea what to try next? 
-- 
Jeffrey Meltzer  http://www.meltzer.org
ICS Network Operations Center Support Manager
Phone 516-218-0700/Fax 516-218-0769
620 Johnson Ave. Bohemia, NY 11716
  --------------BE0EA0BC0689479632FC445F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 11:15:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01875 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 11:15:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ascetic.portal.ca (ascetic.portal.ca [206.87.139.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01854; Wed, 16 Sep 1998 11:14:59 -0700 (PDT) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by ascetic.portal.ca (8.8.8/8.8.5) with SMTP id LAA24429; Wed, 16 Sep 1998 11:13:46 -0700 (PDT) X-Authentication-Warning: ascetic.portal.ca: cjs owned process doing -bs Date: Wed, 16 Sep 1998 11:13:45 -0700 (PDT) From: Curt Sampson To: Alex Le Heux cc: Mike Smith , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 3Com 3c900B-FL? In-Reply-To: <3.0.5.32.19980916001225.00a0a420@crap.31337.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Sep 1998, Alex Le Heux wrote: > At 12:44 15-09-98 -0700, Mike Smith wrote: > >> Hi, > >> > >> Is anyone working on support for the 3c900B-FL card? > > > >Is this substantially different from the other members of the 3c900 > >family? > > > I have no clue. > > This is what the probe looks like: > > Sep 15 18:27:05 cthulu /kernel: pci0:8: vendor=0x10b7, > device=0x900a,class=network (ethernet) int a irq 10 [no driver assigned] Could be all you need to do is add the PCI ID to the appropriate table so that the standard 3c900 driver will recognise it as a card it knows about. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite mist, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 12:23:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15948 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 12:23:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15899 for ; Wed, 16 Sep 1998 12:23:08 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:w+VDV/LwvgyUzkIEKrXS8IkZnj5GRclI@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA00546; Wed, 16 Sep 1998 21:22:24 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809161922.VAA00546@gratis.grondar.za> To: Jeffrey Meltzer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: Your message of " Wed, 16 Sep 1998 12:48:19 -0400." <35FFEBD3.66EA91D4@meltzer.org> References: <35FFEBD3.66EA91D4@meltzer.org> Date: Wed, 16 Sep 1998 21:22:19 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey Meltzer wrote: > I'm having some problems setting up FreeBSD on the Libretto 50CT with a > Linksys Ethercard Combo, which is supposedly supported by FreeBSD. I > run through the PAO install disk, and when it gets to the nic part, it > finds the card as a Linksys Ethercard Combo, but says it is > unsupported, > and then aborts. Anybody have any idea what to try next? Sure. Look in /etc/pccard.conf to determine the format of each card's description. (I'm doing this from memory, so my terminology will suck). Each card is described by a paragraph that looks like card "" "" is the manufacturer, is a description. Look in /var/log/messages for the turd that pccardd put in there logging the failure, and use that to start a ^card "..." "..." paragraph in pccardd.conf. You'll need to use pccardc to "dumpcis" the card to find out which config to use. Get your paragraph right, HUP pccardd, and you're cool! With those clues and TFM, you should be OK. :-) 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 Wed Sep 16 12:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17862 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 12:31:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17663 for ; Wed, 16 Sep 1998 12:30:23 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id VAA05020; Wed, 16 Sep 1998 21:12:08 +0200 (CEST) Message-Id: <199809161912.VAA05020@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: "Hallam Oaks P/L list account" cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: 'struct isa_device' advice sought Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 16 Sep 1998 22:24:39 +1000." <199809161224.WAA22191@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Sep 1998 21:12:08 +0200 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Hallam Oaks P/L list account" writes: >My question is this : is the concept of a PCI card masquerading (in a limited >sense) as an ISA one a legitimate approach ? Is it likely to cause problems ? >I know it's a kludge but the alternative is also not particularly desirable. > >Any advice appreciated. > I think there's precedent for this for e.g. the ed driver. See i386/isa/if_ed.c and pci/if_ed_p.c. IIRC the isa driver calls the pci driver to check for a pci card. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 13:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25803 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 13:11:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25742 for ; Wed, 16 Sep 1998 13:11:11 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA07354; Wed, 16 Sep 1998 14:10:16 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA14062; Wed, 16 Sep 1998 14:10:15 -0600 Date: Wed, 16 Sep 1998 14:10:15 -0600 Message-Id: <199809162010.OAA14062@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mark Murray Cc: Jeffrey Meltzer , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: <199809161922.VAA00546@gratis.grondar.za> References: <35FFEBD3.66EA91D4@meltzer.org> <199809161922.VAA00546@gratis.grondar.za> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You'll need to use pccardc to "dumpcis" the card to find out which > config to use. > > Get your paragraph right, HUP pccardd, and you're cool! FYI, pccardd doesn't honor HUP. You must kill and restart it, but only after the cards are removed. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 13:18:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27350 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 13:18:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27187 for ; Wed, 16 Sep 1998 13:17:26 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:eHxLggLqy34iN3w60al/izGVMlOSxuUA@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id WAA01187; Wed, 16 Sep 1998 22:16:27 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809162016.WAA01187@gratis.grondar.za> To: Nate Williams cc: Jeffrey Meltzer , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: Your message of " Wed, 16 Sep 1998 14:10:15 CST." <199809162010.OAA14062@mt.sri.com> References: <35FFEBD3.66EA91D4@meltzer.org> <199809161922.VAA00546@gratis.grondar.za> <199809162010.OAA14062@mt.sri.com> Date: Wed, 16 Sep 1998 22:16:27 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > You'll need to use pccardc to "dumpcis" the card to find out which > > config to use. > > > > Get your paragraph right, HUP pccardd, and you're cool! > > FYI, pccardd doesn't honor HUP. You must kill and restart it, but only > after the cards are removed. :( This chap is using PAO. On PAO, pccardd honours HUP. :-) Care to upgrade CURRENT? :-) 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 Wed Sep 16 14:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07533 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 14:13:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay8.Austria.EU.net (relay8.Austria.EU.net [193.154.160.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07513 for ; Wed, 16 Sep 1998 14:12:53 -0700 (PDT) (envelope-from hfwirth@eunet.at) Received: from eunet.at (a064.static.Vienna.AT.EU.net [193.154.186.64]) by relay8.Austria.EU.net (8.9.1/8.9.1) with ESMTP id XAA11683; Wed, 16 Sep 1998 23:12:15 +0200 (MET DST) Message-ID: <3600297D.7F302BD1@eunet.at> Date: Wed, 16 Sep 1998 23:11:25 +0200 From: "Helmut F. Wirth" X-Mailer: Mozilla 4.06 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: CAM question: Worm devices ? 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 did not build yet a new kernel with CAM, but I noticed the absence of the device type worm. I am using a HP6020 Surestore with old SCSI and worm. How is worm supported in CAM ? Thank you Helmut -- Helmut F. Wirth Email: hfwirth@eunet.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 14:33:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11313 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 14:33:18 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11289 for ; Wed, 16 Sep 1998 14:33:09 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA13637; Wed, 16 Sep 1998 14:32:47 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd013615; Wed Sep 16 14:32:45 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA27690; Wed, 16 Sep 1998 14:32:41 -0700 (MST) From: Terry Lambert Message-Id: <199809162132.OAA27690@usr04.primenet.com> Subject: Re: Unused functions To: eivind@yes.no (Eivind Eklund) Date: Wed, 16 Sep 1998 21:32:41 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980916100311.62440@follo.net> from "Eivind Eklund" at Sep 16, 98 10:03:11 am X-Mailer: ELM [version 2.4 PL25] 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 > Hmmm. I can't see any reason why you would want to do a > Floyd-Warshall - that calculate the connectivity of the entire graph, > which is really producing a lot of data you don't need. Right. Which is why I wanted to do a Hamiltonian, not a Warshall (or a Floyd-Warshall). > Both algorithm 1 and 2 are o(N) and O(N) in the number of edges > connecting the set of used symbols. The only case you can avoid > examining all of these edges is if all symbols are included in the > final used set; then you could do a cutoff. I don't think it would be > worthwhile, though. Well, I think it would, at least if the theory were that you didn't link against things you planned to use, and you were only eliminating dead code in objects from an archive where you knew you were using at least one or more symbols (which is the case under consideration). > > Consider all top level "known referenced" symbols to be connected > > by an edge. > > Connected to _what_ by an edge? Each other. All used symbols are implicitly connected. This means than any other used symbol implies a cycle. > Why is this easier/faster than the trivial algorithms I present above? Because it's O(2) for the test, and only walks the portion of the tree related to the symbol being tested. 8-). > And where does hamilton cycles (as opposed to just cycles in the > graph) enter into this? Before you test a symbol, you "connect" it to all of the other used symbols. If you make it back to the root, then the symbol is used. > I can sort of get a picture of using cycles to separate used/unused > symbols, but I can't see any direct advantages to it, and I can't see > Hamiltonian cycles in there at all. > > What am I missing here? (I'm interested due to sometimes needing this > type of algorithms, and if something else is more effective than the > techniques outlined above - well, then I want that :-) You should look at the section of the Sedgewick C++ book on Hamiltonian cycles. This is really useful for runtime optimizations for things like a hierarchical SMP lock manager. You attach all nodes into the graph for the objects that are intended to be used, and calculate a Warshalls. Then, as you add leaves, you update using standard Floyd-Steinberg, so the Warshall's is always accurate. This allows you to insert leaf nodes in O(1) along the vector to the root of the graph. For a list of locks you want to test for deadlock, the list itself describes a vector. Using this vector as an arc through the existing Warshall-complete graph, you look for a Hamiltonian cycle. If the cycle exists, then you have a deadlock condition. This allows deadlock detection without having to do stack rewind and/or resource precommit (presuming that the tentative lock vector's elements are inserted using intention modes to prevent another tentative lock from coming back "safe"). This algorithm was actually the basis of the lock manager in the NetWare for UNIX server; it was capable of 20,000 transactions a second -- basically 2 orders of magnitude better than Tuxedo. 8-). You can further optimize this using the Dynix paper's finding on shared memory multiprocessors, to wit, you establish seperate intention zones for resource pools on a per processor basis for things like a free page pool so that you don't have to hold the top lock for page allocation, only for pool drain/refill. The same algorithm applies cleanly to the system process table and the system open file table; if you segment the table by the number of expecte reeentrancies, then you can establish an intention write for one processor that does not interfere with a traversal by another processor (intention read/read). The idea is to ensure maximal concurrancy. Of course the top levels of the per processor hierarchies are connected (via an edge through a system-wide lock), to allow deadlock avoidance. The actual system resources are in a pseudo-per-cpu ownership zone, so you lock a cpu zone and that zone, not a "big giant lock", in order to do the fill/drain. The computation of deadlock (transitive closure) is done, as in the symbol table example, by inferring Hamiltonian cycles along the two edges you know about (the real one and the pretend one made up of the resources you will require for a given idempotent operation). This is terrifically fun stuff to watch when it works. It's much better than Djikstra's soloution (the banker's algorithm), in that you wouldn't have to rebuild FreeBSD from the ground up to make it work... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 15:15:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21709 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 15:15:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21540 for ; Wed, 16 Sep 1998 15:14:29 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id AAA20351; Thu, 17 Sep 1998 00:14:01 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id AAA00474; Thu, 17 Sep 1998 00:12:28 +0200 (CEST) X-Face: " Date: Thu, 17 Sep 1998 00:12:28 +0200 From: Stefan Esser To: Hallam Oaks P/L list account , "freebsd-hackers@FreeBSD.ORG" Cc: Stefan Esser Subject: Re: 'struct isa_device' advice sought Mail-Followup-To: Hallam Oaks P/L list account , "freebsd-hackers@FreeBSD.ORG" References: <199809161224.WAA22191@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199809161224.WAA22191@mail.aussie.org>; from Hallam Oaks P/L list account on Wed, Sep 16, 1998 at 10:24:39PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-09-16 22:24 +1000, Hallam Oaks P/L list account wrote: > Hello; > > I'm implementing a PCI device interface for an ISDN card. The interface has > the normal pci/ dir support code (this is already done so is not an issue). > > The main driver, however, is the i4b ISDN code, and this is where I'm running > into trouble (despite appearances, this is not an ISDN-specific posting). > > The particular i4b code that I need to deal with assumes that the card it's > working with is ISA, and as such makes liberal use of isa_device structs as > parameters to functions, etc. I converted the "ed" (NE2000) and "lnc" (Lance) Ethernet drivers to support both ISA and PCI cards, more than 2 years ago. You may want to check out my patches from the CVS repository: /sys/i386/isa/if_ed.c (1.97 -> 1.99) /sys/i386/isa/if_lnc.c (1.23 -> 1.25). > To make this work with the PCI card, I'd have to either extensively modify > this code (possible but not desirable), or init an isa_device structure and > pretend that the PCI card is an ISA device (at least insofar as the i4b code > is concerned). The changes necessary to the i4b code to make this work would > not be so major - it would be aware of the PCI-ness of the card where it > mattered, but otherwise not. I replaced the array indexed by unit with softc structs addressed by pointers. The code became shorter and simpler in a lot of places ... > My question is this : is the concept of a PCI card masquerading (in a limited > sense) as an ISA one a legitimate approach ? Is it likely to cause problems ? > I know it's a kludge but the alternative is also not particularly desirable. It was very simple to just do away with the isa_device structure, except for the ISA probe/attach code. I'll be happy to support you (I'm a user of the i4b ISDN code myself, and my next system most probably will have a PCI ISDN card ;-), but may need up to one or two weeks to reply (sorry). Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 15:52:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00732 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 15:52:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00669; Wed, 16 Sep 1998 15:52:13 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id AAA17021; Thu, 17 Sep 1998 00:51:42 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Thu, 17 Sep 1998 00:51:41 +0200 (MET DST) Mime-Version: 1.0 To: Alex Le Heux Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: 3Com 3c900B-FL? References: <19980915183742.20167@funk.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling =?iso-8859-1?Q?Co=EFdan?= =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 17 Sep 1998 00:51:40 +0200 In-Reply-To: Alex Le Heux's message of "Tue, 15 Sep 1998 18:37:42 +0000" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA00683 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Le Heux writes: > Is anyone working on support for the 3c900B-FL card? Try adding the card's PCI device ID to the xl_devs array in src/sys/pci/if_xl.c and see if it works. If it does, please notify Bill Paul so he can commit the change to 3.0. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 16:53:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12909 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 16:53:54 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12753 for ; Wed, 16 Sep 1998 16:53:08 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA28633; Wed, 16 Sep 1998 17:52:42 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809162352.RAA28633@panzer.plutotech.com> Subject: Re: CAM question: Worm devices ? In-Reply-To: <3600297D.7F302BD1@eunet.at> from "Helmut F. Wirth" at "Sep 16, 98 11:11:25 pm" To: hfwirth@eunet.at (Helmut F. Wirth) Date: Wed, 16 Sep 1998 17:52:42 -0600 (MDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Helmut F. Wirth wrote... > Hello, > > I did not build yet a new kernel with CAM, but I noticed the absence of > the device type worm. > I am using a HP6020 Surestore with old SCSI and worm. How is worm > supported in CAM ? The "officially supported" way to write CDs under CAM is to use cdrecord. There is no WORM driver in CAM, and there probably won't be. (My plan is to eventually add CD-R, CD-RW, and perhaps DVD support to the CD driver.) There's a port here: ftp://ftp.kdm.org/pub/FreeBSD/cam/cdrecord-1.6-cam.980709.tar.gz There's also a newer binary for -current, located here: ftp://ftp.kdm.org/pub/FreeBSD/cam/test/cdrecord-1.6.1a3.test I'm working with Joerg Schilling on getting CAM support in the official cdrecord distribution. A new version should be out in a few days with CAM support included. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 17:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14700 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 17:02:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14573 for ; Wed, 16 Sep 1998 17:01:31 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id RAA05357; Wed, 16 Sep 1998 17:54:38 -0600 (MDT) Date: Wed, 16 Sep 1998 17:54:38 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809162354.RAA05357@narnia.plutotech.com> To: "Helmut F. Wirth" cc: hackers@FreeBSD.ORG Subject: Re: CAM question: Worm devices ? Newsgroups: pluto.freebsd.hackers In-Reply-To: <3600297D.7F302BD1@eunet.at> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3600297D.7F302BD1@eunet.at> you wrote: > Hello, > > I did not build yet a new kernel with CAM, but I noticed the absence of > the device type worm. > I am using a HP6020 Surestore with old SCSI and worm. How is worm > supported in CAM ? Via cdrecord. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 20:20:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25582 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 20:20:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from unix.tfs.net (as1-p218.tfs.net [139.146.210.218]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25472 for ; Wed, 16 Sep 1998 20:19:22 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id WAA19148 for freebsd-hackers@freebsd.org; Wed, 16 Sep 1998 22:18:51 -0500 (CDT) From: Jim Bryant Message-Id: <199809170318.WAA19148@unix.tfs.net> Subject: 1998-09-16 Briefing on Encryption (fwd) To: freebsd-hackers@FreeBSD.ORG Date: Wed, 16 Sep 1998 22:18:50 -0500 (CDT) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Mailer: ELM [version 2.4ME+ PL32 (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 this is interesting... -jim ----- Forwarded message from The White House ----- THE WHITE HOUSE Office of the Press Secretary ________________________________________________________________________ For Immediate Release September 16, 1998 PRESS BRIEFING BY THE VICE PRESIDENT, DEPUTY CHIEF OF STAFF JOHN PODESTA, PRINCIPAL ASSOCIATE DEPUTY ATTORNEY GENERAL ROBERT LITT, ASSISTANT DIRECTOR OF THE FBI CAROLYN MORRIS, UNDER SECRETARY OF COMMERCE WILLIAM REINSCH, DEPUTY SECRETARY OF DEFENSE JOHN HAMRE, AND DEPUTY NATIONAL SECURITY ADVISOR JIM STEINBERG The Briefing Room 11:57 A.M. EDT THE VICE PRESIDENT: Good morning. While my colleagues are coming in here, let me acknowledge them. John Podesta is going to take over the podium after I complete my statement, and he is joined by Bob Litt of the Justice Department, Bill Reinsch of the Commerce Department -- Under Secretary for the Export Administration -- and John Hamre, Deputy Secretary of Defense. I also want to acknowledge Carolyn Morris of the FBI; Barbara McNamara of the National Security Agency; John Gordon, Deputy Director of the CIA. And you all should know that this process, the results of -- the interim results of which I'm announcing here, is a process that has been run principally by John Podesta and Jim Steinberg, Deputy at the National Security Council. And I also want to thank Sally Katzen at the NEC and David Beier on my staff for the work that they and many others have done on this. Some of you who have followed this issue know that it is probably one of the single, most difficult and complex issues that you can possibly imagine. But we've made progress, and we're here this morning to announce an important new action that will protect our national security and our safety, and advance our economic interests and safeguard our basic rights and values in this new Information Age. The Information Age has brought us the Internet, an inter-connected global economy and the promise of connecting us all to the same vast world of knowledge. But with that exciting promise comes new challenges. We must make sure that in the Information Age you get information about the rest of the world and not the other way around. We must ensure that new technology does not mean new and sophisticated criminal and terrorist activity which leaves law enforcement outmatched -- we can't allow that to happen. And we must ensure that the sensitive financial and business transactions that now cruise along the information superhighway are 100 percent safe in cyberspace. Balancing these needs is no simple task, to say the least. That is why, in taking the next step toward meeting these complex goals, we worked very closely with members of Congress from both parties, House and Senate; with industry; with our law enforcement community and with our national security community. And as we move forward we want to keep working closely with all who share a stake in this issue -- especially law enforcement -- to constantly assess and reassess the effectiveness of our actions in this fast changing medium. Today I'm pleased to announce a new federal policy for the encryption and protection of electronic communication, a policy that dramatically increases privacy and security for families and businesses without endangering out national security. Beginning today, American companies will be able to use encryption programs of unlimited strength when communicating between most countries. Health, medical, and insurance companies will be able to use far stronger electronic protection for personal records and information. Law enforcement will still have access to criminally-related information under strict and appropriate legal procedures. And we will maintain our full ability to fight terrorism and monitor terrorist activity that poses a grave danger to American citizens. With this new announcement, we will protect the privacy of average Americans, because privacy is a basic value in the Information Age, indeed in any age. We will give industry the full protection that it needs to enable electronic commerce to grow and to thrive. And we will give law enforcement the ability to fight 21st century crimes with 21st century technology, so our families and businesses are safe, but on-line outlaws are not safe. In just a moment you will hear more of the details of this new policy, but I want to conclude by saying that this policy does reflect one of the greatest challenges of these new times. And to state it broadly, it's a challenge of how we can harness powerful new technology while protecting our oldest and most cherished values, such as privacy and safety. I'm grateful to those who have worked so hard to reach this balance. And with today's announcement I believe that all families and businesses have reason to feel safer, more secure and more confident as we approach the 21st century. And now I'd like to turn things over to White House Deputy Chief of Staff John Podesta. Q Mr. Vice President, before you go, can you tell us what you say to Democratic lawmakers who say the President ought to resign? THE VICE PRESIDENT: I disagree. Q How about the release of that tape? What do you think -- THE VICE PRESIDENT: The President is going to have a press conference shortly and I'm sure that you will not miss the opportunity at this national security press conference with the leader of a foreign country to raise all these questions. Q What about the videotape, should it be released? Q It was staged by the White House -- you know that, don't you? MR. PODESTA: Guess what? I'm here to talk about encryption. Okay. I can see the front row leaving here. (Laughter.) As the Vice President noted, Jim Steinberg and I have co-chaired our process in this matter. I volunteered for that duty because of my well-known fascination with The X Files, which most of you know about. As you know, this is an important and challenging issue that affects many of our interests in our society. And over the past year we've promoted a balanced approach to the issue, working with all segments of our government and working with industry to find a policy that promotes electronic commerce, preserves privacy, protects national security and law enforcement interests, and permits U.S. industry to secure global markets. Recognizing the importance of moving this issue forward, last March the Vice President asked us to intensify our dialogue with U.S. industry, to bring industry's technical expertise to bear on this issue with the hope of finding more innovative ways that we might assist law enforcement. We appreciate the efforts of Congress, the law enforcement community and particularly the industry groups. I would note the Computer Systems Policy Project and the Americans for Computer Privacy, who have been in an intensive dialogue with us over the past many months to foster an environment that has allowed us to come up with a policy which we believe has balanced the elements that are necessary in this regard. I think all the stakeholders in this process, on our side, as well as on private industry's side, now have a greater appreciation of the issues and intend to continue the dialogue, which I think we're most pleased by. Again, I think some of the people here from industry will be available at the stakeout later to take some comment. Based on the ideas discussed among the various stakeholders, today we're proposing an update to our policies that we've announced in the past. I'm going to serve kind of as M.C. We're going to start off with Bob Litt from the Justice Department and Carol Morris, who I asked to join us, from the FBI, to talk about the law enforcement-FBI concerns. Then we're going to turn to Bill Reinsch from the Commerce Department to talk about export control and electronic commerce. And finally you'll hear from Dr. Hamre from the Defense Department. I might ask Jim also to join us up here. Before I give up the floor to Bob and Carol, though, I want to stress that encryption policy is an ongoing process. It's one of adaptation; it's an evolutionary process. We intend to continue the dialogue, and over the course of the next year, determine what further updates are necessary as we work with industry to try to, again, come up with a policy that balances national security, law enforcement, and the real needs for privacy and security in electronic commerce. Thank you. Let me turn it over to Bob. MR. LITT: Thank you, John. Good afternoon. The Justice Department and the FBI and law enforcement in general is supportive, very supportive of today's announcement on the updating of our export controls on encryption products, particularly with respect to those products that allow law enforcement to obtain lawful access to the plain text of encrypted information. We have been very encouraged over the last few months by industry's efforts to work with us to develop and market strong encryption products that provide law-abiding citizens with the ability to protect the privacy of their communications and their electronically-stored data, while at the same time maintaining law enforcement's ability to ensure public safety when these products, when they become commercially available, are used in furtherance of serious criminal activity. Our goal is through whatever means to ensure that when we have the lawful authority to take steps to protect public safety, we have the ability to do so. And we have been working cooperatively with industry for many months to develop approaches that will deal with that. Carolyn Morris will now talk a little bit about the technical support center that is being proposed. MS. MORRIS: Thank you very much, Bob. Good afternoon, ladies and gentlemen. We in federal, state, and local law enforcement, are pleased with the administration's support to establish a technical support center. This center will provide federal, state, and local law enforcement with the resources and the technical capabilities we need to fulfill our investigative responsibilities. In light of strong, commercially available encryption products that are being proliferated within the United States, and when such products are used in the furtherance of serious criminal activity, this center becomes very, very critical to solving the encryption issues that we need to make cases. As a matter of fact, the FBI has already begun planning activities of this critical technical support center in anticipation of the availability of funds. The United States federal, local and state law enforcement community looks forward to a cooperative partnership with American industry, the Congress and the administration to ensure that this technical support center becomes a reality in the near future. With this center the American people can be assured that federal, state, and local law enforcement has the necessary resources and tools we need to fulfill our public safety mission. Thank you very much. UNDER SECRETARY REINSCH: With respect to export controls, the administration is updating its policy in three areas: Our existing policy and some revisions there, an expansion with respect to certain sectors, and an expansion with respect to so-called recoverable products. And let me address each of these separately. In keeping with the administration's reinvention initiatives, I'm going to try to do it in plain language -- or plain English, So that those of you that speak the vocabulary of encryption may find it to elementary, but we can go back and do it again in another language, if you want, later on in questions. With respect to our existing policy, we have for two years ending this December, permitted the export of 56-bit products after an initial one-time review without further review by the government. What we're announcing today is the maintenance of that window permanently. And so 56-bit products will be freed from export controls after a one-time review, in perpetuity, not ending at the end of this year. We are, however, removing the requirement for key recovery plans or key recovery commitments to be provided in return for that change, which was the initial condition that we extracted. In addition, we are continuing to permit the export of key recovery products -- products that contain those features -- without restraint worldwide. We are, however, going to simplify significantly our regulations that relate to those exports. In particular, we're going to eliminate the need for six-month progress reports for the plans that have been submitted, and we're going to eliminate the requirement for any prior reporting of key recovery agent information. For those of you that follow the regulations in detail, that means we're going to eliminate Supplement Five of our regulations on these matters. Now, with respect to sectors, we're making some new innovations in four areas. Some of you may be familiar with the fact that some time ago we announced expanded treatment of encryption products for export to banks and financial institutions. And what we did at that time, briefly, was to permit the export of encryption products of any length, any bit length, with or without key recovery features to banks and financial institutions in a list of 45 countries. What we are announcing today is, first, that we are adding insurance companies to the definition of financial institutions, so insurance companies will be treated the same way under this policy as banks and other financial institutions are now. In addition, we are providing the same kind of treatment for exports of these encryption products to the health and medical sector operating in the same set of countries. We are excluding from that biochemical and pharmaceutical producers. But the rest of the health and medical sector will be the beneficiary of the same kind of treatment. In addition, we are providing also this expanded treatment for that country group to on-line merchants that are operating in those countries. That means that for products that are like client-server applications, like SSL, will be able to be exported to those destinations. All these things will take place under what we call license exception, which means after initial one-time review to determine whether or not your product is, in fact, what you say it is, they can then go without any further review or intervention by the government to those locations. In addition, there is always the option in the export control system of coming in with an application to export these kinds of products to other destinations beyond the ones that I'm talking about right now, and those will be reviewed one by one on their merits. Finally, with respect to what we have come to refer to as a class of so-called recovery capable or recoverable products, and these are the products that, among others, include what has become known as the doorbell products, which are products that, among other things, will deal with the development of local area or wide area networks and the transmission of e-mail and other data over networks -- we are going to permit the export of those products under a presumption of approval and an export licensing arrangement to a list of 42 countries. And within those countries we are going to permit that export to commercial firms only within those countries. And both in that case and in the case of the on-line merchants that I referred to a few minutes ago, we are going to exclude manufacturers or distributors of munitions items, I think for obvious reasons. We can go into further details later, if you would like. I think for those of you that are interested in the nitty-gritty of all this stuff, BXA intends to post all the details, including the country lists, on its website and we should have that up later today. Thank you. DEPUTY SECRETARY HAMRE: Good morning. I'm here to speak on behalf of the national security community. I'm joined today by my enormously capable counterparts and colleagues, Deputy Director Barbara McNamara for the National Security Agency; and Deputy Director John Gordon from the Central Intelligence Agency. The national security establishment strongly supports this step forward. We think this is a very important advance in a crucial area for our security in the future. We in DOD had four goals when we entered these discussions. First was to strengthen our ability to do electronic commerce. We're the largest company in the world. Every month we write about 10 million paychecks. We write about 800,000 travel vouchers. One of our finance centers disburses $45 million an hour. We are a major, major force in business. And for that reason, we can't be efficient unless we can become fully electronic, and electronic commerce is essential for us. And this is an enormous step forward. Second, we must have strong encryption and a security structure for that in order to protect ourselves in cyberspace. Many of you know that we have experienced a number of cyber attacks during the last year. This will undoubtedly increase in the future. We need to have strong encryption because we're operating over public networks; 95 percent of all of our communications now go over public infrastructure -- public telephone lines, telephone switches, computer systems, et cetera. To protect ourselves in that public environment, we must have encryption and we must have a key recovery system for ourselves. The third goal that we had was to help protect America's infrastructure. One of the emerging national security challenges of the next decade is to protect this country, the homeland defense of this country, against attack. We must have strong encryption in order to do that, because most of this infrastructure now is being managed through distributed computer-based management systems, and this is an important step forward. Finally, it is very important that the Department of Defense and our colleagues in the national security establishment have the ability to prosecute our national security interests overseas. Terrorists and rogue nations are increasingly using these tools to communicate with each other and to lay their plans. We must have the ability to deal with that. And so this policy, it's a balanced and structured approach to be able to deal with all four of those problems. UNDER SECRETARY REINSCH: I apologize -- in listing my changes, I neglected one very important item that I want to go back to, and that is, in the sector area we are also announcing today the ability to export strong encryption of any bit length, with or without key recovery features, to subsidiaries of U.S. companies to all destinations in the world with the exception of the seven terrorist nations. MR. PODESTA: Okay, I think we're happy to take your questions now. If you could identify whom you're addressing, because there is a variety of expertise. And I would like to introduce one other person, Charlotte Knepper from the NSC staff, who has been instrumental in pulling this all together. Q John, this is a question for you. In October '96 and other White House statements on encryption, there has usually been a line also addressing the domestic side, saying that all Americans remain free to use any strength encryption. I didn't notice anything like that in today's announcement. Are there any conditions under which the White House would back domestic restrictions on encryption? MR. PODESTA: We haven't changed our policy, and the previous statements are certainly intact. We have made a number of policy statements in the past, since this administration came into office, and I think that you should view this as a step forward, building on the policies that we have put before the American public in the past. Q John, could I ask you one question about an un-encrypted matter? MR. PODESTA: Maybe. (Laughter.) Q Democrats on the Hill are now saying, and John Kerry is saying that the President's actions absolutely call for some sort of punishment. What are Democrats telling you about what they feel must be done at this point? MR. PODESTA: Well, I think I'm not going to stand here and take a lot of questions, but I'm going to give special dispensation, as a Catholic, today -- which is I'm going to return your phone calls later. But in deference to the people up here I think we'll handle it that way. But in specific response, I'll take one, which is that I think that we had a number of productive meetings with Democrats on both sides of the Hill yesterday. They view the President as a person who has led on the issues that are important to them, and I think what they want to do is get back to having him speak out and be a leader on the issues of education and the health care bill of rights, on saving Social Security. And I think they pointed at that and wanted to work with us on that. I think with regard to the question that you posed with regard to Senator Kerry, I think that's a matter that they are debating amongst themselves more than they are debating with the White House. I think it's probably presumptuous for us at this point to offer them assistance or guidance. I mean, the President has said that what he has done was wrong; he's apologized for it; he's asked for forgiveness. He is moving forward. And I think that this debate is going on, on Capitol Hill, but it's largely going on amongst members themselves. Q We haven't heard many of them say they want to get back to the work at hand. MR. STEINBERG: You heard John, and I'm going to leave it there. Let me just add a word in response, in connection with the domestic controls issue. I think one of the lessons that we've learned from this exercise is that -- actually, two lessons -- one, that trying to balance the various interests and equities in this is much less of a zero sum gain than I think some began to look at the question. That is, you heard from Dr. Hamre and others that many of the interests involved have common interests in making sure that we have secure and effective means of dealing with communications and stored data. And so we found, by looking in a very pragmatic way, that there were ways to solve these problems without very, kind of, broad-based solutions. In particular, I think the idea that there's no one-size-fits-all answer to the problems of meeting the various needs informs the decisions that we reached -- that there are a variety of different techniques that respond to the different aspects of the industry, the different aspects of the technology. I think that's what made the progress possible today, is that industry, agencies and Congress sat down together, pulled the problem apart, began to look at its different components and began to fashion very pragmatic solutions. And so I think we came to this discussion with a spirit of not looking for a kind of single or simple solution to the problem but, rather, how do you tackle and meet the various needs. And I think that's what led to this resolve. Q Could you talk a little more about the on-line merchants part of it? I mean, what do you have to do to qualify as an on-line merchant? Do you have to register or can anybody sort of set themselves up in business? UNDER SECRETARY REINSCH: I think the simplest way to respond to that right now is we'll have a definition in the reg that will be very clear as to what the criteria are for qualification. And those definitions have already been dealt with and agreed to, so we should have them up on the web site this afternoon. Q A question for Bill Reinsch. How do you handle, then, 128-bit, to which the Department has given export -- or has allowed to be exported after going through this review? Will 128 or things above 56-bit, will they require a license or will they still have to go through plans -- UNDER SECRETARY REINSCH: Well, with respect to the subsidiaries, the health sector, the banks, the financial institutions, the insurance companies, the on-line merchants, and the recoverable products as in the universe defined -- no. In the case of all but the recoverable products, they will all go on license exception, which means one-time review and then out the door. With respect to recoverable products, they will come in and go out pursuant to an export licensing arrangement, where we'll have to do a little tailoring depending upon the nature of the product. But there is a presumption of approval for the 42 countries that I indicated. And that's without reference to bit length -- 128 or more is all covered by that. Now, if you want to export an 128-bit product that is beyond any of those universes, then you would have to come in for an individual license application. Q A question for Mr. Litt. With regard to the technical support center, when do you expect that to be in operation? MR. LITT: I don't think we have a specific timetable yet. Obviously, it would be helpful for us to have it up and operational as soon as possible, but there are planning and budgetary issues that have to be dealt with. Q This is probably a question for Under Secretary Reinsch. The export exceptions now are essentially going to U.S. subsidiaries -- foreign subsidiaries of U.S. companies. I was wondering, could you be a little more specific -- what size company, what kind of company will be allowed to export powerful crypto to its foreign subsidiaries? UNDER SECRETARY REINSCH: That doesn't make any difference. The universe is determined by the end user, not by the nature of the American company. But it is not -- while part of this relates to subsidiaries of U.S. companies, that is correct, we also intend, on a case-by-case basis, to provide for favorable treatment for export of the same kind of thing to strategic partners of U.S. companies -- those foreign companies that are engaged in a closer, say, joint venture, that kind of relationship. Well, I think that's it. Q What about foreign companies that have U.S. subsidiaries, like Seaman's or -- or Chrysler -- can they get this encryption? UNDER SECRETARY REINSCH: Well, keep in mind, there are multiple universes here. If you're talking about the financial institutions, the banks and the insurance companies, those aren't necessarily American financial institutions. That's for export to any financial institution, and for their use in any of their branches, aside from the terrorist countries. This is true for the health sector; this is true for on-line merchants as well. Those are not restricted to U.S. companies. Obviously, if we're going to have a requirement for U.S. subs, it relates to U.S. subs, and wouldn't affect the examples you've described. Now, with respect to recoverable products, which actually is one of the areas where the companies you mentioned would probably be looking because they'd be looking to build a network among their various offices, affiliates of subsidiaries, dealers if necessary, worldwide, the recoverable provisions that I described could be exported to those companies within the territorial universe I described -- the 42 countries. Thank you very much. END 12:25 P.M. EDT ----- End of forwarded message from The White House ----- -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 21:01:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03679 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 21:01:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA03475 for ; Wed, 16 Sep 1998 21:00:36 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zJVEe-0003JS-00; Wed, 16 Sep 1998 22:00:00 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id WAA13166; Wed, 16 Sep 1998 22:01:07 -0600 (MDT) Message-Id: <199809170401.WAA13166@harmony.village.org> To: Jeffrey Meltzer Subject: Re: FreeBSD on Libretto Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 16 Sep 1998 12:48:19 EDT." <35FFEBD3.66EA91D4@meltzer.org> References: <35FFEBD3.66EA91D4@meltzer.org> Date: Wed, 16 Sep 1998 22:01:06 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35FFEBD3.66EA91D4@meltzer.org> Jeffrey Meltzer writes: : I'm having some problems setting up FreeBSD on the Libretto 50CT : with a Linksys Ethercard Combo, which is supposedly supported by : FreeBSD. I run through the PAO install disk, and when it gets to : the nic part, it finds the card as a Linksys Ethercard Combo, but : says it is unsupported, and then aborts. Anybody have any idea what : to try next? I had problems with the Linksys ethernet card that I purchased. The combo part may give you fits, as they generally aren't supported. The problem that I ran into with the linksys ethernet card (not the combo one) was that it relied on the 12V line, which the libretto doesn't have (at least that's what tech support told me). I wound up with a 3c589d, and haven't had many problems with it, certainly not enough to complain. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 22:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16081 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 22:17:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from icsnet.com (icsnet.com [204.194.104.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16073 for ; Wed, 16 Sep 1998 22:17:02 -0700 (PDT) (envelope-from meltzer@icsnet.com) Received: HReceived: from xu90.villagenet.com (xu90 [205.136.35.9]) by icsnet.com (ics mailserver) with SMTP id BAA20886; Thu, 17 Sep 1998 01:18:11 -0400 (EDT) Received: from sparc.icsnet.com by xu90.villagenet.com via smtpd (for icsnet.com [204.194.104.2]) with SMTP; 17 Sep 1998 05:45:44 UT Date: Thu, 17 Sep 1998 01:05:09 -0400 (EDT) From: Jeffrey Meltzer X-Sender: meltzer@sparc To: Mark Murray cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: <199809162016.WAA01187@gratis.grondar.za> Message-ID: x-company: Intelligent Computer Solutions x-website: http://www.hostname.net x-phone: 516-218-0700 x-comment: the sender of this message thinks microsoft products are garbage. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id WAA16074 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok. I've given up on the Network install. I sacrificed 150MB of my hard drive, and downloaded the OS. setup a 150MB dos partition, and via zipdisk dumped freebsd in there. Booted up with the freebsd boot disk, but during the setup it craps out at: DEBUG: Generating /etc/fstab file DEBUG: DOS Partition /dev/wd0s1 mounted I have the freebsd stuff installed in c:\freebsd\bin c:\freebsd\src etc, etc. any ideas? i am DETERMINED to make this work! Jeffrey Meltzer http://www.meltzer.org ICS Network Operations Center Support Manager Phone 516-218-0700/Fax 516-218-0769 620 Johnson Ave. Bohemia, NY 11716 On Wed, 16 Sep 1998, Mark Murray wrote: :>Nate Williams wrote: :>> > You'll need to use pccardc to "dumpcis" the card to find out which :>> > config to use. :>> > :>> > Get your paragraph right, HUP pccardd, and you're cool! :>> :>> FYI, pccardd doesn't honor HUP. You must kill and restart it, but only :>> after the cards are removed. :( :> :>This chap is using PAO. On PAO, pccardd honours HUP. :-) :> :>Care to upgrade CURRENT? :-) :> :>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 :> Received: from eagle1.villagenet.com ([109.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 22:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20875 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 22:44:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20746 for ; Wed, 16 Sep 1998 22:44:05 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:rMDxVvc/GauHfy9ihEAMXrNUWh0driRC@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id HAA03300; Thu, 17 Sep 1998 07:43:09 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809170543.HAA03300@gratis.grondar.za> To: Jeffrey Meltzer cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: Your message of " Thu, 17 Sep 1998 01:05:09 -0400." References: Date: Thu, 17 Sep 1998 07:43:08 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey Meltzer wrote: > Ok. I've given up on the Network install. I sacrificed 150MB of my hard > drive, and downloaded the OS. setup a 150MB dos partition, and via zipdisk > dumped freebsd in there. Booted up with the freebsd boot disk, but during > the setup it craps out at: > > DEBUG: Generating /etc/fstab file > DEBUG: DOS Partition /dev/wd0s1 mounted > > I have the freebsd stuff installed in c:\freebsd\bin c:\freebsd\src etc, > etc. > > any ideas? What makes you think that is a "crap out"? Things look fine to me... 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 Wed Sep 16 23:02:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24514 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 23:02:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA24410 for ; Wed, 16 Sep 1998 23:02:06 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA24645; Thu, 17 Sep 1998 06:10:56 +0200 From: Luigi Rizzo Message-Id: <199809170410.GAA24645@labinfo.iet.unipi.it> Subject: Re: FreeBSD on Libretto To: meltzer@icsnet.com (Jeffrey Meltzer) Date: Thu, 17 Sep 1998 06:10:56 +0200 (MET DST) Cc: mark@grondar.za, nate@mt.sri.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jeffrey Meltzer" at Sep 17, 98 01:04:50 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok. I've given up on the Network install. I sacrificed 150MB of my hard i installed mine using ppp and the serial port from a 2.2.6 server. The only issue was probably setting clocal on the tty port on the server side. Other than that, the install went pretty smooth -- i started it in the morning, and came back for lunch time and eveything was done. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 16 23:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27982 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 23:21:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27967 for ; Wed, 16 Sep 1998 23:21:44 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id IAA05326; Thu, 17 Sep 1998 08:21:10 +0200 (CEST) (envelope-from sos) Message-Id: <199809170621.IAA05326@sos.freebsd.dk> Subject: Re: CAM question: Worm devices ? In-Reply-To: <199809162352.RAA28633@panzer.plutotech.com> from "Kenneth D. Merry" at "Sep 16, 98 05:52:42 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Thu, 17 Sep 1998 08:21:10 +0200 (CEST) Cc: hfwirth@eunet.at, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Kenneth D. Merry who wrote: > > The "officially supported" way to write CDs under CAM is to use cdrecord. > There is no WORM driver in CAM, and there probably won't be. (My plan is > to eventually add CD-R, CD-RW, and perhaps DVD support to the CD driver.) You can see how thats done in the atapi-cd.c driver. This will only work for MMC compliant drives (luckily all ATAPI ones are), the old HP's etc wont work without drive specific code, ick. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 00:22:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09916 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 00:22:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gibralter.net (pollux.gibralter.net [208.220.166.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA09898 for ; Thu, 17 Sep 1998 00:22:30 -0700 (PDT) (envelope-from distributor@phonecheck.net) From: distributor@phonecheck.net Received: from jake.gibralter.net by gibralter.net (SMI-8.6/SMI-SVR4) id DAA04776; Thu, 17 Sep 1998 03:15:45 -0400 Date: Thu, 17 Sep 1998 03:15:45 -0400 To: freebsd-hackers@FreeBSD.ORG Subject: FREE Classifieds Up Date Organization: Internet Resource Center Message-Id: <8QB46EB9.00S8V6S3@phonecheck.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I discovered your business on the internet, and thought you might br interested in our website located at http://rodweb.localweb.com/classads/sites/web/htm You can place FREE CLASSIFIEDS that will be seen all over the worldwide web. Take a look at the counter and see why you want to place your ad here. Go there now and place your ad so you can see your business increase. Thank you Jake If you would like to be removed from future mailing simply respond with "REMOVE" in the subject line. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 00:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16043 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 00:52:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.27.216.204.in-addr.arpa [204.216.27.226] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15901 for ; Thu, 17 Sep 1998 00:51:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA25287 for ; Thu, 17 Sep 1998 00:52:00 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: hackers@FreeBSD.ORG Subject: Promotional CDs and evil customs agencies. Date: Thu, 17 Sep 1998 00:52:00 -0700 Message-ID: <25283.906018720@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I know that this is typically -chat material, but I'm not going to reach the people who are actually involved by sending this to -chat ] I just thought I'd let folks know that I've reached a hard, but irrevokable, decision with regard to sending promotional CDs overseas: I'm not going to do it anymore. This decision doesn't come easily since I know that there are a lot people overseas who have done some very good work with promotional CDs in the past, but these people also need to understand that almost every single batch of CDs I've sent overseas has come at considerable personal cost. I've probably had over 500 long and tortured conversations regarding CDs stuck in customs, CDs which got billed to the wrong people and CDs which just plain got destroyed on the dock. I just can't afford to spend that kind of time on this sort of thing. Not only do european and asian customs deparments make the process of sending "freebies" a total nightmare (no matter how we declare them, and we've tried just about everything from free to cost-of-materials to full-value on the declaration forms), but the shipping is very expensive, even by boat. Most people don't know that we spent over $10,000 shipping the 2.2.6 CDs to various people overseas, and if I ever do something like that again I'll be taken out to Walnut Creek CDROM's parking lot and shot in the back of the head by the financial controller. I won't even get a fair trial first. So anyway, please don't send me lots of emails going "gosh, don't do that, we can pay shipping!" or "I have a brother in customs who can smuggle them out, just tie a red ribbon around the parcel and mark it ``attention Sigfried''" - I really have thought about this and it really is just too much trouble for us. My mind is made up. No more non-U.S. freebies. The shipping department, already overloaded with work as it is, also refuses to send special letters or otherwise attempt to mediate when stuff gets stuck at customs if the whole deal is only going to cost money (e.g. they'll do this if you're a paying customer, but it's too much to expect for free), so it's really just not practical to try and do this anymore. If you know of someone in the U.S. who is willing to deal with all these issues for you or otherwise provide "trans-shipment" outside the U.S., then that's obviously something else entirely and I'm perfectly willing to do that. Sending CDs within the U.S. is not a problem. What this all says to me is that maybe it's time for some company like S.U.S.E. to pick up the job of making and selling FreeBSD CDs in europe since Walnut Creek CDROM isn't doing much of that anymore in any case. Don't get me wrong - I'd love to see us have a bigger european presence, along with a big inventory of FreeBSD CDs over in Europe which could be sold and/or given away for promotional purposes, but I also don't see that happening anytime soon. We tried to do that about 3 years ago and the whole idea just sort of fizzled out, as much as I would have loved to have seen "Walnut Creek CDROM, Europe." It's not just enough to have a distributor there, you need to have the CDs *made* in europe in order to avoid customs problems. My sincere apologies to the various non-U.S. folks who used to get promotional CDs from me, but I think you also know even better than I do just how much trouble customs can cause and can pretty much relate to my predicament. If it were just one or two incidents a year, I'd deal with it, but it's a heck of a lot more work than that and if I so much as see one more customs declaration form, I'm going to scream! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 01:10:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19815 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 01:10:39 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19802 for ; Thu, 17 Sep 1998 01:10:33 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA14474; Thu, 17 Sep 1998 09:09:43 +0100 (BST) Date: Thu, 17 Sep 1998 09:09:43 +0100 (BST) From: Doug Rabson To: "Kenneth D. Merry" cc: "Helmut F. Wirth" , hackers@FreeBSD.ORG Subject: Re: CAM question: Worm devices ? In-Reply-To: <199809162352.RAA28633@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Sep 1998, Kenneth D. Merry wrote: > Helmut F. Wirth wrote... > > Hello, > > > > I did not build yet a new kernel with CAM, but I noticed the absence of > > the device type worm. > > I am using a HP6020 Surestore with old SCSI and worm. How is worm > > supported in CAM ? > > The "officially supported" way to write CDs under CAM is to use cdrecord. > There is no WORM driver in CAM, and there probably won't be. (My plan is > to eventually add CD-R, CD-RW, and perhaps DVD support to the CD driver.) That would be good. I have been daydreaming about writing a UDF filesystem for CD-R, CD-RW and DVD. Well I started reading the spec anyway... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 03:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15572 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 03:51:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15537 for ; Thu, 17 Sep 1998 03:51:12 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id LAA04957; Thu, 17 Sep 1998 11:50:49 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 17 Sep 1998 11:48:08 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19980809164437.C11095@freebie.lemis.com> References: <199808090649.XAA23702@implode.root.com>; from David Greenman on Sat, Aug 08, 1998 at 11:49:51PM -0700 <19980809160829.A11214@freebie.lemis.com> <199808090649.XAA23702@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 17 Sep 1998 11:48:06 +0000 To: Greg Lehey From: Bob Bishop Subject: Re: AMD-specific kernel code (was: How long a wait?) Cc: FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:44 pm +0930 9/8/98, Greg Lehey wrote: >[...] >Still, that's not proven. I've put the patches on >ftp://ftp.lemis.com/pub/AMD-write-allocate-patch. They relate to >today's -CURRENT. How about some other people grabbing them and >trying them out? I've been running a pretty mixed workload with and without these since you posted. The effect seems to be marginal (less than 1%): compute-bound jobs win, others lose. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 05:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27885 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 05:29:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27875 for ; Thu, 17 Sep 1998 05:29:05 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA05130; Thu, 17 Sep 1998 14:28:43 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA02316; Thu, 17 Sep 1998 14:28:42 +0200 (MET DST) Message-ID: <19980917142841.01218@follo.net> Date: Thu, 17 Sep 1998 14:28:41 +0200 From: Eivind Eklund To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Unused functions References: <19980916100311.62440@follo.net> <199809162132.OAA27690@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809162132.OAA27690@usr04.primenet.com>; from Terry Lambert on Wed, Sep 16, 1998 at 09:32:41PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I'm keeping a lot of context to make this easy to read; I also note that I didn't move this to -chat when I thought I did, but we're getting into some locking-related discussions that are again related to -hackers, so I keep it here now] On Wed, Sep 16, 1998 at 09:32:41PM +0000, Terry Lambert wrote: > > Both algorithm 1 and 2 are o(N) and O(N) in the number of edges > > connecting the set of used symbols. The only case you can avoid > > examining all of these edges is if all symbols are included in the > > final used set; then you could do a cutoff. I don't think it would be > > worthwhile, though. > > Well, I think it would, at least if the theory were that you didn't > link against things you planned to use, and you were only eliminating > dead code in objects from an archive where you knew you were using > at least one or more symbols (which is the case under consideration). Well, it's two lines extra code to check if you're all out of symbols (ie, the list containing symbols of "unknown" status is empty). > > Why is this easier/faster than the trivial algorithms I present above? > > Because it's O(2) for the test, and only walks the portion of the > tree related to the symbol being tested. 8-). In this case: 2 what's? And how is walking "the portion of the tree related symbol being tested" compatible with O(2)? Finding a Hamiltonian cycle is a classic NP-complete problem, ie, only solvable in exponential time. I'm very curious how this improve on my simple linear time. (And unfortunately I still don't get it any more than I did intially :-( [On what I'm missing wrt using Hamiltonian cycles for this] > You should look at the section of the Sedgewick C++ book on > Hamiltonian cycles. I'll go out and buy this on monday, probably. I don't think I'll have time before. (That it is missing is really is a gaping hole in my bookcase...) > This is really useful for runtime optimizations for things like > a hierarchical SMP lock manager. You attach all nodes into the > graph for the objects that are intended to be used, and calculate > a Warshalls. Then, as you add leaves, you update using standard > Floyd-Steinberg, so the Warshall's is always accurate. > > This allows you to insert leaf nodes in O(1) along the vector to > the root of the graph. > > For a list of locks you want to test for deadlock, the list itself > describes a vector. > > Using this vector as an arc through the existing Warshall-complete > graph, you look for a Hamiltonian cycle. If the cycle exists, then > you have a deadlock condition. Don't you have a deadlock condition if _any_ cycle exists? Ie, you grab a bunch of locks, blocking on an attempted lock of X. Whatever is holding X end up blocking on one of your locks. You've got a cycle, and thus you've got a deadlock. Why do you need Hamiltonian cycles? They're a pain to find, and I can't see that looking for them gets you anything; I can't see that whether they are present make a difference for this case. > This allows deadlock detection without having to do stack rewind > and/or resource precommit (presuming that the tentative lock vector's > elements are inserted using intention modes to prevent another > tentative lock from coming back "safe"). > > This algorithm was actually the basis of the lock manager in the > NetWare for UNIX server; it was capable of 20,000 transactions a > second -- basically 2 orders of magnitude better than Tuxedo. 8-). Nice! :-) > The computation of deadlock (transitive closure) is done, as in the > symbol table example, by inferring Hamiltonian cycles along the two > edges you know about (the real one and the pretend one made up of > the resources you will require for a given idempotent operation). > > This is terrifically fun stuff to watch when it works. It's much > better than Djikstra's soloution (the banker's algorithm), in > that you wouldn't have to rebuild FreeBSD from the ground up to > make it work... That way to look for deadlocks look right for FreeBSD. However, I still don't get why it need Hamiltonian (as opposed to plain) cycles :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 06:23:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05778 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 06:23:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05750 for ; Thu, 17 Sep 1998 06:23:15 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA06066; Thu, 17 Sep 1998 15:22:43 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA02497; Thu, 17 Sep 1998 15:22:42 +0200 (MET DST) Message-ID: <19980917152242.26074@follo.net> Date: Thu, 17 Sep 1998 15:22:42 +0200 From: Eivind Eklund To: Hallam Oaks P/L list account , "freebsd-hackers@FreeBSD.ORG" Subject: Re: 'struct isa_device' advice sought References: <199809161502.BAA22369@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199809161502.BAA22369@mail.aussie.org>; from Hallam Oaks P/L list account on Thu, Sep 17, 1998 at 01:01:39AM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 17, 1998 at 01:01:39AM +1000, Hallam Oaks P/L list account wrote: > On Wed, 16 Sep 1998 15:47:12 +0200, Eivind Eklund wrote: > > >On Wed, Sep 16, 1998 at 10:24:39PM +1000, Hallam Oaks P/L list account > wrote: > >> My question is this : is the concept of a PCI card masquerading (in > >> a limited sense) as an ISA one a legitimate approach ? Is it likely > >> to cause problems ? I know it's a kludge but the alternative is > >> also not particularly desirable. > > > >The alternative is particularly desireable, and I hope to get time to > >fix it Real Soon Now. It is also necessary to be able to get a clean > >integration of the PnP code (which I have a hacky intergration of > >now). > > ok, from an architecture point of view it's desirable, but recoding all > of that section to suit PCI (in a consistent manner such that it integrates > cleanly with the rest of i4b) is probably too much for me to bite off right > now. I simply don't have a good enough grasp of the i4b package as a whole > to do it intelligently :) > > Nevertheless ... I have a card I need to get going. What do you suggest ? Is > the isa masquerading going to be more trouble than it's worth ? The ISA masquerading will probably work, but it is really dirty. Given that I have no idea when I'll get time, it is probably the best bet for now... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 07:09:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12150 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 07:09:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12145 for ; Thu, 17 Sep 1998 07:09:37 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA13537 for ; Thu, 17 Sep 1998 07:09:15 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA06204 for ; Thu, 17 Sep 1998 07:09:13 -0700 (PDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.68.38]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id KAA22744; Thu, 17 Sep 1998 10:09:13 -0400 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.8/8.8.8) with ESMTP id KAA02717 for ; Thu, 17 Sep 1998 10:09:10 -0400 (EDT) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199809171409.KAA02717@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: GDB modifies shared libraries? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Sep 1998 10:09:09 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was debugging a (large) program using GDB on an xterm (which prevented me from getting the exact text, as you will see). This is on 2.2.6-RELEASE on a P6-200 with 128M ram. I was running as a normal user, not root. I issued the "run" command and GDB said that /usr/lib/libc.so.3.1 had changed and it was re-loading it. That was followed immediately by X freezing, and then a spontaneous re-boot. After the system re-booted, sure enough the date on /usr/lib/libc.so.3.1 had been changed! Now, with this program, GDB generally says that the *program* has changed *every* time I issue the "run" command, but I thought that was just a GDB problem. But I don't understand how GDB can override protections on /usr/lib/libc.so.3.1 in order to change its date. This seems like an OS bug. Any fixes around? -- Robert Withrow -- (+1 978 916 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 07:42:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16499 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 07:42:30 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from icsnet.com (icsnet.com [204.194.104.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16389 for ; Thu, 17 Sep 1998 07:42:11 -0700 (PDT) (envelope-from jeffrey@meltzer.org) Received: HReceived: from xu90.villagenet.com (xu90 [205.136.35.9]) by icsnet.com (ics mailserver) with SMTP id KAA00417; Thu, 17 Sep 1998 10:43:20 -0400 (EDT) Message-ID: <36011CFB.7C87EE72@meltzer.org> Received: from sparc.icsnet.com by xu90.villagenet.com via smtpd (for icsnet.com [204.194.104.2]) with SMTP; 17 Sep 1998 15:10:56 UT Date: Thu, 17 Sep 1998 10:30:19 -0400 From: Jeffrey Meltzer Organization: ICS Network Operations Center X-Mailer: Mozilla 4.5b1 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto References: <199809170543.HAA03300@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'd say it's a 'crap out' because i left it at that point at about 1am last night, and came back at 7am this morning and it was still at the same point. Unless that's how long it's supposed to take? Mark Murray wrote: > > Jeffrey Meltzer wrote: > > Ok. I've given up on the Network install. I sacrificed 150MB of my hard > > drive, and downloaded the OS. setup a 150MB dos partition, and via zipdisk > > dumped freebsd in there. Booted up with the freebsd boot disk, but during > > the setup it craps out at: > > > > DEBUG: Generating /etc/fstab file > > DEBUG: DOS Partition /dev/wd0s1 mounted > > > > I have the freebsd stuff installed in c:\freebsd\bin c:\freebsd\src etc, > > etc. > > > > any ideas? > > What makes you think that is a "crap out"? Things look fine to me... > > 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 -- Jeffrey Meltzer http://www.meltzer.org ICS Network Operations Center Support Manager Phone 516-218-0700/Fax 516-218-0769 620 Johnson Ave. Bohemia, NY 11716 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 08:13:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22614 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 08:13:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22596 for ; Thu, 17 Sep 1998 08:12:59 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:ovKyrqJEuNlMGJQZincUQZ4gtRV7Hoce@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA09407; Thu, 17 Sep 1998 17:11:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809171511.RAA09407@gratis.grondar.za> To: Jeffrey Meltzer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: Your message of " Thu, 17 Sep 1998 10:30:19 -0400." <36011CFB.7C87EE72@meltzer.org> References: <199809170543.HAA03300@gratis.grondar.za> <36011CFB.7C87EE72@meltzer.org> Date: Thu, 17 Sep 1998 17:11:56 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey Meltzer wrote: > i'd say it's a 'crap out' because i left it at that point at about 1am > last night, and came back at 7am this morning and it was still at the > same point. Unless that's how long it's supposed to take? This would have been useful to know. Also useful is _exactly_ what you did. Be very specific about what you did, what you saw what errors you saw (if any) and how your reality deviates from expected reality. The messages you see look normal for a certain stage of the operations. If there was anything else, like it did not respond for many hours, TELL ME. I am not clairvoyant. 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 Sep 17 08:30:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25300 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 08:30:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from icsnet.com (icsnet.com [204.194.104.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25199 for ; Thu, 17 Sep 1998 08:30:06 -0700 (PDT) (envelope-from meltzer@icsnet.com) Received: HReceived: from xu90.villagenet.com (xu90 [205.136.35.9]) by icsnet.com (ics mailserver) with SMTP id LAA01423; Thu, 17 Sep 1998 11:31:13 -0400 (EDT) Message-ID: <36012834.CD373510@icsnet.com> Received: from sparc.icsnet.com by xu90.villagenet.com via smtpd (for icsnet.com [204.194.104.2]) with SMTP; 17 Sep 1998 15:58:49 UT Date: Thu, 17 Sep 1998 11:18:12 -0400 From: Jeffrey Meltzer Organization: ICS Network Operations Center X-Mailer: Mozilla 4.5b1 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto References: <199809170543.HAA03300@gratis.grondar.za> <36011CFB.7C87EE72@meltzer.org> <199809171511.RAA09407@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I'm running through this again, step by step on the Libretto. Booting w/ a FreeBSD boot disk Going through the first visual config screen, getting rid of some conflicts. Here's what i have left: Storage: Floppy Disk Controller IDE/ESDI/MFM Disk Controller Network: NE1000,NE2000,3C503,WD/80xx Ethernet Adapters (actually i've got a Linksys Ethercard) Communications: Parallel Printer Port 8250/16450/16550 Serial Port Input: PS/2 Mouse Syscons Console Driver and a bunch of PCI stuff it won't let me get rid of Next it hit the next screen Novice Installation Go into the pseudo fdisk I've got my 150MB dos partition, and i choose 'C' to create a freebsd partition out of the rest of the disk. i set both partitions to bootable Next, i choose the BootMgr, so i can still use the dos partition in the Disklabel editor, i choose 'A', to let it autoselect the sizes of the partitions Next, i Choose 'A', for all sources and X-window system Next, i choose to install from a dos partition (freebsd is sitting at c:\freebsd) it goes through writing partition, newgs, and all that jazz next thing i know, it dumps me back at the screen when i chose 'a', for all sources and x-window system i hit alt+f2 and i can see a couple cpio's /mnt/stand/etc /mnt/stand/etc/protocols /mnt/stand/etc/rc.conf and a bunch of other stand things /mnt/etc /mnt/etc/protocols and the same things from just above, without the stand DEBUG: Generating /etc/fstab file DEBUG: DOS Partition /etc/wd0s1 mounted and that's it. crapped out. vicious circle ANY IDEAS????????? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 08:41:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27267 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 08:41:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27092 for ; Thu, 17 Sep 1998 08:40:26 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:XClYTffMx/31FTgy01ra6fxpymMDAVxm@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA09515; Thu, 17 Sep 1998 17:39:32 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809171539.RAA09515@gratis.grondar.za> To: Jeffrey Meltzer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: Your message of " Thu, 17 Sep 1998 11:18:12 -0400." <36012834.CD373510@icsnet.com> References: <199809170543.HAA03300@gratis.grondar.za> <36011CFB.7C87EE72@meltzer.org> <199809171511.RAA09407@gratis.grondar.za> <36012834.CD373510@icsnet.com> Date: Thu, 17 Sep 1998 17:39:28 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeffrey Meltzer wrote: > i hit alt+f2 > and i can see > > a couple cpio's > > /mnt/stand/etc > /mnt/stand/etc/protocols > /mnt/stand/etc/rc.conf > and a bunch of other stand things > > /mnt/etc > /mnt/etc/protocols > and the same things from just above, without the stand > > DEBUG: Generating /etc/fstab file > DEBUG: DOS Partition /etc/wd0s1 mounted > > and that's it. > crapped out. > vicious circle ALT-F1. What is happening on that screen? 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 Sep 17 09:09:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01377 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 09:09:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from icsnet.com (icsnet.com [204.194.104.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01361 for ; Thu, 17 Sep 1998 09:09:11 -0700 (PDT) (envelope-from meltzer@icsnet.com) Received: HReceived: from xu90.villagenet.com (xu90 [205.136.35.9]) by icsnet.com (ics mailserver) with SMTP id MAA02182; Thu, 17 Sep 1998 12:10:23 -0400 (EDT) Message-ID: <36013161.752C974A@icsnet.com> Received: from sparc.icsnet.com by xu90.villagenet.com via smtpd (for icsnet.com [204.194.104.2]) with SMTP; 17 Sep 1998 16:37:58 UT Date: Thu, 17 Sep 1998 11:57:21 -0400 From: Jeffrey Meltzer Organization: ICS Network Operations Center X-Mailer: Mozilla 4.5b1 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto References: <199809170543.HAA03300@gratis.grondar.za> <36011CFB.7C87EE72@meltzer.org> <199809171511.RAA09407@gratis.grondar.za> <36012834.CD373510@icsnet.com> <199809171539.RAA09515@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > Jeffrey Meltzer wrote: > > i hit alt+f2 Back at the 'Choose Distributions' screen > > and i can see > > > > a couple cpio's > > > > /mnt/stand/etc > > /mnt/stand/etc/protocols > > /mnt/stand/etc/rc.conf > > and a bunch of other stand things > > > > /mnt/etc > > /mnt/etc/protocols > > and the same things from just above, without the stand > > > > DEBUG: Generating /etc/fstab file > > DEBUG: DOS Partition /etc/wd0s1 mounted > > > > and that's it. > > crapped out. > > vicious circle > > ALT-F1. What is happening on that screen? > > 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 -- Jeffrey Meltzer http://www.meltzer.org ICS Network Operations Center Support Manager Phone 516-218-0700/Fax 516-218-0769 620 Johnson Ave. Bohemia, NY 11716 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 09:20:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04300 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 09:20:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04272 for ; Thu, 17 Sep 1998 09:20:44 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:4upLPNc4QQ+vIpQiYtzhOWtJVHl4vNCN@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id SAA09625; Thu, 17 Sep 1998 18:19:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199809171619.SAA09625@gratis.grondar.za> To: Jeffrey Meltzer cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-Reply-To: Your message of " Thu, 17 Sep 1998 11:57:21 -0400." <36013161.752C974A@icsnet.com> References: <199809170543.HAA03300@gratis.grondar.za> <36011CFB.7C87EE72@meltzer.org> <199809171511.RAA09407@gratis.grondar.za> <36012834.CD373510@icsnet.com> <199809171539.RAA09515@gratis.grondar.za> <36013161.752C974A@icsnet.com> Date: Thu, 17 Sep 1998 18:19:54 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jeffrey Meltzer wrote: > > Jeffrey Meltzer wrote: > > > i hit alt+f2 > Back at the 'Choose Distributions' screen On Alt-f2?? Huh!!?? Time to send a formal bug report. 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 Sep 17 09:32:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07100 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 09:32:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07066 for ; Thu, 17 Sep 1998 09:32:37 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA11090; Thu, 17 Sep 1998 09:32:08 -0700 (PDT) (envelope-from jdp) Message-Id: <199809171632.JAA11090@austin.polstra.com> To: bwithrow@BayNetworks.COM Subject: Re: GDB modifies shared libraries? In-Reply-To: <199809171409.KAA02717@tuva.engeast.baynetworks.com> References: <199809171409.KAA02717@tuva.engeast.baynetworks.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Thu, 17 Sep 1998 09:32:08 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199809171409.KAA02717@tuva.engeast.baynetworks.com>, Robert Withrow wrote: > I was debugging a (large) program using GDB on an xterm (which > prevented me from getting the exact text, as you will see). This > is on 2.2.6-RELEASE on a P6-200 with 128M ram. I was running as > a normal user, not root. > > I issued the "run" command and GDB said that /usr/lib/libc.so.3.1 > had changed and it was re-loading it. That was followed immediately > by X freezing, and then a spontaneous re-boot. > > After the system re-booted, sure enough the date on /usr/lib/libc.so.3.1 > had been changed! > > Now, with this program, GDB generally says that the *program* has changed > *every* time I issue the "run" command, but I thought that was just a > GDB problem. But I don't understand how GDB can override protections > on /usr/lib/libc.so.3.1 in order to change its date. This seems like > an OS bug. Yes, it is a kernel bug. As far as I know, it doesn't actually modify the file -- it just "updates" it with its original contents, changing the timestamp. The problem is believed to be solved in -current (and hence in 3.0). At least, I haven't heard it reported there for a good long time. However, I don't think anybody (except possibly John Dyson) knows exactly what "the" fix was. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 11:54:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03570 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 11:54:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03564 for ; Thu, 17 Sep 1998 11:54:20 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id LAA28955; Thu, 17 Sep 1998 11:53:47 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Jeffrey Meltzer cc: Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on Libretto In-reply-to: Your message of "Thu, 17 Sep 1998 11:57:21 EDT." <36013161.752C974A@icsnet.com> Date: Thu, 17 Sep 1998 11:53:47 -0700 Message-ID: <28951.906058427@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Back at the 'Choose Distributions' screen You must have failed to choose any distributions. You're not hitting "return" at that menu rather than actually selecting some dists with "space", then hitting return? This looks like a case where it's doing exactly what you told it (or didn't, as the case may be) - it's doing everything up to the point of installing dists then seeing that you haven't asked for any and coming back out. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 12:36:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10896 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 12:36:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10872 for ; Thu, 17 Sep 1998 12:36:41 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id PAA19772 for ; Thu, 17 Sep 1998 15:36:09 -0400 (EDT) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.8.8/8.8.7) with ESMTP id PAA00480 for ; Thu, 17 Sep 1998 15:36:08 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Message-Id: <199809171936.PAA00480@stiegl.niksun.com> X-Mailer: exmh version 2.0zeta 7/24/97 From: Andrew Heybey To: freebsd-hackers@FreeBSD.ORG Subject: masking of hardware interrupts in {,icu_}vector.s Date: Thu, 17 Sep 1998 15:36:08 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I'm working with -STABLE though the vectors in -current look unchanged.] The interrupt vectors in sys/i386/isa/vector.s (icu_vector.s in -current) mask the current interrupt in the hardware while the interrupt handler runs. Is this done for any reason besides efficiency? For example, say I wanted to change the interrupt vector to count hardware interrupts even if the handler was already executing. If I dike out the parts of the INTR macro in vector.s as follows: #if 0 movb _imen + IRQ_BYTE(irq_num),%al ; \ orb $IRQ_BIT(irq_num),%al ; \ movb %al,_imen + IRQ_BYTE(irq_num) ; \ outb %al,$icu+ICU_IMR_OFFSET ; \ #endif enable_icus ; \ /* Following line is new code to count HW interrupts. */ \ incl _interrupt_count + (irq_num) * 4 ; /* Count this HW intr */ \ movl _cpl,%eax ; \ testb $IRQ_BIT(irq_num),%reg ; \ jne 2f ; \ incb _intr_nesting_level ; \ __CONCAT(Xresume,irq_num): ; \ FAKE_MCOUNT(12*4(%esp)) ; /* XXX late to avoid double count */ \ incl _cnt+V_INTR ; /* tally interrupts */ \ movl _intr_countp + (irq_num) * 4,%eax ; \ incl (%eax) ; \ movl _cpl,%eax ; \ pushl %eax ; \ pushl _intr_unit + (irq_num) * 4 ; \ orl _intr_mask + (irq_num) * 4,%eax ; \ movl %eax,_cpl ; \ sti ; \ call *_intr_handler + (irq_num) * 4 ; \ cli ; /* must unmask _imen and icu atomically */ \ #if 0 movb _imen + IRQ_BYTE(irq_num),%al ; \ andb $~IRQ_BIT(irq_num),%al ; \ movb %al,_imen + IRQ_BYTE(irq_num) ; \ outb %al,$icu+ICU_IMR_OFFSET ; \ #endif What I think this means is that if the same interrupt happens again, then the handler won't run (because the CPL is set too high), but the vector will run and count the extra interrupt. Is there anything I'm going to break by doing this? I am going to try it to see what happens, but I thought I would ask just in case there is magic about the ICU and/or devices that I don't understand that would make this fail. thanks, andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 13:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26848 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 13:54:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26673 for ; Thu, 17 Sep 1998 13:52:49 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id WAA06377; Thu, 17 Sep 1998 22:51:35 +0200 (MET DST) Message-ID: <19980917225134.A6368@cons.org> Date: Thu, 17 Sep 1998 22:51:34 +0200 From: Martin Cracauer To: John Polstra , bwithrow@BayNetworks.COM Cc: hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? References: <199809171409.KAA02717@tuva.engeast.baynetworks.com> <199809171632.JAA11090@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199809171632.JAA11090@austin.polstra.com>; from John Polstra on Thu, Sep 17, 1998 at 09:32:08AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The original mail of this thread has been forwarded to bugtraq. If someone is certain what goes on here, please given them an update. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 14:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10925 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 14:38:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10722 for ; Thu, 17 Sep 1998 14:37:25 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id XAA03246; Thu, 17 Sep 1998 23:35:18 +0200 (CEST) Message-ID: <19980917233517.22291@foobar.franken.de> Date: Thu, 17 Sep 1998 23:35:17 +0200 From: Harold Gutch To: John Polstra , bwithrow@BayNetworks.COM Cc: hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? References: <199809171409.KAA02717@tuva.engeast.baynetworks.com> <199809171632.JAA11090@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199809171632.JAA11090@austin.polstra.com>; from John Polstra on Thu, Sep 17, 1998 at 09:32:08AM -0700 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 17, 1998 at 09:32:08AM -0700, John Polstra wrote: > > GDB problem. But I don't understand how GDB can override protections > > on /usr/lib/libc.so.3.1 in order to change its date. This seems like > > an OS bug. > > Yes, it is a kernel bug. As far as I know, it doesn't actually modify > the file -- it just "updates" it with its original contents, changing > the timestamp. > Is this really all this bug can do ? Update an arbitrary (?) file with it's original contents again ? Or is it possible to overwrite arbitrary files with arbitrary or random data if "options KTRACE" (or whatever allows this in the kernel) is in the configfile ? I don't believe that this is be possible without "kernel-help", that is without a kernel including some specific stuff (KTRACE ?). -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 14:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12888 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 14:43:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12727 for ; Thu, 17 Sep 1998 14:42:55 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id RAA05734; Thu, 17 Sep 1998 17:41:19 -0400 (EDT) Date: Thu, 17 Sep 1998 17:41:19 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: John Polstra cc: bwithrow@BayNetworks.COM, hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? In-Reply-To: <199809171632.JAA11090@austin.polstra.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 Actually I see someone has just posted Mr. Withrow's message to Bugtraq. Odd. He's hinting that it's a security issue, which I don't quite see. It could create some confusion though, I suppose. --- Charles Sprickman spork@super-g.com On Thu, 17 Sep 1998, John Polstra wrote: > In article <199809171409.KAA02717@tuva.engeast.baynetworks.com>, > Robert Withrow wrote: > > I was debugging a (large) program using GDB on an xterm (which > > prevented me from getting the exact text, as you will see). This > > is on 2.2.6-RELEASE on a P6-200 with 128M ram. I was running as > > a normal user, not root. > > > > I issued the "run" command and GDB said that /usr/lib/libc.so.3.1 > > had changed and it was re-loading it. That was followed immediately > > by X freezing, and then a spontaneous re-boot. > > > > After the system re-booted, sure enough the date on /usr/lib/libc.so.3.1 > > had been changed! > > > > Now, with this program, GDB generally says that the *program* has changed > > *every* time I issue the "run" command, but I thought that was just a > > GDB problem. But I don't understand how GDB can override protections > > on /usr/lib/libc.so.3.1 in order to change its date. This seems like > > an OS bug. > > Yes, it is a kernel bug. As far as I know, it doesn't actually modify > the file -- it just "updates" it with its original contents, changing > the timestamp. > > The problem is believed to be solved in -current (and hence in 3.0). > At least, I haven't heard it reported there for a good long time. > However, I don't think anybody (except possibly John Dyson) knows > exactly what "the" fix was. > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > > 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 Sep 17 14:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15860 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 14:55:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts02-011.dublin.indigo.ie [194.125.134.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15666 for ; Thu, 17 Sep 1998 14:54:20 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA01812; Thu, 17 Sep 1998 22:47:04 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199809172147.WAA01812@indigo.ie> Date: Thu, 17 Sep 1998 22:47:03 +0000 In-Reply-To: <25283.906018720@time.cdrom.com>; "Jordan K. Hubbard" Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: Promotional CDs and evil customs agencies. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 17, 12:52am, "Jordan K. Hubbard" wrote: } Subject: Promotional CDs and evil customs agencies. > [ I know that this is typically -chat material, but I'm not going to > reach the people who are actually involved by sending this to -chat ] > > I just thought I'd let folks know that I've reached a hard, but > irrevokable, decision with regard to sending promotional CDs overseas: > > I'm not going to do it anymore. I was talking to you about getting a promo CD for the Irish Times (you even said it was a good letter !!*%%#$^) so I take it thats off the cards now? What kind of volumes of promo CDs were you sending around? I would have never expected a couple of CDs getting much attention at customs, sheesh. > If you know of someone in the U.S. who is willing to deal with all > these issues for you or otherwise provide "trans-shipment" outside the > U.S., then that's obviously something else entirely and I'm perfectly > willing to do that. Sending CDs within the U.S. is not a problem. I might be interested in doing it for Europe depending on volume and the amount of hassle it is sending them to people. (I really can't see this being a problem, maybe its just US->EU thats causing difficulty) So, how many CDs are we talking a month/week on average? > It's > not just enough to have a distributor there, you need to have the CDs > *made* in europe in order to avoid customs problems. For sale or promo? Did you do to the customs people, you weren't a drug trafficker in a previous life or anything? Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 15:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17543 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 15:02:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts02-011.dublin.indigo.ie [194.125.134.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17128; Thu, 17 Sep 1998 15:00:42 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id WAA01841; Thu, 17 Sep 1998 22:53:19 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199809172153.WAA01841@indigo.ie> Date: Thu, 17 Sep 1998 22:53:19 +0000 In-Reply-To: <199809152109.OAA25292@usr09.primenet.com>; Terry Lambert Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Terry Lambert , sthaug@nethelp.no Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets Cc: hackers@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 15, 9:09pm, Terry Lambert wrote: } Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets > > > > I agree that this is the best place for it - but I'd also like FreeBSD > > systems to be secure against smurf attacks out of the box, even if the > > router/firewall/whatever lets IP broadcast through (and translates it > > to link-level broadcast). > > And what about NFS hijack, SMB hijack, source routing, IP spoofing, > etc.? These are different issues, someone can be partly responsible for a smurf attack without ever realising it and (more importantly) without _their_ security/quality of service being compromised. I don't care how many boxes get hacked as long as they aren't mine, but it's reasonable to complain about a configuration which makes it too easy for script kiddies to exploit the ineptitude or carelessness of admins to affect _other_ competant and careful admins boxes. It's akin to shipping sendmail with open relaying. Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 16:15:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28904 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 16:15:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28880 for ; Thu, 17 Sep 1998 16:15:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01195; Thu, 17 Sep 1998 16:18:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809172318.QAA01195@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Harold Gutch cc: John Polstra , bwithrow@BayNetworks.COM, hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? In-reply-to: Your message of "Thu, 17 Sep 1998 23:35:17 +0200." <19980917233517.22291@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Sep 1998 16:18:13 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Sep 17, 1998 at 09:32:08AM -0700, John Polstra wrote: > > > GDB problem. But I don't understand how GDB can override protections > > > on /usr/lib/libc.so.3.1 in order to change its date. This seems like > > > an OS bug. > > > > Yes, it is a kernel bug. As far as I know, it doesn't actually modify > > the file -- it just "updates" it with its original contents, changing > > the timestamp. > > > Is this really all this bug can do ? Update an arbitrary (?) file > with it's original contents again ? Yes. > Or is it possible to overwrite arbitrary files with arbitrary or > random data if "options KTRACE" (or whatever allows this in the > kernel) is in the configfile ? No. What appears to happen is that one or more pages in the text section are marked dirty (for some unknown reason) and thus written out. The page contents themselves are read-only, so they can't be modified. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 19:32:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07725 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 19:32:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07635 for ; Thu, 17 Sep 1998 19:32:13 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA00719; Thu, 17 Sep 1998 19:32:12 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: rotel@indigo.ie cc: hackers@FreeBSD.ORG Subject: Re: Promotional CDs and evil customs agencies. In-reply-to: Your message of "Thu, 17 Sep 1998 22:47:03 -0000." <199809172147.WAA01812@indigo.ie> Date: Thu, 17 Sep 1998 19:32:12 -0700 Message-ID: <715.906085932@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was talking to you about getting a promo CD for the Irish Times > (you even said it was a good letter !!*%%#$^) so I take it thats off > the cards now? A single promo CD for a journalist (or even one or two) is an entirely different matter and I apologise for not clarifying that. What causes trouble are the bulk orders of 20 or more; I sent over 500 to India alone in one batch and boy was THAT fun. :-( > For sale or promo? Did you do to the customs people, you weren't > a drug trafficker in a previous life or anything? Irish customs always proceeds on the assumption that *everyone* is a drug trafficker. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 20:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14648 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 20:05:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14633 for ; Thu, 17 Sep 1998 20:05:18 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA07286; Thu, 17 Sep 1998 20:04:47 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd007260; Thu Sep 17 20:04:41 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA00324; Thu, 17 Sep 1998 20:04:35 -0700 (MST) From: Terry Lambert Message-Id: <199809180304.UAA00324@usr04.primenet.com> Subject: Re: Unused functions To: eivind@yes.no (Eivind Eklund) Date: Fri, 18 Sep 1998 03:04:35 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19980917142841.01218@follo.net> from "Eivind Eklund" at Sep 17, 98 02:28:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [I'm keeping a lot of context to make this easy to read; I also note > that I didn't move this to -chat when I thought I did, but we're > getting into some locking-related discussions that are again related > to -hackers, so I keep it here now] I'll take the compiler discussion to private email... > > Using this vector as an arc through the existing Warshall-complete > > graph, you look for a Hamiltonian cycle. If the cycle exists, then > > you have a deadlock condition. > > Don't you have a deadlock condition if _any_ cycle exists? > > Ie, you grab a bunch of locks, blocking on an attempted lock of X. > Whatever is holding X end up blocking on one of your locks. You've > got a cycle, and thus you've got a deadlock. Yes. The question is "how do I know when I have a cycle?". The best way is to take the list of locks that an entity has, and consider it as a connectivity vector through a graph. For the standard graph, you have precalculated transitive closure via Warshall's before you try this. Basically, this means I have: 1) A DAG of hierarchically connected nodes that model the granularity of the locking infrastructure for the system; an individual node is called a "LOCKABLE". 2) An DAG of hierarchically related contexts that can hold locks. In typical use, this will be a set of related scheduling entities that can not be permitted to lock against themselves (e.g., kernel threads, or more generally, kernel schedulable entities, or KSE's). The most common DAG will reduce to a simply connected DAG of KSE's, or a "locking context vector". An individual node is called a "LOCKING ENTITY". 3) A simply connected DAG (vector) that describes the locks held by an individual locking entity *or* locakable. This is a "LOCK VECTOR". An individual vector element is called a "LOCK". ;-). So what we have is the intersection of two graphs complexly connected via one or more vectors that describe the connection points. When I ask for a lock, I'm asking to extend a vector by one element off (a) the locakable and (b) the locking entity. In effect, I have a 5 dimensional graph that I need to search for a cycle. > Why do you need Hamiltonian cycles? They're a pain to find, and I > can't see that looking for them gets you anything; I can't see that > whether they are present make a difference for this case. Because most of the work to find them has already been done, and then cached, into the structure of the graph. I have the transitive closure over the lockable graph, and I have the closure over the the locking entity graph, and I inherit the vector back to the "parent" (topmost) locking entity. This means I can find a Hamiltonian by examining from the point I want to lock in the lockable graph to the root of the lockable graph, looking for instances of my locking entity. If I find it, then I have a cycle. So it's mostly precalculated, and the time it takes is the time needed for exactly one traversal to the root. In generally, this the depth of the locakable in the graph which is being locked number of pointer dereferences + compares. For locking, this is damn fast, and the cost of maintaining a closure calculation when adding a leaf node (i.e., registering a new lockable into the tree) is trivial, as is the cost of inheriting the locks up. > That way to look for deadlocks look right for FreeBSD. However, I > still don't get why it need Hamiltonian (as opposed to plain) cycles > :-( Because they are nearly free, given the already cached data. Effectively, each vector is reduced to a single element, and each locking entity DAG is reduced to a single element. One of the biggest wins here is that you don't have to take IPI's for L1/L2 cache coherency for most locks. The use of intention mode locking to implement the locks on top of this framework justs ads gravy to already high concurrency. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 20:08:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15251 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 20:08:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15183 for ; Thu, 17 Sep 1998 20:08:24 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA29704; Thu, 17 Sep 1998 20:08:00 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd029652; Thu Sep 17 20:07:54 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA00463; Thu, 17 Sep 1998 20:07:49 -0700 (MST) From: Terry Lambert Message-Id: <199809180307.UAA00463@usr04.primenet.com> Subject: Re: GDB modifies shared libraries? To: jdp@polstra.com (John Polstra) Date: Fri, 18 Sep 1998 03:07:48 +0000 (GMT) Cc: bwithrow@BayNetworks.COM, hackers@FreeBSD.ORG In-Reply-To: <199809171632.JAA11090@austin.polstra.com> from "John Polstra" at Sep 17, 98 09:32:08 am X-Mailer: ELM [version 2.4 PL25] 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 > Yes, it is a kernel bug. As far as I know, it doesn't actually modify > the file -- it just "updates" it with its original contents, changing > the timestamp. This appears to be a problem with the mmap code, and an ITIMES on a vm object for a page that has been improperly reused (from the other behaviour associated with a known mmap bug -- this could be an unrelated problem, however). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 21:45:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00599 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 21:45:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from creator.gu.net (creator-eth0.gu.net [194.93.191.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00589 for ; Thu, 17 Sep 1998 21:45:44 -0700 (PDT) (envelope-from stesin@gu.net) Received: from localhost (stesin@localhost) by creator.gu.net (8.8.8/8.8.8) with SMTP id HAA20485 for ; Fri, 18 Sep 1998 07:45:12 +0300 Date: Fri, 18 Sep 1998 07:45:12 +0300 (EEST) From: To: hackers@FreeBSD.ORG Subject: Unified Unix (c) Intel? 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 What news.com says: Intel is working with Compaq, IBM, HP, Sun, and SCO to develop common standards for the Unix operating systems, a critical step as the company develops high-end, next-gen 64-bit Merced technologies. http://www.news.com/News/Item/0%2C4%2C26490%2C00.html?dd.ne.tx.ts1.0917 Comments? How can/will/might this affect FreeBSD development? Best, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 17 23:00:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12019 for freebsd-hackers-outgoing; Thu, 17 Sep 1998 23:00:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12013; Thu, 17 Sep 1998 23:00:38 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA28028; Thu, 17 Sep 1998 23:00:15 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd027951; Thu Sep 17 23:00:05 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA00693; Thu, 17 Sep 1998 20:11:16 -0700 (MST) From: Terry Lambert Message-Id: <199809180311.UAA00693@usr04.primenet.com> Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets To: rotel@indigo.ie Date: Fri, 18 Sep 1998 03:11:14 +0000 (GMT) Cc: tlambert@primenet.com, sthaug@nethelp.no, hackers@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <199809172153.WAA01841@indigo.ie> from "Niall Smart" at Sep 17, 98 10:53:19 pm X-Mailer: ELM [version 2.4 PL25] 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 > These are different issues, someone can be partly responsible for > a smurf attack without ever realising it and (more importantly) > without _their_ security/quality of service being compromised. I > don't care how many boxes get hacked as long as they aren't mine, > but it's reasonable to complain about a configuration which makes > it too easy for script kiddies to exploit the ineptitude or > carelessness of admins to affect _other_ competant and careful > admins boxes. > > It's akin to shipping sendmail with open relaying. If you want a C2 hardened system, quit pussyfooting around and start addressing the real issues leading up to C2 certification. Otherwise, griping about something that will never happen given a correctly configured firewall, and which "fixing" will break a behaviour that is universally known to be useful, seems a bit counter-productive. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 00:25:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21780 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 00:25:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from homer.talcom.net ([209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21775 for ; Fri, 18 Sep 1998 00:25:20 -0700 (PDT) (envelope-from leo@homer.talcom.net) Received: (from leo@localhost) by homer.talcom.net (8.8.8/8.8.5) id DAA17042; Fri, 18 Sep 1998 03:26:19 -0400 (EDT) Message-ID: <19980918032618.47449@talcom.net> Date: Fri, 18 Sep 1998 03:26:18 -0400 From: Leo Papandreou To: hackers@FreeBSD.ORG Subject: Re: Unified Unix (c) Intel? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from stesin@gu.kiev.ua on Fri, Sep 18, 1998 at 07:45:12AM +0300 X-Organization: Once neatly stacked a pile of paper. X-Wife: Forgotten but not gone. X-No-Archive: Yes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 18, 1998 at 07:45:12AM +0300, stesin@gu.kiev.ua wrote: > > What news.com says: > > Intel is working with Compaq, IBM, HP, Sun, and SCO to develop common > standards for the Unix operating systems, Bullwinkle: Hey, Rocky, wanna see me pull a rabbit out of my hat? Rocky: Aaagain? > a critical step as the company > develops high-end, next-gen 64-bit Merced technologies. Translation: we're hedging our bets for the timely appearance of NT on Merced. > http://www.news.com/News/Item/0%2C4%2C26490%2C00.html?dd.ne.tx.ts1.0917 > > Comments? How can/will/might this affect FreeBSD development? There can be but one winner. The time is ripe for FreeBSD to ally itself with Microsoft. > > Best, > Andrew > > > 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 Fri Sep 18 02:27:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06005 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 02:27:12 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06000 for ; Fri, 18 Sep 1998 02:27:09 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA18846; Fri, 18 Sep 1998 10:26:13 +0100 (BST) Date: Fri, 18 Sep 1998 10:26:12 +0100 (BST) From: Doug Rabson To: Leo Papandreou cc: hackers@FreeBSD.ORG Subject: Re: Unified Unix (c) Intel? In-Reply-To: <19980918032618.47449@talcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Sep 1998, Leo Papandreou wrote: > On Fri, Sep 18, 1998 at 07:45:12AM +0300, stesin@gu.kiev.ua wrote: > > > > What news.com says: > > > > Intel is working with Compaq, IBM, HP, Sun, and SCO to develop common > > standards for the Unix operating systems, > > > Bullwinkle: Hey, Rocky, wanna see me pull a rabbit out of my hat? > Rocky: Aaagain? > > > a critical step as the company > > develops high-end, next-gen 64-bit Merced technologies. > > Translation: we're hedging our bets for the timely appearance of > NT on Merced. > > > http://www.news.com/News/Item/0%2C4%2C26490%2C00.html?dd.ne.tx.ts1.0917 > > > > Comments? How can/will/might this affect FreeBSD development? > > There can be but one winner. The time is ripe for FreeBSD to ally > itself with Microsoft. Please no! I just spent two years working at Microsoft! Please don't make me go back :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 05:33:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19358 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 05:33:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19341 for ; Fri, 18 Sep 1998 05:32:46 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id OAA17792 for ; Fri, 18 Sep 1998 14:39:53 +0200 (SAST) Received: by citadel via recvmail id 17790; Fri Sep 18 14:39:06 1998 From: Graham Wheeler Message-Id: <199809181237.OAA03132@cdsec.com> Subject: FreeBSD hanging/rebooting To: hackers@FreeBSD.ORG Date: Fri, 18 Sep 1998 14:37:40 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks We have a couple of clients are complaining about their systems hanging or rebooting. Usually this is preceded by some `fork: resource temporarily unavailable' log messages, or failed calls to socket() (usually by named). There are also occasional log messages generated by inetd, of the form: `realloc: junk pointer (too low to make sense)'. The obvious explanation is that the file descriptor table is too small. I have built a new kernel, with MAXUSERS set to 100, and a modified param.c which sets NPROC to (64+16*MAXUSERS) (i.e. 1664) and maxfiles to (NPROC*10) (i.e. 16640). Unfortunately, this hasn't solved the problem. I have got a client to send me the output of `top' and `lsof' when the log messages start appearing, and it appears to occur when there are typically 100-200 processes running, and about 500-600 open files, with less than 50% of the swap space used, and a load average of about 2. The system should hardly be breaking sweat, from all appearances, but there are at least four separate systems on which this is occuring. These are all running FreeBSD 2.2.2; we are about to upgrade them to 2.2.7 but I'm not sure that will solve the problem. At the moment I can't seem to be able to access www.freebsd.org (even though I can ping it), so I haven't been able to search the site for clues. But if anyone can suggest anything else worth trying, I would appreciate it. TIA gram -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 07:39:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03638 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 07:39:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03633 for ; Fri, 18 Sep 1998 07:39:39 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id QAA23943 for ; Fri, 18 Sep 1998 16:46:54 +0200 (SAST) Received: by citadel via recvmail id 23893; Fri Sep 18 16:46:17 1998 From: Graham Wheeler Message-Id: <199809181445.QAA03398@cdsec.com> Subject: Re: FreeBSD hanging/rebooting To: hackers@FreeBSD.ORG Date: Fri, 18 Sep 1998 16:45:00 +0200 (SAT) X-Mailer: ELM [version 2.4 PL25-h4.1] 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 While this may or may not be related to the other problems we are experiencing, I just ran a test program of mine that used to crash 2.2.2 and noticed that it still crashes 2.2.7. I posted a similar program a long time back; clearly the problem that it reveals still exists. When run as root, this program forks child processes until the system runs out of swap space, after which it is killed by a signal. The entire O/S then hangs. Alt-F1 etc still works to change VTs, but nothing else works, and a hard reset is needed. #include #include #define MAXPROC 2000 main() { int pids[MAXPROC], i; for (i = 0; i < MAXPROC; i++) { pids[i] = fork(); if (pids[i] < 0) { perror("fork"); break; } else if (pids[i] == 0) /* child */ { sleep(60); exit(0); } else printf("%d\n", i); } sleep(30); } -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 07:48:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05004 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 07:48:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04880 for ; Fri, 18 Sep 1998 07:47:41 -0700 (PDT) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id QAA24319; Fri, 18 Sep 1998 16:54:54 +0200 (SAST) Received: by citadel via recvmail id 24271; Fri Sep 18 16:54:29 1998 From: Graham Wheeler Message-Id: <199809181453.QAA03418@cdsec.com> Subject: Re: FreeBSD hanging/rebooting To: bright@hotjobs.com (Alfred Perlstein) Date: Fri, 18 Sep 1998 16:53:13 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Sep 18, 98 10:39:59 am X-Mailer: ELM [version 2.4 PL25-h4.1] 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 > > > 2.2.7 is really good, however if you can make your clients hold out a bit > 3.0-release is coming out, the whole system is MUCH better and refined. Unfortunately, these are live firewalls, and people are starting to scream at me to do something. 8-( > odd question, if this is happening now... and not in the past, did you > install 2.2.2 recently? or is this a long time ago install that's not > working right now...? We have been basing our firewall on 2.2.2 since about a month after it was released. We have a reasonably large number of firewalls installed, The problem is occurring on about 4 of them, which have been handling increasing loads over time. All of them have been running for at least six months (previously on FreeBSD 2.1.6). Two have 32Mb RAM, and two have 64Mb. The swap space in each is calculated as (16Mb + 2 x physical). -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 08:33:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09325 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 08:33:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09320 for ; Fri, 18 Sep 1998 08:33:21 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA21509; Fri, 18 Sep 1998 08:28:00 -0700 (PDT) Message-Id: <199809181528.IAA21509@implode.root.com> To: Robert Withrow cc: hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? From: David Greenman Reply-To: dg@root.com Date: Fri, 18 Sep 1998 08:28:00 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I was debugging a (large) program using GDB on an xterm (which >prevented me from getting the exact text, as you will see). This >is on 2.2.6-RELEASE on a P6-200 with 128M ram. I was running as >a normal user, not root. > >I issued the "run" command and GDB said that /usr/lib/libc.so.3.1 >had changed and it was re-loading it. That was followed immediately >by X freezing, and then a spontaneous re-boot. > >After the system re-booted, sure enough the date on /usr/lib/libc.so.3.1 >had been changed! > >Now, with this program, GDB generally says that the *program* has changed >*every* time I issue the "run" command, but I thought that was just a >GDB problem. But I don't understand how GDB can override protections >on /usr/lib/libc.so.3.1 in order to change its date. This seems like >an OS bug. > >Any fixes around? I think this may have been fixed already in newer versions of FreeBSD. I seem to recall a procfs bug (or was it ptrace??) that was responsible. Is there any chance you code try the same thing on a 2.2.7 (or -current) machine? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 08:56:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12766 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 08:56:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bashful.realminfo.com (bashful.realminfo.com [208.205.6.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12692 for ; Fri, 18 Sep 1998 08:56:02 -0700 (PDT) (envelope-from smyth@bashful.realminfo.com) Received: from localhost (smyth@localhost) by bashful.realminfo.com (8.8.7/8.8.7) with SMTP id MAA01873 for ; Fri, 18 Sep 1998 12:06:11 -0400 Date: Fri, 18 Sep 1998 12:06:11 -0400 (EDT) From: Scott Smyth To: freebsd-hackers Subject: memory allocation above "physical" memory 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 If the kernel is hacked to only know about 64 MB, is there functionality already in the BSD kernel so allocate the memory that may lie above what the kernel "knows" about. For instance, in linux, vremap builds new page tables and returns a virtual address you can use. So, I am looking for a function that retrieves memory the kernel does not know about necessarily and maps it to virtual addresses (whether or not it is contigous in physical memory -- it may be). The example: physical memory the kernel knows: 64 MB, but the real memory banks hold 96 MB. How can I access the top 32 MB? Does functionality exist for: 1) getting page tables; 2) mapping page tables to virtual addresses. Thanks, Scott -- Scott Smyth, Senior Developer R&D (770) 446-1332 ssmyth@realminfo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 10:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20656 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 10:00:50 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (castles149.castles.com [208.214.165.149]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20651 for ; Fri, 18 Sep 1998 10:00:47 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id KAA00787; Fri, 18 Sep 1998 10:06:09 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809181706.KAA00787@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Scott Smyth cc: freebsd-hackers Subject: Re: memory allocation above "physical" memory In-reply-to: Your message of "Fri, 18 Sep 1998 12:06:11 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 10:06:08 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the kernel is hacked to only know about 64 MB, is there > functionality already in the BSD kernel so allocate the memory > that may lie above what the kernel "knows" about. For instance, > in linux, vremap builds new page tables and returns a virtual > address you can use. So, I am looking for a function that > retrieves memory the kernel does not know about necessarily and > maps it to virtual addresses (whether or not it is contigous in > physical memory -- it may be). > > The example: physical memory the kernel knows: 64 MB, but the > real memory banks hold 96 MB. How can I access the top 32 MB? > Does functionality exist for: > 1) getting page tables; > 2) mapping page tables to virtual addresses. In most cases this is already taken care of; there should be no systems on which physical memory is not correctly sized if you are running a recent release or 3.0-current. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 11:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28500 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 11:00:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bashful.realminfo.com (bashful.realminfo.com [208.205.6.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28490 for ; Fri, 18 Sep 1998 11:00:15 -0700 (PDT) (envelope-from smyth@bashful.realminfo.com) Received: from localhost (smyth@localhost) by bashful.realminfo.com (8.8.7/8.8.7) with SMTP id OAA02807; Fri, 18 Sep 1998 14:09:39 -0400 Date: Fri, 18 Sep 1998 14:09:39 -0400 (EDT) From: Scott Smyth To: Mike Smith cc: freebsd-hackers Subject: Re: memory allocation above "physical" memory In-Reply-To: <199809181706.KAA00787@word.smith.net.au> 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, 18 Sep 1998, Mike Smith wrote: > > If the kernel is hacked to only know about 64 MB, is there > > functionality already in the BSD kernel so allocate the memory > > that may lie above what the kernel "knows" about. For instance, > > in linux, vremap builds new page tables and returns a virtual > > address you can use. So, I am looking for a function that > > retrieves memory the kernel does not know about necessarily and > > maps it to virtual addresses (whether or not it is contigous in > > physical memory -- it may be). > > > > The example: physical memory the kernel knows: 64 MB, but the > > real memory banks hold 96 MB. How can I access the top 32 MB? > > Does functionality exist for: > > 1) getting page tables; > > 2) mapping page tables to virtual addresses. > > In most cases this is already taken care of; there should be no systems > on which physical memory is not correctly sized if you are running a > recent release or 3.0-current. > You are right. This is a special case. I am going to try creating a device that d_mmap() the memory and treats it like device pages (i.e., not managed by the kernel). It is similar to a frame buffer. I was just wondering if there were any standard functions similar to linux. Thanks -- Scott Smyth, Senior Developer R&D (770) 446-1332 ssmyth@realminfo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 12:14:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12563 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 12:14:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12557 for ; Fri, 18 Sep 1998 12:14:19 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA15433; Fri, 18 Sep 1998 13:07:04 -0600 (MDT) Date: Fri, 18 Sep 1998 13:07:04 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809181907.NAA15433@narnia.plutotech.com> To: Mike Smith cc: hackers@FreeBSD.ORG, Scott Smyth Subject: Re: memory allocation above "physical" memory Newsgroups: pluto.freebsd.hackers In-Reply-To: <199809181706.KAA00787@word.smith.net.au> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199809181706.KAA00787@word.smith.net.au> you wrote: >> If the kernel is hacked to only know about 64 MB, is there >> functionality already in the BSD kernel so allocate the memory >> that may lie above what the kernel "knows" about. For instance, >> in linux, vremap builds new page tables and returns a virtual >> address you can use. So, I am looking for a function that >> retrieves memory the kernel does not know about necessarily and >> maps it to virtual addresses (whether or not it is contigous in >> physical memory -- it may be). >> >> The example: physical memory the kernel knows: 64 MB, but the >> real memory banks hold 96 MB. How can I access the top 32 MB? >> Does functionality exist for: >> 1) getting page tables; >> 2) mapping page tables to virtual addresses. > > In most cases this is already taken care of; there should be no systems > on which physical memory is not correctly sized if you are running a > recent release or 3.0-current. Although I don't know why Scott wants to map this memory into kernel virtual memory (does the kernel or userland app need to grovel through the data???), I know that he has purposefully "stolen" the memory from the kernel. My guess is that the easiest way to map this into the kernel virtual address space is via pmap_mapdev(). To get this mapped into a userland process would probably require a device driver with a mmap entry point. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 13:42:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29508 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 13:42:41 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29502 for ; Fri, 18 Sep 1998 13:42:35 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with SMTP id OAA03546 for ; Fri, 18 Sep 1998 14:42:10 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Fri, 18 Sep 1998 14:42:09 -0600 (MDT) From: Brian Handy To: freebsd-hackers@FreeBSD.ORG Subject: I can't compile -STABLE Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I'm trying to buildworld on a 2.2-STABLE machine. Last 'make world' happened July 8, so I re-cvsupped -stable and had another go at it. I'm sticking on something in libc (error included below). I've tried 'make bootstrap', I've removed my obj directory completely and started from scratch, and 'make buildworld' gets me nowhere. I imagine this is pilot error...any suggestions? Thanks, Brian -------------------- cc -fpic -DPIC -O2 -pipe -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/b/src/lib/libc/../libc/locale -DYP -I/usr/obj/usr/src/tmp/usr/include -c /b/src/lib/libc/../libc/i386/sys/i386_set_ldt.c -o i386_set_ldt.so building shared c library (version 3.1) nm: setreuid.so: not object file or archive nm: setrlimit.so: not object file or archive nm: bt_debug.so: no name list nm: euc.so: no name list nm: mskanji.so: no name list nm: utf2.so: no name list nm: setreuid.so: not object file or archive nm: setrlimit.so: not object file or archive ld: setrlimit.so: malformed input file (not rel or archive) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 14:06:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03526 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 14:06:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from odd.qualcomm.com (odd.qualcomm.com [129.46.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03517 for ; Fri, 18 Sep 1998 14:06:45 -0700 (PDT) (envelope-from mmitchel@qualcomm.com) Received: from mmitchel-nt (NOBODY@mmitchel-nt.qualcomm.com [129.46.171.128]) by odd.qualcomm.com (8.8.5/1.4/8.7.2/1.14) with SMTP id OAA23924 for ; Fri, 18 Sep 1998 14:06:23 -0700 (PDT) From: "Mike Mitchell" To: "FreeBSD Hackers List" Subject: query: www.freebsd.org down? Date: Fri, 18 Sep 1998 14:06:19 -0700 Message-ID: <000201bde348$2ec3b450$80ab2e81@mmitchel-nt.qualcomm.com> 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 8.5, Build 4.71.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been attempting to grab some driver information from www.freebsd.org and am having little luck. Is it down today? Thank you for your time and effort. Mike Mitchell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 14:24:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05077 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 14:24:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05063 for ; Fri, 18 Sep 1998 14:24:39 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id RAA16662 for ; Fri, 18 Sep 1998 17:24:12 -0400 (EDT) Date: Fri, 18 Sep 1998 17:24:12 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun1 To: hackers Subject: PC memory usage (what is PIC?) 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 read in the FreeBSD handbook on PC memory usage: Since it has been linked for another (high) address, it will have to execute PIC until the page table and page directory stuff is setup properly, at which point paging will be enabled and the kernel will finally run at the address for which it was linked. Can anyone explain to me what is PIC and the two different linked addresses mentioned here? Thanks for your help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 15:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12173 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 15:07:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12157 for ; Fri, 18 Sep 1998 15:07:38 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id PAA10420; Fri, 18 Sep 1998 15:07:15 -0700 (PDT) Message-ID: <19980918150715.F6421@Alameda.net> Date: Fri, 18 Sep 1998 15:07:15 -0700 From: Ulf Zimmermann To: Mike Mitchell , FreeBSD Hackers List Subject: Re: query: www.freebsd.org down? Reply-To: ulf@Alameda.net References: <000201bde348$2ec3b450$80ab2e81@mmitchel-nt.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <000201bde348$2ec3b450$80ab2e81@mmitchel-nt.qualcomm.com>; from Mike Mitchell on Fri, Sep 18, 1998 at 02:06:19PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 18, 1998 at 02:06:19PM -0700, Mike Mitchell wrote: > I have been attempting to grab some driver information from www.freebsd.org > and am having little luck. Is it down today? > > Thank you for your time and effort. I can reach www.freebsd.org fine (3:07pm PDT) > > Mike Mitchell > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 15:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12234 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 15:08:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12197 for ; Fri, 18 Sep 1998 15:07:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01422; Fri, 18 Sep 1998 15:12:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809182212.PAA01422@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: zhihuizhang cc: hackers Subject: Re: PC memory usage (what is PIC?) In-reply-to: Your message of "Fri, 18 Sep 1998 17:24:12 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Sep 1998 15:12:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I read in the FreeBSD handbook on PC memory usage: > > Since it has been linked for another (high) address, it will have to > execute PIC until the page table and page directory stuff is setup properly, > at which point paging will be enabled and the kernel will finally run at > the address for which it was linked. > > Can anyone explain to me what is PIC and the two different linked > addresses mentioned here? PIC is position-independant code. The kernel is linked to run at a virtual address different from the physical address that it's loaded at. When it starts, it can't know what the current virtual:physical mapping is and thus what the current virtual address is, so everything must be performed relative to %eip. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 15:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19896 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 15:43:08 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19707 for ; Fri, 18 Sep 1998 15:42:04 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id SAA09452; Fri, 18 Sep 1998 18:53:51 -0400 (EDT) Date: Fri, 18 Sep 1998 18:53:50 -0400 (EDT) From: Charles Youse To: zhihuizhang cc: hackers Subject: Re: PC memory usage (what is PIC?) 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, 18 Sep 1998, zhihuizhang wrote: > Since it has been linked for another (high) address, it will have to > execute PIC until the page table and page directory stuff is setup properly, > at which point paging will be enabled and the kernel will finally run at > the address for which it was linked. > > Can anyone explain to me what is PIC and the two different linked > addresses mentioned here? PIC refers to Position-Independent Code, which requires that all references to memory be relative to the IP register. Code written in this way will execute correctly no matter where it is loaded into the address space. Because the kernel is linked to run at a different address than it's loaded, references to absolute addresses will fetch invalid data from a [nonexistent] random memory location. The solution is to restrict the kernel to PIC (which has no such absolute references) until the vm subsystem is initialized to redirect those absolute [virtual] addresses to the proper physical addresses. It's actually much easier to understand than it is to explain ;) Chuck Youse cyouse@syncom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 16:40:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02598 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 16:40:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02538 for ; Fri, 18 Sep 1998 16:40:30 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA14525; Fri, 18 Sep 1998 16:40:02 -0700 (PDT) Message-ID: <19980918164001.B10612@Alameda.net> Date: Fri, 18 Sep 1998 16:40:01 -0700 From: Ulf Zimmermann To: hackers@FreeBSD.ORG Subject: Question to the ethernet driver programmer about 10/100 HD/FD switch Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do you handle the switch of 10, 100, Full and Half duplex via ifconfig in regards to packets in the queue ? Wait that they are all send ? Just go ahead and switch ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 18:13:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17610 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 18:13:48 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17589 for ; Fri, 18 Sep 1998 18:13:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA04143; Fri, 18 Sep 1998 18:13:29 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Graham Wheeler cc: bright@hotjobs.com (Alfred Perlstein), hackers@FreeBSD.ORG Subject: Re: FreeBSD hanging/rebooting In-reply-to: Your message of "Sat, 18 Sep 1998 16:53:13 +0200." <199809181453.QAA03418@cdsec.com> Date: Fri, 18 Sep 1998 18:13:29 -0700 Message-ID: <4139.906167609@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have been basing our firewall on 2.2.2 since about a month after > it was released. We have a reasonably large number of firewalls installed, > The problem is occurring on about 4 of them, which have been handling > increasing loads over time. All of them have been running for at least six > months (previously on FreeBSD 2.1.6). > > Two have 32Mb RAM, and two have 64Mb. The swap space in each is calculated > as (16Mb + 2 x physical). If it's any consolation, I have seen this problem at a local ISP friend whom I help out from time to time and I'm no closer to fixing it either. It seems to be a combination of some bogus code in inetd and a low-resource condition, though just what that condition is it's hard to fathom since different people report different symptoms. To cite my ISP friend as an example, the errors started to occur most frequently when they lost a 2nd disk and the amount of available swap space decreased by half, then the problems started happening very frequently (and they run many web servers + some large perl5 CGI scripts there). Others, like yourself, report that it's not swap related at all. Gah. What to do?! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 18:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26443 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 18:54:00 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26387 for ; Fri, 18 Sep 1998 18:53:48 -0700 (PDT) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4019.ime.net [209.90.195.29]) by Loki.orland.u91.k12.me.us (8.8.8/8.8.8) with SMTP id VAA03120; Fri, 18 Sep 1998 21:53:04 -0400 (EDT) (envelope-from netmonger@genesis.ispace.com) Message-Id: <199809190153.VAA03120@Loki.orland.u91.k12.me.us> X-Server-Comment: Sent via OCSNet/Orland, Admin is: Droobie@Onenetwork.orland.me.us X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.52 (Beta) Date: Fri, 18 Sep 1998 21:49:52 -0400 To: "Mike Mitchell" , "FreeBSD Hackers List" From: Drew Baxter Subject: Re: query: www.freebsd.org down? In-Reply-To: <000201bde348$2ec3b450$80ab2e81@mmitchel-nt.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been pretty sluggish lately for me. Aim for a mirror, maybe you'll have better luck. At 02:06 PM 9/18/98 -0700, Mike Mitchell wrote: >I have been attempting to grab some driver information from www.freebsd.org >and am having little luck. Is it down today? > >Thank you for your time and effort. > >Mike Mitchell > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 19:24:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00543 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 19:24:23 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00538 for ; Fri, 18 Sep 1998 19:24:21 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id VAA13353 for ; Fri, 18 Sep 1998 21:23:57 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.8.8/8.7.3) id VAA05466 for hackers@freebsd.org; Fri, 18 Sep 1998 21:23:57 -0500 (CDT) Message-ID: <19980918212357.L656@cs.rice.edu> Date: Fri, 18 Sep 1998 21:23:57 -0500 From: Alan Cox To: hackers@FreeBSD.ORG Subject: Re: GDB modifies shared libraries? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take a look at revision 1.24 of procfs_mem.c and some related changes in vm_map.c. None of these fixes were ever applied to -stable. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 20:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09647 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 20:27:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-85.joh.za.ibm.net [139.92.122.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09632 for ; Fri, 18 Sep 1998 20:27:12 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id FAA12252; Sat, 19 Sep 1998 05:24:20 +0200 (SAT) From: Robert Nordier Message-Id: <199809190324.FAA12252@ceia.nordier.com> Subject: Re: PC memory usage (what is PIC?) In-Reply-To: from Charles Youse at "Sep 18, 98 06:53:50 pm" To: cyouse@artemis.syncom.net (Charles Youse) Date: Sat, 19 Sep 1998 05:24:18 +0200 (SAT) Cc: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Charles Youse wrote: > On Fri, 18 Sep 1998, zhihuizhang wrote: > > > Since it has been linked for another (high) address, it will have to > > execute PIC until the page table and page directory stuff is setup > > properly, at which point paging will be enabled and the kernel will > > finally run at the address for which it was linked. > > > > Can anyone explain to me what is PIC and the two different linked > > addresses mentioned here? In the standard i386 kernel, the first few hundred bytes of startup code execute at 0x100000 before the virtual address changes to 0xf0100000 (though the code remains at the same physical location). > > PIC refers to Position-Independent Code, which requires that all > references to memory be relative to the IP register. Code written in > this way will execute correctly no matter where it is loaded into the > address space. Actually, calling the kernel startup code PIC is a merely a convenient distortion of the truth, at least as far as the i386 FreeBSD kernel startup is concerned. Writing truly IP-independent i386 assembly code by hand (and the initial portion is pure assembly code), requires completely unnatural practices. > Because the kernel is linked to run at a different address than it's > loaded, references to absolute addresses will fetch invalid data from > a [nonexistent] random memory location. The solution is to restrict > the kernel to PIC (which has no such absolute references) until the > vm subsystem is initialized to redirect those absolute [virtual] > addresses to the proper physical addresses. The actual i386 solution is to pre-bias each actual absolute address reference in the initial startup section. This macros is used: #define R(foo) ((foo)-KERNBASE) The resultant code is not really position-independent in any sense, but it is correct for its execution address. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 21:04:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12756 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 21:04:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from vespucci.advicom.net (vespucci.advicom.net [199.170.120.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12751 for ; Fri, 18 Sep 1998 21:04:16 -0700 (PDT) (envelope-from avalon@vespucci.advicom.net) Received: from localhost (avalon@localhost) by vespucci.advicom.net (8.8.8/8.8.5) with SMTP id XAA12451; Fri, 18 Sep 1998 23:03:35 -0500 (CDT) X-Envelope-Recipient: hackers@FreeBSD.ORG Date: Fri, 18 Sep 1998 23:03:35 -0500 (CDT) From: Avalon Books To: Leo Papandreou cc: hackers@FreeBSD.ORG Subject: Re: Unified Unix (c) Intel? In-Reply-To: <19980918032618.47449@talcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Sep 1998, Leo Papandreou wrote: > > Comments? How can/will/might this affect FreeBSD development? > > There can be but one winner. The time is ripe for FreeBSD to ally > itself with Microsoft. > Ew..... Glad I haven't eaten anything before reading that... --Rick Pelletier Sys Admin, House Galiagante Quietly Fighting the Micro$oft Sub-Standard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 21:58:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17344 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 21:58:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from SetiDude.com (dnas-01-40.sat.idworld.net [209.142.68.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17332 for ; Fri, 18 Sep 1998 21:58:01 -0700 (PDT) (envelope-from john01@idworld.net) Received: from idworld.net (localhost [127.0.0.1]) by SetiDude.com (8.8.8/8.8.8) with ESMTP id XAA00753 for ; Fri, 18 Sep 1998 23:57:04 -0500 (CDT) (envelope-from john01@idworld.net) Message-ID: <3603399F.4132346C@idworld.net> Date: Fri, 18 Sep 1998 23:57:04 -0500 From: john garcia X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: device drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been using FreeBSD for about 3 month now and I am now a FreeBSD advocate. I was wondering where I can get some information on writing device drivers for FreeBSD? Are there any newsgroups or web sites where I can learn more? I was also wondering if there are any good books out there covering the topic? any help would be great. John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 18 23:54:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02577 for freebsd-hackers-outgoing; Fri, 18 Sep 1998 23:54:07 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from babylon.wsc.monash.edu.au (babylon.wsc.monash.edu.au [130.194.166.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02571 for ; Fri, 18 Sep 1998 23:54:03 -0700 (PDT) (envelope-from graeme@babylon.wsc.monash.edu.au) Received: from localhost (graeme@localhost) by babylon.wsc.monash.edu.au (8.8.8/8.8.8) with SMTP id QAA31932; Sat, 19 Sep 1998 16:53:32 +1000 Date: Sat, 19 Sep 1998 16:53:32 +1000 (EST) From: Graeme Cross Reply-To: Graeme.Cross@sci.monash.edu.au To: john garcia cc: freebsd-hackers@FreeBSD.ORG Subject: Re: device drivers In-Reply-To: <3603399F.4132346C@idworld.net> Message-ID: X-Attribution: gjc X-PGP-Key-ID: 702DB549 X-URL: http://www.wsc.monash.edu.au/~graeme/ 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, 18 Sep 1998, john garcia wrote: > I have been using FreeBSD for about 3 month now and I > am now a FreeBSD advocate. I was wondering where I can get some > information on writing device drivers for FreeBSD? Are there any > newsgroups or web sites where I can learn more? I was also wondering > if there are any good books out there covering the topic? > any help would be great. > There is a device driver tutorial at: http://www.freebsd.org/tutorials/ddwg/ddwg.html Cheers Graeme -- Graeme Cross -- Water Studies Centre, Monash University Random thought #149 (Collect all 229) f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 00:45:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07370 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 00:45:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07365 for ; Sat, 19 Sep 1998 00:45:19 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA19578; Sat, 19 Sep 1998 00:44:54 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd019558; Sat Sep 19 00:44:47 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA18882; Sat, 19 Sep 1998 00:44:43 -0700 (MST) From: Terry Lambert Message-Id: <199809190744.AAA18882@usr08.primenet.com> Subject: Re: FreeBSD hanging/rebooting To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 19 Sep 1998 07:44:43 +0000 (GMT) Cc: gram@cdsec.com, bright@hotjobs.com, hackers@FreeBSD.ORG In-Reply-To: <4139.906167609@time.cdrom.com> from "Jordan K. Hubbard" at Sep 18, 98 06:13:29 pm X-Mailer: ELM [version 2.4 PL25] 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 > > We have been basing our firewall on 2.2.2 since about a month after > > it was released. We have a reasonably large number of firewalls installed, > > The problem is occurring on about 4 of them, which have been handling > > increasing loads over time. All of them have been running for at least six > > months (previously on FreeBSD 2.1.6). > > > > Two have 32Mb RAM, and two have 64Mb. The swap space in each is calculated > > as (16Mb + 2 x physical). > > If it's any consolation, I have seen this problem at a local ISP > friend whom I help out from time to time and I'm no closer to fixing > it either. It seems to be a combination of some bogus code in inetd > and a low-resource condition, though just what that condition is it's > hard to fathom since different people report different symptoms. To > cite my ISP friend as an example, the errors started to occur most > frequently when they lost a 2nd disk and the amount of available > swap space decreased by half, then the problems started happening > very frequently (and they run many web servers + some large perl5 > CGI scripts there). Others, like yourself, report that it's not swap > related at all. Gah. What to do?! This may be unrelated, but is there a logged firewall "reject" that occurs immediately before the reboot? There was a well known problem with the ip firewall code that resulted in a kernel stack corruption, since a stack buffer was used as an argument to an explicit reject send, and the stack went out of scope before the reject was serviced, resulting in a curruption of a kernel stack with (basically) the remote IP address (among other data). Archie Cobb fixed this a while back, but you may have stale code? It was most frequently triggered (for us) by rejects of RIP packets from ISP's who erroneously configured their dialin network with RIP enabled (a silly thing to do, for a lot of reasons). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 01:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11088 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 01:19:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11080 for ; Sat, 19 Sep 1998 01:19:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id BAA15507; Sat, 19 Sep 1998 01:19:33 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: gram@cdsec.com, bright@hotjobs.com, hackers@FreeBSD.ORG Subject: Re: FreeBSD hanging/rebooting In-reply-to: Your message of "Sat, 19 Sep 1998 07:44:43 -0000." <199809190744.AAA18882@usr08.primenet.com> Date: Sat, 19 Sep 1998 01:19:33 -0700 Message-ID: <15503.906193173@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This may be unrelated, but is there a logged firewall "reject" that > occurs immediately before the reboot? Unrelated. No firewall present at all in this scenario. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 03:43:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20609 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 03:43:09 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20604 for ; Sat, 19 Sep 1998 03:43:06 -0700 (PDT) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.8.8/8.8.7) id LAA08891 for freebsd-hackers@freebsd.org; Sat, 19 Sep 1998 11:23:44 GMT (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <199809191123.LAA08891@mauibuilt.com> Subject: Help with Digiboard 16em To: freebsd-hackers@FreeBSD.ORG Date: Sat, 19 Sep 1998 11:23:44 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need help getting a Digiboard 16em working.. I have been following mailing lists as best I can but with no results.. I get this error while booting which suggests a hardware problem.. but according to some old posts in the lists Im not alone is there a fix for this now?? dgb0: PC/Xi 512K dgb0 at 0x224-0x227 maddr 0xfc0000 msize 524288 flags 0x2 on isa dgb0: 2nd reset failed I have the Digiboard pluged into the EBI unit and a modem on port wone I am trying to talk to the modem using cu -s 9600 -l /dev/cuaD00 and get.. /root 102% cu -s 9600 -l /dev/cuaD00 cu: open (/dev/cuaD00): Device not configured cu: /dev/cuaD00: Line in use am I doing this part correct?? Thanks in advance for the help.. Richard Puga puga@mauibuilt.com freebsd@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 13:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16310 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 13:07:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16281 for ; Sat, 19 Sep 1998 13:07:08 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id QAA25790 for ; Sat, 19 Sep 1998 16:06:40 -0400 (EDT) Date: Sat, 19 Sep 1998 16:06:39 -0400 (EDT) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: Question about wiring a page 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 read in vm_map_lookup() the following comment: /* * If this page is not pageable, we have to get it for all possible * accesses. */ Does this mean that even if the map entry is specified as wired, the pages in its range still have to be faulted in for the very first time? Another question: Can any process wire a page at its own will? There must be some regulations, otherwise anyone can hog the memory. Any help is appreciated. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 17:40:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28954 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 17:40:53 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from indigo.ie (ts05-026.dublin.indigo.ie [194.125.220.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28771; Sat, 19 Sep 1998 17:39:36 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id BAA05064; Sun, 20 Sep 1998 01:32:23 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199809200032.BAA05064@indigo.ie> Date: Sun, 20 Sep 1998 01:32:23 +0000 In-Reply-To: <199809180311.UAA00693@usr04.primenet.com>; Terry Lambert Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Terry Lambert , rotel@indigo.ie Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets Cc: sthaug@nethelp.no, hackers@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 18, 3:11am, Terry Lambert wrote: } Subject: Re: problem using 3 x znyx314 cards for 12 de ethernets > > These are different issues, someone can be partly responsible for > > a smurf attack without ever realising it and (more importantly) > > without _their_ security/quality of service being compromised. I > > don't care how many boxes get hacked as long as they aren't mine, > > but it's reasonable to complain about a configuration which makes > > it too easy for script kiddies to exploit the ineptitude or > > carelessness of admins to affect _other_ competant and careful > > admins boxes. > > > > It's akin to shipping sendmail with open relaying. > > If you want a C2 hardened system, quit pussyfooting around and start > addressing the real issues leading up to C2 certification. I'm not familiar with the orange book in any detail but suspect C2 hardening would be of little more use than providing a checkbox in a feature list; seeing C2 Solaris rooted by a standard exploit doesn't exactly engender confidence in the level of real-world security required for certification. > Otherwise, > griping about something that will never happen given a correctly > configured firewall, and which "fixing" will break a behaviour that > is universally known to be useful, seems a bit counter-productive. Its unfortunate that useful and well-known features are often both insecure and acheiveable through secure means. :) How about a compromise - no replies to broadcast ping's from outside the hosts subnet by default? Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 18:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03634 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 18:17:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03629 for ; Sat, 19 Sep 1998 18:17:14 -0700 (PDT) (envelope-from easmith@beatrice.rutgers.edu) Received: (from easmith@localhost) by beatrice.rutgers.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) id VAA18729; Sat, 19 Sep 1998 21:15:59 -0400 (EDT) From: "Allen Smith" Message-Id: <9809192115.ZM18727@beatrice.rutgers.edu> Date: Sat, 19 Sep 1998 21:15:59 -0400 In-Reply-To: Luigi Rizzo "Re: Packet/traffic shapper ?" (Sep 12, 9:46pm) References: <199809121124.NAA20742@labinfo.iet.unipi.it> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Luigi Rizzo , kev@lab321.ru (Eugeny Kuzakov) Subject: Re: Packet/traffic shapper ? Cc: mike@smith.net.au, hackers@FreeBSD.ORG, ipfilter@postbox.anu.edu.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 12, 9:46pm, Luigi Rizzo (possibly) wrote: > shouldn't take too much to patch ipfilter to return a different action > than pass/drop and thus cause packets to be passed through the > bw limiter. I've taken a look at getting ALTQ and ipfilter to work together. However, the most obvious way to get ipfilter to interface with ALTQ (namely, having ipfilter figure out under which ALTQ class packets should go, so that you're not examining the packets twice) unfortunately has the problem that the ALTQ classes are only distinguished via a human-comprehensible form (numbering) until they go into the kernel; they're then no longer numbered. Otherwise, you could just have an ipfilter action to put them into the appropriate class via an added mbuf field or whatever. -Allen -- Allen Smith easmith@beatrice.rutgers.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 18:26:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04354 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 18:26:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04343 for ; Sat, 19 Sep 1998 18:26:39 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id SAA00387; Sat, 19 Sep 1998 18:26:02 -0700 (PDT) (envelope-from jdp) Message-Id: <199809200126.SAA00387@austin.polstra.com> To: alc@cs.rice.edu Subject: Re: GDB modifies shared libraries? In-Reply-To: <19980918212357.L656@cs.rice.edu> References: <19980918212357.L656@cs.rice.edu> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Sat, 19 Sep 1998 18:26:02 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980918212357.L656@cs.rice.edu>, Alan Cox wrote: > Take a look at revision 1.24 of procfs_mem.c and some related > changes in vm_map.c. None of these fixes were ever applied > to -stable. Yes, I found the changes you're talking about. I was able to merge them into -stable without much trouble. I'm running them now, and they seem to fix the problem. I'll test some more and commit the fix to the -stable branch if I don't find any problems with it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 19 22:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25866 for freebsd-hackers-outgoing; Sat, 19 Sep 1998 22:29:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25861 for ; Sat, 19 Sep 1998 22:29:54 -0700 (PDT) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.44]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with ESMTP id AAA15619 for ; Sun, 20 Sep 1998 00:32:28 +0500 Message-ID: <360491FA.3BEA2BE6@bachue.usc.unal.edu.co> Date: Sun, 20 Sep 1998 00:26:18 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: More on the Intel-UNIX standard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm concerned about the SNR in hackers, but I just couldn't resist asking if someone was aware and acting on this http://www.sco.com/udi/ It will be ported for Linux and distributed as freeware, as far as SCO knows... Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message