From owner-freebsd-hackers Sun Sep 10 2:40:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.ovis.net (ns1.ovis.net [207.0.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 6026837B422; Sun, 10 Sep 2000 02:40:19 -0700 (PDT) Received: from 207.0.147.112 (s46.pm5.ovis.net [207.0.147.112]) by ns1.ovis.net (8.9.3/8.9.3) with SMTP id FAA17867; Sun, 10 Sep 2000 05:39:17 -0400 Message-Id: <200009100939.FAA17867@ns1.ovis.net> Reply-To: chromexa From: chromexa@ovis.net To: Majordomo@FreeBSD.ORG, hackers@FreeBSD.ORG Cc: Subject: re: Majordomo results: unsubscribe freebsd-hackers user reecetl Date: 10 Sep 2000 05:47:52 -0500 X-Mailer: NeoPlanet Version: 5.1.0.1531 X-ID: 3BEB18605EB911D3BC29444553540000 X-Brand: NeoPlanet X-Build: 1531 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ** Original Subject: Majordomo results: unsubscribe freebsd-hackers user reecetl > ** Original Sender: Majordomo@FreeBSD.ORG > ** Original Date: Sat, 9 Sep 2000 16:33:44 -0400 > ** Original Message follows... > > -- > > >>>> unsubscribe freebsd-hackers user reecetl@marforlant.usmc.mil > **** The address you supplied, user reecetl@marforlant.usmc.mil > **** does not seem to be a legal Internet address. You may have supplied > **** your full name instead of your address, or you may have included your > **** name along with your address in a manner that does not comply with > **** Internet standards for addresses. > **** It is also possible that you are using a mailer that wraps long lines > **** and the end of your request ended up on the following line. If the > **** latter is true, try using backslashes to split long lines. (Split the > **** line between words, then put a backslash at the end of all but the > **** last line.) > > **** unsubscribe: invalid address 'user reecetl@marforlant.usmc.mil' > >>>> > >>>> > >>>> freebsd-hackers-digest Saturday, September 9 2000 Volume 04 : Number 943 > **** Command 'freebsd-hackers-digest' not recognized. > >>>> > >>>> > >>>> > >>>> In this issue: > **** Command 'in' not recognized. > >>>> Vinum RAID-5 performance problem > **** Command 'vinum' not recognized. > >>>> Re: How to stop problems from printf > **** Command 're:' not recognized. > >>>> Re: How to stop problems from printf > **** Command 're:' not recognized. > >>>> Re: md5 in boot loader > **** Command 're:' not recognized. > >>>> Re: Creating a list of newbus devices. > **** Command 're:' not recognized. > >>>> Re: Vinum RAID-5 performance problem > **** Command 're:' not recognized. > >>>> Re: Shared Memory Issues > **** Command 're:' not recognized. > >>>> Re: makecontext & friends ? > **** Command 're:' not recognized. > >>>> Re: Vinum RAID-5 performance problem > **** Command 're:' not recognized. > >>>> RE: Vinum RAID-5 performance problem > **** Command 're:' not recognized. > >>>> Re: makecontext & friends ? > **** Command 're:' not recognized. > >>>> Re: makecontext() & friends ? > **** Command 're:' not recognized. > >>>> Re: makecontext & friends ? > **** Command 're:' not recognized. > >>>> Re: Token Ring ?? > **** Command 're:' not recognized. > >>>> > >>>> ---------------------------------------------------------------------- > END OF COMMANDS > **** Help for Majordomo@FreeBSD.ORG: > > > This help message is being sent to you from the Majordomo mailing list > management system at Majordomo@FreeBSD.ORG. > > This is version 1.94.4 of Majordomo. > > If you're familiar with mail servers, an advanced user's summary of > Majordomo's commands appears at the end of this message. > > Majordomo is an automated system which allows users to subscribe > and unsubscribe to mailing lists, and to retrieve files from list > archives. > > You can interact with the Majordomo software by sending it commands > in the body of mail messages addressed to "Majordomo@FreeBSD.ORG". > Please do not put your commands on the subject line; Majordomo does > not process commands in the subject line. > > You may put multiple Majordomo commands in the same mail message. > Put each command on a line by itself. > > If you use a "signature block" at the end of your mail, Majordomo may > mistakenly believe each line of your message is a command; you will > then receive spurious error messages. To keep this from happening, > either put a line starting with a hyphen ("-") before your signature, > or put a line with just the word > > end > > on it in the same place. This will stop the Majordomo software from > processing your signature as bad commands. > > Here are some of the things you can do using Majordomo: > > I. FINDING OUT WHICH LISTS ARE ON THIS SYSTEM > > To get a list of publicly-available mailing lists on this system, put the > following line in the body of your mail message to Majordomo@FreeBSD.ORG: > > lists > > Each line will contain the name of a mailing list and a brief description > of the list. > > To get more information about a particular list, use the "info" command, > supplying the name of the list. For example, if the name of the list > about which you wish information is "demo-list", you would put the line > > info demo-list > > in the body of the mail message. > > II. SUBSCRIBING TO A LIST > > Once you've determined that you wish to subscribe to one or more lists on > this system, you can send commands to Majordomo to have it add you to the > list, so you can begin receiving mailings. > > To receive list mail at the address from which you're sending your mail, > simply say "subscribe" followed by the list's name: > > subscribe demo-list > > If for some reason you wish to have the mailings go to a different address > (a friend's address, a specific other system on which you have an account, > or an address which is more correct than the one that automatically appears > in the "From:" header on the mail you send), you would add that address to > the command. For instance, if you're sending a request from your work > account, but wish to receive "demo-list" mail at your personal account > (for which we will use "jqpublic@my-isp.com" as an example), you'd put > the line > > subscribe demo-list jqpublic@my-isp.com > > in the mail message body. > > Based on configuration decisions made by the list owners, you may be added > to the mailing list automatically. You may also receive notification > that an authorization key is required for subscription. Another message > will be sent to the address to be subscribed (which may or may not be the > same as yours) containing the key, and directing the user to send a > command found in that message back to Majordomo@FreeBSD.ORG. (This can be > a bit of extra hassle, but it helps keep you from being swamped in extra > email by someone who forged requests from your address.) You may also > get a message that your subscription is being forwarded to the list owner > for approval; some lists have waiting lists, or policies about who may > subscribe. If your request is forwarded for approval, the list owner > should contact you soon after your request. > > Upon subscribing, you should receive an introductory message, containing > list policies and features. Save this message for future reference; it > will also contain exact directions for unsubscribing. If you lose the > intro mail and would like another copy of the policies, send this message > to Majordomo@FreeBSD.ORG: > > intro demo-list > > (substituting, of course, the real name of your list for "demo-list"). > > III. UNSUBSCRIBING FROM MAILING LISTS > > Your original intro message contains the exact command which should be > used to remove your address from the list. However, in most cases, you > may simply send the command "unsubscribe" followed by the list name: > > unsubscribe demo-list > > (This command may fail if your provider has changed the way your > address is shown in your mail.) > > To remove an address other than the one from which you're sending > the request, give that address in the command: > > unsubscribe demo-list jqpublic@my-isp.com > > In either of these cases, you can tell Majordomo@FreeBSD.ORG to remove > the address in question from all lists on this server by using "*" > in place of the list name: > > unsubscribe * > unsubscribe * jqpublic@my-isp.com > > IV. FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED > > To find the lists to which your address is subscribed, send this command > in the body of a mail message to Majordomo@FreeBSD.ORG: > > which > > You can look for other addresses, or parts of an address, by specifying > the text for which Majordomo should search. For instance, to find which > users at my-isp.com are subscribed to which lists, you might send the > command > > which my-isp.com > > Note that many list owners completely or fully disable the "which" > command, considering it a privacy violation. > > V. FINDING OUT WHO'S SUBSCRIBED TO A LIST > > To get a list of the addresses on a particular list, you may use the > "who" command, followed by the name of the list: > > who demo-list > > Note that many list owners allow only a list's subscribers to use the > "who" command, or disable it completely, believing it to be a privacy > violation. > > VI. RETRIEVING FILES FROM A LIST'S ARCHIVES > > Many list owners keep archives of files associated with a list. These > may include: > - back issues of the list > - help files, user profiles, and other documents associated with the list > - daily, monthly, or yearly archives for the list > > To find out if a list has any files associated with it, use the "index" > command: > > index demo-list > > If you see files in which you're interested, you may retrieve them by > using the "get" command and specifying the list name and archive filename. > For instance, to retrieve the files called "profile.form" (presumably a > form to fill out with your profile) and "demo-list.9611" (presumably the > messages posted to the list in November 1996), you would put the lines > > get demo-list profile.form > get demo-list demo-list.9611 > > in your mail to Majordomo@FreeBSD.ORG. > > VII. GETTING MORE HELP > > To contact a human site manager, send mail to postmaster@FreeBSD.ORG. > > To get another copy of this help message, send mail to Majordomo@FreeBSD.ORG > with a line saying > > help > > in the message body. > > VIII. COMMAND SUMMARY FOR ADVANCED USERS > > In the description below items contained in []'s are optional. When > providing the item, do not include the []'s around it. Items in angle > brackets, such as
, are meta-symbols that should be replaced > by appropriate text without the angle brackets. > > It understands the following commands: > > subscribe [
] > Subscribe yourself (or
if specified) to the named . > > unsubscribe [
] > Unsubscribe yourself (or
if specified) from the named . > "unsubscribe *" will remove you (or
) from all lists. This > _may not_ work if you have subscribed using multiple addresses. > > get > Get a file related to . > > index > Return an index of files you can "get" for . > > which [
] > Find out which lists you (or
if specified) are on. > > who > Find out who is on the named . > > info > Retrieve the general introductory information for the named . > > intro > Retrieve the introductory message sent to new users. Non-subscribers > may not be able to retrieve this. > > lists > Show the lists served by this Majordomo server. > > help > Retrieve this message. > > end > Stop processing commands (useful if your mailer adds a signature). > > Commands should be sent in the body of an email message to > "Majordomo@FreeBSD.ORG". Multiple commands can be processed provided > each occurs on a separate line. > > Commands in the "Subject:" line are NOT processed. > > If you have any questions or problems, please contact > "Majordomo-Owner@FreeBSD.ORG". > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message >** --------- End Original Message ----------- ** > I never subescribed thisperson can some Majordomo hacker explain how thisone happened. I am subscribed and gladtobe sobut don't go around subscribing otherpeople. Have Fun, Sends STeve Download NeoPlanet at http://www.neoplanet.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 10 9:46:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mir.kapi.net (mir.kapi.net [195.165.21.13]) by hub.freebsd.org (Postfix) with ESMTP id 7376237B424 for ; Sun, 10 Sep 2000 09:46:07 -0700 (PDT) Received: from kapi.net (kapi.net [195.165.21.10]) by mir.kapi.net (8.9.3/8.9.3) with ESMTP id TAA77481 for ; Sun, 10 Sep 2000 19:46:05 +0300 (EEST) (envelope-from esko@kapi.net) Received: from localhost (esko@localhost) by kapi.net (8.9.2/8.9.3) with ESMTP id TAA19306 for ; Sun, 10 Sep 2000 19:46:05 +0300 (EEST) (envelope-from esko@kapi.net) X-Authentication-Warning: kapi.net: esko owned process doing -bs Date: Sun, 10 Sep 2000 19:46:05 +0300 (EEST) From: Esko Petteri Matinsola X-Sender: esko@sputnik To: hackers@FreeBSD.ORG Subject: Re: Vinum RAID-5 performance problem In-Reply-To: <20000909113319.E5876@wantadilla.lemis.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 Sat, 9 Sep 2000, Greg Lehey wrote: > On Friday, 8 September 2000 at 22:24:51 +0300, Esko Petteri Matinsola wrote: > > Please don't use bonnie. It's not measuring what you think it is. OK, I used rawio as you suggested. > I don't know how you'd find anything at vinumvm.org which tells you > what to expect from bonnie. No I did not. I found that I should be expecting about 25% of the write performance of striping than with raid5. > Well, using master and slave together isn't fine in my book. I ordered additional IDE-card three weeks ago, but haven't recieved it so I thought I should get started with these two on the motherboard. So, I tested with rawio. Here's rawio -a -p 8 /dev/ad0e: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec ad0e 1355.1 85 5335.0 326 1530.4 95 6416.9 392 With the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 sd length 512m drive drive2 sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid0 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid0 3593.0 221 17807.7 1087 11551.0 711 17503.5 1068 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid10 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 plex org striped 256k sd length 512m drive drive2 sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid10 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid10 3727.4 230 20024.5 1222 5727.5 358 10073.2 615 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid5 plex org raid5 256k sd length 512m drive drive0 sd length 512m drive drive1 sd length 512m drive drive2 sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid5 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid5 3569.9 221 19001.7 1160 1169.8 73 1105.1 67 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 # sd length 512m drive drive1 sd length 512m drive drive2 # sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid0 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid0 3756.6 233 16859.6 1029 5972.7 368 17213.3 1051 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 # sd length 512m drive drive2 # sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid0 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid0 3756.6 233 16859.6 1029 5972.7 368 17213.3 1051 So, is this just what I should get or is there something I could do to that raid5 write performance ? Based on these figures, it's nowhere near 25% what I expect. I expect to get somewhat better performance when I get that IDE-card when I can put every drive as master on its own channel. Please comment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 10 9:48:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id BDC6637B423 for ; Sun, 10 Sep 2000 09:48:31 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YAHN-0002GV-00 for freebsd-hackers@freebsd.org; Sun, 10 Sep 2000 19:48:29 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YAHL-0004cL-00 for freebsd-hackers@freebsd.org; Sun, 10 Sep 2000 19:48:27 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@freebsd.org Subject: diskless workstation Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Sep 2000 19:48:27 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i spent some time trying out diskless ws, using dhcp/pxe/tftp. now im stuck after loadin the kernel - via nfs - and not finding the root i tried putting 'host:/something/root/bar / nfs rw 0 0' in its fstab, and the error i get is something like: bar device not found. what magic am i missing? BTW, is someone working in passing all this stuff via dhcp? im trying to come up with an almost zero admin diskless ws solution. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 10 12:53:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 8585737B423; Sun, 10 Sep 2000 12:53:39 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA09717; Sun, 10 Sep 2000 12:53:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009101953.MAA09717@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Cc: hardware@freebsd.org Subject: New 'aac' driver version supports Dell onboard RAID Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Sep 2000 12:53:00 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quick note to let people know that the latest BETA version of the 'aac' driver at http://people.freebsd.org/~msmith/RAID/index.html#adaptec now includes support for the onboard RAID controller found in the Dell PowerEdge 2400, 2450 and 4400 server systems. There've also been a few bugfixes and a number of improvements in the name of supporting the as-yet unreleased management utilities. With some more cleaning up, the driver is almost ready to be committed to -current. Feedback would be greatly appreciated. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 10 13: 7:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 8495F37B423 for ; Sun, 10 Sep 2000 13:07:35 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 10 Sep 2000 15:09:21 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8AK7QX19483; Sun, 10 Sep 2000 15:07:27 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1] (may be forged)) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8AK7KG15668; Sun, 10 Sep 2000 15:07:20 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009102007.e8AK7KG15668@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: Adam , hackers@FreeBSD.ORG Subject: Re: What's the best PCMCIA Ethernet card? In-Reply-To: Message from Kenneth Wayne Culver of "Sun, 10 Sep 2000 01:40:25 EDT." Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Sep 2000 15:07:20 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hi, I'd just like to say that I dont think non cardbus cards are capable > > of doing more than 10bt speeds even if it talks 100bt. I have not met one > > that did and I assume it is a limit of the pcmcia design. Just warning > > you not to waste your money on one if you get near 10bt speeds already. > > My main reason for wanting to replace the wretched thing is that it keeps on hanging when doing lots of writes under NFS (when it's a client), even when the write size is reduced to 2k. Everyone's currently banging away at the new SMP code, so rather than plague Bill Paul with requests about the if_sn driver, I'm thinking of just getting a more reliable card. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 10 15:56:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (Postfix) with ESMTP id 1838F37B422 for ; Sun, 10 Sep 2000 15:56:39 -0700 (PDT) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.9.3/8.9.3) id XAA00953; Sun, 10 Sep 2000 23:53:44 +0100 (BST) (envelope-from rjs) Date: Sun, 10 Sep 2000 23:53:44 +0100 (BST) Message-Id: <200009102253.XAA00953@fdy2.demon.co.uk> From: Robert Swindells To: shocking@houston.rr.com Cc: hackers@freebsd.org In-reply-to: <200009102007.e8AK7KG15668@bloop.craftncomp.com> (message from Stephen Hocking on Sun, 10 Sep 2000 15:07:20 -0500) Subject: Re: What's the best PCMCIA Ethernet card? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > Hi, I'd just like to say that I dont think non cardbus cards are capable >> > of doing more than 10bt speeds even if it talks 100bt. I have not met one >> > that did and I assume it is a limit of the pcmcia design. Just warning >> > you not to waste your money on one if you get near 10bt speeds already. >> > >My main reason for wanting to replace the wretched thing is that it >keeps on hanging when doing lots of writes under NFS (when it's a >client), even when the write size is reduced to 2k. Everyone's >currently banging away at the new SMP code, so rather than plague Bill >Paul with requests about the if_sn driver, I'm thinking of just >getting a more reliable card. I have had about 2MB/sec out of a Netgear FX410. This is a NE2000 clone that is supported by if_ed under 4-STABLE. This was under NT though not FreeBSD since I'm still running 3.5-STABLE on my laptop. Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 10 21:40:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.kyx.net (cr95838-b.crdva1.bc.wave.home.com [24.113.50.147]) by hub.freebsd.org (Postfix) with ESMTP id 99F2B37B424 for ; Sun, 10 Sep 2000 21:40:29 -0700 (PDT) Received: from smp.kyx.net (unknown [10.22.22.45]) by mail.kyx.net (Postfix) with SMTP id 257021DC03; Sun, 10 Sep 2000 21:40:00 -0700 (PDT) From: Dragos Ruiu Organization: kyx.net To: shocking@houston.rr.com, Stephen Hocking , Kenneth Wayne Culver Subject: Re: What's the best PCMCIA Ethernet card? Date: Sun, 10 Sep 2000 21:36:49 -0700 X-Mailer: KYX-CP/M [version core00-mail-92] Content-Type: text/plain Cc: Adam , hackers@FreeBSD.ORG References: <200009102007.e8AK7KG15668@bloop.craftncomp.com> In-Reply-To: <200009102007.e8AK7KG15668@bloop.craftncomp.com> MIME-Version: 1.0 Message-Id: <00091021403114.41956@smp.kyx.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, Stephen Hocking wrote: > > > > > Hi, I'd just like to say that I dont think non cardbus cards are capable > > > of doing more than 10bt speeds even if it talks 100bt. I have not met one > > > that did and I assume it is a limit of the pcmcia design. Just warning > > > you not to waste your money on one if you get near 10bt speeds already. > > > Benchmarked.... Host laptop, Sharp Acius A100 233 MMX, OS Linux Two cards same type/mfgr, cardbus and non-cardbus (linksys EtherFast): -Non Cardbus: 16Mbps transfer rate -Cardbus: 32Mbps transfer rate ymmv, --dr -- dursec.com ltd. / kyx.net - we're from the future pgp fingerprint: 18C7 E37C 2F94 E251 F18E B7DC 2B71 A73E D2E8 A56D pgp key: http://www.dursec.com/drkey.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 1:22:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id D378F37B423 for ; Mon, 11 Sep 2000 01:21:08 -0700 (PDT) Received: (qmail 80345 invoked by uid 1001); 11 Sep 2000 08:18:03 -0000 Date: Mon, 11 Sep 2000 11:18:03 +0300 From: Peter Pentchev To: Danny Braniss Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation Message-ID: <20000911111803.A80232@ringwraith.office1.bg> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from danny@cs.huji.ac.il on Sun, Sep 10, 2000 at 07:48:27PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following excerpt from isc-dhcp3-3.0.b1.17's dhcpd.conf works for me: subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.193 192.168.1.208; filename "/tftpboot/ringnet.kernel.fd0"; option root-path "192.168.1.2:/usr/n/ringrowl/root"; host ringrowl { hardware ethernet 00:01:02:ab:50:67; fixed-address 192.168.1.66; } host ringcrawl { hardware ethernet 00:01:02:1c:7d:ef; fixed-address 192.168.1.67; } } This specifies the same root path for all diskless stations - the rest is left to the rc.diskless* scripts, which look for config files in /conf/their.ip.address/etc/; just place an rc.conf there with overrides over /etc/defaults/rc.conf, and.. ideally, things should work :) Hope that helps :) G'luck, Peter -- This sentence would be seven words long if it were six words shorter. On Sun, Sep 10, 2000 at 07:48:27PM +0300, Danny Braniss wrote: > hi, > i spent some time trying out diskless ws, using dhcp/pxe/tftp. > now im stuck after loadin the kernel - via nfs - and not finding the root > i tried putting 'host:/something/root/bar / nfs rw 0 0' in its fstab, and > the error i get is something like: bar device not found. > what magic am i missing? > > BTW, is someone working in passing all this stuff via dhcp? im trying to come > up with an almost zero admin diskless ws solution. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 3:11: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 228EA37B422 for ; Mon, 11 Sep 2000 03:11:06 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8BAB1N29261; Mon, 11 Sep 2000 12:11:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: awr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Regarding kldunload / open /dev/ panic In-Reply-To: Your message of "Sat, 09 Sep 2000 22:35:56 +0200." Date: Mon, 11 Sep 2000 12:11:01 +0200 Message-ID: <29259.968667061@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , awr writ es: > >Also, shouldn't /usr/src/sys/dev/vn/vn.c use make_dev() and destroy_dev() >calls instead of cdevsw_add()?? Yes :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 5: 6:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id E567737B422 for ; Mon, 11 Sep 2000 05:06:53 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YSMI-0007XD-00 for freebsd-hackers@freebsd.org; Mon, 11 Sep 2000 15:06:46 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YSMH-0005Iu-00 for freebsd-hackers@freebsd.org; Mon, 11 Sep 2000 15:06:45 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@freebsd.org Subject: Re: diskless workstation Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Sep 2000 15:06:45 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, once i compiled a kernel with options BOOTP things got better ;-) it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs) but after it re-configures the ethernet, the ethernet stops working! ponters anyone? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 5:55: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id BFD8E37B422 for ; Mon, 11 Sep 2000 05:54:55 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YT6p-0000M6-00; Mon, 11 Sep 2000 15:54:51 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YT6o-0005Ku-00; Mon, 11 Sep 2000 15:54:50 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: "Koster, K.J." Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation In-reply-to: Your message of Mon, 11 Sep 2000 14:22:00 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Sep 2000 15:54:50 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <59063B5B4D98D311BC0D0001FA7E4522026D787E@l04.research.kpn.com>you w rite: }Are you sure that it's listening on the right media (utp/bnc/aui)? } }There might be a problem where the machine downloads the kernel, boots the }kernel, reprobing the NIC, setting it to a different media. What's the probe }look like? } but it worked!! anyway, the rc.diskless1 does not reconfigure the ethernet - my mistook it hangs sometime later ... } Kees Jan } }================================================= } TV is the worst of both worlds. It's not as } good at words as radio is because the pictures } are a distraction which demand attention, and } it's not as good as cinema because the pictures } are not nearly as good. } Douglas Adams } } }> -----Original Message----- }> From: Danny Braniss [mailto:danny@cs.huji.ac.il] }> Sent: maandag 11 september 2000 13:19 }> To: Koster, K.J. }> Subject: Re: diskless workstation }> }> }> In message }> <59063B5B4D98D311BC0D0001FA7E4522026D787C@l04.research.kpn.com>you w }> rite: }> }Error message? }> } }> }> Interface xl0 IP-Address 132.65.80.251 Broadcast }> 132.65.255.255 (which is ok) }> cp: /conf/default/etc/*: No such file or directory }> (which makes sence since the ether is no longer working) }> some files not found }> and finaly: }> nfs server ....: not responding }> }> danny }> }> } }> }================================================= }> } TV is the worst of both worlds. It's not as }> } good at words as radio is because the pictures }> } are a distraction which demand attention, and }> } it's not as good as cinema because the pictures }> } are not nearly as good. }> } Douglas Adams }> } }> } }> }> -----Original Message----- }> }> From: Danny Braniss [mailto:danny@cs.huji.ac.il] }> }> Sent: maandag 11 september 2000 13:07 }> }> To: freebsd-hackers@FreeBSD.ORG }> }> Subject: Re: diskless workstation }> }> }> }> }> }> ok, once i compiled a kernel with options BOOTP things got }> better ;-) }> }> it worked several times, but now it boots ok, }> }> (pxe->dhcp->tftpboot->nfs) }> }> but after it re-configures the ethernet, the ethernet }> stops working! }> }> }> }> ponters anyone? }> }> > }> danny }> }> }> }> }> }> }> }> }> }> }> }> }> }> 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 Mon Sep 11 7:33:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 454C637B440 for ; Mon, 11 Sep 2000 07:33:46 -0700 (PDT) Received: by gatekeeper.veriohosting.com; Mon, 11 Sep 2000 08:33:27 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma019472; Mon, 11 Sep 00 08:33:06 -0600 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id IAA71025; Mon, 11 Sep 2000 08:33:05 -0600 (MDT) Date: Mon, 11 Sep 2000 08:45:55 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: Robert Swindells Cc: shocking@houston.rr.com, hackers@FreeBSD.ORG Subject: Re: What's the best PCMCIA Ethernet card? In-Reply-To: <200009102253.XAA00953@fdy2.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have had about 2MB/sec out of a Netgear FX410. This is a NE2000 clone > that is supported by if_ed under 4-STABLE. I use a linksys ect2 card and get about the same (it's also an ne2000 clone). Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 7:44:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id CAAE737B424 for ; Mon, 11 Sep 2000 07:44:15 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YUob-0001o1-00 for freebsd-hackers@freebsd.org; Mon, 11 Sep 2000 17:44:09 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13YUoa-0005P8-00 for freebsd-hackers@FreeBSD.ORG; Mon, 11 Sep 2000 17:44:08 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation In-reply-to: Your message of Mon, 11 Sep 2000 15:54:50 +0300 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Sep 2000 17:44:08 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im getting better, answering my own requests :-) long story, short message /usr was not being mounted! now why it worked and suddenly stopped, i don't have a clue. next mile-stone: how do i get hostname set? currently it's null/Amesiac. In message you write: }In message <59063B5B4D98D311BC0D0001FA7E4522026D787E@l04.research.kpn.com>you }w }rite: }}Are you sure that it's listening on the right media (utp/bnc/aui)? }} }}There might be a problem where the machine downloads the kernel, boots the }}kernel, reprobing the NIC, setting it to a different media. What's the probe }}look like? }} } }but it worked!! }anyway, the rc.diskless1 does not reconfigure the ethernet - my mistook }it hangs sometime later ... } }} Kees Jan }} }}================================================= }} TV is the worst of both worlds. It's not as }} good at words as radio is because the pictures }} are a distraction which demand attention, and }} it's not as good as cinema because the pictures }} are not nearly as good. }} Douglas Adams }} }} }}> -----Original Message----- }}> From: Danny Braniss [mailto:danny@cs.huji.ac.il] }}> Sent: maandag 11 september 2000 13:19 }}> To: Koster, K.J. }}> Subject: Re: diskless workstation }}> }}> }}> In message }}> <59063B5B4D98D311BC0D0001FA7E4522026D787C@l04.research.kpn.com>you w }}> rite: }}> }Error message? }}> } }}> }}> Interface xl0 IP-Address 132.65.80.251 Broadcast }}> 132.65.255.255 (which is ok) }}> cp: /conf/default/etc/*: No such file or directory }}> (which makes sence since the ether is no longer working) }}> some files not found }}> and finaly: }}> nfs server ....: not responding }}> }}> danny }}> }}> } }}> }================================================= }}> } TV is the worst of both worlds. It's not as }}> } good at words as radio is because the pictures }}> } are a distraction which demand attention, and }}> } it's not as good as cinema because the pictures }}> } are not nearly as good. }}> } Douglas Adams }}> } }}> } }}> }> -----Original Message----- }}> }> From: Danny Braniss [mailto:danny@cs.huji.ac.il] }}> }> Sent: maandag 11 september 2000 13:07 }}> }> To: freebsd-hackers@FreeBSD.ORG }}> }> Subject: Re: diskless workstation }}> }> }}> }> }}> }> ok, once i compiled a kernel with options BOOTP things got }}> better ;-) }}> }> it worked several times, but now it boots ok, }}> }> (pxe->dhcp->tftpboot->nfs) }}> }> but after it re-configures the ethernet, the ethernet }}> stops working! }}> }> }}> }> ponters anyone? }}> }> }> }> danny }}> }> }}> }> }}> }> }}> }> }}> }> }}> }> }}> }> To Unsubscribe: send mail to majordomo@FreeBSD.org }}> }> with "unsubscribe freebsd-hackers" in the body of the message }}> }> }}> }}> }}> }}> } } } } } } }To Unsubscribe: send mail to majordomo@FreeBSD.org }with "unsubscribe freebsd-hackers" in the body of the message } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 8:14:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from doorman.brann.org (remote-brann-gw.nyc.dsl.access.net [166.84.145.254]) by hub.freebsd.org (Postfix) with ESMTP id 7229A37B42C for ; Mon, 11 Sep 2000 08:14:55 -0700 (PDT) Received: from freebie.brann.org (freebie.brann.org [10.0.0.2]) by doorman.brann.org (8.9.3/8.9.3) with ESMTP id LAA77944; Mon, 11 Sep 2000 11:14:49 -0400 (EDT) (envelope-from john@brann.org) Received: (from john@localhost) by freebie.brann.org (8.9.3/8.9.3) id LAA70731; Mon, 11 Sep 2000 11:14:40 -0400 (EDT) (envelope-from john) Date: Mon, 11 Sep 2000 11:14:40 -0400 From: John Brann To: Mike Nowlin Cc: hackers@freebsd.org Subject: Re: [john: tty behaviour] Message-ID: <20000911111439.A70712@freebie.brann.org> References: <20000907095254.A52345@freebie.brann.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mike@argos.org on Fri, Sep 08, 2000 at 02:04:52AM -0400 Organization: Not while I'm at home X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 08, 2000 at 02:04:52AM -0400, Mike Nowlin wrote: > > > I sent this to questions a couple of weeks ago, but didn't receive any > > helpful replies. Anyone doing this - two machines connected by a null-modem > > cable with the ability to create a serial terminal session from either > > side, with suitable juggling of getty processes? > > Used to do this in Linux w/o any problems... Just make sure that each > side waits for CD to go high before actively "starting" the getty > process, and that DTR is NOT asserted while the lines are idle. Kick up > kermit (or whatever) on the box 1, and the DTR signal from box 1 goes to > CD of box 2 - box 2 sends a login prompt, and life is good. > > (If memory's working, I had to beat up getty a bit to keep DTR low when it > was idle, but that wasn't too difficult - one ioctl at the appropriate > place... If I remember, I'll look at this a little more carefully when > I'm not so fried.) > > mike > Thanks for the reply. My guess on this is that the serial console on box 1 is keeping DTR high, hence preventing me from switching 'direction' on the serial line. If you have any more thoughts, please let me know. John -- Unreal City, Under the brown fog of a winter dawn, finger john@doorman.brann.org for pgp public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 11:56: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 49AA737B422 for ; Mon, 11 Sep 2000 11:56:05 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA10610 for ; Mon, 11 Sep 2000 14:57:25 -0400 (EDT) Message-Id: <200009111857.OAA10610@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 11 Sep 2000 14:56:41 -0400 To: hackers@freebsd.org From: Dennis Subject: fixing the if_dc.c driver Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see that, months after reporting the problem, the if_dc driver still takes 3 underruns to get to where its usable on a 100Mb/s network. Since i have no docs, can someone help with a hack that starts the device in store-and-forward mode? Im sure im not the only one who needs this. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 11:58:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id A3A5237B422 for ; Mon, 11 Sep 2000 11:58:10 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA10619 for ; Mon, 11 Sep 2000 14:59:50 -0400 (EDT) Message-Id: <200009111859.OAA10619@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 11 Sep 2000 14:59:06 -0400 To: hackers@freebsd.org From: Dennis Subject: SIOCSIFADDR broken? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it widely known and expected that the SIOCSIFADDR and companion commands dont work in FreeBSD 4.1? I know that the preferred command is SIOCAIFADDR, but shouldnt the standard calls also work for compatibility with portable code? dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 11:59:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mir.kapi.net (mir.kapi.net [195.165.21.13]) by hub.freebsd.org (Postfix) with ESMTP id 0799037B42C for ; Mon, 11 Sep 2000 11:59:46 -0700 (PDT) Received: from kapi.net (kapi.net [195.165.21.10]) by mir.kapi.net (8.9.3/8.9.3) with ESMTP id VAA88345 for ; Mon, 11 Sep 2000 21:59:39 +0300 (EEST) (envelope-from esko@kapi.net) Received: from localhost (esko@localhost) by kapi.net (8.9.2/8.9.3) with ESMTP id VAA28976 for ; Mon, 11 Sep 2000 21:59:39 +0300 (EEST) (envelope-from esko@kapi.net) X-Authentication-Warning: kapi.net: esko owned process doing -bs Date: Mon, 11 Sep 2000 21:59:39 +0300 (EEST) From: Esko Petteri Matinsola X-Sender: esko@sputnik To: hackers@freebsd.org Subject: Vinum RAID5 rawio performance Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Sep 2000, Greg Lehey wrote: > Please don't use bonnie. It's not measuring what you think it is. OK, I used rawio as you suggested. > I don't know how you'd find anything at vinumvm.org which tells you > what to expect from bonnie. No I did not. I found that I should be expecting about 25% of the write performance of striping than with raid5. > Well, using master and slave together isn't fine in my book. I ordered additional IDE-card three weeks ago, but haven't recieved it so I thought I should get started with these two on the motherboard. So, I tested with rawio. Here's rawio -a -p 8 /dev/ad0e: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec ad0e 1355.1 85 5335.0 326 1530.4 95 6416.9 392 With the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 sd length 512m drive drive2 sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid0 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid0 3593.0 221 17807.7 1087 11551.0 711 17503.5 1068 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid10 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 plex org striped 256k sd length 512m drive drive2 sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid10 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid10 3727.4 230 20024.5 1222 5727.5 358 10073.2 615 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid5 plex org raid5 256k sd length 512m drive drive0 sd length 512m drive drive1 sd length 512m drive drive2 sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid5 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid5 3569.9 221 19001.7 1160 1169.8 73 1105.1 67 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 # sd length 512m drive drive1 sd length 512m drive drive2 # sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid0 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid0 3756.6 233 16859.6 1029 5972.7 368 17213.3 1051 And with the the following configuration of vinum: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 # sd length 512m drive drive2 # sd length 512m drive drive3 I ran rawio -a -p 8 /dev/vinum/raid0 and got: Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec aid0 3756.6 233 16859.6 1029 5972.7 368 17213.3 1051 So, is this just what I should get or is there something I could do to that raid5 write performance ? Based on these figures, it's nowhere near 25% what I expect. I expect to get somewhat better performance when I get that IDE-card when I can put every drive as master on its own channel. Please comment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 12:27:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 186EC37B423 for ; Mon, 11 Sep 2000 12:27:24 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA13990; Mon, 11 Sep 2000 12:26:37 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009111926.MAA13990@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of "Mon, 11 Sep 2000 15:06:45 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Sep 2000 12:26:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ok, once i compiled a kernel with options BOOTP things got better ;-) > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs) > but after it re-configures the ethernet, the ethernet stops working! > > ponters anyone? You can't run dhclient (DHCP in any of the ifconfig lines in /etc/ rc.conf) if you have mounted / via NFS. If you're running -current or a very recent -stable, remove the 'BOOTP' options. The loader now passes all the DHCP information into the kernel. Then leave the interface configuration alone... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 11 13: 5:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id C948737B424; Mon, 11 Sep 2000 13:05:16 -0700 (PDT) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id QAA05967; Mon, 11 Sep 2000 16:05:14 -0400 (EDT) Date: Mon, 11 Sep 2000 16:05:14 -0400 From: Mathew KANNER To: Mike Smith Cc: Danny Braniss , freebsd-hackers@FreeBSD.ORG Subject: Re: diskless workstation Message-ID: <20000911160514.E27356@cs.mcgill.ca> References: <200009111926.MAA13990@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: Mike Smith's message [Re: diskless workstation] as of Mon, Sep 11, 2000 at 12:26:37PM -0700 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 11, Mike Smith wrote: > > ok, once i compiled a kernel with options BOOTP things got better ;-) > > it worked several times, but now it boots ok, (pxe->dhcp->tftpboot->nfs) > > but after it re-configures the ethernet, the ethernet stops working! > > > > ponters anyone? > > You can't run dhclient (DHCP in any of the ifconfig lines in /etc/ > rc.conf) if you have mounted / via NFS. > > If you're running -current or a very recent -stable, remove the 'BOOTP' > options. The loader now passes all the DHCP information into the kernel. > Then leave the interface configuration alone... Awesome!!! Another piece of the puzzle. Another note should be that if you use dynamic ranges, the dhcp lease times should be longer than you expect the client stations to up. --Mat > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Mathew Kanner Systems Programmer, SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 2:56:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 9EA3137B422; Tue, 12 Sep 2000 02:56:42 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13Ymnq-0007ng-00; Tue, 12 Sep 2000 12:56:34 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13Ymnp-00061r-00; Tue, 12 Sep 2000 12:56:33 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: diskless workstation In-reply-to: Your message of Mon, 11 Sep 2000 12:26:37 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Sep 2000 12:56:33 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009111926.MAA13990@mass.osd.bsdi.com>you write: }If you're running -current or a very recent -stable, remove the 'BOOTP' }options. The loader now passes all the DHCP information into the kernel. }Then leave the interface configuration alone... } the 'problem' is in dhcpd, who refuses to send the host-name tag, though it does send out allot of other info. when i added to nfs/bootp_subr.c call.vend[j++]=99; call.vend[j++]=53; /* dhcp-message-type */ call.vend[j++]=1; /* len */ call.vend[j++]=1; /* one :-) */ it answeres with allot of data, but more importantly: i get hostname! now for the next mile-stone - at this rate ... danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 3:58:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from charon.cs.uoi.gr (charon.cs.uoi.gr [195.130.121.185]) by hub.freebsd.org (Postfix) with ESMTP id 5629437B422 for ; Tue, 12 Sep 2000 03:58:14 -0700 (PDT) Received: (from peppe@localhost) by charon.cs.uoi.gr (8.11.0/8.11.0) id e8CAw6d03042 for hackers@FreeBSD.ORG; Tue, 12 Sep 2000 13:58:06 +0300 (EEST) (envelope-from peppe) From: Spyros Melissovas Message-Id: <200009121058.e8CAw6d03042@charon.cs.uoi.gr> Subject: Promise FasTrack66 IDE RAID controller In-Reply-To: "from freebsd-hackers-digest at Sep 12, 2000 02:56:50 am" To: hackers@FreeBSD.ORG Date: Tue, 12 Sep 2000 13:58:06 +0300 (EEST) X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was wondering if there is any kind of support for the Promise FasTrack66 IDE RAID controller AFAIK the controller needs a driver which will use the made-up disk geometry instead of the individual disks attached to it. Is anybody in the process of developing something for this controller? TIA -- Spyros Melissovas email: peppe@cs.uoi.gr tel: +30-651-98823 fax: +30-651-97048 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 4: 8:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3B67237B42C for ; Tue, 12 Sep 2000 04:08:07 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA47224; Tue, 12 Sep 2000 13:10:36 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009121110.NAA47224@freebsd.dk> Subject: Re: Promise FasTrack66 IDE RAID controller In-Reply-To: <200009121058.e8CAw6d03042@charon.cs.uoi.gr> from Spyros Melissovas at "Sep 12, 2000 01:58:06 pm" To: peppe@charon.cs.uoi.gr (Spyros Melissovas) Date: Tue, 12 Sep 2000 13:10:36 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Spyros Melissovas wrote: > Hello, > > I was wondering if there is any kind of support for the Promise FasTrack66 > IDE RAID controller We support it already as a normail ATA controller... > AFAIK the controller needs a driver which will use the made-up disk geometry > instead of the individual disks attached to it. > > Is anybody in the process of developing something for this controller? I have some submitted patches lying around, and have gotten info from HighPoint how they do their version of the SW RAID stuff. I'm working on getting this done generically and cover both the Promise and the HPT chips, and any other ATA controllers for that matter... Watch this space for further announcements... -Sřren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 7:12:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6C0F937B422; Tue, 12 Sep 2000 07:12:21 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA12324; Tue, 12 Sep 2000 10:14:05 -0400 (EDT) Message-Id: <200009121414.KAA12324@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 12 Sep 2000 10:13:07 -0400 To: "David B" , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG From: Dennis Subject: Re: Intel 815E In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:38 PM 07/21/2000 -0400, David B wrote: >I was wondering if anyone is using a motherboard with the Intel 815E >chipset. If so did you get the onboard video and sound to work?(not that is >overly important, I would popin an ATI xpert 98 8MB if need be). And if so, >which frebsd 3.4S, 5.0C or somewhere in between? > >I was thinking of the ABIT SE-6, in particular. > >To my knowlegde Intel, Asus and Abit are considered good manufacturers. >What are some others? and which are the manufacturers to avoid? In >particular, I was wondering about DFI they cost less but are their products >stable or problematic? The Intel BIOS sucks, and they are very slow booters. Every MB is an adventure. You cant make generalizations about any manufacturers in particular. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 12:52:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id AA89A37B423 for ; Tue, 12 Sep 2000 12:52:19 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA23074; Tue, 12 Sep 2000 12:51:16 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA67330; Tue, 12 Sep 2000 12:51:15 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 12 Sep 2000 12:51:15 -0700 (PDT) Message-Id: <200009121951.MAA67330@vashon.polstra.com> To: hackers@freebsd.org Cc: cobra@ceid.upatras.gr Subject: Re: ports cvsup In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Balis George wrote: > The last days I am trying to cvs both the latest stable source and the > latest ports from several servers. The problem is that when I am cvsing > the ports I get a segmentation faults and cvsup exits ungracefully > with a core dump. What could be wrong? > I include some maybe helpful info [...] > achilles# /usr/local/bin/cvsup -g -L 2 /usr/local/etc/cvsup/freebsd-ports-supfile > Parsing supfile "/usr/local/etc/cvsup/freebsd-ports-supfile" > Connecting to cvsup3.FreeBSD.org > Connected to cvsup3.FreeBSD.org > Server software version: REL_16_1 > Negotiating file attribute support > Exchanging collection information > Establishing multiplexed-mode data connection > Running > Updating collection ports-base/cvs > Edit ports/INDEX > Add delta 1.293 2000.09.05.19.23.28 asami > Checkout ports/Mk/bsd.ruby.mk > Edit ports/Mk/bsd.sites.mk > Add delta 1.9 2000.09.05.01.04.52 steve > Illegal instruction (core dumped) Illegal instruction faults may indicate that a thread stack overflowed, or they might be symptomatic of HW or kernel problems. Does it always seem to fail at the same point in the update? Actually it is hard to tell, since the log output only reflects what the Updater thread is doing. Here is what I would recommend. Make sure your kernel has "options KTRACE" configured in. Run cvsup under "ktrace -t cnis", but also add "@M3novm -P -" to the cvsup command line options. (If firewall issues prevent that from working, try "@M3novm -P a" instead.) Do this a few times, saving the "ktrace.out" file each time. Then use "kdump" to generate printable output from each ktrace.out file. Send me the last 500 lines of each one, and I'll try to figure out what's going wrong. If a thread stack is overflowing, it is probably caused by a corrupted file. However, I would prefer that you let me analyze the problem before you try to correct it by removing files, since it's a bug if cvsup dumps core because of a bad file (or for any reason at all). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 13: 0: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 513D237B422 for ; Tue, 12 Sep 2000 13:00:04 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13YwDq-000PYP-00; Tue, 12 Sep 2000 20:00:02 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8CK14G02661; Tue, 12 Sep 2000 22:01:04 +0200 (CEST) (envelope-from wkb) Date: Tue, 12 Sep 2000 22:01:04 +0200 From: Wilko Bulte To: John Polstra Cc: hackers@freebsd.org, cobra@ceid.upatras.gr Subject: Re: ports cvsup Message-ID: <20000912220104.A2638@freebie.demon.nl> References: <200009121951.MAA67330@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009121951.MAA67330@vashon.polstra.com>; from jdp@polstra.com on Tue, Sep 12, 2000 at 12:51:15PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 12:51:15PM -0700, John Polstra wrote: > In article , > Balis George wrote: > > The last days I am trying to cvs both the latest stable source and the > > latest ports from several servers. The problem is that when I am cvsing > > the ports I get a segmentation faults and cvsup exits ungracefully > > with a core dump. What could be wrong? > > I include some maybe helpful info > [...] > > achilles# /usr/local/bin/cvsup -g -L 2 /usr/local/etc/cvsup/freebsd-ports-supfile > > Parsing supfile "/usr/local/etc/cvsup/freebsd-ports-supfile" > > Connecting to cvsup3.FreeBSD.org > > Connected to cvsup3.FreeBSD.org > > Server software version: REL_16_1 > > Negotiating file attribute support > > Exchanging collection information > > Establishing multiplexed-mode data connection > > Running > > Updating collection ports-base/cvs > > Edit ports/INDEX > > Add delta 1.293 2000.09.05.19.23.28 asami > > Checkout ports/Mk/bsd.ruby.mk > > Edit ports/Mk/bsd.sites.mk > > Add delta 1.9 2000.09.05.01.04.52 steve > > Illegal instruction (core dumped) > > Illegal instruction faults may indicate that a thread stack > overflowed, or they might be symptomatic of HW or kernel problems. Or an executable built with mcpu / march. Happened to me when I had executables lying around that where built for pentiumpro and I tried to execute on a plain pentium box. Thought I'd mention this, YMMV obviously -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 13:16:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0B00337B424 for ; Tue, 12 Sep 2000 13:16:10 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA23293; Tue, 12 Sep 2000 13:16:04 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA67457; Tue, 12 Sep 2000 13:16:04 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 12 Sep 2000 13:16:04 -0700 (PDT) Message-Id: <200009122016.NAA67457@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: wkb@freebie.demon.nl Subject: Re: ports cvsup In-Reply-To: <20000912220104.A2638@freebie.demon.nl> References: <200009121951.MAA67330@vashon.polstra.com> <20000912220104.A2638@freebie.demon.nl> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000912220104.A2638@freebie.demon.nl>, Wilko Bulte wrote: > On Tue, Sep 12, 2000 at 12:51:15PM -0700, John Polstra wrote: > > > > Illegal instruction faults may indicate that a thread stack > > overflowed, or they might be symptomatic of HW or kernel problems. > > Or an executable built with mcpu / march. Happened to me when I had > executables lying around that where built for pentiumpro and I tried > to execute on a plain pentium box. Good point. However, it doesn't apply in this particular case. As I recall, the person reporting the problem was using the cvsup-bin port, which has a binary that I built myself without any of those options. In any case, it's not easy to figure out how to add such options when building a Modula-3 program. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 13:50:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 6F35D37B423 for ; Tue, 12 Sep 2000 13:50:10 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Yx0L-0001Rk-00 for hackers@freebsd.org; Tue, 12 Sep 2000 20:50:09 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8CKpBl02864 for hackers@freebsd.org; Tue, 12 Sep 2000 22:51:11 +0200 (CEST) (envelope-from wkb) Date: Tue, 12 Sep 2000 22:51:11 +0200 From: Wilko Bulte To: hackers@freebsd.org Subject: Re: ports cvsup Message-ID: <20000912225111.A2734@freebie.demon.nl> References: <200009121951.MAA67330@vashon.polstra.com> <20000912220104.A2638@freebie.demon.nl> <200009122016.NAA67457@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009122016.NAA67457@vashon.polstra.com>; from jdp@polstra.com on Tue, Sep 12, 2000 at 01:16:04PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 01:16:04PM -0700, John Polstra wrote: > In article <20000912220104.A2638@freebie.demon.nl>, > Wilko Bulte wrote: > > On Tue, Sep 12, 2000 at 12:51:15PM -0700, John Polstra wrote: > > > > > > Illegal instruction faults may indicate that a thread stack > > > overflowed, or they might be symptomatic of HW or kernel problems. > > > > Or an executable built with mcpu / march. Happened to me when I had > > executables lying around that where built for pentiumpro and I tried > > to execute on a plain pentium box. > > Good point. However, it doesn't apply in this particular case. As I > recall, the person reporting the problem was using the cvsup-bin port, > which has a binary that I built myself without any of those options. > In any case, it's not easy to figure out how to add such options when > building a Modula-3 program. :-) Right.. and I *knew* it was Modula-3. But forgot all about it when I posted the message. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 15:30:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 8F4CC37B42C; Tue, 12 Sep 2000 15:29:51 -0700 (PDT) Received: (from jkh@localhost) by winston.osd.bsdi.com (8.11.0/8.9.3) id e8CMTmV12787; Tue, 12 Sep 2000 15:29:48 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) Date: Tue, 12 Sep 2000 15:29:48 -0700 (PDT) Message-Id: <200009122229.e8CMTmV12787@winston.osd.bsdi.com> From: Jordan Hubbard To: hackers@freebsd.org Subject: Installation and package tools document, version 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Without a lot of preamble, let me just say that all that talk of FreeBSD needing a more active specifications and management process finally got me motivated into writing all this down. This being version 1.0 of this document, I also expect it to go through multiple versions as I get feedback on it, so please consider it merely the start of an ongoing effort to write down all these installation and packaging thoughts which have been rattling around my head these past 6 or so years. See the Preface for more information, and thanks in advance for being willing to read through a 5300 word document. :-) - Jordan Title: FreeBSD installation and package tools, past, present and future Date: September 8th, 2000 Author: Jordan K. Hubbard Version: 1.0 Abstract: This document discusses FreeBSD's installation, configuration and package management tools from the perspective of where they are and where I think they need to go. Contents -------- 1. Preface 2. History and current limitations 2.1 The package tools 2.2 Sysinstall 3. The Future 3.1 FreeBSD's distribution format 3.2 User Interface 3.3 Security 3.4 Configuration and version control 3.5 Installation scripting 4. Appendix: Current efforts 4.1 libh 4.2 lizard 1. Preface ---------- There has been a lot of discussion throughout FreeBSD's history as to just what purpose sysinstall and the pkg_install suite were intended to achieve, what their shortcomings are and how we might move forward with a design document which breaks the various challenges into more manageable pieces which might be implemented by a number of different teams. It's long been my desire to sit down and do exactly that, a lack of time being my only excuse for not having done so long ago. I'm also of the understanding that a new "open packages" effort was recently started by some of the people at Daemon News, a project with parallels to some of the existing efforts to get all the various open source projects to standardize on existing package formats like RPM, Debian packages, etc., and a good excuse for me to finally do this. I'm certainly all in favor of a standardization effort based around some viable and practical second-generation technology and can only hope that producing this document will in some way aid the design of a next-generation package and installation system. Should such an effort ultimately prove itself attractive to a large segment of the open source community then all the better, but we have to start somewhere and that somewhere, for me at least, is FreeBSD. The existing package systems (RPM, Deb, *BSD) all suffer from being first-generation efforts and, while quite mature, do not address a number of significant issues which I'll cover in this document. I'll also document some of the design decisions which went into FreeBSD's current system, hopefully explaining some of the [mis]features which have confused newcomers to FreeBSD or caused them to wonder just why things were not done differently. 2. History and current limitations ---------------------------------- 2.1 The package tools --------------------- The FreeBSD package tools, located in /usr/src/usr.sbin/pkg_install, were written in August of 1993 in response to several requirements that we had at the time. Most significantly, it was not possible to easily track "extra software" that one might add to the system and conceivably wish to easily remove again, nor was it easy to see which versions of software had been installed on a given system for easier troubleshooting. Finally, any specialized installation procedures for a given piece of software essentially had to be done manually by reading the README file (when available) accompanying the binary distribution tarball, assuming of course that anything other than sources which you needed to build yourself were available. After looking at the problem for awhile, I decided that the quickest and easiest solution would be to simply add a little extra "meta-data" to these existing binary tarballs, something which could then be executed and recorded for future reference by a package adding utility. Thus were born the pkg_install utilities we have today. At the time, system administrators were also very mistrustful of pre-built binary distributions of software (not that many would actually read source code before building and installing binaries from it, but that's another story) so that's why I decided to use an existing archive format, namely gzipped tar files. This approach allowed paranoid admins to easily extract a package manually and inspect it, it also allowing me to leverage our existing tools relatively easily (though one feature, --fast-read, did need to be added to tar so that individual items could be extracted more quickly). There were and are problems with this approach, however, the most significant being that tar files (especially gzipped ones) are NOT very amenable to random-access. The directory structure of a tarfile is distributed, e.g. the file data is interleaved with the directory meta-data and, in order to get to a given item in a tarball, pkg_add(1) needs to read serially through the whole thing looking for it. This can be an especially big problem when all it has to work with is a file handle and not an actual file, something which is the case when a package is coming directly from an FTP server or some other data source which offers only serial access to the bits. pkg_add "solves" this problem by first finding sufficient temporary space on one of the available file systems and then unpacking the tarball to be extracted into a scratch directory. After the tarball is extracted, pkg_add then reads through the "packing list" (one of the meta-data files) and follow its instructions to move only those parts of the unpacked tarball into place which are needed, thus skipping the meta-data files and any others which might be optional and not actually requested by the user. During this process, it is then possible to run any custom installation scripts the package might have provided to ask the user configuration questions, do special permissions/conflict checks, and run through the package's list of dependencies on other packages to see if they should be somehow fetched and installed as well. All in all, it's a very general purpose and open-ended mechanism which many packages have used to good effect, but the temporary directory requirement would also turn around to bite me firmly on the ass when it came time to write sysinstall, which followed in April of 1995. 2.2 Sysinstall -------------- Sysinstall, located in /usr/src/release/sysinstall, was FreeBSD's first attempt at doing something more elegant and user-friendly than a simple shell script-based installation which merely asked questions in a fixed order and gave the user little opportunity to do different types of installation and configuration. The "first draft" of sysinstall was actually meant to be little more than a prototype of the installer I really wanted to write, especially from the user interface perspective since it used something called dialog(3). The dialog library began its life as a monolithic utility for writing semi-graphical shell scripts and was pressed, with great reluctance, into the duty of functioning as an interface library for C programmers. At the time, this seemed the easiest course of action given that I wasn't overly keen on writing a new set of interface components in curses(3) and the dialog library provided some fairly colorful canned dialogs which looked, at least for the time, reasonably visually impressive. In retrospect, this was also one of my biggest mistakes given that dialog(3) is also extremely limited in the user-friendliness department and lacks features like the ability to put more than 2 buttons into a dialog or a Yes/No dialog which had a selectable default (e.g. No). The inability to put a "Back" button into various dialogs which could really use one or the necessity for asking only "positive" questions are outgrowths of those limitations and good examples of how an insufficiently powerful UI library can drive the utility-writer in undesirable but unavoidable directions. The dialog library also features checkbox/radio menus which use the spacebar and enter keys very, erm, creatively to essentially confuse the heck of out users who don't pay too much attention to the Usage instructions at the beginning and simply impulsively hit Enter through the whole installation. Earlier versions of the library also completely lacked the idea of call-backs, so any form of real "dynamism" in a menu or dialog was pretty much out of the question. The things I had to do to this library in order to provide those features were so hideous that I'll probably go to a special programmer's hell when I die and be forced to do AI programming in RPG-II, or something, it also souring me on the idea of extending dialog(3) to the point where it might have actually made sysinstall less pathological in its interface behavior. The user interface library has also turned out to be not the least of sysinstall's design shortcomings. Since it was, at least in my mind, a prototype, there wasn't a lot of attention put into the area of flexibility. I provided for things like "Expert" and "Novice" (now less-insultingly named "Standard") installs, but I didn't really do much for people who wished to build many machines in a more assembly-line fashion or allow the user to save their answers to its questions for later "replay" into another installation session. Extending sysinstall also requires a knowledge of C programming (and the willingness to hack on a prototype) in order to customize it for other purposes, say a university environment where special course-ware might be part of the FreeBSD installation at the beginning of each semester. It's nowhere near as easy as it should be and many have been impaled on sysinstall in their efforts to customize FreeBSD for their unique needs. An even more significant issue with sysinstall and FreeBSD's release methodology in general is the distribution format of FreeBSD itself and sysinstall's handling of packages, especially interactive ones. FreeBSD's release methodology has really not changed all that much in the last 8 years, the basic distribution format still being largely influenced by the size of a 3.5" floppy. Each chunk of a FreeBSD distribution, e.g. the "bin" or "manpages" distributions, is nothing more than one big gzipped tarball which has been split into 240K chunks which can conveniently fit on floppies, 5 to a 5.25" floppy or 6 to a 3.5" one. Back in 1992, when we first started doing this, there were a lot of people doing floppy installs and CDs were still uncommon and/or expensive. Sysinstall was therefore designed to take a lot of the hair out of the process by automagically gluing these 240K chunks together as they came along, from whatever distribution medium was available, and feeding them to a background tar process which would simply extract them verbatim into a directory (usually, but not always, /). There are lots of problems with this, one being the fact that since a "distribution" is nothing more than a gzipped tarball split into pieces, there is none of the nifty meta-data which packages provide to say what has been installed, what dependencies it has, or any hooks for providing post-installation configuration opportunities. Even component size information is a mystery, making sysinstall unable to predict when you've chosen more distribution data than will fit on a given filesystem, leading to occasionally unpleasant surprises during installation when something fills up and simply exlodes in a messy and unhelpful fashion. A bigger problem is the fuzzy and entirely undesirable dividing line between packages and distributions. What should be a distribution and what should be a package? Where does the ``base distribution'' stop and the ports/packages collection begin? How should one upgrade the respective bits? Erasing this line of demarcation has proven to be one of the more annoying challenges in FreeBSD's release engineering process and I'll explain how and why later in this document. Finally, sysinstall simply represents a conglomeration of too many tasks. It partitions your disk(s), it loads software, it asks you questions about your network interfaces, it sets up your ppp connection, etc etc. It just tries to do too much in one place and that's a violation of the Unix Philosophy, where each component should do one easily recognizable task and no more than that, more complex tasks being achieved by putting such tools together. What we currently think of as sysinstall should essentially do nothing more than partition your disks and get a much fancier second-stage "configurator" onto the root partition before rebooting. At that stage, the configurator can give the user the option of adding the other disks and chosing what kinds of software to put on them. The scope of the configurator should be such that it becomes a general-purpose setup tool which can be used to manage all the hardware and software in the system on an ongoing basis, not simply run once and forgotten. 3. The Future ------------- 3.1 FreeBSD's distribution format --------------------------------- As I mentioned in the history section, one of the more annoying problems with FreeBSD's current distribution format is the dividing line between distributions and packages. There should really only be one type of "distribution format" and, of course, it should be the package (There Can Be Only One). Achieving this means we're first going to have to grapple with several problems, however: First, eliminating the distribution format means either teaching the package tools how to deal with a split archive format (they currently do not) or divorcing ourselves forever from floppies as a distribution medium. This is an issue which would seem an easy one to decide but invariably becomes Highly Religious(tm) every time it's brought up. In some dark corner of the world, there always seems to be somebody still installing FreeBSD via floppies and even some of the fortune 500 folks can cite FreeBSD success stories where they resurrected some old 386 box (with only a floppy drive and no networking/CD/...) and turned it into the star of the office/saved the company/etc etc. That's not to say we can't still bite that particular bullet, just that it's not a decision which will go down easily with everyone and should be well thought-out. Second, there's the issue of packages currently requiring temporary space as part of their extraction method. If we're going to have things like "bin" be a package, even if we split it up into subcomponents and make "bin" simply a package which contains a list of dependencies and nothing more (which is desirable), there are still going to be pieces which are non-extractable under the current scheme because the available disk space is too small to contain both the temporary copy and the final installed copy, which may not be on the same file system can cannot be simply moved into place. Since we'd also like to retain the ability to extract a package directly over a network connection and never have the temporary bits "hit the disk", this means that we're almost certainly going to have to go to a different archival format. Fortunately, there are some existing formats to choose from which have a lot of the required features so we won't have to reinvent the wheel and come up with our own (yuck). My current favorite is the Zip archive format. Zip is a popular archival format which gives us a wide variety of existing tools for creating, fixing and inspecting zip files. The directory is also at the very beginning so we can quickly read it in and figure out where in the data stream/file we need to go to get a specific item. Since the "configurator" stage of the installation will also be running after we've acquired a root partition and some swap space, it's also not inconceivable that we could buffer bits read over a network connection in memory so that even "seeking" out to the end of an archive file read from an FTP server socket would still allow us to move backwards in the archive for other contents. The zip file format also allows for per-archive and per-file "comment" fields which can be used to store things like MD5 checksums, pgp signatures and all sorts of other potentially useful types of meta-data. I'm not wedded to the zip file format, I simply find its combination of good compression and random-access (without having to decompress the entire archive) to be especially attractive for what we need to do. Finally, there's the issue of user interaction. The bulk of sysinstall's hard-coded features do things like make user queries which could just as easily be part of a package's install-time configuration script. Sysinstall, for example, allows you to specify which daemons will run at startup time even though this is only pertinent to the "bin" package which actually contains those daemons. Similarly, there have been security-related questions pertaining to the cryptography distributions which, even though the US crypto export and RSA issues have now been largely dealt with, may still be pertinent in other countries. Clearly, such interaction should be part of the package installation procedure itself and sysinstall should be little more than a friendly wrapper for selecting which packages to install and running their installation procedures, and that brings us to the question of User Interface. 3.2 User Interface ------------------ As noted in the History section, one of the biggest problems with sysinstall is its user interface which could only be charitably described as Evil Incarnate. The dialog(3) interface library, as I've already described, is insufficiently powerful to give the user a flexible and intuitive installation experience nor it does not take any real advantage of environments like the X Window System, should the user be running a configurator under such an environment. The package system also suffers significantly in the UI area since the pkg_add(1) utility has no idea as to whether it's running at the end of a pipe, as it currently does under sysinstall, or if it's got a real live user at the other end who's invoked it interactively from a shell. This leads to real problems when a package suddenly decides it wants to talk to the user but is being run via a front-end which will react adversely (or not at all) to the sudden appearance of the package's own interaction dialogs. This is not just a hypothetical situation but one which can, and currently does, happen whenever sysinstall's packages menu invokes a package which is interactive. The user dialogs all go to the 2nd VTY and leave the actual user somewhat mystified as to why the package installation has mysteriously "hung" on them as it waits for user input which never arrives. To effectively solve this problem, what is needed is a flexible (e.g. containing more basic "widgets" than canned dialogs) and generic UI library which provides front-end utilities like sysinstall and pkg_add with the ability to play traffic cop and direct all user interaction through a common interface. That might be something CUI based, like TurboVision (my current CUI favorite) or GUI based, like Qt/gtk, when running under X. It might even be something which talks to a Java-enabled web browser at some point in the future - we really can't predict all the conceivable UI scenarios. The package system would call into this library whenever it wanted to talk to the user, thus sharing the screen/display non-competitively with whatever utility invoked it. It would be up to the outermost "caller" (be it pkg_add or sysinstall) to decide at initialization time just what kind of back-end UI to instantiate for the generic UI. Such an approach would allow us to write all of our configuration utilities and scripts in a UI-neutral fashion which allows us to take advantage of new UI technologies as they come along without having to go back and re-write all of those painstakingly crafted user dialogs. That's basically where 99% of all the work of crafting such user interfaces goes, and we certainly don't want to have to write two different interface definitions for CUI (serial console / remote installer) and GUI (X Desktop) based users. There are some operating systems (that I won't mention) which sort of get away with this today, but FreeBSD has always been a strongly server-centric operating system and that means we really can't have a highly desktop-centric installer, we have to support the idea of installation on machines without graphics cards at all or even in situations where the user is visually handicapped and wishes to have a customized installer who's "interface" is a voice synthesizer. All of this is possible when the UI library you write directly to makes no assumptions at all about what the ultimate rendering model is going to be, it simply thinks in terms of objects like "buttons" and "choice lists", leaving it up to the back-end layer to ultimately render the appropriate UI objects somehow. 3.3 Security ------------ A major failing of most package systems, ours included, is that a package's installation and configuration scripts can essentially be any type of executable at all. While this does allow the package writer a great deal of flexibility in providing for a package's needs, and there are packages which do have highly specialized requirements, it also has a huge potential effect on security. Most packages are installed as root for a variety of reasons, some legitimate and some not, and the overall effect is that security is essentially an "opt-in" process for whomever creates or installs a package. A package which is installed as root is a package which can be either intentionally or unintentionally lethal to a user's system, even a pgp-signed and triple-authenticated package being capable of completely destroying a user's system, and it's not hard to see how. Consider what might happen if an otherwise perfectly respectable package author, overly caffeinated and partially delirious at 4am, were to write: ``rm -rf /${MYTMPDIR}'' into a package's installation script as part of its clean-up procedure. Let's also say that this removal operation is inside a failure-case check in the installation script and the author doesn't hit that case during their testing since they happen to drive the installation successfully each time. Let's finally say that the actual name of the variable in question is "MYTEMPDIR" and the author, in a state of 4am dyslexia, does not spot this mistake. You get the idea. Even if the package is pgp signed and the package author is your personal, trusted friend, you're still going to be wondering at all the sudden extra disk activity right after bombing out of his package's installation script and none of the conventional security practices have saved you from his mistake. The author is most embarrassed, your system is most toast, and you can both chalk it up to another annoying conjunction of human and infra-structural stupidity. Clearly, it would be desirable for a package which genuinely and truly needs to be root to do so in a manner which is in any way safer than it is now. One method I'm in favor of is to change a package's customization script(s) from being any arbitrary executable to being a very specific executable, namely a set of instructions in some tightly constrained scripting language. My personal favorite is Secure TCL, a useful outgrowth of the enhancements done to TCL when it got stuffed into a web browser and suddenly needed to worry a lot more about security issues. Secure TCL allows us to create highly restricted TCL environments which can be selectively "tightened" according to an administrator's own level of paranoia, allowing them to have a highly customizable and final say over what level of capability will be given to any package they install. Thus it would be possible, just to give an example, to restrict the ``file-access'' primitive to only returning a positive "It's OK to access this" indication for file names who's paths match "/etc/.*", "/usr/local/.*" or "/usr/X11R6/.*". The ``file-create'', ``file-write'' and ``file-remove'' primitives could, in turn, always validate their arguments against ``file-access'' before proceeding. With a properly designed set of primitives, it would be thus possible to evolve mechanisms for "practical security", where potentially foot-shooting primitives can either be disallowed entirely, allowed to proceed only upon user confirmation or go completely unhindered, all according to the administrator's wishes. With a little time, such package security tweaks would also begin to float around and come into the reach of less skilled administrators, just as standardized cisco access-lists for fire-walling are passed around today. It need not be TCL that is chosen for this purpose, naturally, it's simply my personal preference since I happen to already know and have working experience with TCL. A language like Python or Ruby is also probably capable of doing the job just as well, it only being necessary for the interpreted language of choice to have some sort of reasonable security model and a comparatively small footprint. I stipulate that the footprint needs to be small because any future system configurator and package infrastructure will need to be wrapped together to some extent, the resulting product being something we may wish to bootstrap off of comparatively small media. A properly written package management system will be an indispensable piece of the installation process given that the pieces of the operating system will, of course, be packages. 3.4 Configuration and version control ------------------------------------- Ultimately, installing the "OS networking package" or the "Apache Server" package should be part of a seamless, "one piece", installation experience with a common and consistent UI. The ability to leave "configurators" for each subsystem or tool behind should also be an integral part of the process, these later being runnable from a single front-end tool (let's call it ``setup'') which offers a properly organized menu/folder hierarchy for all the available tool configurators to drop themselves into. None of this is rocket science and folks like Microsoft and Apple have been doing it for ages with their operating systems. It's a workable model and, perhaps more importantly, it's now the most familiar model. Another nice thing about having a package install itself through a carefully controlled scripting language is that each mutagenic operation (say, a file overlay) can store "undo" information for itself if given enough available disk space. Also imagine that all of the undo information for a given package, throughout its lineage, goes onto an "undo stack" for that package. If necessary, the package can thus be "popped" back through its previous versions to test and see where and if a given problem (which may be noticed only months after the last upgrade) first appeared. Since the changes would be stored as deltas, files which do not change would also appear only once and no space wasted in representing multiple redundant copies of those pieces of a package which don't change from version to version (like the docs :-). Making such a mechanism part of the basic infrastructure may strike some as an over-kill proposal, but I would also submit that the problem of upgrading packages and of having multiple active versions of a single package (like gtk or TCL) are significant issues which have received rather ad-hoc attention to date. With the creative and automated use of symlinks and some filename hashing, I think we could come up with a mechanism which does for package version control what CVS does for software version control (though hopefully even less painfully :). A genuine database of some sort containing package version meta-data is also a requirement since, on a fully tricked-out system, many hundreds (if not thousands) of files might eventually be involved and keeping track of various their inter-relationships is not something you'd generally want to do with simplistic file structures (like /var/db/pkg) which require a lot of time to search and index. 3.5 Installation scripting -------------------------- Another subject I touched on earlier was the need for automated and/or highly customized installations since the needs of everyone installing FreeBSD aren't exactly identical. Given access to a nice generic UI library, as described in section 3.2, and a powerful scripting language, as described in section 3.3, we could make what people currently regard as sysinstall a purely script-driven affair. This will obviously make customization a lot easier since all anyone needs is a text-editor and a document of available primitives (which many would probably choose to learn simply by looking at the example installation anyway) in order to create a customized install and/or add their own questions to an existing package configurator. I also doubt that most people would need to be able to do this, but for those very few that do, such flexibility can and will make the difference between getting FreeBSD into some highly customized environments or simply not making the grade. 4. Appendix: Current efforts ---------------------------- 4.1. libh --------- The libh project is something I started over a year ago, with input from Mike Smith and the paid services of a Russian contract programmer named Eugene, to fulfill many of the goals expressed in this document. Unfortunately, managing a project of this complexity with a contractor many thousands of miles away and a personal schedule which allowed for very little interaction with him didn't prove to be a workable scenario and work was stopped while partially in progress. Since that time, work on it has been taken over by Alexander Langer and a small group of volunteers. A mailing list, freebsd-libh, can also be subscribed to via majordomo@freebsd.org, and the sources checked out via ``:pserver:anonymous@usw4.freebsd.org:/home/libh/cvs'' using anoncvs. The name ``libh'' is also something of a mystery to everyone but it nonetheless stuck as a working title. It probably needs to be renamed to something sexier before this project can really succeed. :-) Roughly speaking, libh currently contains: A first cut at the generic UI library, as described in section 3.2, with back-end renderers for TurboVision and Qt currently being provided. The generic UI API it provides is available for C, C++ and TCL. A complete zip file-access library written for C, C++ and TCL as described in section 3.1. Much of the security infrastructure described in section 3.2 is also implemented, with enough currently done to make possible a prototype package creation/extraction system with some test packages available (and used as part of the regression-test suite). The package information database is also written, with APIs for C, C++ and TCL. It provides for package conflict, upgrade and outdate checking. While libh does contain a lot of the code we might ultimately use, it should nonetheless be considered only one possible starting point for implementing what I've described in this document. I certainly would be happy to see the time and investment in libh ultimately go to good use, of course, but I also wouldn't want it to stand in the way of any larger and more successful effort which chose a different scripting language or UI design, for example. 4.2 lizard ---------- Lizard is the installer currently bundled, albeit in highly modified form, with Caldera's OpenLinux distribution and made freely available in some of its earlier incarnations from ftp.caldera.com. It has been suggested that a "Desktop version" of FreeBSD could be created using this technology as a stop-gap measure until libh or some similar project succeeded in solving the more complex set of issues I've outlined, that perhaps buying us a bit more time to "do things right" (in my highly prejudicial opinion :). As far as I'm aware from my limited reading of the code, lizard is only applicable to graphical installations and does not make allowances for people installing via a serial console, hence its applicability to just a desktop-oriented product. Still, it might be worth looking at by people who's interests lie solely in that direction. Customization from the highly linux-centric environment lizard currently assumes is, of course, something else which would need to be grappled with as part of such an effort. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 12 20:53: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from diogenis.ceid.upatras.gr (diogenis.ceid.upatras.gr [150.140.141.181]) by hub.freebsd.org (Postfix) with SMTP id EDB3437B423 for ; Tue, 12 Sep 2000 20:53:04 -0700 (PDT) Received: (qmail 10497 invoked by uid 1604); 13 Sep 2000 03:49:26 -0000 Date: Wed, 13 Sep 2000 06:49:25 +0300 (EET DST) From: Balis George To: John Polstra Cc: hackers@freebsd.org Subject: Re: ports cvsup In-Reply-To: <200009121951.MAA67330@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-7 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Sep 2000, John Polstra wrote: > Date: Tue, 12 Sep 2000 12:51:15 -0700 (PDT) > From: John Polstra > To: hackers@freebsd.org > Cc: cobra@ceid.upatras.gr > Subject: Re: ports cvsup >=20 > In article , > Balis George wrote: > > The last days I am trying to cvs both the latest stable source and the > > latest ports from several servers. The problem is that when I am cvsing > > the ports I get a segmentation faults and cvsup exits ungracefully > > with a core dump. What could be wrong? > > I include some maybe helpful info > [...] > > achilles# /usr/local/bin/cvsup -g -L 2 /usr/local/etc/cvsup/freebsd-por= ts-supfile > > Parsing supfile "/usr/local/etc/cvsup/freebsd-ports-supfile" > > Connecting to cvsup3.FreeBSD.org > > Connected to cvsup3.FreeBSD.org > > Server software version: REL_16_1 > > Negotiating file attribute support > > Exchanging collection information > > Establishing multiplexed-mode data connection > > Running > > Updating collection ports-base/cvs > > Edit ports/INDEX > > Add delta 1.293 2000.09.05.19.23.28 asami > > Checkout ports/Mk/bsd.ruby.mk > > Edit ports/Mk/bsd.sites.mk > > Add delta 1.9 2000.09.05.01.04.52 steve > > Illegal instruction (core dumped) >=20 > Illegal instruction faults may indicate that a thread stack > overflowed, or they might be symptomatic of HW or kernel problems. > Does it always seem to fail at the same point in the update? Actually > it is hard to tell, since the log output only reflects what the > Updater thread is doing. >=20 > Here is what I would recommend. Make sure your kernel has "options > KTRACE" configured in. Run cvsup under "ktrace -t cnis", but also add > "@M3novm -P -" to the cvsup command line options. (If firewall issues > prevent that from working, try "@M3novm -P a" instead.) Do this a few > times, saving the "ktrace.out" file each time. Then use "kdump" to > generate printable output from each ktrace.out file. Send me the > last 500 lines of each one, and I'll try to figure out what's going > wrong. >=20 > If a thread stack is overflowing, it is probably caused by a corrupted > file. However, I would prefer that you let me analyze the problem > before you try to correct it by removing files, since it's a bug if > cvsup dumps core because of a bad file (or for any reason at all). >=20 > John > --=20 > John Polstra jdp@polstra.= com > John D. Polstra & Co., Inc. Seattle, Washington = USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam Tr= ungpa >=20 Thank you very much John but it seems that my problem got solved when i specified: ports-all instead of specifying individual ones. Also the core dump happened only when i was cvs-ing the ports not the system sources. So maybe there is a bug in the current cvsupd implementaion that I'm not aware of. In anycase I got my ports and I'm ok now but maybe I should check a little more on the matter. George =09=09 // =09=09// *=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D> =09=09\\ =09=09 \\ =09=09=09When you gaze long into the abyss,=20 =09=09=09the abyss also gazes into you... =09=09=09=09=09"Friedrich Nietzche" =09=09=09=09=09=09=09 \\ =09=09=09=09=09=09=09 \\ <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D* =09=09=09=09=09=09=09 // =09=09=09=09=09=09=09 // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 2:32:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 0F5A537B43C for ; Wed, 13 Sep 2000 02:32:24 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8D8vvH11278; Wed, 13 Sep 2000 09:57:57 +0100 (BST) (envelope-from nik) Date: Wed, 13 Sep 2000 09:57:55 +0100 From: Nik Clayton To: Jordan Hubbard Cc: hackers@freebsd.org Subject: Documentation (was Re: Installation and package tools document, version 1.0) Message-ID: <20000913095753.A11235@canyon.nothing-going-on.org> References: <200009122229.e8CMTmV12787@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009122229.e8CMTmV12787@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Sep 12, 2000 at 03:29:48PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, On Tue, Sep 12, 2000 at 03:29:48PM -0700, Jordan Hubbard wrote: > Title: FreeBSD installation and package tools, past, present and future > Date: September 8th, 2000 > Author: Jordan K. Hubbard > Version: 1.0 For everyone's reference; documentation like this is *always* on topic for -doc. If you write something like this for anything you're currently working on, please send a cc: to -doc (and set reply-to to go back to the other lists). This gives the -doc folk a chance to keep an eye on what's happening, and to make sure that things like this are available from the web site, and so on. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 4:12:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rye.elite.net (rye.elite.net [205.199.220.6]) by hub.freebsd.org (Postfix) with ESMTP id 18AB937B422 for ; Wed, 13 Sep 2000 04:12:20 -0700 (PDT) Received: from almond.elite.net (root@almond.elite.net [205.199.220.5]) by rye.elite.net (8.9.3/8.9.3) with ESMTP id EAA81805 for ; Wed, 13 Sep 2000 04:12:14 -0700 (PDT) Received: (bangel@localhost) by almond.elite.net (8.8.3/8.6.12) id EAA06034; Wed, 13 Sep 2000 04:12:14 -0700 (PDT) Date: Wed, 13 Sep 2000 04:12:14 -0700 (PDT) From: kts To: hackers@freebsd.org Subject: help debugging kernel crash dump Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Just wanted to see if anyone could give me some feedback as to what happened, or how to get more info. My machine was just sitting on the LAN and it panic'd. X was running and it had some ssh's open. I'm running 4-STABLE from August 3rd. IdlePTD 3522560 initial pcb at 2ce300 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc061d000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01acb69 stack pointer = 0x10:0xd3e69c20 frame pointer = 0x10:0xd3e69c58 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 210 (rc5des) interrupt mask = trap number = 12 panic: page fault syncing disks... 1 done Uptime: 3d16h11m57s dumping to dev #wd/0x20001, offset 278560 dump ata0: resetting devices .. done 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc0141ef0 in boot () (kgdb) bt #0 0xc0141ef0 in boot () #1 0xc014228d in panic () #2 0xc025b166 in trap_fatal () #3 0xc025ae19 in trap_pfault () #4 0xc025a9df in trap () #5 0xc01acb69 in fr_makefrip () #6 0xc01b2a98 in fr_checkicmpmatchingstate () #7 0xc01b2cd9 in fr_checkstate () #8 0xc01ad758 in fr_check () #9 0xc01a17e8 in ip_output () #10 0xc019fa6a in icmp_send () #11 0xc019f9eb in icmp_reflect () #12 0xc019f314 in icmp_error () #13 0xc01aa46e in udp_input () #14 0xc01a0498 in ip_input () #15 0xc01a050b in ipintr () #16 0xc024de85 in swi_net_next () Cannot access memory at address 0x531b6b24. (kgdb) any way I can get more information from that? I know using a kernel compiled with -g would help, but how would that be done, because I've been sup'ing my src every day... Thanks Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 10:36:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C17CF37B423 for ; Wed, 13 Sep 2000 10:36:25 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA65590; Wed, 13 Sep 2000 11:36:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA89128; Wed, 13 Sep 2000 11:35:49 -0600 (MDT) Message-Id: <200009131735.LAA89128@harmony.village.org> To: Adam Subject: Re: What's the best PCMCIA Ethernet card? Cc: Stephen Hocking , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 09 Sep 2000 23:23:43 EDT." References: Date: Wed, 13 Sep 2000 11:35:49 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Adam writes: : Hi, I'd just like to say that I dont think non cardbus cards are capable : of doing more than 10bt speeds even if it talks 100bt. I have not met one : that did and I assume it is a limit of the pcmcia design. Just warning : you not to waste your money on one if you get near 10bt speeds already. I've seen about 18-20Mb/s on the 100bt cards that I have. I think this is close to the theoretical max for pcmcia in a cardbus bridge (10MHz bus at 16bits/transaction). I think the max for an ISA bridge is more like 15-16Mb/s because the card is limited to the 8MHz (or 8.33MHz) speed of the ISA bus. 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 13 10:39:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5E9DD37B43E for ; Wed, 13 Sep 2000 10:39:20 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA65611; Wed, 13 Sep 2000 11:39:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA89169; Wed, 13 Sep 2000 11:38:49 -0600 (MDT) Message-Id: <200009131738.LAA89169@harmony.village.org> To: shocking@houston.rr.com Subject: Re: What's the best PCMCIA Ethernet card? Cc: Kenneth Wayne Culver , Adam , hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 10 Sep 2000 15:07:20 CDT." <200009102007.e8AK7KG15668@bloop.craftncomp.com> References: <200009102007.e8AK7KG15668@bloop.craftncomp.com> Date: Wed, 13 Sep 2000 11:38:49 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009102007.e8AK7KG15668@bloop.craftncomp.com> Stephen Hocking writes: : My main reason for wanting to replace the wretched thing is that it : keeps on hanging when doing lots of writes under NFS (when it's a : client), even when the write size is reduced to 2k. Everyone's : currently banging away at the new SMP code, so rather than plague : Bill Paul with requests about the if_sn driver, I'm thinking of just : getting a more reliable card. Odd. The sn card is my main card these days and I've not seen any NFS performance issues. Maybe you have an interrupt problem? I use the Megahertz XJ10BT, btw. Which card are you using? I was doing NFS last night on it with little hassle on a -current kernel from last night. 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 13 12: 4: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id 1860737B422 for ; Wed, 13 Sep 2000 12:03:56 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 13 Sep 2000 14:01:23 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8DJ3aG02728; Wed, 13 Sep 2000 14:03:36 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1] (may be forged)) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e8DJ3WG07447; Wed, 13 Sep 2000 14:03:32 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009131903.e8DJ3WG07447@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: culverk@wam.umd.edu, bsdx@looksharp.net, hackers@FreeBSD.ORG Subject: Re: What's the best PCMCIA Ethernet card? In-Reply-To: Your message of "Wed, 13 Sep 2000 11:38:49 MDT." <200009131738.LAA89169@harmony.village.org> Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-19048462580" Date: Wed, 13 Sep 2000 14:03:32 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-19048462580 Content-Type: text/plain; charset=us-ascii > Odd. The sn card is my main card these days and I've not seen any NFS > performance issues. Maybe you have an interrupt problem? > > I use the Megahertz XJ10BT, btw. Which card are you using? I was > doing NFS last night on it with little hassle on a -current kernel > from last night. The card's a "Megahertz (CC10BT/2)", according to pccardd. I had to manually put the IRQ in the /etc/pccard.conf file. The kernel code is from the PRE_SMPng tag. Hmmm - I kind of suspect interrupt issues. The dmesg is as follows, the card doesn't seem to load up if I dont have a "device sn" in the config file. I'm not sure why it's not seen when loaded as a module. I do have "COMPAT_OLDISA" and "COMPAT_OLDPCI" defined in there (don't ask, I think I was planning on using the old sound drivers at one stage). This may be why interrupts are being dropped. Stephen --==_Exmh_-19048462580 Content-Type: text/plain ; name="dmesg.out"; charset=us-ascii Content-Description: dmesg.out Content-Disposition: attachment; filename="dmesg.out" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Sep 8 21:48:55 CDT 2000 toor@bleep.craftncomp.com:/usr/src/sys/compile/wanderer Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 132632202 Hz CPU: Pentium/P54C (132.63-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 151126016 (147584K bytes) avail memory = 143417344 (140056K bytes) pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "kernel.ko" at 0xc036a000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 4.0 isa0: on motherboard ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 pcm0: at port 0x530-0x537 irq 5 drq 1 flags 0xa100 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pccard: card inserted, slot 0 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 2067MB [4200/16/63] at ata0-master using BIOSPIO acd0: CDROM at ata1-master using BIOSPIO Mounting root from ufs:/dev/ad0s1a sn1 at port 0x240-0x24f irq 11 slot 0 on pccard0 sn1: SMC91C94 UTP MAC address 00:00:86:16:b7:e5 module_register: module isa/sn already exists! Module isa/sn failed to register: 17 module_register: module pccard/sn already exists! Module pccard/sn failed to register: 17 --==_Exmh_-19048462580 Content-Type: text/plain; charset=us-ascii The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California --==_Exmh_-19048462580-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 12:27:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 3251E37B424 for ; Wed, 13 Sep 2000 12:27:24 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZIBk-0002Kz-00 for hackers@freebsd.org; Wed, 13 Sep 2000 22:27:20 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZIBj-0007C1-00 for hackers@FreeBSD.ORG; Wed, 13 Sep 2000 22:27:19 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: hackers@FreeBSD.ORG Subject: installing ... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Sep 2000 22:27:19 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG after i made a 'make buidlworld' how can i get it to install in /5.0-CURRENT? i compiled on a 4.1. tia, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 12:53:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 514FB37B424 for ; Wed, 13 Sep 2000 12:53:26 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA66296; Wed, 13 Sep 2000 13:53:24 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA90339; Wed, 13 Sep 2000 13:52:53 -0600 (MDT) Message-Id: <200009131952.NAA90339@harmony.village.org> To: shocking@houston.rr.com Subject: Re: What's the best PCMCIA Ethernet card? Cc: culverk@wam.umd.edu, bsdx@looksharp.net, hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Sep 2000 14:03:32 CDT." <200009131903.e8DJ3WG07447@bloop.craftncomp.com> References: <200009131903.e8DJ3WG07447@bloop.craftncomp.com> Date: Wed, 13 Sep 2000 13:52:53 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009131903.e8DJ3WG07447@bloop.craftncomp.com> Stephen Hocking writes: : The card's a "Megahertz (CC10BT/2)", according to pccardd. I had to manually : put the IRQ in the /etc/pccard.conf file. The kernel code is from the : PRE_SMPng tag. Hmmm - I kind of suspect interrupt issues. The dmesg is as : follows, the card doesn't seem to load up if I dont have a "device sn" in the : config file. I'm not sure why it's not seen when loaded as a module. I do have : "COMPAT_OLDISA" and "COMPAT_OLDPCI" defined in there (don't ask, I think I was : planning on using the old sound drivers at one stage). This may be why : interrupts are being dropped. OK. My card identifies itself as the same thing. Here's my pccard.conf entry: card "Megahertz" "CC10BT/2" config 0x1 "sn" ? ether attr2 insert /etc/pccard_ether $device logstr "Warner's Oddball sn card" Well, ok, the logstr isn't quite accurate, but I wanted to test it vs the default log string. Otherwise I think it is the same as in the default pccard.conf. 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 13 13:14:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 1042537B423 for ; Wed, 13 Sep 2000 13:14:27 -0700 (PDT) Received: from hermes.tue.nl (hermes.tue.nl [131.155.2.46]) by mailhost.tue.nl (8.11.0/8.11.0) with ESMTP id e8DKEQN11596 for ; Wed, 13 Sep 2000 22:14:26 +0200 (MDT) Received: from deathstar (n9.dial.tue.nl [131.155.209.8]) by hermes.tue.nl (Postfix) with ESMTP id 41FDD2E802 for ; Wed, 13 Sep 2000 22:14:25 +0200 (CEST) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Wed, 13 Sep 2000 22:14:41 +0100 Subject: ENTER allowed? X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000913201425.41FDD2E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Linux, use of the Enter is not allowed because of the internals of stack page fault handlers. Is this also the case on FreeBSD (3.x + )? Marco van de Voort (MarcoV@Stack.nl or marco@freepascal.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 13 13:32:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tistix.ratp.fr (tistix.ratp.fr [62.160.169.66]) by hub.freebsd.org (Postfix) with ESMTP id 3FC7F37B43C; Wed, 13 Sep 2000 13:32:12 -0700 (PDT) Received: from nyplic12.neuilly.ratp (mail.ratp.fr [62.160.169.132]) by tistix.ratp.fr with ESMTP id WAA20852 ; Wed, 13 Sep 2000 22:32:10 +0200 (DST) From: Received: by nyplic12.neuilly.ratp with Internet Mail Service (5.5.2650.21) id ; Wed, 13 Sep 2000 22:33:32 +0100 Message-ID: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 Date: Wed, 13 Sep 2000 22:33:17 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We are trying to create a dynamic library of extensions to PHP 4.02. This library implements a C++ class and has a C interface using the "Extern C" declaration. This library is linked with libstdc++.so.3 . If the library is called in a C program => no trouble. If the library is called from PHP with the "dlopen()" function => [Warning: Unable to load dynamic library '/users/em/ftp/php/test_cpp/debug/libphptest.so' - /usr/lib/libstdc++.so.3: Undefined symbol "__ti9exception" in /usr/local/httpd/htdocs/www/Iti_q/testso.php on line 2 Fatal error: Call to undefined function: php_get_session_id() in /usr/local/httpd/htdocs/www/Iti_q/testso.php on line 3] This problem appears on FreeBSD 4.1 and a PRE_SMPNG -current(FBSD 3.4 is ok). Does this sounds like a known problem ? Do you have any idea of what can be wrong ? Thanks in advance. Janick Taillandier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 13:35:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8808F37B50E for ; Wed, 13 Sep 2000 13:34:38 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA28927; Wed, 13 Sep 2000 13:34:27 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA00651; Wed, 13 Sep 2000 13:34:27 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Sep 2000 13:34:27 -0700 (PDT) Message-Id: <200009132034.NAA00651@vashon.polstra.com> To: hackers@freebsd.org Cc: cobra@ceid.upatras.gr Subject: Re: ports cvsup In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Balis George wrote: > Thank you very much John but it seems that my problem got solved > when i specified: ports-all instead of specifying individual ones. Really?! OK, that's a good clue. I suspect the problem is one of two things: - You are using the "-s" option on the cvsup command line, but you have modified a file locally, or - One of your "checkouts.*" files (most likely the "ports-base" one) is corrupted. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 13:53: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ertpg14e1.nortelnetworks.com (ertpg14e1.nortelnetworks.com [47.234.0.35]) by hub.freebsd.org (Postfix) with ESMTP id 5419A37B424; Wed, 13 Sep 2000 13:52:59 -0700 (PDT) Received: from zrtpd004.us.nortel.com (actually zrtpd004) by ertpg14e1.nortelnetworks.com; Wed, 13 Sep 2000 16:52:33 -0400 Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2652.35) id ; Wed, 13 Sep 2000 16:52:32 -0400 Message-ID: From: "Hao Zhang" To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: need a recommendation of NIC Date: Wed, 13 Sep 2000 16:52:29 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C01DC4.87B53850" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C01DC4.87B53850 Content-Type: text/plain; charset="iso-8859-1" I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets thru FreeBSD routers. It's found that the duplications happened in FreeBSD router. Now The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. To isolate this problem. We will try different NIC. Can anyone give me some recommendation for the high performance NIC for FreeBSD 3.3. Thanks in advance for any comments. -Hao ------_=_NextPart_001_01C01DC4.87B53850 Content-Type: text/html; charset="iso-8859-1" need a recommendation of NIC

I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets
thru FreeBSD routers. It's found that the duplications happened in FreeBSD router.
Now The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. To isolate this
problem. We will try different NIC. Can anyone give me some recommendation for the
high performance NIC for FreeBSD 3.3. Thanks in advance for any comments.

-Hao

------_=_NextPart_001_01C01DC4.87B53850-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 14:31: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id C2BA837B422 for ; Wed, 13 Sep 2000 14:30:59 -0700 (PDT) Received: from ny1wsh031 (blackhole.cioe.com [204.120.165.44]) (authenticated) by virtual-voodoo.com (8.11.0/8.11.0) with ESMTP id e8DLUxN56092 for ; Wed, 13 Sep 2000 16:30:59 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <078601c01dc9$e857bcf0$8a1a050a@winstar.com> From: "Steven E. Ames" To: Subject: rcp -x Date: Wed, 13 Sep 2000 16:30:58 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The man page for rcp(1) lists a '-x' option: -x Turn on DES encryption for all data passed by rcp. This may im- pact response time and CPU utilization, but provides increased security. But the command line doesn't seem to honor it? winrad3# rcp -x rcp: illegal option -- x usage: rcp [-p] f1 f2 rcp [-pr] f1 ... fn directory ditto -K and -k. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 15:23: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EE1B737B423 for ; Wed, 13 Sep 2000 15:22:57 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id SAA38200; Wed, 13 Sep 2000 18:22:54 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 13 Sep 2000 18:22:53 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Steven E. Ames" Cc: freebsd-hackers@freebsd.org Subject: Re: rcp -x In-Reply-To: <078601c01dc9$e857bcf0$8a1a050a@winstar.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 The -x options on rsh, rcp, and rlogin rely on Kerberos support, which it appears you haven't installed. (example w/o kerberos installed) > rcp -x rcp: illegal option -- x usage: rcp [-p] f1 f2 rcp [-pr] f1 ... fn directory (example w/kerberos installed) > rcp -x usage: rcp [-Kpx] [-k realm] f1 f2 rcp [-Kprx] [-k realm] f1 ... fn directory There's a tutorial on setting up Kerberos in the handbook, although it may be out of date. However, Kerberos involves substantial administrative overhead -- if you're not interested in that, try using SSH. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services On Wed, 13 Sep 2000, Steven E. Ames wrote: > The man page for rcp(1) lists a '-x' option: > > -x Turn on DES encryption for all data passed by rcp. This may > im- > pact response time and CPU utilization, but provides > increased > security. > > But the command line doesn't seem to honor it? > > winrad3# rcp -x > rcp: illegal option -- x > usage: rcp [-p] f1 f2 > rcp [-pr] f1 ... fn directory > > ditto -K and -k. > > -Steve > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 15:30:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [63.147.8.7]) by hub.freebsd.org (Postfix) with ESMTP id AFAF937B43C for ; Wed, 13 Sep 2000 15:30:34 -0700 (PDT) Received: from Spaz.HuntsvilleAL.COM (spaz.huntsvilleal.com [63.147.8.31]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id RAA23840; Wed, 13 Sep 2000 17:02:54 -0400 Received: from Barricuda.Catonic.NET (barricuda [216.126.175.226]) by Spaz.HuntsvilleAL.COM (8.9.3/8.9.3) with ESMTP id WAA39043; Wed, 13 Sep 2000 22:29:54 GMT (envelope-from kris@catonic.net) Received: from localhost (localhost [127.0.0.1]) by Barricuda.Catonic.NET (8.9.3/8.9.3) with ESMTP id RAA12656; Wed, 13 Sep 2000 17:29:51 -0500 (CDT) (envelope-from kris@barricuda.catonic.net) Date: Wed, 13 Sep 2000 17:29:46 -0500 (CDT) From: Kris Kirby To: Stephen Hocking Cc: hackers@FreeBSD.ORG Subject: Re: What's the best PCMCIA Ethernet card? In-Reply-To: <200009102007.e8AK7KG15668@bloop.craftncomp.com> Message-ID: X-Tech-Support-Email: bofh@catonic.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, Stephen Hocking wrote: > My main reason for wanting to replace the wretched thing is that it > keeps on hanging when doing lots of writes under NFS (when it's a > client), even when the write size is reduced to 2k. Everyone's > currently banging away at the new SMP code, so rather than plague Bill > Paul with requests about the if_sn driver, I'm thinking of just > getting a more reliable card. This comes to mind: mount_nfs -s -r 1024 -w 1024 -t 30 Whenever I use 10Mbit LAN for NFS, I use 1K blocksizes. This dates back from me installing FreeBSD 2.2.5 on a 486/33 from a 386-16 luggable. That and FreeBSD doesn't seize to badly waiting for NFS. ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 15:34:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 53FFD37B424 for ; Wed, 13 Sep 2000 15:34:39 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8DMYcs08633 for ; Wed, 13 Sep 2000 15:34:38 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma008629; Wed, 13 Sep 2000 15:34:17 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id PAA87368 for freebsd-hackers@freebsd.org; Wed, 13 Sep 2000 15:34:17 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009132234.PAA87368@bubba.whistle.com> Subject: c++ error To: freebsd-hackers@freebsd.org Date: Wed, 13 Sep 2000 15:34:17 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happens on 4.1-RELEASE: $ c++ ... foo.cc /usr/include/netinet/in.h:303: ANSI C++ forbids data member `ip_opts' with same name as enclosing class *** Error code 1 Any ideas? I tried __BEGIN_DECLS and __END_DECLS but that didn't help. I'm not a C++ expert. $ c++ --version $ 2.95.2 Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 16:59: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 71E3337B423 for ; Wed, 13 Sep 2000 16:59:01 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA29589; Wed, 13 Sep 2000 16:58:53 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA01085; Wed, 13 Sep 2000 16:58:53 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Sep 2000 16:58:53 -0700 (PDT) Message-Id: <200009132358.QAA01085@vashon.polstra.com> To: hackers@freebsd.org Cc: archie@whistle.com Subject: Re: c++ error In-Reply-To: <200009132234.PAA87368@bubba.whistle.com> References: <200009132234.PAA87368@bubba.whistle.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009132234.PAA87368@bubba.whistle.com>, Archie Cobbs wrote: > This happens on 4.1-RELEASE: > > $ c++ ... foo.cc > > /usr/include/netinet/in.h:303: ANSI C++ forbids data member `ip_opts' with same name as enclosing class > *** Error code 1 > > Any ideas? I tried __BEGIN_DECLS and __END_DECLS but that didn't help. > I'm not a C++ expert. > > $ c++ --version > $ 2.95.2 I can't duplicate it with this "program": #include #include I compile it with "cc -c test.cc" and get no errors. The diagnostic is valid, but there is a kludge in the compiler to make it work anyway. See "src/contrib/gcc.295/cp/decl.c" around line 11515: /* 9.2p13 [class.mem] */ if (declarator == constructor_name (current_class_type) /* Divergence from the standard: In extern "C", we allow non-static data members here, because C does and /usr/include/netinet/in.h uses that. */ && (staticp || ! in_system_header)) cp_pedwarn ("ANSI C++ forbids data member `%D' with same name as enclosing class", declarator); Notice that it is permissive if the declaration is in a "system header". This seems to work right, because if I create a local directory "netinet" containing a copy of "in.h" and add "-I." to the command line, then I get the diagnostic. Is this the standard compiler installation, or are you using the ports version? If it's the ports version, maybe it has an incorrect notion of where the system headers are. I ran my tests using the standard FreeBSD compiler installation. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 17:10:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 94F3637B424 for ; Wed, 13 Sep 2000 17:10:54 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8E0ACe09682; Wed, 13 Sep 2000 17:10:12 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009680; Wed, 13 Sep 2000 17:10:10 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id RAA04731; Wed, 13 Sep 2000 17:10:10 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009140010.RAA04731@bubba.whistle.com> Subject: Re: c++ error In-Reply-To: <200009132358.QAA01085@vashon.polstra.com> "from John Polstra at Sep 13, 2000 04:58:53 pm" To: John Polstra Date: Wed, 13 Sep 2000 17:10:10 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > > This happens on 4.1-RELEASE: > > > > $ c++ ... foo.cc > > > > /usr/include/netinet/in.h:303: ANSI C++ forbids data member `ip_opts' with same name as enclosing class > > *** Error code 1 > > > > Any ideas? I tried __BEGIN_DECLS and __END_DECLS but that didn't help. > > I'm not a C++ expert. > > > > $ c++ --version > > $ 2.95.2 > > I can't duplicate it with this "program": > > #include > #include > > I compile it with "cc -c test.cc" and get no errors. The diagnostic Same here. > is valid, but there is a kludge in the compiler to make it work > anyway. See "src/contrib/gcc.295/cp/decl.c" around line 11515: > > /* 9.2p13 [class.mem] */ > if (declarator == constructor_name (current_class_type) > /* Divergence from the standard: In extern "C", we > allow non-static data members here, because C does > and /usr/include/netinet/in.h uses that. */ > && (staticp || ! in_system_header)) > cp_pedwarn ("ANSI C++ forbids data member `%D' with same name as enclosing class", > declarator); That is a kludge if I ever saw one!! > Notice that it is permissive if the declaration is in a "system > header". This seems to work right, because if I create a local > directory "netinet" containing a copy of "in.h" and add "-I." to the > command line, then I get the diagnostic. > > Is this the standard compiler installation, or are you using the ports > version? If it's the ports version, maybe it has an incorrect notion > of where the system headers are. I ran my tests using the standard > FreeBSD compiler installation. This is the standard compiler in 4.1. However, the particular source files being compiled are messy and it wouldn't surprise me that they are triggering something. On the other hand, nothing in the kernel actually uses "struct ip_opts", though I haven't checked all of userland.. so we may just be able to remove it. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 17:16:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CEB0537B423 for ; Wed, 13 Sep 2000 17:16:48 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA29675; Wed, 13 Sep 2000 17:16:47 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA01182; Wed, 13 Sep 2000 17:16:46 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Sep 2000 17:16:46 -0700 (PDT) Message-Id: <200009140016.RAA01182@vashon.polstra.com> To: hackers@freebsd.org Cc: archie@whistle.com Subject: Re: c++ error In-Reply-To: <200009140010.RAA04731@bubba.whistle.com> References: <200009140010.RAA04731@bubba.whistle.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009140010.RAA04731@bubba.whistle.com>, Archie Cobbs wrote: > > That is a kludge if I ever saw one!! Yep, it sure is! > This is the standard compiler in 4.1. However, the particular source > files being compiled are messy and it wouldn't surprise me that > they are triggering something. There is something strange (buggy) about the way the compiler is doing the checks. I saw some inconsistent behavior which I couldn't explain. > On the other hand, nothing in the kernel actually uses "struct ip_opts", > though I haven't checked all of userland.. so we may just be able to > remove it. From it looks like a couple of [gs]etsockopt calls use it. Search for "ip_opts" just past that structure declaration. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 17:20:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 6C32637B424 for ; Wed, 13 Sep 2000 17:20:15 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8E0Jh709773; Wed, 13 Sep 2000 17:19:43 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009771; Wed, 13 Sep 2000 17:19:25 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id RAA04988; Wed, 13 Sep 2000 17:19:25 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009140019.RAA04988@bubba.whistle.com> Subject: Re: c++ error In-Reply-To: <200009140016.RAA01182@vashon.polstra.com> "from John Polstra at Sep 13, 2000 05:16:46 pm" To: John Polstra Date: Wed, 13 Sep 2000 17:19:25 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > > On the other hand, nothing in the kernel actually uses "struct ip_opts", > > though I haven't checked all of userland.. so we may just be able to > > remove it. > > >From it looks like a couple of [gs]etsockopt calls > use it. Search for "ip_opts" just past that structure declaration. Oh, duh.. I was only checking C files.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 17:23:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail20.bigmailbox.com (mail20.bigmailbox.com [209.132.220.51]) by hub.freebsd.org (Postfix) with ESMTP id 26EF337B423 for ; Wed, 13 Sep 2000 17:23:51 -0700 (PDT) Received: œby mail20.bigmailbox.com (8.8.7/8.8.7) id RAA20791; Wed, 13 Sep 2000 17:28:10 -0700 Date: Wed, 13 Sep 2000 17:28:10 -0700 Message-Id: <200009140028.RAA20791@mail20.bigmailbox.com> Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: MIME-tools 4.104 (Entity 4.116) Mime-Version: 1.0 X-Originating-Ip: [4.33.194.94] From: "Nathaniel G H" To: freebsd-hackers@freebsd.org Subject: graphics adapter ports reference Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I have been pulling my hair out for a while with some low level code I'm writing, and I'd like some help. Hardware ports 3D0h through 3DFh (controlled by the IN and OUT instructions) can be used to control the graphics adapter. I need some sort of reference material that can at least hint at what these ports do. (I only need to work with standard EGA/VGA text-mode functions, not anything really fancy.) Please help me find some material like this, or let me know where I should ask. I have already figured out that search engines don't help much with this, and most everybody's code that I examined wasn't commented well enough to give me the clues I need. Any help will be greatly appreciated. Kind regards, Nathaniel G H ------------------------------------------------------------ Free email: http://BeMail.org/ Free BeOS: http://free.be.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 13 17:36:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id BC48E37B423 for ; Wed, 13 Sep 2000 17:36:08 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA29750; Wed, 13 Sep 2000 17:36:06 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA01292; Wed, 13 Sep 2000 17:36:05 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Sep 2000 17:36:05 -0700 (PDT) Message-Id: <200009140036.RAA01292@vashon.polstra.com> To: hackers@freebsd.org Cc: archie@whistle.com Subject: Re: c++ error In-Reply-To: <200009140019.RAA04988@bubba.whistle.com> References: <200009140019.RAA04988@bubba.whistle.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009140019.RAA04988@bubba.whistle.com>, Archie Cobbs wrote: > John Polstra writes: > > > On the other hand, nothing in the kernel actually uses "struct ip_opts", > > > though I haven't checked all of userland.. so we may just be able to > > > remove it. > > > > >From it looks like a couple of [gs]etsockopt calls > > use it. Search for "ip_opts" just past that structure declaration. > > Oh, duh.. I was only checking C files.. About the best fix I can think of (and it's not very good) is to change so the structure is declared like this: struct ip_opts { struct in_addr ip_dst; /* first hop, 0 w/o src rt */ #ifdef __cplusplus char ip_optbuf[40]; /* actually variable in size */ #else char ip_opts[40]; /* actually variable in size */ #endif }; This shouldn't break any C++ code, since it already wouldn't compile anyway. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 17:49:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A9EE537B422 for ; Wed, 13 Sep 2000 17:49:20 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA29801; Wed, 13 Sep 2000 17:49:11 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA01334; Wed, 13 Sep 2000 17:49:11 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Sep 2000 17:49:11 -0700 (PDT) Message-Id: <200009140049.RAA01334@vashon.polstra.com> To: hackers@freebsd.org Cc: Janick.Taillandier@ratp.fr Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp>, wrote: > We are trying to create a dynamic library of extensions to PHP 4.02. > This library implements a C++ class and has a C interface using the "Extern C" > declaration. > This library is linked with libstdc++.so.3 . > > If the library is called in a C program => no trouble. > If the library is called from PHP with the "dlopen()" function => > [Warning: Unable to load dynamic library > '/users/em/ftp/php/test_cpp/debug/libphptest.so' - /usr/lib/libstdc++.so.3: > Undefined symbol "__ti9exception" in > /usr/local/httpd/htdocs/www/Iti_q/testso.php on line 2 This is because FreeBSD uses an archive library "libgcc.a" instead of a shared library. That means that everything from libgcc which is needed by your shared libraries had better already be linked into the main program. The right solution is for us to use a shared library for libgcc. (Note to eager committers: don't do this without coordinating with obrien. There are ramifications that aren't obvious.) As a work-around, try adding this to your main program. (I am assuming it is a C++ program too.) extern void terminate(void); void (*kludge_city)(void) = terminate; Another possibility would be to link explicitly with libgcc when creating your dynamic library: cc -shared -o libphptest.so ... -lgcc That might cause other problems, but probably not. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 18:42:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 3346937B42C for ; Wed, 13 Sep 2000 18:42:43 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id FAA13600; Thu, 14 Sep 2000 05:42:38 +0400 (MSD) Message-Id: <200009140142.FAA13600@aaz.links.ru> Subject: Re: graphics adapter ports reference In-Reply-To: <200009140028.RAA20791@mail20.bigmailbox.com> from "Nathaniel G H" at "Sep 13, 0 05:28:10 pm" To: bsd_appliance@bemail.org (Nathaniel G H) Date: Thu, 14 Sep 2000 05:42:37 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Nathaniel G H writes: > I have been pulling my hair out for a while with some low > level code I'm writing, and I'd like some help. > > Hardware ports 3D0h through 3DFh (controlled by the IN and > OUT instructions) can be used to control the graphics > adapter. I need some sort of reference material that can at > least hint at what these ports do. (I only need to work with > standard EGA/VGA text-mode functions, not anything really > fancy.) > > Please help me find some material like this, or let me know > where I should ask. I have already figured out that search > engines don't help much with this, and most everybody's code > that I examined wasn't commented well enough to give me the > clues I need. Not exactly you want but a little help for test src/usr.sbin/pcvt/vgaio > Any help will be greatly appreciated. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 18:58:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id E632937B423 for ; Wed, 13 Sep 2000 18:58:43 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8E1wYA62900; Thu, 14 Sep 2000 11:28:34 +0930 (CST) (envelope-from grog) Date: Thu, 14 Sep 2000 11:28:34 +0930 From: Greg Lehey To: kts Cc: hackers@FreeBSD.ORG Subject: Re: help debugging kernel crash dump Message-ID: <20000914112834.C45769@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bangel@elite.net on Wed, Sep 13, 2000 at 04:12:14AM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 13 September 2000 at 4:12:14 -0700, kts wrote: > Hi > > Just wanted to see if anyone could give me some feedback as to what > happened, or how to get more info. My machine was just sitting on > the LAN and it panic'd. X was running and it had some ssh's open. > > I'm running 4-STABLE from August 3rd. > > IdlePTD 3522560 > initial pcb at 2ce300 > panicstr: page fault > panic messages: > --- > > dumping to dev #wd/0x20001, offset 278560 > dump ata0: resetting devices .. done > 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 > 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 > 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 > --- > #0 0xc0141ef0 in boot () > (kgdb) bt > #0 0xc0141ef0 in boot () > #1 0xc014228d in panic () > #2 0xc025b166 in trap_fatal () > #3 0xc025ae19 in trap_pfault () > #4 0xc025a9df in trap () > #5 0xc01acb69 in fr_makefrip () > #6 0xc01b2a98 in fr_checkicmpmatchingstate () > #7 0xc01b2cd9 in fr_checkstate () > #8 0xc01ad758 in fr_check () > #9 0xc01a17e8 in ip_output () > #10 0xc019fa6a in icmp_send () > #11 0xc019f9eb in icmp_reflect () > #12 0xc019f314 in icmp_error () > #13 0xc01aa46e in udp_input () > #14 0xc01a0498 in ip_input () > #15 0xc01a050b in ipintr () > #16 0xc024de85 in swi_net_next () > Cannot access memory at address 0x531b6b24. > (kgdb) > > any way I can get more information from that? I know using a kernel > compiled with -g would help, but how would that be done, because > I've been sup'ing my src every day... Yes, a kernel with -g would be a great help. The stack trace suggests a network problem, and possibly somebody with more experience in this area would recognize this signature. To build a kernel with -g, you either run config with the -g option, or better put this into the config file: makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols 'make install' will still install a stripped version, but you'll have the unstripped version to use for crash dumps. Unfortunately, you can't just build a debug kernel from these sources and expect to get the same thing; it seems that there are some minor differences in code generation when you set -g. It's possible, though, that there would be enough similarity that it would help. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 20:11:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uranium.dashmail.net (uranium.dashmail.net [216.36.26.29]) by hub.freebsd.org (Postfix) with ESMTP id 921E537B424 for ; Wed, 13 Sep 2000 20:11:25 -0700 (PDT) Received: from Ptacek (rc1s7p8.dashmail.net [216.36.33.80]) by uranium.dashmail.net (8.10.1/8.10.1) with SMTP id e8E3HKW87526 for ; Thu, 14 Sep 2000 03:17:21 GMT Reply-To: From: "Chris Ptacek" To: Subject: Getting all the IP address for a machine from code... Date: Wed, 13 Sep 2000 20:12:47 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking for a way to get all the IP addresses that are configured a machine. I need to do this in c source code, and without using DNS services (ie: gethostname/gethostbyname won't work). I am hoping there are some system calls I can use to get this information. Thanks in advance for any help. - Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 20:12:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (Postfix) with ESMTP id 54EFB37B422; Wed, 13 Sep 2000 20:12:49 -0700 (PDT) Received: (from chris@localhost) by dei.calldei.com (8.9.3/8.9.0) id UAA22657; Wed, 13 Sep 2000 20:12:48 -0700 (PDT) Date: Wed, 13 Sep 2000 20:12:48 -0700 (PDT) From: Chris Costello Message-Id: <200009140312.UAA22657@dei.calldei.com> To: hackers@FreeBSD.org Subject: Fdescfs updates--coming to a devfs near you! Cc: current@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Over the past few months, I've been working on the /dev/fd file system ("fdescfs"). After weeks of occasionally-hacking and putting it off, I've finalized a patch for fdescfs. What this patch changes: + fdesc_allocvp() becomes curproc-free as a `struct proc' pointer is passed as the new fourth parameter. + All usage of the `DTYPE' open file type macros are removed. Anything whose fo_stat() operation does not return proper fdesc information is broken. The checks for DTYPE_VNODE (for determining whether setattr() will do anything) are replaced by getvnode() so that if the method for determining a vnode from a file entry changes, (hopefully) that's the only place it will happen. There is one loose end I'm not sure I know just how to tie up yet. I'm having trouble modifying src/sys/kern/sys_pipe.c:pipe_stat() to return the right st_mode flags based on various conditions. I'd appreciate it if someone else who knows about the pipe code could point me in the right direction as to what conditions permit reading and what conditions permit writing (and what makes them fail). The patch is available at http://people.FreeBSD.org/~chris/fdesc-dtype.patch, Documentation for it is available at http://people.FreeBSD.org/~chris/fdesc/ all in one page: http://people.FreeBSD.org/~chris/fdesc/article.html |Chris Costello |Press [ESC] to detonate or any other key to explode. `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 21: 2:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 773A037B423 for ; Wed, 13 Sep 2000 21:02:32 -0700 (PDT) Received: by gw.nectar.com (Postfix, from userid 1001) id 25B7D1925D; Wed, 13 Sep 2000 23:02:28 -0500 (CDT) Date: Wed, 13 Sep 2000 23:02:28 -0500 From: "Jacques A. Vidrine" To: John Polstra Cc: hackers@freebsd.org, archie@whistle.com Subject: Re: c++ error Message-ID: <20000913230227.A15302@spawn.nectar.com> References: <200009140019.RAA04988@bubba.whistle.com> <200009140036.RAA01292@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009140036.RAA01292@vashon.polstra.com>; from jdp@polstra.com on Wed, Sep 13, 2000 at 05:36:05PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 13, 2000 at 05:36:05PM -0700, John Polstra wrote: > About the best fix I can think of (and it's not very good) is to > change so the structure is declared like this: > > struct ip_opts { > struct in_addr ip_dst; /* first hop, 0 w/o src rt */ > #ifdef __cplusplus > char ip_optbuf[40]; /* actually variable in size */ > #else > char ip_opts[40]; /* actually variable in size */ > #endif > }; > > This shouldn't break any C++ code, since it already wouldn't compile > anyway. :-) Please see PR bin/13383 before doing anything like this. It addresses a similar situation. I'll comment more tomorrow after some sleep :-) -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 13 21:15:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3278B37B424 for ; Wed, 13 Sep 2000 21:15:56 -0700 (PDT) Received: from solaris.cs.rpi.edu (solaris.cs.rpi.edu [128.213.24.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA80991 for ; Thu, 14 Sep 2000 00:15:54 -0400 (EDT) Message-Id: <200009140415.AAA80991@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: install media problems with latest snapshots Date: Thu, 14 Sep 2000 00:15:54 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest snapshots off of releng4.freebsd.org have a couple of problems with the kern.flp/mfsroot.flp images. The first problem is that the "boot.config" file doesn't exist; this makes serial console installs problematic (although easily fixed). Secondly the 20000913 image has the problem that the mfsminiroot is wacked somehow. The system refuses to mount the md0a partition as the slice size and mediasize are not the same (well, it mounts it, tries to run init which signal 6's, and then the system panic()s). -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 1: 9:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f76.law9.hotmail.com [64.4.9.76]) by hub.freebsd.org (Postfix) with ESMTP id BDA6937B423 for ; Thu, 14 Sep 2000 01:09:24 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 14 Sep 2000 01:09:24 -0700 Received: from 209.246.110.152 by lw9fd.law9.hotmail.msn.com with HTTP; Thu, 14 Sep 2000 08:09:24 GMT X-Originating-IP: [209.246.110.152] From: "gerald stoller" To: freebsd-hackers@FreeBSD.ORG Cc: GS_Stoller@juno.com Subject: HELP: Disk/file-systems are loused up Date: Thu, 14 Sep 2000 04:09:24 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 14 Sep 2000 08:09:24.0487 (UTC) FILETIME=[18302170:01C01E23] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I started up my (version 3.3 ) freeBSD , and the first thing that I did was mount a MSDOS diskette and did a find on it (with -name "*hd*" ). I got three lines of output stating something like 'date error; month (14) out of range', then a long pause (during which I typed several ctl-C's ), and the system crashed. I booted immediately, and the system informed me (after the boot) that the disk is loused up and I should run fsck , which I did. I ran it several times and it didn't fix the problem until I ran fsck -p . I tried the find again, with the same results, but this time I withdrew the floppy during the pause trying for another type of termination to the find (rather than a system crash, I was hoping for a message that the device was inaccessible and that I could respond in such a way that the command would abort). Unfortunately, the system crashed again. This time, no matter what I did with fsck I couldn't get the file systems cleaned up. Any suggestions? Send responses to me here and to me as GS_Stoller@juno.com . _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.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 14 1:12:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id D060C37B424; Thu, 14 Sep 2000 01:12:34 -0700 (PDT) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id QAA28282; Thu, 14 Sep 2000 16:12:22 +0800 Received: from jules.elischer.org (reggae-39-66.nv.iinet.net.au [203.59.173.66]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id QAA00430; Thu, 14 Sep 2000 16:12:17 +0800 Message-ID: <39C0885A.41C67EA6@elischer.org> Date: Thu, 14 Sep 2000 01:12:10 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Chris Costello Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! References: <200009140312.UAA22657@dei.calldei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've never thought of a use for fdescfs... -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 1:56:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 7A07F37B422 for ; Thu, 14 Sep 2000 01:56:23 -0700 (PDT) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Sep 2000 09:56:22 +0100 (BST) Date: Thu, 14 Sep 2000 09:56:22 +0100 From: David Malone To: Chris Ptacek Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Getting all the IP address for a machine from code... Message-ID: <20000914095622.A25929@gosset.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ptacek@dashmail.net on Wed, Sep 13, 2000 at 08:12:47PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 13, 2000 at 08:12:47PM -0700, Chris Ptacek wrote: > I am looking for a way to get all the IP addresses that are configured a > machine. I need to do this in c source code, and without using DNS services > (ie: gethostname/gethostbyname won't work). I am hoping there are some > system calls I can use to get this information. Thanks in advance for any > help. You could use getifaddrs in FreeBSD 4 and later - otherwise you'll need to use sysctl to get the list of interfaces and addresses. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 2:45:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id A99EB37B422 for ; Thu, 14 Sep 2000 02:45:47 -0700 (PDT) Received: (qmail 33108 invoked by uid 1001); 14 Sep 2000 09:39:45 -0000 Date: Thu, 14 Sep 2000 12:39:45 +0300 From: Peter Pentchev To: Julian Elischer Cc: Chris Costello , hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <20000914123945.A32524@ringwraith.office1.bg> References: <200009140312.UAA22657@dei.calldei.com> <39C0885A.41C67EA6@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39C0885A.41C67EA6@elischer.org>; from julian@elischer.org on Thu, Sep 14, 2000 at 01:12:10AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: > I've never thought of a use for fdescfs... Well.. just a trivial example - imagine a program which takes a filename as an argument; imagine yourself trying to pipe something into it - passing /dev/fd/0 as a filename to process would do the trick. G'luck, Peter -- .sith ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 2:49:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 4231637B424; Thu, 14 Sep 2000 02:49:09 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8E9mwN56078; Thu, 14 Sep 2000 11:48:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Pentchev Cc: Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of "Thu, 14 Sep 2000 12:39:45 +0300." <20000914123945.A32524@ringwraith.office1.bg> Date: Thu, 14 Sep 2000 11:48:58 +0200 Message-ID: <56076.968924938@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000914123945.A32524@ringwraith.office1.bg>, Peter Pentchev writes : >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: >> I've never thought of a use for fdescfs... > >Well.. just a trivial example - imagine a program which takes a filename >as an argument; imagine yourself trying to pipe something into it - >passing /dev/fd/0 as a filename to process would do the trick. I must admit that I think in general that /dev/std{in,out,err} and /dev/fd is bogus. It looks like something which happened "because we can" more than something which has a legitimate need. If anything I would propose we ditch it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 5:29:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 8816637B422; Thu, 14 Sep 2000 05:29:33 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13ZWeE-0006UB-00; Thu, 14 Sep 2000 11:53:42 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id LAA92642; Thu, 14 Sep 2000 11:53:42 +0100 (BST) (envelope-from ben) Date: Thu, 14 Sep 2000 11:53:42 +0100 From: Ben Smithurst To: Poul-Henning Kamp Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <20000914115342.I77593@strontium.scientia.demon.co.uk> References: <20000914123945.A32524@ringwraith.office1.bg> <56076.968924938@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <56076.968924938@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. You think adding a hack to every program to support "-" to mean stdout/stdin is better? It seems to be that saying "/dev/stdin" when you mean stdin is better than saying "-" and hoping the application handles that correctly. Of course many programs will read stdin by default, and write stdout by default, but that doesn't help when you want to read more than one file, one of which is stdin. > If anything I would propose we ditch it... And break loads of scripts at the same time? -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 5:37:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 6B0DE37B422; Thu, 14 Sep 2000 05:37:07 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8ECb6N56647; Thu, 14 Sep 2000 14:37:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ben Smithurst Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of "Thu, 14 Sep 2000 11:53:42 BST." <20000914115342.I77593@strontium.scientia.demon.co.uk> Date: Thu, 14 Sep 2000 14:37:06 +0200 Message-ID: <56645.968935026@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000914115342.I77593@strontium.scientia.demon.co.uk>, Ben Smithurs t writes: >Poul-Henning Kamp wrote: > >> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd >> is bogus. It looks like something which happened "because we can" more >> than something which has a legitimate need. > >You think adding a hack to every program to support "-" to mean >stdout/stdin is better? The majority of these programs could be handled by adding knowledge of "-" as a magic filename to fopen(3). At the same time I would really love if we implemented "|.*" to mean "do an popen(3)" instead. But of course, this is bikeshed material... >> If anything I would propose we ditch it... > >And break loads of scripts at the same time? I would argue that the programs and the scripts that call them are already broken, but hey... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 5:50:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lobster.baynetworks.com (ns3.BayNetworks.COM [192.32.253.3]) by hub.freebsd.org (Postfix) with ESMTP id 055C437B42C; Thu, 14 Sep 2000 05:49:59 -0700 (PDT) Received: from mailhost.BayNetworks.COM (ns4.baynetworks.com [132.245.135.84]) by lobster.baynetworks.com (8.9.1/8.9.1) with ESMTP id IAA18319; Thu, 14 Sep 2000 08:47:41 -0400 (EDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id IAA19909; Thu, 14 Sep 2000 08:43:04 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id IAA18449; Thu, 14 Sep 2000 08:43:04 -0400 for Message-Id: <200009141243.IAA18449@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message from Poul-Henning Kamp of "Thu, 14 Sep 2000 14:37:06 +0200." <56645.968935026@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 08:43:04 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG phk@critter.freebsd.dk said: :- The majority of these programs could be handled by adding knowledge of :- "-" as a magic filename to fopen(3). Suppose I *want* a filename called "-"? My tough luck, huh? I *like* /dev/stdin. It's orthogonal! -- Robert Withrow -- (+1 978 288 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 14 6: 4:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from messagereach.com (memailout3.messagereach.com [205.183.255.234]) by hub.freebsd.org (Postfix) with ESMTP id 15C2B37B43E for ; Thu, 14 Sep 2000 06:03:54 -0700 (PDT) Received: from [205.183.255.234] (HELO memailout3) by messagereach.com (CommuniGate Pro SMTP 3.2b7) with ESMTP id 5668721 for freebsd-hackers@FreeBSD.org; Thu, 14 Sep 2000 09:03:48 -0400 To: freebsd-hackers@FreeBSD.org From: STS Marketing GmbH Subject: =?ISO-8859-1?Q?Die_=FCber_350_besten_Marketing-Praxis-Checklisten_...?= Mime-Version: 1.0 Message-Id: Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 14 Sep 2000 09:03:48 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG

Mehr Effizienz und Erfolg mit den besten Marketing-Praxis-Checklisten

Liebe Marketingverantwortliche

Stellen Sie sich vor, Sie m=FCssten bis morgen um 10.00 Uhr ein
erfolgsversprechendes Messekonzept pr=E4sentieren.

Oder kreative Ideen f=FCr die n=E4chste Direct-Mail-Aktion und bis in
zwei Tagen Vorschl=E4ge f=FCr ein erfolgreiches Internetmarketing
vorlegen. Und dies nat=FCrlich neben dem =FCblichen Alltagsgesch=E4ft!

Kein Problem mit unseren Marketing-Praxis-Checklisten. Sie sorgen
daf=FCr, dass Sie bei Ihrer t=E4glichen Arbeit entlastet werden und steigern
den Erfolg Ihrer Marketingaktivit=E4ten. Die Checklisten sind f=FCr
Fr. 145.00/St=FCck erh=E4ltlich und damit bereits nach der ersten Anwendung
amortisiert!

Schauen Sie bei uns rein und =FCberzeugen Sie sich von den Vorteilen des
Marketing-Checklisten-Managers, als Handbuch oder CD-Rom erh=E4ltlich:

http://www.stsmarketing.ch

Wir freuen uns auf Ihren Besuch.

Gruss
Stefan Schmidlin
Eid. dipl. Marketingleiter


P.S.: Lassen Sie sich anhand von 5 kostenlosen Checklisten nach ihrer
Wahl von der Qualit=E4t der Marketing-Checklisten-Sammlung =FCberzeugen.



This message was sent to you by Stefan Schmidlin, STS Marketing <= /p>

---------------------------------------------------------------------
Diese Nachricht wurde via MessageREACH versendet.
Wenn Sie keine weiteren Emails von diesem Empfaenger wuenschen:
1. Klicken Sie auf Antworten.
2. Ersetzen Sie den Text in der Betreff-Zeile durch REMOVE.
3. Klicken Sie auf Senden.
Sie werden ein letztes Mal eine Email mit einer Bestaetigung erhalten.
---------------------------------------------------------------------
This message was sent using the MessageREACH Service.
If you would prefer not to receive further messages from this sender:
1. Click on the Reply button.
2. Replace the Subject field with the word REMOVE.
3. Click the Send button.
You will receive one additional e-mail message confirming your removal.<= br>

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 6:30:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 7935A37B42C for ; Thu, 14 Sep 2000 06:30:33 -0700 (PDT) Received: by gw.nectar.com (Postfix, from userid 1001) id 36B8D1925D; Thu, 14 Sep 2000 08:30:32 -0500 (CDT) Date: Thu, 14 Sep 2000 08:30:32 -0500 From: "Jacques A. Vidrine" To: archie@whistle.com Cc: hackers@freebsd.org, John Polstra Subject: Re: c++ error Message-ID: <20000914083032.B16624@spawn.nectar.com> References: <200009140019.RAA04988@bubba.whistle.com> <200009140036.RAA01292@vashon.polstra.com> <20000913230227.A15302@spawn.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000913230227.A15302@spawn.nectar.com>; from n@nectar.com on Wed, Sep 13, 2000 at 11:02:28PM -0500 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 13, 2000 at 11:02:28PM -0500, Jacques A. Vidrine wrote: > Please see PR bin/13383 before doing anything like this. It addresses > a similar situation. I'll comment more tomorrow after some sleep :-) I knew I needed some sleep. It ``addressess'' the exact same situation. In summary, gcc has a kluge to work around a bug in the C++ standard. It looks like you and Justin have both found edge cases where the gcc kluge loses. If you can come up with a reasonable test case that reproduces the problem, perhaps it can be PR'd to the GCC folks? As per the PR, I'm against #ifdef'ing structures like ip_opts for C++, since it is likely that a later C++ standard will be corrected. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 6:40:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hwang112.ibt.nctu.edu.tw (Hwang112.IBT.NCTU.edu.tw [140.113.173.112]) by hub.freebsd.org (Postfix) with ESMTP id 93BEF37B43E for ; Thu, 14 Sep 2000 06:40:25 -0700 (PDT) Received: (from frankch@localhost) by hwang112.ibt.nctu.edu.tw (8.9.3/8.9.3) id VAA00398 for freebsd-hackers@freebsd.org; Thu, 14 Sep 2000 21:36:47 +0800 (CST) (envelope-from frankch) Date: Thu, 14 Sep 2000 21:36:46 +0800 From: Frank Chen-hsiung Chn To: freebsd-hackers@freebsd.org Subject: 4.1 PCMCIA on IBM ThinkPad A20p Message-ID: <20000914213646.A372@waru.life.nthu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, We recently got one IBM ThinkPad A20p. This might be the top notebook so far. However, we could not make the pccard services work. We have tested some cards, including D-Link DFE-650, a fast ethernet adaptor, and Compaq WL100, a 802.11b wireless NIC, also a generic ata controller (it is actually a SmartMedia to PC Card adaptor). FreeBSD sees these cards. It could identify the card, but the driver allocation failed (at least for the ATA card). For D-Link DFE-650, ifconfig get a ed0 timeout message, ifconfig could assign inet address, but it could not provide media information. The same for Compaq WL100, which uses wi0 driver. Somehow the MAC address reported by wi0 driver for WL100 diffs every time, strange. A20p use TI 1450 pcic controller. The dmesg is attached below. Could someone provide some hints on how to solve this? We think this is a generic PC Card problem related to perhaps the unsupported TI PCI-1450 CardBus Bridge? Oh, none of the cards above are cardbus cards. We also try some cardbus cards, they can not be recognized by freebsd. ===== dmesg begins here ===== real memory = 536870912 (524288K bytes) avail memory = 519606272 (507428K bytes) Preloaded elf kernel "kernel" at 0xc032e000. module_register_init: MOD_LOAD (vesa, c02469e0, 0) error 6 Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pcic-pci0: mem 0x50000000-0x50000fff irq 11 at device 2.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pcic-pci1: mem 0x50100000-0x50100fff irq 11 at device 2.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pci0: (vendor=0x11c1, dev=0x0449) at 3.0 irq 11 csa0: mem 0xf0100000-0xf01fffff,0xf0003000-0xf0003fff irq 11 at device 5.0 on pci0 pcm0: on csa0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1c10-0x1c1f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1c20-0x1c3f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: port 0x1040-0x104f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 1040 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 1000 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 pca0 at port 0x40 on isa0 pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 ad0: 19077MB [41344/15/63] at ata0-master using UDMA33 acd0: DVD-ROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a pccard: card inserted, slot 1 wi0: at port 0x240-0x27f irq 10 slot 1 on pccard1 wi0: Ethernet address: 80:72:25:c1:00:99 ===== dmesg ends here ===== -- Chen-Hsiung Chan [¸âÂíşľ](BIG5) Department of Life Science http://waru.life.nthu.edu.tw/~frankch/ National Tsing Hua University email: frankch@waru.life.nthu.edu.tw Taiwan phone: 03-5715131#3482 fax: 03-5715934 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 6:40:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by hub.freebsd.org (Postfix) with ESMTP id 1FF6237B423; Thu, 14 Sep 2000 06:40:53 -0700 (PDT) Received: (from bygg@localhost) by nic.cafax.se (8.10.2/8.11.0.Gamma1) id e8EDegD10045; Thu, 14 Sep 2000 15:40:42 +0200 (MEST) Date: Thu, 14 Sep 100 15:40:42 WET DST From: Johnny Eriksson To: Robert Withrow Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of Thu, 14 Sep 2000 08:43:04 -0400 Message-ID: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > phk@critter.freebsd.dk said: > :- The majority of these programs could be handled by adding knowledge of > :- "-" as a magic filename to fopen(3). > > Suppose I *want* a filename called "-"? My tough luck, huh? Could you settle for "./-"? > Robert Withrow -- (+1 978 288 8256) > BWithrow@BayNetworks.com --Johnny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 6:54:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id 0C66337B42C; Thu, 14 Sep 2000 06:54:47 -0700 (PDT) Received: from theta.dante.org.uk ([193.63.211.7]) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 13ZZTP-00070a-00; Thu, 14 Sep 2000 14:54:43 +0100 Received: from localhost ([127.0.0.1] helo=dante.org.uk) by theta.dante.org.uk with esmtp (Exim 3.12 #4) id 13ZZTM-000332-00; Thu, 14 Sep 2000 14:54:40 +0100 Message-ID: <39C0D8A0.3BDC3B6C@dante.org.uk> Date: Thu, 14 Sep 2000 14:54:40 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Networking Service to Europe Ltd. X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en, ru MIME-Version: 1.0 To: Johnny Eriksson , hackers@freebsd.org, current@freebsd.org Subject: /proc & /dev/std* [Was: Fdescfs updates--coming to a devfs near you!] References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johnny Eriksson wrote: > > phk@critter.freebsd.dk said: > > :- The majority of these programs could be handled by adding knowledge of > > :- "-" as a magic filename to fopen(3). > > > > Suppose I *want* a filename called "-"? My tough luck, huh? > > Could you settle for "./-"? > I think any "magic" name is not very good idea. To say more, it breaks POSIX. File names are a tratitional UNIX way to access character and block devices; in System V you can access much more via file names, using streams. Magic numbers are for MS DOS (remember COM1 and LPT1? :-) I am not sure /proc/ names are very useful, but /dev/std{in|out|err} definitely are. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 6:57: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.smed.com (smtp.smed.com [12.20.51.11]) by hub.freebsd.org (Postfix) with ESMTP id 5D41C37B422 for ; Thu, 14 Sep 2000 06:56:57 -0700 (PDT) Received: from smtpgate.shrmed.com (keymaster.smed.com [12.20.51.2]) by smtp.smed.com (Postfix) with ESMTP id DC22516473 for ; Thu, 14 Sep 2000 09:56:54 -0400 (EDT) Received: from iesa14.shrmed.com (iesa14.shrmed.com [10.1.99.114]) by smtpgate.shrmed.com (8.9.3/8.9.3) with ESMTP id JAA28497 for ; Thu, 14 Sep 2000 09:56:53 -0400 From: Joe.Warner@smed.com Received: from Deimos.smed.com (unverified) by iesa14.shrmed.com (Content Technologies SMTPRS 2.0.15) with SMTP id ; Thu, 14 Sep 2000 09:52:30 -0400 Received: by Deimos.smed.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 8525695A.004C133D ; Thu, 14 Sep 2000 09:50:56 -0400 X-Lotus-FromDomain: SMS To: freebsd-hackers@freebsd.org Cc: RichardLe@pcmall.com Message-Id: <8525695A.004C10AB.00@Deimos.smed.com> Date: Thu, 14 Sep 2000 07:53:19 -0600 Subject: /dev/cuaa0 locks my system up..Help! MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I'm posting this here as a last resort. I've already done a search of the freebsd mailing lists and have posted several times to freebsd-questions but haven't received any information that has helped me resolve this problem. A while back, while trying to get my APC Smart-UPS 1000 to talk to my FreeBSD 3.4 system, I encountered a problem with the serial port. This problem inspired my to write an article that was published at this months edition of daemonnews. http://www.daemonnews.org/200009/adventure.html Regardless of what application I use to access my serial port (/dev/cuaa0), when I do, it causes my system to freeze up. CTRL + ALT + BACKSPACE doesn't work, CTRL + ALT + F2 doesn't work,..you get the picture. When my system freezes like this, my only alternative is to do a cold reboot and I don't think this is too healthy a practice for any OS. After trying kermit to see if I can, at least, talk to the serial port, I get the same results when trying to connect. Someone suggested I also try minicom but I couldn't get it installed. It timed out when trying to access the ftp sites listed in the Makefile. I also tried to download and install a newer version but couldn't get that to work either. Possibly because my ports need to be updated. I've scoured the contents of all my logs and haven't found any error message that would give a clue as to why this keeps happening. The only thing I haven't tried is using a different serial cable. The folks at APC said they sell a specialized serial cable that's made to work with UNIX systems. I was about to purchase this cable and try it until I received an email from a guy, in response to my article at daemonnews, saying that he's experienced the exact same problem with his serial port as well. Even though he hasn't been trying to hook up a UPS but rather trying to get his modem to dial. My pc is a Compaq Deskpro 2000 (266mhz) with 64m RAM, running FreeBSD 3.4. There is only one serial port on this pc. There should be a way to find out why this keeps happening. Even if I find out that it's just not possible to get the serial port configured correctly for a UPS, I'd still like to know why. I've tried changing permissions for /dev/cuaa0 and the applications I've used to access the port/device, I've tried using ps aux, top and fstat to see if I can found out what process might be using the device but haven't found anything tangible. Even though it's not an emergency that I get this to work, it's a problem I'd like to get fixed or at least find out why I'll never get it to work. Any help would be greatly appreciated. Thanks Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 6:58:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (zoom2-053.telepath.com [216.14.2.53]) by hub.freebsd.org (Postfix) with SMTP id 409DA37B42C for ; Thu, 14 Sep 2000 06:58:22 -0700 (PDT) Received: (qmail 63109 invoked by uid 100); 14 Sep 2000 13:57:41 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14784.55637.790917.142533@guru.mired.org> Date: Thu, 14 Sep 2000 08:57:41 -0500 (CDT) To: Poul-Henning Kamp Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <56645.968935026@critter> References: <20000914115342.I77593@strontium.scientia.demon.co.uk> <56645.968935026@critter> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > In message <20000914115342.I77593@strontium.scientia.demon.co.uk>, Ben Smithurs > t writes: > >Poul-Henning Kamp wrote: > > > >> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > >> is bogus. It looks like something which happened "because we can" more > >> than something which has a legitimate need. > >You think adding a hack to every program to support "-" to mean > >stdout/stdin is better? > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). Ugh. So what happens when you *really* want to read a filed called "-"? Adding magic characters to low-level calls is a bad idea. I believe /dev/fd originated in Unix v8 (or maybe plan 9) to provide a uniform mechanism to get a class of process-internal objects where they can be manipulated by shell scripts. If that's the case, it's provenance is impeccable. > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. Again, putting magic character recognition in a low-level call is a bad idea. Worse yet, this kind of thing is really useful in shells (which don't generally have the ability to manipulate fd's). Consider trying to use that syntax in the shell? Which is why modern shells that implement this kind of thing use a different syntax. Of course, they depend on something like /dev/fd or named pipes to provide this feature. > But of course, this is bikeshed material... Most certainly. If you really want to make C programming look like Perl programming, could you do it by adding new library calls, instead of changing the semantics of existing ones? Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Your message of "Thu, 14 Sep 2000 08:43:04 EDT." <200009141243.IAA18449@pobox.engeast.BayNetworks.COM> Date: Thu, 14 Sep 2000 16:21:14 +0200 Message-ID: <56995.968941274@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141243.IAA18449@pobox.engeast.BayNetworks.COM>, Robert Withro w writes: > >phk@critter.freebsd.dk said: >:- The majority of these programs could be handled by adding knowledge of >:- "-" as a magic filename to fopen(3). > >Suppose I *want* a filename called "-"? My tough luck, huh? ./- Very few programs understand the filename "-" unless it is special cased to mean stdin/stdout -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 7:58:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 5CCCE37B422 for ; Thu, 14 Sep 2000 07:58:54 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id SAA07022; Thu, 14 Sep 2000 18:58:50 +0400 (MSD) Message-Id: <200009141458.SAA07022@aaz.links.ru> Subject: Re: HELP: Disk/file-systems are loused up In-Reply-To: from "gerald stoller" at "Sep 14, 0 04:09:24 am" To: gerald_stoller@hotmail.com (gerald stoller) Date: Thu, 14 Sep 2000 18:58:50 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG, GS_Stoller@juno.com From: "Aleksandr A.Babaylov" 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 gerald stoller writes: > I started up my (version 3.3 ) freeBSD , and the first thing that I did > was mount a MSDOS diskette and did a find on it (with -name "*hd*" ). > I got three lines of output stating something like 'date error; month (14) > out of range', then a long pause (during which I typed several ctl-C's ), > and the system crashed. I booted immediately, and the system informed me > (after the boot) that the disk is loused up and I should run fsck , which I > did. I ran it several times and it didn't fix the problem until I ran > fsck -p . I tried the find again, with the same results, but this time I > withdrew the floppy during the pause trying for another type of termination > to the find (rather than a system crash, I was hoping for a message that > the device was inaccessible and that I could respond in such a way that the > command would abort). Unfortunately, the system crashed again. This time, > no matter what I did with fsck I couldn't get the file systems cleaned up. > Any suggestions? > Send responses to me here and to me as GS_Stoller@juno.com . I loose my file systems while use 3.3 and 3.4 versions and something wrong happen with different scenario. Do not use 3.X - it is highly unstable in wrong conditions. Use 4.X - it is more stable in the same conditions. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 8: 7:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 4EEBA37B424; Thu, 14 Sep 2000 08:07:32 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.0/8.11.0) id e8EF7S370990; Thu, 14 Sep 2000 10:07:28 -0500 (EST) (envelope-from steve) Date: Thu, 14 Sep 2000 10:07:28 -0500 From: Steve Ames To: Robert Watson Cc: freebsd-hackers@freebsd.org Subject: Re: rcp -x Message-ID: <20000914100728.A35439@virtual-voodoo.com> References: <078601c01dc9$e857bcf0$8a1a050a@winstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@freebsd.org on Wed, Sep 13, 2000 at 06:22:53PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert, Thanks for the explanation. That wasn't clear from the manpage. SSH sounds like the better path for me. -Steve On Wed, Sep 13, 2000 at 06:22:53PM -0400, Robert Watson wrote: > > The -x options on rsh, rcp, and rlogin rely on Kerberos support, which it > appears you haven't installed. > > (example w/o kerberos installed) > > rcp -x > rcp: illegal option -- x > usage: rcp [-p] f1 f2 > rcp [-pr] f1 ... fn directory > > (example w/kerberos installed) > > rcp -x > usage: rcp [-Kpx] [-k realm] f1 f2 > rcp [-Kprx] [-k realm] f1 ... fn directory > > There's a tutorial on setting up Kerberos in the handbook, although it may > be out of date. However, Kerberos involves substantial administrative > overhead -- if you're not interested in that, try using SSH. > > Robert N M Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > TIS Labs at Network Associates, Safeport Network Services > > On Wed, 13 Sep 2000, Steven E. Ames wrote: > > > The man page for rcp(1) lists a '-x' option: > > > > -x Turn on DES encryption for all data passed by rcp. This may > > im- > > pact response time and CPU utilization, but provides > > increased > > security. > > > > But the command line doesn't seem to honor it? > > > > winrad3# rcp -x > > rcp: illegal option -- x > > usage: rcp [-p] f1 f2 > > rcp [-pr] f1 ... fn directory > > > > ditto -K and -k. > > > > -Steve > > > > > > > > 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 14 8:15:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 9149E37B423 for ; Thu, 14 Sep 2000 08:15:27 -0700 (PDT) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.11.0/8.11.0) with ESMTP id e8EFFL331653; Thu, 14 Sep 2000 08:15:22 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.11.0/8.11.0) id e8EFFsp05591; Thu, 14 Sep 2000 08:15:54 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200009141515.e8EFFsp05591@realtime.exit.com> Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <56076.968924938@critter> from Poul-Henning Kamp at "Sep 14, 2000 11:48:58 am" To: Poul-Henning Kamp Date: Thu, 14 Sep 2000 08:15:54 -0700 (PDT) Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORGG Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. I strongly disagree. I actually have a script that I use daily which requires a filename as an argument. By handing it /dev/stdin, I can make it take output as a part of a pipe. A _very_ useful little feature, IMNSHO. As far as fdescfs, well, Unixware has something very like it, and I believe that other commercial Unices do as well. I suspect that it's useful to some, if not to all. One thing about end users as opposed to engineers, they put this stuff to uses that we can't even imagine. Never underestimate the sheer ingenuity of a relatively naive user. :-) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.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 14 8:29:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id A9B3637B43C for ; Thu, 14 Sep 2000 08:29:36 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA03629; Thu, 14 Sep 2000 09:29:35 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA17389; Thu, 14 Sep 2000 09:29:34 -0600 (MDT) (envelope-from nate) Date: Thu, 14 Sep 2000 09:29:34 -0600 (MDT) Message-Id: <200009141529.JAA17389@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable To: John Polstra Cc: hackers@FreeBSD.ORG, Janick.Taillandier@ratp.fr Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009140049.RAA01334@vashon.polstra.com> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> <200009140049.RAA01334@vashon.polstra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We are trying to create a dynamic library of extensions to PHP 4.02= . > > This library implements a C++ class and has a C interface using the= "Extern C" > > declaration. > > This library is linked with libstdc++.so.3 . > >=20 > > If the library is called in a C program =3D> no trouble. > > If the library is called from PHP with the "dlopen()" function =3D>= > > [Warning: Unable to load dynamic library > > '/users/em/ftp/php/test_cpp/debug/libphptest.so' - /usr/lib/libstdc= ++.so.3: > > Undefined symbol "__ti9exception" in > > /usr/local/httpd/htdocs/www/Iti_q/testso.php on line 2 >=20 > This is because FreeBSD uses an archive library "libgcc.a" instead > of a shared library. That means that everything from libgcc which > is needed by your shared libraries had better already be linked into > the main program. The right solution is for us to use a shared > library for libgcc. At one point libgcc was shared (FreeBSD 1.*), and it caused way more problems that it solved. Nate (Note to eager committers: don't do this without > coordinating with obrien. There are ramifications that aren't > obvious.) >=20 > As a work-around, try adding this to your main program. (I am > assuming it is a C++ program too.) >=20 > extern void terminate(void); > void (*kludge_city)(void) =3D terminate; >=20 > Another possibility would be to link explicitly with libgcc when > creating your dynamic library: >=20 > cc -shared -o libphptest.so ... -lgcc >=20 > That might cause other problems, but probably not. >=20 > John > --=20 > John Polstra jdp@pols= tra.com > John D. Polstra & Co., Inc. Seattle, Washing= ton USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gya= m Trungpa >=20 >=20 >=20 > 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 14 8:36:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vdsi.net (vdsi.net [206.67.5.34]) by hub.freebsd.org (Postfix) with ESMTP id A062F37B423 for ; Thu, 14 Sep 2000 08:36:17 -0700 (PDT) Received: from rseals (xpress19793.htc.net [208.165.197.93]) by vdsi.net (8.9.2/8.9.2) with SMTP id KAA35982 for ; Thu, 14 Sep 2000 10:32:10 -0500 (CDT) (envelope-from rseals@vdsi.net) Message-ID: <003101c01e60$eb3b4e40$c901000a@magellanhealth.com> From: "Ray Seals" To: Subject: what the heck is ftime and why is the reference undefined??????? Date: Thu, 14 Sep 2000 10:31:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need to read the temps off of a 1-Wire Lan. I know about the mlan stuff in the ports, but the themod is set to read an ibutton 1920 device. I'm using a DS1820. I'm not a programmer so I would have the first clue where to even try modifying this for my device. Is anyone using the DS1820 on a 1-Wire Lan with FreeBSD? I have downloaded Digitemp and the Dallas DS-1820 software listed on Freshmeat. They are both for Linux. I recompiled Digitemp and it runs but doesn't print out any results. The other looked a little more promising, but when I try to compile it, it screams about undefined reference to 'ftime' Any help would be appreciated. Thanks, Ray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 8:43:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 7CDEA37B43C for ; Thu, 14 Sep 2000 08:43:17 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8EFhEN57690; Thu, 14 Sep 2000 17:43:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Ray Seals" Cc: hackers@FreeBSD.ORG Subject: Re: what the heck is ftime and why is the reference undefined??????? In-Reply-To: Your message of "Thu, 14 Sep 2000 10:31:56 CDT." <003101c01e60$eb3b4e40$c901000a@magellanhealth.com> Date: Thu, 14 Sep 2000 17:43:14 +0200 Message-ID: <57688.968946194@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <003101c01e60$eb3b4e40$c901000a@magellanhealth.com>, "Ray Seals" wri tes: >I need to read the temps off of a 1-Wire Lan. I know about the mlan stuff >in the ports, but the themod is set to read an ibutton 1920 device. I'm >using a DS1820. I'm not a programmer so I would have the first clue where >to even try modifying this for my device. Is anyone using the DS1820 on a >1-Wire Lan with FreeBSD? http://firtal.freebsd.dk/weather/ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 8:48: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E442E37B42C for ; Thu, 14 Sep 2000 08:48:01 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 5496D9B05; Thu, 14 Sep 2000 11:48:01 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 41725BA03; Thu, 14 Sep 2000 11:48:01 -0400 (EDT) Date: Thu, 14 Sep 2000 11:48:01 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Ray Seals Cc: hackers@FreeBSD.ORG Subject: Re: what the heck is ftime and why is the reference undefined??????? In-Reply-To: <003101c01e60$eb3b4e40$c901000a@magellanhealth.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 See the manpage on ftime(3) (especially the first and second lines of DESCRIPTION) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 9:12:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hookie.cs.ndsu.NoDak.edu (hookie.cs.ndsu.NoDak.edu [134.129.125.253]) by hub.freebsd.org (Postfix) with ESMTP id 616BA37B424 for ; Thu, 14 Sep 2000 09:12:14 -0700 (PDT) Received: (from tinguely@localhost) by hookie.cs.ndsu.NoDak.edu (8.9.3/8.9.3) id LAA67875 for freebsd-hackers@freebsd.org; Thu, 14 Sep 2000 11:12:07 -0500 (CDT) (envelope-from tinguely) Date: Thu, 14 Sep 2000 11:12:07 -0500 (CDT) From: mark tinguely Message-Id: <200009141612.LAA67875@hookie.cs.ndsu.NoDak.edu> To: freebsd-hackers@freebsd.org Subject: UNIXREVIEW.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: (blatently stolen from UNIXREVIEW.COM EXTRA! Volume 1, Issue 11) UNIXREVIEW.COM Call for Papers unixreview.com is looking for contributors to write feature articles. See the list below for suggested topics, or contact us with your own article ideas. * FreeBSD * Storage Area Networks * Linux performance tuning * Java * Open Source Development * Systems Management * Web Security Issues * Embedded Linux * Comparison of window managers * Comparison of the main X servers for UNIX on Intel Contact Christi Bear (cbear@cmp.com) with proposals for articles, press releases, or general questions about the publication process. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 9:13:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0863A37B422 for ; Thu, 14 Sep 2000 09:13:29 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA04099; Thu, 14 Sep 2000 09:12:04 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA02297; Thu, 14 Sep 2000 09:12:04 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 09:12:04 -0700 (PDT) Message-Id: <200009141612.JAA02297@vashon.polstra.com> To: hackers@freebsd.org Cc: n@nectar.com, archie@whistle.com Subject: Re: c++ error In-Reply-To: <20000914083032.B16624@spawn.nectar.com> References: <200009140019.RAA04988@bubba.whistle.com> <200009140036.RAA01292@vashon.polstra.com> <20000913230227.A15302@spawn.nectar.com> <20000914083032.B16624@spawn.nectar.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000914083032.B16624@spawn.nectar.com>, Jacques A. Vidrine wrote: > In summary, gcc has a kluge to work around a bug in the C++ > standard. It looks like you and Justin Archie. > have both found edge cases where the gcc kluge loses. If you can > come up with a reasonable test case that reproduces the problem, > perhaps it can be PR'd to the GCC folks? Actually, I don't have a test case. I was only able to make it fail when I moved out of /usr/include -- which disables the gcc kludge. I hope that Archie will be able to come up with a test case that demonstrates the failure. BTW, Archie, there are 3 places in the gcc code which can produce that diagnostic: 1 in "cp/class.c" and 2 in "cp/decl.c". Search for "with same name as" and you'll find them. It would be useful to find out which one of those is the culprit in your failing case. > As per the PR, I'm against #ifdef'ing structures like ip_opts for C++, > since it is likely that a later C++ standard will be corrected. I can't argue with that. I don't like my "solution" very much either. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 9:34: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9E97B37B42C for ; Thu, 14 Sep 2000 09:33:56 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA04164; Thu, 14 Sep 2000 09:33:50 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA02393; Thu, 14 Sep 2000 09:33:50 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 09:33:50 -0700 (PDT) Message-Id: <200009141633.JAA02393@vashon.polstra.com> To: hackers@freebsd.org Cc: nate@yogotech.com Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009141529.JAA17389@nomad.yogotech.com> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> <200009140049.RAA01334@vashon.polstra.com> <200009141529.JAA17389@nomad.yogotech.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009141529.JAA17389@nomad.yogotech.com>, Nate Williams wrote: > At one point libgcc was shared (FreeBSD 1.*), and it caused way more > problems that it solved. Do you remember any details? I analyzed it pretty thoroughly (I thought) more than a year ago, and decided the shared library was the best solution. At that time I asked PHK what the reasons were for eliminating the shared libgcc. (He is the person who got rid of it. See "src/gnu/lib/libgcc/Makefile" revisions 1.5 - 1.8.) He said he didn't think it would be a problem to make it shared again. At that time, I converted my -current system to using a shared libgcc and ran it like that for 6 months at least without any problems. I believe David O'Brien was also using a shared libgcc for a long time without problems. The non-shared libgcc used to work for us mainly because on the i386 architecture practically nothing from libgcc was ever used. That is no longer the case, because of all the exception support that has been added to it for C++. If a shared library uses exceptions (as does libstdc++) but the main program doesn't, you get undefined symbol errors as the original poster reported. Using a shared libgcc completely solves that. Also, we _desperately_ need to switch away from the setjmp/longjmp exception implementation and start using the now-standard DWARF2 implementation. It makes a tremendous performance difference even in programs that don't use exceptions at all. (I measured it once.) But that in turn requires more support from libgcc, and exacerbates the problems associated with using a non-shared libgcc. The egcs team used to argue vociferously against making libgcc shared. However, I found their list of reasons and decided that they didn't apply to us. In my view, many of the reasons boiled down to, "It would be too inconvenient for Red Hat." I.e., they didn't want to use their shared library version numbers the way they are supposed to be used. Also, many of the arguments against a shared libgcc which might make sense when gcc is a 3rd-party add-on just don't apply when it is _the_ system compiler. I don't follow the gcc mailing lists any more, but David O'Brien told me some months ago that they had done a complete turn-around on the issue and were planning on making libgcc shared again. (David, please correct me if I'm misrepresenting what you told me.) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 9:44:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 8951337B42C for ; Thu, 14 Sep 2000 09:44:43 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA04889; Thu, 14 Sep 2000 10:44:42 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA17770; Thu, 14 Sep 2000 10:44:41 -0600 (MDT) (envelope-from nate) Date: Thu, 14 Sep 2000 10:44:41 -0600 (MDT) Message-Id: <200009141644.KAA17770@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: hackers@freebsd.org, nate@yogotech.com Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009141633.JAA02393@vashon.polstra.com> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> <200009140049.RAA01334@vashon.polstra.com> <200009141529.JAA17389@nomad.yogotech.com> <200009141633.JAA02393@vashon.polstra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > At one point libgcc was shared (FreeBSD 1.*), and it caused way more > > problems that it solved. > > Do you remember any details? I analyzed it pretty thoroughly (I > thought) more than a year ago, and decided the shared library was the > best solution. If I remember right (and my memory is fuzzy for stuff that far bak) there were a couple of issues. 1) Speed. Shared libraries are slower than static libraries (PIC et. al), and the stuff in libgcc tends to be performance centric. 2) Ease of use. Everytime we upgrade or modify libgcc, it required keeping around the old libgcc.so. I don't think we had much experience with versioning back then, so we tended to either 'never' increment the versions or 'overdo' it. We weren't making releases nearly as often then, so keeping backwards compatability was more difficult as people tended to be running -stable instead of releases. Nowadays we handle backwards compatability better, so having N different versions of libgcc is still annoying, but easier to deal with (/usr/lib/compat). > At that time, I converted my -current system to using a shared libgcc > and ran it like that for 6 months at least without any problems. I > believe David O'Brien was also using a shared libgcc for a long time > without problems. There were no problems, it was just annoying. Many were of the opinion that 'not everything should be linked shared', since it tends to clutter up /usr/lib, and also tends to slow things down. Static linking isn't always bad > The non-shared libgcc used to work for us mainly because on the i386 > architecture practically nothing from libgcc was ever used. Aren't there quite a few 'math' routines inside libgcc (mods and diffs and all sorts of low-level 32/64 bit routines that are quite often used..) > That is no longer the case, because of all the exception support that > has been added to it for C++. If a shared library uses exceptions (as > does libstdc++) but the main program doesn't, you get undefined symbol > errors as the original poster reported. Using a shared libgcc > completely solves that. Ahh. Can't we just make the linker *always* add libgcc onto the end? Because it's a static library, if it's the symbol isn't used, then it won't be linked into the library? > Also, we _desperately_ need to switch away from the setjmp/longjmp > exception implementation and start using the now-standard DWARF2 > implementation. It makes a tremendous performance difference even in > programs that don't use exceptions at all. (I measured it once.) But > that in turn requires more support from libgcc, and exacerbates the > problems associated with using a non-shared libgcc. How so? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 9:59:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 9CAA737B423 for ; Thu, 14 Sep 2000 09:59:35 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id XAA26038; Thu, 14 Sep 2000 23:58:44 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 14 Sep 2000 23:58:44 +0700 (NSS) From: Max Khon To: John Polstra Cc: hackers@FreeBSD.ORG, nate@yogotech.com Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009141633.JAA02393@vashon.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 hi, there! On Thu, 14 Sep 2000, John Polstra wrote: > Also, we _desperately_ need to switch away from the setjmp/longjmp > exception implementation and start using the now-standard DWARF2 > implementation. It makes a tremendous performance difference even in > programs that don't use exceptions at all. (I measured it once.) But > that in turn requires more support from libgcc, and exacerbates the > problems associated with using a non-shared libgcc. libgcc already has support for DWARF2. the only thing that should be changed is crtbegin.o/crtend.o. I have made all the necessary patches for this. I believe, David has them. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 10:58:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id F373137B422 for ; Thu, 14 Sep 2000 10:58:41 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8EHw7T17902; Thu, 14 Sep 2000 10:58:07 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma017894; Thu, 14 Sep 2000 10:57:43 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id KAA12092; Thu, 14 Sep 2000 10:57:42 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009141757.KAA12092@bubba.whistle.com> Subject: Re: c++ error In-Reply-To: <200009141612.JAA02297@vashon.polstra.com> "from John Polstra at Sep 14, 2000 09:12:04 am" To: John Polstra Date: Thu, 14 Sep 2000 10:57:42 -0700 (PDT) Cc: hackers@freebsd.org, n@nectar.com X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > > have both found edge cases where the gcc kluge loses. If you can > > come up with a reasonable test case that reproduces the problem, > > perhaps it can be PR'd to the GCC folks? > > Actually, I don't have a test case. I was only able to make it fail > when I moved out of /usr/include -- which disables the > gcc kludge. I hope that Archie will be able to come up with a test > case that demonstrates the failure. I was doing a build with DESTDIR=/usr/image and so in.h was actually being found in /usr/image/usr/include/netinet/in.h rather than the normal place, so this must be what happened to me as well. Ugh, I'm glad I got to skip C++ and go straight to Java :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 11: 6:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id BF3D737B42C for ; Thu, 14 Sep 2000 11:06:11 -0700 (PDT) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id KAA02686; Thu, 14 Sep 2000 10:57:54 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id OAA00600; Thu, 14 Sep 2000 14:06:01 -0400 (EDT) Received: from baynetworks.com (kyzyl [192.32.150.103]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id OAA10683; Thu, 14 Sep 2000 14:06:01 -0400 for Message-Id: <200009141806.OAA10683@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.1.1 10/15/1999 To: Johnny Eriksson Cc: hackers@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message from Johnny Eriksson of "Thu, 14 Sep 0100 15:40:42 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 14:06:01 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I trimmed off current. ] :- > Suppose I *want* a filename called "-"? My tough luck, huh? :- Could you settle for "./-"? I wouldn't want to. Consider: I have a program that takes user input (from an option or a file or whatever) and uses that to compose an output file name. With the above I have to either test for "magic" filenames, or I have to correctly re-write filenames to prepend "./" when appropriate (and *only* when appropriate). Sure, it can be done, but it isn't trivial work and it has to be done to every program or you have a unexpected lurking bug. IMO, "magic" filenames are bad design. Orthogonality should always win out. -- Robert Withrow -- (+1 978 288 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 14 11:29:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id F23F837B422; Thu, 14 Sep 2000 11:29:10 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA83568; Thu, 14 Sep 2000 11:29:10 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 14 Sep 2000 11:29:10 -0700 (PDT) From: Kris Kennaway To: Danny Braniss Cc: hackers@FreeBSD.ORG Subject: Re: installing ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 Sep 2000, Danny Braniss wrote: > after i made a 'make buidlworld' how can i get it to install in /5.0-CURRENT? > i compiled on a 4.1. I respectfully suggest that if you dont know how to install FreeBSD from source, you shouldn't be using 5.0-CURRENT, which can and will screw up your system unless you already know how to fix it yourself. See http://www.freebsd.org/handbook/current-stable.html Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 11:47:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D949737B423 for ; Thu, 14 Sep 2000 11:47:42 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id LAA83370; Thu, 14 Sep 2000 11:43:49 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009141843.LAA83370@pike.osd.bsdi.com> Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <56076.968924938@critter> from Poul-Henning Kamp at "Sep 14, 2000 11:48:58 am" To: Poul-Henning Kamp Date: Thu, 14 Sep 2000 11:43:49 -0700 (PDT) Cc: Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORGG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <20000914123945.A32524@ringwraith.office1.bg>, Peter Pentchev writes > : > >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: > >> I've never thought of a use for fdescfs... > > > >Well.. just a trivial example - imagine a program which takes a filename > >as an argument; imagine yourself trying to pipe something into it - > >passing /dev/fd/0 as a filename to process would do the trick. > > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. How about the fact that the printing chapter in the Handbook uses /dev/fd/0 in its example of setting up a print filter using ghostscript since gs doesn't read from stdin by default or use '-' for that purpose. Hmmm?? > If anything I would propose we ditch it... Tools, not policy, as you are so fond of saying. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 11:55:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw1a.lmco.com (mailgw1a.lmco.com [192.31.106.7]) by hub.freebsd.org (Postfix) with ESMTP id 5272D37B42C for ; Thu, 14 Sep 2000 11:55:45 -0700 (PDT) Received: from emss02g01.ems.lmco.com (relay2.ems.lmco.com [166.29.2.54]) by mailgw1a.lmco.com (8.8.8/8.8.8) with ESMTP id MAA07907; Thu, 14 Sep 2000 12:55:33 -0600 (MDT) From: joe.loughry@lmco.com Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-32 #38887) id <0G0W00A014KCUW@lmco.com>; Thu, 14 Sep 2000 12:55:27 -0600 (MDT) Received: from emss02i00.ems.lmco.com ([166.29.2.48]) by lmco.com (PMDF V5.2-32 #38887) with ESMTP id <0G0W00MZ24JVS6@lmco.com>; Thu, 14 Sep 2000 12:55:08 -0600 (MDT) Received: by emss02i00.ems.lmco.com with Internet Mail Service (5.5.2650.21) id ; Thu, 14 Sep 2000 12:57:48 -0600 Content-return: allowed Date: Thu, 14 Sep 2000 12:55:32 -0600 Subject: re: /dev/cuaa0 locks my system up..Help! To: Joe.Warner@smed.com Cc: freebsd-hackers@freebsd.org Message-id: <784F51866054D4118E8A00508BDF581A8DB998@emss02m02.ems.lmco.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had some weird serial port problems myself a few days ago. I was having an (unrelated) problem with a PCI video card, and I swapped it to a different PCI slot on the advice of the manufacturer, which fixed the problem, but also caused my VGA card to change *it's* interrupt, which grabbed the same interrupt as one of my serial ports. The symptoms were, sometimes FreeBSD would identify the serial port on bootup, and sometimes it wouldn't see it at all. I would get a login banner on the terminal connected to that serial port when the system was booted, but the terminal wouldn't respond to keystrokes at all. Anyway, do this: dmesg | grep -i irq and look for two devices using the same IRQ number. Maybe that's it. -Joe Loughry loughry@uswest.net > Regardless of what application I use to access my serial port (/dev/cuaa0), > when I do, it causes my system to freeze up. CTRL + ALT + BACKSPACE > doesn't work, CTRL + ALT + F2 doesn't work,..you get the picture. When my > system freezes like this, my only alternative is to do a cold reboot and I > don't think this is too healthy a practice for any OS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 12:17:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 7172837B43C; Thu, 14 Sep 2000 12:17:43 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZeVv-0004ul-00; Thu, 14 Sep 2000 22:17:39 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZeVu-0000Nv-00; Thu, 14 Sep 2000 22:17:38 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Kris Kennaway Cc: hackers@FreeBSD.ORG Subject: Re: installing ... In-reply-to: Your message of Thu, 14 Sep 2000 11:29:10 -0700 (PDT) . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 22:17:38 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message you write: }On Wed, 13 Sep 2000, Danny Braniss wrote: } }> after i made a 'make buidlworld' how can i get it to install in /5.0-CURRENT? }> i compiled on a 4.1. } }I respectfully suggest that if you dont know how to install FreeBSD from }source, you shouldn't be using 5.0-CURRENT, which can and will screw up }your system unless you already know how to fix it yourself. well, it shouldn't screw up my system, if, for example, the install is not to a live system but to another partition, or disk which i could later boot from. i only asked, since i saw that one can compile to /usr/obj, which is fine, so what happend to that extra mile? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 12:22:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 224BC37B43E for ; Thu, 14 Sep 2000 12:22:09 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZeaC-0004yN-00; Thu, 14 Sep 2000 22:22:04 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13ZeaB-0000OD-00; Thu, 14 Sep 2000 22:22:03 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: hackers@FreeBSD.ORG Cc: John Baldwin Subject: Re: Fdescfs updates--coming to a devfs near you! In-reply-to: Your message of Thu, 14 Sep 2000 11:43:49 -0700 (PDT) . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 2000 22:22:03 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009141843.LAA83370@pike.osd.bsdi.com>you write: }How about the fact that the printing chapter in the Handbook uses /dev/fd/0 }in its example of setting up a print filter using ghostscript since gs }doesn't read from stdin by default or use '-' for that purpose. Hmmm?? } what about programs that were never meant to read from stdin, since, for example they like to seek ..., dvi2ps comes to mind. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 13: 8:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id CC39A37B422 for ; Thu, 14 Sep 2000 13:08:09 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id NAA87191; Thu, 14 Sep 2000 13:07:21 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009142007.NAA87191@pike.osd.bsdi.com> Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: from Danny Braniss at "Sep 14, 2000 10:22:03 pm" To: Danny Braniss Date: Thu, 14 Sep 2000 13:07:21 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss wrote: > In message <200009141843.LAA83370@pike.osd.bsdi.com>you write: > > }How about the fact that the printing chapter in the Handbook uses /dev/fd/0 > }in its example of setting up a print filter using ghostscript since gs > }doesn't read from stdin by default or use '-' for that purpose. Hmmm?? > } > > what about programs that were never meant to read from stdin, since, for > example they like to seek ..., dvi2ps comes to mind. Well, then they won't work. But just because some program won't work with it but many do doesn't mean we shouldn't remove the functionality. If you want to blow your own foot off, the OS's job is to deliver the bullet quickly and accurately to its destination. :) > danny -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 13:20:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f284.law9.hotmail.com [64.4.8.159]) by hub.freebsd.org (Postfix) with ESMTP id 8395137B422 for ; Thu, 14 Sep 2000 13:20:49 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 14 Sep 2000 13:20:49 -0700 Received: from 12.20.190.1 by lw9fd.law9.hotmail.msn.com with HTTP; Thu, 14 Sep 2000 20:20:49 GMT X-Originating-IP: [12.20.190.1] From: "gerald stoller" To: K.J.Koster@kpn.com Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: HELP: Disk/file-systems are loused up Date: Thu, 14 Sep 2000 16:20:49 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 14 Sep 2000 20:20:49.0354 (UTC) FILETIME=[459B6AA0:01C01E89] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Koster, K.J. writes >Subject: RE: HELP: Disk/file-systems are loused up >Date: Thu, 14 Sep 2000 10:16:38 +0100 > >Hello Gerald, > > > > > I started up my (version 3.3 ) freeBSD , and the > > first thing that I did > > was mount a MSDOS diskette and did a find on it (with > > -name "*hd*" ). > > I got three lines of output stating something like 'date > > error; month (14) > > out of range', then a long pause (during which I typed > > several ctl-C's ), > > and the system crashed. I booted immediately, and the system > > informed me > > (after the boot) that the disk is loused up and I should run > > fsck , which I > > did. I ran it several times and it didn't fix the problem > > until I ran > > fsck -p . I tried the find again, with the same > > results, but this time I > > withdrew the floppy during the pause trying for another type > > of termination > > to the find (rather than a system crash, I was hoping for a > > message that > > the device was inaccessible and that I could respond in such > > a way that the > > command would abort). Unfortunately, the system crashed > > again. This time, > > no matter what I did with fsck I couldn't get the file > > systems cleaned up. > > Any suggestions? > > >From your text it is not clear what you are fsck-ing. You cannot fsck an >MSDOS floppy. fsck is only for your harddisk after the crash. > >First boot some form of MSDOS or windows and use some form of scandisk to >fix the filesystem on the floppy. A broken filesystem on a floppy (or any >other device for that matter) *will" panic your system. > >I suggest that after you found what you were looking for, you bin the >floppy. One broken sector indicates it's about to die completely. > > Kees Jan > The fsck was operating on and reporting on the hard disk; the floppy was not even mounted while I was booting. Since fsck in all the variations with which I am familiar didn't fix the disk, I am trying to find another variation or another program to run which will complete the job without causing any disasters. I also think that the find program should be checked to see why it crashed and fix it to keep it from doing similarly in the future; I don't know whom to contact as yet. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.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 14 13:34:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 1ACA237B424; Thu, 14 Sep 2000 13:34:22 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA199770; Thu, 14 Sep 2000 16:31:25 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <56076.968924938@critter> References: <56076.968924938@critter> Date: Thu, 14 Sep 2000 16:33:55 -0400 To: Poul-Henning Kamp , Peter Pentchev From: Garance A Drosihn Subject: Re: Fdescfs updates--coming to a devfs near you! Cc: Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:48 AM +0200 9/14/00, Poul-Henning Kamp wrote: >I must admit that I think in general that /dev/std{in,out,err} >and /dev/fd is bogus. It looks like something which happened >"because we can" more than something which has a legitimate need. > >If anything I would propose we ditch it... I think it is a reasonable feature to have. It probably won't be useful all that often, but it could be very useful in some situations. I know I've hit situations where I wished I could do something like this, but I couldn't tell you an example right this minute. So, I wouldn't want to see fdesfs ditched, but on the other hand I don't have any clue how to address the loose ends that Chris mentioned in his initial message. :-) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 14: 1:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3EEE137B422; Thu, 14 Sep 2000 14:01:12 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA12425; Thu, 14 Sep 2000 14:01:12 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 14 Sep 2000 14:01:12 -0700 (PDT) From: Kris Kennaway To: Danny Braniss Cc: hackers@FreeBSD.ORG Subject: Re: installing ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Sep 2000, Danny Braniss wrote: > In message you > write: > }On Wed, 13 Sep 2000, Danny Braniss wrote: > } > }> after i made a 'make buidlworld' how can i get it to install in > /5.0-CURRENT? > }> i compiled on a 4.1. > } > }I respectfully suggest that if you dont know how to install FreeBSD from > }source, you shouldn't be using 5.0-CURRENT, which can and will screw up > }your system unless you already know how to fix it yourself. > > well, it shouldn't screw up my system, if, for example, the install is not to > a live system but to another partition, or disk which i could later boot from. > i only asked, since i saw that one can compile to /usr/obj, which is fine, so > what happend to that extra mile? Current can screw up anything and everything :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 14:34:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id F3F1E37B43C for ; Thu, 14 Sep 2000 14:34:28 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA05885; Thu, 14 Sep 2000 14:32:00 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA02822; Thu, 14 Sep 2000 14:31:59 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 14:31:59 -0700 (PDT) Message-Id: <200009142131.OAA02822@vashon.polstra.com> To: hackers@freebsd.org Cc: nate@yogotech.com Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009141644.KAA17770@nomad.yogotech.com> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> <200009141529.JAA17389@nomad.yogotech.com> <200009141633.JAA02393@vashon.polstra.com> <200009141644.KAA17770@nomad.yogotech.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009141644.KAA17770@nomad.yogotech.com>, Nate Williams wrote: [shared libgcc?] > If I remember right (and my memory is fuzzy for stuff that far bak) > there were a couple of issues. > > 1) Speed. Shared libraries are slower than static libraries (PIC > et. al), and the stuff in libgcc tends to be performance centric. True. But if we just make it link against "-lgcc" then knowledgeable users can always add "-static" if they know how to deal with the consequences and they need the performance. > 2) Ease of use. Everytime we upgrade or modify libgcc, it required > keeping around the old libgcc.so. I don't think we had much > experience with versioning back then, so we tended to either 'never' > increment the versions or 'overdo' it. Luckily, libgcc doesn't seem to be changing very often/much these days. > Aren't there quite a few 'math' routines inside libgcc (mods and diffs > and all sorts of low-level 32/64 bit routines that are quite often used..) I think most of the stuff that's actually used for C is just for the relatively rare 64-bit operations on the i386. > Ahh. Can't we just make the linker *always* add libgcc onto the end? > Because it's a static library, if it's the symbol isn't used, then it > won't be linked into the library? I assume you mean always add it onto the end when building shared libraries. That's problematic because the exception stuff uses some static variables inside libgcc, and you end up with multiple copies of them. > > Also, we _desperately_ need to switch away from the setjmp/longjmp > > exception implementation and start using the now-standard DWARF2 > > implementation. It makes a tremendous performance difference even in > > programs that don't use exceptions at all. (I measured it once.) But > > that in turn requires more support from libgcc, and exacerbates the > > problems associated with using a non-shared libgcc. > > How so? Well, I should have made that a separate topic as it doesn't have that much to do with whether libgcc is shared or not. But what I meant was that the DWARF2 exception support uses more stuff from libgcc, so you're more likely to run into an undefined symbol if libgcc is not shared. Probably a bogus point for this discussion. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 14:38:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9A36137B423 for ; Thu, 14 Sep 2000 14:38:17 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA05902; Thu, 14 Sep 2000 14:36:56 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA02870; Thu, 14 Sep 2000 14:36:55 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 14:36:55 -0700 (PDT) Message-Id: <200009142136.OAA02870@vashon.polstra.com> To: hackers@freebsd.org Cc: fjoe@iclub.nsu.ru Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > libgcc already has support for DWARF2. the only thing that should be > changed is crtbegin.o/crtend.o. Yes. > I have made all the necessary patches for this. I believe, David has > them. Actually I now think we should simply build the crt* files from gcc's "crtstuff.c" in the standard way, rather than having our own versions. The gcc versions are messy but they work fine, and they are specifically exempted from the GPL as long as they are used together with gcc. There are some potential problems with backward compatibility when making this change, but we need to do it anyway. The performance penalty from the sjlj exceptions is really terrible. I think I decided that using a shared libgcc would help with the compatibility issues when I looked at the problem a long time ago. But I can't remember the details any more. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 14:39: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7C16337B422 for ; Thu, 14 Sep 2000 14:38:59 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA05918; Thu, 14 Sep 2000 14:38:43 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA02894; Thu, 14 Sep 2000 14:38:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 14:38:42 -0700 (PDT) Message-Id: <200009142138.OAA02894@vashon.polstra.com> To: hackers@freebsd.org Cc: archie@whistle.com Subject: Re: c++ error In-Reply-To: <200009141757.KAA12092@bubba.whistle.com> References: <200009141757.KAA12092@bubba.whistle.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009141757.KAA12092@bubba.whistle.com>, Archie Cobbs wrote: > > I was doing a build with DESTDIR=/usr/image and so in.h was actually > being found in /usr/image/usr/include/netinet/in.h rather than the > normal place, so this must be what happened to me as well. That explains it then. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 14:51:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 7FC8737B42C for ; Thu, 14 Sep 2000 14:51:36 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id PAA10361; Thu, 14 Sep 2000 15:51:34 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id PAA24562; Thu, 14 Sep 2000 15:51:34 -0600 (MDT) (envelope-from nate) Date: Thu, 14 Sep 2000 15:51:34 -0600 (MDT) Message-Id: <200009142151.PAA24562@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: hackers@freebsd.org, nate@yogotech.com Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009142131.OAA02822@vashon.polstra.com> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> <200009141529.JAA17389@nomad.yogotech.com> <200009141633.JAA02393@vashon.polstra.com> <200009141644.KAA17770@nomad.yogotech.com> <200009142131.OAA02822@vashon.polstra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [shared libgcc?] > > If I remember right (and my memory is fuzzy for stuff that far bak) > > there were a couple of issues. > > > > 1) Speed. Shared libraries are slower than static libraries (PIC > > et. al), and the stuff in libgcc tends to be performance centric. > > True. But if we just make it link against "-lgcc" then knowledgeable > users can always add "-static" if they know how to deal with the > consequences and they need the performance. Ahh, but -static implies the entire enchilada is linked static, which may not be the case. :( > > 2) Ease of use. Everytime we upgrade or modify libgcc, it required > > keeping around the old libgcc.so. I don't think we had much > > experience with versioning back then, so we tended to either 'never' > > increment the versions or 'overdo' it. > > Luckily, libgcc doesn't seem to be changing very often/much these > days. > > > Aren't there quite a few 'math' routines inside libgcc (mods and diffs > > and all sorts of low-level 32/64 bit routines that are quite often used..) > > I think most of the stuff that's actually used for C is just for the > relatively rare 64-bit operations on the i386. Bruce would know more. I know that the JDK uses them, but then again it also does 64-bit math, so that may be the case. :) > > Ahh. Can't we just make the linker *always* add libgcc onto the end? > > Because it's a static library, if it's the symbol isn't used, then it > > won't be linked into the library? > > I assume you mean always add it onto the end when building shared > libraries. That's problematic because the exception stuff uses some > static variables inside libgcc, and you end up with multiple copies of > them. Hmmm.... > > > Also, we _desperately_ need to switch away from the setjmp/longjmp > > > exception implementation and start using the now-standard DWARF2 > > > implementation. It makes a tremendous performance difference even in > > > programs that don't use exceptions at all. (I measured it once.) But > > > that in turn requires more support from libgcc, and exacerbates the > > > problems associated with using a non-shared libgcc. > > > > How so? > > Well, I should have made that a separate topic as it doesn't have that > much to do with whether libgcc is shared or not. But what I meant > was that the DWARF2 exception support uses more stuff from libgcc, so > you're more likely to run into an undefined symbol if libgcc is not > shared. Probably a bogus point for this discussion. Gotcha... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 14:57:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0CF7837B422 for ; Thu, 14 Sep 2000 14:57:41 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA06012; Thu, 14 Sep 2000 14:57:33 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA02976; Thu, 14 Sep 2000 14:57:33 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 14:57:33 -0700 (PDT) Message-Id: <200009142157.OAA02976@vashon.polstra.com> To: hackers@freebsd.org Cc: nate@yogotech.com Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009142151.PAA24562@nomad.yogotech.com> References: <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp> <200009141644.KAA17770@nomad.yogotech.com> <200009142131.OAA02822@vashon.polstra.com> <200009142151.PAA24562@nomad.yogotech.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009142151.PAA24562@nomad.yogotech.com>, Nate Williams wrote: > > True. But if we just make it link against "-lgcc" then knowledgeable > > users can always add "-static" if they know how to deal with the > > consequences and they need the performance. > > Ahh, but -static implies the entire enchilada is linked static, which > may not be the case. :( Then you can sprinkle in the appropriate "-Wl,-Bstatic" and "-Wl,-Bdynamic" options in the right places. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 15:32:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 1367637B422; Thu, 14 Sep 2000 15:32:49 -0700 (PDT) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) id 13ZhYm-0001Qp-00; Thu, 14 Sep 2000 15:32:48 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.3+Sun/8.9.3) with SMTP id PAA19703; Thu, 14 Sep 2000 15:32:47 -0700 (PDT) From: patl@Phoenix.Volant.ORG Date: Thu, 14 Sep 2000 15:32:47 -0700 (PDT) Reply-To: patl@Phoenix.Volant.ORG Subject: Re: "!.*" [ was: Fdescfs updates--coming to a devfs near you! ] To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <56645.968935026@critter> 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 14-Sep-00 at 05:37, Poul-Henning Kamp (phk@critter.freebsd.dk) wrote: > >You think adding a hack to every program to support "-" to mean > >stdout/stdin is better? > > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). > > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. Isn't that potentially a huge security hole in every program that gets a filename from an external source? > But of course, this is bikeshed material... > > >> If anything I would propose we ditch it... > > > >And break loads of scripts at the same time? > > I would argue that the programs and the scripts that call them are > already broken, but hey... And I would argue that the fdescfs is cleaner than the '-' hack. (Which, by the way, should not be considered a filename hack so much as a command-line-parameter hack; since it was invented before there was a way to say 'use stdin/stdout' on the command-line... You could think of '/dev/stdin' as "'-' version 2") -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 18:37:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id D6E7F37B422 for ; Thu, 14 Sep 2000 18:37:20 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id IAA49948; Fri, 15 Sep 2000 08:37:01 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 15 Sep 2000 08:37:01 +0700 (NSS) From: Max Khon To: John Polstra Cc: hackers@FreeBSD.org Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009142136.OAA02870@vashon.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 hi, there! On Thu, 14 Sep 2000, John Polstra wrote: > > I have made all the necessary patches for this. I believe, David has > > them. > > Actually I now think we should simply build the crt* files from > gcc's "crtstuff.c" in the standard way, rather than having our own > versions. The gcc versions are messy but they work fine, and they are > specifically exempted from the GPL as long as they are used together > with gcc. changes to crt* files to support DWARF2 are minimal, however. there were some problems with pthreads initialization (but David will not like the way I did it -- some files in contrib/gcc should be changed). this happened because we initialize pthreads from static object constructor (which is not the right thing anyway). there are some workarounds (to not change anything improted from vendor branch), of course. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 22:42:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vbook.express.ru (vbook.express.ru [212.24.37.106]) by hub.freebsd.org (Postfix) with ESMTP id AA0FF37B43E; Thu, 14 Sep 2000 22:42:10 -0700 (PDT) Received: (from vova@localhost) by vbook.express.ru (8.9.3/8.9.3) id JAA39047; Fri, 15 Sep 2000 09:27:59 +0400 (MSD) (envelope-from vova) From: "Vladimir B. Grebenschikov" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14785.45919.363291.506910@vbook.express.ru> Date: Fri, 15 Sep 2000 09:27:59 +0400 (MSD) To: "Hao Zhang" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: need a recommendation of NIC In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hao Zhang writes: > I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets > thru FreeBSD routers. It's found that the duplications happened in FreeBSD router. > Now The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. To isolate this > problem. We will try different NIC. Can anyone give me some recommendation for the > high performance NIC for FreeBSD 3.3. Thanks in advance for any comments. Intell EtherExpress fxp driver in FreeBSD, I think it best low-cost ethernet card for FreeBSD now. > -Hao -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 22:56: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 08DAA37B422 for ; Thu, 14 Sep 2000 22:56:07 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13ZocG-0000Pu-00; Fri, 15 Sep 2000 00:04:52 -0600 Message-ID: <39C1BC04.4A534A80@softweyr.com> Date: Fri, 15 Sep 2000 00:04:52 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: ptacek@dashmail.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Getting all the IP address for a machine from code... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Ptacek wrote: > > I am looking for a way to get all the IP addresses that are configured a > machine. I need to do this in c source code, and without using DNS services > (ie: gethostname/gethostbyname won't work). I am hoping there are some > system calls I can use to get this information. Thanks in advance for any > help. Look in /usr/src/sbin/ifconfig/*.c and cut out the parts you don't need. It's under a BSD license, so you are pretty much free to do as you wish. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 14 23:48:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 553A937B423 for ; Thu, 14 Sep 2000 23:48:08 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JU72IW7GTU000ICD@research.kpn.com> for freebsd-hackers@freebsd.org; Fri, 15 Sep 2000 08:48:05 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Fri, 15 Sep 2000 08:48:05 +0100 Content-return: allowed Date: Fri, 15 Sep 2000 08:48:04 +0100 From: "Koster, K.J." Subject: RE: HELP: Disk/file-systems are loused up To: 'gerald stoller' Cc: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D78A6@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The fsck was operating on and reporting on the hard > disk; the floppy > was not even mounted while I was booting. Since fsck in > all the variations with which I am familiar didn't fix the > disk, I am trying to find another variation or another > program to run which will complete the job without causing > any disasters. > "The job"? Which job finding or fscking? "the disk"? The floppy or the harddisk? Please be specific. If it's an MSDOS floppy, use Windows to find files on it. Windows cares a whole lot less about broken sectors than FreeBSD does. You could have a look at mtools (somewhere in the ports), it will allow you to access the floppy without mounting it, so your system is not going to die when you use a broken floppy. Mtools do not mount the floppy, so it will just give you hard sector errors on the console in case of trouble. If the problem is to restore a broken harddisk filesystem after a crash, and fsck can't help you, you're in a pile of it (if you'll pardon the expression). If this is indeed your problem, that is not clear from the original post you did. I have little experience with restoring screwed filesystems (I just rebuild and restore backups). Try posting the output of fsck, or at least the error it's giving you. > I also think that the find program should be checked > to see why it > crashed and fix it to keep it from doing similarly in the > future; I don't know whom to contact as yet. > No matter how broken, a program is unable to crash the OS (well, very, very unlikely :). If you mount a broken filesystem, FreeBSD will die, find or no find. I'll bet that you could 'cd' into the broken directory and do 'echo *' to crash the box. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 1:54:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 1B8D737B422 for ; Fri, 15 Sep 2000 01:54:40 -0700 (PDT) Received: (qmail 334 invoked from network); 15 Sep 2000 09:03:13 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 15 Sep 2000 09:03:13 -0000 Received: from wall.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.9.3/8.9.3) with ESMTP id IAA32155; Fri, 15 Sep 2000 08:06:29 GMT (envelope-from jhs@wall.jhs.private) Message-Id: <200009150806.IAA32155@jhs.muc.de> To: Joe.Warner@smed.com Cc: freebsd-hackers@freebsd.org Subject: Re: /dev/cuaa0 locks my system up..Help! From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Thu, 14 Sep 2000 07:53:19 MDT." <8525695A.004C10AB.00@Deimos.smed.com> Date: Fri, 15 Sep 2000 10:06:27 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A while back, while trying to get my APC Smart-UPS 1000 to talk to my > FreeBSD 3.4 system, I encountered a problem with the serial port. This > problem inspired my to write an article that was published at this months > edition of daemonnews. > > The only thing I haven't tried is using a different serial cable. The > folks at APC said they sell a specialized serial cable that's made to work > with UNIX systems. I was about to purchase this cable and try it until I I succesfully use my APC Smart 2000 UPS on cuaa0 on 4.1 with my own home soldered _special_ cable, (but an upgrade from 3.4 is not what I'm suggesting, though of course you might want to try 4.1 anyway). An APC, is Not a normal PC type plug, but totaly non PC standard pinout with back compatability for non Smart models that don't use serial but do use 3 wire DC state output ! Do not use APC cables between 2 normal non APC devices. Do not use normal serial cables with an APC. I got my pdf format of the APC manual from Web August 2000: http://www.apc.com http://answers.apcc.com/cgi-bin/apc/solved http://www.apcc.com/support/ http://159.215.19.5/techref.nsf/umanuals http://159.215.19.5/techref.nsf/\ umanuals?OpenView&Start=1&Count=500&Expand=29#29 http://159.215.19.5/techref.nsf/umanuals/\ 128C9E5051B779BD852567A70057E436?OpenDocument ports/graphics/xpdf will display it. All pinouts for PC, APC UPS, cable I made to work between etc are on my http://bim.bsn.com/~jhs/standards/rs232.v24 which I'm also emailing you a private copy of. You might possibly have damaged your serial port if you connected a normal cable between the UPS & PC. Did you use a straight cable (PC to modem type) or a 'crossed' (= `rolled') cable used to normally connect 2 PCs together ? Ask yourself this question, add the information from my pin out diagram, & you can figure out which signals you connected where. After that, if still have have questions, mail me. If you really want to know what's going on, you probably need to use an RS232/V24 Serial Breakout Box, a small cheapish thing with 9 LEDs, lots of switches & jumper cables, & [multiple] male & female 25 or 9 pin plugs & sockets each side of the box. (Mine had a single 25 female + 25 male, but I extended it to have M+F 25+9 each side) Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 2: 2:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id 6FA1A37B423 for ; Fri, 15 Sep 2000 02:02:11 -0700 (PDT) Received: (qmail 45612 invoked from network); 15 Sep 2000 09:02:03 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 15 Sep 2000 09:02:03 -0000 Date: Fri, 15 Sep 2000 02:02:03 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... In-Reply-To: <53059.968085674@critter> 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 get it on my newsserver pretty much every night when expire runs. 12 IDE drives on 3 Promise controllers. I was just actually about to replace the MB, thinking it was just something freaky or unstable. I will try the patch. On Mon, 4 Sep 2000, Poul-Henning Kamp wrote: > > I'm looking for the remaining victims of the dreaded "microuptime > went backwards" message. > > If you can reliably reproduce the problem, please contact me, so > we can arrange for some very detailed tracing to try to find out > what exactly is going on. I have not been able to trigger the > problem in my lab in a long time. > > If you see the message only occationally, please try the attached > patch and let me know if this changes the picture. The patch is > not meant as a fix, but it might reduce the impact of this condition > considerably when it happens. Basically by reducing the width of > the timecounter the magnitude of the hit we take if the timecounter > goes backwards is reduced from about an hour to approx 110msec. > > Reducing the width to less than 17 bits starts to run the risk of > ambiguity due to clock rollover. > > This patch may not be safe with PCAUDIO. > > Poul-Henning > > Index: clock.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > retrieving revision 1.155 > diff -u -r1.155 clock.c > --- clock.c 2000/07/30 21:05:22 1.155 > +++ clock.c 2000/09/04 16:34:16 > @@ -194,7 +194,7 @@ > static struct timecounter i8254_timecounter = { > i8254_get_timecount, /* get_timecount */ > 0, /* no poll_pps */ > - ~0u, /* counter_mask */ > + 0x1ffff, /* counter_mask */ > 0, /* frequency */ > "i8254" /* name */ > }; > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" 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 15 2:19:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 4DA0437B422 for ; Fri, 15 Sep 2000 02:19:34 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-194-8-209-137.netcologne.de [194.8.209.137]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id LAA10712 for ; Fri, 15 Sep 2000 11:19:32 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e8F9JH900653 for ; Fri, 15 Sep 2000 11:19:17 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 15 Sep 2000 11:19:17 +0200 (CEST) From: Paul Herman To: freebsd-hackers@FreeBSD.ORG Subject: init(8) and securelevel Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1161302707-969008466=:323" Content-ID: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1161302707-969008466=:323 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: After some thought about init(8) and securelevel (and a suggestion from Sheldon Hearn) I believe a good compromise is to have the whole "init(8) being able to lower the securelevel in single-user mode" behaviour a boot variable in /boot/loader.conf. This has the advantage of giving people who wish to lower the secure level in maintenence mode what they want, without changing the default behavior of FreeBSD. Attached is a patch against -CURRENT from a few days ago (don't know if it patches cleanly against -STABLE.) Feedback welcome (for example, I'm not so happy with the boot variable name...) -Paul. --0-1161302707-969008466=:323 Content-Type: APPLICATION/OCTET-STREAM; NAME="init_securelevel.patch.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="init_securelevel.patch.gz" H4sICBvkwTkCA2luaXRfc2VjdXJlbGV2ZWwucGF0Y2gAvVhhc+I4Ev1s/4q+ bNUEgg02kAScy9YkGWY2tRkyFbJ7d584YwtQxdicJMNkd+e/X7dkE+OErau6 2qGIcazup5b0+qnl2zRmXwOQz7IzyzLVmWdCLTtJFsZMtKMsnduX///HfriZ wJwnLIDOMluxThptZEeKqHO4X2djC6YEZxueLkDgj+RZCn6717NjPp+Dm4Pb A1fQE6gG7Lrun4zH6nqe1/GGHd8DvxecDvBradRWq/U/+XXBPw08P/BO7ffv wT3rOmfQwus5vH9vww/kPpUYdMIuj8b3R9YPMFGhUISt2Ap4CqbVzSUTsMpi VnrRA+qLL0rPhzyFJyZSlhxL9FRMhJHiGwYxTkjEwFjnIlQ0OWuRLUS4KuE2 TMwyuYviJkR8CeyrEiH6z/LFgqaWpzjWlQFQGcwYwlBPsd0yMMlWTCWLkk1S Il0lSbaleLgiF8HiHGNBm1ywhG1YcmCQ5DBdh2p5edSRM5526EFgbrPKPd22 Z+ET/qvCNCaW8BRvk+TIBsuiGWVKgloySLhUkM1NLBEa8zhUTNpg39aYzXuD s07CZ/qXntDA29F34veB3g+yvHtWZ3n3DCpR75H8AHhB2UHH64E3DPw+stbS 0HtU/3NvQ/h+cNoLfF8T/rRHhMerITx9fj/STFnEsyPHeriefvpw/c3ZazJs MK2T2/Gnu1HNoCCrsfh19HB9PyGTVsXkhYjG6u4fD5O7X+92QONf7u4cy/tm w7eLfQJQCmlWTVchT7/Hotd7PLjQfv+VnuEjqAZbrnUdsy5luEhdyyCWC3zY xSzqWdD19KIOtYoNSxWTSuSRslBQIjghf7qjSSURgmgVyie4hJvPV5OfL+wW Sgr2A6YtTKeoDqxcKnQyzZbBBC0IJ4TnrcM4Fhq16G+TolDAicDV3qwvDNu8 c003b+AMdWiWxefQIEIssy2qzzvYUaoJv2t9aGwyHjdlPntWrOG6ebR24Fge Ny90a7YmrZMYv4+xW9Y3uryBWdCLQNHAqg/M+AP5o7LNYzaHNFPPTBk2Vj9v gH+8mjxe398/EnqdqHSZrvjsu/H0pcPDu+75q133HCqB7nH05XnBt/OO1wff D7qnQZcoimh7DH3lsCPoedDtax74Z1p26OdFd/DjOfRFpEgl02UmVRqumANH V0d4+an4/6i54251l7pEWKTAW7TFNu/C6pxAuL/XxSwSLJT7u91Jx3AYN9GI OrHLePS4CstN0pj8a3LzeDf96Wr84W70ML16+DRpmsGd06ha/nnfGRQkZ0Jk AqMoR4ZbW8KmCN5AbiOf3+mu9eAF+4+hNvHM+P3xB/wNH7s/pmy7VqKpiY8r m2OaGhP0cI2HGcPfqyNqlinxRhu8e6fzoQG6gzV+p2sew4/g627rM9mE/d5H X0YPn028+2uhf/XzeqCVBKE/wSiZ2su/PjuqvR1W8MErAR/ALsYyMapQlj8c Dmlj7g7A84JT39SgCFRmxZ51LSWw+ByaytPXladfVp4oQTxlxf5rWd7XAToS h1FyAR9hUKtMsaL2QxWmooqFMdVPH7CZaFwB+fzL44hQfK+AucH5gXwNW66W uvjC6lNmCYNVjuVi3X0yuvv4OJo8IkK3RIiz9FjpMoZyKaW6M4FszUz96mA7 Mi2ZYwGnCK5VgSvUGNH6JZpOTSp6IyapskVITTzDVq6eq9lZgSLdvR1/vC9m qIRbhlhX/7vYpco6CE6OIRQLA1LysKxRTaH6V6t0rbeDPOz7dR72fSgi1Cys Ae3KQ6wsUZuxwDvtWRpGs/Bt6/L8g9++qRzOep6mIf745Q49ZV+5ang6y3F7 RL3onOAFTuB2rpkTxiuExbkOFarVMpS0d+K6Kd1arp+RBFpX1zfueMuxxo+w xkfL0JibAxLIZZYnsQYSeGxa5Yniutigw4hWGoNBhxGHHPHAlO8h4PFsnYlQ 8OSZZJz6Mo7ap63dDcb4/nEUwOOSS8yGBDmcoss2E0+0189wpw+0neU3YcsM s77cfsBFMu5Wtwm1kha2OAk0ARitqcurZ1oNhrtdWGYPXxXxYJZopV7giahK +0YTFdnTQi7rTbQwLQvXhhwbJN6XgIfAp0azCZe48RV1FK4ZXjFcc37VK6PL eFPDYcoR89oH0mLwXdNicPgk9aq+7pryGiN8Iy0Ge0TvBj0v8Cktur230qJi rc9YvS4mkSmoe7iVt4ZUtFBOtL+sbeTLjmrIUGmEdJ7lAihCJhgWInqFJEly uWZtG67SZ5A56qQ5TheSR0ULiJBL9kbWODBDcqdZaWy7DZ5GSR7j9Nhue7yC saSdmTCMauJwTIj7QBL1jwU4gusEXBUuwN3ymOJOwoUpXnpDB0ff8nvnDs4Z jbbI8loec1NGcdTtZ4ws/Y2JzCQioo9XNpphoqARHhLSCCueBYvbtnuPFmKL o8TTYAG8wRwNZwkmdHu0qmeS3SpTqZotjunD1fNVvDso1cWHGUP+M1hkRB6t HGam8ak2nXMhy6xzx7tJdWB/Tm2XK9rAHNvVa2NejOz6cgCvKYoFFBUO9l15 TYIJHQpBw9Z7GYmYnsXdeyMTsKfVCLZLTIuqO3qn8YuZXzV7GVJbr05YGC35 AieXpBRThRYoZpJj2IUbhpDuzwhOo3nRQi+KaI4PzBwOtb1oIwmfzRhIQbB0 kJHga6yP2/8UICIYgGP/FxZI+tWCFAAA --0-1161302707-969008466=:323-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 5:56:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id AC57E37B422 for ; Fri, 15 Sep 2000 05:56:28 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id QAA17273; Fri, 15 Sep 2000 16:56:19 +0400 (MSD) Message-Id: <200009151256.QAA17273@aaz.links.ru> Subject: Re: HELP: Disk/file-systems are loused up In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D78A6@l04.research.kpn.com> from "Koster, K.J." at "Sep 15, 0 08:48:04 am" To: K.J.Koster@kpn.com (Koster, K.J.) Date: Fri, 15 Sep 2000 16:56:19 +0400 (MSD) Cc: gerald_stoller@hotmail.com, freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Koster, K.J. writes: > > I also think that the find program should be checked > > to see why it > > crashed and fix it to keep it from doing similarly in the > > future; I don't know whom to contact as yet. > No matter how broken, a program is unable to crash the OS (well, very, very > unlikely :). If you mount a broken filesystem, FreeBSD will die, find or no > find. I'll bet that you could 'cd' into the broken directory and do 'echo *' > to crash the box. It is very easy to crash the OS. ports/audio/dap for example. Or worst. try create 2 big slices of type 165 on one big (>10G?) disk. and write then read both labels. Yes, I understand that find program is not a key. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 6: 3:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 21A9437B43E; Fri, 15 Sep 2000 06:03:18 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id RAA17646; Fri, 15 Sep 2000 17:03:11 +0400 (MSD) Message-Id: <200009151303.RAA17646@aaz.links.ru> Subject: Re: need a recommendation of NIC In-Reply-To: <14785.45919.363291.506910@vbook.express.ru> from "Vladimir B. Grebenschikov" at "Sep 15, 0 09:27:59 am" To: vova@express.ru (Vladimir B. Grebenschikov) Date: Fri, 15 Sep 2000 17:03:10 +0400 (MSD) Cc: zhanghao@nortelnetworks.com, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Vladimir B. Grebenschikov writes: > Hao Zhang writes: > > I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets > > thru FreeBSD routers. It's found that the duplications happened in FreeBSD router. > > Now The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. To isolate this > > problem. We will try different NIC. Can anyone give me some recommendation for the > > high performance NIC for FreeBSD 3.3. Thanks in advance for any comments. > > Intell EtherExpress > fxp driver in FreeBSD, I think it best low-cost ethernet card for > FreeBSD now. As far as I know EtherExpress has hardware bug. The easy way to trigger it is connect 2 EtherExpress by crossover cable and load by traffic. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 6:36: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from euitt.upm.es (haddock.euitt.upm.es [138.100.52.102]) by hub.freebsd.org (Postfix) with ESMTP id C8A2A37B42C; Fri, 15 Sep 2000 06:35:54 -0700 (PDT) Received: from deneb.euitt.upm.es (deneb.euitt.upm.es [138.100.52.12]) by euitt.upm.es (8.9.3/8.9.3) with ESMTP id PAA00639; Fri, 15 Sep 2000 15:34:43 +0200 (MET DST) Date: Fri, 15 Sep 2000 15:34:43 +0200 (CEST) From: "Pedro J. Lobo" To: "Aleksandr A.Babaylov" Cc: "Vladimir B. Grebenschikov" , zhanghao@nortelnetworks.com, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: need a recommendation of NIC In-Reply-To: <200009151303.RAA17646@aaz.links.ru> Message-ID: 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 On Fri, 15 Sep 2000, Aleksandr A.Babaylov wrote: > Vladimir B. Grebenschikov writes: > > > > Intell EtherExpress > > fxp driver in FreeBSD, I think it best low-cost ethernet card for > > FreeBSD now. > As far as I know EtherExpress has hardware bug. > The easy way to trigger it is connect 2 EtherExpress by > crossover cable and load by traffic. :-? I've been using Pro/100 cards for years, and I've always found them rock stable. Can you explain us a bit more? -- --------------------------------------------------------------------- Pedro José Lobo Perea Tel: +34 91 336 78 19 Centro de Cálculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjlobo@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espańa / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 7:18:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ertpg14e1.nortelnetworks.com (ertpg14e1.nortelnetworks.com [47.234.0.35]) by hub.freebsd.org (Postfix) with ESMTP id D7A9537B423; Fri, 15 Sep 2000 07:18:38 -0700 (PDT) Received: from zrtpd004.us.nortel.com (actually zrtpd004) by ertpg14e1.nortelnetworks.com; Fri, 15 Sep 2000 10:17:28 -0400 Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2652.35) id ; Fri, 15 Sep 2000 10:17:28 -0400 Message-ID: From: "Hao Zhang" To: "'Pedro J. Lobo'" , "Aleksandr A.Babaylov" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: RE: need a recommendation of NIC Date: Fri, 15 Sep 2000 10:17:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C01F1F.ABCED500" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C01F1F.ABCED500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks for your info. I'm using FreeBSD v3.3 which suppports The PRO/100B with chipset 82558. = If I want to use Intel Pro/100+ with the 82559 chipset, what driver should I = use? fxp?=20 -Hao -----Original Message----- From: Pedro J. Lobo [mailto:pjlobo@euitt.upm.es] Sent: Friday, September 15, 2000 9:35 AM To: Aleksandr A.Babaylov Cc: Vladimir B. Grebenschikov; Zhang, Hao [WDLN2:AN22:EXCH]; freebsd-hackers@FreeBSD.ORG; freebsd-net@FreeBSD.ORG Subject: Re: need a recommendation of NIC On Fri, 15 Sep 2000, Aleksandr A.Babaylov wrote: > Vladimir B. Grebenschikov writes: > >=20 > > Intell EtherExpress > > fxp driver in FreeBSD, I think it best low-cost ethernet card for > > FreeBSD now. > As far as I know EtherExpress has hardware bug. > The easy way to trigger it is connect 2 EtherExpress by > crossover cable and load by traffic. :-? I've been using Pro/100 cards for years, and I've always found them rock stable. Can you explain us a bit more? --=20 --------------------------------------------------------------------- Pedro Jos=E9 Lobo Perea Tel: +34 91 336 78 19 Centro de C=E1lculo Fax: +34 91 331 92 29 E.U.I.T. Telecomunicaci=F3n e-mail: pjlobo@euitt.upm.es Universidad Polit=E9cnica de Madrid Ctra. de Valencia, Km. 7 E-28031 Madrid - Espa=F1a / Spain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message ------_=_NextPart_001_01C01F1F.ABCED500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: need a recommendation of NIC

Thanks for your info.
I'm using FreeBSD v3.3 which suppports The PRO/100B = with chipset 82558. If I want to use Intel Pro/100+ with the 82559 = chipset, what driver should I use? fxp?

-Hao



-----Original Message-----
From: Pedro J. Lobo [mailto:pjlobo@euitt.upm.es]
Sent: Friday, September 15, 2000 9:35 AM
To: Aleksandr A.Babaylov
Cc: Vladimir B. Grebenschikov; Zhang, Hao = [WDLN2:AN22:EXCH];
freebsd-hackers@FreeBSD.ORG; = freebsd-net@FreeBSD.ORG
Subject: Re: need a recommendation of NIC


On Fri, 15 Sep 2000, Aleksandr A.Babaylov = wrote:

> Vladimir B. Grebenschikov writes:
> >
> > Intell EtherExpress
> > fxp driver in FreeBSD, I think it best = low-cost ethernet card for
> > FreeBSD now.
> As far as I know EtherExpress has hardware = bug.
> The easy way to trigger it is connect 2 = EtherExpress by
> crossover cable and load by traffic.

:-? I've been using Pro/100 cards for years, and I've = always found them
rock stable. Can you explain us a bit more?

--
---------------------------------------------------------------= ------
Pedro Jos=E9 Lobo = Perea           &= nbsp;    Tel:    +34 91 336 78 19
Centro de = C=E1lculo          &nb= sp;         = Fax:    +34 91 331 92 29
E.U.I.T. = Telecomunicaci=F3n         =    e-mail: pjlobo@euitt.upm.es
Universidad Polit=E9cnica de Madrid
Ctra. de Valencia, Km. = 7            = ; E-28031 Madrid - Espa=F1a / Spain



To Unsubscribe: send mail to = majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the = body of the message

------_=_NextPart_001_01C01F1F.ABCED500-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 7:29:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 238B137B423; Fri, 15 Sep 2000 07:29:33 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id SAA22804; Fri, 15 Sep 2000 18:28:02 +0400 (MSD) Message-Id: <200009151428.SAA22804@aaz.links.ru> Subject: Re: need a recommendation of NIC In-Reply-To: from "Pedro J. Lobo" at "Sep 15, 0 03:34:43 pm" To: pjlobo@euitt.upm.es (Pedro J. Lobo) Date: Fri, 15 Sep 2000 18:28:02 +0400 (MSD) Cc: babolo@links.ru, vova@express.ru, zhanghao@nortelnetworks.com, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Pedro J. Lobo writes: [Charset ISO-8859-1 unsupported, filtering to ASCII...] > On Fri, 15 Sep 2000, Aleksandr A.Babaylov wrote: > > > Vladimir B. Grebenschikov writes: > > > > > > Intell EtherExpress > > > fxp driver in FreeBSD, I think it best low-cost ethernet card for > > > FreeBSD now. > > As far as I know EtherExpress has hardware bug. > > The easy way to trigger it is connect 2 EtherExpress by > > crossover cable and load by traffic. > > :-? I've been using Pro/100 cards for years, and I've always found them > rock stable. Can you explain us a bit more? My mail based on message from David Greenman : http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=45338+47352+/usr/local/www/db/text/1998/freebsd-hackers/19981025.freebsd-hackers -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 7:40:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tistix.ratp.fr (tistix.ratp.fr [62.160.169.66]) by hub.freebsd.org (Postfix) with ESMTP id 3C55837B423 for ; Fri, 15 Sep 2000 07:40:42 -0700 (PDT) Received: from nyplic12.neuilly.ratp (mail.ratp.fr [62.160.169.132]) by tistix.ratp.fr with ESMTP id QAA72403 ; Fri, 15 Sep 2000 16:40:01 +0200 (DST) From: Received: by nyplic12.neuilly.ratp with Internet Mail Service (5.5.2650.21) id ; Fri, 15 Sep 2000 16:41:24 +0100 Message-ID: <4F88710E19D4D311B36A00508B08FD0F2C84F6@nyplme11.neuilly.ratp> To: jdp@polstra.com, hackers@freebsd.org Subject: RE: Trouble with dynamic loading of C++ libs in PHP v4.02 on Free BSD 4.1 Date: Fri, 15 Sep 2000 16:41:20 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you John! Linking the library with -lgcc solved the problem. In article = <4F88710E19D4D311B36A00508B08FD0F2C84DA@nyplme11.neuilly.ratp>, wrote: > We are trying to create a dynamic library of extensions to PHP 4.02. > This library implements a C++ class and has a C interface using the = "Extern C" > declaration. > This library is linked with libstdc++.so.3 . >=20 > If the library is called in a C program =3D> no trouble. > If the library is called from PHP with the "dlopen()" function =3D> > [Warning: Unable to load dynamic library > '/users/em/ftp/php/test_cpp/debug/libphptest.so' - = /usr/lib/libstdc++.so.3: > Undefined symbol "__ti9exception" in > /usr/local/httpd/htdocs/www/Iti_q/testso.php on line 2 This is because FreeBSD uses an archive library "libgcc.a" instead of a shared library. That means that everything from libgcc which is needed by your shared libraries had better already be linked into the main program. The right solution is for us to use a shared library for libgcc. (Note to eager committers: don't do this without coordinating with obrien. There are ramifications that aren't obvious.) As a work-around, try adding this to your main program. (I am assuming it is a C++ program too.) extern void terminate(void); void (*kludge_city)(void) =3D terminate; Another possibility would be to link explicitly with libgcc when creating your dynamic library: cc -shared -o libphptest.so ... -lgcc That might cause other problems, but probably not. John --=20 John Polstra = jdp@polstra.com John D. Polstra & Co., Inc. Seattle, = Washington USA "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam = Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 8:20:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bag-2.mail.digex.net (bag-2.mail.digex.net [204.91.99.101]) by hub.freebsd.org (Postfix) with ESMTP id 2BAFC37B43C for ; Fri, 15 Sep 2000 08:20:03 -0700 (PDT) Received: from [209.49.190.34] (fireout.mbakercorp.com [209.49.190.34]) by bag-2.mail.digex.net (8.9.3/8.9.3) with SMTP id LAA03611 for ; Fri, 15 Sep 2000 11:19:44 -0400 (EDT) Received: from admin_4.mbakercorp.com by [209.49.190.34] via smtpd (for bag-2.mail.digex.net [204.91.99.101]) with SMTP; 15 Sep 2000 18:29:48 UT Received: from gatedom-Message_Server by mbakercorp.com with Novell_GroupWise; Fri, 15 Sep 2000 11:19:10 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Fri, 15 Sep 2000 11:18:46 -0400 From: "Joseph Wright" To: Subject: Sound Yamaha YmF 724F Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently heard that in release 4.1 of FreeBSD the Yamaha 724F would be = supported. I just finished installing FreeBSD 4.1 (intel) I was wondering what I = would have to do to get the sound card to work. thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 8:23:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 1DC5B37B43C; Fri, 15 Sep 2000 08:23:51 -0700 (PDT) Received: from frolic.no-support.loc (ppp36-174.hrz.uni-bielefeld.de [129.70.36.174]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0G0X0005XPFJFC@mail.uni-bielefeld.de>; Fri, 15 Sep 2000 17:23:50 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id DAA03536; Fri, 15 Sep 2000 03:40:53 +0200 (CEST envelope-from bjoern) Date: Fri, 15 Sep 2000 03:40:52 +0200 From: Bjoern Fischer Subject: Re: Fdescfs updates--coming to a devfs near you! In-reply-to: <56645.968935026@critter>; from phk@critter.freebsd.dk on Thu, Sep 14, 2000 at 02:37:06PM +0200 To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Message-id: <20000915034052.B2859@frolic.no-support.loc> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline Content-transfer-encoding: 7BIT User-Agent: Mutt/1.2.5i References: <20000914115342.I77593@strontium.scientia.demon.co.uk> <56645.968935026@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote: [...] > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). > > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. This would break POSIX and raise a security flaw in many applications. fopen(3) *never* should perform a fork/exec. Scary. Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 8:24: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web5101.mail.yahoo.com (web5101.mail.yahoo.com [216.115.106.71]) by hub.freebsd.org (Postfix) with SMTP id E2AD637B446 for ; Fri, 15 Sep 2000 08:23:57 -0700 (PDT) Message-ID: <20000915152357.17970.qmail@web5101.mail.yahoo.com> Received: from [203.101.88.10] by web5101.mail.yahoo.com; Sat, 16 Sep 2000 02:23:57 EST Date: Sat, 16 Sep 2000 02:23:57 +1100 (EST) From: =?iso-8859-1?q?Paul=20Jansen?= Subject: Diskless boot - almost there now I think To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having problems with diskless booting. I'm using the frreebsd etherboot port. Here's my /usr/local/etc/dhcpd.conf file for the ISC v2 DHCP server: # dhcpd.conf # option definitions common to all supported networks... option domain-name "jansen.org"; option domain-name-servers 202.167.41.130; option subnet-mask 255.255.255.0; default-lease-time 600; max-lease-time 7200; subnet 192.168.0.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.0.10 192.168.0.20; option routers 192.168.0.8; option broadcast-address 192.168.0.255; filename "/tftpboot/kernel.XWORKSTATION"; option root-path "192.168.0.1:/usr/diskless/rootfs/xworkstation"; option option-128 "192.168.0.1:/usr/diskless/swap"; option option-176 5; option option-160 "timeout=8:default=193:"; option option-192 "IJ2:::/tftpboot/kernel.ij2:"; option option-193 "XWORKSTATION:::/tftpboot/kernel.XWORKSTATION:"; } my /etc/exports file has this line in it: /usr -alldirs -maproot=0:0 edessa pico host10 host11 host12 host13 The last few messages that pop up on the diskless systems screen are: Mounting root from NFS: NFS ROOT: 192.168.0.1:/usr/diskless/rootfs/xworkstation NFS SWAP: 192.168.0.1:/usr/diskless/swap The system sits here like this. I have tried this on two different diskless boxes with the same result. I have left them for up to 20 minutes but nothing happens. I have to admit that I am fumbling my way through this due to lack of a good resource on diskless booting with freebsd. I'm not sure what's meant to happen next. I don;t know if my filesystem exported for the diskless machine is set up right either. Is freebsd diskless like netbsd in that if it doesn't find an /etc/rc.conf file it drops to single user mode? Can someone help me with what is meant to happen next and what I'm not doing right? I'm using 4.1R and a kernel for the diskless machine compiled with the following options: # Kernel BOOTP support options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options BOOTP_NFSV3 # Use NFS v3 to NFS mount root options BOOTP_COMPAT # Workaround for broken bootp daemons. Thanks. _____________________________________________________________________________ http://geocities.yahoo.com.au - Yahoo! Australia & NZ GeoCities - Build your own Web Site - for free! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 8:52:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A850237B422 for ; Fri, 15 Sep 2000 08:52:42 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA45467; Fri, 15 Sep 2000 11:52:32 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 15 Sep 2000 11:52:31 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: David Malone Cc: Chris Ptacek , freebsd-hackers@FreeBSD.ORG Subject: Re: Getting all the IP address for a machine from code... In-Reply-To: <20000914095622.A25929@gosset.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Sep 2000, David Malone wrote: > On Wed, Sep 13, 2000 at 08:12:47PM -0700, Chris Ptacek wrote: > > I am looking for a way to get all the IP addresses that are configured a > > machine. I need to do this in c source code, and without using DNS services > > (ie: gethostname/gethostbyname won't work). I am hoping there are some > > system calls I can use to get this information. Thanks in advance for any > > help. > > You could use getifaddrs in FreeBSD 4 and later - otherwise you'll > need to use sysctl to get the list of interfaces and addresses. It is possible to get interface lists on earlier versions (and I hope still current versions) using the ioctl interfaces described in Stevens. See also ifconfig.c source from various versions of FreeBSD :-). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 8:54:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 0C23837B423; Fri, 15 Sep 2000 08:54:54 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA45491; Fri, 15 Sep 2000 11:54:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 15 Sep 2000 11:54:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Julian Elischer Cc: Chris Costello , hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <39C0885A.41C67EA6@elischer.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 Thu, 14 Sep 2000, Julian Elischer wrote: > I've never thought of a use for fdescfs... I used /dev/fd/1 just yesterday for a third-party precompiled binary that insists on outputting to a file specified on the command line. Slapping in /dev/fd/1 lets me stuff the command in a pipe chain. Same goes for /dev/fd/0. Other file descriptors, I'm less sure about :-) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 8:58:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2523937B424 for ; Fri, 15 Sep 2000 08:58:22 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA45535; Fri, 15 Sep 2000 11:58:19 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 15 Sep 2000 11:58:19 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Steve Ames Cc: freebsd-hackers@freebsd.org Subject: Re: rcp -x In-Reply-To: <20000914100728.A35439@virtual-voodoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Sep 2000, Steve Ames wrote: > Thanks for the explanation. That wasn't clear from the manpage. SSH > sounds like the better path for me. As was also pointed out in a private e-mail, this probably ought to be cleaned up so that either (a) a different man page is installed for the non-crypto distribution (which is going away), or (b) the man page references the support being conditional on Kerberos support being built. (b) is probably the right answer. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 9: 7:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.mobilix.dk (mail.mobilix.dk [194.234.53.85]) by hub.freebsd.org (Postfix) with ESMTP id 92F0337B440 for ; Fri, 15 Sep 2000 09:07:16 -0700 (PDT) Received: from lflat.vas.mobilix.dk (gw-vas.mobilix.net [212.97.206.4]) by mail.mobilix.dk (8.8.7/8.8.7) with ESMTP id OAA20016 for ; Fri, 15 Sep 2000 14:55:00 +0200 Received: by lflat.vas.mobilix.dk (Postfix, from userid 72044) id 1000CA820; Fri, 15 Sep 2000 14:25:44 +0200 (CEST) Date: Fri, 15 Sep 2000 14:25:44 +0200 From: Vadim Belman To: freebsd-hackers@freebsd.org Subject: Live debugging of a process being hung in a syscall. Message-ID: <20000915142543.A3697@lflat.vas.mobilix.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seem like I got a NFS-related bug here where a httpd process hung in a uninterruptable wait (a disk operation, most likely). In order to locate the problem I need the process' stack trace first. gdb doesn't attach to the process for obvious reasons. Making a crashdump doesn't inspire me at all. The question is: is there a way of working with /proc entries? I.e. is it possible to get all what I need from, say, /proc//mem? -- /Voland Vadim Belman E-mail: voland@lflat.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 9: 9:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 69DC637B424 for ; Fri, 15 Sep 2000 09:09:29 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA10543; Fri, 15 Sep 2000 09:05:43 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA04563; Fri, 15 Sep 2000 09:05:42 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 15 Sep 2000 09:05:42 -0700 (PDT) Message-Id: <200009151605.JAA04563@vashon.polstra.com> To: hackers@freebsd.org Cc: fjoe@iclub.nsu.ru Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > On Thu, 14 Sep 2000, John Polstra wrote: > > > Actually I now think we should simply build the crt* files from > > gcc's "crtstuff.c" in the standard way, rather than having our own > > versions. The gcc versions are messy but they work fine, and they are > > specifically exempted from the GPL as long as they are used together > > with gcc. > > changes to crt* files to support DWARF2 are minimal, however. The reason I think we should use gcc's "crtstuff.c" versions is that it will make it easier for us to keep in sync with any future changes they make. > there were some problems with pthreads initialization (but David will not > like the way I did it -- some files in contrib/gcc should be changed). > this happened because we initialize pthreads from static object > constructor (which is not the right thing anyway). It seemed like a good idea at the time. :-) What is the problem -- is it that libc_r is initialized at the wrong time? What would you suggest as a better method for initializing the library? I'd hate to introduce a bunch of "if (!initted) { ... }" checks, since those add runtime overhead on every call. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 9:57: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 2C17937B43C for ; Fri, 15 Sep 2000 09:57:01 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id XAA80044; Fri, 15 Sep 2000 23:56:30 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 15 Sep 2000 23:56:29 +0700 (NSS) From: Max Khon To: John Polstra Cc: hackers@freebsd.org Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: <200009151605.JAA04563@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-479365117-969036989=:78659" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-479365117-969036989=:78659 Content-Type: TEXT/PLAIN; charset=US-ASCII hi, there! On Fri, 15 Sep 2000, John Polstra wrote: > > there were some problems with pthreads initialization (but David will not > > like the way I did it -- some files in contrib/gcc should be changed). > > this happened because we initialize pthreads from static object > > constructor (which is not the right thing anyway). > > It seemed like a good idea at the time. :-) What is the problem -- > is it that libc_r is initialized at the wrong time? What would you > suggest as a better method for initializing the library? I'd hate to > introduce a bunch of "if (!initted) { ... }" checks, since those add > runtime overhead on every call. `__register_frame_info' should be called from `do_ctors' in src/lib/csu/common/crtbegin.c to load frame information from .eh_frame sections before any constructors are executed because try/catch can be used in constructors of static objects (`__register_frame_info' is defined in src/contrib/gcc/frame.c, this file is linked into libgcc[_r].a). however `__register_frame_info' uses locks and other threading stuff (using pthreads on FreeBSD) so we must have pthreads initialized before locks are used. another issue with our pthreads initialization is that pthreads can be used in static object constructors so the first `pthread_xxx' call can happen before `_thread_init' is called from constructor of our _thread_init_invoker (it depends on order in which constructors are placed in .ctors section). I see two solutions (both seem to be hacks for me): 1) we can insert if (!initted) ... in `pthread_once' (this seem to be the first pthreads function called from __register_frame_info) 2) we can insert #if __GTHREADS _thread_init(); #endif at the very beginning of `__register_frame_info' The second approach seems to be cleaner but require changes in src/contrib/gcc/ /fjoe PS I have attached patches and Makefile.inc which should be placed into src/lib/csu. Makefile.inc can be slightly out of date (I made it somewhere around May/Jun 2000) --0-479365117-969036989=:78659 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="eh_frame.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="eh_frame.diff" LS0tIGNvbnRyaWIvZ2NjL2NvbmZpZy9mcmVlYnNkLmgub3JpZwlXZWQgSnVs IDE5IDA3OjMwOjUzIDIwMDANCisrKyBjb250cmliL2djYy9jb25maWcvZnJl ZWJzZC5oCVN1biBKdWwgMjMgMTc6NTk6MzMgMjAwMA0KQEAgLTEzNywxMiAr MTM3LDYgQEANCiAjdW5kZWYgIEhBTkRMRV9TWVNWX1BSQUdNQQ0KICNkZWZp bmUgSEFORExFX1NZU1ZfUFJBR01BDQogDQotLyogRnJlZUJTRCBFTEYgdXNp bmcgb3VyIGhvbWUtZ3Jvd24gY3J0YmVnaW4uby9jcnRlbmQubyBkb2VzIG5v dCBzdXBwb3J0IHRoZQ0KLSAgIERXQVJGMiB1bndpbmRpbmcgbWVjaGFuaXNt cy4gIE9uY2UgYG1ha2Ugd29ybGQnIGJvb3RzdHJhcGluZyBwcm9ibGVtcyB3 aXRoDQotICAgdGhlIEVHQ1MgY3J0c3R1ZmYuYyBpcyBvdmVyY29tZSwgd2Ug d2lsbCBzd2l0Y2ggdG8gdGhlIG5vbi1zamxqLWV4Y2VwdGlvbnMgDQotICAg dHlwZSBleGNlcHRpb24gbWFjaGFuaXNtLiAgKi8NCi0jZGVmaW5lIERXQVJG Ml9VTldJTkRfSU5GTyAwDQotDQogLyogRG8gbm90IHVzZSBgYHRodW5rcycn IHRvIGltcGxlbWVudCBDKysgdnRhYmxlcy4gIFRoaXMgbWV0aG9kIHN0aWxs IGhhcw0KICAgIGZhdGFsIGJ1Z3MuICBBbHNvLCBHQ0MgMy4wIHdpbGwgaGF2 ZSBhIG5ldyBDKysgQUJJIHRoYXQgbWF5IG5vdCBldmVuDQogICAgc3VwcG9y dCBgdGh1bmtzJy4gICovDQotLS0gY29udHJpYi9nY2MvZnJhbWUuYy5vcmln CU1vbiBKdWwgMjQgMDA6Mjk6MjUgMjAwMA0KKysrIGNvbnRyaWIvZ2NjL2Zy YW1lLmMJTW9uIEp1bCAyNCAwMDozMzoyOCAyMDAwDQpAQCAtNzI1LDYgKzcy NSwxMCBAQA0KIHZvaWQNCiBfX3JlZ2lzdGVyX2ZyYW1lX2luZm8gKHZvaWQg KmJlZ2luLCBzdHJ1Y3Qgb2JqZWN0ICpvYikNCiB7DQorI2lmIF9fR1RIUkVB RFMNCisgIF90aHJlYWRfaW5pdCgpOw0KKyNlbmRpZg0KKw0KICAgb2ItPmZk ZV9iZWdpbiA9IGJlZ2luOw0KIA0KICAgb2ItPnBjX2JlZ2luID0gb2ItPnBj X2VuZCA9IDA7DQotLS0gbGliL2NzdS9jb21tb24vY3J0YmVnaW4uYy5vcmln CU1vbiBKdWwgMTAgMTY6MTU6MjUgMjAwMA0KKysrIGxpYi9jc3UvY29tbW9u L2NydGJlZ2luLmMJTW9uIEp1bCAyNCAwMDozNjoyNSAyMDAwDQpAQCAtMjYs NiArMjYsOSBAQA0KICAqLw0KIA0KICNpbmNsdWRlIDxzeXMvcGFyYW0uaD4N CisjaW5jbHVkZSAidG0uaCINCisjaW5jbHVkZSAiZGVmYXVsdHMuaCINCisj aW5jbHVkZSA8ZnJhbWUuaD4NCiANCiAjZGVmaW5lIEFCSV9WRU5ET1IJIkZy ZWVCU0QiDQogI2RlZmluZSBBQklfU0VDVElPTgkiLm5vdGUuQUJJLXRhZyIN CkBAIC0zMywxMyArMzYsMjMgQEANCiANCiB0eXBlZGVmIHZvaWQgKCpmcHRy KSh2b2lkKTsNCiANCitleHRlcm4gdm9pZCBfX3JlZ2lzdGVyX2ZyYW1lX2lu Zm8odm9pZCAqLCBzdHJ1Y3Qgb2JqZWN0ICopDQorCQkJX19hdHRyaWJ1dGVf Xygod2VhaykpOw0KK2V4dGVybiB2b2lkICpfX2RlcmVnaXN0ZXJfZnJhbWVf aW5mbyh2b2lkICopDQorCQkJX19hdHRyaWJ1dGVfXygod2VhaykpOw0KKw0K IHN0YXRpYyBmcHRyIGN0b3JfbGlzdFsxXSBfX2F0dHJpYnV0ZV9fKChzZWN0 aW9uKCIuY3RvcnMiKSkpID0geyAoZnB0cikgLTEgfTsNCiBzdGF0aWMgZnB0 ciBkdG9yX2xpc3RbMV0gX19hdHRyaWJ1dGVfXygoc2VjdGlvbigiLmR0b3Jz IikpKSA9IHsgKGZwdHIpIC0xIH07DQorc3RhdGljIGNoYXIgZWhfZnJhbWVf YmVnaW5bXSBfX2F0dHJpYnV0ZV9fKChzZWN0aW9uKCIuZWhfZnJhbWUiKSkp ID0geyB9Ow0KIA0KIHN0YXRpYyB2b2lkDQogZG9fY3RvcnModm9pZCkNCiB7 DQogICAgIGZwdHIgKmZwcDsNCisgICAgc3RhdGljIHN0cnVjdCBvYmplY3Qg b2JqZWN0Ow0KKw0KKyAgICBpZiAoX19yZWdpc3Rlcl9mcmFtZV9pbmZvKQ0K KwlfX3JlZ2lzdGVyX2ZyYW1lX2luZm8oZWhfZnJhbWVfYmVnaW4sICZvYmpl Y3QpOw0KIA0KICAgICBmb3IoZnBwID0gY3Rvcl9saXN0ICsgMTsgICpmcHAg IT0gMDsgICsrZnBwKQ0KIAk7DQpAQCAtNTQsNiArNjcsOSBAQA0KIA0KICAg ICBmb3IoZnBwID0gZHRvcl9saXN0ICsgMTsgICpmcHAgIT0gMDsgICsrZnBw KQ0KIAkoKipmcHApKCk7DQorDQorICAgIGlmIChfX2RlcmVnaXN0ZXJfZnJh bWVfaW5mbykNCisJX19kZXJlZ2lzdGVyX2ZyYW1lX2luZm8oZWhfZnJhbWVf YmVnaW4pOw0KIH0NCiANCiAvKg0KLS0tIGxpYi9jc3UvY29tbW9uL2NydGVu ZC5jLm9yaWcJTW9uIEp1bCAxMCAxNjoxNToyOCAyMDAwDQorKysgbGliL2Nz dS9jb21tb24vY3J0ZW5kLmMJU3VuIEp1bCAyMyAxNzo1OTozMyAyMDAwDQpA QCAtMjYsOCArMjYsMTEgQEANCiAgKi8NCiANCiAjaW5jbHVkZSA8c3lzL2Nk ZWZzLmg+DQorI2luY2x1ZGUgPHN5cy90eXBlcy5oPg0KIA0KIHR5cGVkZWYg dm9pZCAoKmZwdHIpKHZvaWQpOw0KIA0KIHN0YXRpYyBmcHRyIGN0b3JfZW5k WzFdIF9fYXR0cmlidXRlX18oKHNlY3Rpb24oIi5jdG9ycyIpKSkgX191bnVz ZWQgPSB7IDAgfTsNCiBzdGF0aWMgZnB0ciBkdG9yX2VuZFsxXSBfX2F0dHJp YnV0ZV9fKChzZWN0aW9uKCIuZHRvcnMiKSkpIF9fdW51c2VkID0geyAwIH07 DQorc3RhdGljIHVfaW50MzJfdCBlaF9mcmFtZV9lbmRbMV0gX19hdHRyaWJ1 dGVfXygoc2VjdGlvbigiLmVoX2ZyYW1lIikpKQ0KKwkJCQkgX191bnVzZWQg PSB7IDAgfTsNCg== --0-479365117-969036989=:78659 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="Makefile.inc" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="Makefile.inc" VEFSR0VUX0FSQ0g/PQkke01BQ0hJTkVfQVJDSH0NCg0KLmlmICR7VEFSR0VU X0FSQ0h9ID09ICJtaXBzZWwiIHx8ICR7VEFSR0VUX0FSQ0h9ID09ICJtaXBz ZWIiDQpHQ0NfQVJDSD0JbWlwcw0KLmVsc2UgDQpHQ0NfQVJDSD0JJHtUQVJH RVRfQVJDSH0NCi5lbmRpZg0KR0NDRElSPQkJJHsuQ1VSRElSfS8uLi8uLi8u Li9jb250cmliL2djYw0KDQpHRU5TUkNTPQl0bS5oDQpTUkNTKz0JCSR7R0VO U1JDU30NCkNMRUFORklMRVMrPQkke0dFTlNSQ1N9DQpDRkxBR1MrPQktSS4g LUkke0dDQ0RJUn0gLUkke0dDQ0RJUn0vY29uZmlnXA0KCQktSSR7LkNVUkRJ Un0vLi4vLi4vLi4vZ251L3Vzci5iaW4vY2MvY2NfdG9vbHMNCg0KIyAgICAg ICBLRUVQIFRISVMgSU4gU1lOQyB3aXRoIHNyYy9nY2MvbGliL2xpYmdjYy9N YWtlZmlsZSAhIQ0KdG0uaDoNCgllY2hvICcjaW5jbHVkZSAiJHtHQ0NfQVJD SH0vJHtHQ0NfQVJDSH0uaCInCT4gJHsuVEFSR0VUfQ0KLmlmICR7R0NDX0FS Q0h9ID09ICJpMzg2Ig0KCWVjaG8gJyNpbmNsdWRlICIke0dDQ19BUkNIfS9h dHQuaCInCQk+PiAkey5UQVJHRVR9DQouZW5kaWYNCgllY2hvICcjaW5jbHVk ZSA8ZnJlZWJzZC5oPicJCQk+PiAkey5UQVJHRVR9DQoJZWNobyAnI2luY2x1 ZGUgIiR7R0NDX0FSQ0h9L2ZyZWVic2QuaCInCQk+PiAkey5UQVJHRVR9DQou aWYgJHtHQ0NfQVJDSH0gPT0gImkzODYiDQoJZWNobyAnI2luY2x1ZGUgIiR7 R0NDX0FSQ0h9L3BlcmZvcm0uaCInCQk+PiAkey5UQVJHRVR9DQouZW5kaWYN CgllY2hvICcjaW5jbHVkZSA8ZnJlZWJzZC1uYXRpdmUuaD4nCQk+PiAkey5U QVJHRVR9DQo= --0-479365117-969036989=:78659-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 10: 1:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from androcles.com (androcles.com [204.57.240.10]) by hub.freebsd.org (Postfix) with ESMTP id 832BF37B423 for ; Fri, 15 Sep 2000 10:01:32 -0700 (PDT) Received: (from dhh@localhost) by androcles.com (8.9.3/8.9.3) id KAA87283; Fri, 15 Sep 2000 10:01:23 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <20000915142543.A3697@lflat.vas.mobilix.dk> Date: Fri, 15 Sep 2000 10:01:23 -0700 (PDT) From: "Duane H. Hesser" To: Vadim Belman Subject: RE: Live debugging of a process being hung in a syscall. Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "The Coroner's Toolkit" from Venema and Farmer includes a tool which paws through /proc and writes process memory for all processes running on the system to record files (intended for post-mortem analysis after a breakin). Sounds like this tool would do what you want. The toolkit can be found at http://www.fish.com/forensics/ or http://www.porcupine.org/forensics/ On 15-Sep-00 Vadim Belman wrote: > It seem like I got a NFS-related bug here where a httpd process > hung in a uninterruptable wait (a disk operation, most likely). In order to > locate the problem I need the process' stack trace first. > > gdb doesn't attach to the process for obvious reasons. Making a > crashdump doesn't inspire me at all. > > The question is: is there a way of working with /proc entries? I.e. > is it possible to get all what I need from, say, /proc//mem? > > -- > /Voland Vadim Belman > E-mail: voland@lflat.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -------------- Duane H. Hesser dhh@androcles.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 15 10:17:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ds-01.itg.discovery.com (ops.itg.discovery.com [198.147.13.130]) by hub.freebsd.org (Postfix) with ESMTP id 8EA7A37B423; Fri, 15 Sep 2000 10:17:26 -0700 (PDT) Received: by ds-01.itg.discovery.com; id NAA21959; Fri, 15 Sep 2000 13:16:51 -0400 (EDT) Received: by bet-su5-23.itg.discovery.com; id RAA09229; Fri, 15 Sep 2000 17:17:05 GMT Message-ID: <39C25991.1A261861@freebsd.org> Date: Fri, 15 Sep 2000 17:17:05 +0000 From: Patrick Gardella X-Mailer: Mozilla 4.61 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Aleksandr A.Babaylov" Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: need a recommendation of NIC References: <200009151428.SAA22804@aaz.links.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Aleksandr A.Babaylov" wrote: > > Pedro J. Lobo writes: > [Charset ISO-8859-1 unsupported, filtering to ASCII...] > > On Fri, 15 Sep 2000, Aleksandr A.Babaylov wrote: > > > > > Vladimir B. Grebenschikov writes: > > > > > > > > Intell EtherExpress > > > > fxp driver in FreeBSD, I think it best low-cost ethernet card for > > > > FreeBSD now. > > > As far as I know EtherExpress has hardware bug. > > > The easy way to trigger it is connect 2 EtherExpress by > > > crossover cable and load by traffic. > > > > :-? I've been using Pro/100 cards for years, and I've always found them > > rock stable. Can you explain us a bit more? > My mail based on message from David Greenman : > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=45338+47352+/usr/local/www/db/text/1998/freebsd-hackers/19981025.freebsd-hackers So don't use cross-over cables :) Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 10:53:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id CC70137B424 for ; Fri, 15 Sep 2000 10:53:47 -0700 (PDT) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id NAA26607 for freebsd-hackers@freebsd.org; Fri, 15 Sep 2000 13:53:41 -0400 (EDT) Date: Fri, 15 Sep 2000 13:53:41 -0400 From: Mathew KANNER To: freebsd-hackers@freebsd.org Subject: my crummy diskless howto page Message-ID: <20000915135341.E22175@cs.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I was whipping something up for in-house use. Maybe other would like to take a look at it. It describes how to set-up diskless workstations with PXE but without BOOTP. I'm sure it's relevance will quickly diminish once 4.2-RELEASE comes out. http://www.cs.McGill.CA/~mat/diskless/ If you find any problems, esp. ones that reveal inside info about us, please let me know. Thanks, --Mat -- Mathew Kanner SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 10:59:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 978BA37B42C; Fri, 15 Sep 2000 10:59:47 -0700 (PDT) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13ZzlA-0005hy-00; Fri, 15 Sep 2000 18:58:48 +0100 Date: Fri, 15 Sep 2000 18:58:48 +0100 To: Hao Zhang Cc: "'Pedro J. Lobo'" , "Aleksandr A.Babaylov" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: need a recommendation of NIC Message-ID: <20000915185848.A21753@firedrake.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zhanghao@nortelnetworks.com on Fri, Sep 15, 2000 at 10:17:25AM -0400 From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 15, 2000 at 10:17:25AM -0400, Hao Zhang wrote: > Thanks for your info. > I'm using FreeBSD v3.3 which suppports The PRO/100B with chipset 82558. If I > want to use Intel Pro/100+ with the 82559 chipset, what driver should I use? > fxp? Yes. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 11:23: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 2518E37B42C for ; Fri, 15 Sep 2000 11:22:58 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA28503; Fri, 15 Sep 2000 13:22:54 -0500 (CDT) (envelope-from dan) Date: Fri, 15 Sep 2000 13:22:54 -0500 From: Dan Nelson To: Vadim Belman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Live debugging of a process being hung in a syscall. Message-ID: <20000915132253.A27598@dan.emsphone.com> References: <20000915142543.A3697@lflat.vas.mobilix.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.3.8i In-Reply-To: <20000915142543.A3697@lflat.vas.mobilix.dk>; from "Vadim Belman" on Fri Sep 15 14:25:44 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Sep 15), Vadim Belman said: > It seem like I got a NFS-related bug here where a httpd process > hung in a uninterruptable wait (a disk operation, most likely). In order to > locate the problem I need the process' stack trace first. > > gdb doesn't attach to the process for obvious reasons. Making a > crashdump doesn't inspire me at all. > > The question is: is there a way of working with /proc entries? I.e. > is it possible to get all what I need from, say, /proc//mem? You can run "gcore " to generate a coredump from a running program. I do this all the time to programs that I *don't* want to attach directly to with gdb. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 11:55:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 7C3A337B424 for ; Fri, 15 Sep 2000 11:55:42 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e8FIteK83173; Fri, 15 Sep 2000 11:55:40 -0700 (PDT) Date: Fri, 15 Sep 2000 11:55:40 -0700 (PDT) From: Doug White To: Mathew KANNER Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: my crummy diskless howto page In-Reply-To: <20000915135341.E22175@cs.mcgill.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Sep 2000, Mathew KANNER wrote: > Hi All, > I was whipping something up for in-house use. Maybe other > would like to take a look at it. It describes how to set-up diskless > workstations with PXE but without BOOTP. I'm sure it's relevance will > quickly diminish once 4.2-RELEASE comes out. > > http://www.cs.McGill.CA/~mat/diskless/ > > If you find any problems, esp. ones that reveal inside info > about us, please let me know. It's already out of date -- loader can mount NFS natively now and no longer requires the mfsroot image. Mike Smith can elaborate. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 12:34:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id 3E73537B423 for ; Fri, 15 Sep 2000 12:34:29 -0700 (PDT) Received: (qmail 90709 invoked from network); 15 Sep 2000 19:34:23 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 15 Sep 2000 19:34:23 -0000 Date: Fri, 15 Sep 2000 12:34:22 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: hackers@freebsd.org Subject: SYM driver for Compaq 5500 Xeon? 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 Compaq Proliant 5500, with the on-board NCR SCSI: I get: pci0: (vendor=0x0e11, dev=0xa0f0) sym0: <875> port blahblah sym0: no NVRAM, ID 7, Fast-20, SE, parity-checking And the same for sym1. What's the magic incantation to make this work? Or do I need to use an adaptect to get installed, then update to -stable or somesuch? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 13:23:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bag-2.mail.digex.net (bag-2.mail.digex.net [204.91.99.101]) by hub.freebsd.org (Postfix) with ESMTP id E5BBC37B43E for ; Fri, 15 Sep 2000 13:23:40 -0700 (PDT) Received: from [209.49.190.34] (fireout.mbakercorp.com [209.49.190.34]) by bag-2.mail.digex.net (8.9.3/8.9.3) with SMTP id QAA16396 for ; Fri, 15 Sep 2000 16:23:22 -0400 (EDT) Received: from admin_4.mbakercorp.com by [209.49.190.34] via smtpd (for bag-2.mail.digex.net [204.91.99.101]) with SMTP; 15 Sep 2000 23:33:26 UT Received: from gatedom-Message_Server by mbakercorp.com with Novell_GroupWise; Fri, 15 Sep 2000 16:22:37 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Fri, 15 Sep 2000 16:22:34 -0400 From: "Joseph Wright" To: Subject: unsubscribe freebsd-hackers Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 14: 7:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front5.grolier.fr (front5.grolier.fr [194.158.96.55]) by hub.freebsd.org (Postfix) with ESMTP id 1ACC637B424 for ; Fri, 15 Sep 2000 14:07:52 -0700 (PDT) Received: from nas26-164.vlt.club-internet.fr (nas26-164.vlt.club-internet.fr [195.36.223.164]) by front5.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA04651; Fri, 15 Sep 2000 23:07:43 +0200 (MET DST) Date: Fri, 15 Sep 2000 22:50:49 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: SYM driver for Compaq 5500 Xeon? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Sep 2000, Jaye Mathisen wrote: > Compaq Proliant 5500, with the on-board NCR SCSI: >=20 > I get: >=20 > pci0: (vendor=3D0x0e11, dev=3D0xa0f0) > sym0: <875> port blahblah > sym0: no NVRAM, ID 7, Fast-20, SE, parity-checking >=20 >=20 > And the same for sym1. >=20 >=20 > What's the magic incantation to make this work? Or do I need to use an > adaptect to get installed, then update to -stable or somesuch? You seemed to say that your hard disks are not discovered in another email (I didn't see it but saw a reply to it). Could you describe the machine ? Does it have a some hot-plug backplane, for example ? What FreeBSD version ? About trying to install the system using an Adaptec, why not ? (Btw, it also happen that using a Symbios device sometimes cures a failing system that used an Adaptec controller). G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 14:15:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id 986C137B422 for ; Fri, 15 Sep 2000 14:15:35 -0700 (PDT) Received: (qmail 10129 invoked from network); 15 Sep 2000 21:15:34 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 15 Sep 2000 21:15:34 -0000 Date: Fri, 15 Sep 2000 14:15:33 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: hackers@FreeBSD.ORG Subject: Re: SYM driver for Compaq 5500 Xeon? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is with the 4.1 boot floppies. But the drives don't show. I'm booting -v now to see. Just did, still no drives. Nothing extraordinary in the -v output. it's a compaq PROLIANT, 5500, quad xeon, 1.25GB of RAM, 2 9GB scsi disks on ID's 0 and 1 of the only controller. bootloader sees them just fine. I don't know much about hot-plug stuff, it looks relatively normal to me, and it's an older rev. That's about it. My adaptec suggestion was only because perhaps the driver wasn't integrated until after the floppies were made, so I could get installed, then update the kernel. I guess I"ll try that route, but I'd rather not. On Fri, 15 Sep 2000, [ISO-8859-1] Gérard Roudier wrote: > > > On Fri, 15 Sep 2000, Jaye Mathisen wrote: > > > Compaq Proliant 5500, with the on-board NCR SCSI: > > > > I get: > > > > pci0: (vendor=0x0e11, dev=0xa0f0) > > sym0: <875> port blahblah > > sym0: no NVRAM, ID 7, Fast-20, SE, parity-checking > > > > > > And the same for sym1. > > > > > > What's the magic incantation to make this work? Or do I need to use an > > adaptect to get installed, then update to -stable or somesuch? > > You seemed to say that your hard disks are not discovered in another > email (I didn't see it but saw a reply to it). > > Could you describe the machine ? > Does it have a some hot-plug backplane, for example ? > What FreeBSD version ? > > About trying to install the system using an Adaptec, why not ? > (Btw, it also happen that using a Symbios device sometimes cures a failing > system that used an Adaptec controller). > > Gérard. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 15: 6:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id C72BF37B422 for ; Fri, 15 Sep 2000 15:06:47 -0700 (PDT) Received: from nas22-71.vlt.club-internet.fr (nas22-71.vlt.club-internet.fr [195.36.170.71]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id AAA12557; Sat, 16 Sep 2000 00:06:36 +0200 (MET DST) Date: Fri, 15 Sep 2000 23:49:42 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: SYM driver for Compaq 5500 Xeon? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Sep 2000, Jaye Mathisen wrote: > This is with the 4.1 boot floppies. But the drives don't show. I'm > booting -v now to see. >=20 > Just did, still no drives. Nothing extraordinary in the -v output. >=20 > it's a compaq PROLIANT, 5500, quad xeon, 1.25GB of RAM, 2 9GB scsi disks > on ID's 0 and 1 of the only controller. >=20 > bootloader sees them just fine. The bootloader uses the BIOS. > I don't know much about hot-plug stuff, it looks relatively normal to me, > and it's an older rev. That's about it. If you mean that the disks are hot-pluggable, then it could be the SCSI device that allows to control the hot-plug bay that makes problem during the scan of the SCSI BUS. If there is some way to desactivate this 'for now hypothetical device' or to update its firmware, you should try either. > My adaptec suggestion was only because perhaps the driver wasn't > integrated until after the floppies were made, so I could get installed, > then update the kernel. No problem here, if it works with Adaptec. Nobody wants to waste one's time. I just wanted to say that this also may apply in the reverse direction. Regards, G=E9rard. > I guess I"ll try that route, but I'd rather not. >=20 > On Fri, 15 Sep 2000, [ISO-8859-1] G=E9rard Roudier wrote: >=20 > >=20 > >=20 > > On Fri, 15 Sep 2000, Jaye Mathisen wrote: > >=20 > > > Compaq Proliant 5500, with the on-board NCR SCSI: > > >=20 > > > I get: > > >=20 > > > pci0: (vendor=3D0x0e11, dev=3D0xa0f0) > > > sym0: <875> port blahblah > > > sym0: no NVRAM, ID 7, Fast-20, SE, parity-checking > > >=20 > > >=20 > > > And the same for sym1. > > >=20 > > >=20 > > > What's the magic incantation to make this work? Or do I need to use = an > > > adaptect to get installed, then update to -stable or somesuch? > >=20 > > You seemed to say that your hard disks are not discovered in another > > email (I didn't see it but saw a reply to it). > >=20 > > Could you describe the machine ? > > Does it have a some hot-plug backplane, for example ? > > What FreeBSD version ? > >=20 > > About trying to install the system using an Adaptec, why not ? > > (Btw, it also happen that using a Symbios device sometimes cures a fail= ing > > system that used an Adaptec controller). > >=20 > > G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 17:39:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2334837B424 for ; Fri, 15 Sep 2000 17:39:15 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA12959; Fri, 15 Sep 2000 17:37:37 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA06418; Fri, 15 Sep 2000 17:37:37 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 15 Sep 2000 17:37:37 -0700 (PDT) Message-Id: <200009160037.RAA06418@vashon.polstra.com> To: hackers@freebsd.org Cc: fjoe@iclub.nsu.ru Subject: Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1 In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > > `__register_frame_info' should be called from `do_ctors' in > src/lib/csu/common/crtbegin.c to load frame information from .eh_frame > sections before any constructors are executed because try/catch can be > used in constructors of static objects (`__register_frame_info' > is defined in src/contrib/gcc/frame.c, this file is linked into > libgcc[_r].a). however `__register_frame_info' uses locks and other > threading stuff (using pthreads on FreeBSD) so we must have pthreads > initialized before locks are used. > > another issue with our pthreads initialization is that pthreads can be > used in static object constructors so the first `pthread_xxx' call can > happen before `_thread_init' is called from constructor of our > _thread_init_invoker (it depends on order in which constructors are placed > in .ctors section). > > I see two solutions (both seem to be hacks for me): > 1) we can insert if (!initted) ... in `pthread_once' (this seem to be the > first pthreads function called from __register_frame_info) > 2) we can insert > > #if __GTHREADS > _thread_init(); > #endif > > at the very beginning of `__register_frame_info' > > The second approach seems to be cleaner but require changes in > src/contrib/gcc/ Here is another possibility: we could call _thread_init() from crt1.o. The patch (untested) is below. It calls _thread_init() if and only if that symbol is defined -- i.e., libc_r is linked in. What do you think about this solution? John Index: crt1.c =================================================================== RCS file: /home/ncvs/src/lib/csu/i386-elf/crt1.c,v retrieving revision 1.4 diff -u -r1.4 crt1.c --- crt1.c 1999/08/27 23:57:57 1.4 +++ crt1.c 2000/09/16 00:30:51 @@ -48,6 +48,9 @@ extern int _DYNAMIC; #pragma weak _DYNAMIC +extern void _thread_init(void); +#pragma weak _thread_init + #ifdef __i386__ #define get_rtld_cleanup() \ ({ fptr __value; \ @@ -91,6 +94,8 @@ #ifdef GCRT monstartup(&eprol, &etext); #endif + if (&_thread_init != NULL) + _thread_init(); _init(); exit( main(argc, argv, env) ); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 19: 3: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 6E6DB37B424 for ; Fri, 15 Sep 2000 19:03:00 -0700 (PDT) Received: from bellatlantic.net (client-151-198-135-11.nnj.dialup.bellatlantic.net [151.198.135.11]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id WAA11713; Fri, 15 Sep 2000 22:02:48 -0400 (EDT) Message-ID: <39C2D571.EF9548BA@bellatlantic.net> Date: Fri, 15 Sep 2000 22:05:37 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: =?iso-8859-1?Q?G=E9rard?= Roudier Cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: SYM driver for Compaq 5500 Xeon? References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gérard Roudier wrote: > > On Fri, 15 Sep 2000, Jaye Mathisen wrote: > > > I don't know much about hot-plug stuff, it looks relatively normal to me, > > and it's an older rev. That's about it. > > If you mean that the disks are hot-pluggable, then it could be the SCSI > device that allows to control the hot-plug bay that makes problem during > the scan of the SCSI BUS. If there is some way to desactivate this 'for > now hypothetical device' or to update its firmware, you should try either. FWIW, on older Compaqs this deactivation was achieved by disconnecting the small power cable going from the power supply to this piece of intelligence at the back of the drive bays. It could be quite possible that Compaq did something bad with the circuitry around the Symbios chip, they like to change everything and then write their own drivers. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 19:50:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id D242937B42C; Fri, 15 Sep 2000 19:50:26 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G2n7v32143; Sat, 16 Sep 2000 03:49:07 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G2n3n02415; Sat, 16 Sep 2000 03:49:03 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Ben Smithurst , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.org, current@FreeBSD.org, brian@Awfulhak.org Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message from Poul-Henning Kamp of "Thu, 14 Sep 2000 14:37:06 +0200." <56645.968935026@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Sep 2000 03:49:02 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). [.....] > I would argue that the programs and the scripts that call them are > already broken, but hey... So (just to add fuel to the mass opposition), do this without temporary files: count=$(program | tee /dev/stderr | wc -l) exit $count But then, you also said: > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. so I guess this could result in count=$(program |. cat | wc -l) exit $count (substitute correct "|.*" syntax - whatever that is). > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 15 20:15:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 443AE37B42C for ; Fri, 15 Sep 2000 20:15:24 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G3BEv32249; Sat, 16 Sep 2000 04:11:14 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8G3BAn15495; Sat, 16 Sep 2000 04:11:11 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009160311.e8G3BAn15495@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: ptacek@dashmail.net Cc: freebsd-hackers@FreeBSD.org, brian@Awfulhak.org Subject: Re: Getting all the IP address for a machine from code... In-Reply-To: Message from "Chris Ptacek" of "Wed, 13 Sep 2000 20:12:47 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Sep 2000 04:11:10 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am looking for a way to get all the IP addresses that are configured a > machine. I need to do this in c source code, and without using DNS services > (ie: gethostname/gethostbyname won't work). I am hoping there are some > system calls I can use to get this information. Thanks in advance for any > help. This is a bit late.... I'd favour copying src/usr.sbin/portmap/from_local.c (a reasonably recent version of the code). It can be built as a main program that literally just outputs a list of local IP numbers. > - Chris -- 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 Sat Sep 16 3: 1:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 7A60937B422; Sat, 16 Sep 2000 03:01:12 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Sep 2000 11:01:11 +0100 (BST) To: Robert Watson Cc: Chris Ptacek , freebsd-hackers@FreeBSD.ORG Subject: Re: Getting all the IP address for a machine from code... In-reply-to: Your message of "Fri, 15 Sep 2000 11:52:31 EDT." X-Request-Do: Date: Sat, 16 Sep 2000 11:01:10 +0100 From: David Malone Message-ID: <200009161101.aa71225@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is possible to get interface lists on earlier versions (and I hope > still current versions) using the ioctl interfaces described in Stevens. > See also ifconfig.c source from various versions of FreeBSD :-). I think Garret suggested that the ioctl method was deprecated? I wrote some code just to figure out how the sysctl stuff is packed 'cos it's not that obvoius - I've included it below incase it might be of use to someone. David. #include #include #include #include #include #include #include #include #include #include #include #include /* * This is an example of how to find info about the currently configured * interfaces. * * The code in rwhod and ifconfig if pretty hard to understand as it * doesn't really exploit the structure of what you're returned. We use * a sysctl to get the interface list, which returns a buffer with a * list of things each starting with: * * msglen * version * type * * The generic type used to with this start in the kernel seems to be * "struct rt_msghdr". For this sysctl we call it returns a message of * type RTM_IFINFO followed by a list of RTM_NEWADDR for each interface. * This corrisponds to the interface and each of the configurations you * "put" on it with ifconfig. * * The RTM_IFINFO message contains a struct if_msghdr followed by a * list of struct sockaddr. The RTM_NEWADDR contains a struct ifa_msghdr * followed by a list of struct sockaddr. * * The struct sockaddr's sizes have been truncated to the nearest * power of two into which the data will fit. The struct sockaddr's * included depend on what is apropriate to this message. You can tell * which of RTAX_* sockaddr's have been included by looking at the set * bits of ifm_addrs or ifam_addrs, so you have to expand them out into * an array of struct sockaddr's of size RTAX_MAX. */ void unpack_addrs(struct sockaddr *packed,struct sockaddr *unpacked,int rti_addrs); void print_addrs(struct sockaddr *unpacked,int rti_addrs); int main(int argc, char **argv) { char *buf, *lim, *next; /* For sysctl */ size_t needed; int mib[6]; struct rt_msghdr *rtm; /* For decoding messages */ struct if_msghdr *ifm; struct ifa_msghdr *ifam; struct sockaddr *packed_addr; /* For decoding addresses */ struct sockaddr unpacked_addr[RTAX_MAX]; mib[0] = CTL_NET; mib[1] = PF_ROUTE; mib[2] = 0; mib[3] = AF_INET; mib[4] = NET_RT_IFLIST; mib[5] = 0; if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) errx(1, "route-sysctl-estimate"); if ((buf = malloc(needed)) == NULL) errx(1, "malloc"); if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) errx(1, "actual retrieval of interface table"); lim = buf + needed; for( next = buf; next < lim; next += rtm->rtm_msglen ) { rtm = (struct rt_msghdr *)next; switch( rtm->rtm_type ) { case RTM_IFINFO: ifm = (struct if_msghdr *)next; packed_addr = (struct sockaddr *)(next + sizeof(struct if_msghdr)); printf("Found an interface.\n"); if( ifm->ifm_flags & IFF_UP ) printf("It is currently up.\n"); if( ifm->ifm_addrs != 0 ) { printf("These addresses were available:\n"); unpack_addrs(packed_addr,unpacked_addr, ifm->ifm_addrs); print_addrs(unpacked_addr,ifm->ifm_addrs); } else printf("No addresses were available.\n"); break; case RTM_NEWADDR: ifam = (struct ifa_msghdr *)next; packed_addr = (struct sockaddr *)(next + sizeof(struct ifa_msghdr)); printf("Found extra addresses associated with interface.\n"); unpack_addrs(packed_addr,unpacked_addr, ifam->ifam_addrs); print_addrs(unpacked_addr,ifam->ifam_addrs); break; default: errx(1, "unexpected rtm type"); } } exit(0); } #define ROUNDUP(a) \ ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) : sizeof(long)) void unpack_addrs(struct sockaddr *packed,struct sockaddr *unpacked,int rti_addrs) { int i; for( i = 0; i < RTAX_MAX; i++ ) { bzero(&unpacked[i],sizeof(unpacked[i])); if( rti_addrs & (1<sa_len); packed = (struct sockaddr *)(((char *)packed) + ROUNDUP(packed->sa_len)); } } } void print_addrs(struct sockaddr *unpacked,int rti_addrs) { int i; for( i = 0; i < RTAX_MAX; i++ ) { if( (rti_addrs & (1<sin_addr)); break; default: printf("address in family %d", unpacked[i].sa_family); break; } printf(".\n"); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 6:15:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 5B13837B422 for ; Sat, 16 Sep 2000 06:15:26 -0700 (PDT) Received: (qmail 22295 invoked by uid 0); 16 Sep 2000 13:15:24 -0000 Received: from p3ee21661.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.97) by mail.gmx.net with SMTP; 16 Sep 2000 13:15:24 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id KAA30413; Sat, 16 Sep 2000 10:04:47 +0200 Date: Sat, 16 Sep 2000 10:04:47 +0200 From: Gerhard Sittig To: current@FreeBSD.org, hackers@freebsd.org Subject: Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!) Message-ID: <20000916100447.I27034@speedy.gsinet> Mail-Followup-To: current@FreeBSD.org, hackers@freebsd.org References: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Sep 16, 2000 at 03:49:02AM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG using Brian's post since I don't have the original around ... On Sat, Sep 16, 2000 at 03:49 +0100, Brian Somers wrote: > > [ attribution missing, is it Poul-Henning Kamp's text? ] > > > The majority of these programs could be handled by adding > > knowledge of "-" as a magic filename to fopen(3). > [.....] > > At the same time I would really love if we implemented "|.*" > > to mean "do an popen(3)" instead. The only reasonable way to provide this functionality to apps not wanting to reinvent it themselves without breaking those who feel that files should be just that - files - is a _new_ function next to fopen(3) named some rather alerting way like superduperopen(3) with flags like SDO_KNOWS_STDIN, SDO_CAN_PIPEFROM, SDO_CAN_PIPEINTO and whatever other extension you can think of. 32 of these new behaviour patterns should suffice for quite a while. :) This will collapse the "-" recognition and handling logic in existing programs to passing a simple flag to a different function (with only one more int parameter compared to fopen(3)) and leave those alone who just want to fopen(3) any file. And when the options set is extended no app will "inherit" unwanted and unexpected features turning out to be holes. Unless there's a SDO_DO_ANY_PRESENT_AND_FUTURE_MAGIC flag passed with a value of 0xffffffff. But authors doing so will get what they deserve. :> One could even think of switching to the new function "to be ready" and passing a SDO_DONT_DO_ANY_MAGIC flag. How much sense does it make to think about implementing tee and select methods this way? Like "open file1 and file2 and write to both of them whatever I give to you" and "give me data coming in from whatever file is in this set"? The only problem is to determine available characters to separate these names. '+' as well as ':', ',' and ';' are perfectly valid characters for constructing filenames. '&' seems to be too, but could be used rarely enough. And the split upon these new separators actually should be done only when the appropriate SDO_ flags are passed. e.g. superduperopen("file1&file2", "a+", SDO_TEEFILES) superduperopen("file1&file2", "r" , SDO_SELECT) Semantics could be braindead simple: TEE will just dup any data to every file specified and SELECT will have implicit priorities since there's no logic doing round robing or something. This will suffice for randomly filled input channels being fed more alternatively rather than concurrently. Of course the mode parameter from fopen(3) and the magicmask parameter from superduperopen(3) (i.e. the second and third parameters) have to pass certain checks. Nobody should try to read from "|command". And I cannot see any use for "write to whatever descriptor is ready to write to first" as would result from "w" and SDO_SELECT. Feel free to correct the flag's data type. I have the feeling not all int's have 32bits. :) Some other means of storage might be more appropriate while still being easy to combine and to pass to the function. But I feel strings like "STD,PIPE,TEE" are harder to parse and single character notation like the "wt" mode flags are harder to find (think of) and to read (in terms of eyeballing the source code) for the sdo case. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 8: 9:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 348DD37B424 for ; Sat, 16 Sep 2000 08:09:13 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA00610; Sat, 16 Sep 2000 11:09:01 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 16 Sep 2000 11:09:01 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: David Malone Cc: Chris Ptacek , freebsd-hackers@FreeBSD.ORG Subject: Re: Getting all the IP address for a machine from code... In-Reply-To: <200009161101.aa71225@salmon.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Sep 2000, David Malone wrote: > > It is possible to get interface lists on earlier versions (and I hope > > still current versions) using the ioctl interfaces described in Stevens. > > See also ifconfig.c source from various versions of FreeBSD :-). > > I think Garret suggested that the ioctl method was deprecated? That said, the ioctl() method is probably also portable across platforms. Recommending the deprecating quasi-standard interfaces in favor of local interfaces for third-party application writers would probably be a mistake. Where it's not possible to perform the function with the portable API, fine, of course. :-) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 12: 6:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from merc95.us.sas.com (merc95.us.sas.com [149.173.6.5]) by hub.freebsd.org (Postfix) with ESMTP id A133F37B43C for ; Sat, 16 Sep 2000 12:06:09 -0700 (PDT) Received: from merc95.us.sas.com ([127.0.0.1]) by merc95.us.sas.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2651.58) id TA8FL3AW; Sat, 16 Sep 2000 15:06:08 -0400 Received: from 10.28.149.26 by merc95.us.sas.com (InterScan E-Mail VirusWall NT); Sat, 16 Sep 2000 15:06:08 -0400 (Eastern Daylight Time) Received: from bb01f39.unx.sas.com (bb01f39.unx.sas.com [10.16.2.246]) by mozart.unx.sas.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id PAA02810 for ; Sat, 16 Sep 2000 15:06:06 -0400 (EDT) Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id PAA77922 for freebsd-hackers@FreeBSD.org; Sat, 16 Sep 2000 15:06:06 -0400 (EDT) (envelope-from jwd) Date: Sat, 16 Sep 2000 15:06:06 -0400 From: John DeBoskey To: freebsd-hackers@FreeBSD.org Subject: > 32k directories in a directory Message-ID: <20000916150606.A77687@unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Ok, no laughing folks. I've run up against an application (which I do not have control over) that wants to create more than 32k directories in a directory. in syslimits.h I find: #define LINK_MAX 32767 /* max file link count */ which I think is what I'm running up against. This is referenced in sys/ufs/ufs/ufs_vnops.c at which point EMLINK is returned. Yes, this is being done against a ufs filesystem. I also note some int32_t variables in the dir structures which worries me. Has anyone built a system which can support > 32k dirs in a dir, or have any ideas what is involved? The FAQ and handbook don't appear to address this anywhere. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 13:49:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 5564A37B422; Sat, 16 Sep 2000 13:49:57 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Sep 2000 21:49:56 +0100 (BST) Date: Sat, 16 Sep 2000 21:49:55 +0100 From: David Malone To: John DeBoskey Cc: freebsd-hackers@FreeBSD.org Subject: Re: > 32k directories in a directory Message-ID: <20000916214955.A71692@walton.maths.tcd.ie> References: <20000916150606.A77687@unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000916150606.A77687@unx.sas.com>; from jwd@FreeBSD.org on Sat, Sep 16, 2000 at 03:06:06PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 03:06:06PM -0400, John DeBoskey wrote: > #define LINK_MAX 32767 /* max file link count */ Looking at /usr/include/ufs/ufs/dinode.h, which seems to describe the format of the on-disk inode I see that di_nlink is a int16_t, for which the largest positive value is 32767. If you try increasing this things will almost certainly blow up. > Has anyone built a system which can support > 32k dirs in > a dir, or have any ideas what is involved? You really don't want to have a directory with 32K entries on a UFS filesystem - it will be painfully slow and inefficient. I've tried to clean up a news filesystem which had directories with large numbers of entries and you can only delete entries once every few seconds - in the end I unmounted the filesystem, clried the directory and fscked. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 14:25:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 6003937B422; Sat, 16 Sep 2000 14:25:36 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id RAA08307; Sat, 16 Sep 2000 17:20:11 -0400 Date: Sat, 16 Sep 2000 17:20:11 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: device naming convention 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 is the FreeBSD naming convention for devices of disk slices and labels? Considering my system is installed on the first partition of /dev/wd0 (non-dedicated), these are the block-device interfaces I have to my disk: wd0 wd0c wd0f wd0s1 wd0s1c wd0s1f wd0s2 wd0a wd0d wd0g wd0s1a wd0s1d wd0s1g wd0s3 wd0b wd0e wd0h wd0s1b wd0s1e wd0s1h wd0s4 Questions: 1. What are wd0[a-h] used for? 2. If wd0s1 is my first slice, why isn't it named wd0s0? 3. If I format wd0s2 as any type (Xenix for example), will /dev now contain wd0s2[a-h]? Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1 doesn't span to the end of disk: 4. If I want to use /dev/wd0s2 as a raw slice for reading and writing, what are the steps to follow? 4a. Do I need to format the partition as any type? If so is there a recommended type (perhaps one which won't be recognised by the bootloader would be preferable)? 4b. Should I then be using /dev/rwd0s2 or /dev/rwd0s2a for reading and writing (of course, this is assuming block i/o of multiples of 512 bytes)? Lastly, where else could I have found this information other than asking on the FreeBSD mailing list? Thanks, Marc Tardif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 15:13: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.rcn.com (146-115-58-158.c4-0.wtr-ubr1.sbo-wtr.ma.cable.rcn.com [146.115.58.158]) by hub.freebsd.org (Postfix) with ESMTP id 9336037B424 for ; Sat, 16 Sep 2000 15:13:04 -0700 (PDT) Received: from rcn.com (localhost [127.0.0.1]) by smtp.rcn.com (8.9.3/8.9.3) with ESMTP id SAA03346; Sat, 16 Sep 2000 18:13:04 -0400 (EDT) Message-ID: <39C3F070.36E7E030@rcn.com> Date: Sat, 16 Sep 2000 18:13:04 -0400 From: David Bein Reply-To: bein@world.std.com Organization: Network Appliance (New England) X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: Panic key on std PC keyboard .... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... Does anyone know which key is the PNC key on a typical keyboard? This is the key which with sysctl machdep.enable_panic_key=1 should force a panic. Earlier today I found my machine wedged and had to power cycle to get unstuck. So for future reference, this will be very handy info. Thanks very much. --David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 15:29:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0D3FE37B424 for ; Sat, 16 Sep 2000 15:29:41 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Sep 2000 23:29:40 +0100 (BST) Date: Sat, 16 Sep 2000 23:29:40 +0100 From: David Malone To: bein@world.std.com Cc: freebsd-hackers@FreeBSD.org Subject: Re: Panic key on std PC keyboard .... Message-ID: <20000916232939.A74382@walton.maths.tcd.ie> References: <39C3F070.36E7E030@rcn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39C3F070.36E7E030@rcn.com>; from bein@rcn.com on Sat, Sep 16, 2000 at 06:13:04PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 06:13:04PM -0400, David Bein wrote: > Does anyone know which key is the PNC key on a typical keyboard? > This is the key which with sysctl machdep.enable_panic_key=1 should force > a panic. Earlier today I found my machine wedged and had to power cycle > to get unstuck. So for future reference, this will be very handy info. Just grepping through /usr/share/syscons/keymaps/ it looks like the panic key isn't usually enabeled. So you have to enable the sysctl and edit a keymap to make some combination of keys panic the machine. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 16:27:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id A2B4A37B422; Sat, 16 Sep 2000 16:27:10 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id DAA17240; Sun, 17 Sep 2000 03:27:05 +0400 (MSD) Message-Id: <200009162327.DAA17240@aaz.links.ru> Subject: Re: device naming convention In-Reply-To: from "Marc Tardif" at "Sep 16, 0 05:20:11 pm" To: intmktg@CAM.ORG (Marc Tardif) Date: Sun, 17 Sep 2000 03:27:05 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Marc Tardif writes: > What is the FreeBSD naming convention for devices of disk slices and > labels? Considering my system is installed on the first partition of > /dev/wd0 (non-dedicated), these are the block-device interfaces I > have to my disk: > > wd0 wd0c wd0f wd0s1 wd0s1c wd0s1f wd0s2 > wd0a wd0d wd0g wd0s1a wd0s1d wd0s1g wd0s3 > wd0b wd0e wd0h wd0s1b wd0s1e wd0s1h wd0s4 > > Questions: > 1. What are wd0[a-h] used for? For wd0sN[a-h] where N is number of first slice recognized as FreeBSD slice > 2. If wd0s1 is my first slice, why isn't it named wd0s0? wd0s0 == wd0 wd0s0a == wd0a > 3. If I format wd0s2 as any type (Xenix for example), > will /dev now contain wd0s2[a-h]? Content of /dev is totally undependent of any hardware and kernel conditions. Do yourself cd /dev ; ./MAKEDEV wd0s2h for wd0s2[a-h] entries > Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1 > doesn't span to the end of disk: > 4. If I want to use /dev/wd0s2 as a raw slice for reading > and writing, what are the steps to follow? You can't write several blocks near /dev/wd0s2 beginning. Use /dev/wd0 with proper address > 4a. Do I need to format the partition as any type? If so > is there a recommended type (perhaps one which won't > be recognised by the bootloader would be preferable)? It depends on usage. And remember - kernel looks up every slice to find FreeBSD label - even if you mark it 0 (unused) > 4b. Should I then be using /dev/rwd0s2 or /dev/rwd0s2a > for reading and writing (of course, this is assuming > block i/o of multiples of 512 bytes)? You can do what you want, but remember, [a-h] can be used only if partitino have a FreeBSD label For example, for label on wd0s2 # some space not included in FreeBSD partition 514080 0 a: 514080 514080 b: 514080 1028160 you can use wd0s2a AND wd0s2 as different file systems IF you properly initialise with newfs. > Lastly, where else could I have found this information other > than asking on the FreeBSD mailing list? Read sources and experiment. BE AWARE - FreeBSD 4.X in difference with FreeBSD 2.2.X is highly unstable while experiment with labels -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 18:17: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id EFD7237B423; Sat, 16 Sep 2000 18:16:56 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id VAA09153; Sat, 16 Sep 2000 21:11:27 -0400 Date: Sat, 16 Sep 2000 21:11:27 -0400 (EDT) From: Marc Tardif To: "Aleksandr A.Babaylov" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: device naming convention In-Reply-To: <200009162327.DAA17240@aaz.links.ru> 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 [ snip ] > > 1. What are wd0[a-h] used for? > For wd0sN[a-h] where N is number of first slice recognized > as FreeBSD slice > If I understand correctly, wd0[a-h] will be the same as wd0s3[a-h] in a situation where DOS is on first slice, Linux on second and FreeBSD on third, right? But what if the fourth slice is also FreeBSD? In such a case, I'll assume you meant "booted slice" instead of "first slice", where the slice selected when booting will be referred to by the OS as wd0[a-h] which would translate to "current slice". Confirmation of my assumption would be appreciated. > > 2. If wd0s1 is my first slice, why isn't it named wd0s0? > wd0s0 == wd0 > wd0s0a == wd0a > I somehow doubt that. Considering wd0s* goes from 1 to 4 inclusively, I would tend to believe the first slice is wd0s1. [ snip ] > > Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1 > > doesn't span to the end of disk: > > 4. If I want to use /dev/wd0s2 as a raw slice for reading > > and writing, what are the steps to follow? > You can't write several blocks near /dev/wd0s2 beginning. > Use /dev/wd0 with proper address > That is rather risky. Wouldn't it be safer to have a device name I could dedicate to some purpose. In such a case, I could chown the device to an appropriate username and group. Furthermore, I could avoid the unfortunate mistake of overwriting my current FreeBSD fs in case I get the addresses wrong. > > 4a. Do I need to format the partition as any type? If so > > is there a recommended type (perhaps one which won't > > be recognised by the bootloader would be preferable)? > It depends on usage. And remember - kernel looks up every > slice to find FreeBSD label - even if you mark it 0 (unused) > How does it depend on usage? Are some formats preferable for some specific usage (consider I'll only be using the raw interface to the device)? [ snip ] Thanks for the first message, Marc Tardif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 19:39:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 10FD437B506; Sat, 16 Sep 2000 19:39:39 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id GAA18264; Sun, 17 Sep 2000 06:39:34 +0400 (MSD) Message-Id: <200009170239.GAA18264@aaz.links.ru> Subject: Re: device naming convention In-Reply-To: from "Marc Tardif" at "Sep 16, 0 09:11:27 pm" To: intmktg@CAM.ORG (Marc Tardif) Date: Sun, 17 Sep 2000 06:39:34 +0400 (MSD) Cc: babolo@links.ru, freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG From: "Aleksandr A.Babaylov" 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 Marc Tardif writes: > [ snip ] > > > 1. What are wd0[a-h] used for? > > For wd0sN[a-h] where N is number of first slice recognized > > as FreeBSD slice > > > If I understand correctly, wd0[a-h] will be the same as wd0s3[a-h] in a > situation where DOS is on first slice, Linux on second and FreeBSD on > third, right? But what if the fourth slice is also FreeBSD? In such a > case, I'll assume you meant "booted slice" instead of "first slice", where > the slice selected when booting will be referred to by the OS as wd0[a-h] > which would translate to "current slice". Confirmation of my assumption > would be appreciated. As far as I remember not booted, but first May be it is version dependant? > > > 2. If wd0s1 is my first slice, why isn't it named wd0s0? > > wd0s0 == wd0 > > wd0s0a == wd0a > I somehow doubt that. Considering wd0s* goes from 1 to 4 inclusively, I > would tend to believe the first slice is wd0s1. Bits in minor with slice number can be from 0 to 31 (5 bits). 0 is for wd0s0 == wd0 And lok at /dev/MAKEDEV > [ snip ] > > > Assuming /dev/wd0s2 contains a few blocks, ie /dev/wd0s1 > > > doesn't span to the end of disk: > > > 4. If I want to use /dev/wd0s2 as a raw slice for reading > > > and writing, what are the steps to follow? > > You can't write several blocks near /dev/wd0s2 beginning. > > Use /dev/wd0 with proper address > That is rather risky. Wouldn't it be safer to have a device name I could > dedicate to some purpose. In such a case, I could chown the device to an > appropriate username and group. Furthermore, I could avoid the unfortunate > mistake of overwriting my current FreeBSD fs in case I get the addresses > wrong. My tests in this area are old enough, may be up to 3.1 It depends on whether /dev/wd0s2 has a FreeBSD label or not. If pure MSDOS slice, it is not write protected, and in times I had some M$ slices I restored it by dd. Any slices that recognized with labels (not only FreeBSD labels, but FreeBSD take not care about whos labels are) have some write protected block so you can't restore, for example, boot loader by simlpe dd. In such a case you need use for example dd of=/dev/wd0 seek=(shift of slice from disk begin) > > > 4a. Do I need to format the partition as any type? If so > > > is there a recommended type (perhaps one which won't > > > be recognised by the bootloader would be preferable)? > > It depends on usage. And remember - kernel looks up every > > slice to find FreeBSD label - even if you mark it 0 (unused) > How does it depend on usage? Are some formats preferable for some specific > usage (consider I'll only be using the raw interface to the device)? Partition you mean is M$ partition? (slice in FBSD) or partition in FBSD slice? You are NOT restricted by FBSD slices to have ufs in. But if use some slice without ufs be aware from occasionaly create some pattern that FBSD think as label. May be just not use slice begin. If you mean FBSD partition, the first of them hase write protected blocks. I was not tested another. The same - just not use partition's begin. IMHO 8K, but I am not hard in this. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 21:24: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id AAB1C37B422 for ; Sat, 16 Sep 2000 21:24:00 -0700 (PDT) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA52144 for ; Sat, 16 Sep 2000 21:23:55 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39C4475A.DBDA6C5@gorean.org> Date: Sat, 16 Sep 2000 21:23:54 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-091 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: mergemaster RFC (long) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings campers, Mergemaster first made its appearance as a port two years ago tomorrow, and became part of the FreeBSD source tree last October 20th. Lots of things have changed since the original version of the program (or script, whatever), and there are some proposals on the board for it that I'd really like to get some input on. For those that aren't aware, mm started its life kind of on a dare. My life before getting the full time job that I have now was mostly doing consulting work, so I did a lot of updates remotely. Making the system safe for remote upgrading has always been a major goal of mine. The proto-mergemaster was just a little script that I used because I got tired of forgetting the little bits and pieces. During a conversation on line about how the configuration system should be expanded, I mentioned that I had a little script that helped during upgrades, and a lot of people wanted a copy. Since I had to clean the code up anyway, and since certain people said it couldn't be done, I created what turned into the mergemaster we know and love today. I had some design goals when I started the project, most of which came from my background in doing remote upgrades. The first goal was to make mm as secure as possible. There are numerous precautions built in to avoid overwriting files inappropriately, avoid typical /tmp file overwriting exploits, etc. I also wanted it to be as independent as possible from having to know anything about specific files. This would allow it to continue to be useful no matter what got changed or upgraded. To accomplish this goal I mercilessly cribbed some ideas from Nik Clayton's make world page. The next goal was to make the program as simple as possible given the complexity of some of the stuff that it deals with. I tried to accomplish that by making it as unix like as possible, with tools, options, etc. that act as much like "regular" unix tools as my knowledge and ability allowed. Finally, one of the central design goals was to never take any action that the user didn't specifically request. ALL of the defaults in the program are to do nothing, because in almost all cases that's the safest thing to (not) do. That final goal has been compromised somewhat in the past year, as different people have requested various hacks to avoid having to look at certain files that they never want to upgrade. I'm uncomfortable with this for several reasons. First, because of the way mm works it's already possible (and in fact, desirable) to "hide" local modifications to files by keeping their cvs $FreeBSD ($Id) tags the same as the current version in source. In this way, you only have to deal with the file when there are actual updates, which I feel strongly is something you _should_ do anyway. However, over time I've come to accept the fact that mm now belongs more to the community than to me exclusively, so what *I* think you should do is less important than it was. The other struggle I'm having currently is that the thing is really becoming a beast. I wanted it to be small, simple and fast, and in the tradition of unix tools to do one thing and do it well. The thing already has WAY more options than I ever use, which isn't necessarily the ultimate barometer, but it is starting to give me the willies. The other reason I'm growing increasingly concerned is the number of posts in -questions, et al that go something like; "I see in UPDATING that I should be using mergemaster, but I tried it and I don't really understand what the hell it does, so I just didn't bother." I tried to make the man page as simple as possible, and include stuff that I wish was present in other man pages, but it's not uncommon for people to not even bother reading the man page, or read it, get overwhelmed by the options, give up, and go anyway. All of that is background to aid in understanding where I'm coming from when I talk about the following. There are a couple of categories of proposed changes. Some are things that I'm definitely going to do. Some are things that I plan to do, and am currently working on and/or have patches for. I'm including those two categories because if I don't someone will feel the need to suggest them. :) The final category are things that I would like comments about, hence the subject of this e-mail. First, the things I am definitely going to do. Christian "naddy" Weisgerber has taken on the task of porting mm to openbsd. He has made some very reasonable requests that will make his life easier and reduce gratuitous differences between versions. Also, several people have asked for the ability to specify DESTDIR, which is an easy fix and definitely an understandable request. Second, the things I am planning to do. Several people have asked for mergemaster to make use of cvs, going all the way back to freebsdcon. However, it's only been recently that anyone has given me actual concrete plans on things to integrate. The first in this category is an option to check whether the installed version of a file is different from the stock cvs version of that same file, and if it's not, just go ahead and install it. The second is to offer the ability to patch the installed version of the file with the cvs diff as an alternative to merging with sdiff. Both of these are excellent ideas, and although they will take a little more work, they are worth it, and will be done soon. Another option that I've decided to add is cribbed from the dhclient script. I'm going to add variables to the .mergemasterrc file for mergemaster-start and mergemaster-end scripts (names may change). These scripts will run after the temproot environment is built, and after mm is done with it's run. These scripts would be source'd from within mm so all the variables will be available to them. This should allow people to add in their own "options" that I don't want to add to the program. Last, the things I want comment on. Top of this list is the very (very!) frequently requested item of having mm automatically eliminate certain files from consideration. As stated, I am extremely uncomfortable with this idea. However, it comes up SO often that some method of dealing with it has to be agreed on. There are two alternatives that come to mind. The first is to just refer users to the mergemaster-start script idea above and let them nuke whatever they want. If the weight of opinion here is to add the feature, here's how it would look. This is cobbled together from various people's suggestions. We need a list of files somewhere (probably in .mergemasterrc) that people don't ever want to have to deal with via the "normal" mm process. If a file on that list has been updated (according to the cvs tag) then instead of presenting that file to the user, it will be ignored the first time through. Then, at the end of the script there will be a printout similar to what happens when the user leaves a file to do by hand later. Something like: *** The following files from your ignore list have newer versions than the ones you have installed, and will remain for you to deal with by hand: master.passwd crontab Then the user will have a choice of either deleting the temproot directory, or dealing with those files by hand. Overall, I prefer the idea of letting people do it on their own. Next on the list of things I'm open to suggestions on is a small script I wrote that compares the variables in /etc/rc.conf[.local] to the ones in /etc/defaults/rc.conf, and does the same for make.conf. This helps you catch those situations where variables you have and depend on may have changed. It's a short script, so I don't see it as really needing to be on its own, but the question is where in the mm process to put it. I generally run mm before I build my world, since if things blow up I have good backups. Other people do it after world & kernel but before reboot (which is sound advice for new users anyway). That's fine for the rc.conf variables, but doesn't really help you for the make.conf variables. I could add more switches (ack!) to just do the conf file comparisons seperately I suppose... This also brings up the question of which files in /etc are good to examine before a world build. In the past there have been things in make.conf, master.passwd and group that have all bit people and caused failed builds (and/or installs). I have kicked around the idea of having a "pre-build" mode for mergemaster that does the temproot build then checks out these 3 files (any other suggestions?) and does the make.conf comparison for you. Is this overkill? Too much handholding? There was a PR filed in regards to the current situation with the new sendmail moving the aliases file to /etc/mail, and mergemaster's "failure" to deal with that. In my opinion, I don't think that fixing this "problem" is in mergemaster's purview. If the site depends on their aliases file, the administrator should probably take note of the fact that mm is installing a new aliases file in a new location and take appropriate steps. There was also a suggestion to have mm create a symlink in /etc to /etc/mail/aliases, which I definitely do not think is a good idea. If the site needs this, the administrator should handle it. If it's not essential, mm shouldn't be messing with it. The analogy in the PR regarding /.cshrc and /.profile is not really valid, since that is a default part of the system which has no objectionable alternatives. My experience is that anything involving mail is likely to start a holy war, and I want to stay far from it. Additionally there is another alternative that I haven't seen discussed, namely putting both /etc/aliases and /etc/mail/aliases in sendmail.cf. This may be undesirable from the "cleanliness" perspective, but it would solve the problem. I have an idea related to getting users to actually READ the man page which entails checking for the presence of a $HOME/.mergemasterrc file, and if one is not present to print a helpful message. This could get annoying though for experienced users doing an update on a new machine. And the last of the ideas I want feedback on is related to the problem of determining permissions on the files to be installed. To my knowledge there is no existing C utility that will tell you the octal permissions on a file, and preferably also combine them with the umask to spit out what the permissions should be. My current solution for that is a couple of one line perl scripts, but I really want to eliminate that as my contribution to the "don't make anything in the base depend on perl" campaign. I have written a little tiny program in C to do this which could be included along with mergemaster, what do people think? It is possible to do the same thing in sh, but it's very cumbersome, unless someone can suggest some combination of existing utilities that I haven't considered yet. The main problem with doing it in sh (which I've done in the past) is that the umask effectively means "different" things if it's a binary/directory or if it's a regular file, so even though getting the permissions is easy (with ls, whatever) combining it with the umask is hard. Of course, I could always take that whole section out, and just install the files with the permissions created by /usr/src/etc/Makefile. I see less need now of custom permissions than I did ages ago, but what do others think? Ok... those are all of my ideas. Now comment away! If you have some additional suggestions of your own, don't hesitate to add those on as well. I finally have some time to work with this, and I'd really like to get something that's ready to MFC by the 9/22 deadline for the 4.1.1 release. Keep those cards and letters coming, Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 16 22:45: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id AB2C937B424 for ; Sat, 16 Sep 2000 22:44:59 -0700 (PDT) Received: (qmail 30897 invoked from network); 17 Sep 2000 05:45:06 -0000 Received: from arsenic.theshell.com (HELO tequila) (root@63.236.138.5) by arsenic.theshell.com with SMTP; 17 Sep 2000 05:45:06 -0000 From: "Peter Avalos" To: Cc: Subject: passwd.1 Date: Sun, 17 Sep 2000 00:48:27 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know who to contact about this, so I'm hoping some people subscribed to this list have commit access. I found some spelling errors in passwd(1) manpage. I have RELENG_4 installed. Here's the output of diff -u: --- /usr/src/usr.bin/passwd/passwd.1 Wed Mar 1 04:20:07 2000 +++ passwd.1 Sat Sep 16 22:33:16 2000 @@ -78,7 +78,7 @@ .if n "mixpasswordcase" setting for a user's login class). Allowing lower case passwords may be useful where the password file will be used in situations where only -lower case passwords are permissable, such as when using Samba to +lower case passwords are permissible, such as when using Samba to authenticate Windows clients. In all other situations, numbers, upper case letters and meta characters are encouraged. .Pp @@ -186,7 +186,7 @@ an NIS server to also be a client) in which case the .Nm passwd command needs to be told what domain to operate on. -.It Fl s Ar host +.It Fl h Ar host Specify the name of an NIS server. This option, in conjunction with the @@ -202,8 +202,8 @@ be .if t ``localhost''. .if n "localhost". -This can be overidden with the -.Fl s +This can be overridden with the +.Fl h flag. The specified hostname need not be the name of an NIS master: the name of the NIS master for a given map can be determined by querying any If I'm composing to the wrong list, please let me know who I should contact about errors like this. Peter Avalos TheShell.com -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS/ED/B d-(+) s:+> a-- C++$ UBLO++++$ P+ L++++ E- W+ N+ o? K? w(++) !O M- V- PS+ PE++ Y+ PGP++ t+@ 5 X- R- tv+ b++ DI- D-- G e>+++ h-- r++ y++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message