From owner-freebsd-hackers Sun Oct 15 0:55:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 0EC6D37B503 for ; Sun, 15 Oct 2000 00:55:41 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9F7vwh00361; Sun, 15 Oct 2000 00:57:59 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010150757.e9F7vwh00361@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jonathan Chen Cc: hackers@freebsd.org Subject: Re: PCI secondary bus In-reply-to: Your message of "Sat, 14 Oct 2000 23:44:41 EDT." <20001014234441.F78298@spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Oct 2000 00:57:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While writing the new cardbus code, I ran into a problem where certain > BIOSes (Dells in particular) does not initialize the pci configuration > space of the pci to cardbus bridge. On a "normal" laptop, the BIOS will > fill in a memory address, irq lines, and the secondary and subordinate bus > numbers. On a dell laptop, those would be left as 0. Warner and I just chatted about this and PCI IRQ routing for a bit. There are a couple of issues that need to be resolved here: - We need a function which will hand out valid PCI bus numbers. We need to do a little exploring to see whether we can just hand them out at random (I don't think we can do this) or whether we need to be more choosy. I get the general impression that we'll need to allocate a range of bus numbers for a bridge based on its parents' space allocation. - We need a callout in the PCI bus' code which handles bus_alloc_resource for SYS_RES_IRQ; specifically, if the indicated interrupt's corresponding configuration space register still contains 0xff (want an interrupt, not assigned), we need to ripple back up through the parent PCI bridge(s) to route a suitable interrupt. To do this we need to get at the $PIR structure and/or the ACPI PCI interrupt routing data for PCI bridges; we're pretty close to having both of these working now. > I could work around > the memory/irq issues, but I have no clue what to fill in for the secondary > and subordinate bus numbers. Is there a magical function (in kernel, > pcibios or otherwise) that would generate these values for me? And if not, > how do I get the numbers? Would it be alright if I assign an arbitrary > number as long as there is no conflict? Any help would be > appreciated. Thanks. In the short term, as long as the device is a child of bus 0 and there are no other root busses you can probably just use eg. 2 (save 1 because it'll probably get eaten by your AGP bridge). -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 15 4:58:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 2BC0A37B503 for ; Sun, 15 Oct 2000 04:58:23 -0700 (PDT) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id 10BDA172E8 for ; Sun, 15 Oct 2000 13:58:15 +0200 (MET DST) Received: (from fn@localhost) by trinity.radio-do.de (8.11.0/8.9.3) id e9FBwFM05241 for freebsd-hackers@FreeBSD.ORG; Sun, 15 Oct 2000 13:58:15 +0200 (CEST) (envelope-from fn@gatekeeper.radio-do.de) Date: Sun, 15 Oct 2000 13:58:15 +0200 From: Frank Nobis To: freebsd-hackers@FreeBSD.ORG Subject: UDMA ICRC WRITE ERROR Message-ID: <20001015135815.A5133@radio-do.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a IDE drive spitting out this messages: ad3: UDMA ICRC WRITE ERROR blk# 48562489 retrying ad3: UDMA ICRC READ ERROR blk# 24576329 retrying ad3: UDMA ICRC WRITE ERROR blk# 69108025 retrying ad3: UDMA ICRC WRITE ERROR blk# 73728313 retrying From the boot messages: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 ad2: 42934MB [87233/16/63] at ata1-master using UDMA33 ad3: 42934MB [87233/16/63] at ata1-slave using UDMA33 Do I have to exchange the drive ? I think I should. In the case of replacing is the best thing to do, that leads to the question, how to replace this drive ? It is a part of a vinum raid5 volume. Is detach and attach the right way ? Regards Frank PS. If someone want more information about the System (PRESMPNG) dual PIII on an ASUS P2B-DS, just let me know. I want avoid spamming the list with big config and dmesg output -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 15 11:34:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 1FA5137B66C for ; Sun, 15 Oct 2000 11:34:32 -0700 (PDT) Received: from localhost (scottj@localhost) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id LAA62045; Sun, 15 Oct 2000 11:34:31 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Date: Sun, 15 Oct 2000 11:34:31 -0700 (PDT) From: Joseph Scott X-Sender: scottj@pebkac.owp.csus.edu To: Gregory Sutter Cc: hackers@FreeBSD.ORG Subject: Re: Routing issues In-Reply-To: <20001014233212.H3444@klapaucius.zer0.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 Sat, 14 Oct 2000, Gregory Sutter wrote: > I'm setting up a network that looks like this: > > > --Internet----Router---Firewall > | > | /--- host > Switch----NAT-----<----- host > | \----- host > | \----- etc... > --------- > | | > email ns When I first looked at this, is there a reason why it isn't something like this instead : ---Internet---Router---| | | Firewall---Nat (Many Hosts) | | | (Multiple Servers) You have to have a hub/switch between the firewall and each network (the NAT and the server). You end up with a firewall with three nics. One the surface what I'd probably do with something like this is actually NAT both the many hosts and the servers network, but on the servers use a 1:1 IP mapping (bimap if you are using IPFilter). The thing that would interest me is if you could use bridging between the outside firewall nic and the servers network in conjuction with NAT'ing the many hosts network. This is something I've wondered about but never tried. If if it's doable I'm not sure it would be a good idea. Having the three nics would allow you to filter based on that entire network based on which nic the traffic is coming from or heading to. > > In other words, a fairly typical small network. I've got an 8-IP > subnet; all hosts outside the NAT have real IPs: > > router: 1.2.3.193 > firewall: 1.2.3.196 fxp0 > 1.2.3.197 fxp1 > nat: 1.2.3.198 > email: 1.2.3.194 > ns: 1.2.3.195 > > The problem I'm having is with my routing. Surprise. Here is > the routing table for the firewall: > > default 1.2.3.193 fxp0 > 1.2.3.193 link#1 fxp0 > 1.2.3.192/29 link#2 fxp1 > 1.2.3.196 lo0 > 1.2.3.197 lo0 > > The gateway_enable (net.inet.ip.forwarding) is also enabled on > the firewall. > > >From the firewall, I can reach any host with no problems. However, > from hosts inside the firewall, I cannot reach outside, and vice > versa. I feel I must be missing something obvious, but have played > with routes for hours to no avail. > > Does anyone see a problem with the routing of this network? > > Greg > -- > Gregory S. Sutter Computing is a terminal addiction. > mailto:gsutter@zer0.org > http://www.zer0.org/~gsutter/ > PGP DSS public key 0x40AE3052 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > --- Joseph Scott joseph.scott@owp.csus.edu The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 15 20:24: 1 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 792C637B66C for ; Sun, 15 Oct 2000 20:23:58 -0700 (PDT) Received: from bloop.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 15 Oct 2000 22:25:51 -0500 Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e9G3N5G48210 for ; Sun, 15 Oct 2000 22:23:05 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200010160323.e9G3N5G48210@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Getting Linux NIS to work with FreeBSD NIS servers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Oct 2000 22:23:05 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Linux box appears toknow about the users, it just cant get the passwords right - something tickles my mind about DES vs MD5, is this the case, and how do I convert my MD5 passwords if needed? 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 Oct 15 20:26:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 96D9437B502 for ; Sun, 15 Oct 2000 20:26:12 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 1E4271C41; Sun, 15 Oct 2000 23:26:12 -0400 (EDT) Date: Sun, 15 Oct 2000 23:26:12 -0400 From: Bill Fumerola To: Stephen Hocking Cc: hackers@freebsd.org Subject: Re: Getting Linux NIS to work with FreeBSD NIS servers Message-ID: <20001015232612.S37870@jade.chc-chimes.com> References: <200010160323.e9G3N5G48210@bloop.craftncomp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010160323.e9G3N5G48210@bloop.craftncomp.com>; from shocking@houston.rr.com on Sun, Oct 15, 2000 at 10:23:05PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 15, 2000 at 10:23:05PM -0500, Stephen Hocking wrote: > The Linux box appears toknow about the users, it just cant get the passwords > right - something tickles my mind about DES vs MD5, is this the case, and how > do I convert my MD5 passwords if needed? Yes thats the case, no there is no "conversion" program. If there was a conversion program it would mean there is a way to translate to plaintext and that obviously isn't the case (modulo brute-force). -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 15 20:38:12 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 D055737B66C for ; Sun, 15 Oct 2000 20:38:09 -0700 (PDT) Received: (qmail 6389 invoked from network); 16 Oct 2000 03:38:15 -0000 Received: from arsenic.theshell.com (HELO tequila) (root@63.236.138.5) by arsenic.theshell.com with SMTP; 16 Oct 2000 03:38:15 -0000 From: "Peter Avalos" To: "Bill Fumerola" , "Stephen Hocking" Cc: Subject: RE: Getting Linux NIS to work with FreeBSD NIS servers Date: Sun, 15 Oct 2000 22:39:59 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20001015232612.S37870@jade.chc-chimes.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually Linux machines "can" handle MD5 passwords. Most likely, the problem is that you haven't merged the hashed passwords into the passwd.* maps. From /var/yp/Makefile: # If you want to use a FreeBSD NIS server to serve non-FreeBSD clients # (i.e. clients who expect the password field in the passwd maps to be # valid) then uncomment this line. This will cause $YPDIR/passwd to # be generated with valid password fields. This is insecure: FreeBSD # normally only serves the master.passwd maps (which have real encrypted # passwords in them) to the superuser on other FreeBSD machines, but # non-FreeBSD clients (e.g. SunOS, Solaris (without NIS+), IRIX, HP-UX, # etc...) will only work properly in 'unsecure' mode. # UNSECURE = "True" 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------ > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Bill Fumerola > Sent: Sunday, October 15, 2000 10:26 PM > To: Stephen Hocking > Cc: hackers@freebsd.org > Subject: Re: Getting Linux NIS to work with FreeBSD NIS servers > > > On Sun, Oct 15, 2000 at 10:23:05PM -0500, Stephen Hocking wrote: > > The Linux box appears toknow about the users, it just cant get > the passwords > > right - something tickles my mind about DES vs MD5, is this the > case, and how > > do I convert my MD5 passwords if needed? > > Yes thats the case, no there is no "conversion" program. If there was > a conversion program it would mean there is a way to translate to > plaintext > and that obviously isn't the case (modulo brute-force). > > -- > Bill Fumerola - Network Architect, BOFH / Chimes, Inc. > billf@chimesnet.com / billf@FreeBSD.org > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 15 20:45: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id D5AA937B66F for ; Sun, 15 Oct 2000 20:45:05 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 662D11C41; Sun, 15 Oct 2000 23:45:05 -0400 (EDT) Date: Sun, 15 Oct 2000 23:45:05 -0400 From: Bill Fumerola To: Peter Avalos Cc: Stephen Hocking , hackers@freebsd.org Subject: Re: Getting Linux NIS to work with FreeBSD NIS servers Message-ID: <20001015234505.T37870@jade.chc-chimes.com> References: <20001015232612.S37870@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from pavalos@theshell.com on Sun, Oct 15, 2000 at 10:39:59PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 15, 2000 at 10:39:59PM -0500, Peter Avalos wrote: > Actually Linux machines "can" handle MD5 passwords. Most likely, the problem > is that you haven't merged the hashed passwords into the passwd.* maps. I stand corrected. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 15 21: 7:31 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 E895D37B66D for ; Sun, 15 Oct 2000 21:07:25 -0700 (PDT) Received: from bloop.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 15 Oct 2000 23:09:22 -0500 Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e9G46ZG84680; Sun, 15 Oct 2000 23:06:35 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200010160406.e9G46ZG84680@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Fumerola Cc: Peter Avalos , hackers@freebsd.org Subject: Re: Getting Linux NIS to work with FreeBSD NIS servers In-Reply-To: Message from Bill Fumerola of "Sun, 15 Oct 2000 23:45:05 EDT." <20001015234505.T37870@jade.chc-chimes.com> Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Oct 2000 23:06:35 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The UNSECURE option in /var/yp/Makefile is the answer - thanks muchly! 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 Mon Oct 16 6:24:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 65E7F37B503 for ; Mon, 16 Oct 2000 06:24:22 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id PAA08183; Mon, 16 Oct 2000 15:23:48 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200010161323.PAA08183@info.iet.unipi.it> Subject: Re: Routing issues In-Reply-To: <39E95406.8F1C0717@cybercable.fr> from Thierry Herbelot at "Oct 15, 2000 08:51:50 am" To: Thierry Herbelot Date: Mon, 16 Oct 2000 15:23:48 +0200 (CEST) Cc: Gregory Sutter , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In your case, you should use a "bridging" firewall, where ony one of the > ethernet interfaces has an IP address (you can then set up your firewall > in a "stealth" config, where it does not touch the TTL in the IP > packets) a "stealth" router is still different from a bridge, it requires a reconfig of the addresses. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 7:24:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cosrel1.hp.com (cosrel1.hp.com [156.153.255.170]) by hub.freebsd.org (Postfix) with ESMTP id 3342A37B503 for ; Mon, 16 Oct 2000 07:24:30 -0700 (PDT) Received: from udlkern.fc.hp.com (udlkern.fc.hp.com [15.1.52.48]) by cosrel1.hp.com (Postfix) with ESMTP id F38C5417 for ; Mon, 16 Oct 2000 08:24:41 -0600 (MDT) Received: from udlkern.fc.hp.com (erdos.fc.hp.com [15.1.54.169]) by udlkern.fc.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 SMKit7.0) id IAA26560 for ; Mon, 16 Oct 2000 08:24:28 -0600 (MDT) Message-ID: <39EB0F9C.9646488B@udlkern.fc.hp.com> Date: Mon, 16 Oct 2000 08:24:28 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.72 [en] (X11; U; HP-UX B.11.00 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: syscons Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a question about syscons, and I was wondering if there were anyone out there who knew enough about the initialization sequence of syscons to answer... Basically, I'm trying to write a TGA driver around syscons, but TGA is a PCI card, and it seems, after having looked through the syscons code and the VGA driver, that syscons is better suited to ISA-style adapters, i.e., it absoultely has to call (tga/vga)_configure() very early in boot (i.e., before main()) to register adapters, and this registration requires a probe of adapters _before_ PCI services are available to do a probe of PCI adapters--is this true? If so, does anyone know of a nifty way around this conundrum? Andrew Miklic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 9:12:19 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 D218137B66F for ; Mon, 16 Oct 2000 09:12:16 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.9.3/8.9.3) with SMTP id MAA27997 for ; Mon, 16 Oct 2000 12:12:15 -0400 (EDT) (envelope-from arr@watson.org) Date: Mon, 16 Oct 2000 12:12:15 -0400 (EDT) From: "Andrew R. Reiter" To: freebsd-hackers@freebsd.org Subject: FireWire Device Driver 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 hihi. I was reading back emails of -hackers from like july '99 and a guy from Japan had been working on a very promising FireWire device driver ... Anyway, the other night I had picked up a really awesome book that goes into detail on FireWire and had basically decided to work on it myself (until I realized someone had already started work on it!)... However, the last email that was seemingly sent regarding this issue was one by jkh in which he gives a major value for the device driver,... and asks when it should be ready for use with -current. I have emailed the guy from japan and have received no response... so I am wondering if anyone else knows what's up with the firewire situation and whether I should go ahead and pick up work on it? Andrew *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 9:45:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hecky.it.northwestern.edu (hecky.acns.nwu.edu [129.105.16.51]) by hub.freebsd.org (Postfix) with ESMTP id B892837B66D for ; Mon, 16 Oct 2000 09:45:39 -0700 (PDT) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id LAA28973 for ; Mon, 16 Oct 2000 11:45:38 -0500 (CDT) Received: from confusion.net (dhcp089155.res-hall.nwu.edu [199.74.89.155]) by hecky.acns.nwu.edu via smap (V2.0) id xma028219; Mon, 16 Oct 00 11:44:43 -0500 Message-ID: <39EB3051.58E631CA@confusion.net> Date: Mon, 16 Oct 2000 11:44:01 -0500 From: Laurence Berland X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Starting to code Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's a good place to start if you're a university student with limited hardware who wants to jump in and get going with the FreeBSD code. Right now I've got a PPro 200 with 32 MB of ram and lots of disk space (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of tossing Current on also, and maybe making the cvs repo a separate partition so I can share it between current and stable. Mostly at this point I'm looking for a way to jump head first into the code. Where's a good starting point? tia, -- Laurence Berland Intern, Flooz.com Northwestern '04 stuyman@confusion.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 9:51:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7B94337B672 for ; Mon, 16 Oct 2000 09:51:38 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9GGpa310113; Mon, 16 Oct 2000 09:51:36 -0700 (PDT) Date: Mon, 16 Oct 2000 09:51:36 -0700 From: Alfred Perlstein To: Laurence Berland Cc: hackers@FreeBSD.ORG Subject: Re: Starting to code Message-ID: <20001016095135.C272@fw.wintelcom.net> References: <39EB3051.58E631CA@confusion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39EB3051.58E631CA@confusion.net>; from stuyman@confusion.net on Mon, Oct 16, 2000 at 11:44:01AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Laurence Berland [001016 09:46] wrote: > What's a good place to start if you're a university student with limited > hardware who wants to jump in and get going with the FreeBSD code. > Right now I've got a PPro 200 with 32 MB of ram and lots of disk space > (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of > tossing Current on also, and maybe making the cvs repo a separate > partition so I can share it between current and stable. This is probably a good setup to have for your hacking. > Mostly at this point I'm looking for a way to jump head first into the > code. Where's a good starting point? How to become a freebsd hacker in 3 (not so) easy steps: 1) figure out what you want to work on or learn more about. 2) look at the code in the system, become utterly confused. 3) ask on freebsd-hackers or irc (zb^3 on efnet/irc.freebsd.org) and be enlightened. If you can't accomplish step 1, take a look at the PR system and see if you can close a problem report or at least bring it up for dicussion if you think you see a partial solution. best of luck, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 10:48:28 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 586EE37B671 for ; Mon, 16 Oct 2000 10:48:25 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9GHmNn46150; Mon, 16 Oct 2000 11:48: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 LAA02638; Mon, 16 Oct 2000 11:48:22 -0600 (MDT) Message-Id: <200010161748.LAA02638@harmony.village.org> To: "Andrew R. Reiter" Subject: Re: FireWire Device Driver Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 16 Oct 2000 12:12:15 EDT." References: Date: Mon, 16 Oct 2000 11:48:22 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Andrew R. Reiter" writes: : which he gives a major value for the device driver,... and asks when it : should be ready for use with -current. I have emailed the guy from japan : and have received no response... so I am wondering if anyone else knows : what's up with the firewire situation and whether I should go ahead and : pick up work on it? Last I heard Mike Smith and he were cleaning up the code for inclusion in FreeBSD. This was in July or August of this year. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 12:59:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 562D437B66E; Mon, 16 Oct 2000 12:59:23 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 7A4266A901; Mon, 16 Oct 2000 21:59:22 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AF39C63E0056; Mon, 16 Oct 2000 22:04:09 +0200 Message-Id: <5.0.0.25.0.20001016215411.048b8bc0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 16 Oct 2000 21:59:32 +0200 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org From: Len Conrad Subject: custom boot/install CD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a disk replacement at a remote site with a FreeBSD firewall and the hardware guy's done his deed, we need to be able to boot a custom FreeBSD CD that will script a total FreeBSD custom install to a bare disk, from fdisk through "shutdown now -r". Are there any how-to's in this area? tia, Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 13:26:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.120.21]) by hub.freebsd.org (Postfix) with ESMTP id ADEF037B66C for ; Mon, 16 Oct 2000 13:26:17 -0700 (PDT) Received: from fraser.sfu.ca (vanepp@fraser.sfu.ca [142.58.101.25]) by rm-rstar.sfu.ca (8.10.1/8.10.1/SFU-5.0H) with ESMTP id e9GKQBF05802 for ; Mon, 16 Oct 2000 13:26:11 -0700 (PDT) From: Peter Van Epp Received: (from vanepp@localhost) by fraser.sfu.ca (8.9.2/8.9.2/SFU-5.0C) id NAA01828 for freebsd-hackers@freebsd.org; Mon, 16 Oct 2000 13:26:10 -0700 (PDT) Message-Id: <200010162026.NAA01828@fraser.sfu.ca> Subject: bpf.c select fix for review To: freebsd-hackers@freebsd.org Date: Mon, 16 Oct 2000 13:26:10 -0700 (PDT) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While working on the new argus version I discovered that there is a bug in the /sys/net/bpf.c code if you are doing select with a timeout (which tcpdump isn't). Basically if you set up tcpreplay on another machine and send a less than full buffer (9 packets 2300 bytes in my case) to a FreeBSD 4.1 RELEASE machine, argus won't see the packets. It turns out that because it is using select (and not immediate mode) the partially full buffer won't get passed up to libpcap. The OpenBSD folks have a partial fix (which only gets the first packet up and leaves the other 8 dangling). I ported that to FreeBSD and then made a fix which appears to work based on what their code looked to be trying to do (as opposed to what it does which is incorrect). Basically at receive packet time the tick counter is stored in a variable in the capture structure. When the select/poll timeout occurs it checks if the current tick time is > then the last received packet count + the timeout value. If so it rotates the (partially full) packet buffer and signals to wake up the process. While this appears to work (and match the Solaris behavior on the same file) I figured I'd see if anyone sees a glaring hole in the fix before submitting a bug report on it. Peter Van Epp / Operations and Technical Support Simon Fraser University, Burnaby, B.C. Canada *** /sys/net/bpf.c.orig Sat Oct 14 19:00:59 2000 --- /sys/net/bpf.c Mon Oct 16 09:30:24 2000 *************** *** 1054,1061 **** if (events & (POLLIN | POLLRDNORM)) { if (d->bd_hlen != 0 || (d->bd_immediate && d->bd_slen != 0)) revents |= events & (POLLIN | POLLRDNORM); ! else ! selrecord(p, &d->bd_sel); } splx(s); return (revents); --- 1054,1076 ---- if (events & (POLLIN | POLLRDNORM)) { if (d->bd_hlen != 0 || (d->bd_immediate && d->bd_slen != 0)) revents |= events & (POLLIN | POLLRDNORM); ! else { ! /* ! * If there is a timeout and no data in the hold buffer ! * see if there has been data in the capture buffer ! * for more than a timeout interval. If so rotate the ! * buffer to push the packets to the user. ! */ ! if ((d->bd_slen != 0) && (d->bd_hlen == 0)) { ! if ((d->bd_rtout != -1) && ! (d->bd_rdStart + d->bd_rtout) > ticks) { ! ROTATE_BUFFERS(d); ! revents |= events & (POLLIN | POLLRDNORM); ! } ! } else ! selrecord(p, &d->bd_sel); ! ! } } splx(s); return (revents); *************** *** 1219,1224 **** --- 1234,1245 ---- */ (*cpfn)(pkt, (u_char *)hp + hdrlen, (hp->bh_caplen = totlen - hdrlen)); d->bd_slen = curlen + totlen; + + /* + * Mark the time the last packet was seen for poll timeout processing. + */ + + d->bd_rdStart = ticks; } /* *** /sys/net/bpfdesc.h.orig Sat Oct 14 19:16:07 2000 --- /sys/net/bpfdesc.h Sat Oct 14 19:21:54 2000 *************** *** 69,74 **** --- 69,75 ---- struct bpf_if * bd_bif; /* interface descriptor */ u_long bd_rtout; /* Read timeout in 'ticks' */ + u_long bd_rdStart; /* when the read started */ struct bpf_insn *bd_filter; /* filter code */ u_long bd_rcount; /* number of packets received */ u_long bd_dcount; /* number of packets dropped */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 14: 5: 2 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 07CB637B503 for ; Mon, 16 Oct 2000 14:04:58 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.9.3/8.9.3) with SMTP id RAA31955; Mon, 16 Oct 2000 17:04:46 -0400 (EDT) (envelope-from arr@watson.org) Date: Mon, 16 Oct 2000 17:04:46 -0400 (EDT) From: "Andrew R. Reiter" To: Peter Van Epp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bpf.c select fix for review In-Reply-To: <200010162026.NAA01828@fraser.sfu.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 Please don't use a java/c++-ism like bdStart... atleast call it bdstart. Thanks, Andrew On Mon, 16 Oct 2000, Peter Van Epp wrote: > While working on the new argus version I discovered that there is a > bug in the /sys/net/bpf.c code if you are doing select with a timeout (which > tcpdump isn't). Basically if you set up tcpreplay on another machine and send > a less than full buffer (9 packets 2300 bytes in my case) to a FreeBSD 4.1 > RELEASE machine, argus won't see the packets. It turns out that because it > is using select (and not immediate mode) the partially full buffer won't get > passed up to libpcap. The OpenBSD folks have a partial fix (which only gets > the first packet up and leaves the other 8 dangling). I ported that to FreeBSD > and then made a fix which appears to work based on what their code looked to > be trying to do (as opposed to what it does which is incorrect). > Basically at receive packet time the tick counter is stored in a > variable in the capture structure. When the select/poll timeout occurs it > checks if the current tick time is > then the last received packet count + > the timeout value. If so it rotates the (partially full) packet buffer and > signals to wake up the process. While this appears to work (and match the > Solaris behavior on the same file) I figured I'd see if anyone sees a glaring > hole in the fix before submitting a bug report on it. > > Peter Van Epp / Operations and Technical Support > Simon Fraser University, Burnaby, B.C. Canada > > *** /sys/net/bpf.c.orig Sat Oct 14 19:00:59 2000 > --- /sys/net/bpf.c Mon Oct 16 09:30:24 2000 > *************** > *** 1054,1061 **** > if (events & (POLLIN | POLLRDNORM)) { > if (d->bd_hlen != 0 || (d->bd_immediate && d->bd_slen != 0)) > revents |= events & (POLLIN | POLLRDNORM); > ! else > ! selrecord(p, &d->bd_sel); > } > splx(s); > return (revents); > --- 1054,1076 ---- > if (events & (POLLIN | POLLRDNORM)) { > if (d->bd_hlen != 0 || (d->bd_immediate && d->bd_slen != 0)) > revents |= events & (POLLIN | POLLRDNORM); > ! else { > ! /* > ! * If there is a timeout and no data in the hold buffer > ! * see if there has been data in the capture buffer > ! * for more than a timeout interval. If so rotate the > ! * buffer to push the packets to the user. > ! */ > ! if ((d->bd_slen != 0) && (d->bd_hlen == 0)) { > ! if ((d->bd_rtout != -1) && > ! (d->bd_rdStart + d->bd_rtout) > ticks) { > ! ROTATE_BUFFERS(d); > ! revents |= events & (POLLIN | POLLRDNORM); > ! } > ! } else > ! selrecord(p, &d->bd_sel); > ! > ! } > } > splx(s); > return (revents); > *************** > *** 1219,1224 **** > --- 1234,1245 ---- > */ > (*cpfn)(pkt, (u_char *)hp + hdrlen, (hp->bh_caplen = totlen - hdrlen)); > d->bd_slen = curlen + totlen; > + > + /* > + * Mark the time the last packet was seen for poll timeout processing. > + */ > + > + d->bd_rdStart = ticks; > } > > /* > > > > *** /sys/net/bpfdesc.h.orig Sat Oct 14 19:16:07 2000 > --- /sys/net/bpfdesc.h Sat Oct 14 19:21:54 2000 > *************** > *** 69,74 **** > --- 69,75 ---- > > struct bpf_if * bd_bif; /* interface descriptor */ > u_long bd_rtout; /* Read timeout in 'ticks' */ > + u_long bd_rdStart; /* when the read started */ > struct bpf_insn *bd_filter; /* filter code */ > u_long bd_rcount; /* number of packets received */ > u_long bd_dcount; /* number of packets dropped */ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 14: 5:36 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 CB0C637B66C for ; Mon, 16 Oct 2000 14:05:32 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.9.3/8.9.3) with SMTP id RAA31998; Mon, 16 Oct 2000 17:05:12 -0400 (EDT) (envelope-from arr@watson.org) Date: Mon, 16 Oct 2000 17:05:11 -0400 (EDT) From: "Andrew R. Reiter" To: Peter Van Epp Cc: freebsd-hackers@FreeBSD.ORG Subject: OOPS Re: bpf.c select fix for review In-Reply-To: <200010162026.NAA01828@fraser.sfu.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 woops.. I meant bd_rdstart. On Mon, 16 Oct 2000, Peter Van Epp wrote: > While working on the new argus version I discovered that there is a > bug in the /sys/net/bpf.c code if you are doing select with a timeout (which > tcpdump isn't). Basically if you set up tcpreplay on another machine and send > a less than full buffer (9 packets 2300 bytes in my case) to a FreeBSD 4.1 > RELEASE machine, argus won't see the packets. It turns out that because it > is using select (and not immediate mode) the partially full buffer won't get > passed up to libpcap. The OpenBSD folks have a partial fix (which only gets > the first packet up and leaves the other 8 dangling). I ported that to FreeBSD > and then made a fix which appears to work based on what their code looked to > be trying to do (as opposed to what it does which is incorrect). > Basically at receive packet time the tick counter is stored in a > variable in the capture structure. When the select/poll timeout occurs it > checks if the current tick time is > then the last received packet count + > the timeout value. If so it rotates the (partially full) packet buffer and > signals to wake up the process. While this appears to work (and match the > Solaris behavior on the same file) I figured I'd see if anyone sees a glaring > hole in the fix before submitting a bug report on it. > > Peter Van Epp / Operations and Technical Support > Simon Fraser University, Burnaby, B.C. Canada > > *** /sys/net/bpf.c.orig Sat Oct 14 19:00:59 2000 > --- /sys/net/bpf.c Mon Oct 16 09:30:24 2000 > *************** > *** 1054,1061 **** > if (events & (POLLIN | POLLRDNORM)) { > if (d->bd_hlen != 0 || (d->bd_immediate && d->bd_slen != 0)) > revents |= events & (POLLIN | POLLRDNORM); > ! else > ! selrecord(p, &d->bd_sel); > } > splx(s); > return (revents); > --- 1054,1076 ---- > if (events & (POLLIN | POLLRDNORM)) { > if (d->bd_hlen != 0 || (d->bd_immediate && d->bd_slen != 0)) > revents |= events & (POLLIN | POLLRDNORM); > ! else { > ! /* > ! * If there is a timeout and no data in the hold buffer > ! * see if there has been data in the capture buffer > ! * for more than a timeout interval. If so rotate the > ! * buffer to push the packets to the user. > ! */ > ! if ((d->bd_slen != 0) && (d->bd_hlen == 0)) { > ! if ((d->bd_rtout != -1) && > ! (d->bd_rdStart + d->bd_rtout) > ticks) { > ! ROTATE_BUFFERS(d); > ! revents |= events & (POLLIN | POLLRDNORM); > ! } > ! } else > ! selrecord(p, &d->bd_sel); > ! > ! } > } > splx(s); > return (revents); > *************** > *** 1219,1224 **** > --- 1234,1245 ---- > */ > (*cpfn)(pkt, (u_char *)hp + hdrlen, (hp->bh_caplen = totlen - hdrlen)); > d->bd_slen = curlen + totlen; > + > + /* > + * Mark the time the last packet was seen for poll timeout processing. > + */ > + > + d->bd_rdStart = ticks; > } > > /* > > > > *** /sys/net/bpfdesc.h.orig Sat Oct 14 19:16:07 2000 > --- /sys/net/bpfdesc.h Sat Oct 14 19:21:54 2000 > *************** > *** 69,74 **** > --- 69,75 ---- > > struct bpf_if * bd_bif; /* interface descriptor */ > u_long bd_rtout; /* Read timeout in 'ticks' */ > + u_long bd_rdStart; /* when the read started */ > struct bpf_insn *bd_filter; /* filter code */ > u_long bd_rcount; /* number of packets received */ > u_long bd_dcount; /* number of packets dropped */ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 15: 0:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7F03437B66D; Mon, 16 Oct 2000 15:00:18 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9GM0Ip22393; Mon, 16 Oct 2000 15:00:18 -0700 (PDT) Date: Mon, 16 Oct 2000 15:00:17 -0700 From: Alfred Perlstein To: hackers@freebsd.org Cc: bde@freebsd.org Subject: readv manpage != UIO_MAXIOV Message-ID: <20001016150017.T272@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Several months ago I was having trouble porting a program of mine to solaris, the problem was that I'd get EINVAL back from writev/readv if my iovec was larger than 16 entries long. I thought this was a pretty stupidly set low limit, however the solaris #define for it looked pretty official: sys/socket.h:#define MSG_MAXIOVLEN 16 sys/stream.h:#define DEF_IOV_MAX 16 anyhow, I just noticed that our manpages now proclaim a 16 entry limit, however our kernel code doesn't seemt to mind up to 1024 iovs. (sys/uio.h:#define UIO_MAXIOV 1024) So do we: a) change the kernel to match the docco and possibly breaks lotsa stuff? b) change the docco to note that although FreeBSD allows more than 16 iovecs, it's not recommeneded for portability reasons c) change readv/writev but provide compat syscalls. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 16: 9:34 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 C832537B503; Mon, 16 Oct 2000 16:09:28 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Oct 2000 00:09:27 +0100 (BST) Date: Tue, 17 Oct 2000 00:09:26 +0100 From: David Malone To: Alfred Perlstein Cc: hackers@freebsd.org, bde@freebsd.org Subject: Re: readv manpage != UIO_MAXIOV Message-ID: <20001017000926.A52976@walton.maths.tcd.ie> References: <20001016150017.T272@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001016150017.T272@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Oct 16, 2000 at 03:00:17PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 16, 2000 at 03:00:17PM -0700, Alfred Perlstein wrote: > a) change the kernel to match the docco and possibly breaks > lotsa stuff? > b) change the docco to note that although FreeBSD allows > more than 16 iovecs, it's not recommeneded for portability > reasons > c) change readv/writev but provide compat syscalls. Susv2 man pages say: iovcnt is valid if greater than 0 and less than or equal to {IOV_MAX}, defined in We don't seem to #define IOV_MAX, but we could and them update the man page to refer to it. It says IOV_MAX must be atleast _XOPEN_IOV_MAX which is 16. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 16:13:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C185737B677; Mon, 16 Oct 2000 16:13:33 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9GNDTr25092; Mon, 16 Oct 2000 16:13:29 -0700 (PDT) Date: Mon, 16 Oct 2000 16:13:29 -0700 From: Alfred Perlstein To: David Malone Cc: hackers@freebsd.org, bde@freebsd.org Subject: Re: readv manpage != UIO_MAXIOV Message-ID: <20001016161329.W272@fw.wintelcom.net> References: <20001016150017.T272@fw.wintelcom.net> <20001017000926.A52976@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001017000926.A52976@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Oct 17, 2000 at 12:09:26AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Malone [001016 16:09] wrote: > On Mon, Oct 16, 2000 at 03:00:17PM -0700, Alfred Perlstein wrote: > > > a) change the kernel to match the docco and possibly breaks > > lotsa stuff? > > b) change the docco to note that although FreeBSD allows > > more than 16 iovecs, it's not recommeneded for portability > > reasons > > c) change readv/writev but provide compat syscalls. > > Susv2 man pages say: > > iovcnt is valid if greater than 0 and less than or equal to > {IOV_MAX}, defined in > > We don't seem to #define IOV_MAX, but we could and them update the > man page to refer to it. It says IOV_MAX must be atleast _XOPEN_IOV_MAX > which is 16. So I guess we need a #define for IOV_MAX set to 1024? This would be ideal since it will give a reasonable #define for applications to use and we don't break our current interface. All that would be needed is the additional #define and a mention of it in the manpage. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 16:23:40 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 6B91037B503; Mon, 16 Oct 2000 16:23:36 -0700 (PDT) Received: from lanczos.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Oct 2000 00:23:35 +0100 (BST) Date: Tue, 17 Oct 2000 00:23:33 +0100 From: David Malone To: Alfred Perlstein Cc: hackers@freebsd.org, bde@freebsd.org Subject: Re: readv manpage != UIO_MAXIOV Message-ID: <20001017002333.A24520@lanczos.maths.tcd.ie> References: <20001016150017.T272@fw.wintelcom.net> <20001017000926.A52976@walton.maths.tcd.ie> <20001016161329.W272@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001016161329.W272@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Oct 16, 2000 at 04:13:29PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 16, 2000 at 04:13:29PM -0700, Alfred Perlstein wrote: > So I guess we need a #define for IOV_MAX set to 1024? This would > be ideal since it will give a reasonable #define for applications > to use and we don't break our current interface. > > All that would be needed is the additional #define and a mention of > it in the manpage. Sounds reasonable - I guess that the define would go in sys/syslimits.h, but I'm not sure how to link it to the kernel's value (should it be replaced with the Posix name?) I'm sure Bruce can recommend a reasonable way to do it. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 16:27:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 2B4B837B66C for ; Mon, 16 Oct 2000 16:27: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 13ktdr-0000Px-00; Sun, 15 Oct 2000 13:40:19 -0600 Message-ID: <39EA0823.D9D353D8@softweyr.com> Date: Sun, 15 Oct 2000 13:40:19 -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: Thierry Herbelot Cc: Gregory Sutter , hackers@FreeBSD.ORG Subject: Re: Routing issues References: <20001014233212.H3444@klapaucius.zer0.org> <39E95406.8F1C0717@cybercable.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thierry Herbelot wrote: > > Gregory Sutter wrote: > > > > I'm setting up a network that looks like this: > > > > --Internet----Router---Firewall > > | > > | /--- host > > Switch----NAT-----<----- host > > | \----- host > > | \----- etc... > > --------- > > | | > > email ns > > > > In other words, a fairly typical small network. I've got an 8-IP > > subnet; all hosts outside the NAT have real IPs: > > > > router: 1.2.3.193 > > firewall: 1.2.3.196 fxp0 > > 1.2.3.197 fxp1 > > nat: 1.2.3.198 > > email: 1.2.3.194 > > ns: 1.2.3.195 > > > > The problem I'm having is with my routing. Surprise. Here is > > the routing table for the firewall: > > > > default 1.2.3.193 fxp0 > > 1.2.3.193 link#1 fxp0 > > 1.2.3.192/29 link#2 fxp1 > > 1.2.3.196 lo0 > > 1.2.3.197 lo0 > > > > The gateway_enable (net.inet.ip.forwarding) is also enabled on > > the firewall. > > with a *routing* firewall, like the one you are using, you must have two > different IP subnets, one for each physical interface (or else, the > kernel will not know which interface to use to send a packet). You can handle it by using host routes to the interior computers, but that is messy. -- "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 Mon Oct 16 16:36:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from klapaucius.zer0.org (klapaucius.zer0.org [204.152.186.45]) by hub.freebsd.org (Postfix) with ESMTP id 5740237B66E for ; Mon, 16 Oct 2000 16:36:30 -0700 (PDT) Received: by klapaucius.zer0.org (Postfix, from userid 1001) id 59AD0239AB1; Mon, 16 Oct 2000 16:36:30 -0700 (PDT) Date: Mon, 16 Oct 2000 16:36:30 -0700 From: Gregory Sutter To: Wes Peters Cc: Thierry Herbelot , hackers@FreeBSD.ORG Subject: Re: Routing issues Message-ID: <20001016163630.B98214@klapaucius.zer0.org> References: <20001014233212.H3444@klapaucius.zer0.org> <39E95406.8F1C0717@cybercable.fr> <39EA0823.D9D353D8@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39EA0823.D9D353D8@softweyr.com>; from wes@softweyr.com on Sun, Oct 15, 2000 at 01:40:19PM -0600 Organization: Zer0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-10-15 13:40 -0600, Wes Peters wrote: > Thierry Herbelot wrote: > > Gregory Sutter wrote: > > > > > > I'm setting up a network that looks like this: > > > > > > --Internet----Router---Firewall > > > | > > > | /--- host > > > Switch----NAT-----<----- host > > > | \----- host > > > | \----- etc... > > > --------- > > > | | > > > email ns > > > > > > In other words, a fairly typical small network. I've got an 8-IP > > > subnet; all hosts outside the NAT have real IPs: > > > > > > router: 1.2.3.193 > > > firewall: 1.2.3.196 fxp0 > > > 1.2.3.197 fxp1 > > > nat: 1.2.3.198 > > > email: 1.2.3.194 > > > ns: 1.2.3.195 > > > > > > The problem I'm having is with my routing. Surprise. Here is > > > the routing table for the firewall: > > > > > > default 1.2.3.193 fxp0 > > > 1.2.3.193 link#1 fxp0 > > > 1.2.3.192/29 link#2 fxp1 > > > 1.2.3.196 lo0 > > > 1.2.3.197 lo0 > > > > > > The gateway_enable (net.inet.ip.forwarding) is also enabled on > > > the firewall. > > > > with a *routing* firewall, like the one you are using, you must have two > > different IP subnets, one for each physical interface (or else, the > > kernel will not know which interface to use to send a packet). > > You can handle it by using host routes to the interior computers, but that > is messy. The bridging was the key that I was missing. Turning it on instantly resulted in a working network with the configuration described above. The default route, since it's a host route anyway, is entered with interface fxp0, and the rest of the 1.2.3.192/29 network is routed with interface fxp1. Destination Gateway Flags Refs Use Netif Expire default 1.2.3.193 UGSc 1 163304 fxp0 127.0.0.1 127.0.0.1 UH 0 0 lo0 1.2.3.192/29 link#2 UCSc 3 0 fxp1 => 1.2.3.193 0:f:cf:7f:ff:f4 UHLW 1 32 fxp0 1032 1.2.3.196 0:df:f7:f6:1f:f6 UHLW 0 106 lo0 1.2.3.197 0:f:bf:f:df:f1 UHLS 0 2 lo0 net.inet.ip.forwarding: 1 net.link.ether.bridge_cfg: fxp0:1,fxp1:1, net.link.ether.bridge: 1 net.link.ether.bridge_ipfw: 1 Thanks to all who replied! Greg -- Gregory S. Sutter "How do I read this file?" mailto:gsutter@zer0.org "You uudecode it." http://www.zer0.org/~gsutter/ "I I I decode it?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 17:28:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from never.tellme.com (never.tellme.com [209.157.156.27]) by hub.freebsd.org (Postfix) with ESMTP id 054FF37B503 for ; Mon, 16 Oct 2000 17:28:38 -0700 (PDT) Received: by never.tellme.com (Postfix, from userid 501) id 9FBAB71658; Mon, 16 Oct 2000 17:28:32 -0700 (PDT) Date: Mon, 16 Oct 2000 17:28:32 -0700 From: Danny Howard To: hackers@freebsd.org Subject: mfsroot over nfs and optional install.cfg ?? Message-ID: <20001016172832.E97579@never.tellme.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Loop: djhoward@uiuc.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm working on doing a FreeBSD jumpstat process based on http://people.freebsd.org/~alfred/pxe/ My primary limitation is configurability - I need to be able to run sysinstall with a different install.cfg per install. So the first answer to that is "configure each client with a different PXE root and go from there." Then I get the irritation that I must diddle with an mfsroot image to change the install.cfg. I've been poring over what loader documentation I can find, but still haven't even figured out how the "let's go to mfsroot which will take us to sysinstall in the next stage" thing works ... there's nothing in mfsroot's /etc, for example ... From loader.rc: load -t mfs_root /mfsroot [...] set vfs.root.mountfrom="ufs:/dev/md0c" boot How is boot different from autoboot? Can I get around having to load the mfs_root image and just dump it in the pxe boot directory? I'm getting a hunch that maybe I can do an NFS partition and set vfs.root.mountfrom to use NFS ... Then, the other question is, how the heck does sysinstall get launched? If I can get at a script that launches sysinstall, I could set an install.cfg for sysinstall to run instead of having to point at differnt install.cfg's via dhcpd.conf ... Any help appreciated. Thanks, -danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 17:53:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 2363D37B66D; Mon, 16 Oct 2000 17:53:33 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id RAA09825; Mon, 16 Oct 2000 17:53:52 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp05.primenet.com, id smtpdAAA03aigt; Mon Oct 16 17:53:41 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA04059; Mon, 16 Oct 2000 17:53:16 -0700 (MST) From: Terry Lambert Message-Id: <200010170053.RAA04059@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: gcorcoran@lucent.com (Gary T. Corcoran) Date: Tue, 17 Oct 2000 00:53:15 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <39E7AB10.EADBB53B@lucent.com> from "Gary T. Corcoran" at Oct 13, 2000 08:38:40 PM X-Mailer: ELM [version 2.5 PL2] 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 > Back in July I was asking about the capability to set parameters (variables) > when loading my DSL driver module. There was a small flurry of activity > about some initial ideas on how to do it, but I never heard any more about > it. Did you (Mike, Warner, or anybody) have time to work on it? Did this > capability get put into release 4.1, by any chance? :) A common trick "in the old days" was to load a parameter module that the driver module depended up, and give it a hook that it could call to get data from the parameter module, by reference to a statis structure. You would send the data down to the parameter module before you load the driver module; thus: 1) Load paramter module 2) Open parameter module psuedo device 3) Ioctl parameters up/down via the pseudo device 4) Load the deriver module 5) Driver module attach routine call parameter_fetch() routine out of parameter module 6) Parameter module returns static parameter structure, by reference 7) Driver dereferences parameters out of static struct 8) Driver completes attach Really, it seems to me that if this driver looks like an ethernet interface, you should be able to set the parameters after the atttach, before bringing the interface up. Alternately, if the problem is lack of reference counting on FreeBSD's part, and you therefore can't do the job on the open, since you can't track closes aws they happen, only the last clse, there are a couple of approaches: A) Have one driver, but two devices; one for control, and one for data B) Have only one device, but inactivate it until a special ioctl() starting it up is issued; thus: 1) Open 2) Set parameters 3) ioctl(fd,LUCENT_START,...) 4) ... 5) ioctl(fd,LUCENT_STOP,...) 6) Set new parameters 7) ioctl(fd,LUCENT_START,...) 8) ... One of these aprroaches should be able to work for you; the parameter driver approach with a pseudo device will definitely work, but is much less elegant (parameters on an attach probably mean that you are doing something in an attach that really belongs elsewhere). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 17:58:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 012F437B66D for ; Mon, 16 Oct 2000 17:58:11 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id RAA11115; Mon, 16 Oct 2000 17:56:29 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpdAAA.gaqQv; Mon Oct 16 17:56:22 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA04303; Mon, 16 Oct 2000 17:57:58 -0700 (MST) From: Terry Lambert Message-Id: <200010170057.RAA04303@usr05.primenet.com> Subject: Re: ASUS CUBX Motherboard 3rd and 4th IDE channels To: patseal@hyperhost.net (Patrick Seal) Date: Tue, 17 Oct 2000 00:57:58 +0000 (GMT) Cc: dave@jetcafe.org (Dave Hayes), freebsd-hackers@FreeBSD.ORG In-Reply-To: <20001014231253.A58936@hyperhost.net> from "Patrick Seal" at Oct 14, 2000 11:12:53 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am attempting to install FreeBSD 4.1.1, off floppy, brand new CUBX > > motherboard with the 4 IDE channels. It's a GENERIC kernel, so I've done > > nothing to it yet. > > GENERIC: > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > > notice the lack of ata2 and ata3. > > I have no idea what irq to use though. Kind of begs the question: why is this stuff still statically allocated in "config" anyway, since it's PnP known to the system, and so could be configured dynamically. The only argument for this, I guess, is to allow you to leave the controller and driver out of a kernel entirely? It seems to me that the same effect could be had by ensuring that said drivers were in their own ELF sections, and that that space be reclaimed, should a device not be found. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 18: 4:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9480837B66E; Mon, 16 Oct 2000 18:04:12 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9H149T28639; Mon, 16 Oct 2000 18:04:09 -0700 (PDT) Date: Mon, 16 Oct 2000 18:04:09 -0700 From: Alfred Perlstein To: Terry Lambert Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) Message-ID: <20001016180409.C272@fw.wintelcom.net> References: <39E7AB10.EADBB53B@lucent.com> <200010170053.RAA04059@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010170053.RAA04059@usr05.primenet.com>; from tlambert@primenet.com on Tue, Oct 17, 2000 at 12:53:15AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Terry Lambert [001016 17:55] wrote: > > Alternately, if the problem is lack of reference counting on > FreeBSD's part, and you therefore can't do the job on the > open, since you can't track closes aws they happen, only the > last clse, there are a couple of approaches: FreeBSD has had that capability for over a year now. /* * Flags for d_flags. */ #define D_MEMDISK 0x10000 /* memory type disk */ #define D_NAGGED 0x20000 /* nagged about missing make_dev() */ #define D_CANFREE 0x40000 /* can free blocks */ #define D_TRACKCLOSE 0x80000 /* track all closes */ (from sys/conf.h) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 18:11:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 66B6837B503 for ; Mon, 16 Oct 2000 18:11:30 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id SAA00950; Mon, 16 Oct 2000 18:08:07 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpdAAAnEaGVb; Mon Oct 16 18:07:56 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA05324; Mon, 16 Oct 2000 18:11:14 -0700 (MST) From: Terry Lambert Message-Id: <200010170111.SAA05324@usr05.primenet.com> Subject: Re: Getting Linux NIS to work with FreeBSD NIS servers To: billf@chimesnet.com (Bill Fumerola) Date: Tue, 17 Oct 2000 01:11:14 +0000 (GMT) Cc: shocking@houston.rr.com (Stephen Hocking), hackers@FreeBSD.ORG In-Reply-To: <20001015232612.S37870@jade.chc-chimes.com> from "Bill Fumerola" at Oct 15, 2000 11:26:12 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The Linux box appears toknow about the users, it just cant get > > the passwords right - something tickles my mind about DES vs > > MD5, is this the case, and how do I convert my MD5 passwords > > if needed? > > Yes thats the case, no there is no "conversion" program. If there was > a conversion program it would mean there is a way to translate to plaintext > and that obviously isn't the case (modulo brute-force). You can also implmenet an update proxy, using an appropriate PAM mechanism, if you force it to go through PAM; I did a similar thing to provide a migration path for an email system from one provider to a new provider. The way it works is that you communicate your password to the proxy before the cryptographic has (of whatever flavor) is applied. If the credentials don't yet exist, in the new database, you apply the legacy hash, and check the value in the legacy database. If this matches, then you know the password is valid in the legacy database. You then apply the new cryptographic hash to the plaintext, resulting in a new password. You store the new value in your new database, and you're done. Cyrus has both IMAP4 and POP3 proxies that are easily adapted to this sort of scheme; for example, for migrating credentials from a UNIX-style password file into an OpenLDAP 2.0 (LDAPv3) directory... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 18:14:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by hub.freebsd.org (Postfix) with ESMTP id 6C61D37B679; Mon, 16 Oct 2000 18:14:14 -0700 (PDT) Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id VAA19871; Mon, 16 Oct 2000 21:14:14 -0400 (EDT) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id VAA19859; Mon, 16 Oct 2000 21:14:13 -0400 (EDT) Received: from lucent.com (positron.micro.lucent.com [192.19.56.129]) by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id VAA22823; Mon, 16 Oct 2000 21:14:12 -0400 (EDT) Message-ID: <39EBA79C.26BFFE3@lucent.com> Date: Mon, 16 Oct 2000 21:13:00 -0400 From: "Gary T. Corcoran" Organization: Lucent Microelectronics - Client Access Broadband Systems X-Mailer: Mozilla 4.73 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) References: <200010170053.RAA04059@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry, First, thanks for the reply. > > Back in July I was asking about the capability to set parameters (variables) > > when loading my DSL driver module. There was a small flurry of activity > > about some initial ideas on how to do it, but I never heard any more about > > it. Did you (Mike, Warner, or anybody) have time to work on it? Did this > > capability get put into release 4.1, by any chance? :) > > A common trick "in the old days" was to load a parameter module > that the driver module depended up, and give it a hook that it > could call to get data from the parameter module, by reference > to a statis structure. Hmmm... Quite a hack :), but yes it should work. If all else fails, I guess I could do this... > Really, it seems to me that if this driver looks like an > ethernet interface, you should be able to set the parameters > after the atttach, before bringing the interface up. ... > One of these aprroaches should be able to work for you; the parameter > driver approach with a pseudo device will definitely work, but is > much less elegant (parameters on an attach probably mean that you > are doing something in an attach that really belongs elsewhere). One of the problems with supporting DSL is that there are many "flavors" of protocol that different equipment providers use. But there are two main divisions, which unfortunately make for a Jekyl-and-Hyde personality. The DSL card must either appear as a LAN device (ethernet interface) or a WAN device (sync PPP device). Thus, at the moment of attach(), I need to know whether to do an ether_ifattach() or an sppp_attach(). That's the main reason I need module parameters. The other reason I _want_ module parameters is that Linux provides them, so the Linux flavor of my driver uses them, and it's easier to keep the drivers in sync with changes if they are written in a similar manner (since only the Linux driver is "officially" supported)... Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 18:19:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id DC84237B479; Mon, 16 Oct 2000 18:19:37 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id SAA04562; Mon, 16 Oct 2000 18:16:16 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpdAAAXTaaRi; Mon Oct 16 18:16:01 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA05533; Mon, 16 Oct 2000 18:19:16 -0700 (MST) From: Terry Lambert Message-Id: <200010170119.SAA05533@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 17 Oct 2000 01:19:16 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <20001016180409.C272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 16, 2000 06:04:09 PM X-Mailer: ELM [version 2.5 PL2] 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 > > Alternately, if the problem is lack of reference counting on > > FreeBSD's part, and you therefore can't do the job on the > > open, since you can't track closes aws they happen, only the > > last clse, there are a couple of approaches: > > FreeBSD has had that capability for over a year now. > > /* > * Flags for d_flags. > */ > #define D_TRACKCLOSE 0x80000 /* track all closes */ Under what circumstances is it permissable to _not_ set this bit? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 18:39: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3B17437B4B1; Mon, 16 Oct 2000 18:38:53 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9H1ckd29873; Mon, 16 Oct 2000 18:38:46 -0700 (PDT) Date: Mon, 16 Oct 2000 18:38:46 -0700 From: Alfred Perlstein To: Terry Lambert Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) Message-ID: <20001016183846.G272@fw.wintelcom.net> References: <20001016180409.C272@fw.wintelcom.net> <200010170119.SAA05533@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010170119.SAA05533@usr05.primenet.com>; from tlambert@primenet.com on Tue, Oct 17, 2000 at 01:19:16AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Terry Lambert [001016 18:19] wrote: > > > Alternately, if the problem is lack of reference counting on > > > FreeBSD's part, and you therefore can't do the job on the > > > open, since you can't track closes aws they happen, only the > > > last clse, there are a couple of approaches: > > > > FreeBSD has had that capability for over a year now. > > > > /* > > * Flags for d_flags. > > */ > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > Under what circumstances is it permissable to _not_ set this bit? When you want the old behavior. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 18:57:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 51CEE37B4CF; Mon, 16 Oct 2000 18:57:44 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id SAA00281; Mon, 16 Oct 2000 18:54:45 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAANHa4va; Mon Oct 16 18:54:34 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA06764; Mon, 16 Oct 2000 18:57:25 -0700 (MST) From: Terry Lambert Message-Id: <200010170157.SAA06764@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 17 Oct 2000 01:57:25 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <20001016183846.G272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 16, 2000 06:38:46 PM X-Mailer: ELM [version 2.5 PL2] 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 > > > > Alternately, if the problem is lack of reference counting on > > > > FreeBSD's part, and you therefore can't do the job on the > > > > open, since you can't track closes aws they happen, only the > > > > last clse, there are a couple of approaches: > > > > > > FreeBSD has had that capability for over a year now. > > > > > > /* > > > * Flags for d_flags. > > > */ > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > Under what circumstances is it permissable to _not_ set this bit? > > When you want the old behavior. Under what circumstances is it permissable to want the old behaviour? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 19:15:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id D0A0337B4C5 for ; Mon, 16 Oct 2000 19:15:35 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id 5D0D2DC74; Mon, 16 Oct 2000 22:08:57 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 47736DC73 for ; Mon, 16 Oct 2000 22:08:57 -0400 (EDT) Date: Mon, 16 Oct 2000 22:08:57 -0400 (EDT) From: David Miller To: freebsd-hackers@freebsd.org Subject: Swap numbers in systcl? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All:) I'm looking to write a self throttling program which will use all the resources on my system without driving it into oblivion. I can tell when the CPU is used up, or when load average goes too high, or when I'm using more of the network than I want. But I'm not sure what to check to see when I'm using enough virtual memory to start the system swapping. I can't just check to see if swap is used and or growing: it might be normal for another process, like named, to very slowly suck down more and more virtual memory. It's also not always given back as quickly as I'd need to start more processes. Suggestions? Pointers to available docs most welcome:) --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 19:41:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 05A4237B4D7; Mon, 16 Oct 2000 19:41:50 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9H2fmt02044; Mon, 16 Oct 2000 19:41:48 -0700 (PDT) Date: Mon, 16 Oct 2000 19:41:48 -0700 From: Alfred Perlstein To: Terry Lambert Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) Message-ID: <20001016194147.I272@fw.wintelcom.net> References: <20001016183846.G272@fw.wintelcom.net> <200010170157.SAA06764@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200010170157.SAA06764@usr05.primenet.com>; from tlambert@primenet.com on Tue, Oct 17, 2000 at 01:57:25AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Terry Lambert [001016 18:57] wrote: > > > > > Alternately, if the problem is lack of reference counting on > > > > > FreeBSD's part, and you therefore can't do the job on the > > > > > open, since you can't track closes aws they happen, only the > > > > > last clse, there are a couple of approaches: > > > > > > > > FreeBSD has had that capability for over a year now. > > > > > > > > /* > > > > * Flags for d_flags. > > > > */ > > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > > > Under what circumstances is it permissable to _not_ set this bit? > > > > When you want the old behavior. > > Under what circumstances is it permissable to want the old behaviour? Jeez Terry, I don't know, it's how it used to be so I assume it's for compatibility or for drivers that simply don't care. Am I missing something here? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 20:48:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id 78CFA37B4C5 for ; Mon, 16 Oct 2000 20:48:11 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e9H3lhG58203; Mon, 16 Oct 2000 20:47:44 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010170347.e9H3lhG58203@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Terry Lambert Cc: patseal@hyperhost.net (Patrick Seal), dave@jetcafe.org (Dave Hayes), freebsd-hackers@FreeBSD.ORG Subject: Re: ASUS CUBX Motherboard 3rd and 4th IDE channels In-Reply-To: <200010170057.RAA04303@usr05.primenet.com> Date: Mon, 16 Oct 2000 20:47:43 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > I am attempting to install FreeBSD 4.1.1, off floppy, brand new CUBX > > > motherboard with the 4 IDE channels. It's a GENERIC kernel, so I've done > > > nothing to it yet. > > > > GENERIC: > > device ata0 at isa? port IO_WD1 irq 14 > > device ata1 at isa? port IO_WD2 irq 15 > > > > notice the lack of ata2 and ata3. > > > > I have no idea what irq to use though. > > Kind of begs the question: why is this stuff still statically > allocated in "config" anyway, It isn't anymore. > since it's PnP known to the > system, and so could be configured dynamically. Yes, it is dynamic now. These were only ever used as fallback hints for non-PnP, non-PCI systems. > The only argument for this, I guess, is to allow you to > leave the controller and driver out of a kernel entirely? You can already do this - it would be trivially easy to wrap up the ide drivers into a kld file and have it loaded prior to boot time. > It seems to me that the same effect could be had by ensuring > that said drivers were in their own ELF sections, and that > that space be reclaimed, should a device not be found. This is one of the exact goals in -current - to be able to do this. We can already reclaim preload space, but nobody has connected it up yet. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 21:28:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 7B2A537B4D7; Mon, 16 Oct 2000 21:28:48 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id VAA19886; Mon, 16 Oct 2000 21:29:10 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpdAAA1KaWYM; Mon Oct 16 21:29:07 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id VAA06237; Mon, 16 Oct 2000 21:28:41 -0700 (MST) From: Terry Lambert Message-Id: <200010170428.VAA06237@usr01.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 17 Oct 2000 04:28:41 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <20001016194147.I272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 16, 2000 07:41:48 PM X-Mailer: ELM [version 2.5 PL2] 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 > > > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > Under what circumstances is it permissable to _not_ set this bit? > > > When you want the old behavior. > > Under what circumstances is it permissable to want the old behaviour? > > Jeez Terry, I don't know, it's how it used to be so I assume it's for > compatibility or for drivers that simply don't care. Am I missing > something here? I guess I'm asking "What moron would want to intentionally disable system resource tracking?". It's OK for the driver to not care, I guess, if it doesn't want to allow you to unload it, and other evil things. I can maybe buy the legacy argument, but, frankly, and I said this when Poul and David first asked that the capability to track closes first went in, unless everyone plays by the same rules, no one benefits. I guess it'd be nice if it weren't possible to have new drivers not support device close tracking, even if they did nothing about it, other than disallowing unloads when the open count was positive. In the specific context of this thread, if there was a control daemon, then the first open could always be the control daemon, and "attach" parameters could be passed by doing an open, noting it was the first open, and delaying the attach until the open count went from 1->2. For symmetry, this means that if I want to change the parameters after a reconfiguration, I need to know when the open count has gone from 2->1 (leaving only the control daemon). In order to differentiate the control daemon failing, from a normal non-control close, I would need to track and maintain a list of who the opener is, and remove from that list on close. As a general approach, this removes the need for a seperate control and usage device distinction, for those devices which have it now. It also means that I can distinguish a control open from another open, and that I can wedge an open in through an ioctl() to let me do things like have opens onto the ISO9660 and DVDROM views onto a DVD, without having to have seperate character and block devices, so tat, given a legal codec, I can play DVDs on FreeBSD, just like you can on MacOS X (which uses the caharcter device for one type of access, and the block device for the other: efectively another control device hack). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 21:58:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6098737B4C5; Mon, 16 Oct 2000 21:58:07 -0700 (PDT) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA09570; Tue, 17 Oct 2000 14:27:56 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200010170428.VAA06237@usr01.primenet.com> Date: Tue, 17 Oct 2000 14:27:56 +0930 (CST) From: "Daniel O'Connor" To: Terry Lambert Subject: Re: Module parameters? (WildWire DSL card driver) Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, (Gary T. Corcoran) , (Alfred Perlstein) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Oct-00 Terry Lambert wrote: > I guess I'm asking "What moron would want to intentionally disable > system resource tracking?". > > It's OK for the driver to not care, I guess, if it doesn't want to > allow you to unload it, and other evil things. > > > I can maybe buy the legacy argument, but, frankly, and I said > this when Poul and David first asked that the capability to > track closes first went in, unless everyone plays by the same > rules, no one benefits. If you don't need 'per-open' instance data then getting notified of the final close would be sufficient. Also, if you only allow one open you don't need to track each close. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 16 22:55:43 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 7195037B4E5 for ; Mon, 16 Oct 2000 22:53:34 -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 13lPjS-0000DN-00; Mon, 16 Oct 2000 23:56:14 -0600 Message-ID: <39EBE9FE.9CFB1373@softweyr.com> Date: Mon, 16 Oct 2000 23:56:14 -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: Laurence Berland Cc: hackers@freebsd.org Subject: Re: Starting to code References: <39EB3051.58E631CA@confusion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Laurence Berland wrote: > > What's a good place to start if you're a university student with limited > hardware who wants to jump in and get going with the FreeBSD code. > Right now I've got a PPro 200 with 32 MB of ram and lots of disk space > (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of > tossing Current on also, and maybe making the cvs repo a separate > partition so I can share it between current and stable. I love it when people call a PPro 200 with 32 MB "limited hardware". My first Free/NetBSD machine was a 386/40 with 8MB RAM and a 340 MB disk, and it was state of the art except for lack of a CD-ROM drive. > Mostly at this point I'm looking for a way to jump head first into the > code. Where's a good starting point? Look at the PR database, pick a problem, and start looking. Better yet, pick something that works but isn't documented and write a man page. In order to write a man page, you need to really understand the code, and will probably need to write one or several little test programs to exercise whatever you're documenting. -- "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 Mon Oct 16 23:12:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from happy.koganei.wide.ad.jp (koganei.wide.ad.jp [202.249.37.254]) by hub.freebsd.org (Postfix) with ESMTP id 073CC37B4C5 for ; Mon, 16 Oct 2000 23:12:22 -0700 (PDT) Received: from koganei.wide.ad.jp (tweedledee.koganei.wide.ad.jp [202.249.37.72]) by happy.koganei.wide.ad.jp (8.9.3/8.9.3) with ESMTP id PAA57853; Tue, 17 Oct 2000 15:12:08 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) Message-ID: <39EBED1D.D9A3FF97@koganei.wide.ad.jp> Date: Tue, 17 Oct 2000 15:09:33 +0900 From: Katsushi Kobayashi X-Mailer: Mozilla 4.75 (Macintosh; U; PPC) X-Accept-Language: ja,pdf MIME-Version: 1.0 To: "Andrew R. Reiter" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FireWire Device Driver References: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew, I am sorry I have lost private mail from you (I just found it in my Mbox), and I am admitted your comments in hackers by other people. I have once proposed my firewire code to merrge -current. And a lot of problems are pointed out. Almost problems will be resolved by code clarification work and it is not difficult. The most important issue pointed out is, the firewire code have to accords "newbus" archtecture and we have to define the firewire specific part. I have not updated the latest code published in ftp site I announced, because I have not a enough time right now to maintain it, and I am investigating bus architecture. If you would like to update my code, I am welcome to new cooperator. If you thought to write another implementation, I am OK. Thanks, "Andrew R. Reiter" wrote: > > hihi. > > I was reading back emails of -hackers from like july '99 and a guy from > Japan had been working on a very promising FireWire device driver ... > Anyway, the other night I had picked up a really awesome book that goes > into detail on FireWire and had basically decided to work on it myself > (until I realized someone had already started work on it!)... However, the > last email that was seemingly sent regarding this issue was one by jkh in > which he gives a major value for the device driver,... and asks when it > should be ready for use with -current. I have emailed the guy from japan > and have received no response... so I am wondering if anyone else knows > what's up with the firewire situation and whether I should go ahead and > pick up work on it? > > Andrew > > *-------------................................................. > | Andrew R. Reiter > | arr@fledge.watson.org > | "It requires a very unusual mind > | to undertake the analysis of the obvious" -- A.N. Whitehead > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 0:12:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id CF4AE37B4D7; Tue, 17 Oct 2000 00:12:08 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e9H7C3G58805; Tue, 17 Oct 2000 00:12:04 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010170712.e9H7C3G58805@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Terry Lambert Cc: bright@wintelcom.net (Alfred Perlstein), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) In-Reply-To: <200010170428.VAA06237@usr01.primenet.com> Date: Tue, 17 Oct 2000 00:12:03 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > > > > #define D_TRACKCLOSE 0x80000 /* track all closes */ > > > > > Under what circumstances is it permissable to _not_ set this bit? > > > > When you want the old behavior. > > > Under what circumstances is it permissable to want the old behaviour? > > > > Jeez Terry, I don't know, it's how it used to be so I assume it's for > > compatibility or for drivers that simply don't care. Am I missing > > something here? > > I guess I'm asking "What moron would want to intentionally disable > system resource tracking?". Who said anything about disabling system resource tracking? "track all closes" means to call the devsw d_close function for *each* close, not just for the "last close" as 99% of our drivers expect... If we suddenly caused d_close() to be called on every close() syscall, then existing drivers break because they are used to freeing everything and cleaning up when the close function is called. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 8:23:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from calcaphon.demon.co.uk (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id A230E37B4F9 for ; Tue, 17 Oct 2000 08:23:23 -0700 (PDT) Received: from localhost (gate [192.168.1.1]) by calcaphon.demon.co.uk (8.9.3/8.9.1) with ESMTP id QAA27497; Tue, 17 Oct 2000 16:23:15 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 17 Oct 2000 08:22:58 -0700 (PDT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Torbjorn Kristoffersen Cc: freebsd-hackers@FreeBSD.org Subject: Re: Programming a USB driver 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 Starting from a Linux driver is an option. Also, you want to subscribe to the usb-bsd mailing list at http://lists.inteltec.com/wws/info/usb-bsd There are some people there that are toying with the idea and someone might have started to work on a driver. Nick > I don't know if this is the right list to post to, so i'm sorry if it is. > > I'm borrowing a Digital Camera, it has only Windows drivers, and I heard > that it may be running in Linux using the CPiA drivers. > > These are my boot msgs: > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ugen0: STMicroelectronics USB Dual-mode Camera, rev 1.10/0.00, addr 2 > > It obviously found something there. Would it be hard to make a driver for > this camera? I would really appreciate some starting places and tips. > > TIA > > Torbjorn Kristoffersen > sgt@netcom.no > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 8:44: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from laguna.tiscalinet.it (laguna.tiscalinet.it [195.130.224.86]) by hub.freebsd.org (Postfix) with ESMTP id 67CE937B4CF for ; Tue, 17 Oct 2000 08:44:01 -0700 (PDT) Received: from kryo (62.11.120.52) by laguna.tiscalinet.it; 17 Oct 2000 17:43:11 +0200 Message-ID: <003101c03788$06865240$2f29a8c0@kryo> From: "Daniele Mancini" To: Subject: Date: Mon, 16 Oct 2000 17:44:33 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01C03798.BE89EA40" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0021_01C03798.BE89EA40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe freebsd-hackers ------=_NextPart_000_0021_01C03798.BE89EA40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
unsubscribe=20 freebsd-hackers
------=_NextPart_000_0021_01C03798.BE89EA40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 9:17:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4D60B37B4D7 for ; Tue, 17 Oct 2000 09:17:47 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA09887; Tue, 17 Oct 2000 18:17:46 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: hackers@freebsd.org Subject: I'm convinced 'gcc' is meant to be pronounced 'ARRRRGGGHHH!' From: Dag-Erling Smorgrav Date: 17 Oct 2000 18:17:45 +0200 Message-ID: Lines: 8 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will someone please inform the gcc developers of the last decade's advances in C standardization? Yes, Virginia, ISO C (it's not ISO C any more, and hasn't been since 1989) does support 'long long' and the 'll' format. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 9:36: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B727337B4E5 for ; Tue, 17 Oct 2000 09:36:02 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA17448; Tue, 17 Oct 2000 09:35:59 -0700 Date: Tue, 17 Oct 2000 09:32:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: I'm convinced 'gcc' is meant to be pronounced 'ARRRRGGGHHH!' 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 > Will someone please inform the gcc developers of the last decade's > advances in C standardization? Yes, Virginia, ISO C (it's not ISO C > any more, and hasn't been since 1989) does support 'long long' and the > 'll' format. > > DES > Eh? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 9:54:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3B9FA37B4D7 for ; Tue, 17 Oct 2000 09:54:52 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA10041; Tue, 17 Oct 2000 18:54:44 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: mjacob@feral.com Cc: hackers@FreeBSD.ORG Subject: Re: I'm convinced 'gcc' is meant to be pronounced 'ARRRRGGGHHH!' References: From: Dag-Erling Smorgrav Date: 17 Oct 2000 18:54:43 +0200 In-Reply-To: Matthew Jacob's message of "Tue, 17 Oct 2000 09:32:41 -0700 (PDT)" Message-ID: Lines: 17 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > Will someone please inform the gcc developers of the last decade's > > advances in C standardization? Yes, Virginia, ISO C (it's not ISO C > > any more, and hasn't been since 1989) does support 'long long' and the > > 'll' format. > Eh? 'gcc -pedantic' generates a warning for every use of the 'long long' type or the 'll' printf format modifier, incorrectly stating that they are not supported in ANSI C. C99 (which includes 'long long' and the 'll' format modifier) has been in the works for most of the previous decade, and was ratified (as ISO/IEC 9899:1999) on December 16th, 1999, but gcc still seems to live in 1989-land. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 10: 1:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 81A5637B4E5 for ; Tue, 17 Oct 2000 10:01:38 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA17543; Tue, 17 Oct 2000 10:01:34 -0700 Date: Tue, 17 Oct 2000 09:58:12 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: I'm convinced 'gcc' is meant to be pronounced 'ARRRRGGGHHH!' 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 > Matthew Jacob writes: > > > Will someone please inform the gcc developers of the last decade's > > > advances in C standardization? Yes, Virginia, ISO C (it's not ISO C > > > any more, and hasn't been since 1989) does support 'long long' and the > > > 'll' format. > > Eh? > > 'gcc -pedantic' generates a warning for every use of the 'long long' > type or the 'll' printf format modifier, incorrectly stating that they > are not supported in ANSI C. C99 (which includes 'long long' and the > 'll' format modifier) has been in the works for most of the previous > decade, and was ratified (as ISO/IEC 9899:1999) on December 16th, > 1999, but gcc still seems to live in 1989-land. Ah, yes- I see what you mean. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 12: 6:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 40DF937B4CF; Tue, 17 Oct 2000 12:06:14 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id MAA07087; Tue, 17 Oct 2000 12:03:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpdAAAaoaGzn; Tue Oct 17 12:02:55 2000 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA00326; Tue, 17 Oct 2000 12:05:43 -0700 (MST) From: Terry Lambert Message-Id: <200010171905.MAA00326@usr05.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: peter@netplex.com.au (Peter Wemm) Date: Tue, 17 Oct 2000 19:05:42 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), bright@wintelcom.net (Alfred Perlstein), gcorcoran@lucent.com (Gary T. Corcoran), freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-Reply-To: <200010170712.e9H7C3G58805@netplex.com.au> from "Peter Wemm" at Oct 17, 2000 12:12:03 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I guess I'm asking "What moron would want to intentionally disable > > system resource tracking?". > > Who said anything about disabling system resource tracking? "track all > closes" means to call the devsw d_close function for *each* close, not just > for the "last close" as 99% of our drivers expect... If we suddenly caused > d_close() to be called on every close() syscall, then existing drivers break > because they are used to freeing everything and cleaning up when the close > function is called. Who remembers the open that resulted in the close, if not the driver? Perhaps I'm merely complaining that there are not seperate "close" and "last_close" entry points, since exposing a "last_close" entry point, and then a generic "close" handler that calls "last_close" when the reference count goes from 1->0, which is ignored if the driver has a non-generic handler. Not much of a namespace exposure kludge. I guess I'm anout as annoyed as I was when supposed "bit rot" killed the ISODE and X.25 functioning, when certain kernel interfaces were redefined, without the person doing the redefintion taking care to maintain all caller instances, or when a similar thing ate LFS. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 17: 7:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D60037B4CF for ; Tue, 17 Oct 2000 17:07:15 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA17496 for ; Tue, 17 Oct 2000 20:07:14 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e9I07E092094; Tue, 17 Oct 2000 20:07:14 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 17 Oct 2000 20:07:14 -0400 (EDT) To: freebsd-hackers@freebsd.org Subject: dumb usb question X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14828.58690.249376.915698@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A friend of mine just bought a D-Link USB-S25 USB to Serial Port converter cable. Given that he cannot make it work under linux and that I've been trying to sell him on FreeBSD, I'd like to give it a whirl under FreeBSD. What is the appropriate driver? umodem looks like it just deals with generic serial devices and might do the job. Is that correct? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 20:27:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 2A0D337B4E5 for ; Tue, 17 Oct 2000 20:27:25 -0700 (PDT) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id UAA02101 for ; Tue, 17 Oct 2000 20:27:15 -0700 (PDT) Message-Id: <200010180327.UAA02101@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: freebsd-hackers@freebsd.org Subject: Adaptec 29160 problems (what you all want to hear eh?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Oct 2000 20:27:15 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to boot 4.1.1 GENERIC from floppy. The system installs cleanly, but come boot time all I get is something of the form FreeBSD F1: FreeBSD at which point the boot process hangs with a long beep and refuses to continue. The SCSI disk is hanging on an adaptec 29160. I have toggled a lot of options in the bios, no dice. Anyone have any clues? ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< He who has self-conceit in his head - Do not imagine that he will ever hear the truth. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 20:38: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hecky.it.northwestern.edu (hecky.acns.nwu.edu [129.105.16.51]) by hub.freebsd.org (Postfix) with ESMTP id ADD1D37B479 for ; Tue, 17 Oct 2000 20:38:04 -0700 (PDT) Received: (from mailnull@localhost) by hecky.it.northwestern.edu (8.8.7/8.8.7) id WAA00191; Tue, 17 Oct 2000 22:38:03 -0500 (CDT) Received: from confusion.net (dhcp089155.res-hall.nwu.edu [199.74.89.155]) by hecky.acns.nwu.edu via smap (V2.0) id xma000113; Tue, 17 Oct 00 22:37:49 -0500 Message-ID: <39ED1AE2.4914EE6C@confusion.net> Date: Tue, 17 Oct 2000 22:37:06 -0500 From: Laurence Berland X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wes Peters Cc: hackers@FreeBSD.ORG Subject: Re: Starting to code References: <39EB3051.58E631CA@confusion.net> <39EBE9FE.9CFB1373@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > Laurence Berland wrote: > > > > What's a good place to start if you're a university student with limited > > hardware who wants to jump in and get going with the FreeBSD code. > > Right now I've got a PPro 200 with 32 MB of ram and lots of disk space > > (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of > > tossing Current on also, and maybe making the cvs repo a separate > > partition so I can share it between current and stable. > > I love it when people call a PPro 200 with 32 MB "limited hardware". My > first Free/NetBSD machine was a 386/40 with 8MB RAM and a 340 MB disk, and > it was state of the art except for lack of a CD-ROM drive. > I thought it was more than fast enough, and for most things it is, but KDE manages to crawl nonetheless... -- Laurence Berland Intern, Flooz.com Northwestern '04 stuyman@confusion.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 17 20:41: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sun.tsu.ru (sun.lib.tsu.ru [212.192.96.5]) by hub.freebsd.org (Postfix) with ESMTP id 6A9F137B4D7 for ; Tue, 17 Oct 2000 20:40:45 -0700 (PDT) Received: from sun.tsu.ru (alex.lib.tsu.ru [212.192.96.7]) by sun.tsu.ru (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e9I3dX529734 for ; Wed, 18 Oct 2000 11:39:33 +0800 (TSD) Message-ID: <39ED2A01.DA62039C@sun.tsu.ru> Date: Wed, 18 Oct 2000 11:41:37 +0700 From: "Alexandr A. Gilyazov" X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: (no subject) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit 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 Wed Oct 18 6:42:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sneety.insync.net (sneety.insync.net [209.113.65.5]) by hub.freebsd.org (Postfix) with ESMTP id 5279F37B4D7 for ; Wed, 18 Oct 2000 06:42:25 -0700 (PDT) Received: from Matt (209-113-91-158.insync.net [209.113.91.158]) by sneety.insync.net (8.9.3/8.9.3) with SMTP id IAA17968 for ; Wed, 18 Oct 2000 08:42:15 -0500 (CDT) Reply-To: From: "Matt Bettinger" To: Subject: irq Date: Wed, 18 Oct 2000 08:40:22 -0500 Message-ID: <71F816A89AA9D3119F4C00D0B7094EFC1990B3@FIN_SYN> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-reply-to: <71F816A89AA9D3119F4C00D0B7094EFC1FF556@FIN_SYN> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello posted this on questions without a response so thought maybe someone here would help me out.. .... compiled a kernel on 4.1.1 STABLE and after exiting X I saw a message stating something about /kernel stray irq 7 should i post a dmesg or does anyone know why one might be getting a stray irq other than that things seem to be running fine with a stray irq or not. ;-> matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 18 6:46:22 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 0186537B4C5 for ; Wed, 18 Oct 2000 06:46:20 -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 <01JVHKQQOC72000RSQ@research.kpn.com> for freebsd-hackers@freebsd.org; Wed, 18 Oct 2000 15:46:16 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 18 Oct 2000 15:46:15 +0100 Content-return: allowed Date: Wed, 18 Oct 2000 15:46:14 +0100 From: "Koster, K.J." Subject: RE: irq To: "'mattb@finsyn.com'" Cc: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D794D@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="koi8-r" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > compiled a kernel on 4.1.1 STABLE and after exiting X I saw a message > stating something about /kernel stray irq 7 > http://www.FreeBSD.org/cgi/search.cgi?words=stray+irq+7&max=25&sort=score&in dex=recent&source=freebsd-questions 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 Wed Oct 18 8: 2:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sydney.worldwide.lemis.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 0FC0E37B479 for ; Wed, 18 Oct 2000 08:02:08 -0700 (PDT) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.0/8.9.3) id e9I3IjB01467; Tue, 17 Oct 2000 20:18:45 -0700 (PDT) (envelope-from grog) Date: Tue, 17 Oct 2000 20:18:45 -0700 From: Greg Lehey To: Frank Nobis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA ICRC WRITE ERROR Message-ID: <20001017201845.E1250@sydney.worldwide.lemis.com> References: <20001015135815.A5133@radio-do.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001015135815.A5133@radio-do.de>; from fn@radio-do.de on Sun, Oct 15, 2000 at 01:58:15PM +0200 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 Sunday, 15 October 2000 at 13:58:15 +0200, Frank Nobis wrote: > Hi, > > I have a IDE drive spitting out this messages: > > ad3: UDMA ICRC WRITE ERROR blk# 48562489 retrying > ad3: UDMA ICRC READ ERROR blk# 24576329 retrying > ad3: UDMA ICRC WRITE ERROR blk# 69108025 retrying > ad3: UDMA ICRC WRITE ERROR blk# 73728313 retrying Is this always the same drive? >> From the boot messages: > > atapci0: port 0xd800-0xd80f at device 4.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > ad2: 42934MB [87233/16/63] at ata1-master using UDMA33 > ad3: 42934MB [87233/16/63] at ata1-slave using UDMA33 > > Do I have to exchange the drive ? I think I should. You could try setting PIO mode first. > In the case of replacing is the best thing to do, that leads to the > question, how to replace this drive ? Shut the machine down. Replace drive, making sure the jumpers are set correctly. Reboot. > It is a part of a vinum raid5 volume. Is detach and attach the > right way ? No. Take a look at the description on http://www.vinumvm.org/. Sorry, I don't know the exact URL, and I'm currently off the net. One thing that occurs to me is that I suspect you're using ad[123] as your RAID-5 drive. That's seriously sub-optimal for performance, but it also means that ad2 and ad3 will frequently have transfers outstanding at the same time. That might be the real issue; you might find that if you swap ad1 and ad3 (which you can do without losing data on the volume), you will continue having problems with the new ad3. > PS. If someone want more information about the System (PRESMPNG) > dual PIII on an ASUS P2B-DS, just let me know. I want avoid spamming > the list with big config and dmesg output Right, we don't need them. Read http://www.vinumvm.org/how-to-debug.html for details regarding Vinum 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 Oct 18 11:12:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BD7D37B4CF for ; Wed, 18 Oct 2000 11:12:08 -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 13lxrx-0000Pr-00; Wed, 18 Oct 2000 12:23:17 -0600 Message-ID: <39EDEA94.BAE8F635@softweyr.com> Date: Wed, 18 Oct 2000 12:23:16 -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: Laurence Berland Cc: hackers@FreeBSD.ORG Subject: Re: Starting to code References: <39EB3051.58E631CA@confusion.net> <39EBE9FE.9CFB1373@softweyr.com> <39ED1AE2.4914EE6C@confusion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Laurence Berland wrote: > > Wes Peters wrote: > > > > Laurence Berland wrote: > > > > > > What's a good place to start if you're a university student with limited > > > hardware who wants to jump in and get going with the FreeBSD code. > > > Right now I've got a PPro 200 with 32 MB of ram and lots of disk space > > > (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of > > > tossing Current on also, and maybe making the cvs repo a separate > > > partition so I can share it between current and stable. > > > > I love it when people call a PPro 200 with 32 MB "limited hardware". My > > first Free/NetBSD machine was a 386/40 with 8MB RAM and a 340 MB disk, and > > it was state of the art except for lack of a CD-ROM drive. > > > I thought it was more than fast enough, and for most things it is, but > KDE manages to crawl nonetheless... WindowMaker. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 18 12:47:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.getrelevant.com (mail.getrelevant.com [63.211.149.12]) by hub.freebsd.org (Postfix) with ESMTP id 2422537B4C5 for ; Wed, 18 Oct 2000 12:47:09 -0700 (PDT) Received: from khmere.com ([63.211.149.44]) by mail.getrelevant.com (Lotus Domino Release 5.0.4a) with ESMTP id 2000101812450540:253604 ; Wed, 18 Oct 2000 12:45:05 -0700 Message-ID: <39EDFE2E.583B5631@khmere.com> Date: Wed, 18 Oct 2000 12:46:54 -0700 From: Nathan Boeger Organization: Getrelevant X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: struct proc and struct vmspace help, please X-MIMETrack: Itemize by SMTP Server on notes/GetRelevant(Release 5.0.4a |July 24, 2000) at 10/18/2000 12:45:05 PM, Serialize by Router on notes/GetRelevant(Release 5.0.4a |July 24, 2000) at 10/18/2000 12:45:07 PM, Serialize complete at 10/18/2000 12:45:07 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the need for the /proc//status file inside the linprocfs. So I have added it to the linprocfs_misc.c Well the only problem I am having is the VmRSS: field. How do I get the rssize from inside the kernel for a process ? from userland I can do: struct kinfo_proc->kp_eproc . e_vm . vm_rssize ( like top ) but from inside the struct proc what do I use ? I have tried the struct vmspace but it give me strange numbers (well, maybe not strange but are they in pages ? bytes ? and why are they 0 sometimes ? ) I have looked and explored all over the headers, but I am stuck. Any help will be greatly appreciated !!! thank you nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 18 15: 0:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 20E1037B4C5 for ; Wed, 18 Oct 2000 15:00:57 -0700 (PDT) Received: from hermes.tue.nl (hermes.tue.nl [131.155.2.46]) by kweetal.tue.nl (8.11.0/8.11.0) with ESMTP id e9IM0tt15865 for ; Thu, 19 Oct 2000 00:00:55 +0200 (MDT) Received: from deathstar (n127.dial.tue.nl [131.155.209.126]) by hermes.tue.nl (Postfix) with ESMTP id BC9362E805 for ; Thu, 19 Oct 2000 00:00:48 +0200 (CEST) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Thu, 19 Oct 2000 00:02:25 +0100 Subject: ncurses+ full screen apps X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20001018220048.BC9362E805@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to capture alt-x keys on the console? Prefer a ncurses solution, but a FreeBSD specific, or even a RAW freebsd console one will do. 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 Oct 18 17: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 2E74537B4F9; Wed, 18 Oct 2000 17:24:04 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA27764; Wed, 18 Oct 2000 17:23:41 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Wed, 18 Oct 2000 17:23:40 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: Rusty Nejdl Cc: freebsd-questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Where to post... In-Reply-To: <39EDF951.4C95C455@ringofsaturn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Oct 2000, Rusty Nejdl wrote: > Believe it or not, I just wanted to know where I should post a > compliment on the > new FreeBSD 4.1 OS that you guys have released. I have successfully > gotten it working on my laptop with the NIC, graphics, and sound, so I > wanted to say thanks for a few new features that made my life much > easier. > > Rusty Nejdl > CCNA > Training Engineer > Verio, INC. -questions is as good a place as any. :) I'm cc'ing -hackers to reach a slightly wider audience of developers. Believe me when I say, _kind_ words are always appreciated, and I for one thank you for taking to time to offer yours. It helps make the work we do worthwhile. 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 Wed Oct 18 17:32: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [206.50.17.51]) by hub.freebsd.org (Postfix) with ESMTP id 06EBB37B4D7; Wed, 18 Oct 2000 17:31:55 -0700 (PDT) Received: (from rnejdl@localhost) by tethys.ringofsaturn.com (8.9.3/8.9.3) id TAA85400; Wed, 18 Oct 2000 19:32:21 -0500 (CDT) (envelope-from rnejdl) Date: Wed, 18 Oct 2000 19:32:21 -0500 From: Rusty Nejdl To: Doug Barton Cc: freebsd-questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Where to post... Message-ID: <20001018193221.A85334@tethys.ringofsaturn.com> References: <39EDF951.4C95C455@ringofsaturn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from DougB@gorean.org on Wed, Oct 18, 2000 at 05:23:40PM -0700 X-State: Dazed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug, Thanks for the quick reply. I have been a FreeBSD user since 3.2 first came out as I stumbled into your OS. I just wanted to take the time to say that the most recent changes that you all have put forth in the 4.0 series is a great step. I used the new PCM audio driver and it works extremely well and that was something that I never expected to see anytime soon. As well, the further compatibilities with the Linux software are well done and have done great things to help me make FreeBSD a workstation and not just a server or hobby machine at home. I have always been impressed with the stability in the OS and am using it for 2 web servers and a shell server at this time. Seeing where you are taking the desktop side of things, keep up the great work! Thanks! Rusty Nejdl CCNA Training Engineer Verio, INC. Doug Barton(DougB) wrote: > On Wed, 18 Oct 2000, Rusty Nejdl wrote: > > > Believe it or not, I just wanted to know where I should post a > > compliment on the > > new FreeBSD 4.1 OS that you guys have released. I have successfully > > gotten it working on my laptop with the NIC, graphics, and sound, so I > > wanted to say thanks for a few new features that made my life much > > easier. > > > > Rusty Nejdl > > CCNA > > Training Engineer > > Verio, INC. > > -questions is as good a place as any. :) I'm cc'ing -hackers to > reach a slightly wider audience of developers. Believe me when I say, > _kind_ words are always appreciated, and I for one thank you for taking to > time to offer yours. It helps make the work we do worthwhile. > > Doug > -- > "The dead cannot be seduced." > - Kai, "Lexx" > > Do YOU Yahoo!? > -- Rusty Nejdl "If it ain't broke, it doesn't have enough features yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 18 21:40:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 533CA37B4D7 for ; Wed, 18 Oct 2000 21:40:03 -0700 (PDT) Received: (qmail 24810 invoked by uid 1003); 19 Oct 2000 04:39:59 -0000 Date: Thu, 19 Oct 2000 06:39:59 +0200 From: Neil Blakey-Milner To: Wes Peters Cc: Laurence Berland , chat@FreeBSD.org Subject: Re: Starting to code Message-ID: <20001019063959.A19817@mithrandr.moria.org> References: <39EB3051.58E631CA@confusion.net> <39EBE9FE.9CFB1373@softweyr.com> <39ED1AE2.4914EE6C@confusion.net> <39EDEA94.BAE8F635@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39EDEA94.BAE8F635@softweyr.com>; from wes@softweyr.com on Wed, Oct 18, 2000 at 12:23:16PM -0600 X-Operating-System: FreeBSD 4.1-STABLE i386 X-URL: http://mithrandr.moria.org/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -hackers => -chat ] On Wed 2000-10-18 (12:23), Wes Peters wrote: > Laurence Berland wrote: > > > > Wes Peters wrote: > > > > > > Laurence Berland wrote: > > > > > > > > What's a good place to start if you're a university student with limited > > > > hardware who wants to jump in and get going with the FreeBSD code. > > > > Right now I've got a PPro 200 with 32 MB of ram and lots of disk space > > > > (~50 gigs). 10 gigs or so is used by FreeBSD-Stable. I'm thinking of > > > > tossing Current on also, and maybe making the cvs repo a separate > > > > partition so I can share it between current and stable. > > > > > > I love it when people call a PPro 200 with 32 MB "limited hardware". My > > > first Free/NetBSD machine was a 386/40 with 8MB RAM and a 340 MB disk, and > > > it was state of the art except for lack of a CD-ROM drive. > > > > > I thought it was more than fast enough, and for most things it is, but > > KDE manages to crawl nonetheless... > > WindowMaker. ;^) I've recently discovered pwm, and I must say I can't imagine going back to anything else. The key feature is windows that share a common frame. I have three Eterms connected to the same frame with tabs at the top of the frame to choose the Eterm I want to see. This works even better for Netscape - I have about 12 or so Netscapes connected in one frame, and I just use meta-W to close ones I'm finished with and meta-N to add a new Netscape to the frame. No new windows rushing to the top in some weird place - all Netscape windows share the same mostly-maximised frame. I can shortcut with ctrl-shift-x where x is a single numeral to the number of the tab, or use ctrl-shift-N and ctrl-shift-P to move to the next and previous tabs respectively. Netscape even seems to crash less, but that's probably just wishful thinking. It _is_ chewing a whole 1.7 megs SIZE and 1.3 RES, though. Bad bad pwm, with quite a few frames and a number of tabs in each, all over about 6 workspaces. And I haven't manage to crash it yet, so I'm quite happy. Check out ports/x11-wm/pwm sometime. See the home page http://www.students.tut.fi/~tuomov/pwm/ for what passes for "themes". (: End of advertisement. Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 18 22: 9:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.iitb.ac.in (mailhost.iitb.ac.in [203.197.74.142]) by hub.freebsd.org (Postfix) with SMTP id 1F69137B4FE for ; Wed, 18 Oct 2000 22:09:53 -0700 (PDT) Received: (qmail 3036 invoked from network); 19 Oct 2000 05:13:15 -0000 Received: from akash.it.iitb.ernet.in.116.16.144.in-addr.arpa (HELO akash.it.iitb.ernet.in) (144.16.116.2) by mailhost.iitb.ac.in with SMTP; 19 Oct 2000 05:13:15 -0000 Received: from slashetc.net (mercury.it.iitb.ernet.in [144.16.116.231]) by akash.it.iitb.ernet.in (8.9.3/8.8.8) with ESMTP id KAA31038 for ; Thu, 19 Oct 2000 10:38:28 +0530 Received: by slashetc.net (Postfix, from userid 1000) id 843C8369; Thu, 19 Oct 2000 10:28:13 +0530 (IST) Date: Thu, 19 Oct 2000 10:28:13 +0530 From: Chirag Kantharia To: freebsd-hackers@freebsd.org Subject: hdd problem Message-ID: <20001019102813.A4498@slashetc.net> Reply-To: Chirag Kantharia Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Loop: chyrag@slashetc.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've been using 4.1.1-RELEASE on my machine. Lately, my hard disk starts whirring noisily for a period ranging from 3 to 15 secs during which the hdd led shines very bright and the machine *almost* stops responding. A few secs later, everything comes back to normal and the following appears in /var/log/messages: Oct 19 10:23:10 mercury /kernel: ad0: WRITE command timeout - resetting Oct 19 10:23:10 mercury /kernel: ata0: resetting devices .. device dissapeared! 1 ata0-master: timeout waiting to give command=c6 s=80 e=00 Oct 19 10:23:10 mercury /kernel: done Any ideas, as to what is happening? Or just a coupla loose connections? chyrag. -- Chirag Kantharia http://slashetc.net/chyrag/ GCS/IT/B/E/MU/TW d->! s-:- a-->? C++++@ UBLS++++ P++++(+++) L++ E-(---) W++ N--@ w--- M- PS+ PE++ PGP>++ R* b++ DI+ D+ G+++ e++ h>++ r-- y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 0: 8:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (d4044.dtk.chello.nl [213.46.4.44]) by hub.freebsd.org (Postfix) with ESMTP id 7E0C537B4C5 for ; Thu, 19 Oct 2000 00:08:37 -0700 (PDT) Received: from aurum (aurum.springer.cx [10.0.0.52]) by minerva.springer.cx (8.9.3/8.9.3) with SMTP id IAA06063; Thu, 19 Oct 2000 08:17:30 -0400 Message-ID: <002f01c02208$776ba540$3400000a@springer.cx> From: "Rink Springer" To: "Chirag Kantharia" , References: <20001019102813.A4498@slashetc.net> Subject: Re: hdd problem Date: Tue, 19 Sep 2000 09:08:51 +0200 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 ----- Original Message ----- From: "Chirag Kantharia" To: Sent: Thursday, October 19, 2000 6:58 AM Subject: hdd problem Hi! Sounds to me like your harddisk is broken or faulty... I've had the same problem with a 1.6GB harddisk of mine. When you put a lot of strain on it, it would suddenly disappear (even the BIOS wouldn't find it). After 15 minutes or so, it'd come back... this might also be caused by heat, though. --Rink > > Hello! > > I've been using 4.1.1-RELEASE on my machine. Lately, my hard disk starts > whirring noisily for a period ranging from 3 to 15 secs during which the > hdd led shines very bright and the machine *almost* stops responding. A > few secs later, everything comes back to normal and the following > appears in /var/log/messages: > > Oct 19 10:23:10 mercury /kernel: ad0: WRITE command timeout - resetting > Oct 19 10:23:10 mercury /kernel: ata0: resetting devices .. device dissapeared! 1 ata0-master: timeout waiting to give command=c6 s=80 e=00 > Oct 19 10:23:10 mercury /kernel: done > > Any ideas, as to what is happening? Or just a coupla loose connections? > > chyrag. > -- > Chirag Kantharia http://slashetc.net/chyrag/ > GCS/IT/B/E/MU/TW d->! s-:- a-->? C++++@ UBLS++++ P++++(+++) L++ E-(---) > W++ N--@ w--- M- PS+ PE++ PGP>++ R* b++ DI+ D+ G+++ e++ h>++ r-- y > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 0:16:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.iitb.ac.in (mailhost.iitb.ac.in [203.197.74.142]) by hub.freebsd.org (Postfix) with SMTP id 7B85037B479 for ; Thu, 19 Oct 2000 00:16:14 -0700 (PDT) Received: (qmail 9044 invoked from network); 19 Oct 2000 07:19:42 -0000 Received: from akash.it.iitb.ernet.in.116.16.144.in-addr.arpa (HELO akash.it.iitb.ernet.in) (144.16.116.2) by mailhost.iitb.ac.in with SMTP; 19 Oct 2000 07:19:42 -0000 Received: from slashetc.net (mercury.it.iitb.ernet.in [144.16.116.231]) by akash.it.iitb.ernet.in (8.9.3/8.8.8) with ESMTP id MAA00443; Thu, 19 Oct 2000 12:44:51 +0530 Received: by slashetc.net (Postfix, from userid 1000) id 37D19372; Thu, 19 Oct 2000 12:34:32 +0530 (IST) Date: Thu, 19 Oct 2000 12:34:32 +0530 From: Chirag Kantharia To: Rink Springer Cc: freebsd-hackers@freebsd.org Subject: Re: hdd problem Message-ID: <20001019123432.B7146@slashetc.net> Reply-To: Chirag Kantharia References: <20001019102813.A4498@slashetc.net> <002f01c02208$776ba540$3400000a@springer.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002f01c02208$776ba540$3400000a@springer.cx>; from rink@springer.cx on Tue, Sep 19, 2000 at 09:08:51AM +0200 X-Loop: chyrag@slashetc.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 19, 2000 at 09:08:51AM +0200, Rink Springer wrote: | Sounds to me like your harddisk is broken or faulty... I've had the same | problem with a 1.6GB harddisk of mine. When you put a lot of strain on it, | it would suddenly disappear (even the BIOS wouldn't find it). After 15 | minutes or so, it'd come back... this might also be caused by heat, though. Hi! Thanx for the ideas. Heat doesn't seem to the problem here. The other suggestion might hold. I'll check it. Thanx again. chyrag. -- Chirag Kantharia http://slashetc.net/chyrag/ GCS/IT/B/E/MU/TW d->! s-:- a-->? C++++@ UBLS++++ P++++(+++) L++ E-(---) W++ N--@ w--- M- PS+ PE++ PGP>++ R* b++ DI+ D+ G+++ e++ h>++ r-- y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 0:59:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 4C4A237B4C5 for ; Thu, 19 Oct 2000 00:59:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id AAA88957; Thu, 19 Oct 2000 00:57:13 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Date: Thu, 19 Oct 2000 00:57:13 -0700 (PDT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Andrew Gallatin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dumb usb question In-Reply-To: <14828.58690.249376.915698@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We do not have support for that serial device yet. And it is not straightforward to write support for it. Nick On Tue, 17 Oct 2000, Andrew Gallatin wrote: > > A friend of mine just bought a D-Link USB-S25 USB to Serial Port > converter cable. Given that he cannot make it work under linux and > that I've been trying to sell him on FreeBSD, I'd like to give it a > whirl under FreeBSD. > > What is the appropriate driver? umodem looks like it just deals with > generic serial devices and might do the job. Is that correct? > > Thanks, > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 5:30:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id 5FBB437B667 for ; Thu, 19 Oct 2000 05:30:48 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 19 Oct 2000 12:30:48 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D2608@erlangen01.atrada.de> From: Alexander Maret To: "'freebsd-hackers@freebsd.org'" Subject: How to sense DCD on serial port? Date: Thu, 19 Oct 2000 14:30:37 +0200 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 Hello, I just assembled a mini IR receiver for the serial Port. This device shows the IR-code by pulling DCD up or down. As there is no software for FreeBSD supporting IR I would like to have a try and code it myself. Unfortunately those Pulses sent by the IR device sometimes only last a few milliseconds. Now my question: How can I sense the state of the DCD line that quick? I can meassure the overal time with gettimeofday() but how can I sense DCD? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 6:30:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 10EEA37B479 for ; Thu, 19 Oct 2000 06:30:40 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 3FDC5A856; Fri, 20 Oct 2000 00:30:21 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 3C8DB545D; Thu, 19 Oct 2000 23:30:21 +1000 (EST) Date: Thu, 19 Oct 2000 23:30:21 +1000 (EST) From: andrew@ugh.net.au To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: How to sense DCD on serial port? In-Reply-To: <58A002A02C5ED311812E0050044517F00D2608@erlangen01.atrada.de> Message-ID: X-WonK: *wibble* 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, 19 Oct 2000, Alexander Maret wrote: > How can I sense the state of the DCD line that quick? I I'm not sure how quick it is but have you tried ioctl with an argument of TIOCMGET? See tty(4) for more details. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 7: 2:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A7E737B4C5 for ; Thu, 19 Oct 2000 07:02:09 -0700 (PDT) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id 8FC661746C; Thu, 19 Oct 2000 16:01:57 +0200 (MET DST) Received: (from fn@localhost) by trinity.radio-do.de (8.11.0/8.9.3) id e9JE1vw06264; Thu, 19 Oct 2000 16:01:57 +0200 (CEST) (envelope-from fn@gatekeeper.radio-do.de) Date: Thu, 19 Oct 2000 16:01:57 +0200 From: Frank Nobis To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UDMA ICRC WRITE ERROR Message-ID: <20001019160156.A6224@radio-do.de> References: <20001015135815.A5133@radio-do.de> <20001017201845.E1250@sydney.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001017201845.E1250@sydney.worldwide.lemis.com>; from grog@lemis.com on Tue, Oct 17, 2000 at 08:18:45PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 17, 2000 at 08:18:45PM -0700, Greg Lehey wrote: > On Sunday, 15 October 2000 at 13:58:15 +0200, Frank Nobis wrote: > > Hi, > > > > I have a IDE drive spitting out this messages: > > > > ad3: UDMA ICRC WRITE ERROR blk# 48562489 retrying > > ad3: UDMA ICRC READ ERROR blk# 24576329 retrying > > ad3: UDMA ICRC WRITE ERROR blk# 69108025 retrying > > ad3: UDMA ICRC WRITE ERROR blk# 73728313 retrying It seems the problem is solved for now. I replaced the cables with real UDMA66 parts (the ones with 80 wires) even if the ata controller is only UDMA33. Currently the drives are running without spitting out any more errors. Now the drives really operate at the physical maximum transfer rates up to 16 MB/s measured with iostat. Regards, Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 9:17:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id 81E3937B4E5 for ; Thu, 19 Oct 2000 09:17:21 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 19 Oct 2000 16:17:21 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D260A@erlangen01.atrada.de> From: Alexander Maret To: "'andrew@ugh.net.au '" Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: How to sense DCD on serial port? Date: Thu, 19 Oct 2000 18:17:07 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >-----Original Message----- >From: andrew@ugh.net.au >To: Alexander Maret >Cc: 'freebsd-hackers@freebsd.org' >Sent: 19.10.00 15:30 >Subject: Re: How to sense DCD on serial port? > > > >> How can I sense the state of the DCD line that quick? I > >I'm not sure how quick it is but have you tried ioctl with an argument >of >TIOCMGET? See tty(4) for more details. Thanks for your answer. I meanwhile tried TIOCMGET and I can sense the state of dcd. Unfortunately I can't continously check DCD because this takes ernormous cpu time. Is there a possibility to get a signal,intr or whatever, whenever the state of DCD changes? If not, what could you think of I have to do to implement such a feature? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 9:42:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 5EDDC37B479 for ; Thu, 19 Oct 2000 09:42:52 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id JAA08348; Thu, 19 Oct 2000 09:41:11 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdAAAWiaGgq; Thu Oct 19 09:41:01 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id JAA11007; Thu, 19 Oct 2000 09:42:38 -0700 (MST) From: Terry Lambert Message-Id: <200010191642.JAA11007@usr02.primenet.com> Subject: Re: dumb usb question To: n_hibma@qubesoft.com Date: Thu, 19 Oct 2000 16:42:37 +0000 (GMT) Cc: gallatin@cs.duke.edu (Andrew Gallatin), freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Nick Hibma" at Oct 19, 2000 12:57:13 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We do not have support for that serial device yet. And it is not > straightforward to write support for it. Doug Ambrisko has support for a number of devices that aren't supported in the current FreeBSD code. You may want to contact him: ambrisko@whistle.com Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 10:21:31 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 5628337B4CF for ; Thu, 19 Oct 2000 10:21:29 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e9JHLE524515; Thu, 19 Oct 2000 10:21:18 -0700 (PDT) Date: Thu, 19 Oct 2000 10:21:14 -0700 (PDT) From: Doug White To: Danny Howard Cc: hackers@FreeBSD.ORG Subject: Re: mfsroot over nfs and optional install.cfg ?? In-Reply-To: <20001016172832.E97579@never.tellme.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Oct 2000, Danny Howard wrote: > I'm working on doing a FreeBSD jumpstat process based on > http://people.freebsd.org/~alfred/pxe/ If you're at BSDCon please to my talk on it tomorrow. :-) > My primary limitation is configurability - I need to be able to run sysinstall > with a different install.cfg per install. So the first answer to that is > "configure each client with a different PXE root and go from there." I'm curious what differences you need. If it's radical or can't be handled in post-install then you would be better off writing your own installer. > Then I get the irritation that I must diddle with an mfsroot image to change > the install.cfg. I've been poring over what loader documentation I can find, > but still haven't even figured out how the "let's go to mfsroot which will > take us to sysinstall in the next stage" thing works ... there's nothing in > mfsroot's /etc, for example ... It isn't needed for the most part -- sysinstall runs as init in the install environment so there's no /etc/rc* to run. > >From loader.rc: > load -t mfs_root /mfsroot > [...] > set vfs.root.mountfrom="ufs:/dev/md0c" > boot > > How is boot different from autoboot? Autoboot is a variable; 'boot' does a countdown from 'autoboot' seconds. > Can I get around having to load the mfs_root image and just dump it in > the pxe boot directory? I'm getting a hunch that maybe I can do an > NFS partition and set vfs.root.mountfrom to use NFS ... You're shooting for an NFS-mounted root I bet, and I believe we have it going on the lab machines here at the con. I'll have to pick them apart and see what they do. > Then, the other question is, how the heck does sysinstall get launched? If I > can get at a script that launches sysinstall, I could set an install.cfg for > sysinstall to run instead of having to point at differnt install.cfg's via > dhcpd.conf ... You're in the 'hack sysinstall' arena. You can recompile it to use a different path for the install.cfg. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 13: 8:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 7A16937B479; Thu, 19 Oct 2000 13:08:16 -0700 (PDT) Received: from tellurian.com (unverified [208.59.162.242]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Thu, 19 Oct 2000 16:08:04 -0400 Message-ID: <39EF5505.7B7C2BFD@tellurian.com> Date: Thu, 19 Oct 2000 16:09:41 -0400 From: Marko Ruban X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,uk MIME-Version: 1.0 To: FreeBSD questions , freebsd-hackers@freebsd.org Subject: Routing issue with cable modem Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess no one knew the answer to my original question about getting RCN cable modem (with analog upstream line dialup) to work. So here's a somewhat simplified question. I narrowed the problem down to routing. Cable modem does dial out when I try to ping something on it's subnet (10.17.56.###), however it does not respond to any broadcast ARP queries about location of DNS server. Goal -- to add cable modem as the default gateway to internet. Symptom -- "add net default: gateway 10.17.56.XXX: Network is unreachable" Problem -- I think modem gateway cannot be added because it's on a different subnet then my NICs. Attempted -- aliasing ed0 to modem subnet.... all 10.17.56 IPs seem to be occupied. Any ideas would be greatly appreciated. It's been 2 weeks now that I'm stuck to using windows box :( Marko P.S. If someone on the freebsd-hackers mailing list knows the answer, please reply to my address because I'm not subscribed to freebsd-hackers (yet). P.S.S. On a side note: it would be very interesting to know how MSWin98 does it's network setup, that it has no trouble using the modem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 13:29:55 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 4CF7937B4D7 for ; Thu, 19 Oct 2000 13:29:51 -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 OAA25843 for ; Thu, 19 Oct 2000 14:29:49 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id OAA25357; Thu, 19 Oct 2000 14:29:49 -0600 (MDT) (envelope-from nate) Date: Thu, 19 Oct 2000 14:29:49 -0600 (MDT) Message-Id: <200010192029.OAA25357@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hackers@FreeBSD.org Subject: IPFW bug/incoming TCP connections being let in. 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 I had blocked incoming TCP connections coming into my network using IPFW, and I noticed that my brother was able to establish a Napster connection, even though I had blocked it earlier. I thought, no worries, I'll just block it at the port level. I read a couple of articles, and noted that connections from 8888 to the server should be blocked. Easy enough, I'll just block my clients from establishing connections to port 8888. Unfortunately, that doesn't work. Looking at tcpdump output, the 'server' appears to initiates a TCP connection from 8888 -> some random port. My firewall rules do *NOT* allow incoming TCP connections to be made to internal machines, since they only allow 'setup' packets to go out. So, how can Napster work? What happened to the 3-way handshake? I could see an issue if the OS's were hacked to get around this and not require a 3-way handshake, but the client in this case in a Win98 box. I'm *really* confused, and more than a little concerned, since it appears that somehow Napster is getting around the 3-way handshake. Does Napster create 'raw' sockets that emulate TCP traffic? In an attempt to attempt to debug what was going on, I stuck the following rules in place; 00016 allow log tcp from ${client} to any out xmit ep0 setup 00017 allow log tcp from any to ${client} in recv ep0 setup 00018 allow log tcp from ${client} to any out xmit ep0 established 00019 allow log tcp from any to ${client} in recv ep0 established 00020 allow log tcp from ${client} to any out xmit ep0 00021 allow log tcp from any to ${client} in recv ep0 Then, I started up Napster and logged what showed up. It was suprising (to me at least). One would think that rules 16 or 17 *must* be hit first, because the connection has to be initially established. However, it doesn't work that way. ipfw: 18 Accept TCP CLIENT-IP:1897 NAPSTER:8888 out via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 ipfw: 18 Accept TCP CLIENT-IP:1897 NAPSTER:8888 out via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 ipfw: 18 Accept TCP CLIENT-IP:1897 NAPSTER:8888 out via ep0 ipfw: 18 Accept TCP CLIENT-IP:1897 NAPSTER:8888 out via ep0 ipfw: 19 Accept TCP NAPSTER:8888 CLIENT-IP:1897 in via ep0 .... No 'setup' packets are sent at all. Confused and concerned.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 14: 0:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by hub.freebsd.org (Postfix) with ESMTP id CAF0537B4CF for ; Thu, 19 Oct 2000 14:00:50 -0700 (PDT) Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id RAA02361 for ; Thu, 19 Oct 2000 17:00:45 -0400 (EDT) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id RAA02350; Thu, 19 Oct 2000 17:00:44 -0400 (EDT) Received: from lucent.com (positron.micro.lucent.com [192.19.56.129]) by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id RAA23605; Thu, 19 Oct 2000 17:00:43 -0400 (EDT) Message-ID: <39EF60AE.B9498195@lucent.com> Date: Thu, 19 Oct 2000 16:59:26 -0400 From: "Gary T. Corcoran" Organization: Lucent Microelectronics - Client Access Broadband Systems X-Mailer: Mozilla 4.73 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Module parameters? (WildWire DSL card driver) References: <200010170053.RAA04059@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > Back in July I was asking about the capability to set parameters (variables) > > when loading my DSL driver module. There was a small flurry of activity > > about some initial ideas on how to do it, but I never heard any more about > > it. Did you (Mike, Warner, or anybody) have time to work on it? Did this > > capability get put into release 4.1, by any chance? :) > > A common trick "in the old days" was to load a parameter module > that the driver module depended up, and give it a hook that it > could call to get data from the parameter module, by reference > to a statis structure. > > You would send the data down to the parameter module before you > load the driver module; thus: > > 1) Load paramter module > 2) Open parameter module psuedo device > 3) Ioctl parameters up/down via the pseudo device > 4) Load the deriver module > 5) Driver module attach routine call parameter_fetch() > routine out of parameter module > 6) Parameter module returns static parameter structure, > by reference > 7) Driver dereferences parameters out of static struct > 8) Driver completes attach I'm implementing this suggested method, but I have one problem. I don't know what "device" to access to allow me to do ioctl's to it. That is, I've created a parameter module (which loads and is accessible by my driver) - but I don't think that (alone) has created a "device", has it? If so, what is it named? Realize that at step 3, my real device doesn't exist yet, so I can't reference that... Do I need to somehow "create" a (pseudo-)device in my parameter module - and if so how do I do that? Thanks, Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 14:14:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from css-1.cs.iastate.edu (css-1.cs.iastate.edu [129.186.3.24]) by hub.freebsd.org (Postfix) with ESMTP id 98D0C37B4D7 for ; Thu, 19 Oct 2000 14:14:19 -0700 (PDT) Received: from popeye.cs.iastate.edu (ghelmer@popeye.cs.iastate.edu [129.186.3.4]) by css-1.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id QAA02265; Thu, 19 Oct 2000 16:14:19 -0500 (CDT) Received: from localhost (ghelmer@localhost) by popeye.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id QAA27221; Thu, 19 Oct 2000 16:14:15 -0500 (CDT) X-Authentication-Warning: popeye.cs.iastate.edu: ghelmer owned process doing -bs Date: Thu, 19 Oct 2000 16:14:14 -0500 (CDT) From: Guy Helmer To: Nate Williams Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW bug/incoming TCP connections being let in. In-Reply-To: <200010192029.OAA25357@nomad.yogotech.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, 19 Oct 2000, Nate Williams wrote: > I had blocked incoming TCP connections coming into my network using > IPFW, and I noticed that my brother was able to establish a Napster > connection, even though I had blocked it earlier. > > I thought, no worries, I'll just block it at the port level. > > I read a couple of articles, and noted that connections from 8888 to the > server should be blocked. > > Easy enough, I'll just block my clients from establishing connections to > port 8888. > > Unfortunately, that doesn't work. Looking at tcpdump output, the > 'server' appears to initiates a TCP connection from 8888 -> some random > port. My firewall rules do *NOT* allow incoming TCP connections to be > made to internal machines, since they only allow 'setup' packets to go > out. > > So, how can Napster work? What happened to the 3-way handshake? I > could see an issue if the OS's were hacked to get around this and not > require a 3-way handshake, but the client in this case in a Win98 box. The remote napster client sends a message through the central Napster server, which relays the message to your Napster client to tell your machine to make a connection to the remote machine. This is so that, as long as one of the two Napster clients are not behind a firewall, the two clients can communicate directly. The client behind the firewall makes the connection to the client that isn't behind a firewall, since most firewalls are configured to allow internal machines to make connections to any outside machine. The regular 3-way handshake is occurring. It's just not initiated by the machine you would expect. You'd have to block outgoing SYNs to any outside host at port 8888 (but anyone who knows anything about ports could change their port number and get around your block). Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 14:24:13 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 6963437B4E5 for ; Thu, 19 Oct 2000 14:24:10 -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 PAA26756; Thu, 19 Oct 2000 15:24:03 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id PAA25574; Thu, 19 Oct 2000 15:24:03 -0600 (MDT) (envelope-from nate) Date: Thu, 19 Oct 2000 15:24:03 -0600 (MDT) Message-Id: <200010192124.PAA25574@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Guy Helmer Cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW bug/incoming TCP connections being let in. In-Reply-To: References: <200010192029.OAA25357@nomad.yogotech.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 > > I had blocked incoming TCP connections coming into my network using > > IPFW, and I noticed that my brother was able to establish a Napster > > connection, even though I had blocked it earlier. > > > > I thought, no worries, I'll just block it at the port level. > > > > I read a couple of articles, and noted that connections from 8888 to the > > server should be blocked. > > > > Easy enough, I'll just block my clients from establishing connections to > > port 8888. > > > > Unfortunately, that doesn't work. Looking at tcpdump output, the > > 'server' appears to initiates a TCP connection from 8888 -> some random > > port. My firewall rules do *NOT* allow incoming TCP connections to be > > made to internal machines, since they only allow 'setup' packets to go > > out. > > > > So, how can Napster work? What happened to the 3-way handshake? I > > could see an issue if the OS's were hacked to get around this and not > > require a 3-way handshake, but the client in this case in a Win98 box. > > The remote napster client sends a message through the central Napster > server, which relays the message to your Napster client to tell your > machine to make a connection to the remote machine. This much I undertand. However, I'm not making any downloads, so my client isn't (yet) connecting to another client. I'm trying to block connections to the server. How is the client connecting to the server? I don't see *any* TCP setup packets being sent out by my client, so how is the client communicating with the server via TCP? (I *AM* seeing TCP packets being sent out, but they are being sent as 'established' connections, before a setup packet is being sent.) > The regular 3-way handshake is occurring. It's just not initiated by the > machine you would expect. The only way my client can work is if it initiates the connection, but I don't see it initiating a connection to port 8888. So, how then is the Napster server at port 8888 communicating with my client? > You'd have to block outgoing SYNs to any > outside host at port 8888 (but anyone who knows anything about ports could > change their port number and get around your block). That was what I did, but the rule is never being hit. However, there appears to be a connecting from my client to port 8888 on the server. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 14:33: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id D8A3437B4FE for ; Thu, 19 Oct 2000 14:32:59 -0700 (PDT) Received: from krasnegar.demon.co.uk ([194.222.168.155] helo=farie) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 13mNJ3-000HS4-0B for freebsd-hackers@freebsd.org; Thu, 19 Oct 2000 21:32:58 +0000 Received: from steve by farie with local (Exim 3.12 #1) id 13mNIV-0000R6-00 (Debian); Thu, 19 Oct 2000 22:32:23 +0100 Date: Thu, 19 Oct 2000 22:32:23 +0100 From: Steve Dobson To: freebsd-hackers@freebsd.org Subject: Problems with pthread Message-ID: <20001019223223.A1105@krasnegar.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="yEPQxsgoJgBvi8ip" User-Agent: Mutt/1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --yEPQxsgoJgBvi8ip Content-Type: text/plain; charset=us-ascii Hi First please CC to me as I am not on the hackers mail list. I am trying to get the ORBacus working for FreeBSD. I know you already have a port of ORBacus, but that is version 3, and their latest release is version 4. In order to get ORBacus working to it I first need to get their JTC library working (JTC is a thin wrapper to pthread). Now that the user threads have re-written I was hoping to get the JTC library to compile and work under the 4.1 kernel. I have managed to get it to compile, but it core dumps very early in the start up code of my application. I have written a little simple program (attached with its Makefile) that also exhibits the same problem. When I run the program I see the following error reported from gdb: (gdb) run Starting program: nod Program received signal SIGSEGV, Segmentation fault. 0x280747b8 in pth_cancel_point () from /usr/local/lib/libpthread.so.13 (gdb) Can anyone offer any advice. Steve -- Steve Dobson steve.dobson@krasnegar.demon.co.uk People don't usually make the same mistake twice -- they make it three times, four time, five times... --yEPQxsgoJgBvi8ip Content-Type: text/x-c++src Content-Disposition: attachment; filename="nod.FSO8wN.cpp" #include #include int main(int argc, char **argv) { pthread_mutex_t lock; cerr << "About to initialise the lock" << endl; if (pthread_mutex_init(&lock, 0)) { cerr << "Failed to init the lock" << cout; return 1; } cerr << "About to grab the lock" << endl; if (pthread_mutex_lock(&lock)) { cerr << "Failed to grab the lock" << cout; return 1; } cerr << "About to release the lock" << endl; if (pthread_mutex_unlock(&lock)) { cerr << "Failed to release the lock" << cout; return 1; } cerr << "All done" << endl; } --yEPQxsgoJgBvi8ip Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="Makefile.FuKxyt" SRC.cpp = nod.cpp CPPFLAGS = -I/usr/local/include -D_THREAD_SAFE CXXFLAGS = -g LDFLAGS = -L/usr/local/lib -pthread -g LDLIBS = -lpthread OBJS = ${SRC.cpp:%.cpp=%.o} nod: ${OBJS} ${CXX} ${LDFLAGS} -o nod ${OBJS} ${LDLIBS} clean: rm -f nod ${OBJS} --yEPQxsgoJgBvi8ip-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 15: 7: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id CDD0E37B4C5 for ; Thu, 19 Oct 2000 15:07:05 -0700 (PDT) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G2P004726AOQ1@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Thu, 19 Oct 2000 16:56:49 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id QAA62444; Thu, 19 Oct 2000 16:57:07 -0500 (CDT envelope-from chris) Date: Thu, 19 Oct 2000 16:57:06 -0500 From: Chris Costello Subject: Re: Problems with pthread In-reply-to: <20001019223223.A1105@krasnegar.demon.co.uk> To: Steve Dobson Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20001019165705.C55936@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <20001019223223.A1105@krasnegar.demon.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, October 19, 2000, Steve Dobson wrote: > I have written a little simple program (attached with its Makefile) that also > exhibits the same problem. When I run the program I see the following > error reported from gdb: > (gdb) run > Starting program: nod > > Program received signal SIGSEGV, Segmentation fault. > 0x280747b8 in pth_cancel_point () from /usr/local/lib/libpthread.so.13 > (gdb) This is GNU Pth, not FreeBSD pthreads. Use the ``-pthread'' cc(1) switch to link to the FreeBSD threads library. -- |Chris Costello |Design simplicity: It was developed on a shoe-string budget. `------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 15:49:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtppop3pub.verizon.net (smtppop3pub.gte.net [206.46.170.22]) by hub.freebsd.org (Postfix) with ESMTP id 2C90137B479 for ; Thu, 19 Oct 2000 15:49:08 -0700 (PDT) Received: from sbiswas ([206.86.227.28]) by smtppop3pub.verizon.net with SMTP for ; id RAA38770958 Thu, 19 Oct 2000 17:45:01 -0500 (CDT) Message-ID: <002201c03a1f$a99cda00$0a01640a@sbiswas> Reply-To: "Soumen Biswas" From: "Soumen Biswas" To: References: <20001019223223.A1105@krasnegar.demon.co.uk> <20001019165705.C55936@holly.calldei.com> Subject: Troube with remote kernel debugging using --- gdb ptrace( PT_GETDBREGS ) Date: Thu, 19 Oct 2000 15:55:19 -0700 Organization: Netscaler Inc. 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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am haveing a slight problem with remote kernel debugging using gdb. ( host & target both fbsd 4.1.1 + gdb that came along - 4.18 ) I am able to attach and an debug the target But I keep getting the following warning : ptrace( PT_GETDBREGS ) failed: no such process Otherwise things seem to be working. Soumen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 18:57:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 1B1E237B4D7; Thu, 19 Oct 2000 18:57:13 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 594B22878E; Fri, 20 Oct 2000 08:57:00 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 1AFFF2878D; Fri, 20 Oct 2000 08:57:00 +0700 (ALMST) Date: Fri, 20 Oct 2000 08:56:59 +0700 (ALMST) From: Boris Popov To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: smbfs-1.3.0 released Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, At first, I'm want to say 'thank you' for everybody who provided me with feedback on my work. So, here is a records from the HISTORY file for last two releases: 20.10.2000 1.3.0 - Network IO engine significantly reworked. Now it uses kernel threads to implement 'smbiod' process which handles network traffic for each VC. Previous model were incapable to serve large number of mount points and didn't work well with intensive IO operations performed on a different files on the same mount point. Special care was taken on better usage of MP systems. Unfortunately, kernel threads aren't supported by FreeBSD 3.X and for now it is excluded from the list of supported systems. - Reduce overhead caused by using single hash table for each mount point. 26.09.2000 1.2.8 (never released) - More SMP related bugs are fixed. - Make smbfs compatible with the Linux emulator. - smbfs now known to work with IBM LanManager (special thanks to Eugen Averin) - Fix problem with files bigger than 2GB (reported by Lee McKenna) - Please note that smbfs may not work properly with FreeBSD 3.X. New version can be downloaded from: ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 19 20:18:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id C8F6037B4CF for ; Thu, 19 Oct 2000 20:18:39 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id CA6D5A854; Fri, 20 Oct 2000 14:18:38 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id C6F43545D; Fri, 20 Oct 2000 13:18:38 +1000 (EST) Date: Fri, 20 Oct 2000 13:18:38 +1000 (EST) From: andrew@ugh.net.au To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: How to sense DCD on serial port? In-Reply-To: <58A002A02C5ED311812E0050044517F00D260A@erlangen01.atrada.de> Message-ID: X-WonK: *wibble* 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, 19 Oct 2000, Alexander Maret wrote: > DCD because this takes ernormous cpu time. Is there a possibility > to get a signal,intr or whatever, whenever the state of DCD changes? Umm....I'm not sure but wouldn't you get SIGHUP if DCD was dropped? It would look like the "dialed in user" had closed the connection. Not to sure though. I don't think you get anything when it goes high again although a blocked open will return so you might be able to hack up something there...but there must be a better way :-) > If not, what could you think of I have to do to implement such > a feature? You could look at the source for various serial port related stuff such as cu and tip. You may even get some hints from looking at getty etc that handles serial logins. Perhaps the sio source might help as well. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 1: 6: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 32C0137B4D7 for ; Fri, 20 Oct 2000 01:06:04 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id BAA11073; Fri, 20 Oct 2000 01:05:30 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp05.primenet.com, id smtpdAAAHraWbU; Thu Oct 19 22:31:26 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id WAA10151; Thu, 19 Oct 2000 22:30:58 -0700 (MST) From: Terry Lambert Message-Id: <200010200530.WAA10151@usr09.primenet.com> Subject: Re: Module parameters? (WildWire DSL card driver) To: gcorcoran@lucent.com (Gary T. Corcoran) Date: Fri, 20 Oct 2000 05:30:58 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), freebsd-hackers@FreeBSD.ORG In-Reply-To: <39EF60AE.B9498195@lucent.com> from "Gary T. Corcoran" at Oct 19, 2000 04:59:26 PM X-Mailer: ELM [version 2.5 PL2] 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 > > You would send the data down to the parameter module before you > > load the driver module; thus: > > > > 1) Load paramter module > > 2) Open parameter module psuedo device > > 3) Ioctl parameters up/down via the pseudo device > > 4) Load the deriver module > > 5) Driver module attach routine call parameter_fetch() > > routine out of parameter module > > 6) Parameter module returns static parameter structure, > > by reference > > 7) Driver dereferences parameters out of static struct > > 8) Driver completes attach > > I'm implementing this suggested method, but I have one problem. I don't > know what "device" to access to allow me to do ioctl's to it. > That is, I've created a parameter module (which loads and is accessible > by my driver) - but I don't think that (alone) has created a "device", > has it? If so, what is it named? Realize that at step 3, my real > device doesn't exist yet, so I can't reference that... > Do I need to somehow "create" a (pseudo-)device in my parameter module > - and if so how do I do that? Yes, you need to have a pseudo device. There are examples in the modules stuff, in particular, the "bpf" code. But it basically just means a device with an attach routine that does nothing, and with an open routine that returns an fd handle that points to the global data structure that you put your parameters in, a close routine, and an ioctl() routine. Everything else can be ENOTIMP (well, you might want a detach routine, and any other load/unload houskeeping, but you get the idea). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 3:29: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bratislava.telecom.sk (bratislava.telecom.sk [195.146.128.61]) by hub.freebsd.org (Postfix) with ESMTP id 30F0D37B479 for ; Fri, 20 Oct 2000 03:29:01 -0700 (PDT) Received: from sdxnet.com (prem182-ba-ad3.telecom.sk [212.5.221.182]) by bratislava.telecom.sk (8.9.3/8.9.3) with ESMTP id MAA27041 for ; Fri, 20 Oct 2000 12:31:55 +0200 (MET DST) Received: (from tomas@localhost) by sdxnet.com (8.9.3/8.9.3) id MAA39266 for freebsd-hackers@freebsd.org; Fri, 20 Oct 2000 12:23:45 GMT From: Tomas Hruz Organization: Solidnet Ltd. To: freebsd-hackers@FreeBSD.ORG Subject: burncd utility for atapi burners Date: Fri, 20 Oct 2000 11:27:09 +0000 X-Mailer: KMail [version 1.0.21] Content-Type: Multipart/Mixed; boundary="Boundary-=_yzAZOHsNGHcxSfUBSnsNWfUJeLgt" MIME-Version: 1.0 Message-Id: <00102012234401.39055@srv.ba.sdxnet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Boundary-=_yzAZOHsNGHcxSfUBSnsNWfUJeLgt Content-Type: text/plain Content-Transfer-Encoding: 8bit I have corrected a problem with msinfo command in burncd. The major problem was that the method used was not robust enough (I am using Misumi CR 4801 atapi burner). In the response to burncd -f /dev/acd1c msinfo the first LBA of the last track on the media was always 0 (incorrect in the case of more sessions) and the next writeable address was correct. I have adopted a method from kernel (from cd9660 file system) to obtain more robust solution which I hope will cover wider selection of drives (because on all drives you can mount cd9660). Here is the change in diff -u form: ------------------------------------------------------------- --- burncd.c 2000/08/17 12:45:14 1.1.1.1 +++ burncd.c 2000/10/03 11:33:09 1.2 @@ -28,6 +28,11 @@ * $FreeBSD: src/usr.sbin/burncd/burncd.c,v 1.10 2000/03/03 23:17:27 sos Exp $ */ +/*- + * t.h. changes copyright (c) 2000 Tomas Hruz + * All rights reserved. + */ + #include #include #include @@ -40,10 +45,13 @@ #include #include +#include + #define BLOCKS 16 static int fd, saved_block_size; void cleanup(int); +int iso_get_ssector_user(int); int main(int argc, char **argv) @@ -109,15 +117,16 @@ break; } if (!strcmp(argv[arg], "msinfo")) { - struct ioc_read_toc_single_entry entry; + /*t.h.*//* struct ioc_read_toc_single_entry entry; bzero(&entry, sizeof(struct ioc_read_toc_single_entry)); entry.address_format = CD_LBA_FORMAT; - if (ioctl(fd, CDIOREADTOCENTRY, &entry) < 0) - err(EX_IOERR, "ioctl(CDIOREADTOCENTRY)"); + if (ioctl(fd, CDIOREADTOCENTRY, &entry) < 0) { + err(EX_IOERR, "ioctl(CDIOREADTOCENTRY)"); + } */ if (ioctl(fd, CDRIOCNEXTWRITEABLEADDR, &addr) < 0) err(EX_IOERR, "ioctl(CDRIOCNEXTWRITEABLEADDR)"); - fprintf(stderr, "%d, %d\n", entry.entry.addr.lba, addr); + fprintf(stdout, "%d,%d\n", iso_get_ssector_user(fd), addr); break; } if (!strcmp(argv[arg], "blank")) { @@ -229,4 +238,38 @@ { if (ioctl(fd, CDRIOCSETBLOCKSIZE, &saved_block_size) < 0) err(EX_IOERR, "ioctl(CDRIOCSETBLOCKSIZE)"); +} + +/* t.h. + * Try to find the start of the last data track on this CD-ROM. This + * is used to mount the last session of a multi-session CD. Bail out + * and return 0 if we fail, this is always a safe bet. Procedure from + * kernel /usr/src/sys/isofs/cd9660/cd9660_vfsops.c(iso_get_ssector). + * Changed for use outside of the kernel. + */ +int iso_get_ssector_user(fd) + int fd; +{ + struct ioc_toc_header h; + struct ioc_read_toc_single_entry t; + int i; + + + if (ioctl(fd, CDIOREADTOCHEADER, (caddr_t)&h) != 0) + return 0; + + for (i = h.ending_track; i >= 0; i--) { + t.address_format = CD_LBA_FORMAT; + t.track = i; + if (ioctl(fd, CDIOREADTOCENTRY, (caddr_t)&t) != 0) + return 0; + if ((t.entry.control & 4) != 0) + /* found a data track */ + break; + } + + if (i < 0) + return 0; + + return ntohl(t.entry.addr.lba); } ------------------------------------------------------------------- Moreover there was a minor problem that the output was to stderr and had the format %d,%d and therefore it was harder to use it directly in mkisofs as .... -C `burncd -f /dev/acd1c msinfo`. I changed this to stdout and format %d,%d. I would like to communicate the proposed changes to the author but I did not find his address. Could somebody provide his email to me? Yours tomas hruz --Boundary-=_yzAZOHsNGHcxSfUBSnsNWfUJeLgt Content-Type: text/english; name="burncd.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="burncd.c" LyotCiAqIENvcHlyaWdodCAoYykgMjAwMCBT+HJlbiBTY2htaWR0CiAqIEFsbCByaWdodHMgcmVz ZXJ2ZWQuCiAqCiAqIFJlZGlzdHJpYnV0aW9uIGFuZCB1c2UgaW4gc291cmNlIGFuZCBiaW5hcnkg Zm9ybXMsIHdpdGggb3Igd2l0aG91dAogKiBtb2RpZmljYXRpb24sIGFyZSBwZXJtaXR0ZWQgcHJv dmlkZWQgdGhhdCB0aGUgZm9sbG93aW5nIGNvbmRpdGlvbnMKICogYXJlIG1ldDoKICogMS4gUmVk aXN0cmlidXRpb25zIG9mIHNvdXJjZSBjb2RlIG11c3QgcmV0YWluIHRoZSBhYm92ZSBjb3B5cmln aHQKICogICAgbm90aWNlLCB0aGlzIGxpc3Qgb2YgY29uZGl0aW9ucyBhbmQgdGhlIGZvbGxvd2lu ZyBkaXNjbGFpbWVyLAogKiAgICB3aXRob3V0IG1vZGlmaWNhdGlvbiwgaW1tZWRpYXRlbHkgYXQg dGhlIGJlZ2lubmluZyBvZiB0aGUgZmlsZS4KICogMi4gUmVkaXN0cmlidXRpb25zIGluIGJpbmFy eSBmb3JtIG11c3QgcmVwcm9kdWNlIHRoZSBhYm92ZSBjb3B5cmlnaHQKICogICAgbm90aWNlLCB0 aGlzIGxpc3Qgb2YgY29uZGl0aW9ucyBhbmQgdGhlIGZvbGxvd2luZyBkaXNjbGFpbWVyIGluIHRo ZQogKiAgICBkb2N1bWVudGF0aW9uIGFuZC9vciBvdGhlciBtYXRlcmlhbHMgcHJvdmlkZWQgd2l0 aCB0aGUgZGlzdHJpYnV0aW9uLgogKiAzLiBUaGUgbmFtZSBvZiB0aGUgYXV0aG9yIG1heSBub3Qg YmUgdXNlZCB0byBlbmRvcnNlIG9yIHByb21vdGUgcHJvZHVjdHMKICogICAgZGVyaXZlZCBmcm9t IHRoaXMgc29mdHdhcmUgd2l0aG91dCBzcGVjaWZpYyBwcmlvciB3cml0dGVuIHBlcm1pc3Npb24u CiAqCiAqIFRISVMgU09GVFdBUkUgSVMgUFJPVklERUQgQlkgVEhFIEFVVEhPUiBgYEFTIElTJycg QU5EIEFOWSBFWFBSRVNTIE9SCiAqIElNUExJRUQgV0FSUkFOVElFUywgSU5DTFVESU5HLCBCVVQg Tk9UIExJTUlURUQgVE8sIFRIRSBJTVBMSUVEIFdBUlJBTlRJRVMKICogT0YgTUVSQ0hBTlRBQklM SVRZIEFORCBGSVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRSBBUkUgRElTQ0xBSU1FRC4K ICogSU4gTk8gRVZFTlQgU0hBTEwgVEhFIEFVVEhPUiBCRSBMSUFCTEUgRk9SIEFOWSBESVJFQ1Qs IElORElSRUNULAogKiBJTkNJREVOVEFMLCBTUEVDSUFMLCBFWEVNUExBUlksIE9SIENPTlNFUVVF TlRJQUwgREFNQUdFUyAoSU5DTFVESU5HLCBCVVQKICogTk9UIExJTUlURUQgVE8sIFBST0NVUkVN RU5UIE9GIFNVQlNUSVRVVEUgR09PRFMgT1IgU0VSVklDRVM7IExPU1MgT0YgVVNFLAogKiBEQVRB LCBPUiBQUk9GSVRTOyBPUiBCVVNJTkVTUyBJTlRFUlJVUFRJT04pIEhPV0VWRVIgQ0FVU0VEIEFO RCBPTiBBTlkKICogVEhFT1JZIE9GIExJQUJJTElUWSwgV0hFVEhFUiBJTiBDT05UUkFDVCwgU1RS SUNUIExJQUJJTElUWSwgT1IgVE9SVAogKiAoSU5DTFVESU5HIE5FR0xJR0VOQ0UgT1IgT1RIRVJX SVNFKSBBUklTSU5HIElOIEFOWSBXQVkgT1VUIE9GIFRIRSBVU0UgT0YKICogVEhJUyBTT0ZUV0FS RSwgRVZFTiBJRiBBRFZJU0VEIE9GIFRIRSBQT1NTSUJJTElUWSBPRiBTVUNIIERBTUFHRS4KICoK ICogJEZyZWVCU0Q6IHNyYy91c3Iuc2Jpbi9idXJuY2QvYnVybmNkLmMsdiAxLjEwIDIwMDAvMDMv MDMgMjM6MTc6Mjcgc29zIEV4cCAkCiAqLwoKLyotCiAqIHQuaC4gY2hhbmdlcyBjb3B5cmlnaHQg KGMpIDIwMDAgVG9tYXMgSHJ1egogKiBBbGwgcmlnaHRzIHJlc2VydmVkLgogKi8KCiNpbmNsdWRl IDx1bmlzdGQuaD4KI2luY2x1ZGUgPHN0ZGlvLmg+CiNpbmNsdWRlIDxzdGRsaWIuaD4KI2luY2x1 ZGUgPHN0cmluZy5oPgojaW5jbHVkZSA8ZXJyLmg+CiNpbmNsdWRlIDxzeXNleGl0cy5oPgojaW5j bHVkZSA8ZmNudGwuaD4KI2luY2x1ZGUgPHN5cy9pb2N0bC5oPgojaW5jbHVkZSA8c3lzL3N0YXQu aD4KI2luY2x1ZGUgPHN5cy9jZGlvLmg+CiNpbmNsdWRlIDxzeXMvY2RyaW8uaD4KCiNpbmNsdWRl IDxzeXMvcGFyYW0uaD4KCiNkZWZpbmUgQkxPQ0tTCTE2CgpzdGF0aWMgaW50IGZkLCBzYXZlZF9i bG9ja19zaXplOwp2b2lkIGNsZWFudXAoaW50KTsKaW50IGlzb19nZXRfc3NlY3Rvcl91c2VyKGlu dCk7CgppbnQKbWFpbihpbnQgYXJnYywgY2hhciAqKmFyZ3YpCnsKCWludCBjaCwgc3BlZWQgPSAx LCBwcmVlbXAgPSAwLCB0ZXN0X3dyaXRlID0gMCwgZWplY3QgPSAwLCBxdWlldCA9IDA7CgljaGFy ICpkZXZuYW1lID0gIi9kZXYvYWNkMGMiOwoJY2hhciBidWZbMjM1MipCTE9DS1NdOwoJaW50IGFy ZywgZmlsZSwgYWRkciwgY291bnQsIGZpbGVzaXplOwoJaW50IGJsb2NrX3NpemUgPSAwLCBjZG9w ZW4gPSAwLCBzaXplLCB0b3Rfc2l6ZSA9IDA7CglzdHJ1Y3QgY2RyX3RyYWNrIHRyYWNrOwoJc3Ry dWN0IHN0YXQgc3RhdDsKCgl3aGlsZSAoKGNoID0gZ2V0b3B0KGFyZ2MsIGFyZ3YsICJlZjpwcXM6 dCIpKSAhPSAtMSkgewoJCXN3aXRjaCAoY2gpIHsKCQljYXNlICdlJzoKCQkJZWplY3QgPSAxOwoJ CQlicmVhazsKCgkJY2FzZSAnZic6CgkJCWRldm5hbWUgPSBvcHRhcmc7CgkJCWJyZWFrOwoKCQlj YXNlICdwJzoKCQkJcHJlZW1wID0gMTsKCQkJYnJlYWs7CgoJCWNhc2UgJ3EnOgoJCQlxdWlldCA9 IDE7CgkJCWJyZWFrOwoKCQljYXNlICdzJzoKCQkJc3BlZWQgPSBhdG9pKG9wdGFyZyk7CgkJCWJy ZWFrOwoKCQljYXNlICd0JzoKCQkJdGVzdF93cml0ZSA9IDE7CgkJCWJyZWFrOwoKCQlkZWZhdWx0 OiAKCQkJZXhpdChFWF9VU0FHRSk7CgkJfQoJfQoJYXJnYyAtPSBvcHRpbmQ7Cglhcmd2ICs9IG9w dGluZDsKCglpZiAoKGZkID0gb3BlbihkZXZuYW1lLCBPX1JEV1IsIDApKSA8IDApCgkJZXJyKEVY X05PSU5QVVQsICJvcGVuKCVzKSIsIGRldm5hbWUpOwoKCWlmIChpb2N0bChmZCwgQ0RSSU9DV1JJ VEVTUEVFRCwgJnNwZWVkKSA8IDApIAogICAgICAgCQllcnIoRVhfSU9FUlIsICJpb2N0bChDRFJJ T0NXUklURVNQRUVEKSIpOwoKCWlmIChpb2N0bChmZCwgQ0RSSU9DR0VUQkxPQ0tTSVpFLCAmc2F2 ZWRfYmxvY2tfc2l6ZSkgPCAwKSAKICAgICAgIAkJZXJyKEVYX0lPRVJSLCAiaW9jdGwoQ0RSSU9D R0VUQkxPQ0tTSVpFKSIpOwoKCWVycl9zZXRfZXhpdChjbGVhbnVwKTsKCglmb3IgKGFyZyA9IDA7 IGFyZyA8IGFyZ2M7IGFyZysrKSB7CgkJaWYgKCFzdHJjbXAoYXJndlthcmddLCAiZml4YXRlIikp IHsKCQkJaWYgKCFxdWlldCkKCQkJCWZwcmludGYoc3RkZXJyLCAiZml4YXRpbmcgQ0QsIHBsZWFz ZSB3YWl0Li5cbiIpOwoJCQlpZiAoaW9jdGwoZmQsIENEUklPQ0NMT1NFRElTSykgPCAwKQogICAg ICAgIAkJCWVycihFWF9JT0VSUiwgImlvY3RsKENEUklPQ0NMT1NFRElTSykiKTsKCQkJYnJlYWs7 CgkJfQoJCWlmICghc3RyY21wKGFyZ3ZbYXJnXSwgIm1zaW5mbyIpKSB7CgkJICAvKnQuaC4qLy8q IHN0cnVjdCBpb2NfcmVhZF90b2Nfc2luZ2xlX2VudHJ5IGVudHJ5OwoKCQkJYnplcm8oJmVudHJ5 LCBzaXplb2Yoc3RydWN0IGlvY19yZWFkX3RvY19zaW5nbGVfZW50cnkpKTsKCQkJZW50cnkuYWRk cmVzc19mb3JtYXQgPSBDRF9MQkFfRk9STUFUOwoJCQlpZiAoaW9jdGwoZmQsIENESU9SRUFEVE9D RU5UUlksICZlbnRyeSkgPCAwKSB7CgkJCSAgZXJyKEVYX0lPRVJSLCAiaW9jdGwoQ0RJT1JFQURU T0NFTlRSWSkiKTsgCgkJCSAgfSAqLwoJCQlpZiAoaW9jdGwoZmQsIENEUklPQ05FWFRXUklURUFC TEVBRERSLCAmYWRkcikgPCAwKSAKCQkJCWVycihFWF9JT0VSUiwgImlvY3RsKENEUklPQ05FWFRX UklURUFCTEVBRERSKSIpOwoJCQlmcHJpbnRmKHN0ZG91dCwgIiVkLCVkXG4iLCBpc29fZ2V0X3Nz ZWN0b3JfdXNlcihmZCksIGFkZHIpOwoJCQlicmVhazsKCQl9CgkJaWYgKCFzdHJjbXAoYXJndlth cmddLCAiYmxhbmsiKSkgewoJCQlpZiAoIXF1aWV0KQoJCQkJZnByaW50ZihzdGRlcnIsICJibGFu a2luZyBDRCwgcGxlYXNlIHdhaXQuLlxuIik7CgkJCWlmIChpb2N0bChmZCwgQ0RSSU9DQkxBTksp IDwgMCkKICAgICAgICAJCQllcnIoRVhfSU9FUlIsICJpb2N0bChDRFJJT0NCTEFOSykiKTsKCQkJ Y29udGludWU7CgkJfQoJCWlmICghc3RyY21wKGFyZ3ZbYXJnXSwgImF1ZGlvIikgfHwgIXN0cmNt cChhcmd2W2FyZ10sICJyYXciKSkgewoJCQl0cmFjay50ZXN0X3dyaXRlID0gdGVzdF93cml0ZTsK CQkJdHJhY2sudHJhY2tfdHlwZSA9IENEUl9EQl9SQVc7CgkJCXRyYWNrLnByZWVtcCA9IHByZWVt cDsKCQkJYmxvY2tfc2l6ZSA9IDIzNTI7CgkJCWNvbnRpbnVlOwoJCX0KCQlpZiAoIXN0cmNtcChh cmd2W2FyZ10sICJkYXRhIikgfHwgIXN0cmNtcChhcmd2W2FyZ10sICJtb2RlMSIpKSB7CgkJCXRy YWNrLnRlc3Rfd3JpdGUgPSB0ZXN0X3dyaXRlOwoJCQl0cmFjay50cmFja190eXBlID0gQ0RSX0RC X1JPTV9NT0RFMTsKCQkJdHJhY2sucHJlZW1wID0gMDsKCQkJYmxvY2tfc2l6ZSA9IDIwNDg7CgkJ CWNvbnRpbnVlOwoJCX0KCQlpZiAoIXN0cmNtcChhcmd2W2FyZ10sICJtb2RlMiIpKSB7CgkJCXRy YWNrLnRlc3Rfd3JpdGUgPSB0ZXN0X3dyaXRlOwoJCQl0cmFjay50cmFja190eXBlID0gQ0RSX0RC X1JPTV9NT0RFMjsKCQkJdHJhY2sucHJlZW1wID0gMDsKCQkJYmxvY2tfc2l6ZSA9IDIzMzY7CgkJ CWNvbnRpbnVlOwoJCX0KCQlpZiAoIXN0cmNtcChhcmd2W2FyZ10sICJYQW1vZGUxIikpIHsKCQkJ dHJhY2sudGVzdF93cml0ZSA9IHRlc3Rfd3JpdGU7CgkJCXRyYWNrLnRyYWNrX3R5cGUgPSBDRFJf REJfWEFfTU9ERTE7CgkJCXRyYWNrLnByZWVtcCA9IDA7CgkJCWJsb2NrX3NpemUgPSAyMDQ4OwoJ CQljb250aW51ZTsKCQl9CgkJaWYgKCFibG9ja19zaXplKQoJCQllcnIoRVhfTk9JTlBVVCwgIm5v IGRhdGEgZm9ybWF0IHNlbGVjdGVkIik7CgoJCWlmICgoZmlsZSA9IG9wZW4oYXJndlthcmddLCBP X1JET05MWSwgMCkpIDwgMCkKCQkJZXJyKEVYX05PSU5QVVQsICJvcGVuKCVzKSIsIGFyZ3ZbYXJn XSk7CgoJCWlmICghY2RvcGVuKSB7CgkJCWlmIChpb2N0bChmZCwgQ0RSSU9DT1BFTkRJU0spIDwg MCkKICAgICAgICAJCQllcnIoRVhfSU9FUlIsICJpb2N0bChDRFJJT0NPUEVORElTSykiKTsKCQkJ Y2RvcGVuID0gMTsKCQl9CgkJaWYgKGlvY3RsKGZkLCBDRFJJT0NPUEVOVFJBQ0ssICZ0cmFjaykg PCAwKQogICAgICAgIAkJZXJyKEVYX0lPRVJSLCAiaW9jdGwoQ0RSSU9DT1BFTlRSQUNLKSIpOwoK CQlpZiAoaW9jdGwoZmQsIENEUklPQ05FWFRXUklURUFCTEVBRERSLCAmYWRkcikgPCAwKSAKICAg ICAgICAJCWVycihFWF9JT0VSUiwgImlvY3RsKENEUklPQ05FWFRXUklURUFCTEVBRERSKSIpOwoK CQlpZiAoZnN0YXQoZmlsZSwgJnN0YXQpIDwgMCkKCQkJZXJyKEVYX0lPRVJSLCAiZnN0YXQoJXMp IiwgYXJndlthcmddKTsKCQlmaWxlc2l6ZSA9IHN0YXQuc3Rfc2l6ZSAvIDEwMjQ7CgkJaWYgKCFx dWlldCkgewoJCQlmcHJpbnRmKHN0ZGVyciwgIm5leHQgd3JpdGVhYmxlIExCQSAlZFxuIiwgYWRk cik7CgkJCWZwcmludGYoc3RkZXJyLCAid3JpdGluZyBmcm9tIGZpbGUgJXMgc2l6ZSAlZCBLQlxu IiwKCQkJCWFyZ3ZbYXJnXSwgZmlsZXNpemUpOwoJCX0KCQlsc2VlayhmZCwgYWRkciAqIGJsb2Nr X3NpemUsIFNFRUtfU0VUKTsKCQlzaXplID0gMDsKCQlpZiAoZmlsZXNpemUgPT0gMCkKCQkJZmls ZXNpemUrKzsJLyogY2hlYXQsIGF2b2lkIGRpdmlkZSBieSB6ZXJvICovCgoJCXdoaWxlICgoY291 bnQgPSByZWFkKGZpbGUsIGJ1ZiwgYmxvY2tfc2l6ZSAqIEJMT0NLUykpID4gMCkgewkKCQkJaW50 IHJlczsKCQkJaWYgKGNvdW50ICUgYmxvY2tfc2l6ZSkgewoJCQkJLyogcGFkIGZpbGUgdG8gJSBi bG9ja19zaXplICovCgkJCQliemVybygmYnVmW2NvdW50XSwgYmxvY2tfc2l6ZSAqIEJMT0NLUyAt IGNvdW50KTsKCQkJCWNvdW50ID0gKChjb3VudCAvIGJsb2NrX3NpemUpICsgMSkgKiBibG9ja19z aXplOwoJCQl9CgkJCWlmICgocmVzID0gd3JpdGUoZmQsIGJ1ZiwgY291bnQpKSAhPSBjb3VudCkg ewoKCQkJCWZwcmludGYoc3RkZXJyLCAiXG5vbmx5IHdyb3RlICVkIG9mICVkIGJ5dGVzXG4iLAoJ CQkJCXJlcywgY291bnQpOwoJCQkJYnJlYWs7CgkJCX0KCQkJc2l6ZSArPSBjb3VudDsKCQkJdG90 X3NpemUgKz0gY291bnQ7CgkJCWlmICghcXVpZXQpIHsKCQkJCWludCBwY3Q7CgoJCQkJcGN0ID0g KHNpemUgLyAxMDI0KSAqIDEwMCAvIGZpbGVzaXplOwoJCQkJZnByaW50ZihzdGRlcnIsICJ3cml0 dGVuIHRoaXMgdHJhY2sgJWQgS0IiCgkJCQkJCSIgKCVkJSUpIHRvdGFsICVkIEtCXHIiLAoJCQkJ CQlzaXplLzEwMjQsIHBjdCwgdG90X3NpemUvMTAyNCk7CgkJCX0KCQl9CgkJaWYgKCFxdWlldCkK CQkJZnByaW50ZihzdGRlcnIsICJcbiIpOwoJCWNsb3NlKGZpbGUpOwoJCWlmIChpb2N0bChmZCwg Q0RSSU9DQ0xPU0VUUkFDSykgPCAwKQogICAgICAgIAkJZXJyKEVYX0lPRVJSLCAiaW9jdGwoQ0RS SU9DQ0xPU0VUUkFDSykiKTsKCX0KCglpZiAoaW9jdGwoZmQsIENEUklPQ1NFVEJMT0NLU0laRSwg JnNhdmVkX2Jsb2NrX3NpemUpIDwgMCkgCiAgICAgICAJCWVycihFWF9JT0VSUiwgImlvY3RsKENE UklPQ1NFVEJMT0NLU0laRSkiKTsKCglpZiAoZWplY3QpCgkJaWYgKGlvY3RsKGZkLCBDRElPQ0VK RUNUKSA8IDApCgkJCWVycihFWF9JT0VSUiwgImlvY3RsKENESU9DRUpFQ1QpIik7CgljbG9zZShm ZCk7Cn0KCnZvaWQgY2xlYW51cChpbnQgZHVtbXkpCnsKCWlmIChpb2N0bChmZCwgQ0RSSU9DU0VU QkxPQ0tTSVpFLCAmc2F2ZWRfYmxvY2tfc2l6ZSkgPCAwKSAKICAgICAgIAkJZXJyKEVYX0lPRVJS LCAiaW9jdGwoQ0RSSU9DU0VUQkxPQ0tTSVpFKSIpOwp9CgovKiB0LmguCiAqIFRyeSB0byBmaW5k IHRoZSBzdGFydCBvZiB0aGUgbGFzdCBkYXRhIHRyYWNrIG9uIHRoaXMgQ0QtUk9NLiAgVGhpcwog KiBpcyB1c2VkIHRvIG1vdW50IHRoZSBsYXN0IHNlc3Npb24gb2YgYSBtdWx0aS1zZXNzaW9uIENE LiAgQmFpbCBvdXQKICogYW5kIHJldHVybiAwIGlmIHdlIGZhaWwsIHRoaXMgaXMgYWx3YXlzIGEg c2FmZSBiZXQuIFByb2NlZHVyZSBmcm9tCiAqIGtlcm5lbCAvdXNyL3NyYy9zeXMvaXNvZnMvY2Q5 NjYwL2NkOTY2MF92ZnNvcHMuYyhpc29fZ2V0X3NzZWN0b3IpLgogKiBDaGFuZ2VkIGZvciB1c2Ug b3V0c2lkZSBvZiB0aGUga2VybmVsLgogKi8KaW50IGlzb19nZXRfc3NlY3Rvcl91c2VyKGZkKQoJ aW50IGZkOwp7CglzdHJ1Y3QgaW9jX3RvY19oZWFkZXIgaDsKCXN0cnVjdCBpb2NfcmVhZF90b2Nf c2luZ2xlX2VudHJ5IHQ7CglpbnQgaTsKCgoJaWYgKGlvY3RsKGZkLCBDRElPUkVBRFRPQ0hFQURF UiwgKGNhZGRyX3QpJmgpICE9IDApCgkJcmV0dXJuIDA7CgoJZm9yIChpID0gaC5lbmRpbmdfdHJh Y2s7IGkgPj0gMDsgaS0tKSB7CgkJdC5hZGRyZXNzX2Zvcm1hdCA9IENEX0xCQV9GT1JNQVQ7CgkJ dC50cmFjayA9IGk7CgkJaWYgKGlvY3RsKGZkLCBDRElPUkVBRFRPQ0VOVFJZLCAoY2FkZHJfdCkm dCkgIT0gMCkKCQkJcmV0dXJuIDA7CgkJaWYgKCh0LmVudHJ5LmNvbnRyb2wgJiA0KSAhPSAwKQoJ CQkvKiBmb3VuZCBhIGRhdGEgdHJhY2sgKi8KCQkJYnJlYWs7Cgl9CgoJaWYgKGkgPCAwKQoJCXJl dHVybiAwOwoKCXJldHVybiBudG9obCh0LmVudHJ5LmFkZHIubGJhKTsKfQo= --Boundary-=_yzAZOHsNGHcxSfUBSnsNWfUJeLgt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 3:46:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 47A8537B4C5; Fri, 20 Oct 2000 03:46:43 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id DAA28002; Fri, 20 Oct 2000 03:43:14 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpdAAAz4ayi0; Thu Oct 19 22:49:33 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id WAA10743; Thu, 19 Oct 2000 22:52:56 -0700 (MST) From: Terry Lambert Message-Id: <200010200552.WAA10743@usr09.primenet.com> Subject: Re: Routing issue with cable modem To: marko@tellurian.com (Marko Ruban) Date: Fri, 20 Oct 2000 05:52:55 +0000 (GMT) Cc: freebsd-questions@FreeBSD.ORG (FreeBSD questions), freebsd-hackers@FreeBSD.ORG In-Reply-To: <39EF5505.7B7C2BFD@tellurian.com> from "Marko Ruban" at Oct 19, 2000 04:09:41 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess no one knew the answer to my original question about getting RCN > cable modem (with analog upstream line dialup) to work. So here's a > somewhat simplified question. I narrowed the problem down to routing. > Cable modem does dial out when I try to ping something on it's subnet > (10.17.56.###), however it does not respond to any broadcast ARP queries > about location of DNS server. [ ... ] > P.S.S. On a side note: it would be very interesting to know how MSWin98 > does it's network setup, that it has no trouble using the modem. Have you tried typing "route print" into an MSDOS window, and having Windows simply tell you what its network configuration? I suspect you are incorrectly setting up an asymetric route, since you say that you have zero upchannel through the cable line, and must use an analog dialup, instead... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 8:13:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from DarkOne.ural.net (relay.ural.ru [195.64.192.49]) by hub.freebsd.org (Postfix) with ESMTP id 63AB037B4D7 for ; Fri, 20 Oct 2000 08:13:08 -0700 (PDT) Received: from relay.svrw.ru (relay.svrw.ru [195.64.206.2]) by DarkOne.ural.net (8.11.1/eTn) with ESMTP id e9KFCva43813 for ; Fri, 20 Oct 2000 21:12:58 +0600 (ESS) Received: from ivc-gate.svrw.mps (the.svrw.ru [195.64.206.7]) by relay.svrw.ru (8.8.8/8.8.8) with ESMTP id TAA28923 for ; Fri, 20 Oct 2000 19:12:51 +0400 Received: by ivc-gate.svrw.mps with Internet Mail Service (5.5.2650.21) id ; Fri, 20 Oct 2000 19:12:51 +0400 Message-ID: <91CBC4487424D411B17900508B5F0C8B160660@tumen-mail.tumen.svrw.mps> From: =?koi8-r?Q?=EB=C1=D2=D0=D5=DB=C9=CE_=F3=C5=D2=C7=C5=CA_=F7=C9=CB=D4?= =?koi8-r?Q?=CF=D2=CF=D7=C9=DE?= To: "'freebsd-hackers@FreeBSD.ORG'" Subject: HELP Date: Fri, 20 Oct 2000 19:01:38 +0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HELP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 8:46:35 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 64AE737B4CF for ; Fri, 20 Oct 2000 08:46:33 -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 JAA14659; Fri, 20 Oct 2000 09:46:25 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA04367; Fri, 20 Oct 2000 09:46:24 -0600 (MDT) (envelope-from nate) Date: Fri, 20 Oct 2000 09:46:24 -0600 (MDT) Message-Id: <200010201546.JAA04367@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hackers@FreeBSD.org Cc: Guy Helmer Subject: Re: IPFW bug/incoming TCP connections being let in. In-Reply-To: <200010192029.OAA25357@nomad.yogotech.com> References: <200010192029.OAA25357@nomad.yogotech.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 > I had blocked incoming TCP connections coming into my network using > IPFW, and I noticed that my brother was able to establish a Napster > connection, even though I had blocked it earlier. *sigh* Thanks to Guy Helmer for being patient with me as I fretted about this. I just found out that Napster leaves a client running in the background, and even though I had added firewall rules to block new connections to the server, the old 'established' connection was still up and running. I didn't realize that was the case, so that everytime I 'restarted' Napster the packets were getting through. In fact, what had happened was that the 'GUI' was being stopped/restarted, but the network portion was running the entire time. Once Guy walked me through and showed me that things were indeed working correct, we rebooted the box and my rules worked fine. Sorry for the false alarm! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 8:51:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 0DFF337B4D7 for ; Fri, 20 Oct 2000 08:51:52 -0700 (PDT) Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24]) by thehousleys.net (8.11.0/8.11.0) with ESMTP id e9KFpkQ63668; Fri, 20 Oct 2000 11:51:46 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39F06A10.8643A0B0@thehousleys.net> Date: Fri, 20 Oct 2000 11:51:44 -0400 From: James Housley X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: freebsd-hackers@FreeBSD.ORG Subject: Blocking Napster (WAS: IPFW bug/incoming TCP connections being let in.) References: <200010192029.OAA25357@nomad.yogotech.com> <200010201546.JAA04367@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > > I had blocked incoming TCP connections coming into my network using > > IPFW, and I noticed that my brother was able to establish a Napster > > connection, even though I had blocked it earlier. > > *sigh* > > Thanks to Guy Helmer for being patient with me as I fretted about this. > > I just found out that Napster leaves a client running in the background, > and even though I had added firewall rules to block new connections to > the server, the old 'established' connection was still up and running. > This might be helpful to you and others. Since napster uses what ever ports it can find the best way is to block the servers. # Napster $fwcmd add deny tcp from any to 208.178.163.56/29 via tun0 $fwcmd add deny tcp from any to 208.178.175.128/29 via tun0 $fwcmd add deny tcp from any to 208.49.239.240/28 via tun0 $fwcmd add deny tcp from any to 208.49.228.0/24 via tun0 $fwcmd add deny tcp from any to 208.184.216.0/24 via tun0 Jim -- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net --------------------------------------------------------------------- Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 8:52:43 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 53F9137B4CF for ; Fri, 20 Oct 2000 08:52:40 -0700 (PDT) Received: from ovis.net (s12.pm5.ovis.net [207.0.147.79]) by ns1.ovis.net (8.9.3/8.9.3) with ESMTP id LAA11055; Fri, 20 Oct 2000 11:51:06 -0400 Message-ID: <39F06C55.CB763160@ovis.net> Date: Fri, 20 Oct 2000 12:01:25 -0400 From: Steve Kudlak Reply-To: chromexa@ovis.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD ezn/58/n (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: I'm convinced 'gcc' is meant to be pronounced 'ARRRRGGGHHH!' References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Will someone please inform the gcc developers of the last decade's > advances in C standardization? Yes, Virginia, ISO C (it's not ISO C > any more, and hasn't been since 1989) does support 'long long' and the > 'll' format. > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Sorry topost to everyone. I'll get my mailer fixed. But many times I have been comvinced that IEEE is indeed a primal scream! :) Have Fun, Sends Steve P.S. Back to lurking and hacking and amnsewering stacks of email. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 8:55:55 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 E944437B4C5 for ; Fri, 20 Oct 2000 08:55:48 -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 JAA14852; Fri, 20 Oct 2000 09:55:42 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA04439; Fri, 20 Oct 2000 09:55:41 -0600 (MDT) (envelope-from nate) Date: Fri, 20 Oct 2000 09:55:41 -0600 (MDT) Message-Id: <200010201555.JAA04439@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: James Housley Cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: Blocking Napster (WAS: IPFW bug/incoming TCP connections being let in.) In-Reply-To: <39F06A10.8643A0B0@thehousleys.net> References: <200010192029.OAA25357@nomad.yogotech.com> <200010201546.JAA04367@nomad.yogotech.com> <39F06A10.8643A0B0@thehousleys.net> 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 > > > I had blocked incoming TCP connections coming into my network using > > > IPFW, and I noticed that my brother was able to establish a Napster > > > connection, even though I had blocked it earlier. > > > > *sigh* > > > > Thanks to Guy Helmer for being patient with me as I fretted about this. > > > > I just found out that Napster leaves a client running in the background, > > and even though I had added firewall rules to block new connections to > > the server, the old 'established' connection was still up and running. > > > > This might be helpful to you and others. Since napster uses what ever > ports it can find the best way is to block the servers. > > # Napster > $fwcmd add deny tcp from any to 208.178.163.56/29 via tun0 > $fwcmd add deny tcp from any to 208.178.175.128/29 via tun0 > $fwcmd add deny tcp from any to 208.49.239.240/28 via tun0 > $fwcmd add deny tcp from any to 208.49.228.0/24 via tun0 > $fwcmd add deny tcp from any to 208.184.216.0/24 via tun0 I had these rules in place, but it appears that there are new servers in place. I also had to to add > $fwcmd add deny tcp from any to 64.124.41.0/24 via tun0 (I'm guessing it's a class C, I just had hit two addresses in that block, so I blocked the entire class C.) The above is the reason I was trying to do a 'port' block of the Napster servers, because trying to keep up with IP addresses is a real pain in the butt... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 8:58:40 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 36A7037B479 for ; Fri, 20 Oct 2000 08:58:25 -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 PAA13867 for ; Fri, 20 Oct 2000 15:28:51 +0200 Received: by lflat.vas.mobilix.dk (Postfix, from userid 72044) id 71A2BA8A6; Fri, 20 Oct 2000 14:50:43 +0200 (CEST) Date: Fri, 20 Oct 2000 14:50:43 +0200 From: Vadim Belman To: freebsd-hackers@freebsd.org Subject: NFS/VM deadlock report and help request Message-ID: <20001020145043.B73760@lflat.vas.mobilix.dk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm trying to locate a bug which causes a deadlock in VM subsystem and would like to find some help here. First of all, I'd describe the situation which has revealed the problem. We run a bunch of web servers providing free webpage service to our customers. Back in July it was decided to upgrade the boxes due to security issues with older kernels. Same time some other changes was done to the internal network and some other stuff and now it's rather unclear whether the upgrade is the cause, but thereafter we experience systematic httpd hangups in uniterruptable waits ('D' status in ps output). Each hangup was related to a webcam page with a image been updated each minute or so via ftp (the way our customers update their pages). While trying to find a solution we tested thttpd instead of apache with one single box serving both HTTP and FTP. It resulted in even more regular hangups occuring approximately each hour perhaps due to single-process nature of thttpd. Just after another hangup the box was taken out of service and preserved in that state so that I was able to dig into the kernel and see what's going on. Here is technical details I've got so far. The kernel config I supply as an attachment. Kernel-mode stack trace for the thttpd process looks like this: ====================================================================== IdlePTD 2928640 initial pcb at 1f1cf000 panic messages: --- --- #0 mi_switch () at ../../kern/kern_synch.c:858 858 if (switchtime.tv_sec == 0) #0 mi_switch () at ../../kern/kern_synch.c:858 #1 0xc0151881 in tsleep (ident=0xc05c38d0, priority=4, wmesg=0xc0233171 "vmopar", timo=0) at ../../kern/kern_synch.c:467 #2 0xc01e40ff in vm_object_page_remove (object=0xdeb81c60, start=2, end=8, clean_only=0) at ../../vm/vm_page.h:546 #3 0xc01e8189 in vnode_pager_setsize (vp=0xdeb8ec80, nsize=8192) at ../../vm/vnode_pager.c:289 #4 0xc01a1cb7 in nfs_loadattrcache (vpp=0xdeb3ebec, mdp=0xdeb3ebf8, dposp=0xdeb3ebfc, vaper=0x0) at ../../nfs/nfs_subs.c:1335 #5 0xc01a87e7 in nfs_readrpc (vp=0xdeb8ec80, uiop=0xdeb3ec60, cred=0xc4d49100) at ../../nfs/nfs_vnops.c:1102 #6 0xc019b219 in nfs_getpages (ap=0xdeb3ec98) at ../../nfs/nfs_bio.c:153 #7 0xc01e8736 in vnode_pager_getpages (object=0xdeb81c60, m=0xdeb3ed2c, count=2, reqpage=0) at vnode_if.h:1089 #8 0xc01dd606 in vm_fault (map=0xdc3e7e80, vaddr=712876032, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_pager.h:130 #9 0xc0209266 in trap_pfault (frame=0xdeb3eddc, usermode=0, eva=712876032) at ../../i386/i386/trap.c:800 #10 0xc0208ecf in trap (frame={tf_fs = 134545424, tf_es = 16, tf_ds = -599916528, tf_edi = -1054114628, tf_esi = 712876031, tf_ebp = -558633400, tf_isp = -558633464, tf_ebx = 2048, tf_edx = 712876867, tf_ecx = 209, tf_eax = -558641152, tf_trapno = 12, tf_err = 0, tf_eip = -1071610959, tf_cs = 8, tf_eflags = 66054, tf_esp = -558633252, tf_ss = -558633260}) at ../../i386/i386/trap.c:426 #11 0xc02083b1 in generic_copyin () #12 0xc0169c64 in sosend (so=0xdaea9780, addr=0x0, uio=0xdeb3eedc, top=0x0, control=0x0, flags=0, p=0xdc3e45e0) at ../../kern/uipc_socket.c:567 #13 0xc015ef50 in soo_write (fp=0xc4eb0180, uio=0xdeb3eedc, cred=0xc4d49100, flags=0, p=0xdc3e45e0) at ../../kern/sys_socket.c:78 #14 0xc015bc52 in dofilewrite (p=0xdc3e45e0, fp=0xc4eb0180, fd=76, buf=0x2a7d9b43, nbyte=6797, offset=-1, flags=0) at ../../sys/file.h:159 #15 0xc015bb57 in write (p=0xdc3e45e0, uap=0xdeb3ef80) at ../../kern/sys_generic.c:298 #16 0xc02098a5 in syscall2 (frame={tf_fs = -1078001617, tf_es = -558694353, tf_ds = 47, tf_edi = 136698368, tf_esi = 68, tf_ebp = -1077938184, tf_isp = -558633004, tf_ebx = 0, tf_edx = 0, tf_ecx = 134826912, tf_eax = 4, tf_trapno = 0, tf_err = 2, tf_eip = 672115896, tf_cs = 31, tf_eflags = 514, tf_esp = -1077938244, tf_ss = 47}) at ../../i386/i386/trap.c:1126 #17 0xc01fe4d6 in Xint0x80_syscall () #18 0x804a443 in ?? () #19 0x80499b5 in ?? () ====================================================================== Further investigation has shown that the hangup happend while trying to release a page which is most likely locked by NFS subsystem. The page belongs to the image file I mentioned before. Versions of the sources shown in the stack trace: ====================================================================== $FreeBSD: src/sys/kern/kern_synch.c,v 1.87.2.1 2000/05/16 06:58:12 dillon Exp $ $FreeBSD: src/sys/kern/kern_synch.c,v 1.87.2.1 2000/05/16 06:58:12 dillon Exp $ $FreeBSD: src/sys/kern/kern_synch.c,v 1.87.2.1 2000/05/16 06:58:12 dillon Exp $ $FreeBSD: src/sys/vm/vm_page.h,v 1.75 1999/12/29 04:55:10 peter Exp $ $FreeBSD: src/sys/vm/vnode_pager.c,v 1.116 1999/10/29 18:09:36 phk Exp $ $FreeBSD: src/sys/nfs/nfs_subs.c,v 1.90 2000/02/13 03:32:06 peter Exp $ $FreeBSD: src/sys/nfs/nfs_vnops.c,v 1.150 2000/01/05 00:32:18 dillon Exp $ $FreeBSD: src/sys/nfs/nfs_bio.c,v 1.83 2000/01/05 05:11:36 dillon Exp $ $FreeBSD: src/sys/vm/vm_pager.h,v 1.24.2.1 2000/03/27 21:34:45 dillon Exp $ $FreeBSD: src/sys/i386/i386/trap.c,v 1.147.2.1 2000/05/16 06:58:07 dillon Exp $ $FreeBSD: src/sys/i386/i386/trap.c,v 1.147.2.1 2000/05/16 06:58:07 dillon Exp $ $FreeBSD: src/sys/kern/uipc_socket.c,v 1.68.2.2 2000/05/05 03:49:57 jlemon Exp $ $FreeBSD: src/sys/kern/sys_socket.c,v 1.28 1999/11/08 03:30:59 peter Exp $ $FreeBSD: src/sys/sys/file.h,v 1.22.2.4 2000/05/16 16:27:32 dillon Exp $ $FreeBSD: src/sys/kern/sys_generic.c,v 1.55.2.1 2000/05/13 19:28:13 dillon Exp $ $FreeBSD: src/sys/i386/i386/trap.c,v 1.147.2.1 2000/05/16 06:58:07 dillon Exp $ ====================================================================== I'm looking for some help with further analysis directions because from this point I'm not good enough with kernel internals. -- /Voland Vadim Belman E-mail: voland@lflat.org --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="KERNEL-4.X" machine "i386" cpu "I686_CPU" ident "KERNEL-4-WWW" maxusers 512 options INET options FFS options FFS_ROOT options NFS options NFS_NOSERVER options "CD9660" options PROCFS options "COMPAT_43" options SCSI_DELAY=15000 options UCONSOLE options USERCONFIG options KTRACE options SYSVSHM options SYSVSEM options SYSVMSG options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM options NMBCLUSTERS=20000 options QUOTA options MAXDSIZ="(512*1024*1024)" options DFLDSIZ="(256*1024*1024)" options INCLUDE_CONFIG_FILE device isa device pci device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ncr device ahc device sym device bt0 at isa? device scbus device da device pass device cd device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? pseudo-device splash device sc0 at isa? options SC_HISTORY_SIZE=512 device npx0 at isa? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? irq 7 device ppbus device plip device ppi device de device fxp pseudo-device loop pseudo-device ether pseudo-device tun pseudo-device pty 64 pseudo-device bpf options NFS_DEBUG makeoptions DEBUG=-g --SUOF0GtieIMvvwua-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 9:18:16 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 35D0237B4D7 for ; Fri, 20 Oct 2000 09:18:12 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Oct 2000 17:18:11 +0100 (BST) Date: Fri, 20 Oct 2000 17:18:10 +0100 From: David Malone To: Vadim Belman Cc: freebsd-hackers@freebsd.org Subject: Re: NFS/VM deadlock report and help request Message-ID: <20001020171810.A28345@walton.maths.tcd.ie> References: <20001020145043.B73760@lflat.vas.mobilix.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001020145043.B73760@lflat.vas.mobilix.dk>; from voland@lflat.org on Fri, Oct 20, 2000 at 02:50:43PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 20, 2000 at 02:50:43PM +0200, Vadim Belman wrote: > The kernel config I supply as an attachment. Kernel-mode stack > trace for the thttpd process looks like this: I think we've seen a similar problem and have a work around for it. You could try the following patch, though it might take more fiddling to get it right. (The patch is by Ian Dowse, Matt Dillon had a quick look at it and said it looked OK, we've been testing it for a bit here). David. Index: nfs/nfs.h =================================================================== RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfs.h,v retrieving revision 1.53 diff -u -r1.53 nfs.h --- nfs/nfs.h 2000/01/13 20:18:25 1.53 +++ nfs/nfs.h 2000/10/20 16:13:49 @@ -616,7 +616,7 @@ struct ucred *, struct mbuf **, struct mbuf **, caddr_t *)); int nfs_loadattrcache __P((struct vnode **, struct mbuf **, caddr_t *, - struct vattr *)); + struct vattr *, int)); int nfs_namei __P((struct nameidata *, fhandle_t *, int, struct nfssvc_sock *, struct sockaddr *, struct mbuf **, caddr_t *, struct vnode **, struct proc *, int, int)); Index: nfs/nfs_subs.c =================================================================== RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfs_subs.c,v retrieving revision 1.90 diff -u -r1.90 nfs_subs.c --- nfs/nfs_subs.c 2000/02/13 03:32:06 1.90 +++ nfs/nfs_subs.c 2000/10/20 16:13:49 @@ -1203,11 +1203,12 @@ * copy the attributes to *vaper */ int -nfs_loadattrcache(vpp, mdp, dposp, vaper) +nfs_loadattrcache(vpp, mdp, dposp, vaper, dontshrink) struct vnode **vpp; struct mbuf **mdp; caddr_t *dposp; struct vattr *vaper; + int dontshrink; { register struct vnode *vp = *vpp; register struct vattr *vap; @@ -1322,9 +1323,18 @@ vap->va_gen = fxdr_unsigned(u_int32_t,fp->fa2_ctime.nfsv2_usec); vap->va_filerev = 0; } + np->n_attrstamp = time_second; if (vap->va_size != np->n_size) { if (vap->va_type == VREG) { - if (np->n_flag & NMODIFIED) { + if (dontshrink && vap->va_size < np->n_size) { + /* + * We've been told not to shrink the file; + * zero np->n_attrstamp to indicate that + * the attributes are stale. + */ + vap->va_size = np->n_size; + np->n_attrstamp = 0; + } else if (np->n_flag & NMODIFIED) { if (vap->va_size < np->n_size) vap->va_size = np->n_size; else @@ -1337,7 +1347,6 @@ np->n_size = vap->va_size; } } - np->n_attrstamp = time_second; if (vaper != NULL) { bcopy((caddr_t)vap, (caddr_t)vaper, sizeof(*vap)); if (np->n_flag & NCHG) { Index: nfs/nfsm_subs.h =================================================================== RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfsm_subs.h,v retrieving revision 1.27 diff -u -r1.27 nfsm_subs.h --- nfs/nfsm_subs.h 1999/08/28 00:50:02 1.27 +++ nfs/nfsm_subs.h 2000/10/20 16:13:49 @@ -212,7 +212,7 @@ #define nfsm_loadattr(v, a) \ do { \ struct vnode *ttvp = (v); \ - if ((t1 = nfs_loadattrcache(&ttvp, &md, &dpos, (a))) != 0) { \ + if ((t1 = nfs_loadattrcache(&ttvp, &md, &dpos, (a), 0)) != 0) { \ error = t1; \ m_freem(mrep); \ goto nfsmout; \ @@ -226,7 +226,7 @@ nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED); \ if (((f) = fxdr_unsigned(int, *tl)) != 0) { \ if ((t1 = nfs_loadattrcache(&ttvp, &md, &dpos, \ - (struct vattr *)0)) != 0) { \ + (struct vattr *)0, 1)) != 0) { \ error = t1; \ (f) = 0; \ m_freem(mrep); \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 9:24: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 6A54737B4C5 for ; Fri, 20 Oct 2000 09:24:07 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e9KGO3B08039; Fri, 20 Oct 2000 09:24:03 -0700 (PDT) (envelope-from dillon) Date: Fri, 20 Oct 2000 09:24:03 -0700 (PDT) From: Matt Dillon Message-Id: <200010201624.e9KGO3B08039@earth.backplane.com> To: David Malone Cc: Vadim Belman , freebsd-hackers@FreeBSD.ORG Subject: Re: NFS/VM deadlock report and help request References: <20001020145043.B73760@lflat.vas.mobilix.dk> <20001020171810.A28345@walton.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Fri, Oct 20, 2000 at 02:50:43PM +0200, Vadim Belman wrote: : :> The kernel config I supply as an attachment. Kernel-mode stack :> trace for the thttpd process looks like this: : :I think we've seen a similar problem and have a work around for it. :You could try the following patch, though it might take more fiddling :to get it right. : :(The patch is by Ian Dowse, Matt Dillon had a quick look at it and said :it looked OK, we've been testing it for a bit here). : : David. Ah yes, that problem... if Ian's patch solves the problem for Vadim, I think you should go ahead and commit it. -Matt :Index: nfs/nfs.h :=================================================================== :RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfs.h,v :retrieving revision 1.53 :diff -u -r1.53 nfs.h :--- nfs/nfs.h 2000/01/13 20:18:25 1.53 :+++ nfs/nfs.h 2000/10/20 16:13:49 :@@ -616,7 +616,7 @@ : struct ucred *, struct mbuf **, struct mbuf **, : caddr_t *)); :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 9:34: 0 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 0AFDC37B4C5 for ; Fri, 20 Oct 2000 09:33:54 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Oct 2000 17:33:53 +0100 (BST) To: Vadim Belman Cc: freebsd-hackers@freebsd.org Subject: Re: NFS/VM deadlock report and help request In-Reply-To: Your message of "Fri, 20 Oct 2000 14:50:43 +0200." <20001020145043.B73760@lflat.vas.mobilix.dk> Date: Fri, 20 Oct 2000 17:33:53 +0100 From: Ian Dowse Message-ID: <200010201733.aa97121@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001020145043.B73760@lflat.vas.mobilix.dk>, Vadim Belman writes: > wmesg=0xc0233171 "vmopar", timo=0) at ../../kern/kern_synch.c:467 ... >#8 0xc01dd606 in vm_fault (map=0xdc3e7e80, vaddr=712876032, > fault_type=1 '\001', fault_flags=0) at ../../vm/vm_pager.h:130 If anyone is interested, here are a few further details from my mailbox. The patch David included appears to have solved this particular problem for us, but there is another similar problem lurking within the NFS/VM system. Ian -------------------------------------------- The problem seems to originate with NFS's postop_attr information that is returned with a read or write RPC. Within a vm_fault context, the code cannot deal with vnode_pager_setsize() shrinking a vnode. The workaround in the patch below stops the nfsm_postop_attr() macro from ever shrinking a vnode. If the new size in the postop_attr information is smaller, then it just sets the nfsnode n_attrstamp to 0 to stop the wrong size getting used in the future. This change only affects postop_attr attributes; the nfsm_loadattr() macro works as normal. The change is implemented by adding a new argument to nfs_loadattrcache() called 'dontshrink'. When this is non-zero, nfs_loadattrcache() will never reduce the vnode/nfsnode size; instead it zeros n_attrstamp. ----------------------------------------------- Hmm. We used this patch for a while - it stopped those particular vmopar hangs, but another kind of deadlock has emerged (which happens with or without the patch). It seems that vinvalbuf() locks the vnode's v_interlock before calling vm_object_page_remove(). vm_object_page_remove will then lock a page i.e. vinvalbuf() [Lock v_interlock] -> vm_object_page_remove() [Lock page] If another process concurrently vm_fault's on the same vnode then it locks the page, and finishes with a vput(vp). vput() locks the interlock, so it results in: vm_fault() [Lock page] -> vput() [Lock v_interlock] This is a simple lock-ordering deadlock. Since vm_fault can keep the page locked for a considerable amount of time with NFS, this deadlock can happen quite easily. I'm not sure what to suggest as a solution, but keeping the v_interlock locked across a tsleep seems wrong... Any ideas? Traces below. #12 0xc02140f0 in atkbd_isa_intr (unit=0) at ../../i386/isa/atkbd_isa.c:84 #13 0xc020eceb in wait () #14 0xc01e22d3 in _unlock_things (fs=0xca6f0ef0, dealloc=0) at ../../vm/vm_fault.c:148 #15 0xc01e2b73 in vm_fault (map=0xca6d2ac0, vaddr=134766592, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:745 #16 0xc0210252 in trap_pfault (frame=0xca6f0fbc, usermode=1, eva=134769544) at ../../i386/i386/trap.c:816 #17 0xc020fda2 in trap (frame={tf_es = 39, tf_ds = 39, tf_edi = -1077946880, tf_esi = 1, tf_ebp = -1077947052, tf_isp = -898691100, tf_ebx = -1077946872, tf_edx = 4, tf_ecx = -1077947772, tf_eax = 2, tf_trapno = 12, tf_err = 4, tf_eip = 134769544, tf_cs = 31, tf_eflags = 66050, tf_esp = -1077947172, tf_ss = 39}) at ../../i386/i386/trap.c:358 #18 0x8086b88 in ?? () (kgdb) proc 1042 (kgdb) bt #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0150b4d in tsleep (ident=0xc0598534, priority=4, wmesg=0xc024d22a "vmopar", timo=0) at ../../kern/kern_synch.c:443 #2 0xc01eaec6 in vm_page_sleep (m=0xc0598534, msg=0xc024d22a "vmopar", busy=0xc0598563 "") at ../../vm/vm_page.c:1052 #3 0xc01e9aff in vm_object_page_remove (object=0xca6bac1c, start=0, end=0, clean_only=1) at ../../vm/vm_object.c:1335 #4 0xc0172a6a in vinvalbuf (vp=0xca6bf700, flags=1, cred=0xc171ec80, p=0xca6e5a40, slpflag=256, slptimeo=0) at ../../kern/vfs_subr.c:671 #5 0xc019541c in nfs_vinvalbuf (vp=0xca6bf700, flags=1, cred=0xc171ec80, p=0xca6e5a40, intrflg=1) at ../../nfs/nfs_bio.c:978 #6 0xc01b6859 in nfs_open (ap=0xca6f3e2c) at ../../nfs/nfs_vnops.c:490 #7 0xc01796ae in vn_open (ndp=0xca6f3f00, fmode=1, cmode=1512) at vnode_if.h:163 #8 0xc01760d9 in open (p=0xca6e5a40, uap=0xca6f3f94) at ../../kern/vfs_syscalls.c:935 #9 0xc02108bf in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134725618, tf_esi = -1077946896, tf_ebp = -1077946944, tf_isp = -898678812, tf_ebx = -1077946956, tf_edx = -1077946588, tf_ecx = 134893176, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 672042756, tf_cs = 31, tf_eflags = 514, tf_esp = -1077949296, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #10 0xc01ff11c in Xint0x80_syscall () #11 0x8049d39 in ?? () ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 9:35:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 407F937B4CF for ; Fri, 20 Oct 2000 09:35:57 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id JAA03182; Fri, 20 Oct 2000 09:32:24 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpdAAATvaidg; Fri Oct 20 09:32:14 2000 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id JAA07149; Fri, 20 Oct 2000 09:35:36 -0700 (MST) From: Terry Lambert Message-Id: <200010201635.JAA07149@usr06.primenet.com> Subject: Re: burncd utility for atapi burners To: tomas@sdxnet.com (Tomas Hruz) Date: Fri, 20 Oct 2000 16:35:35 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <00102012234401.39055@srv.ba.sdxnet.com> from "Tomas Hruz" at Oct 20, 2000 11:27:09 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would like to communicate the proposed changes to the author but I did not > find his address. Could somebody provide his email to me? [ ... ] This is going to be a problem in getting your changes accepted: > +/*- > + * t.h. changes copyright (c) 2000 Tomas Hruz > + * All rights reserved. > + */ Since that includes the right to integrate and distribute. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 10:21: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id EDD2837B4C5 for ; Fri, 20 Oct 2000 10:21:06 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id BF6C0DC75; Fri, 20 Oct 2000 13:14:14 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id A4128DC74 for ; Fri, 20 Oct 2000 13:14:14 -0400 (EDT) Date: Fri, 20 Oct 2000 13:14:14 -0400 (EDT) From: David Miller To: freebsd-hackers@freebsd.org Subject: Boot off USB SanDisk? 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 SanDisk makes a IDE-like flash card one could plug into a $30 USB flashcard reader. Would FreeBSD have any idea how to boot off such a beast? Alternatively, anyone know of an ISA/PCI adapter with enough bios on it to boot off a similar flash? Thanks, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 10:25:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 47DFF37B4CF for ; Fri, 20 Oct 2000 10:25:08 -0700 (PDT) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id LAA68006; Fri, 20 Oct 2000 11:25:07 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id LAA21851; Fri, 20 Oct 2000 11:25:07 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Fri, 20 Oct 2000 11:25:07 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: David Miller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Boot off USB SanDisk? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Oct 2000, David Miller wrote: > Would FreeBSD have any idea how to boot off such a beast? Alternatively, > anyone know of an ISA/PCI adapter with enough bios on it to boot off a > similar flash? Put it in millenium disk-on-chip, 60 MB (soon) in the 32-pin DIP slot found on most mainboards nowadays (yes, they have moved from surface mount back to dip!) I'm booting to single-user in 3 seconds using these things. The IDE delays are high, even for Flash IDE, so going for the socket is a good thing. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 10:27:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 5394C37B479 for ; Fri, 20 Oct 2000 10:27:29 -0700 (PDT) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id LAA68031; Fri, 20 Oct 2000 11:27:29 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id LAA21878; Fri, 20 Oct 2000 11:27:28 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Fri, 20 Oct 2000 11:27:28 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: David Miller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Boot off USB SanDisk? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Oct 2000, Ronald G Minnich wrote: > I'm booting to single-user in 3 seconds using these things. The IDE delays > are high, even for Flash IDE, so going for the socket is a good thing. should have said: single user Linux. FreeBSD did not work, I think because the bootup stuff in the kernel wants to as the BIOS "a few questions", and there's not bios there. If anyone wants to work on a non-bios-querying boot-time parameter interface for freebsd (like the one linux has) let me know. I would really like to boot freebsd out of flash. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 11:12:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id BF9A537B479; Fri, 20 Oct 2000 11:12:06 -0700 (PDT) Received: from tellurian.com (unverified [208.59.162.242]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Fri, 20 Oct 2000 14:12:16 -0400 Message-ID: <39F08B52.2E598CC5@tellurian.com> Date: Fri, 20 Oct 2000 14:13:38 -0400 From: Marko Ruban X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,uk MIME-Version: 1.0 To: FreeBSD questions Cc: freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem References: <39EF5505.7B7C2BFD@tellurian.com> <04c701c03a0f$716181f0$6d0a280a@speedera.com> <39EF8AAD.94739B2B@tellurian.com> <06ba01c03a2e$f66625d0$6d0a280a@speedera.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried replicating my windows routing table in freebsd. Only one entry didn't work... (guess) "route add default 10.17.56.xx" I'm cursed ! read below .... > > > > Goal -- to add cable modem as the default gateway to internet. > > > > Symptom -- "add net default: gateway 10.17.56.XXX: Network is > > > > unreachable" > > > > Problem -- I think modem gateway cannot be added because it's on a > > > > different subnet then my NICs. > > > > Attempted -- aliasing ed0 to modem subnet.... all 10.17.56 IPs seem to > > > > be occupied. > > > > > > It does sound like routing- > > > A gateway, by definition, has to be on the same network as your NIC. > > > I'm guessing your cable modem is in bridging mode? (vs routing mode) > > > > What would that mean in terms of my config changes ?? > So is the cable modem in this computer, or is it some standalone device? The cable modem is an external device. It is connected to one of my two NICs. The other NIC has been connected to a small LAN for a while (which worked perfect with dialup PPP and NAT). And it is also connected to the TV cable and a phone line. The uplink is handled automatically by the modem. > > > So it's presenting itself as some IP right? > > > And you just have to use this IP as the default gateway for all your > other > > > machines- > > > > > What is the subnet masking in place here? > > > > The modem works fine on my windows machine, and I looked up the > configuration > > there (winipcfg). > > Windows sets 10.17.56.XXX as the default gateway (and DHCP server), and > assigns > > 208.59.162.XXX (subnet 255.255.255.0) to me. DNS server is set to > 207.172.3.9. > > > > Seems like should be no difficulty setting up unix in the same way... but > unix > > does like 10.17.56.XXX as gateway (because supposedly network is > unreachable). > > > > So that's the story... any suggestions? > > Ok, so the machine is being given a 208.59.162.xxx IP address (via DHCP), > and a default gateway of 10.17.56.xx. > > Ok I think I know what's going on- > > Try manually adding the default route, but specify the interface that you > want to use. > It's something like: > > "route add default 10.17.56.xx netmask 255.255.255.0 interface ed0" "route add default 10.17.56.xx -netmask 255.255.255.0 -interface ed0" did not work, probably because 10.17.56.xx was specifying a gateway for the network 0.0.0.0 and ed0 was trying to be a gateway as well. I can however "route add default -interface ed0" which is actually the closest I've gotten to it working (modem dials out when I ping 10.17.56.1). "route add default 10.17.56.xx" would not work under any circumstances :( tells me "Network is unreachable". I just wonder how windows has no problem adding it as gateway. > I think that because the machine doesnt have an interface on the 10.x.x.x > network, it doesn't know how to get to the 10.x.x.0 network. > > I think you alternately could add a static route that looks like this: > > "route add 10.0.0.0 208.59.162.xx" When route to 10.0.0.0 is added, outgoing packets are corrupted (checked with ethereal). I.E. the header of the packet has 4 bytes inserted between the source and destination MACs. Those 4 bytes always seem to be part of the destination MAC itself. Following from another reply..... >>>>>>>>>>>>>>>>>>>>>> >> > > defaultrouter="10.17.56.12" #<-- fails with symptom previously described >> > >> > DHCP will normally configure the default route for you -- try setting >> > this to NO. >> >> Tried setting to NO... DHCP doesn't seem to add a default route, so in my case it >> makes no difference really. >> Should it add default route? > >Normally, yes. You sort of need default route and netmask in order to >make things work. This should happen with the stock dhclient.conf >(which is empty). You could try to run dhclient by hand, something >like: > > # killall dhclient > # dhclient -dD ed0 > >Or whatever your interface is. Terminate it with Ctrl+C. You should >get a bunch of files in /tmp, containing values received from the >server. You may also get some interesting error messages. Tried "dhclient -d -D ed0".... no files are written to /tmp dir. Do you think it could be a problem with my dhclient ? I tried using wide-dhcp client earlier, with even less success. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 11:44:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 150F537B479; Fri, 20 Oct 2000 11:44:27 -0700 (PDT) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id MAA43767; Fri, 20 Oct 2000 12:44:19 -0600 (MDT) Date: Fri, 20 Oct 2000 12:44:19 -0600 (MDT) From: Nick Rogness To: Marko Ruban Cc: FreeBSD questions , freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem In-Reply-To: <39F08B52.2E598CC5@tellurian.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 Fri, 20 Oct 2000, Marko Ruban wrote: > I tried replicating my windows routing table in freebsd. > Only one entry didn't work... (guess) > "route add default 10.17.56.xx" > > I'm cursed ! My guess guess would be your DHCP client is not working right. Is it suppose to be using DHCP? Is it really something else like PPPoE? You see, the problem is not that the network is unreachable. It is that the default network is not DIRECTLY reachable. This is a violation of basic routing principles...although many devices work with that setup (Windows,Cisco,etc). FreeBSD does not allow you to add a default route to a network that is not directly connected. Why don't you dump your windows routing table `route -print` to the list and we could put together a routing table for you or see what is acutally going on. > read below .... > > > > > > Goal -- to add cable modem as the default gateway to internet. > > > > > Symptom -- "add net default: gateway 10.17.56.XXX: Network is > > > > > unreachable" > > > > > Problem -- I think modem gateway cannot be added because it's on a > > > > > different subnet then my NICs. > > > > > Attempted -- aliasing ed0 to modem subnet.... all 10.17.56 IPs seem to > > > > > be occupied. > > > > > > > > It does sound like routing- > > > > A gateway, by definition, has to be on the same network as your NIC. > > > > I'm guessing your cable modem is in bridging mode? (vs routing mode) > > > > > > What would that mean in terms of my config changes ?? > > > So is the cable modem in this computer, or is it some standalone device? > > The cable modem is an external device. It is connected to one of my two NICs. > The other NIC has been connected to a small LAN for a while (which worked > perfect with dialup PPP and NAT). And it is also connected to the TV cable and > a phone line. The uplink is handled automatically by the modem. > > > > > So it's presenting itself as some IP right? > > > > And you just have to use this IP as the default gateway for all your > > other > > > > machines- > > > > > > > What is the subnet masking in place here? > > > > > > The modem works fine on my windows machine, and I looked up the > > configuration > > > there (winipcfg). > > > Windows sets 10.17.56.XXX as the default gateway (and DHCP server), and > > assigns > > > 208.59.162.XXX (subnet 255.255.255.0) to me. DNS server is set to > > 207.172.3.9. > > > > > > Seems like should be no difficulty setting up unix in the same way... but > > unix > > > does like 10.17.56.XXX as gateway (because supposedly network is > > unreachable). > > > > > > So that's the story... any suggestions? > > > > Ok, so the machine is being given a 208.59.162.xxx IP address (via DHCP), > > and a default gateway of 10.17.56.xx. > > > > Ok I think I know what's going on- > > > > Try manually adding the default route, but specify the interface that you > > want to use. > > It's something like: > > > > "route add default 10.17.56.xx netmask 255.255.255.0 interface ed0" > > "route add default 10.17.56.xx -netmask 255.255.255.0 -interface ed0" did not > work, probably because 10.17.56.xx was specifying a gateway for the network > 0.0.0.0 and ed0 was trying to be a gateway as well. I can however "route add > default -interface ed0" which is actually the closest I've gotten to it working > (modem dials out when I ping 10.17.56.1). > > "route add default 10.17.56.xx" would not work under any circumstances :( > tells me "Network is unreachable". I just wonder how windows has no problem > adding it as gateway. > > > I think that because the machine doesnt have an interface on the 10.x.x.x > > network, it doesn't know how to get to the 10.x.x.0 network. > > > > I think you alternately could add a static route that looks like this: > > > > "route add 10.0.0.0 208.59.162.xx" > > When route to 10.0.0.0 is added, outgoing packets are corrupted (checked with > ethereal). I.E. the header of the packet has 4 bytes inserted between the > source and destination MACs. Those 4 bytes always seem to be part of the > destination MAC itself. > > > Following from another reply..... > >>>>>>>>>>>>>>>>>>>>>> > >> > > defaultrouter="10.17.56.12" #<-- fails with symptom previously > described > >> > > >> > DHCP will normally configure the default route for you -- try setting > >> > this to NO. > >> > >> Tried setting to NO... DHCP doesn't seem to add a default route, so in my > case it > >> makes no difference really. > >> Should it add default route? > > > >Normally, yes. You sort of need default route and netmask in order to > >make things work. This should happen with the stock dhclient.conf > >(which is empty). You could try to run dhclient by hand, something > >like: > > > > # killall dhclient > > # dhclient -dD ed0 > > > >Or whatever your interface is. Terminate it with Ctrl+C. You should > >get a bunch of files in /tmp, containing values received from the > >server. You may also get some interesting error messages. > > Tried "dhclient -d -D ed0".... no files are written to /tmp dir. > Do you think it could be a problem with my dhclient ? > I tried using wide-dhcp client earlier, with even less success. > > Marko > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 12:16:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id E717C37B4C5; Fri, 20 Oct 2000 12:16:02 -0700 (PDT) Received: from tellurian.com (unverified [208.59.162.242]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Fri, 20 Oct 2000 15:16:13 -0400 Message-ID: <39F09A58.5B2711BD@tellurian.com> Date: Fri, 20 Oct 2000 15:17:44 -0400 From: Marko Ruban X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,uk MIME-Version: 1.0 To: Nick Rogness Cc: FreeBSD questions , freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem References: Content-Type: text/html; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG  
Nick Rogness wrote:
On Fri, 20 Oct 2000, Marko Ruban wrote:

> I tried replicating my windows routing table in freebsd.
> Only one entry didn't work... (guess)
> "route add default 10.17.56.xx"
>
> I'm cursed !

        My guess guess would be your DHCP client is not working right.
        Is it suppose to be using DHCP?  Is it really something else like
        PPPoE?

It definitely uses DHCP, because I update the setup with "winipcfg" whenever I switch the modem over to windows machine.
Also ethereal (for windows) shows DHCP packets being exchanged.
        You see, the problem is not that the network is unreachable.  It
        is that the default network is not DIRECTLY reachable.  This is a
        violation of basic routing principles...although many devices work
        with that setup (Windows,Cisco,etc).  FreeBSD does not allow you
        to add a default route to a network that is not directly
        connected.
If windows can do it, freebsd probably can too, even if it takes a custom program  ;)
        Why don't you dump your windows routing table `route -print` to
        the list and we could put together a routing table for you or see
        what is acutally going on.
NOTE: table below best viewed in proportional font....
('route print' and 'netstat -r' seem to yield identical results) 

C:\WINDOWS>netstat -r

Route Table

Active Routes:

  Network Address         
Netmask  Gateway Address       
Interface  Metric

          0.0.0.0         
0.0.0.0      10.17.56.12   208.59.162.242      
1

        127.0.0.0       
255.0.0.0        127.0.0.1       
127.0.0.1       1

     208.59.162.0    255.255.255.0  
208.59.162.242   208.59.162.242      
1

   208.59.162.242  255.255.255.255       
127.0.0.1        127.0.0.1      
1

   208.59.162.255  255.255.255.255   208.59.162.242  
208.59.162.242       1

        224.0.0.0       
224.0.0.0   208.59.162.242   208.59.162.242      
1

  255.255.255.255  255.255.255.255   208.59.162.242  
208.59.162.242       1

I also edited (a copy of) the dhclient-script to dump output of commands to /tmp instead of /dev/null maybe I'll see something interesting there.

*** old discussion follows

> > > > > Goal -- to add cable modem as the default gateway to internet.
> > > > > Symptom -- "add net default: gateway 10.17.56.XXX: Network is
> > > > > unreachable"
> > > > > Problem -- I think modem gateway cannot be added because it's on a
> > > > > different subnet then my NICs.
> > > > > Attempted -- aliasing ed0 to modem subnet.... all 10.17.56 IPs seem to
> > > > > be occupied.
> > > >
> > > > It does sound like routing-
> > > > A gateway, by definition, has to be on the same network as your NIC.
> > > > I'm guessing your cable modem is in bridging mode? (vs routing mode)
> > >
> > > What would that mean in terms of my config changes ??
>
> > So is the cable modem in this computer, or is it some standalone device?
>
> The cable modem is an external device.  It is connected to one of my two NICs.
> The other NIC has been connected to a small LAN for a while (which worked
> perfect with dialup PPP and NAT).  And it is also connected to the TV cable and
> a phone line.  The uplink is handled automatically by the modem.
>
> > > > So it's presenting itself as some IP right?
> > > > And you just have to use this IP as the default gateway for all your
> > other
> > > > machines-
> > >
> > > > What is the subnet masking in place here?
> > >
> > > The modem works fine on my windows machine, and I looked up the
> > configuration
> > > there (winipcfg).
> > > Windows sets 10.17.56.XXX as the default gateway (and DHCP server), and
> > assigns
> > > 208.59.162.XXX (subnet 255.255.255.0) to me.  DNS server is set to
> > 207.172.3.9.
> > >
> > > Seems like should be no difficulty setting up unix in the same way... but
> > unix
> > > does like 10.17.56.XXX as gateway (because supposedly network is
> > unreachable).
> > >
> > > So that's the story... any suggestions?
> >
> > Ok, so the machine is being given a 208.59.162.xxx IP address (via DHCP),
> > and a default gateway of 10.17.56.xx.
> >
> > Ok I think I know what's going on-
> >
> > Try manually adding the default route, but specify the interface that you
> > want to use.
> > It's something like:
> >
> > "route add default 10.17.56.xx netmask 255.255.255.0 interface ed0"
>
> "route add default 10.17.56.xx -netmask 255.255.255.0 -interface ed0"  did not
> work, probably because 10.17.56.xx was specifying a gateway for the network
> 0.0.0.0 and ed0 was trying to be a gateway as well.  I can however "route add
> default -interface ed0" which is actually the closest I've gotten to it working
> (modem dials out when I ping 10.17.56.1).
>
> "route add default 10.17.56.xx" would not work under any circumstances :(
> tells me "Network is unreachable".  I just wonder how windows has no problem
> adding it as gateway.
>
> > I think that because the machine doesnt have an interface on the 10.x.x.x
> > network, it doesn't know how to get to the 10.x.x.0 network.
> >
> > I think you alternately could add a static route that looks like this:
> >
> > "route add 10.0.0.0 208.59.162.xx"
>
> When route to 10.0.0.0 is added, outgoing packets are corrupted (checked with
> ethereal).  I.E. the header of the packet has 4 bytes inserted between the
> source and destination MACs.  Those 4 bytes always seem to be part of the
> destination MAC itself.
>
>
> Following from another reply.....
> >>>>>>>>>>>>>>>>>>>>>>
> >> > > defaultrouter="10.17.56.12"   #<-- fails with symptom previously
> described
> >> >
> >> > DHCP will normally configure the default route for you -- try setting
> >> > this to NO.
> >>
> >> Tried setting to NO... DHCP doesn't seem to add a default route, so in my
> case it
> >> makes no difference really.
> >> Should it add default route?
> >
> >Normally, yes.  You sort of need default route and netmask in order to
> >make things work.  This should happen with the stock dhclient.conf
> >(which is empty).  You could try to run dhclient by hand, something
> >like:
> >
> > # killall dhclient
> > # dhclient -dD ed0
> >
> >Or whatever your interface is.  Terminate it with Ctrl+C. You should
> >get a bunch of files in /tmp, containing values received from the
> >server.  You may also get some interesting error messages.
>
> Tried "dhclient -d -D ed0".... no files are written to /tmp dir.
> Do you think it could be a problem with my dhclient ?
> I tried using wide-dhcp client earlier, with even less success.
>
> Marko
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>

Nick Rogness
- Drive defensively.  Buy a tank.

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 12:22:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A0B537B4D7; Fri, 20 Oct 2000 12:22:51 -0700 (PDT) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id NAA64989; Fri, 20 Oct 2000 13:22:48 -0600 (MDT) Date: Fri, 20 Oct 2000 13:22:48 -0600 (MDT) From: Nick Rogness To: Marko Ruban Cc: FreeBSD questions , freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Oct 2000, Nick Rogness wrote: Made an error in my previous statement, clarification below: > On Fri, 20 Oct 2000, Marko Ruban wrote: > > > I tried replicating my windows routing table in freebsd. > > Only one entry didn't work... (guess) > > "route add default 10.17.56.xx" > > > > I'm cursed ! > > My guess guess would be your DHCP client is not working right. > Is it suppose to be using DHCP? Is it really something else like > PPPoE? > > You see, the problem is not that the network is unreachable. It > is that the default network is not DIRECTLY reachable. This is a > violation of basic routing principles...although many devices work This is not neccessarily true. There are some instances where this is perfectly legal and are out-of-scope for this mail. However, they are usually handled by dynamic routing protocols and/or other equipment/software interaction. This argument has come up before on this list and the concept has went back and forth on why's and why not's. > with that setup (Windows,Cisco,etc). FreeBSD does not allow you > to add a default route to a network that is not directly > connected. > > Why don't you dump your windows routing table `route -print` to > the list and we could put together a routing table for you or see > what is acutally going on. > Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 12:38:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw3.netvision.net.il (mailgw3.netvision.net.il [194.90.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 00EFD37B4C5 for ; Fri, 20 Oct 2000 12:38:56 -0700 (PDT) Received: from phpStop.com (ras3-p90.hfa.netvision.net.il [62.0.147.90]) by mailgw3.netvision.net.il (8.9.3/8.9.3) with ESMTP id VAA26651; Fri, 20 Oct 2000 21:38:02 +0200 (IST) Message-ID: <39F09EF1.E2AB0438@phpStop.com> Date: Fri, 20 Oct 2000 21:37:21 +0200 From: "phpStop.com" Organization: phpStop.com X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: FreeBSD vs. Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, If this is not the right place to ask such questions, please forgive me and I'll appreciate it if you can forward me to the right place. Is there any detailed information or technical sheet about the difference between FreeBSD and Linux? Also, what are the advantages over the disadvantages of each of the mentioned OS's? If someone could point me to a technical page, also, that indicates FreeBSD's and Linux's performance when running Apache, PHP and MySQL? We need this information in order to determine which of these two OS to choose from to drive our website. Thank you in advance for your help. -- Regards, phpStop.com http://www.phpstop.com/ stop here. start everywhere. mailto:info@phpstop.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 14:34:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 122E237B479; Fri, 20 Oct 2000 14:34:01 -0700 (PDT) Received: from dppl.com (unverified [216.182.27.51]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Fri, 20 Oct 2000 17:34:12 -0400 Message-ID: <39F0B9A6.56FFE589@dppl.com> Date: Fri, 20 Oct 2000 17:31:18 -0400 From: Marko Ruban X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Nick Rogness Cc: Marko Ruban , FreeBSD questions , freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG New issue seems to be at hand... I set the alias for the interface to be the gateway IP (10.17.56.12), and then I was able to add that as my default gateway. Not sure why aliasing wouldn't work with 10.17.56.11 or some other IP in that subnet. I tried to ping the DNS server after that, and watched hundreds of corrupt packets get sent out with no replies. So my new question is, which part of the system actually builds the packets ? Any way to debug or log that process ? Here's an example taken from ethereal output.... (view with proportional font) --------------------------------------------------------- Frame 6 (102 on wire, 102 captured) Arrival Time: Oct 20, 2000 16:42:38.2715 Time delta from previous packet: 0.000071 seconds Frame Number: 6 Packet Length: 102 bytes Capture Length: 102 bytes Ethernet II Destination: 02:00:00:00:52:54 (02:00:00:00:52:54) Source: 05:f4:21:3f:52:54 (05:f4:21:3f:52:54) Type: Unknown (0x05f4) Data (88 bytes) 0 0200 0000 5254 05f4 213f 5254 05f4 213f ....RT..!?RT..!? 10 0800 4500 0054 13fa 0000 fa01 97dc 0a11 ..E..T.......... 20 380c cfac 0309 0800 c1f0 6101 0000 3eae 8.........a...>. 30 f039 b722 0400 0809 0a0b 0c0d 0e0f 1011 .9."............ 40 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 .............. ! 50 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 "#$%&'()*+,-./01 60 3233 3435 3637 234567 --------------------------------------------------------- Why I think this packet is malformed..... First of all, protocol type Unknown (0x05f4) looks definitely bad. Secondly, protocol type looks like part of my NICs MAC address (52:54:05:f4:21:3f according to ifconfig, which translates into hex: 0x5254 05f4 213f). Thirdly, source address decoded by ethereal (and probably by any other packet processor) is wrong (first two bytes are carried over to the other side). Now, keeping all that in mind, lets do a pattern match on the REAL MAC address in hex dump of the packet. HEY, the source address actually starts four bytes later than it should, thus shifting the TRUE protocol type (0x0800 = IP) as well. First six bytes are the destination MAC, then come the EVIL 4 bytes, followed by 6 bytes of source MAC. I don't know what's going on, but looks pretty bad, yet simple on the hex level :) Any ideas ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 14:41:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from trill.hh.se (trill.hh.se [194.47.5.10]) by hub.freebsd.org (Postfix) with ESMTP id 3225637B4CF; Fri, 20 Oct 2000 14:41:14 -0700 (PDT) Received: from gs177.gsten.hh.se (chip@L22-212.gsten.hh.se [194.47.16.177]) by trill.hh.se (8.9.3/8.9.3) with ESMTP id XAA25660; Fri, 20 Oct 2000 23:41:09 +0200 (MET DST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <39F09A58.5B2711BD@tellurian.com> Date: Fri, 20 Oct 2000 23:41:10 +0200 (CEST) From: Joel Bjork To: Marko Ruban Subject: Re: Routing issue with cable modem Cc: freebsd-hackers@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG, FreeBSD questions , Nick Rogness Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That was some really really nasty HTML there, I think you might want to send that again as plaintext. ---------------------------------- E-Mail: Joel Bjork Date: 20-Oct-00 Time: 23:41:10 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 15:37:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C5CB37B4D7; Fri, 20 Oct 2000 15:37:45 -0700 (PDT) Received: from dppl.com (unverified [216.182.27.51]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Fri, 20 Oct 2000 18:37:57 -0400 Message-ID: <39F0C896.30C53A1D@dppl.com> Date: Fri, 20 Oct 2000 18:35:02 -0400 From: Marko Ruban X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel said HTML was badly formatted, so I'm resubmitting in plain text. Thanks :) New issue seems to be at hand... I set the alias for the interface to be the gateway IP (10.17.56.12), and then I was able to add that as my default gateway. Not sure why aliasing wouldn't work with 10.17.56.11 or some other IP in that subnet. I tried to ping the DNS server after that, and watched hundreds of corrupt packets get sent out with no replies. So my new question is, which part of the system actually builds the packets ? Any way to debug or log that process ? Here's an example taken from ethereal output.... (view with proportional font) --------------------------------------------------------- Frame 6 (102 on wire, 102 captured) Arrival Time: Oct 20, 2000 16:42:38.2715 Time delta from previous packet: 0.000071 seconds Frame Number: 6 Packet Length: 102 bytes Capture Length: 102 bytes Ethernet II Destination: 02:00:00:00:52:54 (02:00:00:00:52:54) Source: 05:f4:21:3f:52:54 (05:f4:21:3f:52:54) Type: Unknown (0x05f4) Data (88 bytes) 0 0200 0000 5254 05f4 213f 5254 05f4 213f ....RT..!?RT..!? 10 0800 4500 0054 13fa 0000 fa01 97dc 0a11 ..E..T.......... 20 380c cfac 0309 0800 c1f0 6101 0000 3eae 8.........a...>. 30 f039 b722 0400 0809 0a0b 0c0d 0e0f 1011 .9."............ 40 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 .............. ! 50 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 "#$%&'()*+,-./01 60 3233 3435 3637 234567 --------------------------------------------------------- Why I think this packet is malformed..... First of all, protocol type Unknown (0x05f4) looks definitely bad. Secondly, protocol type looks like part of my NICs MAC address (52:54:05:f4:21:3f according to ifconfig, which translates into hex: 0x5254 05f4 213f). Thirdly, source address decoded by ethereal (and probably by any other packet processor) is wrong (first two bytes are carried over to the other side). Now, keeping all that in mind, lets do a pattern match on the REAL MAC address in hex dump of the packet. HEY, the source address actually starts four bytes later than it should, thus shifting the TRUE protocol type (0x0800 = IP) as well. First six bytes are the destination MAC, then come the EVIL 4 bytes, followed by 6 bytes of source MAC. I don't know what's going on, but looks pretty bad, yet simple on the hex level :) Any ideas ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 16:30: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hmp.net (core.hmp.net [207.226.50.8]) by hub.freebsd.org (Postfix) with ESMTP id 7915937B479; Fri, 20 Oct 2000 16:29:59 -0700 (PDT) Received: from your email address (port11.fairfax.hmp.net [207.226.50.31]) by hmp.net (Postfix) with SMTP id B1D465087D; Fri, 20 Oct 2000 18:22:06 -0400 (EDT) Date: 10/20/2000 7:01:14 PM Pacific Daylight Time From: Subscriptions@SkiBumNews.com Reply-To: Subscriptions@SkiBumNews.com To: Subscriptions@SkiBumNews.com Subject: Ski Bum News Subscription Message-Id: <20001020222206.B1D465087D@hmp.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am very sorry to bother you but our mailing list at the Ski Bum News was destroyed. If you were receiving a FREE SUBSCRIPTION to http://www.SkiBumNews.com or WOULD like to please respond with Subscription in the subject box. If you were not receiving a subscription or do NOT want one do NOTHING, we will not contact you again regarding this matter. Please let me apologize again for bothering you, there was nothing else I could think of to do. Sincerely, The Editor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 18:34:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from downstairs.conyers.net (cr419806-a.wlfdle1.on.wave.home.com [24.42.55.97]) by hub.freebsd.org (Postfix) with ESMTP id 6593F37B4D7; Fri, 20 Oct 2000 18:34:44 -0700 (PDT) Received: from home.com (localhost [127.0.0.1]) by downstairs.conyers.net (8.9.3/8.9.3) with ESMTP id VAA75388; Fri, 20 Oct 2000 21:34:41 -0400 (EDT) (envelope-from pnmurphy@home.com) Message-ID: <39F0F2AB.C50E0E8D@home.com> Date: Fri, 20 Oct 2000 21:34:35 -0400 From: Paul Murphy X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Marko Ruban Cc: FreeBSD questions , freebsd-hackers@FreeBSD.ORG Subject: Re: Routing issue with cable modem References: <39EF5505.7B7C2BFD@tellurian.com> <04c701c03a0f$716181f0$6d0a280a@speedera.com> <39EF8AAD.94739B2B@tellurian.com> <06ba01c03a2e$f66625d0$6d0a280a@speedera.com> <39F08B52.2E598CC5@tellurian.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marko Ruban wrote: > > I tried replicating my windows routing table in freebsd. > Only one entry didn't work... (guess) > "route add default 10.17.56.xx" > > I'm cursed ! > read below .... > > > > > > Goal -- to add cable modem as the default gateway to internet. > > > > > Symptom -- "add net default: gateway 10.17.56.XXX: Network is > > > > > unreachable" > > > > > Problem -- I think modem gateway cannot be added because it's on a > > > > > different subnet then my NICs. > > > > > Attempted -- aliasing ed0 to modem subnet.... all 10.17.56 IPs seem to > > > > > be occupied. > > > > > > > > It does sound like routing- > > > > A gateway, by definition, has to be on the same network as your NIC. > > > > I'm guessing your cable modem is in bridging mode? (vs routing mode) > > > > > > What would that mean in terms of my config changes ?? > > > So is the cable modem in this computer, or is it some standalone device? > > The cable modem is an external device. It is connected to one of my two NICs. > The other NIC has been connected to a small LAN for a while (which worked > perfect with dialup PPP and NAT). And it is also connected to the TV cable and > a phone line. The uplink is handled automatically by the modem. > > > > > So it's presenting itself as some IP right? > > > > And you just have to use this IP as the default gateway for all your > > other > > > > machines- > > > > > > > What is the subnet masking in place here? > > > > > > The modem works fine on my windows machine, and I looked up the > > configuration > > > there (winipcfg). > > > Windows sets 10.17.56.XXX as the default gateway (and DHCP server), and > > assigns > > > 208.59.162.XXX (subnet 255.255.255.0) to me. DNS server is set to > > 207.172.3.9. > > > > > > Seems like should be no difficulty setting up unix in the same way... but > > unix > > > does like 10.17.56.XXX as gateway (because supposedly network is > > unreachable). > > > > > > So that's the story... any suggestions? > > > > Ok, so the machine is being given a 208.59.162.xxx IP address (via DHCP), > > and a default gateway of 10.17.56.xx. > > > > Ok I think I know what's going on- > > > > Try manually adding the default route, but specify the interface that you > > want to use. > > It's something like: > > > > "route add default 10.17.56.xx netmask 255.255.255.0 interface ed0" > > "route add default 10.17.56.xx -netmask 255.255.255.0 -interface ed0" did not > work, probably because 10.17.56.xx was specifying a gateway for the network > 0.0.0.0 and ed0 was trying to be a gateway as well. I can however "route add > default -interface ed0" which is actually the closest I've gotten to it working > (modem dials out when I ping 10.17.56.1). > > "route add default 10.17.56.xx" would not work under any circumstances :( > tells me "Network is unreachable". I just wonder how windows has no problem > adding it as gateway. > > > I think that because the machine doesnt have an interface on the 10.x.x.x > > network, it doesn't know how to get to the 10.x.x.0 network. > > > > I think you alternately could add a static route that looks like this: > > > > "route add 10.0.0.0 208.59.162.xx" > > When route to 10.0.0.0 is added, outgoing packets are corrupted (checked with > ethereal). I.E. the header of the packet has 4 bytes inserted between the > source and destination MACs. Those 4 bytes always seem to be part of the > destination MAC itself. > > Following from another reply..... > >>>>>>>>>>>>>>>>>>>>>> > >> > > defaultrouter="10.17.56.12" #<-- fails with symptom previously > described > >> > > >> > DHCP will normally configure the default route for you -- try setting > >> > this to NO. > >> > >> Tried setting to NO... DHCP doesn't seem to add a default route, so in my > case it > >> makes no difference really. > >> Should it add default route? > > > >Normally, yes. You sort of need default route and netmask in order to > >make things work. This should happen with the stock dhclient.conf > >(which is empty). You could try to run dhclient by hand, something > >like: > > > > # killall dhclient > > # dhclient -dD ed0 > > > >Or whatever your interface is. Terminate it with Ctrl+C. You should > >get a bunch of files in /tmp, containing values received from the > >server. You may also get some interesting error messages. > > Tried "dhclient -d -D ed0".... no files are written to /tmp dir. > Do you think it could be a problem with my dhclient ? > I tried using wide-dhcp client earlier, with even less success. > > Marko > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message I could never manually config my cable modem for @home; it works if you let DHCP config it. [ifconfig_ep0="DHCP" <- in rc.conf] -- P. Murphy Home: Lat 43.5584 Long -79.6502 Work: Lat 43.4277 Long -79.7077 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 19:15:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 6F89B37B479; Fri, 20 Oct 2000 19:15:23 -0700 (PDT) Received: from takhus-home.ashlandfn.org (AFN-Dyn-2084621972.pc.ashlandfiber.net [208.46.219.72]) by ego.mind.net (8.9.3/8.9.3) with ESMTP id TAA03986; Fri, 20 Oct 2000 19:15:12 -0700 Received: from localhost (fleisher@localhost) by takhus-home.ashlandfn.org (8.11.1/8.11.1) with ESMTP id e9L2FBL00314; Fri, 20 Oct 2000 19:15:11 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus-home.ashlandfn.org: fleisher owned process doing -bs Date: Fri, 20 Oct 2000 19:15:11 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus-home.ashlandfn.org To: Marko Ruban Cc: FreeBSD questions , freebsd-hackers@FreeBSD.ORG Subject: Re: Routing issue with cable modem In-Reply-To: <39F0B9A6.56FFE589@dppl.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 Hello, Have you perhaps updated to a new kernel since you installed ethereal? I seem to recall seing similiar situations to this when some data structures changed sizes. Is "/usr/sbin/tcpdump -e" showing this same MAC address corruption you describe? If not, I would recommend rebuilding ethereal. TOny. On Fri, 20 Oct 2000, Marko Ruban wrote: > New issue seems to be at hand... > > I set the alias for the interface to be the gateway IP (10.17.56.12), and then I was > able to add that as my default gateway. Not sure why aliasing wouldn't work with > 10.17.56.11 or some other IP in that subnet. > > I tried to ping the DNS server after that, and watched hundreds of corrupt packets > get sent out with no replies. > So my new question is, which part of the system actually builds the packets ? Any > way to debug or log that process ? > > Here's an example taken from ethereal output.... (view with proportional font) > --------------------------------------------------------- > Frame 6 (102 on wire, 102 captured) > Arrival Time: Oct 20, 2000 16:42:38.2715 > Time delta from previous packet: 0.000071 seconds > Frame Number: 6 > Packet Length: 102 bytes > Capture Length: 102 bytes > Ethernet II > Destination: 02:00:00:00:52:54 (02:00:00:00:52:54) > Source: 05:f4:21:3f:52:54 (05:f4:21:3f:52:54) > Type: Unknown (0x05f4) > Data (88 bytes) > > 0 0200 0000 5254 05f4 213f 5254 05f4 213f ....RT..!?RT..!? > 10 0800 4500 0054 13fa 0000 fa01 97dc 0a11 ..E..T.......... > 20 380c cfac 0309 0800 c1f0 6101 0000 3eae 8.........a...>. > 30 f039 b722 0400 0809 0a0b 0c0d 0e0f 1011 .9."............ > 40 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 .............. ! > 50 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 "#$%&'()*+,-./01 > 60 3233 3435 3637 234567 > --------------------------------------------------------- > > Why I think this packet is malformed..... > > First of all, protocol type Unknown (0x05f4) looks definitely bad. > Secondly, protocol type looks like part of my NICs MAC address (52:54:05:f4:21:3f > according to ifconfig, which translates into hex: 0x5254 05f4 213f). > Thirdly, source address decoded by ethereal (and probably by any other packet > processor) is wrong (first two bytes are carried over to the other side). > > Now, keeping all that in mind, lets do a pattern match on the REAL MAC address in > hex dump of the packet. > HEY, the source address actually starts four bytes later than it should, thus > shifting the TRUE protocol type (0x0800 = IP) as well. > > First six bytes are the destination MAC, then come the EVIL 4 bytes, followed by 6 > bytes of source MAC. > I don't know what's going on, but looks pretty bad, yet simple on the hex level :) > > Any ideas ? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 20 19:54:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r35.bfm.org [216.127.220.131]) by hub.freebsd.org (Postfix) with ESMTP id 50A4D37B4CF for ; Fri, 20 Oct 2000 19:54:14 -0700 (PDT) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id VAA00257 for hackers@FreeBSD.org; Fri, 20 Oct 2000 21:52:58 -0500 (CDT) (envelope-from adam) Date: Fri, 20 Oct 2000 21:52:56 -0500 From: "G. Adam Stanislav" To: hackers@FreeBSD.org Subject: Assembly Journal article Message-ID: <20001020215256.A239@whizkidtech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wanted to let you all know that I have submitted my second article on FreeBSD assembly language programming to Assembly Language Journal. (The first one was published in Issue 8: http://asmjournal.freeservers.com/ ) If you want to read it before it is published, see http://www.whizkidtech.net/args.txt . If you want the code from the article, download http://www.whizkidtech.net/args.asm and assemble it with NASM: nasm -f elf args.asm ld -o args args.o strip args Cheers, Adam -- Don't send me spam, I'm a vegetarian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 4:30:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 9798537B4C5 for ; Sat, 21 Oct 2000 04:30:45 -0700 (PDT) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13mwrM-00064d-01; Sat, 21 Oct 2000 13:30:44 +0200 Received: (from naddy@localhost) by kemoauc.mips.inka.de (8.11.0/8.11.0) id e9LBS0C67484 for freebsd-hackers@freebsd.org; Sat, 21 Oct 2000 13:28:00 +0200 (CEST) (envelope-from naddy) Date: Sat, 21 Oct 2000 13:28:00 +0200 From: Christian Weisgerber To: freebsd-hackers@freebsd.org Subject: Anybody want to review vi patch? Message-ID: <20001021132800.A67078@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline There's a bug in nvi 1.79. The options "noprint", "print", and "octal" don't work properly. When these options are changed, the routine that evaluates them is called before the option has been set. Do we have any people who know their way around the guts of nvi? I've appended a patch, partly based on a change in nvi 1.81 where this is fixed incompletely, and I'd like somebody to review this. -- Christian "naddy" Weisgerber naddy@mips.inka.de --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="nvi.patch" diff -ur /usr/src/contrib/nvi/common/options.c nvi/common/options.c --- /usr/src/contrib/nvi/common/options.c Sat Apr 19 01:36:33 1997 +++ nvi/common/options.c Sat Oct 21 13:06:06 2000 @@ -132,7 +132,7 @@ /* O_NUMBER 4BSD */ {"number", f_reformat, OPT_0BOOL, 0}, /* O_OCTAL 4.4BSD */ - {"octal", f_print, OPT_0BOOL, 0}, + {"octal", f_octal, OPT_0BOOL, 0}, /* O_OPEN 4BSD */ {"open", NULL, OPT_1BOOL, 0}, /* O_OPTIMIZE 4BSD */ diff -ur /usr/src/contrib/nvi/common/options_f.c nvi/common/options_f.c --- /usr/src/contrib/nvi/common/options_f.c Fri Nov 1 07:45:38 1996 +++ nvi/common/options_f.c Sat Oct 21 13:11:14 2000 @@ -190,6 +190,34 @@ char *str; u_long *valp; { + /* Preset the value, needed for reinitialization of lookup table. */ + if (o_set(sp, op-sp->opts, OS_STRDUP, str, 0)) + return(1); + + /* Reinitialize the key fast lookup table. */ + v_key_ilookup(sp); + + /* Reformat the screen. */ + F_SET(sp, SC_SCR_REFORMAT); + return (0); +} + +/* + * PUBLIC: int f_octal __P((SCR *, OPTION *, char *, u_long *)); + */ +int +f_octal(sp, op, str, valp) + SCR *sp; + OPTION *op; + char *str; + u_long *valp; +{ + /* Preset the value, needed for reinitialization of lookup table. */ + if (*valp) + O_CLR(sp, op - sp->opts); + else + O_SET(sp, op - sp->opts); + /* Reinitialize the key fast lookup table. */ v_key_ilookup(sp); diff -ur /usr/src/contrib/nvi/include/com_extern.h nvi/include/com_extern.h --- /usr/src/contrib/nvi/include/com_extern.h Fri Nov 1 07:45:31 1996 +++ nvi/include/com_extern.h Sat Oct 21 13:05:53 2000 @@ -157,6 +157,7 @@ int f_msgcat __P((SCR *, OPTION *, char *, u_long *)); int f_paragraph __P((SCR *, OPTION *, char *, u_long *)); int f_print __P((SCR *, OPTION *, char *, u_long *)); +int f_octal __P((SCR *, OPTION *, char *, u_long *)); int f_readonly __P((SCR *, OPTION *, char *, u_long *)); int f_recompile __P((SCR *, OPTION *, char *, u_long *)); int f_reformat __P((SCR *, OPTION *, char *, u_long *)); --UugvWAfsgieZRqgk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 5:47: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F2FB37B4CF for ; Sat, 21 Oct 2000 05:47:06 -0700 (PDT) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13my3F-0008HS-00; Sat, 21 Oct 2000 14:47:05 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.0/8.11.0) id e9LCkqr70781 for freebsd-hackers@freebsd.org; Sat, 21 Oct 2000 14:46:52 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Anybody want to review vi patch? Date: Sat, 21 Oct 2000 12:46:51 +0000 (UTC) Message-ID: <8ss37r$24n8$1@kemoauc.mips.inka.de> References: <20001021132800.A67078@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > I've appended a patch, partly based on a change in nvi 1.81 where Actually, the NetBSD people have already fixed this, and in a much better way. I'll submit a PR. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 9:36: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E36637B479; Sat, 21 Oct 2000 09:36:02 -0700 (PDT) Received: from tellurian.com (unverified [208.59.162.242]) by gate.tellurian.net (Rockliffe SMTPRA 4.2.4) with ESMTP id ; Sat, 21 Oct 2000 12:36:16 -0400 Message-ID: <39F1C652.9ADA7EB0@tellurian.com> Date: Sat, 21 Oct 2000 12:37:38 -0400 From: Marko Ruban X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,uk MIME-Version: 1.0 To: Tony Fleisher Cc: FreeBSD questions , freebsd-hackers@FreeBSD.ORG Subject: Re: Routing issue with cable modem References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I tried tcpdump, and it's reporting the same malformed MAC and same erroneous protocol type. I guess that means, that the packets are trully bad... correct ? I will try rebuilding my kernel once again. I would like to track this problem to the source, I guess stdlib is where I would find the basic functions the build packets and throw them onto the net. I would appreciate any help as to which files/subroutines I should look into. Also, would be great to get some help from someone that knows their way around core system sources :) (I've never been there before) Tony Fleisher wrote: > Hello, > > Have you perhaps updated to a new kernel since you installed ethereal? > I seem to recall seing similiar situations to this when some data > structures changed sizes. > > Is "/usr/sbin/tcpdump -e" showing this same MAC address corruption > you describe? > > If not, I would recommend rebuilding ethereal. > > TOny. > > On Fri, 20 Oct 2000, Marko Ruban wrote: > > > New issue seems to be at hand... > > > > I set the alias for the interface to be the gateway IP (10.17.56.12), and then I was > > able to add that as my default gateway. Not sure why aliasing wouldn't work with > > 10.17.56.11 or some other IP in that subnet. > > > > I tried to ping the DNS server after that, and watched hundreds of corrupt packets > > get sent out with no replies. > > So my new question is, which part of the system actually builds the packets ? Any > > way to debug or log that process ? > > > > Here's an example taken from ethereal output.... (view with proportional font) > > --------------------------------------------------------- > > Frame 6 (102 on wire, 102 captured) > > Arrival Time: Oct 20, 2000 16:42:38.2715 > > Time delta from previous packet: 0.000071 seconds > > Frame Number: 6 > > Packet Length: 102 bytes > > Capture Length: 102 bytes > > Ethernet II > > Destination: 02:00:00:00:52:54 (02:00:00:00:52:54) > > Source: 05:f4:21:3f:52:54 (05:f4:21:3f:52:54) > > Type: Unknown (0x05f4) > > Data (88 bytes) > > > > 0 0200 0000 5254 05f4 213f 5254 05f4 213f ....RT..!?RT..!? > > 10 0800 4500 0054 13fa 0000 fa01 97dc 0a11 ..E..T.......... > > 20 380c cfac 0309 0800 c1f0 6101 0000 3eae 8.........a...>. > > 30 f039 b722 0400 0809 0a0b 0c0d 0e0f 1011 .9."............ > > 40 1213 1415 1617 1819 1a1b 1c1d 1e1f 2021 .............. ! > > 50 2223 2425 2627 2829 2a2b 2c2d 2e2f 3031 "#$%&'()*+,-./01 > > 60 3233 3435 3637 234567 > > --------------------------------------------------------- > > > > Why I think this packet is malformed..... > > > > First of all, protocol type Unknown (0x05f4) looks definitely bad. > > Secondly, protocol type looks like part of my NICs MAC address (52:54:05:f4:21:3f > > according to ifconfig, which translates into hex: 0x5254 05f4 213f). > > Thirdly, source address decoded by ethereal (and probably by any other packet > > processor) is wrong (first two bytes are carried over to the other side). > > > > Now, keeping all that in mind, lets do a pattern match on the REAL MAC address in > > hex dump of the packet. > > HEY, the source address actually starts four bytes later than it should, thus > > shifting the TRUE protocol type (0x0800 = IP) as well. > > > > First six bytes are the destination MAC, then come the EVIL 4 bytes, followed by 6 > > bytes of source MAC. > > I don't know what's going on, but looks pretty bad, yet simple on the hex level :) > > > > Any ideas ? > > > > > > > > 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-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 10:57: 6 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 63F5537B479 for ; Sat, 21 Oct 2000 10:57:05 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9LHugA81909; Sat, 21 Oct 2000 10:56:43 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Christian Weisgerber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Anybody want to review vi patch? In-Reply-To: Message from Christian Weisgerber of "Sat, 21 Oct 2000 13:28:00 +0200." <20001021132800.A67078@kemoauc.mips.inka.de> Date: Sat, 21 Oct 2000 10:56:42 -0700 Message-ID: <81906.972151002@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do we have any people who know their way around the guts of nvi? > I've appended a patch, partly based on a change in nvi 1.81 where > this is fixed incompletely, and I'd like somebody to review this. I've forwarded this message to Keith Bostic since nobody would know better than he. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 13: 7:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 0635437B479 for ; Sat, 21 Oct 2000 13:07:33 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id EB45E6A905 for ; Sat, 21 Oct 2000 22:07:31 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id A8C6FF030054; Sat, 21 Oct 2000 22:12:54 +0200 Message-Id: <5.0.0.25.0.20001021220609.0355c8e0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 21 Oct 2000 22:07:36 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: can't build custom kernel Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hackers, Sorry to bother, but two postings to -question of the msg below in two days got now response. I'm dead in the water. tia, Len ================================================ FreeBSD 4.1.1 from an .iso image Making a custom kernal make depend gives: In file included from ../../i386/isa/isa_compat.c:46: ../../i386/isa/isa_compat.h:42: bw.h: No such file or directory mkdep: compile failed *** Error code 1 I cannot find / -name "bw.h" -print ... this file on our disk. Nor can I find "bw.h" in my -questions archive as a pb for anybody else. What's up? tia, Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 & 8.2.3 T6B for NT4 & W2K http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 13:29:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brutus.conectiva.com.br (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 7668537B4C5 for ; Sat, 21 Oct 2000 13:27:18 -0700 (PDT) Received: from localhost (riel@localhost) by brutus.conectiva.com.br (8.10.2/8.10.2) with ESMTP id e9LKQmG00500; Sat, 21 Oct 2000 18:26:52 -0200 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Sat, 21 Oct 2000 18:26:48 -0200 (BRDT) From: Rik van Riel X-Sender: riel@duckman.distro.conectiva To: Stephen Hocking Cc: hackers@FreeBSD.ORG Subject: Re: Getting Linux NIS to work with FreeBSD NIS servers In-Reply-To: <200010160323.e9G3N5G48210@bloop.craftncomp.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 Sun, 15 Oct 2000, Stephen Hocking wrote: > The Linux box appears toknow about the users, it just cant get > the passwords right - something tickles my mind about DES vs > MD5, is this the case, and how do I convert my MD5 passwords if > needed? Not needed. Configure both machines to use the same crypt for the passwords. (for linux it should be nothing more than editing the right file in /etc/pam.d/ and regenerating the passwords for all "local" users) regards, Rik -- "What you're running that piece of shit Gnome?!?!" -- Miguel de Icaza, UKUUG 2000 http://www.conectiva.com/ http://www.surriel.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 13:53:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id BA2DD37B4C5 for ; Sat, 21 Oct 2000 13:53:28 -0700 (PDT) Received: from server.wes.mee.com (p3E9D16D0.dip.t-dialin.net [62.157.22.208]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id WAA06369; Sat, 21 Oct 2000 22:52:52 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.11.0/8.11.0) with ESMTP id e9LIe7J08056; Sat, 21 Oct 2000 20:40:07 +0200 (CEST) (envelope-from frederik@freddym.org) Date: Sat, 21 Oct 2000 20:40:07 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: "phpStop.com" Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux In-Reply-To: <39F09EF1.E2AB0438@phpStop.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! > If this is not the right place to ask such questions, please forgive me > and I'll appreciate it if you can forward me to the right place. Well, freebsd-qustions would be more specific, but that won't matter. > Is there any detailed information or technical sheet about the > difference between FreeBSD and Linux? Also, what are the advantages over > the disadvantages of each of the mentioned OS's? Differences... FreeBSD is a real Unix, while Linux is a ..how should I say... semi Unix. IMHO FreeBSD ist lots faster than Linux, as I had Linux on my server before, and when I changed to FreeBSD everything ran faster. > If someone could point me to a technical page, also, that indicates > FreeBSD's and Linux's performance when running Apache, PHP and MySQL? I can tell you very much about this. I administer a server with Apache PHP3 and MySQL. First, there was Linux on it, (it's a Pentium 90) and then I put FreeBSD on it. It's a real difference. FreeBSD runs much faster with Apache MySQL and PHP3. > We need this information in order to determine which of these two OS to > choose from to drive our website. Choose FreeBSD. It's faster. -- Best Regards, Freddy ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 14:24:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-99.zoominternet.net [24.154.28.99]) by hub.freebsd.org (Postfix) with ESMTP id E380837B4CF for ; Sat, 21 Oct 2000 14:24:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.11.0/8.11.1) with ESMTP id e9LLP1407583 for ; Sat, 21 Oct 2000 17:25:01 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sat, 21 Oct 2000 17:25:01 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: freebsd-hackers@freebsd.org Subject: Re: can't build custom kernel In-Reply-To: <5.0.0.25.0.20001021220609.0355c8e0@mail.Go2France.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, 21 Oct 2000, Len Conrad wrote: > Hackers, > > Sorry to bother, but two postings to -question of the msg below in > two days got now response. I'm dead in the water. First thing: read /usr/src/UPDATING. The proper procedure to build a kernel is in there. To save you some time: cd /usr/src make buildkernel KERNEL= make installkernel KERNEL= If the build still fails, then yes, you have a legitimate problem. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 14:37:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 82AED37B4C5 for ; Sat, 21 Oct 2000 14:37:15 -0700 (PDT) Received: from server.wes.mee.com (pC19EB34C.dip.t-dialin.net [193.158.179.76]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id XAA26274; Sat, 21 Oct 2000 23:37:13 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.11.0/8.11.0) with ESMTP id e9LLXHJ18837; Sat, 21 Oct 2000 23:33:17 +0200 (CEST) (envelope-from frederik@freddym.org) Date: Sat, 21 Oct 2000 23:33:17 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: Sergey Babkin Cc: "phpStop.com" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux In-Reply-To: <39F209DF.88368125@bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > > > > > We need this information in order to determine which of these two OS to > > > choose from to drive our website. > > > > Choose FreeBSD. It's faster. > > Also if some things don't work or work strangely or are poorly > documented, finding sources for them is MUCH easier in FreeBSD. Linux Huh?! What's strange in FreeBSD? -- Best Regards, Freddy ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 14:39:46 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 3928237B4C5 for ; Sat, 21 Oct 2000 14:39:44 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-141.nnj.dialup.bellatlantic.net [151.198.117.141]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA26161; Sat, 21 Oct 2000 17:25:52 -0400 (EDT) Message-ID: <39F209DF.88368125@bellatlantic.net> Date: Sat, 21 Oct 2000 17:25:51 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Frederik Meerwaldt Cc: "phpStop.com" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. Linux References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frederik Meerwaldt wrote: > > > We need this information in order to determine which of these two OS to > > choose from to drive our website. > > Choose FreeBSD. It's faster. Also if some things don't work or work strangely or are poorly documented, finding sources for them is MUCH easier in FreeBSD. Linux is a patchwork of independent packages, and tracking down what came from where and was patched by what is usually not easy. Also commercial distributions of Linux sometimes tend to "lose" parts of sources, so that you will not always be able to re-compile the stuff at all. There's been a short period when I worked on building a Linux distribution and that was a quite special experience. I you would want to get a Linux after all I would strongly recommend getting a free distribution like Debian or Slackware. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 15: 8:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 2685F37B479 for ; Sat, 21 Oct 2000 15:08:37 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 0E7606A905 for ; Sun, 22 Oct 2000 00:08:35 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id A535193D0054; Sun, 22 Oct 2000 00:14:13 +0200 Message-Id: <5.0.0.25.0.20001022000602.00b072d0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sun, 22 Oct 2000 00:08:46 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: can't build custom kernel In-Reply-To: References: <5.0.0.25.0.20001021220609.0355c8e0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First thing: read /usr/src/UPDATING. but I'm not UPDATING, I've installed to virgin disk from 4.1.1 iso-image. >The proper procedure to >build a kernel is in there. To save you some time: > > cd /usr/src > make buildkernel KERNEL= > make installkernel KERNEL= > > If the build still fails, then yes, you have a legitimate problem. With this pb from a fresh 4.1.1 cdrom install, a legit pb or is it me? thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 15:21:54 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 6ED5F37B479 for ; Sat, 21 Oct 2000 15:21:52 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA60015; Sat, 21 Oct 2000 15:21:42 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39F216F5.F2AE8184@gorean.org> Date: Sat, 21 Oct 2000 15:21:41 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-101 i386) X-Accept-Language: en MIME-Version: 1.0 To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: can't build custom kernel References: <5.0.0.25.0.20001021220609.0355c8e0@mail.Go2France.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad wrote: > > Hackers, > > Sorry to bother, but two postings to -question of the msg below in > two days got now response. I'm dead in the water. > > tia, > Len > > ================================================ > > FreeBSD 4.1.1 from an .iso image > > Making a custom kernal > > make depend > > gives: > > In file included from ../../i386/isa/isa_compat.c:46: > ../../i386/isa/isa_compat.h:42: bw.h: No such file or directory > mkdep: compile failed > *** Error code 1 Your sources are corrupt. There has never been a 'bw.h' file in the FreeBSD tree. How did you install the sources? You might want to delete them and install a fresh set with cvsup. Take a look at http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/isa_compat.h?rev=1.27.2.6&content-type=text/x-cvsweb-markup for the current version of this file in RELENG_4. Good luck, 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 Oct 21 15:35:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id CCF4437B479 for ; Sat, 21 Oct 2000 15:35:47 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 0083C6A905 for ; Sun, 22 Oct 2000 00:35:40 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AB8E1F6E0054; Sun, 22 Oct 2000 00:41:18 +0200 Message-Id: <5.0.0.25.0.20001022003157.0356cc80@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sun, 22 Oct 2000 00:35:59 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: can't build custom kernel In-Reply-To: <39F216F5.F2AE8184@gorean.org> References: <5.0.0.25.0.20001021220609.0355c8e0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Your sources are corrupt. There has never been a 'bw.h' file in the >FreeBSD tree. How did you install the sources? from 4.1.1-R .iso image from ftp.de.freebsd.org >You might want to delete them and install a fresh set with cvsup. dennis@etinc.com has since told me his etinc drivers don't work with 4.1.1 so I've got to drop back to 4.1, for which I have the .iso on cdrom. >Good luck, thanks, an fbsd airhead like me needs it. First time I've been bitten by an .iso image. Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 & 8.2.3 T6B for NT4 & W2K http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 17:30:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id D656337B4C5 for ; Sat, 21 Oct 2000 17:30:14 -0700 (PDT) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.0/8.11.0) with ESMTP id e9M0Vod20577 for ; Sat, 21 Oct 2000 17:31:50 -0700 (PDT) Date: Sat, 21 Oct 2000 17:31:50 -0700 (PDT) From: FengYue X-Sender: fengyue@shell.unixbox.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux 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 Sat, 21 Oct 2000, Frederik Meerwaldt wrote: ->Differences... FreeBSD is a real Unix, while Linux is a ..how should I Hmmm. FreeBSD is not a UNIX, rather it's a UNIX alike OS. (Which really doesn't matter IMHO) Don't forget UNIX is a trademark of Open Group. ->say... semi Unix. IMHO FreeBSD ist lots faster than Linux, as I had Linux ->on my server before, and when I changed to FreeBSD everything ran faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 17:46:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id A5CED37B4C5 for ; Sat, 21 Oct 2000 17:46:43 -0700 (PDT) Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24]) by thehousleys.net (8.11.0/8.11.0) with ESMTP id e9M0kUQ75486; Sat, 21 Oct 2000 20:46:31 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39F238E5.309444B1@thehousleys.net> Date: Sat, 21 Oct 2000 20:46:29 -0400 From: James Housley X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: FengYue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD vs. Linux References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FengYue wrote: > > On Sat, 21 Oct 2000, Frederik Meerwaldt wrote: > > ->Differences... FreeBSD is a real Unix, while Linux is a ..how should I > > Hmmm. FreeBSD is not a UNIX, rather it's a UNIX alike OS. (Which really > doesn't matter IMHO) > > Don't forget UNIX is a trademark of Open Group. > I believe a correct and true statement is "FreeBSD is a direct decendant of Unix(TM). Based on the BSD sources" Jim -- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net --------------------------------------------------------------------- If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's windows. -- Luiz de Barros To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 21 19:26: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id DF2C537B4C5 for ; Sat, 21 Oct 2000 19:26:03 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id FAA67230 for ; Sun, 22 Oct 2000 05:25:58 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id FAA51147 for ; Sun, 22 Oct 2000 05:29:54 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Sun, 22 Oct 2000 05:29:54 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.org Subject: Problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I try to use hfsutils - program for accessing Macintosh HFS floppy disks and CDROm's and when I try to run hmount /dev/cd0a I have SCSI CDROM I receive dscheck(#cd/0): b_bcount 512 is not on a sector boundary (ssize 2048) What is the matter is my CD bad or smth else, may be I bad understood help... Thank you very much for your help... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message